# US 11,909,916 B2 · Platform for emergency event subscriptions > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,909,916 B2 - Document ID: US11909916B2 - Status: Granted - Kind: B2 - Application number: 18/118,600 - Filed: 2023-03-07 - Published: 2023-12-21 - Granted: 2024-02-20 - Earliest claimed: 2020-01-16 - Assignees: RapidDeploy, Inc. - Applicants: RapidDeploy, Inc. - Inventors: Ivor Chalton; Lidia Finn; James P. Algatt; Ryan Matthew Fouts; Noam Fein - Web page: https://patentgrep.com/patent/US11909916B2 ## CPC - H04M 3/5116: {for emergency applications} - G06Q 10/107: Computer-aided management of electronic mailing [e-mailing] - G06Q 50/265: {Personal security, identity or safety} - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract A data subscription system provides emergency event data to receiving systems. The data subscription system includes an event emitter and a distribution module. The event emitter receives event data describing an event in a computer-aided dispatch (CAD) system; the event is related to an emergency call. The event emitter identifies a subscription subscribed to the event based on a tenant identifier identifying a CAD tenant associated with the event, and adds a data message with the event data to a queue for the identified subscription. The distribution module retrieves the data message from the queue, transforms the data message based on one or more filtering or formatting rules, and transmits the transformed data message to a receiving system associated with the subscription. ## Claims ### Claim 1 A non-transitory computer-readable medium having instructions for execution by one or more processors for: receiving, from a computer-aided dispatch (CAD) service, domain event data describing a domain event related to an emergency call, the domain event data comprising an event type and a tenant identifier, the tenant identifier identifying a tenant associated with the domain event; identifying a subscription queue subscribed to the domain event data based on the event type and the tenant identifier, the subscription queue associated with a receiving system; adding a data message comprising at least a subset of the domain event data to the subscription queue; transforming the data message based on a formatting rule to format the data message in a particular format associated with the receiving system; and transmitting the transformed data message to the receiving system, the receiving system comprising a database of domain event data related to emergency calls. ### Claim 2 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the instructions are further executable for: receiving an input from a user of the CAD service and generating the domain event in response to the input. ### Claim 3 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the domain event data is received at a call data ingestion module, the call data ingestion module being configured to receive call data related to calls received at a public safety answering point (PSAP). ### Claim 4 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the instructions are further executable for: storing subscription data relating each of a plurality of receiving systems to at least one tenant and at least one event type; and identifying the subscription queue associated with the receiving system based on the stored subscription data. ### Claim 5 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the event type of the domain event is one of a plurality of event types, a first event type of the plurality of event types associated with a first set of domain event data, and a second event type of the plurality of event types associated with a second set of domain event data. ### Claim 6 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the data message comprises a plurality of data fields, and wherein the instructions are further executable for: filtering a portion of the data fields of the data message according to a filtering rule. ### Claim 7 (depends on 6) The non-transitory computer-readable medium of claim 6, wherein the filtering rule is an event-specific filtering rule for filtering the portion of the data fields based on the event type. ### Claim 8 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the receiving system is a records management system for storing data from emergency calls. ### Claim 9 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the receiving system is an emergency monitoring system that provides one or more user interfaces describing emergencies in a region. ### Claim 10 (depends on 1) The non-transitory computer-readable medium of claim 1, wherein the receiving system is a station alerting system. ### Claim 11 A system comprising: one or more processors configured to execute instructions; one or more non-transitory media storing instructions executable by the one or more processors for: storing subscription data describing domain event data provided to each of a plurality of receiving systems; receive, from a computer-aided dispatch (CAD) service, domain event data describing a domain event related to an emergency call, the domain event data comprising an event type and a tenant identifier, the tenant identifier identifying a tenant associated with the domain event; compare the event type and the tenant identifier to the subscription data to identify a subscription subscribed to the domain event data, the subscription associated with a receiving system; transform the domain event data based on a formatting rule to format the domain event data in a particular format associated with the receiving system; and transmit the transformed domain event data to the receiving system, the receiving system comprising a database of domain event data related to emergency calls. ### Claim 12 (depends on 11) The system of claim 11, wherein the CAD service generates domain events in response to user input provided by a user of the CAD service. ### Claim 13 (depends on 11) The system of claim 11, wherein the domain event data comprises data received from a call data ingestion module, the call data ingestion module configured to receive call data related to calls received at a public safety answering point (PSAP). ### Claim 14 (depends on 11) The system of claim 11, wherein the subscription data relates each of the plurality of receiving systems to at least one tenant and at least one event type. ### Claim 15 (depends on 11) The system of claim 11, wherein the event type of the domain event is one of a plurality of event types, a first event type of the plurality of event types associated with a first set of domain event data, and a second event type of the plurality of event types associated with a second set of domain event data. ### Claim 16 (depends on 11) The system of claim 11, wherein the domain event data comprises a plurality of data fields, the instructions are further executable for filtering a portion of the data fields of the domain event data. ### Claim 17 (depends on 16) The system of claim 16, wherein the filtering implements at least one event-specific filtering rule for filtering the portion of the data fields based on the event type. ### Claim 18 (depends on 11) The system of claim 11, wherein the receiving system is a records management system for storing data from emergency calls. ### Claim 19 (depends on 11) The system of claim 11, wherein the receiving system is an emergency monitoring system that provides one or more user interfaces describing emergencies in a region. ### Claim 20 (depends on 11) The system of claim 11, wherein the receiving system is a station alerting system.