IP Library Granted Patent US 11,405,768
Granted Patent B2
US 11,405,768 · App. 17/070,400 · Granted Aug 2, 2022

Data relay for multi-tenant emergency call system

Inventors: Justin Jensen (Seguin, TX); Michael Edwin Kyle (Austin, TX)
Assignee: RapidDeploy, Inc.
H04W4/90H04L12/66H04L61/103H04L69/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 11,405,768
App. No.
17/070,400
Granted
Aug 2, 2022
Kind
B2
Abstract

An emergency call data relay includes a frame buffer and a frame handler. The frame buffer stores data frames received from a central system (e.g., a central CPE host). The data frames include call data associated with an emergency call being handled at a remote system (e.g., a PSAP) connected to the central system. The frame handler receives a data frame from the frame buffer, identifies a remote system handling the emergency call associated with the call data based on a network address in the data frame, extracts the call data from the data frame, and generates an output packet for a data gateway. The output packet has a header indicating a particular data gateway profile associated with the identified remote system handling the emergency call.

Claims (45)

1. A system for processing emergency call data comprising:

a frame buffer configured to store data frames received from a central emergency call system, each data frame comprising call data associated with an emergency call being handled at one of a plurality of remote emergency call handling systems connected to the central emergency call system;

a frame handler configured to:

receive a data frame from the frame buffer;

identify the remote emergency call handling system handling the emergency call associated with the call data based on a network address in the data frame;

extract the call data from the data frame; and

generate an output packet comprising a packet body, the packet body comprising the call data, and a packet header, the packet header indicating a data gateway profile associated with the identified remote emergency call handling system; and

an output configured to provide the output packet to a data gateway, the data gateway comprising a plurality of data gateway profiles corresponding to the plurality of remote emergency call handling systems.

2. The system of claim 1 , wherein the frame handler is further configured to:

determine a type of data provided in each data frame received from the central emergency call system; and

discard a portion of the stored data frames based on the determined type of data.

3. The system of claim 1 , further comprising:

an Ethernet port configured to receive the data frames from the central emergency call system via an Ethernet switch and pass the received data frames to the frame buffer.

4. The system of claim 3 , wherein the Ethernet switch is configured to output the data frames to the Ethernet port via a mirror port, the mirror port configured to mirror data frames transmitted from the central emergency call system to the plurality of remote emergency call handling systems.

5. The system of claim 3 , wherein the frame buffer, frame handler, and Ethernet port are implemented on an Ethernet network interface controller (NIC) of a gateway device, the gateway device configured to implement the data gateway comprising the plurality of data gateway profiles.

6. The system of claim 1 , wherein the output is a device output port configured to connect to an input port of at least one data gateway device configured to implement at least a portion of the plurality of data gateway profiles.

7. The system of claim 1 , wherein the network address in the data frame comprises an Internet Protocol (IP) address of the remote emergency call handling system.

8. The system of claim 1 , wherein the packet header indicating the data gateway profile comprises an IP address of the data gateway profile.

9. The system of claim 1 , wherein the frame buffer is further configured to store data frames comprising network event data describing the central emergency call system, and the frame handler is further configured to generate an output packet comprising the network event data.

10. A system for processing emergency call data comprising:

a frame buffer configured to store data frames received from a central emergency call system, each data frame comprising call data associated with an emergency call being handled at one of a plurality of remote emergency call handling systems;

a frame handler configured to:

receive a data frame from the frame buffer;

identify the remote emergency call handling system handing the emergency call associated with the call data based on a network address in the data frame; and

generate an output packet comprising the call data, the output packet having a packet header selected based on the identified remote emergency call handling system; and

a data gateway comprising a plurality of data gateway profiles, each data gateway profile associated with one of the plurality of remote emergency call handling systems, and each data gateway profile configured to:

receive, from the frame handler, call data associated with the data gateway profile; and

transmit at least a portion of the call data to a cloud-based processing system.

11. The system of claim 10 , wherein each data gateway profile is further configured to parse the call data, extract a plurality of data fields from the call data, and generate a formatted data message for transmission to the cloud-based processing system.

12. The system of claim 10 , wherein the frame handler is further configured to determine a type of data provided in each data frame received from the central emergency call system, wherein the frame handler is configured to discard a portion of the stored data frames based on the determined type of data.

13. The system of claim 10 , further comprising an Ethernet port configured to receive the data frames from the central emergency call system via an Ethernet switch.

14. The system of claim 10 , wherein the frame buffer and frame handler are implemented on an Ethernet network interface controller (NIC) of a gateway device, the gateway device configured to implement the data gateway comprising the plurality of data gateway profiles.

15. The system of claim 10 , wherein the frame buffer is further configured to store data frames comprising network event data describing the central emergency call system, and the frame handler is further configured to generate an output packet comprising the network event data.

16. The system of claim 13 , wherein the Ethernet switch is configured to output the data frames to the Ethernet port via a mirror port, and the mirror port configured to mirror at least a portion of data frames passing through the Ethernet switch.

17. The system of claim 10 , wherein the network address in the data frame comprises an Internet Protocol (IP) address of the remote emergency call handling system.

18. The system of claim 1 , wherein the system further comprises a packet filter configured to:

determine a type of data provided in each of a plurality of data frames received from the central emergency call system; and

discard a portion of the plurality of data frames based on the determined type of data.

19. The system of claim 10 , wherein the system further comprises a packet filter configured to:

determine a type of data provided in each of a plurality of data frames received from the central emergency call system; and

discard a portion of the plurality of data frames based on the determined type of data.

20. The system of claim 1 , wherein one of the plurality of data gateway profiles is configured to:

receive the output packet;

extract a plurality of data fields from the call data of the output packet; and

generate a formatted data message for transmission to a cloud-based processing system.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Mar 6, 2025
From: AVENUE CAPITAL MANAGEMENT II, L.P.
To: RAPIDDEPLOY, INC.
Reel/Frame 070424/0773 →
SECURITY INTEREST Recorded Mar 29, 2024
From: RAPIDDEPLOY, INC.
To: AVENUE CAPITAL MANAGEMENT II, L.P.
Reel/Frame 066944/0803 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY AT REEL/FRAME NO. 62456/0227 Recorded Mar 28, 2024
From: TEXAS CAPITAL BANK
To: RAPIDDEPLOY, INC.; EMERGENT COMMUNICATIONS INC.
Reel/Frame 066948/0427 →
RELEASE OF SECURITY INTEREST Recorded Jan 23, 2023
From: SILICON VALLEY BANK
To: RAPIDDEPLOY, INC.
Reel/Frame 062456/0948 →
SECURITY INTEREST Recorded Jan 23, 2023
From: RAPIDDEPLOY, INC.; EMERGENT COMMUNICATIONS INC.
To: TEXAS CAPITAL BANK
Reel/Frame 062456/0227 →
RELEASE OF SECURITY INTEREST Recorded Jan 23, 2023
From: SILICON VALLEY BANK, AS AGENT
To: RAPIDDEPLOY, INC.
Reel/Frame 062457/0390 →
SECURITY INTEREST Recorded Mar 31, 2022
From: RAPIDDEPLOY, INC.
To: SILICON VALLEY BANK, AS AGENT
Reel/Frame 059466/0350 →
SECURITY INTEREST Recorded Mar 31, 2022
From: RAPIDDEPLOY, INC.
To: SILICON VALLEY BANK
Reel/Frame 059466/0309 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 14, 2020
From: JENSEN, JUSTIN; KYLE, MICHAEL EDWIN
To: RAPIDDEPLOY, INC.
Reel/Frame 054053/0389 →
Continuity (2)
Provisional Application 62916012 · Oct 16, 2019
Related Publication 20210120393A1 · Apr 22, 2021