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

• US 20100246567A1
• 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,462,769 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• 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

Abstract

A system and method for creating a location uniform resource identifier (“URI”) for determining the location of a target device. A location request may be received for a target device. Location context information may be collected for the target device including starting information, validating information and policy information. This collected location context information may be encrypted in a location information server and converted to a form compatible with URI syntax. A location URI may then be constructed as a function of the converted information.

Claims

1. A method for creating a location uniform resource identifier (“

URI”

) for determining the location of a target device, comprising the steps of;

(a) receiving a location request for a target device;

(b) collecting location context information for the target device including starting information, validating information and policy information;

(c) encrypting the collected location context information in a location information server (“

LIS”

);

(d) converting the encrypted location context information to a form compatible with URI syntax; and

(e) constructing a location URI as a function of the converted information.

2. The method of claim 1 further comprising the step of determining an estimated location of the target device as a function of the constructed location URI.

3. The method of claim 1 further comprising the step of providing the constructed location URI to a requesting entity.

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

5. The method of claim 1 wherein the step of collecting location context information includes determining the target device'"'"'s Media Access Control address or Internet Protocol address.

6. The method of claim 1 wherein the location URI includes a host address of the LIS, an encrypted context string, and addressing information based on protocol, routing, and network details.

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 LIS comprises one or more processing units at one or more processing sites.

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

10. The method of claim 1 wherein the validating information includes information correlating the starting information with the target device.

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

12. The method of claim 1 wherein the location request is in a geodetic location form, a civic location form or a location URI form.

13. 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.

14. A location information server (“

LIS”

) comprising;

(a) circuitry for receiving a location request for a target device;

(b) circuitry for collecting location context information for the target device including starting information, validating information and policy information;

(c) circuitry for encrypting the collected location context information;

(d) circuitry for converting the encrypted location context information to a form compatible with uniform resource identifier (“

URI”

) syntax; and

(e) circuitry for constructing a location URI as a function of the converted information.

15. The LIS of claim 14 further comprising circuitry for verifying the form of the location URI, the form including at least an encrypted context string.

16. The LIS of claim 15 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.

17. The LIS of claim 15 further comprising circuitry for extracting and decrypting the encrypted context string.

18. The LIS of claim 14 further comprising circuitry for determining an estimated location of the target device and for providing the estimated location of the target device to a requesting entity.

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

20. The LIS of claim 14 further comprising one or more processing units at one or more processing sites.

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

URN”

), a uniform resource location (“

URL”

) and combinations thereof.

22. The LIS of claim 14 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.

23. A method for creating a location uniform resource identifier (“

URI”

) for determining the location of a target device, comprising the steps of;

(a) receiving a location request for a target device;

(b) collecting location context information in a location server for the target device including starting information, validating information and policy information;

(c) converting the location context information to a form compatible with URI syntax; and

(d) constructing a location URI as a function of the converted information.