IP Library Granted Patent US 10,582,053
Granted Patent B2
US 10,582,053 · App. 16/289,432 · Granted Mar 3, 2020

Emergency data gateway device

Inventor: Justin Jensen (Seguin, TX)
Assignee: RapidDeploy, 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,582,053
App. No.
16/289,432
Granted
Mar 3, 2020
Kind
B2
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 (72)

1. A gateway device comprising:

a call handling equipment (CHE) listener interface configured to receive call event data from a CHE;

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

a message parsing engine configured to:

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

format the call event data according to a data format recognized by the cloud-based processing system;

wherein the gateway device is configured to transmit the formatted call event data to the cloud-based processing system via a secure network.

2. The gateway device of claim 1 , wherein the message parsing engine parses the call event data received from the CHE according to instructions for parsing data from a data output format of the CHE.

3. The gateway device of claim 1 , wherein the message parsing engine parses the call event data in response to receiving parsing instructions via the IP interface.

4. The gateway device of claim 1 , wherein:

the call event data received from the CHE comprises a plurality of data messages;

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; and

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.

5. 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.

6. 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.

7. The gateway device of claim 1 , further comprising a first physical port for connecting to the CHE and 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.

8. 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 from a data output format of the CHE;

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

transmitting the formatted call event data to the cloud-based processing system via a secure network.

9. The method of claim 8 , 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, parsing instructions from the cloud-based processing system, the parsing instructions for parsing the received call event data, and 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.

10. The method of claim 9 , 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.

11. The method of claim 9 , further comprising:

providing, by the gateway device, a user interface for receiving the configuration data; and

receiving, at the gateway device, the configuration data in the user interface from a user.

12. The method of claim 8 , 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.

13. The method of claim 8 , further comprising:

calculating metrics describing operations of the gateway device; and

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

14. The method of claim 8 , 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.

15. A non-transitory computer-readable storage medium storing computer program instructions executable by a processor to perform operations for processing emergency call data, the operations 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 from a data output format of the CHE;

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

transmitting the formatted call event data to the cloud-based processing system via a secure network.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the operations for processing emergency call data comprise:

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, parsing instructions from the cloud-based processing system, the parsing instructions for parsing the received call event data, and 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.

17. The non-transitory computer-readable storage medium of claim 16 , 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.

18. The non-transitory computer-readable storage medium of claim 16 , the operations further comprising:

providing, by the gateway device, a user interface for receiving the configuration data, and

receiving, at the gateway device, the configuration data in the user interface from a user.

19. The non-transitory computer-readable storage medium of claim 15 , wherein the call event data received from the CHE comprises a plurality of data messages, the operations 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.

20. The non-transitory computer-readable storage medium of claim 15 , the operations further comprising:

calculating metrics describing operations of the gateway device; and

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

21. The non-transitory computer-readable storage medium of claim 15 , the operations 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.

Assignments (8)
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 →
RELEASE OF SECURITY INTEREST Recorded Jan 23, 2023
From: SILICON VALLEY BANK
To: RAPIDDEPLOY, INC.
Reel/Frame 062456/0948 →
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
Reel/Frame 059466/0309 →
SECURITY INTEREST Recorded Mar 31, 2022
From: RAPIDDEPLOY, INC.
To: SILICON VALLEY BANK, AS AGENT
Reel/Frame 059466/0350 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 28, 2019
From: JENSEN, JUSTIN
To: RAPIDDEPLOY USA CORP.
Reel/Frame 048472/0678 →
CHANGE OF NAME Recorded Feb 28, 2019
From: RAPIDDEPLOY USA CORP.
To: RAPIDDEPLOY, INC.
Reel/Frame 048477/0829 →
Continuity (3)
Continuation 16179795 · Nov 2, 2018
Provisional Application 62678845 · May 31, 2018
Related Publication 20190373112A1 · Dec 5, 2019
Cited By (3)
US 12,219,653 US 12,323,273 US 12,604,368