IP Library Granted Patent US 9,591,467
Granted Patent B2
US 9,591,467 · App. 14/792,028 · Granted Mar 7, 2017

Routing engine for emergency communications

Inventors: William Todd Piett (Southborough, MA); Matthew A. Serra (Newton, MA); Brett Wilfred Marceau (Clinton, MA)
Assignee: Rave Wireless, Inc.
H04W4/22G06F17/30979H04W4/02H04W4/025
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 9,591,467
App. No.
14/792,028
Granted
Mar 7, 2017
Kind
B2
Abstract

A computer-implemented method for processing emergency calls includes receiving an emergency call from a calling device via a first communication format, identifying a location associated with the calling device, identifying a destination for the emergency call based at least in part on the location, determining an attribute associated with the destination, and determining an action to be taken based at least in part on the first communication format and on the attribute.

Claims (11)

1. An apparatus for processing emergency calls, said apparatus comprising a processor and memory, wherein said memory comprises instructions that, when executed by said processor, cause said processor to implement a routing engine, a rules engine, and a rules database, wherein said rules engine and said rules database are constituents of said routing engine, wherein said rules database is in communication with said rules engine, wherein said routing engine is configured-to receive an emergency call in a first communication format from a calling device, wherein said routing engine is configured to determine an attribute associated with a destination of said emergency call, wherein said routing engine is configured to cause execution of an action based at least in part on said attribute, and wherein said rules engine is configured to select a rule from said rules database based at least in part on said attribute of said destination.

2. The apparatus of claim 1 , wherein said routing engine is further configured to cause execution of an action based at least in part on an attribute of a caller originating said emergency call.

3. The apparatus of claim 1 , wherein said routing engine comprises a shim between communication networks implementing different communication formats.

4. The apparatus of claim 1 , wherein said routing engine processes emergency calls based on context thereof.

5. The apparatus of claim 1 , wherein said rules database comprises rules for processing emergency calls based on an extent to which said destination is NG-9-1-1 enabled.

6. The apparatus of claim 1 , wherein said routing engine comprises an automated attendant that responds to said calling device with instructions to select an alternative communication format.

7. The apparatus of claim 1 , wherein said routing engine is configured to inspect content of said emergency call and to execute an action based on said content.

8. The apparatus of claim 1 , wherein said routing engine is configured cause execution of said action based at least in part on metadata accompanying said emergency call.

9. An apparatus for directing emergency calls to one of a plurality of destinations, said apparatus comprising a processor and a memory, wherein said memory stores instructions that, when executed, cause said processor to implement a routing engine, a rules engine, a location module, and a rule database, wherein said rule database is in communication with said rules engine, wherein said routing engine is configured to receive an emergency call in a first communication format from a calling device, wherein said routing engine is configured to designate one of a plurality of destinations as a designated destination for said emergency call, wherein said location module is configured for determining a location from which said emergency call originates, wherein said rules engine is configured to determine at least one attribute of said candidate destinations, and wherein said rules engine is configured to designate a destination based at least in part on said first communication format and said at least one attribute of said candidate destinations.

10. The apparatus of claim 9 , wherein said routing engine is further configured to trans-code said emergency call from said first communication format into a second communication format, said second communication format being one that can be understood by said designated destination.

11. The apparatus of claim 9 , wherein said routing engine is further configured to select, as a designated destination for said emergency call, a destination that is incapable of understanding said first communication format.

Assignments (5)
NOTICE OF RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Dec 16, 2022
From: ANTARES CAPITAL LP, AS COLLATERAL AGENT
To: RAVE WIRELESS, INC.; SWIFTREACH NETWORKS, LLC
Reel/Frame 062141/0022 →
PATENT SECURITY AGREEMENT Recorded May 7, 2019
From: RAVE WIRELESS, INC.; SWIFTREACH NETWORKS, LLC
To: ANTARES CAPITAL LP, AS COLLATERAL AGENT
Reel/Frame 049109/0370 →
RELEASE OF SECURITY INTEREST Recorded Apr 23, 2019
From: PNC BANK, NATIONAL ASSOCIATION
To: RAVE WIRELESS, INC.; SWIFTREACH NETWORKS, LLC
Reel/Frame 048975/0921 →
SECURITY INTEREST Recorded Jun 27, 2018
From: RAVE INTERMEDIATE HOLDINGS, INC.; RAVE WIRELESS, INC.
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 046219/0580 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2015
From: PIETT, WILLIAM T.; SERRA, MATTHEW A.; MARCEAU, BRETT WILFRED
To: RAVE WIRELESS INC.
Reel/Frame 036236/0709 →
Continuity (3)
Continuation 13625251 · Sep 24, 2012
Provisional Application 61538505 · Sep 23, 2011
Related Publication 20160192167A1 · Jun 30, 2016