IP Library Granted Patent US 10,264,122
Granted Patent B1
US 10,264,122 · App. 16/179,795 · Granted Apr 16, 2019

Emergency data gateway device

Inventor: Justin Jensen (Seguin, TX)
Assignee: RapdiDeploy, Inc.
H04M3/5116H04L12/66H04L65/102H04W76/50H04M2242/04H04W4/90
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 10,264,122
App. No.
16/179,795
Granted
Apr 16, 2019
Kind
B1
Abstract

A gateway device includes a call handling equipment (CHE) listener interface, an Internet Protocol (IP) interface, a provisioning engine, and a message parsing engine. The CPE listener interface forms a communication channel with a CHE and receives call event data from the CHE. The IP interface communicates with a cloud-based processing system. The provisioning engine receives, from the cloud-based processing system via the IP interface, instructions for parsing data from a data output format of the CHE into a consistent data format of the cloud-based processing system. The message parsing engine parses the call event data received from the CHE via the CHE listener interface, and formats the call event data according to the consistent data format. The gateway device transmits the formatted call event data to the cloud-based processing system via the IP interface.

Claims (59)

1. A gateway device comprising:

a call handling equipment (CHE) listener interface configured to form a communication channel with a CHE and receive call event data from the CHE;

an Internet Protocol (IP) interface configured to communicate with a cloud-based processing system;

a provisioning engine configured to receive, from the cloud-based processing system via the IP interface, instructions for parsing data from a data output format of the CHE; and

a message parsing engine configured to:

parse the call event data received from the CHE via the CHE listener interface according to the instructions, and

format the call event data according to a consistent data format;

wherein the gateway device is configured to transmit the formatted call event data to the cloud-based processing system via the IP interface.

2. The gateway device of claim 1 , wherein the call event data received from the CHE comprises a plurality of data messages, and the CHE listener interface is further configured to:

generate a message identifier for each of the plurality of data messages; and

store each data message of the plurality of data messages with its corresponding message identifier in a message queue.

3. The gateway device of claim 2 , wherein the message parsing engine is further configured to retrieve each data message of the plurality of data messages from the message queue, in an order indicated by the message queue.

4. The gateway device of claim 1 , wherein the provisioning engine is further configured to provide a provisioning user interface to a connected device, the provisioning user interface configured to assist a user in configuring the gateway device based on properties of the CHE to which the gateway device is connected.

5. The gateway device of claim 1 , wherein the provisioning engine is further configured to:

receive configuration data from the CHE, the configuration data indicating the data output format of the CHE; and

transmit the configuration data to the cloud-based processing system via the IP interface,

wherein the cloud-based processing system selects the instructions from a database of configuration instructions based on the configuration data.

6. The gateway device of claim 1 , further comprising a status engine configured to:

calculate metrics describing operations of the gateway device; and

transmit the calculated metrics to the cloud-based processing system via the IP interface.

7. The gateway device of claim 1 , further comprising a status engine configured to:

monitor connectivity of the CHE to the gateway device;

monitor functionality of the CHE based on the call event data received from the CHE;

detect an error on the CHE based on at least one of the monitored connectivity or the monitored functionality; and

transmit an alert to the cloud-based processing system indicating the error on the CHE.

8. The gateway device of claim 1 , further comprising a physical port for connecting to the CHE, wherein the communications channel is formed via the physical port.

9. The gateway device of claim 8 , further comprising a second physical port for connecting to a second CHE, wherein the CHE listener interface is configured to receive call event data from the CHE and the second CHE simultaneously.

10. A method for processing emergency call data comprising:

receiving, at a gateway device, call event data from call handling equipment (CHE) in communication with the gateway device;

parsing, at the gateway device, the received call event data based on parsing instructions for parsing data from a data output format of the CHE;

formatting the parsed call event data according to a consistent data format used by a cloud-based processing system according to formatting instructions; and

transmitting the formatted call event data to the cloud-based processing system via an IP interface.

11. The method of claim 10 , further comprising:

transmitting, by the gateway device, configuration data to the cloud-based processing system, the configuration data describing the CHE connected to the gateway device; and

receiving, at the gateway device, the parsing instructions from the cloud-based processing system, wherein the cloud-based processing system selects the parsing instructions from a plurality of available parsing instructions based on the configuration data describing the CHE.

12. The method of claim 11 , wherein the configuration data comprises at least one sample data message received by the gateway device from the CHE, and the cloud-based processing system determines the data output format of the CHE based on the at least one sample data message.

13. The method of claim 11 , wherein the gateway device provides a user interface for receiving the configuration data, and the configuration data is input by a user to the gateway device in the user interface.

14. The method of claim 10 , wherein the call event data received from the CHE comprises a plurality of data messages, the method further comprising:

generating a message identifier for each of the plurality of data messages;

storing each data message of the plurality of data messages with its corresponding message identifier in a message queue; and

retrieving each data message of the plurality of data messages from the message queue, in an order indicated by the message queue.

15. The method of claim 10 , further comprising:

calculating metrics describing operations of the gateway device; and

transmitting the calculated metrics to the cloud-based processing system.

16. The method of claim 10 , further comprising:

monitoring connectivity of the CHE to the gateway device;

monitoring functionality of the CHE based on the call event data received from the CHE;

detecting an error on the CHE based on at least one of the monitored connectivity or the monitored functionality; and

transmitting an alert to the cloud-based processing system indicating the error on the CHE.

17. A method for provisioning a gateway device comprising:

receiving, from the gateway device over an Internet connection, data describing a local environment of the gateway device, the environment including call handling equipment (CHE) configured to provide emergency call data;

determining an output data format of a plurality of data formats for the CHE based on the data describing the local environment;

retrieving instructions for parsing data from the output data format and formatting the parsed data in a consistent format; and

transmitting the instructions to the gateway device over the Internet connection.

18. The method of claim 17 , further comprising:

receiving, over the Internet connection, real-time call event data in the consistent format from the gateway device, the real-time call event data generated by the gateway device based on data received at the gateway device from the CHE; and

transmitting an update based on the real-time call event data to a dispatcher system.

19. The method of claim 17 , wherein the instructions for parsing data from the output data format and formatting the parsed data in the consistent format are used by at least one additional gateway device.

20. The method of claim 17 , wherein the data describing the local environment of the gateway device comprises at least one of configuration information of a CHE, a sample data message of the CHE, or data identifying one of the CHE or the gateway device.

Assignments (10)
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 →
CHANGE OF NAME Recorded Feb 22, 2019
From: RAPIDDEPLOY USA CORP.
To: RAPIDDEPLOY, INC.
Reel/Frame 048413/0159 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 17, 2018
From: JENSEN, JUSTIN
To: RAPIDDEPLOY USA CORP.
Reel/Frame 047800/0347 →
Continuity (1)
Provisional Application 62678845 · May 31, 2018
Cited By (3)
US 12,219,653 US 12,323,273 US 12,604,368