IP Library Granted Patent US 9,078,092
Granted Patent B2
US 9,078,092 · App. 13/625,251 · Granted Jul 7, 2015

Routing engine for emergency communications

Inventors: William T. Piett (Southborough, MA); Matthew A. Serra (Morristown, NJ); Brett Wilfred Marceau (Clinton, MA)
Assignee: Rave Wireless, Inc.
H04W4/02H04W4/22
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,078,092
App. No.
13/625,251
Granted
Jul 7, 2015
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 (28)

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

2. The method of claim 1 , wherein determining an attribute comprises determining an ability of said destination to accept an emergency call in said first communication format.

3. The method of claim 1 , wherein determining an attribute comprises determining that said identified destination cannot accept emergency calls in said first communication format.

4. The method of claim 1 , wherein determining an action comprises determining a routing for said emergency call to said identified destination.

5. The method of claim 1 , wherein determining an action comprises determining that said emergency call is to be routed to an alternative destination, said alternative destination being different from said identified destination.

6. The method of claim 1 , wherein determining an action comprises determining that said first format of said emergency call is to be changed based on a capability of said identified destination.

7. The method of claim 1 , wherein determining an action comprises determining that a responsive communication is to be sent to said calling device.

8. The method of claim 1 , wherein determining an action comprises determining an action based at least in part on a result of a learning algorithm.

9. The method of claim 8 , wherein determining an action based at least in part on a result of a learning algorithm comprises parsing content of said call.

10. The method of claim 8 , wherein determining an action based at least in part on a result of a learning algorithm comprises making an inference based on content of plural emergency calls.

11. The method of claim 1 , wherein determining an action comprises determining said action based at least in part on at least one attribute associated with an emergency caller associated with said calling device.

12. The method of claim 11 , wherein determining said action based at least in part on at least one attribute associated with an emergency caller associated with said calling device comprises determining said action based at least in part on a preferred communication format of said emergency caller.

13. The method of claim 11 , wherein determining said action based at least in part on at least one attribute associated with an emergency caller associated with said calling device comprises determining said action based at least in part on a capability of said calling device.

14. The method of claim 11 , wherein determining said action based at least in part on at least one attribute associated with an emergency caller associated with said calling device comprises determining said action based at least in part on a subscription status of said emergency caller.

15. The method of claim 11 , further comprising identifying at least one attribute associated with said emergency caller.

16. The method of claim 15 , wherein identifying at least one attribute of said emergency caller comprises accessing a caller registry.

17. The method of claim 1 , wherein determining said action includes determining that a query is to be issued to a rules database.

18. The method of claim 1 , further comprising, in response to losing contact with said calling device, reconnecting with said calling device using a second communication format.

19. The method of claim 18 , where said first communication format relies on a first sensory input of said caller and a second communication format relies on said first sensory input.

20. The method of claim 1 , wherein identifying a location occurs after having received said emergency call.

21. A manufacture comprising a tangible and non-transitory computer-readable medium having encoded thereon software for causing a particular data processing system to execute a method that comprises receiving an emergency call from a calling device via a first communication format, identifying a location associated with said calling device, identifying a destination for said emergency call based at least in part on said location, determining an attribute associated with said destination, and determining an action to be taken based at least in part on said first communication format and on said attribute.

22. A computer-implemented method for processing an emergency call, said method comprising determining a location from which said call originates, determining that a communication format associated with said emergency call is a first communication format, based in part on said location, identifying candidate destinations for said emergency call, designating one of said candidate destinations as a designated destination based at least in part on an attribute of said destination and on said first communication format, and causing said emergency call to be forwarded to said destination.

23. The method of claim 22 , wherein identifying candidate destinations comprises identifying an NG9-1-1 compliant destination and a non-NG9-1-1compliant destination.

24. The method of claim 23 , wherein designating one of said candidate destinations comprises designating said NG9-1-1 compliant destination based on an ability thereof to communicate using said first communication format.

25. The method of claim 23 , wherein designating one of said candidate destinations comprises designating said NG9-1-1 non-compliant destination, and wherein said method further comprises trans-coding said emergency call into a second communication format that can be processed by said NG9-1-1 non-compliant destination.

26. The method of claim 23 , wherein designating one of said candidate destinations comprises designating a destination that is incapable of understanding said first communication format.

27. The method of claim 23 , further comprising trans-coding said emergency call from said first communication format to a second communication format.

28. A computer-implemented method for processing emergency calls, said method comprising receiving a first emergency call from a first calling device, receiving a second emergency call from a second calling device, receiving first information, receiving second information, based at least in part on said first information, routing said first emergency call to a first destination, based at least in part on said second information, routing said second emergency call to a second destination, wherein said first emergency call is a call that is in a first communication format, wherein said second emergency call is a call that is in a second communication format, wherein said first communication format is a format that is different from said second communication format, wherein said first information is indicative of a first location, wherein said first location is associated with said first calling device, wherein said second information is indicative of a second location, wherein said second information is indicative of a location of said second calling device, wherein said first destination has a first attribute, wherein said second destination has a second attribute, wherein said first destination has a third attribute, wherein said first attribute is the attribute of having an ability to receive an emergency call that is in said first communication format, wherein said second attribute is the attribute of having an ability to receive an emergency call that is in said second communication format, which is a format that is not the same as said first communication format, and wherein said third attribute is the attribute of lacking an ability to receive an emergency call in said second communication format, which is a format that is not the same as 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 Oct 2, 2012
From: PIETT, WILLIAM T.; SERRA, MATTHEW A.; MARCEAU, BRETT WILFRED
To: RAVE WIRELESS, INC.
Reel/Frame 029059/0132 →
Continuity (2)
Provisional Application 61538505 · Sep 23, 2011
Related Publication 20130077536A1 · Mar 28, 2013