IP Library Granted Patent US 8,737,594
Granted Patent B2
US 8,737,594 · App. 13/021,134 · Granted May 27, 2014

Emergency services for packet networks

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,737,594
App. No.
13/021,134
Granted
May 27, 2014
Kind
B2
Abstract

The present invention provides a technique for facilitating emergency services via packet networks. Emergency service providers will implement emergency proxies to ensure that proper call setup requests for emergency services are forwarded to the appropriate entities, even if those entities are in overload conditions. The emergency proxies may authenticate and filter call setup requests to ensure that only proper call setup requests are forwarded to help prevent such overload conditions. The emergency proxies may operate solely in a packet network, as well as at the interface between a packet network and a circuit-switched network to assist in call setup requests originating from either the packet network or the circuit-switched network.

Claims (41)

1. A method of controlling access to an emergency service, comprising:

receiving at least one call setup request from at least one originating device;

determining whether a received call setup request is received from a user who is authorized to initiate a call to the emergency service;

selecting a priority level from a plurality of priority levels for the call setup request;

inserting at least one indication of the determination and the selected priority level into the call request; and

forwarding the call request including the at least one indication toward at least one terminating device associated with the emergency service, wherein at least one of the originating devices or terminating devices resides on a packet network.

2. A method as recited in claim 1 , wherein received call setup requests determined to be received from users who are not authorized to initiate a call to the emergency service are not forwarded toward terminating devices associated with the emergency service.

3. A method as recited in claim 1 , further comprising creating emergency information for each call setup request determined to be received from a user who is authorized to initiate a call to the emergency service;

wherein the step of inserting at least one indication of the determination and the selected priority level into the call request comprises inserting the emergency information into the call setup request.

4. A method as recited in claim 1 , wherein the step of inserting at least one indication of the determination and the selected priority level comprises inserting the at least one indication of the determination and the selected priority level into a header of the call setup request.

5. A method as recited in claim 1 , wherein the step of forwarding the call request is dependent on the step of determining whether the received call request is from a user who is authorized to initiate a call to the emergency service, at least when at least one network resource required to forward the call request toward the at least one terminating device or at least one of the terminating devices is in an overload condition.

6. A method as recited in claim 5 , wherein a call request is not forwarded toward the at least one terminating device when the received call request is determined not to be from a user who is authorized to initiate a call to the emergency service.

7. A method as recited in claim 1 , further comprising registering users authorized to initiate calls to the emergency service in response to received registration messages.

8. A method as recited in claim 1 , further comprising processing the call setup request in accordance with the selected priority level at a network element upstream of at least one terminating device associated with the emergency service.

9. A method as recited in claim 1 , wherein the call setup request is a request for a communication session of a type selected from the group consisting of data, audio, voice and video.

10. A system for controlling access to an emergency service, comprising:

at least one communication interface; and

a control system associated with the at least one communication interface and configured to:

receive at least one call setup request from at least one originating device;

determine whether a received call setup request is received from a user who is authorized to initiate a call to the emergency service;

select a priority level from a plurality of priority levels for the call setup request;

insert at least one indication of the determination and the selected priority level into the call request; and

forward the call request including the at least one indication toward at least one terminating device associated with the emergency service, wherein at least one of the originating devices or terminating devices resides on a packet network.

11. A system as recited in claim 10 , wherein the control system is configured to not forward toward terminating devices associated with the emergency service received call setup requests determined to be received from users who are not authorized to initiate a call to the emergency service.

12. A system as recited in claim 10 , wherein the control system is further configured to:

to create emergency information for each call setup request determined to be received from a user who is authorized to initiate a call to the emergency service; and

to insert the emergency information into the call setup request.

13. A system as recited in claim 10 , wherein the control system is configured to insert at least one indication of the determination and the selected priority level by inserting the at least one indication of the determination and the selected priority level into a header of the call setup request.

14. A system as recited in claim 10 , wherein the control system is configured to forward the call request dependent on the determination of whether the received call request is from a user authorized to initiate a call to the emergency service, at least when at least one network resource required to forward the call request toward the at least one terminating device or at least one of the terminating devices is in an overload condition.

15. A system as recited in claim 14 , wherein the control system is configured to not forward a call request toward the at least one terminating device when the received call request is determined not to be from a user who is authorized to initiate a call to the emergency service.

16. A system as recited in claim 10 , wherein the control system is further configured to register users authorized to initiate calls to the emergency service in response to received registration messages.

17. A system as recited in claim 10 , further comprising at least one network element upstream of at least one terminating device associated with the emergency service, the network element being configured to process the call setup request in accordance with the selected priority level.

18. A non-transitory computer-readable medium carrying software for controlling access to an emergency service, the software comprising instructions executable by a processor to:

receive at least one call setup request from at least one originating device;

determine whether a received call setup request is received from a user who is authorized to initiate a call to the emergency service;

select a priority level from a plurality of priority levels for the call setup request;

insert at least one indication of the determination and the selected priority level into the call request; and

forward the call request including the at least one indication toward at least one terminating device associated with the emergency service;

wherein at least one of the originating devices or terminating devices resides on a packet network.

19. A computer-readable medium as recited in claim 18 , wherein the instructions executable to forward the call request are executed dependent on the determination of whether the received call request is from a user who is authorized to initiate a call to the emergency service, at least when at least one network resource required to forward the call request toward the at least one terminating device or at least one of the terminating devices is in an overload condition.

20. A computer-readable medium as recited in claim 18 , wherein the instructions further comprise instructions executable to register users authorized to initiate calls to the emergency service in response to received registration messages.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 10, 2013
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 031749/0498 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →