US20210258655A1 - Personalized emergency alert - Google Patents
Personalized emergency alert Download PDFInfo
- Publication number
- US20210258655A1 US20210258655A1 US16/795,352 US202016795352A US2021258655A1 US 20210258655 A1 US20210258655 A1 US 20210258655A1 US 202016795352 A US202016795352 A US 202016795352A US 2021258655 A1 US2021258655 A1 US 2021258655A1
- Authority
- US
- United States
- Prior art keywords
- receiver
- digital television
- location
- emergency alert
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 claims abstract description 15
- 230000011664 signaling Effects 0.000 description 8
- 238000003860 storage Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000015654 memory Effects 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- VKALYYFVKBXHTF-UHFFFAOYSA-N 4-(methylsulfanyl)-m-cresol Chemical compound CSC1=CC=C(O)C=C1C VKALYYFVKBXHTF-UHFFFAOYSA-N 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000014759 maintenance of location Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 208000019901 Anxiety disease Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000036506 anxiety Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000001931 thermography Methods 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/488—Data services, e.g. news ticker
- H04N21/4882—Data services, e.g. news ticker for displaying messages, e.g. warnings, reminders
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25808—Management of client data
- H04N21/25841—Management of client data involving the geographical location of the client
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
- H04N21/42202—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS] environmental sensors, e.g. for detecting temperature, luminosity, pressure, earthquakes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
- H04N21/44213—Monitoring of end-user related data
- H04N21/44218—Detecting physical presence or behaviour of the user, e.g. using sensors to detect if the user is leaving the room or changes his face expression during a TV program
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
- H04N21/485—End-user interface for client configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/654—Transmission by server directed to the client
- H04N21/6543—Transmission by server directed to the client for forcing some client operations, e.g. recording
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/658—Transmission by the client directed to the server
- H04N21/6581—Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8126—Monomedia components thereof involving additional data, e.g. news, sports, stocks, weather forecasts
- H04N21/814—Monomedia components thereof involving additional data, e.g. news, sports, stocks, weather forecasts comprising emergency warnings
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
Definitions
- This application relates to technical advances necessarily rooted in computer technology and directed to digital television, and more particularly to Advanced Television Systems Committee (ATSC) 3.0.
- ATSC Advanced Television Systems Committee
- ATSC 3.0 The Advanced Television Systems Committee (ATSC) 3.0 suite of standards is a set of over a dozen industry technical standards as indicated in “ATSC 3.0 System” (A/300) for delivering the next generation of broadcast television.
- ATSC 3.0 supports delivery of a wide range of television services including televised video, interactive services, non-real time delivery of data, and tailored advertising to a large number of receiving devices, from ultra-high definition televisions to wireless telephones.
- ATSC 3.0 also orchestrates coordination between broadcast content (referred to as “over the air”) and related broadband delivered content and services (referred to as “over the top”).
- ATSC 3.0 is designed to be flexible so that as technology evolves, advances can be readily incorporated without requiring a complete overhaul of any related technical standard. Present principles are directed to such advances as divulged below.
- ATSC 3.0 provides for emergency alerts.
- emergency alerts are monolithic and provide very little information regarding the scope and imminence or the instant danger, etc.
- present principles provide an ATSC 3.0-based emergency alert system that provides personalized information regarding an imminent threat.
- This information can include an amount of time before the threat is life threatening, identification and directions to a nearest shelter, and an automatic booking of the user into the safest hotel nearest the user's receiver.
- the receiver in response to the alert may contact the emergency alert (broadcaster) server to provide additional information. If the user is not present as indicated by lack of an acknowledgement input to the receiver, the system may attempt to locate the user via a GPS location of the user's phone and call the user.
- a digital television apparatus includes at least one transmitter assembly with at least one processor programmed with instructions to access respective location information for respective first and second receivers indicating respective first and second locations.
- the instructions are executable to broadcast an emergency alert altered at least in part with the location information such that the first receiver presents first information in the emergency alert and the second receiver presents second information in the emergency alert different from the first information.
- the first receiver may not present the second information. Further, the first receiver may be configured to contact the second receiver via other distribution methods (for example, internet communication) and not rely on the transmitter containing user information.
- other distribution methods for example, internet communication
- the first information includes one or more items in an amount of time before a threat subject to the emergency alert is life threatening at the first location, an identification and directions to a shelter nearest the first location, and notification of an automatic booking of a user into a hotel nearest the first location.
- the transmitter instructions may be executable to, responsive to not receiving, within a period, an acknowledgement of the reverse 911 emergency alert from the first receiver, access information associated with the first receiver to identify a phone number and call the phone number.
- an emergency alert refers to a public safety communications technology used by public safety organizations to communicate with groups of people in a defined geographic area.
- the system uses a database of end user identifying information including end user receiver information in conjunction with geographic information to deliver emergency notifications to a selected set of service subscribers.
- features of an emergency alert (sometimes referred to as a “reverse 911”) appear in several documents within the ATSC 3.0 suite of standards which are listed in A/300.
- a digital television system in another aspect, includes digital television transmitter equipment configured with instructions to generate a first emergency alert tailored to a first location in an emergency alert coverage area.
- the first emergency alert indicates a first emergency.
- the transmitter equipment is further configured to generate a second emergency alert tailored to a second location in the emergency alert coverage area, with the second emergency alert indicating the first emergency and containing information different from information in the first emergency alert.
- the transmitting equipment is configured to transmit the first emergency alert to a first receiver at the first location, and to transmit the second emergency alert to a second receiver at the second location.
- a method in another aspect, in a digital television system, includes transmitting a first alert of a first emergency to a first receiver.
- the first alert contains information identified at least in part based on a first location associated with the first receiver.
- the method further includes transmitting a second alert of the first emergency to a second receiver, with the second alert containing information identified at least in part based on a second location associated with the second receiver.
- FIG. 1 is a block diagram of an Advanced Television Systems Committee (ATSC) 3.0 system
- FIG. 2 is a block diagram showing components of the devices shown in FIG. 1 ;
- FIG. 3 is a flow chart of example logic consistent with present principles
- FIG. 4 is a screen shot of an example emergency alert presented on a receiver
- FIG. 5 is a screen shot of an example UI for establishing user information
- FIG. 6 is a screen shot of an example UI for selecting events to be notified of/acted upon.
- FIG. 7 is a flow chart illustrating example receiver logic on an implementation.
- An example system herein may include ATSC 3.0 source components and client components, connected via broadcast and/or over a network such that data may be exchanged between the client and ATSC 3.0 source components.
- the client components may include one or more computing devices including portable televisions (e.g. smart TVs, Internet-enabled TVs), portable computers such as laptops and tablet computers, and other mobile devices including smart phones and additional examples discussed below.
- portable televisions e.g. smart TVs, Internet-enabled TVs
- portable computers e.g. smart TVs, Internet-enabled TVs
- portable computers such as laptops and tablet computers
- other mobile devices including smart phones and additional examples discussed below.
- These client devices may operate with a variety of operating environments.
- some of the client computers may employ, as examples, operating systems from Microsoft, or a Unix operating system, or operating systems produced by Apple Computer or Google, such as Android®.
- These operating environments may be used to execute one or more browsing programs, such as a browser made by Microsoft or Google or Mozilla or other browser
- ATSC 3.0 source components may include broadcast transmission components and servers and/or gateways that may include one or more processors executing instructions that configure the source components to broadcast data and/or to transmit data over a network such as the Internet.
- a client component and/or a local ATSC 3.0 source component may be instantiated by a game console such as a Sony PlayStation®, a personal computer, etc.
- servers and/or clients can include firewalls, load balancers, temporary storages, and proxies, and other network infrastructure for reliability and security.
- instructions refer to computer-implemented steps for processing information in the system. Instructions can be implemented in software, firmware or hardware and include any type of programmed step undertaken by components of the system.
- a processor may be any conventional general-purpose single- or multi-chip processor that can execute logic by means of various lines such as address lines, data lines, and control lines and registers and shift registers.
- Software modules described by way of the flow charts and user interfaces herein can include various sub-routines, procedures, etc. Without limiting the disclosure, logic stated to be executed by a particular module can be redistributed to other software modules and/or combined together in a single module and/or made available in a shareable library. While flow chart format may be used, it is to be understood that software may be implemented as a state machine or other logical method.
- logical blocks, modules, and circuits can be implemented or performed with a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA) or other programmable logic device such as an application specific integrated circuit (ASIC), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
- DSP digital signal processor
- FPGA field programmable gate array
- ASIC application specific integrated circuit
- a processor can be implemented by a controller or state machine or a combination of computing devices.
- HTTP hypertext markup language
- ROM read-only memory
- EEPROM electrically erasable programmable read-only memory
- CD-ROM compact disk read-only memory
- DVD digital versatile disc
- a connection may establish a computer-readable medium.
- Such connections can include, as examples, hard-wired cables including fiber optics and coaxial wires and digital subscriber line (DSL) and twisted pair wires.
- a system having at least one of A, B, and C includes systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.
- an example of an ATSC 3.0 source component is labeled “broadcaster equipment” 10 and may include over-the-air (OTA) equipment 12 for wirelessly broadcasting, typically via orthogonal frequency division multiplexing (OFDM) in a one-to-many relationship, television data to plural receivers 14 such as ATSC 3.0 televisions.
- OTA over-the-air
- OFDM orthogonal frequency division multiplexing
- One or more receivers 14 may communicate with one or more companion devices 16 such as remote controls, tablet computers, mobile telephones, and the like over a short range, typically wireless link 18 that may be implemented by Bluetooth®, low energy Bluetooth, other near field communication (NFC) protocol, infrared (IR), etc.
- one or more of the receivers 14 may communicate, via a wired and/or wireless network link 20 such as the Internet, with over-the-top (OTT) equipment 22 of the broadcaster equipment 10 typically in a one-to-one relationship.
- the OTA equipment 12 may be co-located with the OTT equipment 22 or the two sides 12 , 22 of the broadcaster equipment 10 may be remote from each other and may communicate with each other through appropriate means.
- a receiver 14 may receive ATSC 3.0 television signals OTA over a tuned-to ATSC 3.0 television channel and may also receive related content, including television, OTT (broadband).
- computerized devices described in all of the figures herein may include some or all of the components set forth for various devices in FIGS. 1 and 2 .
- FIG. 2 illustrates an example protocol stack that may be implemented by a combination of hardware and software.
- broadcasters can send hybrid service delivery in which one or more program elements are delivered via a computer network (referred to herein as “broadband” and “over-the-top” (OTT)) as well as via a wireless broadcast (referred to herein as “broadcast” and “over-the-air” (OTA)).
- FIG. 2 also illustrates an example stack with hardware that may be embodied by a receiver.
- the application layer 204 can include one or more software applications written in, e.g., HTML5/JavaScript running in a runtime environment.
- the applications in the application stack 204 may include linear TV applications, interactive service applications, companion screen applications, personalization applications, emergency alert applications, and usage reporting applications.
- the applications typically are embodied in software that represents the elements that the viewer experiences, including video coding, audio coding and the run-time environment.
- an application may be provided that enables a user to control dialog, use alternate audio tracks, control audio parameters such as normalization and dynamic range, and so on.
- the presentation layer 206 includes, on the broadcast (OTA) side, broadcast audio-video playback devices referred to as Media Processing Units (MPU) 208 that, when implemented in a receiver, decode and playback, on one or more displays and speakers, wirelessly broadcast audio video content.
- the MPU 208 is configured to present International Organization for Standardization (ISO) base media file format (BMFF) data representations 210 and video in high efficiency video coding (HEVC) with audio in, e.g., Dolby audio compression (AC)-4 format.
- ISO BMFF is a general file structure for time-based media files broken into “segments” and presentation metadata. Each of the files is essentially a collection of nested objects each with a type and a length.
- the MPU 208 may access a broadcast side encrypted media extension (EME)/common encryption (CENC) module 212 .
- EME broadcast side encrypted media extension
- CENC common encryption
- FIG. 2 further illustrates that on the broadcast side the presentation layer 206 may include signaling modules, including either motion pictures expert group (MPEG) media transport protocol (MMTP) signaling module 214 or real-time object delivery over unidirectional transport (ROUTE) signaling module 216 for delivering non-real time (NRT) content 218 that is accessible to the application layer 204 .
- NRT content may include but is not limited to stored replacement advertisements.
- the presentation layer 206 can include one or more dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) player/decoders 220 for decoding and playing audio-video content from the Internet.
- DASH dynamic adaptive streaming over hypertext transfer protocol
- the DASH player 220 may access a broadband side EME/CENC module 222 .
- the DASH content may be provided as DASH segments 224 in ISO/BMFF format.
- the broadband side of the presentation layer 206 may include NRT content in files 226 and may also include signaling objects 228 for providing play back signaling.
- the session layer 230 includes, on the broadcast side, either MMTP protocol 232 or ROUTE protocol 234 .
- the session layer 230 includes HTTP protocol 236 which may be implemented as HTTP-secure (HTTP(S).
- HTTP HTTP-secure
- the broadcast side of the session layer 230 also may employ a HTTP proxy module 238 and a service list table (SLT) 240 .
- the SLT 240 includes a table of signaling information which is used to build a basic service listing and provide bootstrap discovery of the broadcast content.
- Media presentation descriptions (MPD) are included in the “ROUTE Signaling” tables delivered over user datagram protocol (UDP) by the ROUTE transport protocol.
- a transport layer 242 is below the session layer 230 in the protocol stack for establishing low-latency and loss-tolerating connections.
- the transport layer 242 uses (UDP 244 and on the broadband side transmission control protocol (TCP) 246 .
- the example non-limiting protocol stack shown in FIG. 2 also includes a network layer 248 below the transport layer 242 .
- the network layer 248 uses Internet protocol (IP) on both sides for IP packet communication, with multicast delivery being typical on the broadcast side and unicast being typical on the broadband side.
- IP Internet protocol
- the physical layer 250 which includes broadcast transmission/receive equipment 252 and computer network interface(s) 254 for communicating on the respective physical media associated with the two sides.
- the physical layer 250 converts Internet Protocol (IP) packets to be suitable to be transported over the relevant medium and may add forward error correction functionality to enable error correction at the receiver as well as contain modulation and demodulation modules to incorporate modulation and demodulation functionalities. This converts bits into symbols for long distance transmission as well as to increase bandwidth efficiency.
- IP Internet Protocol
- the physical layer 250 typically includes a wireless broadcast transmitter to broadcast data wirelessly using orthogonal frequency division multiplexing (OFDM) while on the OTT side the physical layer 250 includes computer transmission components to send data over the Internet.
- OFDM orthogonal frequency division multiplexing
- DASH-IF DASH Industry Forum
- HTTP/TCP/IP DASH Industry Forum
- Media files in the DASH-IF profile based on the ISO BMFF may be used as the delivery, media encapsulation and synchronization format for both broadcast and broadband delivery.
- Each receiver 14 typically includes a protocol stack that is complementary to that of the broadcaster equipment.
- a receiver 14 in FIG. 1 may include, as shown in FIG. 2 , an Internet-enabled TV with an ATSC 3.0 TV tuner (equivalently, set top box controlling a TV) 256 .
- the receiver 14 may be an Android®-based system.
- the receiver 14 alternatively may be implemented by a computerized Internet enabled (“smart”) telephone, a tablet computer, a notebook computer, a wearable computerized device, and so on. Regardless, it is to be understood that the receiver 14 and/or other computers described herein is configured to undertake present principles (e.g. communicate with other devices to undertake present principles, execute the logic described herein, and perform any other functions and/or operations described herein).
- the receiver 14 can be established by some or all of the components shown in FIG. 1 .
- the receiver 14 can include one or more displays 258 that may be implemented by a high definition or ultra-high definition “4K” or higher flat screen and that may or may not be touch-enabled for receiving user input signals via touches on the display.
- the receiver 14 may also include one or more speakers 260 for outputting audio in accordance with present principles, and at least one additional input device 262 such as, e.g., an audio receiver/microphone for, e.g., entering audible commands to the receiver 14 to control the receiver 14 .
- the example receiver 14 may further include one or more network interfaces 264 for communication over at least one network such as the Internet, a WAN, a LAN, a PAN etc. under control of one or more processors 266 .
- the interface 264 may be, without limitation, a Wi-Fi transceiver, which is an example of a wireless computer network interface, such as but not limited to a mesh network transceiver.
- the interface 264 may be, without limitation, a Bluetooth® transceiver, Zigbee® transceiver, Infrared Data Association (IrDA) transceiver, Wireless USB transceiver, wired USB, wired LAN, Powerline or Multimedia over Coax Alliance (MoCA).
- IrDA Infrared Data Association
- the processor 266 controls the receiver 14 to undertake present principles, including the other elements of the receiver 14 described herein such as, for instance, controlling the display 258 to present images thereon and receiving input therefrom.
- the network interface 264 may be, e.g., a wired or wireless modem or router, or other appropriate interface such as, e.g., a wireless telephony transceiver, or Wi-Fi transceiver as mentioned above, etc.
- the receiver 14 may also include one or more input ports 268 such as a high definition multimedia interface (HDMI) port or a USB port to physically connect (using a wired connection) to another CE device and/or a headphone port to connect headphones to the receiver 14 for presentation of audio from the receiver 14 to a user through the headphones.
- the input port 268 may be connected via wire or wirelessly to a cable or satellite source of audio video content.
- the source may be a separate or integrated set top box, or a satellite receiver.
- the source may be a game console or disk player.
- the receiver 14 may further include one or more computer memories 270 such as disk-based or solid-state storage that are not transitory signals, in some cases embodied in the chassis of the receiver as standalone devices or as a personal video recording device (PVR) or video disk player either internal or external to the chassis of the receiver for playing back audio video (AV) programs or as removable memory media.
- the receiver 14 can include a position or location receiver 272 such as but not limited to a cellphone receiver, global positioning satellite (GPS) receiver, and/or altimeter that is configured to e.g. receive geographic position information from at least one satellite or cellphone tower and provide the information to the processor 266 and/or determine an altitude at which the receiver 14 is disposed in conjunction with the processor 266 .
- GPS global positioning satellite
- altimeter that is configured to e.g. receive geographic position information from at least one satellite or cellphone tower and provide the information to the processor 266 and/or determine an altitude at which the receiver 14 is disposed in conjunction with the processor 266 .
- another suitable position receiver other
- the receiver 14 may include one or more cameras 274 that may include one or more of a thermal imaging camera, a digital camera such as a webcam, and/or a camera integrated into the receiver 14 and controllable by the processor 266 to gather pictures/images and/or video in accordance with present principles.
- a Bluetooth® transceiver 276 or other Near Field Communication (NFC) element for communication with other devices using Bluetooth® and/or NFC technology, respectively.
- NFC element can be a radio frequency identification (RFID) element.
- the receiver 14 may include one or more auxiliary sensors 278 (such as a motion sensor such as an accelerometer, gyroscope, cyclometer, or a magnetic sensor and combinations thereof), an infrared (IR) sensor for receiving IR commands from a remote control, an optical sensor, a speed and/or cadence sensor, a gesture sensor (for sensing gesture commands) and so on providing input to the processor 266 .
- auxiliary sensors 278 such as a motion sensor such as an accelerometer, gyroscope, cyclometer, or a magnetic sensor and combinations thereof
- IR infrared
- An IR sensor 280 may be provided to receive commands from a wireless remote control.
- a battery (not shown) may be provided for powering the receiver 14 .
- the companion device 16 may incorporate some or all of the elements shown in relation to the receiver 14 described above.
- the methods described herein may be implemented as software instructions executed by a processor, suitably configured application specific integrated circuits (ASIC) or field programmable gate array (FPGA) modules, or any other convenient manner as would be appreciated by those skilled in those art.
- ASIC application specific integrated circuits
- FPGA field programmable gate array
- the software instructions may be embodied in a non-transitory device such as a CD ROM or Flash drive.
- the software code instructions may alternatively be embodied in a transitory arrangement such as a radio or optical signal, or via a download over the Internet.
- the OTA 12 and/or OTT 22 assembly may, for at least some and preferably most or all of the receivers 14 in the digital television system, enter an emergency alert (also referred to herein as a reverse 911) routine at block 300 in which, at block 302 , for each receiver the location of the receiver is identified, as well as certain user information of the receiver.
- the location of the receiver may be identified by causing the receiver to send its GPS location information to the digital television system. Or, the location may be manually input by a user.
- the location may be obtained in other ways, such as by having the receiver triangulate its location using signals from multiple transmitters in the digital television system or in another system such as base stations in a wireless telephony network in the event that the receiver has a wireless telephony transceiver.
- the user information which may include demographic information, a cell phone number, and information pertaining to special needs of people in the home in which the receiver is located may be obtained from the purchaser of the receiver at the point of sale. Or, the cell phone number to be associated with the receiver for use described further below may be looked up by the broadcaster using a database that correlates locations (in this case, the address corresponding to the location of the receiver) with cell phone numbers. Yet again, the user information may be input to the receiver by a user as described below in connection with FIG. 5 . Other techniques to gather the user information.
- an emergency alert is generated by the digital television broadcaster and tailored for at least some of the receivers 14 in the system using the respective location and user information of each receiver.
- a first receiver 14 presents first information in the emergency alert and a second receiver 14 presents second information in the emergency alert different from the first information.
- the first receiver may use the information directly to contact the second receiver to determine user presence. Once user location is determined, appropriate action can automatically take place whether finding evacuation routes, hotel reservations, etc. are to be made available.
- Examples of tailoring this information include but are not limited to an amount of time before a threat subject of the emergency alert is life threatening at the receiver location, directions to a shelter nearest the receiver location, and an automatic booking of a user into a hotel nearest the receiver location along with a notification thereof.
- the logic may move to block 306 .
- the phone number associated with the receiver as obtained at block 302 may be called with a recorded audible alert that may contain some or all of the information discussed herein in audible form.
- FIG. 4 illustrates further.
- a UI 400 may be presented on a display of the receiver as shown in which an identification 402 of the nature of the alert is resented, in the example shown, a tornado. If the name of a user associated with the receiver is known, the name may appear in the alert 402 .
- an advisory 404 may be presented indicating a future time at which the event that is subject to the alert is expected to become life threatening at the location of the receiver. For example, the advisory 404 may indicate that the tornado will arrive in one hour. Similar advisories may be presented for emergencies such as wildfires, etc.
- an advisory 406 may be presented indicating the location of nearest shelter to the location of the receiver that people can seek. This location may be obtained using a database of shelters and their locations and then selecting the shelter closest to the location of the receiver. In some cases, the closest shelter may not be designated as “safe” for the particular emergency, such as a tornado, in which case the indicated shelter is the closest safe (e.g., tornado-hardened) shelter to the receiver.
- a selector 408 may be presented and may be selectable using, e.g., a remote control (RC) to cause the display to present a map showing the route from the receiver location to the shelter.
- RC remote control
- the emergency alert system may access a database of lodgings and automatically book a room at a lodging nearby the location of the receiver at the closest location determined to be safe from the emergency, and a notification 410 of this may be presented on the display.
- An acknowledgement selector 412 may be presented and may be selectable using, e.g., the RC to enable a viewer of the receiver to transmit an acknowledgement of having seen the UI 400 to the digital television system so that the system can dispense with the phone call at block 306 of FIG. 3 .
- FIG. 5 illustrates a UI 500 that may be presented on the receiver display to enable gathering the user information discussed above in relation to block 302 in FIG. 3 .
- An advisory 502 may be presented indicating the location of the receiver as best identified by the digital television using example techniques described herein.
- the digital television system may access a map to correlate the location to a street address as indicated in FIG. 5 , which typically is more understandable to the user.
- a selector 504 may be presented for the user to confirm the location shown at 502 . If the location is incorrect the user may input the correct address in a filed 506 . Similarly, the user's phone number to be called in the event that block 306 in FIG. 3 requires execution may be presented at 508 , and the user may confirm this number by selecting a confirm selector 510 . If the number is incorrect the user may input the correct number in a field 512 . The user may input any special needs of persons in the household at block 514 , e.g., that one of the occupants of the location is blind, or elderly, etc.
- FIG. 6 illustrates a UI 600 that may be presented on a receiver such as an ATSC 3.0 TV.
- the UI 600 may present a list 602 of events that a user can select to be notified of.
- filter codes as described in ATSC standard “Signaling, Delivery, Synchronization, and Error Protection (A/331)” that can be set up to use content codes such as entertainment identification registry (EIDR) codes which trigger what content is available to consumers.
- the filter codes as indicated in the non-limiting example of FIG. 6 , may include amber alerts, school closings, traffic hazards, tornados, inclement weather, fires, etc.
- FIG. 7 provides illustration.
- a receiver in response to an emergency alert automatically may search for nearby hotel rooms for the user and may automatically secure a booking into an available room.
- the receiver may automatically send an electronic or telephonic or other message to an emergency authority such as the local constabulary indicating the location of one or more users as indicated by, e.g., motion detectors in the dwelling in which the receiver is located, face recognition based on time-stamped images rendered by a camera on the receiver, etc.
- an emergency authority such as the local constabulary indicating the location of one or more users as indicated by, e.g., motion detectors in the dwelling in which the receiver is located, face recognition based on time-stamped images rendered by a camera on the receiver, etc.
- the receiver knowing the phone number(s) as may be input using FIG. 5 , may “ping” the mobile device(s) of the user(s) for a location report, and relay the location(s) to the emergency authority.
- Block 704 indicates that the receiver may obtain evacuation maps in response to an emergency alert and send the map(s) to the mobile device(s) or use artificial intelligence to inform users with advanced warning of coming danger.
- the alerts can be sent to other devices (phones) the user has setup/informed to the ATSC 3.0 receiver allowing information to flow even if the user is not in the immediate area (such as on vacation).
- Block 706 indicates that the receiver further may prompt a user to check on others, such as neighbors, to check on safety or other matters, and to obtain additional information, e.g., by presenting a link the user can select for additional information.
- filter codes are used in extensions to fast data transfer (FDT)-Instance elements along with the broadcaster emergency information to trigger a process (including AI) of taking next steps for consumer safety.
- FDT fast data transfer
- Existing online services and user data may be used to provide options for a consumer as he faces emergencies.
Abstract
Description
- This application relates to technical advances necessarily rooted in computer technology and directed to digital television, and more particularly to Advanced Television Systems Committee (ATSC) 3.0.
- The Advanced Television Systems Committee (ATSC) 3.0 suite of standards is a set of over a dozen industry technical standards as indicated in “ATSC 3.0 System” (A/300) for delivering the next generation of broadcast television. ATSC 3.0 supports delivery of a wide range of television services including televised video, interactive services, non-real time delivery of data, and tailored advertising to a large number of receiving devices, from ultra-high definition televisions to wireless telephones. ATSC 3.0 also orchestrates coordination between broadcast content (referred to as “over the air”) and related broadband delivered content and services (referred to as “over the top”). ATSC 3.0 is designed to be flexible so that as technology evolves, advances can be readily incorporated without requiring a complete overhaul of any related technical standard. Present principles are directed to such advances as divulged below.
- As understood herein, ATSC 3.0 provides for emergency alerts. However, emergency alerts are monolithic and provide very little information regarding the scope and imminence or the instant danger, etc.
- Accordingly, present principles provide an ATSC 3.0-based emergency alert system that provides personalized information regarding an imminent threat. This information can include an amount of time before the threat is life threatening, identification and directions to a nearest shelter, and an automatic booking of the user into the safest hotel nearest the user's receiver. The receiver in response to the alert may contact the emergency alert (broadcaster) server to provide additional information. If the user is not present as indicated by lack of an acknowledgement input to the receiver, the system may attempt to locate the user via a GPS location of the user's phone and call the user.
- A digital television apparatus includes at least one transmitter assembly with at least one processor programmed with instructions to access respective location information for respective first and second receivers indicating respective first and second locations. The instructions are executable to broadcast an emergency alert altered at least in part with the location information such that the first receiver presents first information in the emergency alert and the second receiver presents second information in the emergency alert different from the first information.
- The first receiver may not present the second information. Further, the first receiver may be configured to contact the second receiver via other distribution methods (for example, internet communication) and not rely on the transmitter containing user information.
- In example embodiments, the first information includes one or more items in an amount of time before a threat subject to the emergency alert is life threatening at the first location, an identification and directions to a shelter nearest the first location, and notification of an automatic booking of a user into a hotel nearest the first location. In example implementations the transmitter instructions may be executable to, responsive to not receiving, within a period, an acknowledgement of the reverse 911 emergency alert from the first receiver, access information associated with the first receiver to identify a phone number and call the phone number.
- Generally, an emergency alert, sometimes referred to as a “reverse 911”, refers to a public safety communications technology used by public safety organizations to communicate with groups of people in a defined geographic area. The system uses a database of end user identifying information including end user receiver information in conjunction with geographic information to deliver emergency notifications to a selected set of service subscribers. According to A/300, features of an emergency alert (sometimes referred to as a “reverse 911”) appear in several documents within the ATSC 3.0 suite of standards which are listed in A/300.
- In another aspect, a digital television system includes digital television transmitter equipment configured with instructions to generate a first emergency alert tailored to a first location in an emergency alert coverage area. The first emergency alert indicates a first emergency. The transmitter equipment is further configured to generate a second emergency alert tailored to a second location in the emergency alert coverage area, with the second emergency alert indicating the first emergency and containing information different from information in the first emergency alert. The transmitting equipment is configured to transmit the first emergency alert to a first receiver at the first location, and to transmit the second emergency alert to a second receiver at the second location.
- In another aspect, in a digital television system, a method includes transmitting a first alert of a first emergency to a first receiver. The first alert contains information identified at least in part based on a first location associated with the first receiver. The method further includes transmitting a second alert of the first emergency to a second receiver, with the second alert containing information identified at least in part based on a second location associated with the second receiver.
- The details of the present application, both as to its structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:
-
FIG. 1 is a block diagram of an Advanced Television Systems Committee (ATSC) 3.0 system; -
FIG. 2 is a block diagram showing components of the devices shown inFIG. 1 ; -
FIG. 3 is a flow chart of example logic consistent with present principles; -
FIG. 4 is a screen shot of an example emergency alert presented on a receiver; -
FIG. 5 is a screen shot of an example UI for establishing user information; -
FIG. 6 is a screen shot of an example UI for selecting events to be notified of/acted upon; and -
FIG. 7 is a flow chart illustrating example receiver logic on an implementation. - This disclosure relates to technical advances in digital television such as in Advanced Television Systems Committee (ATSC) 3.0 television. An example system herein may include ATSC 3.0 source components and client components, connected via broadcast and/or over a network such that data may be exchanged between the client and ATSC 3.0 source components. The client components may include one or more computing devices including portable televisions (e.g. smart TVs, Internet-enabled TVs), portable computers such as laptops and tablet computers, and other mobile devices including smart phones and additional examples discussed below. These client devices may operate with a variety of operating environments. For example, some of the client computers may employ, as examples, operating systems from Microsoft, or a Unix operating system, or operating systems produced by Apple Computer or Google, such as Android®. These operating environments may be used to execute one or more browsing programs, such as a browser made by Microsoft or Google or Mozilla or other browser program that can access websites hosted by the Internet servers discussed below.
- ATSC 3.0 source components may include broadcast transmission components and servers and/or gateways that may include one or more processors executing instructions that configure the source components to broadcast data and/or to transmit data over a network such as the Internet. A client component and/or a local ATSC 3.0 source component may be instantiated by a game console such as a Sony PlayStation®, a personal computer, etc.
- Information may be exchanged over a network between the clients and servers. To this end and for security, servers and/or clients can include firewalls, load balancers, temporary storages, and proxies, and other network infrastructure for reliability and security.
- As used herein, instructions refer to computer-implemented steps for processing information in the system. Instructions can be implemented in software, firmware or hardware and include any type of programmed step undertaken by components of the system.
- A processor may be any conventional general-purpose single- or multi-chip processor that can execute logic by means of various lines such as address lines, data lines, and control lines and registers and shift registers.
- Software modules described by way of the flow charts and user interfaces herein can include various sub-routines, procedures, etc. Without limiting the disclosure, logic stated to be executed by a particular module can be redistributed to other software modules and/or combined together in a single module and/or made available in a shareable library. While flow chart format may be used, it is to be understood that software may be implemented as a state machine or other logical method.
- Present principles described herein can be implemented as hardware, software, firmware, or combinations thereof; hence, illustrative components, blocks, modules, circuits, and steps are set forth in terms of their functionality.
- Further to what has been alluded to above, logical blocks, modules, and circuits can be implemented or performed with a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA) or other programmable logic device such as an application specific integrated circuit (ASIC), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor can be implemented by a controller or state machine or a combination of computing devices.
- The functions and methods described below, when implemented in software, can be written in an appropriate language such as but not limited to hypertext markup language (HTML)-5, Java/JavaScript, C# or C++, and can be stored on or transmitted through a computer-readable storage medium such as a random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disk read-only memory (CD-ROM) or other optical disk storage such as digital versatile disc (DVD), magnetic disk storage or other magnetic storage devices including removable thumb drives, etc. A connection may establish a computer-readable medium. Such connections can include, as examples, hard-wired cables including fiber optics and coaxial wires and digital subscriber line (DSL) and twisted pair wires.
- Components included in one embodiment can be used in other embodiments in any appropriate combination. For example, any of the various components described herein and/or depicted in the Figures may be combined, interchanged or excluded from other embodiments.
- “A system having at least one of A, B, and C” (likewise “a system having at least one of A, B, or C” and “a system having at least one of A, B, C”) includes systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.
- Turning to
FIG. 1 , an example of an ATSC 3.0 source component is labeled “broadcaster equipment” 10 and may include over-the-air (OTA)equipment 12 for wirelessly broadcasting, typically via orthogonal frequency division multiplexing (OFDM) in a one-to-many relationship, television data toplural receivers 14 such as ATSC 3.0 televisions. One ormore receivers 14 may communicate with one ormore companion devices 16 such as remote controls, tablet computers, mobile telephones, and the like over a short range, typicallywireless link 18 that may be implemented by Bluetooth®, low energy Bluetooth, other near field communication (NFC) protocol, infrared (IR), etc. - Also, one or more of the
receivers 14 may communicate, via a wired and/orwireless network link 20 such as the Internet, with over-the-top (OTT)equipment 22 of thebroadcaster equipment 10 typically in a one-to-one relationship. TheOTA equipment 12 may be co-located with theOTT equipment 22 or the twosides broadcaster equipment 10 may be remote from each other and may communicate with each other through appropriate means. In any case, areceiver 14 may receive ATSC 3.0 television signals OTA over a tuned-to ATSC 3.0 television channel and may also receive related content, including television, OTT (broadband). Note that computerized devices described in all of the figures herein may include some or all of the components set forth for various devices inFIGS. 1 and 2 . - Referring now to
FIG. 2 , details of examples of components shown inFIG. 1 may be seen.FIG. 2 illustrates an example protocol stack that may be implemented by a combination of hardware and software. Using the ATSC 3.0 protocol stack shown inFIG. 2 and modified as appropriate for the broadcaster side, broadcasters can send hybrid service delivery in which one or more program elements are delivered via a computer network (referred to herein as “broadband” and “over-the-top” (OTT)) as well as via a wireless broadcast (referred to herein as “broadcast” and “over-the-air” (OTA)).FIG. 2 also illustrates an example stack with hardware that may be embodied by a receiver. - Disclosing
FIG. 2 in terms ofbroadcaster equipment 10, one ormore processors 200 accessing one or morecomputer storage media 202 such as any memories or storages described herein may be implemented to provide one or more software applications in a top-level application layer 204. Theapplication layer 204 can include one or more software applications written in, e.g., HTML5/JavaScript running in a runtime environment. Without limitation, the applications in theapplication stack 204 may include linear TV applications, interactive service applications, companion screen applications, personalization applications, emergency alert applications, and usage reporting applications. The applications typically are embodied in software that represents the elements that the viewer experiences, including video coding, audio coding and the run-time environment. As an example, an application may be provided that enables a user to control dialog, use alternate audio tracks, control audio parameters such as normalization and dynamic range, and so on. - Below the
application layer 204 is apresentation layer 206. Thepresentation layer 206 includes, on the broadcast (OTA) side, broadcast audio-video playback devices referred to as Media Processing Units (MPU) 208 that, when implemented in a receiver, decode and playback, on one or more displays and speakers, wirelessly broadcast audio video content. TheMPU 208 is configured to present International Organization for Standardization (ISO) base media file format (BMFF)data representations 210 and video in high efficiency video coding (HEVC) with audio in, e.g., Dolby audio compression (AC)-4 format. ISO BMFF is a general file structure for time-based media files broken into “segments” and presentation metadata. Each of the files is essentially a collection of nested objects each with a type and a length. To facilitate decryption, theMPU 208 may access a broadcast side encrypted media extension (EME)/common encryption (CENC)module 212. -
FIG. 2 further illustrates that on the broadcast side thepresentation layer 206 may include signaling modules, including either motion pictures expert group (MPEG) media transport protocol (MMTP) signalingmodule 214 or real-time object delivery over unidirectional transport (ROUTE) signalingmodule 216 for delivering non-real time (NRT)content 218 that is accessible to theapplication layer 204. NRT content may include but is not limited to stored replacement advertisements. - On the broadband (OTT or computer network) side, when implemented by a receiver the
presentation layer 206 can include one or more dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) player/decoders 220 for decoding and playing audio-video content from the Internet. To this end theDASH player 220 may access a broadband side EME/CENC module 222. The DASH content may be provided asDASH segments 224 in ISO/BMFF format. - As was the case for the broadcast side, the broadband side of the
presentation layer 206 may include NRT content infiles 226 and may also include signalingobjects 228 for providing play back signaling. - Below the
presentation layer 206 in the protocol stack is asession layer 230. Thesession layer 230 includes, on the broadcast side, eitherMMTP protocol 232 orROUTE protocol 234. - On the broadband side the
session layer 230 includesHTTP protocol 236 which may be implemented as HTTP-secure (HTTP(S). The broadcast side of thesession layer 230 also may employ aHTTP proxy module 238 and a service list table (SLT) 240. TheSLT 240 includes a table of signaling information which is used to build a basic service listing and provide bootstrap discovery of the broadcast content. Media presentation descriptions (MPD) are included in the “ROUTE Signaling” tables delivered over user datagram protocol (UDP) by the ROUTE transport protocol. - A
transport layer 242 is below thesession layer 230 in the protocol stack for establishing low-latency and loss-tolerating connections. On the broadcast side thetransport layer 242 uses (UDP 244 and on the broadband side transmission control protocol (TCP) 246. - The example non-limiting protocol stack shown in
FIG. 2 also includes anetwork layer 248 below thetransport layer 242. Thenetwork layer 248 uses Internet protocol (IP) on both sides for IP packet communication, with multicast delivery being typical on the broadcast side and unicast being typical on the broadband side. - Below the
network layer 248 is thephysical layer 250 which includes broadcast transmission/receiveequipment 252 and computer network interface(s) 254 for communicating on the respective physical media associated with the two sides. Thephysical layer 250 converts Internet Protocol (IP) packets to be suitable to be transported over the relevant medium and may add forward error correction functionality to enable error correction at the receiver as well as contain modulation and demodulation modules to incorporate modulation and demodulation functionalities. This converts bits into symbols for long distance transmission as well as to increase bandwidth efficiency. On the OTA side thephysical layer 250 typically includes a wireless broadcast transmitter to broadcast data wirelessly using orthogonal frequency division multiplexing (OFDM) while on the OTT side thephysical layer 250 includes computer transmission components to send data over the Internet. - A DASH Industry Forum (DASH-IF) profile sent through the various protocols (HTTP/TCP/IP) in the protocol stack may be used on the broadband side. Media files in the DASH-IF profile based on the ISO BMFF may be used as the delivery, media encapsulation and synchronization format for both broadcast and broadband delivery.
- Each
receiver 14 typically includes a protocol stack that is complementary to that of the broadcaster equipment. - A
receiver 14 inFIG. 1 may include, as shown inFIG. 2 , an Internet-enabled TV with an ATSC 3.0 TV tuner (equivalently, set top box controlling a TV) 256. Thereceiver 14 may be an Android®-based system. Thereceiver 14 alternatively may be implemented by a computerized Internet enabled (“smart”) telephone, a tablet computer, a notebook computer, a wearable computerized device, and so on. Regardless, it is to be understood that thereceiver 14 and/or other computers described herein is configured to undertake present principles (e.g. communicate with other devices to undertake present principles, execute the logic described herein, and perform any other functions and/or operations described herein). - Accordingly, to undertake such principles the
receiver 14 can be established by some or all of the components shown inFIG. 1 . For example, thereceiver 14 can include one ormore displays 258 that may be implemented by a high definition or ultra-high definition “4K” or higher flat screen and that may or may not be touch-enabled for receiving user input signals via touches on the display. Thereceiver 14 may also include one ormore speakers 260 for outputting audio in accordance with present principles, and at least oneadditional input device 262 such as, e.g., an audio receiver/microphone for, e.g., entering audible commands to thereceiver 14 to control thereceiver 14. Theexample receiver 14 may further include one ormore network interfaces 264 for communication over at least one network such as the Internet, a WAN, a LAN, a PAN etc. under control of one ormore processors 266. Thus, theinterface 264 may be, without limitation, a Wi-Fi transceiver, which is an example of a wireless computer network interface, such as but not limited to a mesh network transceiver. Theinterface 264 may be, without limitation, a Bluetooth® transceiver, Zigbee® transceiver, Infrared Data Association (IrDA) transceiver, Wireless USB transceiver, wired USB, wired LAN, Powerline or Multimedia over Coax Alliance (MoCA). It is to be understood that theprocessor 266 controls thereceiver 14 to undertake present principles, including the other elements of thereceiver 14 described herein such as, for instance, controlling thedisplay 258 to present images thereon and receiving input therefrom. Furthermore, note thenetwork interface 264 may be, e.g., a wired or wireless modem or router, or other appropriate interface such as, e.g., a wireless telephony transceiver, or Wi-Fi transceiver as mentioned above, etc. - In addition to the foregoing, the
receiver 14 may also include one ormore input ports 268 such as a high definition multimedia interface (HDMI) port or a USB port to physically connect (using a wired connection) to another CE device and/or a headphone port to connect headphones to thereceiver 14 for presentation of audio from thereceiver 14 to a user through the headphones. For example, theinput port 268 may be connected via wire or wirelessly to a cable or satellite source of audio video content. Thus, the source may be a separate or integrated set top box, or a satellite receiver. Or, the source may be a game console or disk player. - The
receiver 14 may further include one ormore computer memories 270 such as disk-based or solid-state storage that are not transitory signals, in some cases embodied in the chassis of the receiver as standalone devices or as a personal video recording device (PVR) or video disk player either internal or external to the chassis of the receiver for playing back audio video (AV) programs or as removable memory media. Also, in some embodiments, thereceiver 14 can include a position orlocation receiver 272 such as but not limited to a cellphone receiver, global positioning satellite (GPS) receiver, and/or altimeter that is configured to e.g. receive geographic position information from at least one satellite or cellphone tower and provide the information to theprocessor 266 and/or determine an altitude at which thereceiver 14 is disposed in conjunction with theprocessor 266. However, it is to be understood that that another suitable position receiver other than a cellphone receiver, GPS receiver and/or altimeter may be used in accordance with present principles to determine the location of thereceiver 14 in e.g. all three dimensions. - Continuing the description of the
receiver 14, in some embodiments thereceiver 14 may include one ormore cameras 274 that may include one or more of a thermal imaging camera, a digital camera such as a webcam, and/or a camera integrated into thereceiver 14 and controllable by theprocessor 266 to gather pictures/images and/or video in accordance with present principles. Also included on thereceiver 14 may be aBluetooth® transceiver 276 or other Near Field Communication (NFC) element for communication with other devices using Bluetooth® and/or NFC technology, respectively. An example NFC element can be a radio frequency identification (RFID) element. - Further still, the
receiver 14 may include one or more auxiliary sensors 278 (such as a motion sensor such as an accelerometer, gyroscope, cyclometer, or a magnetic sensor and combinations thereof), an infrared (IR) sensor for receiving IR commands from a remote control, an optical sensor, a speed and/or cadence sensor, a gesture sensor (for sensing gesture commands) and so on providing input to theprocessor 266. AnIR sensor 280 may be provided to receive commands from a wireless remote control. A battery (not shown) may be provided for powering thereceiver 14. - The
companion device 16 may incorporate some or all of the elements shown in relation to thereceiver 14 described above. - The methods described herein may be implemented as software instructions executed by a processor, suitably configured application specific integrated circuits (ASIC) or field programmable gate array (FPGA) modules, or any other convenient manner as would be appreciated by those skilled in those art. Where employed, the software instructions may be embodied in a non-transitory device such as a CD ROM or Flash drive. The software code instructions may alternatively be embodied in a transitory arrangement such as a radio or optical signal, or via a download over the Internet.
- Now referring to
FIG. 3 , theOTA 12 and/orOTT 22 assembly may, for at least some and preferably most or all of thereceivers 14 in the digital television system, enter an emergency alert (also referred to herein as a reverse 911) routine atblock 300 in which, atblock 302, for each receiver the location of the receiver is identified, as well as certain user information of the receiver. The location of the receiver may be identified by causing the receiver to send its GPS location information to the digital television system. Or, the location may be manually input by a user. Or, the location may be obtained in other ways, such as by having the receiver triangulate its location using signals from multiple transmitters in the digital television system or in another system such as base stations in a wireless telephony network in the event that the receiver has a wireless telephony transceiver. - The user information, which may include demographic information, a cell phone number, and information pertaining to special needs of people in the home in which the receiver is located may be obtained from the purchaser of the receiver at the point of sale. Or, the cell phone number to be associated with the receiver for use described further below may be looked up by the broadcaster using a database that correlates locations (in this case, the address corresponding to the location of the receiver) with cell phone numbers. Yet again, the user information may be input to the receiver by a user as described below in connection with
FIG. 5 . Other techniques to gather the user information. - Proceeding to block 304, in the event of an emergency alert situation such as an approaching storm, detected possible earthquake, or other situations, an emergency alert is generated by the digital television broadcaster and tailored for at least some of the
receivers 14 in the system using the respective location and user information of each receiver. Thus, afirst receiver 14 presents first information in the emergency alert and asecond receiver 14 presents second information in the emergency alert different from the first information. Some information presented on one receiver is thus not presented on the other, and vice-versa. - Or, the first receiver may use the information directly to contact the second receiver to determine user presence. Once user location is determined, appropriate action can automatically take place whether finding evacuation routes, hotel reservations, etc. are to be made available.
- Examples of tailoring this information include but are not limited to an amount of time before a threat subject of the emergency alert is life threatening at the receiver location, directions to a shelter nearest the receiver location, and an automatic booking of a user into a hotel nearest the receiver location along with a notification thereof.
- In the event of a possibility that no one is viewing the receiver to detect the emergency alert as might be indicated by, e.g., lack of an acknowledgement input to the receiver within a period of time following broadcast of the alert, the logic may move to block 306. At
block 306 the phone number associated with the receiver as obtained atblock 302 may be called with a recorded audible alert that may contain some or all of the information discussed herein in audible form. -
FIG. 4 illustrates further. AUI 400 may be presented on a display of the receiver as shown in which anidentification 402 of the nature of the alert is resented, in the example shown, a tornado. If the name of a user associated with the receiver is known, the name may appear in thealert 402. - In examples, an
advisory 404 may be presented indicating a future time at which the event that is subject to the alert is expected to become life threatening at the location of the receiver. For example, the advisory 404 may indicate that the tornado will arrive in one hour. Similar advisories may be presented for emergencies such as wildfires, etc. - Also, an
advisory 406 may be presented indicating the location of nearest shelter to the location of the receiver that people can seek. This location may be obtained using a database of shelters and their locations and then selecting the shelter closest to the location of the receiver. In some cases, the closest shelter may not be designated as “safe” for the particular emergency, such as a tornado, in which case the indicated shelter is the closest safe (e.g., tornado-hardened) shelter to the receiver. Aselector 408 may be presented and may be selectable using, e.g., a remote control (RC) to cause the display to present a map showing the route from the receiver location to the shelter. - Also, the emergency alert system may access a database of lodgings and automatically book a room at a lodging nearby the location of the receiver at the closest location determined to be safe from the emergency, and a
notification 410 of this may be presented on the display. Anacknowledgement selector 412 may be presented and may be selectable using, e.g., the RC to enable a viewer of the receiver to transmit an acknowledgement of having seen theUI 400 to the digital television system so that the system can dispense with the phone call atblock 306 ofFIG. 3 . -
FIG. 5 illustrates aUI 500 that may be presented on the receiver display to enable gathering the user information discussed above in relation to block 302 inFIG. 3 . An advisory 502 may be presented indicating the location of the receiver as best identified by the digital television using example techniques described herein. When the receiver reports its location in terms of GPS coordinates or triangulated latitude and longitude coordinates, the digital television system may access a map to correlate the location to a street address as indicated inFIG. 5 , which typically is more understandable to the user. - A
selector 504 may be presented for the user to confirm the location shown at 502. If the location is incorrect the user may input the correct address in a filed 506. Similarly, the user's phone number to be called in the event that block 306 inFIG. 3 requires execution may be presented at 508, and the user may confirm this number by selecting aconfirm selector 510. If the number is incorrect the user may input the correct number in afield 512. The user may input any special needs of persons in the household atblock 514, e.g., that one of the occupants of the location is blind, or elderly, etc. -
FIG. 6 illustrates aUI 600 that may be presented on a receiver such as an ATSC 3.0 TV. TheUI 600 may present alist 602 of events that a user can select to be notified of. - This may be implemented using filter codes as described in ATSC standard “Signaling, Delivery, Synchronization, and Error Protection (A/331)” that can be set up to use content codes such as entertainment identification registry (EIDR) codes which trigger what content is available to consumers. The filter codes, as indicated in the non-limiting example of
FIG. 6 , may include amber alerts, school closings, traffic hazards, tornados, inclement weather, fires, etc. - Present principles recognize that in emergencies, panic is a natural reaction and so it would be advantageous to use an ATSC 3.0 receiver to help remove panic or anxiety so that people can remain calm and focus on what needs to be done.
FIG. 7 provides illustration. - Commencing at
block 700, a receiver in response to an emergency alert (either pre-programmed or based on receiving an alert selected from, e.g.,FIG. 6 ) automatically may search for nearby hotel rooms for the user and may automatically secure a booking into an available room. Also, atblock 702 the receiver may automatically send an electronic or telephonic or other message to an emergency authority such as the local constabulary indicating the location of one or more users as indicated by, e.g., motion detectors in the dwelling in which the receiver is located, face recognition based on time-stamped images rendered by a camera on the receiver, etc. As another example, upon receipt of an emergency alert the receiver, knowing the phone number(s) as may be input usingFIG. 5 , may “ping” the mobile device(s) of the user(s) for a location report, and relay the location(s) to the emergency authority. -
Block 704 indicates that the receiver may obtain evacuation maps in response to an emergency alert and send the map(s) to the mobile device(s) or use artificial intelligence to inform users with advanced warning of coming danger. The alerts can be sent to other devices (phones) the user has setup/informed to the ATSC 3.0 receiver allowing information to flow even if the user is not in the immediate area (such as on vacation).Block 706 indicates that the receiver further may prompt a user to check on others, such as neighbors, to check on safety or other matters, and to obtain additional information, e.g., by presenting a link the user can select for additional information. - In a non-limiting example ATSC:A/331:2019 section A.3.3.2.3 filter codes are used in extensions to fast data transfer (FDT)-Instance elements along with the broadcaster emergency information to trigger a process (including AI) of taking next steps for consumer safety. Existing online services and user data may be used to provide options for a consumer as he faces emergencies.
- It will be appreciated that whilst present principals have been described with reference to some example embodiments, these are not intended to be limiting, and that various alternative arrangements may be used to implement the subject matter claimed herein.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/795,352 US20210258655A1 (en) | 2020-02-19 | 2020-02-19 | Personalized emergency alert |
US18/048,676 US20230179835A1 (en) | 2020-02-19 | 2022-10-21 | Personalized emergency alert |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/795,352 US20210258655A1 (en) | 2020-02-19 | 2020-02-19 | Personalized emergency alert |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/048,676 Continuation US20230179835A1 (en) | 2020-02-19 | 2022-10-21 | Personalized emergency alert |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210258655A1 true US20210258655A1 (en) | 2021-08-19 |
Family
ID=77273197
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/795,352 Abandoned US20210258655A1 (en) | 2020-02-19 | 2020-02-19 | Personalized emergency alert |
US18/048,676 Pending US20230179835A1 (en) | 2020-02-19 | 2022-10-21 | Personalized emergency alert |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/048,676 Pending US20230179835A1 (en) | 2020-02-19 | 2022-10-21 | Personalized emergency alert |
Country Status (1)
Country | Link |
---|---|
US (2) | US20210258655A1 (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009069999A (en) * | 2007-09-11 | 2009-04-02 | Jfe Systems Inc | Facility reservation apparatus |
US20100218209A1 (en) * | 2005-06-21 | 2010-08-26 | Scott Allan Kendall | Apparatus having an emergency alert function that facilitates location selection |
US20150032484A1 (en) * | 2013-07-23 | 2015-01-29 | Yakov Z. Mermelstein | Method for making reservations |
US20150149220A1 (en) * | 2013-11-26 | 2015-05-28 | Verizon Patent And Licensing Inc. | Methods and Procedures for a Travel Assistance Platform |
US20150256902A1 (en) * | 2014-03-07 | 2015-09-10 | Verizon Patent And Licensing Inc. | Common distribution and rendering for emergency alert services |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8898697B2 (en) * | 2008-12-08 | 2014-11-25 | At&T Intellectual Property I, Lp | Emergency alert representation |
WO2018016295A1 (en) * | 2016-07-20 | 2018-01-25 | ソニー株式会社 | Receiving device and data processing method |
-
2020
- 2020-02-19 US US16/795,352 patent/US20210258655A1/en not_active Abandoned
-
2022
- 2022-10-21 US US18/048,676 patent/US20230179835A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100218209A1 (en) * | 2005-06-21 | 2010-08-26 | Scott Allan Kendall | Apparatus having an emergency alert function that facilitates location selection |
JP2009069999A (en) * | 2007-09-11 | 2009-04-02 | Jfe Systems Inc | Facility reservation apparatus |
US20150032484A1 (en) * | 2013-07-23 | 2015-01-29 | Yakov Z. Mermelstein | Method for making reservations |
US20150149220A1 (en) * | 2013-11-26 | 2015-05-28 | Verizon Patent And Licensing Inc. | Methods and Procedures for a Travel Assistance Platform |
US20150256902A1 (en) * | 2014-03-07 | 2015-09-10 | Verizon Patent And Licensing Inc. | Common distribution and rendering for emergency alert services |
Also Published As
Publication number | Publication date |
---|---|
US20230179835A1 (en) | 2023-06-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9832539B2 (en) | Method and apparatus for communicating emergency information | |
US8898697B2 (en) | Emergency alert representation | |
US20170272837A1 (en) | System and method for providing location-dependent emergency alert services | |
WO2017038494A1 (en) | Communication device and data processing method | |
JP2024506459A (en) | ATSC 3.0 Long Term Error Correction with Fast Channel Change for Real-Time Broadcast Mobile Applications | |
US20230179835A1 (en) | Personalized emergency alert | |
US20220094992A1 (en) | Atsc 3.0 hospitality tv system | |
US11190835B2 (en) | Intelligent unload of broadcaster application on channel change | |
US11812083B2 (en) | Techniques for pushing personalized storefront ads using digital TV | |
US11818414B2 (en) | Telepresence through OTA VR broadcast streams | |
US20220124401A1 (en) | Digital signage using atsc 3.0 | |
KR20160008336A (en) | Broadcasting system using the mobile device | |
US11763666B1 (en) | System and method for delivering emergency alerts | |
US11606528B2 (en) | Advanced television systems committee (ATSC) 3.0 latency-free display of content attribute | |
US11838680B2 (en) | Techniques for ATSC 3.0 broadcast boundary area management using complete service reception during scan to determine signal quality of frequencies carrying the duplicate service | |
US11553230B2 (en) | Platform-independent USB driver communicating I2C commands to USB dongle through JAVA application | |
US20240107111A1 (en) | Digital tv reception using ott backchannel communication | |
US11601707B2 (en) | Techniques for ATSC 3.0 broadcast boundary area management using plural tuners | |
US11848716B2 (en) | Techniques for ATSC 3.0 broadcast boundary area management using signal quality and packet errors to differentiate between duplicated services on different frequencies during scan | |
US20210329348A1 (en) | Memory management in advanced television systems committee (atsc) 3.0 system | |
US11611792B2 (en) | ATSC 3 reception across boundary conditions using location data | |
WO2023012745A1 (en) | Telepresence through vr broadcast streams | |
US20220224962A1 (en) | Dongle to convert formats to atsc 3.0 low power wireless | |
US11647178B2 (en) | Digital television rendering verification | |
WO2021116839A1 (en) | Advanced television systems committee (atsc) 3.0 latency-free display of content attribute |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SONY CORPORATION, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FAY, LUKE;REEL/FRAME:051971/0710 Effective date: 20200220 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: SONY GROUP CORPORATION, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SONY CORPORATION;REEL/FRAME:066278/0190 Effective date: 20240126 |
|
AS | Assignment |
Owner name: SATURN LICENSING LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SONY GROUP CORPORATION;REEL/FRAME:066314/0103 Effective date: 20240131 |