IP Library Granted Patent US 12,272,228
Granted Patent B2
US 12,272,228 · App. 17/183,317 · Granted Apr 8, 2025

Identifying emergency response validity and severity

Inventor: Nora Ligrani (Denver, CO)
Assignee: Intrado Life & Safety, Inc.
G08B25/007G06Q50/01G08B25/10H04W4/023H04W4/025H04W4/029H04W4/38H04W4/90H04W76/50
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,272,228
App. No.
17/183,317
Granted
Apr 8, 2025
Kind
B2
Abstract

One example method of operation may include identifying a plurality of emergency reporting entities located at an emergency location based on one or more received emergency communications, determining whether one or more of the emergency reporting entities have provided valid emergency response data, determining a level of severity of the emergency response data, and transmitting one or more notifications to one or more emergency response entities based on the level of severity and a type of emergency.

Claims (55)

1. A method, comprising:

receiving emergency response data from a plurality of emergency reporting entities at a location of an emergency;

determining whether the emergency response data provided by one or more of the emergency reporting entities is valid by determining whether at least one emergency reporting entity of the emergency reporting entities is a fixed sensor and whether at least one additional emergency reporting entity of the emergency reporting entities is a mobile device;

determining a level of severity of the emergency response data;

transmitting one or more notifications to one or more emergency response entities based on the level of severity and a type of emergency;

initiating an emergency response time window based on the type of emergency and the level of severity; and

performing a dispatch operation corresponding to the emergency response time window by notifying one or more non-emergency response entities of the emergency.

2. The method of claim 1 , further comprising:

forwarding a request for additional data to one or more additional emergency reporting entities different from the plurality of emergency reporting entities; and

determining the type of emergency via response data received from the one or more additional emergency reporting entities.

3. The method of claim 1 , wherein whether the emergency response data is valid is determined by determining whether received sensor data has exceeded a safety sensor threshold.

4. The method of claim 1 , further comprising:

determining a location of the at least one additional emergency reporting entity; and

weighting the emergency response data received from the at least one additional emergency reporting entity, at least in part based on the location of the at least one additional emergency reporting entity.

5. The method of claim 1 , further comprising:

determining whether a number of mobile devices that moved from or to the location of the emergency in a predetermined amount of time exceeds a predetermined threshold.

6. The method of claim 1 , further comprising:

weighting the emergency response data, at least in part based on a location of the emergency reporting entities, wherein the transmitting is performed, at least in part based on the weighting.

7. The method of claim 6 , wherein the transmitting to the one or more emergency response entities is performed based on the weighting and a threshold.

8. An apparatus, comprising:

a storage medium that stores a program; and

a processor configured to execute the program to

receive emergency response data from a plurality of emergency reporting entities at a location of an emergency;

determine whether the emergency response data provided by one or more of the emergency reporting entities is valid by determining whether at least one emergency reporting entity of the emergency reporting entities is a fixed sensor, and whether at least one additional emergency reporting entity of the emergency reporting entities is a mobile device;

determine a level of severity of the emergency response data;

transmit one or more notifications to one or more emergency response entities based on the level of severity and a type of emergency;

initiate an emergency response time window based on the type of emergency and the level of severity; and

perform a dispatch operation corresponding to the emergency response time window by notifying one or more non-emergency response entities of the emergency.

9. The apparatus of claim 8 , wherein the processor is further configured to

forward a request for additional data to one or more additional emergency reporting entities different from the plurality of emergency reporting entities; and

determine the type of emergency via response data received from the one or more additional emergency reporting entities.

10. The apparatus of claim 8 , wherein whether the emergency response data is valid is determined by determining whether received sensor data has exceeded a safety sensor threshold.

11. The apparatus of claim 8 , wherein the processor is further configured to

determine a location of the at least one additional emergency reporting entity; and

weight the emergency response data received from the at least one additional emergency reporting entity, at least in part based on the location of the at least one additional emergency reporting entity.

12. The apparatus of claim 8 , wherein the processor is further configured to determine whether a number of mobile devices that moved from or to the location of the emergency in a predetermined amount of time exceeds a predetermined threshold.

13. The apparatus of claim 8 , wherein the processor is further configured to perform a weighting of the emergency response data, at least in part based on a location of the emergency reporting entities, and the transmitting is performed, at least in part based on the weighting.

14. The apparatus of claim 13 , wherein the transmitting to the one or more emergency response entities is performed based on the weighting and a threshold.

15. A non-transitory, computer-readable storage medium configured to store instructions that, when executed, cause a processor to perform operations comprising:

receiving emergency response data from a plurality of emergency reporting entities at a location of an emergency;

determining whether the emergency response data provided by one or more of the emergency reporting entities is valid by determining whether at least one emergency reporting entity of the emergency reporting entities is a fixed sensor and whether at least one additional emergency reporting entity of the emergency reporting entities is a mobile device;

determining a level of severity of the emergency response data;

transmitting one or more notifications to one or more emergency response entities based on the level of severity and a type of emergency;

initiating an emergency response time window based on the type of emergency and the level of severity; and

performing a dispatch operation corresponding to the emergency response time window by notifying one or more non-emergency response entities of the emergency.

16. The non-transitory, computer-readable storage medium of claim 15 , wherein the operations further comprise forwarding a request for additional data to one or more additional emergency reporting entities different from the plurality of emergency reporting entities; and

determining the type of emergency via response data received from the one or more additional emergency reporting entities.

17. The non-transitory, computer-readable storage medium of claim 15 , wherein the operations further comprise:

determining a location of the at least one additional emergency reporting entity; and

weighting the emergency response data received from the at least one additional emergency reporting entity, at least in part based on the location of the at least one additional emergency reporting entity.

18. The non-transitory, computer-readable storage medium of claim 15 , wherein the operations further comprise:

determining whether a number of mobile devices that moved from or to the location of the emergency in a predetermined amount of time exceeds a predetermined threshold.

19. The non-transitory, computer-readable storage medium of claim 15 , wherein the operations further comprise:

weighting the emergency response data, at least in part based on a location of the emergency reporting entities, and the transmitting is performed, at least in part based on the weighting.

20. The non-transitory, computer-readable storage medium of claim 19 , wherein the transmitting to the one or more emergency response entities is performed based on the weighting and a threshold.

Assignments (5)
RELEASE OF SECURITY INTEREST Recorded Jan 31, 2023
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS AGENT
To: INTRADO LIFE & SAFETY, INC. (F/K/A WEST SAFETY SERVICES, INC.)
Reel/Frame 062570/0940 →
SECURITY INTEREST Recorded Jan 31, 2023
From: INTRADO LIFE & SAFETY, INC.
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 062596/0780 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 30, 2022
From: INTRADO CORPORATION
To: INTRADO LIFE & SAFETY, INC.
Reel/Frame 062252/0588 →
SECURITY INTEREST Recorded Sep 22, 2022
From: INTRADO CORPORATION (F/K/A WEST CORPORATION)
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061183/0494 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 23, 2021
From: LIGRANI, NORA
To: INTRADO CORPORATION
Reel/Frame 055378/0843 →
Continuity (2)
Provisional Application 62980996 · Feb 24, 2020
Related Publication 20210267010A1 · Aug 26, 2021
References Cited (72)
US 8175225B2 · Buscemi et al. · 2012 [cited by applicant]
US 8447014B2 · Nelson · 2013 [cited by applicant]
US 9380144B1 · Kritt · 2016 [cited by examiner]
US 9457754B1 · Christensen · 2016 [cited by examiner]
US 9602152B2 · Wohl · 2017 [cited by examiner]
US 9619996B1 · Smith · 2017 [cited by examiner]
US 9767677B1 · Paulin · 2017 [cited by applicant]
US 9852599B1 · Slavin et al. · 2017 [cited by applicant]
US 10142687B2 · Gurha · 2018 [cited by examiner]
US 10212231B2 · Cooper · 2019 [cited by examiner]
US 10750346B1 · Di Domenico · 2020 [cited by examiner]
US 10824741B1 · Porter · 2020 [cited by applicant]
US 11315408B1 · Nelson et al. · 2022 [cited by applicant]
US 20110071880A1 · Spector · 2011 [cited by examiner]
US 20110142207A1 · Goldman et al. · 2011 [cited by applicant]
US 20130046847A1 · Zavesky · 2013 [cited by examiner]
US 20130214925A1 · Weiss · 2013 [cited by applicant]
US 20130285820A1 · Assuncao · 2013 [cited by examiner]
US 20140115671A1 · Abhyanker · 2014 [cited by applicant]
US 20140364081A1 · Rauner · 2014 [cited by examiner]
US 20140368601A1 · deCharms · 2014 [cited by applicant]
US 20150288797A1 · Vincent · 2015 [cited by examiner]
US 20150379355A1 · Kanga · 2015 [cited by examiner]
US 20160094964A1 · Barfield, Jr. · 2016 [cited by examiner]
US 20160119424A1 · Kane et al. · 2016 [cited by applicant]
US 20160140299A1 · Al Harbi · 2016 [cited by examiner]
US 20160217669A1 · Benoit · 2016 [cited by examiner]
US 20160227384A1 · Mazzarella · 2016 [cited by examiner]
US 20160232774A1 · Noland · 2016 [cited by examiner]
US 20160266733A1 · Alon · 2016 [cited by examiner]
US 20160277892A1 · Walker · 2016 [cited by examiner]
US 20160371968A1 · Almansour · 2016 [cited by applicant]
US 20170055126A1 · O'Keeffe · 2017 [cited by examiner]
US 20170086192A1 · Bohlander · 2017 [cited by examiner]
US 20170243485A1 · Rubin · 2017 [cited by examiner]
US 20170245237A1 · Thompson · 2017 [cited by examiner]
US 20170294131A1 · Jedrzejewski · 2017 [cited by examiner]
US 20170295252A1 · Mottur · 2017 [cited by examiner]
US 20170372593A1 · Chadwick et al. · 2017 [cited by applicant]
US 20180060767A1 · Dillard · 2018 [cited by examiner]
US 20180095607A1 · Proctor · 2018 [cited by applicant]
US 20180144587A1 · Stogel · 2018 [cited by applicant]
US 20180184051A1 · Watanabe · 2018 [cited by examiner]
US 20180225939A1 · Subramanian · 2018 [cited by examiner]
US 20180247135A1 · Oami · 2018 [cited by examiner]
US 20180253814A1 · Kaguma et al. · 2018 [cited by applicant]
US 20180272992A1 · Gage et al. · 2018 [cited by applicant]
US 20190038362A1 · Nash · 2019 [cited by examiner]
US 20190047578A1 · Swan et al. · 2019 [cited by applicant]
US 20190215339A1 · Chen · 2019 [cited by examiner]
US 20190311534A1 · Shore · 2019 [cited by applicant]
US 20190355237A1 · Singh · 2019 [cited by applicant]
US 20200034454A1 · Chamarajnager · 2020 [cited by examiner]
US 20200110935A1 · Paul · 2020 [cited by examiner]
US 20200178198A1 · Ding et al. · 2020 [cited by applicant]
US 20200236525A1 · Paulin · 2020 [cited by applicant]
US 20200274962A1 · Martin · 2020 [cited by examiner]
US 20200284938A1 · Chaturvedi · 2020 [cited by examiner]
US 20200314240A1 · Leavitt et al. · 2020 [cited by applicant]
US 20200314623A1 · Pellegrini · 2020 [cited by examiner]
US 20200334470A1 · Abeykoon · 2020 [cited by examiner]
US 20200357268A1 · Tyson · 2020 [cited by applicant]
US 20200396292A1 · Ono · 2020 [cited by examiner]
US 20210006933A1 · Dean · 2021 [cited by applicant]
US 20210084436A1 · Sutherland · 2021 [cited by applicant]
US 20220141616A1 · Myshenin et al. · 2022 [cited by applicant]
USPTO Non-Final Office Action mailed in U.S. Appl. No. 18/226,614 on Mar. 26, 2024, 17 pages. [cited by applicant]
Non-Final Office Action mailed in U.S. Appl. No. 18/382,864 dated Jun. 14, 2024, 22 pages. [cited by applicant]
USPTO Notice of Allowance mailed in U.S. Appl. No. 18/226,614 on Jul. 12, 2024, 12 pages. [cited by applicant]
USPTO Non-Final Office Action mailed in U.S. Appl. No. 18/226,148 on Jul. 18, 2024, 20 pages. [cited by applicant]
USPTO Non-Final Office Action mailed in U.S. Appl. No. 18/226,148 on Dec. 4, 2024, 10 pages. [cited by applicant]
USPTO Notice of Allowance mailed in U.S. Appl. No. 17/183,322 on Jun. 30, 2023, 11 pages. [cited by applicant]