# US 2020/0288295 A1 · Apparatus and method for emergency dispatch

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0288295 A1
- Document ID: US20200288295A1
- Status: Published application
- Kind: A1
- Application number: 16/812,995
- Filed: 2020-03-09
- Published: 2020-09-10
- Earliest claimed: 2019-03-08
- Assignees: Rapidsos, Inc.
- Applicants: RapidSOS, Inc.
- Inventors: Michael John Martin; Nicholas Edward Horelik; Riccardo Pellegrini
- Web page: https://patentgrep.com/patent/US20200288295A1

## CPC

- H04M 3/5116: {for emergency applications}
- G06N 5/025: Extracting rules from data
- G06N 20/00: Machine learning
- H04W 4/022: {with dynamic range variability}
- H04W 4/029: Location-based management or tracking services
- H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
- H04W 76/50: for emergency connections
- H04M 2207/18: wireless networks
- H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
- H04W 4/024: Guidance services
- H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
- H04W 4/38: for collecting sensor information
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A disclosed method includes receiving data inputs for a plurality of events including alarms, sensors, and mobile device emergency call and emergency alert related emergency data; determining event correlations based on the data inputs to generate a set of correlated events; determining emergency network dispatch rules for each correlated event based on event type; applying corresponding emergency network dispatch rules to each corresponding correlated event; and sending a dispatch recommendation to an emergency network entity for each correlated event based on application of the corresponding emergency network dispatch rules.

## Claims

### Claim 1

A method comprising:
receiving data inputs for a plurality of events comprising alarms, sensors, and mobile device emergency call and emergency alert related emergency data;
determining event correlations based on the data inputs to generate a set of correlated events;
determining emergency network dispatch rules for each correlated event based on event type;
applying corresponding emergency network dispatch rules to each corresponding correlated event; and
sending a dispatch recommendation to an emergency network entity for each correlated event based on application of the corresponding emergency network dispatch rules.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
dispatching emergency responders automatically by sending the dispatch recommendation to emergency responders corresponding to the event type for each correlated event.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
determining the emergency network entity for each correlated event based on associations between the data inputs corresponding to each correlated event and each emergency network entity's geographic boundary.

### Claim 4 (depends on 1)

The method of claim 1, wherein determining event correlations based on the data inputs to generate a set of correlated events, comprises:
determining event correlations via a logic component trained using machine learning.

### Claim 5 (depends on 1)

The method of claim 1, wherein applying corresponding emergency network dispatch rules to each corresponding correlated event, comprises:
determining answers to a series of questions corresponding to the event type via a logic component trained using machine learning.

### Claim 6 (depends on 3)

The method of claim 3, further comprising:
establishing a plurality of network connections with a plurality of emergency network entities; and
sending dispatch recommendations to each emergency network entity based on the associations between the data inputs corresponding to each correlated event and with each emergency network entity's geographic boundary.

### Claim 7 (depends on 1)

The method of claim 1, wherein determining emergency network dispatch rules for each correlated event based on event type, comprises:
determining an event type for each correlated event as an event type selected from the group of: a fire emergency event, a police emergency event and a medical emergency event.

### Claim 8 (depends on 1)

The method of claim 1, wherein determining emergency network dispatch rules for each correlated event based on event type, comprises:
determining that a correlated event includes a combination of at least two event types selected from the group of: a fire emergency event, a police emergency event and a medical emergency event.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
sending a first dispatch recommendation related to a first event type to an emergency network entity for a correlated event; and
sending a second dispatch recommendation related to a second event type for the correlated event.

### Claim 10 (depends on 8)

The method of claim 8, wherein sending a second dispatch recommendation related to a second event type for the correlated event, comprises:
sending the second dispatch recommendation related to the second event type to a second emergency network entity.

### Claim 11

An apparatus comprising:
a network component, operative to connect to the Internet;
event correlation logic, operatively coupled to the network component, the event correlation logic operative to:
receive data inputs for a plurality of events comprising alarms, sensors, and mobile device emergency call and emergency alert related emergency data;
determine event correlations based on the data inputs to generate a set of correlated events;
determine emergency network dispatch rules for each correlated event based on event type;
apply corresponding emergency network dispatch rules to each corresponding correlated event; and
send a dispatch recommendation to an emergency network entity for each correlated event based on application of the corresponding emergency network dispatch rules.

### Claim 12 (depends on 11)

The apparatus of claim 11, wherein the event correlation logic is further operative to:
dispatch emergency responders automatically by sending the dispatch recommendation to emergency responders corresponding to the emergency type for each correlated event.

### Claim 13 (depends on 11)

The apparatus of claim 11, further comprising:
a geofence module, operatively coupled to the event correlation logic, the geofence module operative to:
determine the emergency network entity for each correlated event based on associations between the data inputs corresponding to each correlated event and each emergency network entity's geographic boundary.

### Claim 14 (depends on 11)

The apparatus of claim 11, wherein the event correlation logic is trained to determine event correlations using machine learning.

### Claim 15 (depends on 11)

The apparatus of claim 11, wherein the event correlation logic is trained to apply corresponding emergency network dispatch rules to each corresponding correlated event, by determining answers to a series of questions corresponding to the event type using machine learning.

### Claim 16 (depends on 13)

The apparatus of claim 13, wherein the event correlation logic is further operative to:
establish a plurality of network connections with a plurality of emergency network entities; and
send dispatch recommendations to each emergency network entity based on the associations between the data inputs corresponding to each correlated event and with each emergency network entity's geographic boundary.

### Claim 17 (depends on 11)

The apparatus of claim 11, wherein the event correlation logic is operative to determine emergency network dispatch rules for each correlated event based on event type, by determining an event type for each correlated event as an event type selected from the group of: a fire emergency event, a police emergency event and a medical emergency event.

### Claim 18 (depends on 11)

The apparatus of claim 11, wherein the event correlation logic is operative to determine emergency network dispatch rules for each correlated event based on event type, by determining that a correlated event includes a combination of at least two event types selected from the group of: a fire emergency event, a police emergency event and a medical emergency event.

### Claim 19 (depends on 18)

The apparatus of claim 18, wherein the event correlation logic is further operative to:
send a first dispatch recommendation related to a first event type to an emergency network entity for a correlated event; and
send a second dispatch recommendation related to a second event type for the correlated event.

### Claim 20 (depends on 18)

The apparatus of claim 18, wherein the event correlation logic is operative to send a second dispatch recommendation related to a second event type for the correlated event, by sending the second dispatch recommendation related to the second event type to a second emergency network entity.