IP Library › Granted Patent US 12,389,086
Granted Patent B2
US 12,389,086 · App. 18/048,676 · Granted Aug 12, 2025

Personalized emergency alert

Inventor: Luke Fay (San Diego, CA)
Assignee: SATURN LICENSING LLC
H04N21/814H04N21/25841G06Q10/02
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,389,086
App. No.
18/048,676
Granted
Aug 12, 2025
Kind
B2
Abstract

Techniques are described for expanding and/or improving the Advanced Television Systems Committee (ATSC) 3.0 television protocol in robustly delivering the next generation broadcast television services. Reverse 911 emergency alerts are personalized to a user of each receiver in the ATSC 3.0 system.

Claims (47)

1. A digital television system comprising:

at least one transmitter assembly comprising circuitry configured to:

obtain location information of a receiver;

obtain evacuation map information and accommodations reservation information corresponding to the location information;

transmit an emergency alert to the receiver; and

transmit the evacuation map information and the accommodations reservation information to the receiver,

wherein the receiver comprises circuitry configured to:

receive the emergency alert;

receive the evacuation map information and the accommodations reservation information;

automatically obtain an accommodations reservation based on the accommodations reservation information; and

send, via a network, the evacuation map information and the accommodations reservation information to a companion device associated with the receiver,

wherein the receiver and the companion device are is an Advanced Television Systems Committee (ATSC) 3.0 receiver and the companion device is an ATSC 3.0 companion device compatible.

2. The digital television system of claim 1 , wherein the circuitry of the receiver is configured to provide the location information.

3. A receiver comprising:

circuitry configured to:

receive data via broadcast;

communicate via a network;

receive an emergency alert via broadcast;

receive evacuation map information and accommodations reservation information via at least one of the broadcast or the network, the evacuation map information and the accommodations reservation information being associated with the emergency alert and corresponding to location information indicative of a location of the receiver;

automatically obtain an accommodations reservation based on the accommodations reservation information; and

send, via the network, the evacuation map information and the accommodations reservation information to a companion device associated with the receiver,

wherein the receiver is an Advanced Television Systems Committee (ATSC) 3.0 receiver and the companion device is an ATSC 3.0 companion device.

4. The receiver of claim 3 , wherein the circuitry comprises an ATSC 3.0 tuner and is configured to receive data in accordance with a moving picture experts group (MPEG) media transport protocol (MMTP) or a real-time object delivery over unidirectional transport (ROUTE) protocol.

5. The receiver of claim 3 , comprising a global positioning satellite (GPS) receiver, the GPS receiver being configured to determine the location of the receiver.

6. The receiver of claim 3 , wherein the evacuation map information includes information on a shelter corresponding to the location information.

7. The receiver of claim 3 , wherein the circuitry comprises a network interface configured to wirelessly communicate with the companion device directly or via the network.

8. The receiver of claim 3 , comprising a sensor to determine a user location, wherein the circuitry is configured to process the emergency alert at least in part on a basis of the user location.

9. The receiver of claim 3 , wherein the circuitry is configured to determine whether a user acknowledgement of the emergency alert has been received within a period of time and to cause communication with a user device to be performed if it has not.

10. The receiver of claim 3 , wherein the circuitry is configured to control communicating with another receiver configured to receive an emergency alert.

11. The receiver of claim 3 , wherein the circuitry is configured to send the location information via the network.

12. The receiver of claim 3 comprising:

a display; and

a speaker,

wherein the display and the speaker are configured to output audiovisual content received via at least one of the broadcast or the network.

13. A method of a receiver, the method comprising:

receiving data via broadcast;

communicating via a network;

receiving an emergency alert via broadcast;

receiving evacuation map information and accommodations reservation information via at least one of the broadcast or the network, the evacuation map information and the accommodations reservation information being associated with the emergency alert and corresponding to location information indicative of a location of the receiver;

automatically obtaining an accommodations reservation based on the accommodations reservation information; and

sending, via the network, the evacuation map information and the accommodations reservation information to a companion device associated with the receiver,

wherein the receiver is an Advanced Television Systems Committee (ATSC) 3.0 receiver and the companion device is an ATSC 3.0 companion device.

14. The method of claim 13 , wherein the broadcast is an ATSC 3.0 broadcast and conveys data in accordance with a moving picture experts group (MPEG) media transport protocol (MMTP) or a real-time object delivery over unidirectional transport (ROUTE) protocol.

15. The method of claim 13 , wherein the evacuation map information includes information on a shelter corresponding to the location information.

16. The method of claim 13 comprising wirelessly communicating with the companion device directly or via the network.

17. The method of claim 13 comprising determining a user location and processing the emergency alert at least in part on a basis of the user location.

18. The method of claim 13 comprising determining whether a user acknowledgement of the emergency alert has been received within a period of time, and causing communication with a user device to be performed if it has not.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2024
From: SONY GROUP CORPORATION
To: SATURN LICENSING LLC
Reel/Frame 066314/0103 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 29, 2024
From: SONY CORPORATION
To: SONY GROUP CORPORATION
Reel/Frame 066278/0418 →
Continuity (2)
Continuation 16795352 · Feb 19, 2020
Related Publication 20230179835A1 · Jun 8, 2023
References Cited (37)
US 9037108B1 · Delatorre · 2015 [cited by applicant]
US 9773047B2 · Chu et al. · 2017 [cited by applicant]
US 20010051876A1 · Seigel · 2001 [cited by examiner]
US 20090210262A1 · Rines et al. · 2009 [cited by applicant]
US 20090249460A1 · Fitzgerald et al. · 2009 [cited by applicant]
US 20100146541A1 · Velazquez · 2010 [cited by examiner]
US 20100218209A1 · Kendall · 2010 [cited by applicant]
US 20140143801A1 · Russell et al. · 2014 [cited by applicant]
US 20150032484A1 · Mermelstein · 2015 [cited by applicant]
US 20150149220A1 · Omar · 2015 [cited by applicant]
US 20150256902A1 · Fusco et al. · 2015 [cited by applicant]
US 20160149657A1 · Kurihara et al. · 2016 [cited by applicant]
US 20160295300A1 · Alman et al. · 2016 [cited by applicant]
US 20190058909A1 · Eyer et al. · 2019 [cited by applicant]
US 20190289370A1 · Deshpande et al. · 2019 [cited by applicant]
US 20200005409A1 · Rowden et al. · 2020 [cited by applicant]
JP 2009069999A · 2009 [cited by applicant]
WO WO2018016295A1 · 2018 [cited by examiner]
Advanced Television Systems Committee, ATSC Standard: Companion Device, Oct. 2, 2019, Doc. A/338:2019 (Year: 2019). [cited by examiner]
“RFC 4033, DNS Security Introduction and Requirements,” Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, Internet Engineering Task Force, Fremont, CA, Mar. 2005. [cited by applicant]
“RFC 4055, Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” J. Schaad, B. Kaliski, R. Housley… [cited by applicant]
“ATSC Implementation Team Document—ATSC 3.0 Advanced Emergency Information System—Implementation Guide”, ATSC, Feb. 20, 2019. [cited by applicant]
“ATSC Standard: ATSC 3.0 Interactive Content (A/344)”, May 2, 2019. [cited by applicant]
“ATSC Standard: ATSC 3.0 Security and Service Protection (A/360)”, Aug. 20, 2019. [cited by applicant]
“ATSC Standard: ATSC 3.0 System (A/300)”, May 15, 2020. [cited by applicant]
“ATSC Standard: Signaling, Delivery, Synchronization, and Error Protection (A/331)”, Jun. 19, 2019. [cited by applicant]
“RFC 3279, Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” L. Bassham, W. Polk, R. Housley, Internet Engineering Task Force, Fremon… [cited by applicant]
“RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, W. Polk, Internet Engineering Task Force, Fremo… [cited by applicant]
“RFC 5289, TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (Gcm),” E. Rescorla, Internet Engineering Task Force, Fremont, CA, Aug. 2008. [cited by applicant]
“RFC 5480, Elliptic Curve Cryptography Subject Public Key Information,” S. Turner, D. Brown, K. Yiu, R. Housley, T. Polk, Internet Engineering Task Force, Fremont, CA, Mar. 2009. [cited by applicant]
“RFC 5652, Cryptographic Message Syntax (CMS),” R. Housley, Internet Engineering Task Force, Fremont, CA, Sep. 2009. [cited by applicant]
“RFC 5751, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.Message Specification,” B. Ramsdell, S. Turner, Internet Engineering Task Force, Fremont, CA, Jan. 2010. [cited by applicant]
“RFC 5753, Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS),” S. Turner, D. Brown, Internet Engineering Task Force, Fremont, CA, Jan. 2010. [cited by applicant]
“RFC 5758, Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA,” Q. Dang, S. Santesson, K. Moriarty, D. Brown, T. Polk, Internet Engineering Task Force, Fremont, CA, Jan. 20… [cited by applicant]
“RFC 5940, Additional Cryptographic Message Syntax (CMS) Revocation Information Choices,” S. Turner, R. Housley, Internet Engineering Task Force, Fremont, CA, Aug. 2010. [cited by applicant]
“RFC 6960, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol—OCSP,” S. Santesson, M. Myers, R. Ankney, A. Malpani, S. Galperin, C. Adams, Internet Engineering Task Force, Fremont, CA, Jun. 2013. [cited by applicant]
“RFC 5019, The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments,” A. Deacon, R. Hurst, Internet Engineering Task Force, Fremont, CA, Sep. 2007. [cited by applicant]
Cited By (1)
US 12,513,363