IP Library Granted Patent US 8,559,601
Granted Patent B2
US 8,559,601 · App. 12/344,819 · Granted Oct 15, 2013

Handling emergency service calls originating from internet telephony

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,559,601
App. No.
12/344,819
Granted
Oct 15, 2013
Kind
B2
Abstract

A method and system for interfacing internet protocol-enabled emergency calls to a public 9-1-1 system are described. The method can include routing an emergency call originating from internet protocol telephony to a data network via a routing device which may include an identifier. The method can include transferring the routed emergency call to a predetermined public service answering point based on the identifier.

Claims (34)

1. A routing device comprising:

a memory to store a routing device identifier for the routing device and profile information for an Internet protocol (IP) user device;

a receive unit to receive an emergency call from the IP user device via a first data network;

a processing unit to retrieve a portion of the profile information from the memory and attach the routing device identifier and the retrieved portion of the profile information to the emergency call, the retrieved portion of the profile information identifying the emergency call as originating from a registered physical location for the IP user device or a different physical location; and

a routing element to route the emergency call along with the retrieved portion of profile information and the routing device identifier to a second data network.

2. The routing device of claim 1 , where the first data network is a local area network.

3. The routing device of claim 2 , where the routing device comprises an edge router associated with the LAN.

4. The routing device of claim 1 , where the IP user device comprises a voice over internet protocol (VoIP) telephony device.

5. The routing device of claim 1 , where the processing unit is further to:

receive, in response to the message being routed, a query associated with the emergency call via the second data network, the query indicating that a server associated with the second data network is unable to identify a physical location of the routing device based on the routing device identifier, and

provide, to the server, a physical location of the routing device based on receiving the query.

6. The routing device of claim 1 , where, when attaching the routing device identifier and the retrieved portion of the profile information to the emergency call, the processing unit is to:

attach the routing device identifier and the retrieved portion of the profile information to a header of the emergency call to associate the routing device with the emergency call.

7. The routing device of claim 1 , where the routing device identifier is associated with:

a primary public service answering point (PSAP),

a secondary PSAP, and

an alternative PSAP.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions which, when executed by one or more processors of a routing device, cause the one or more processors to receive an emergency call from an Internet protocol (IP) user device via a first data network;

one or more instructions which, when executed by the one or more processors, cause the one or more processors to include a device identifier and profile information associated with the IP user device in information transmitted with the emergency call,

the device identifier including information associated with a device that receives the emergency call from the IP user device, and

the profile information identifying the emergency call as:

originating from a first physical location, the first physical location comprising a particular physical location that is associated with the IP user device and is registered with the routing device prior to the routing device receiving the emergency call, or

originating from a second physical location that is different from the first physical location; and

one or more instructions which, when executed by the one or more processors, cause the one or more processors to route the emergency call, including the profile information and the routing device identifier, included in the information transmitted with the emergency call, to a second data network.

9. The computer-readable medium of claim 8 , where the first data network is a local area network (LAN).

10. The computer-readable medium of claim 9 , where the routing device comprises an edge router associated with the LAN.

11. The computer-readable medium of claim 8 , where the IP user device comprises a voice over internet protocol (VoIP) telephony device.

12. The computer-readable medium of claim 8 , where the instructions further comprise:

one or more instructions to receive a query associated with the emergency call, the query being received from a server via the second data network, and

one or more instructions to provide, in response to the query, a physical location of the routing device to the server via the second data network.

13. The computer-readable medium of claim 8 , where the one or more instructions to include the device identifier and the profile information in the information transmitted with the emergency call include:

one or more instructions to include the device identifier and the profile information within a header of the emergency call.

14. The computer-readable medium of claim 8 , where the device identifier is associated with a primary public service answering point (PSAP) and a secondary PSAP.

Assignments (5)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE PREVIOUSLY RECORDED AT REEL: 032734 FRAME: 0502. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Nov 28, 2017
From: VERIZON BUSINESS GLOBAL LLC
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 044626/0088 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 22, 2014
From: VERIZON BUSINESS GLOBAL LLC
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 032734/0502 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2011
From: COSTER, MARK W.; ANDERSON, JOHN R.
To: MCI, INC.
Reel/Frame 027250/0254 →
MERGER Recorded Nov 18, 2011
From: MCI, INC.
To: MCI, LLC
Reel/Frame 027250/0307 →
CHANGE OF NAME Recorded Nov 18, 2011
From: MCI, LLC
To: VERIZON BUSINESS GLOBAL LLC
Reel/Frame 027250/0395 →