IP Library › Granted Patent US 12,477,065
Granted Patent B2
US 12,477,065 · App. 18/234,287 · Granted Nov 18, 2025

Emergency communication system with contextual snippets

Inventors: Anshuman Srivastava (Seattle, WA); Michael Bauer (Seattle, WA); Joseph Pepper (Seattle, WA)
Assignee: Axon Enterprise, Inc.
H04M3/5116H04M3/42221H04M2203/553
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 12,477,065
App. No.
18/234,287
Granted
Nov 18, 2025
Kind
B2
Abstract

Systems and methods for processing emergency communications are provided. A system may receive an emergency communication initiated by an emergency communicator. The system may detect a data field action in response to an emergency receiver entering a data input based on the emergency communication. The system may capture a timestamp of when the data field action occurred. The system may generate a communication snippet based on the action timestamp and a snippet length. The communication snippet may be configured to provide context from the emergency communication to the data input. The system may transmit the communication snippet and the data input to an emergency responder.

Claims (30)

1 . A method comprising:

receiving, by an emergency responder device, a plurality of data inputs related to an emergency communication, wherein each data input of the plurality of data inputs is related to a portion of a plurality of portions of the emergency communication;

receiving, by the emergency responder device, a communication snippet associated with a data input from the plurality of data inputs, wherein the communication snippet comprises the portion of the plurality of portions of the emergency communication related to the data input of the plurality of data inputs, wherein the communication snippet is configured to provide context to the data input from the plurality of data inputs, and wherein the communication snippet comprises audio data;

displaying, by the emergency responder device, the data input from the plurality of data inputs as a visual output; and

outputting, by the emergency responder device, the communication snippet as an audible output.

2 . The method of claim 1 , further comprising generating, by the emergency responder device, a communication snippet revision request associated with the communication snippet.

3 . The method of claim 2 , wherein the communication snippet revision request comprises at least one of a post-snippet revision value or a pre-snippet revision value.

4 . The method of claim 2 , further comprising receiving, by the emergency responder device, a revised communication snippet based on the communication snippet revision request, wherein the revised communication snippet is associated with the data input.

5 . The method of claim 2 , further comprising receiving, by the emergency responder device, a voice command, wherein at least one of the displaying the data input, the outputting the communication snippet, or the generating the communication snippet revision request is responsive to the voice command.

6 . The method of claim 1 , further comprising receiving, by the emergency responder device, a voice command, wherein at least one of the displaying the data input or the outputting the communication snippet is responsive to the voice command.

7 . The method of claim 1 , further comprising outputting, by the emergency responder device, the data input from the plurality of data inputs as a second audible output, wherein the second audible output is separate from the audible output.

8 . The method of claim 1 , wherein the receiving the plurality of data inputs and the receiving the communication snippet is during a dispatch process to dispatch an emergency responder associated with the emergency responder device based on the emergency communication.

9 . The method of claim 1 , wherein the receiving the communication snippet comprises receiving a first portion of the communication snippet and receiving separately a second portion of the communication snippet, and wherein the first portion is received prior to the second portion.

10 . The method of claim 9 , wherein the first portion of the communication snippet is received during generation of the communication snippet, and wherein the second portion of the communication snippet is received after generation of the communication snippet.

11 . A mobile data terminal (MDT) for an emergency responder comprising:

a processor; and

a tangible, non-transitory memory configured to communicate with the processor, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising:

receiving, by the processor, a plurality of data inputs related to an emergency communication, wherein each data input of the plurality of data inputs is related to a portion of a plurality of portions of the emergency communication;

receiving, by the processor, a communication snippet associated with a data input from the plurality of data inputs, wherein the communication snippet comprises the portion of the plurality of portions of the emergency communication related to the data input of the plurality of data inputs, wherein the communication snippet is configured to provide context to the data input from the plurality of data inputs, and wherein the communication snippet comprises audio data;

displaying, by the processor, the data input from the plurality of data inputs as a visual output; and

outputting, by the processor, the communication snippet as an audible output.

12 . The MDT of claim 11 , further comprising generating, by the processor, a communication snippet revision request associated with the communication snippet.

13 . The MDT of claim 12 , wherein the communication snippet revision request comprises at least one of a post-snippet revision value or a pre-snippet revision value.

14 . The MDT of claim 12 , further comprising receiving, by the processor, a revised communication snippet based on the communication snippet revision request, wherein the revised communication snippet is associated with the data input.

15 . The MDT of claim 12 , further comprising receiving, by the processor, a voice command, wherein at least one of the displaying the data input, the outputting the communication snippet, or the generating the communication snippet revision request is responsive to the voice command.

16 . The MDT of claim 11 , further comprising receiving, by the processor, a voice command, wherein at least one of the displaying the data input or the outputting the communication snippet is responsive to the voice command.

17 . The MDT of claim 11 , further comprising outputting, by the processor, the data input from the plurality of data inputs as a second audible output.

18 . The MDT of claim 11 , wherein the receiving the plurality of data inputs and the receiving the communication snippet is during a dispatch process to dispatch an emergency responder based on the emergency communication.

19 . The MDT of claim 11 , wherein the receiving the communication snippet comprises receiving a first portion of the communication snippet and receiving separately a second portion of the communication snippet, and wherein the first portion is received prior to the second portion.

20 . The MDT of claim 19 , wherein the first portion of the communication snippet is received during generation of the communication snippet, and wherein the second portion of the communication snippet is received after generation of the communication snippet.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 21, 2023
From: SRIVASTAVA, ANSHUMAN; BAUER, MICHAEL; PEPPER, JOSEPH
To: AXON ENTERPRISE, INC.
Reel/Frame 064653/0022 →
Continuity (3)
Continuation 17432056
Provisional Application 62952811 · Dec 23, 2019
Related Publication 20230388416A1 · Nov 30, 2023
References Cited (15)
US 6252946B1 · Glowny et al. · 2001 [cited by applicant]
US 7336172B2 · Govindaraj · 2008 [cited by examiner]
US 8538374B1 · Haimo et al. · 2013 [cited by applicant]
US 9547977B2 · Will et al. · 2017 [cited by applicant]
US 9715901B1 · Singh et al. · 2017 [cited by applicant]
US 20130222133A1 · Schultz et al. · 2013 [cited by applicant]
US 20180053401A1 · Martin et al. · 2018 [cited by applicant]
US 20180248929A1 · Han · 2018 [cited by examiner]
US 20190166480A1 · Rauner · 2019 [cited by applicant]
EP 3213494A1 · 2017 [cited by applicant]
Canadian Intellectual Property Office, Office Action for Canadian Application No. 3,162,531 mailed Aug. 25, 2023. [cited by applicant]
International Searching Authority, International Search Report and Written Opinion for International Patent Application PCT/IB2020/062355, p. 1-9. [cited by applicant]
European Patent Office, Extended European Search Report for European Application No. 20908082.9 mailed Dec. 12, 2023. [cited by applicant]
Canadian Patent Office, Office Action for Canadian Application No. 3,162,531 mailed Apr. 16, 2024. [cited by applicant]
Canadian Intellectual Property Office, Office Action for Canadian Application No. 3,162,531, mailed Apr. 29, 2025. [cited by applicant]