E911 location server

• US 9,137,315 B2
• Filed: 11/11/2013
• Issued: 09/15/2015
• Est. Priority Date: 11/16/2005
• Status: Active Grant

• Current Assignee: Rakuten Group, Inc.
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Eichen, Elliot G., Sporel, Eric R., Mitsumori, Derek, Olshansky, Robert
• Primary Examiner(s): NGUYEN, QUYNH H
• Application Number:
  US14/077,152
• Publication Number:
  US 20140071981A1
• Time in Patent Office: 673 Days
• Field of Search: 370/352, 370/351, 370/353, 370/354, 370/355, 370/356, 379/45, 379/106.01, 379/201.06, 379/201.1, 455/456.5, 709/224
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04M 2242/30 Determination of the location of a subscriber
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 12/088 using filters or firewalls
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 76/50 for emergency connections
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support

Abstract

A system including a location server configured to receive registration data from an IP device and a location database configured to store location information of the IP device, wherein the location server queries the location database to determine whether the registration data matches the location information stored at the location database.

Claims

1. A system comprising:

a location server configured to monitor a register message associated with an Internet Protocol (IP) device, wherein the register message includes a source IP address and a second IP address; and

a location database configured to store physical location information and a plurality of IP addresses associated with the IP device, wherein the location server determines whether at least one of the source IP address and the second IP address of a selected message corresponds with any of the plurality of IP addresses associated with the IP device;

acquires, based on the determination, physical location information corresponding to at least one of the source IP address and the second IP address; and

transmits a message using a number associated with the at least one of the source IP address and the second IP address, wherein the transmitted message requests the location of the IP device.

2. The system of claim 1, wherein the location server acquires the physical location information corresponding to at least one of the source IP address and the second IP address if at least one of the source IP address and the second IP address do not correspond with any of the plurality of IP addresses associated with the IP device.

3. The system of claim 1, wherein the plurality of IP addresses associated with the IP device include a source address and a second IP address from a previous register message.

4. The system of claim 1, wherein the location server can provide the physical location information to a service bureau.

5. The system of claim 1, wherein the physical location information includes an emergency number identifier.

6. The system of claim 1, wherein the plurality of IP addresses associated with the IP device are compared with both the source IP address and the second IP address.

7. The system of claim 1, wherein the location server determines whether at least one of the source IP address and the second IP address of a selected message corresponds with any of the plurality of IP addresses includes the location determines whether both the source IP address and the second IP address of the selected message correspond with the plurality of IP addresses associated with the IP device.

8. The system of claim 1, wherein the location database is configured to store an association between physical location information and at least a portion of an IP address.

9. The system of claim 8, wherein the acquired physical location information corresponds to physical location information associated with at least a portion of the IP address that matches at least one of the source IP address and at least a portion of the second IP address.

10. The system of claim 1, wherein the source IP address is a public IP address and the second IP address is a private IP address.

11. The system of claim 10, wherein the private IP address is provided by a Session Initiation Protocol header within the register message.

12. The system of claim 10, wherein the private IP address is provided by a via header within the register message.

13. A method comprising:

monitoring messages from an Internet Protocol (IP) device, wherein at least some of the messages provide a source IP address and a second IP address;

determining whether at least one of the source IP address and the second IP address of a selected message corresponds with any of a plurality of IP addresses associated with the IP device;

acquiring, based on the determination, physical location information corresponding to at least one of the source IP address and the second IP address; and

transmitting a message using a number associated with the at least one of the source IP address and the second IP address, wherein the transmitted message requests the location of the IP device.

14. The method of claim 13, wherein acquiring physical location information includes acquiring physical location information associated with at least one of the source IP address and the second IP address that does not correspond with any of the plurality of IP addresses associated with the IP device.

15. The method of claim 13, wherein the acquired physical location information corresponds to physical location information associated with at least a portion of an IP address that matches at least one of the source IP address and at least a portion of the second IP address.

16. The method of claim 13, wherein the physical location information includes an emergency number identifier.

17. The method of claim 13, wherein the source IP address is a public IP address and the second IP address is a private IP address.

18. The method of claim 17, wherein the private IP address is located in a Session Initiation Protocol header within the selected message.

19. The method of claim 17, wherein the private IP address is located in a via header within the selected message.

20. A method comprising:

providing a plurality of Internet Protocol (IP) addresses that have a stored association with an IP device;

receiving a query for physical location information, wherein the query is a result of at least one of a source IP address and a second IP address, both of which are provided by a register message originating from the IP device, not corresponding with any of the plurality of IP addresses that have the stored association with the IP device and wherein the at least one of the source IP address and the second IP address are not associated with a current physical location information of the IP device; and

indicating to a server that the current physical information of the IP device is unknown, wherein the indication notifies the server to transmit a message using a number associated with the at least one of the source IP address and the second IP address and wherein the transmitted message requests the location of the IP device.