Improving Digital TV Reception Using OTT Backchannel Communications

Abstract

Techniques for extending and / or improving the Advanced Television Systems Committee (ATSC) 3.0 television protocol are described. In an ATSC 3.0 environment, receivers (300) (including consumer and professional receivers) have access to signal reception parameters and antenna coefficients. These reception parameters, along with time and location data, are transmitted (602) to one or more servers that maintain a database of reception characteristics. This data is analyzed (702) to identify a set of potentially receivable signals (based on reception parameters, time of day, location, geographic features, transmitter information, etc.). The receiver queries (604) the server, receives information indicating the set of potentially receivable signals, and reduces channel scan time by scanning only more receivable channels (606) or by scanning first (606). Additionally, difficult reception locations identified in the data collected by the server can be used collectively to guide RF improvements (e.g., adding SFN transmitters) (710). Furthermore, the data collected by the server can provide data used to provide "MFN" data (712).

Description

[Technical Field]

[0001] This application relates to technological advancements directed to digital television that are necessarily rooted in computer technology, and in particular to Advanced Television Systems Committee (ATSC) 3.0. [Background technology]

[0002] The Advanced Television Systems Committee (ATSC) 3.0 family of standards, outlined in A / 300, is a set of numerous industry technical standards for delivering next-generation broadcast television. ATSC 3.0 supports the delivery of a wide range of television services, including televised video, interactive services, non-real-time data delivery, and tailored advertising, to a variety of receiving devices, from ultra-high-definition televisions to wireless telephones. ATSC 3.0 also coordinates coordination between broadcast content (called "over the air," or OTA) and related broadband-delivered content and services (called "over the top," or OTT). ATSC 3.0 is designed to be flexible so that advancements can be easily incorporated as technology evolves without requiring a complete overhaul of any related technical standards. Summary of the Invention [Problem to be solved by the invention]

[0003] As understood herein, measuring RF reception details, collecting those details, and acting on them has typically been a manual process with limited data points. Extending this measurement to a large collection of consumer receivers (which report results) significantly adds to the available data. [Means for solving the problem]

[0004] Thus, in a digital television in which multiple receivers are capable of receiving broadcast signals from at least a first digital television broadcast assembly, a method includes receiving reception parameters for each of the broadcast channels from the multiple receivers, and also includes identifying potentially receivable channels using the reception parameters and assumptions (or user inputs) such as antenna gain, implementation loss, etc., and transmitting the identification of potentially receivable channels to at least some of the multiple receivers to enable the multiple receivers to reduce channel scanning time.

[0005] In some embodiments, the method may include using at least one of the receivers to scan only potentially receivable channels. Alternatively, the method may include using at least one of the receivers to scan potentially receivable channels and then to scan channels other than the potentially receivable channels. The method may include using at least one of the receivers to present at least one of the potentially receivable channels on at least one audio-video display device.

[0006] In some implementations, the receivers each include an Advanced Television Systems Committee (ATSC) 3.0 receiver.

[0007] Optionally, the method can include associating assumptions (or user inputs) such as receive parameters and antenna gain, implementation losses, etc. with the location and time at which the receive parameters were collected by each receiver, and potentially acceptable channels are identified based on the receive parameters, antenna coefficients, location, and time. In a non-limiting example, the method can include identifying hard-to-receive locations using the receive parameters and antenna coefficients, and transmitting the identification of the hard-to-receive locations to at least some of the multiple receivers.

[0008] In a non-limiting example, the method may include providing data derived from receive parameters and antenna coefficients to provide multi-frequency network (MFN) data.

[0009] In some embodiments, the method may include identifying potentially receivable channels at least in part using at least one machine learning (ML) model.

[0010] In another aspect, an apparatus includes at least one receiver configured to transmit at least one reception parameter and antenna coefficients associated with digital television broadcast reception, along with at least one location and at least one time, to at least one wide area computer network. The instructions are executable to receive from the wide area computer network at least one indication of at least one potentially receivable channel and to scan for digital television broadcast channels using the indication.

[0011] In another aspect, a digital television device includes at least one server having at least one processor programmed with instructions that configure the processor to receive reception parameters and antenna coefficients for each of the broadcast channels from a plurality of receivers, the instructions being executable to use the reception parameters and installation antenna coefficients to identify potentially receivable channels and to transmit the identification of the potentially receivable channels to at least some of the plurality of receivers to enable the plurality of receivers to reduce channel scanning time.

[0012] 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 elements and in which: [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 illustrates the Advanced Television Systems Committee (ATSC) 3.0 system. [Figure 2] FIG. 2 illustrates components of the device shown in FIG. 1. [Figure 3] FIG. 1 is a diagram illustrating a specific example of a system. [Figure 4] 1 is a diagram illustrating a first embodiment of a digital TV receiver. [Figure 5] FIG. 10 illustrates a second embodiment of a digital TV receiver. [Figure 6] FIG. 1 illustrates, in exemplary flow chart form, exemplary receiver logic in accordance with present principles; [Figure 7] FIG. 1 illustrates, in exemplary flow chart form, exemplary transmitter logic in accordance with present principles. DETAILED DESCRIPTION OF THE INVENTION

[0014] This disclosure relates to technological advances in digital television, such as Advanced Television Systems Committee (ATSC) 3.0 television. An exemplary system herein may include an ATSC 3.0 source component and a client component, connected via broadcast and / or network to enable data exchange between the client component and the ATSC 3.0 source component. The client component may include one or more computing devices, such as portable televisions (e.g., smart TVs, Internet-enabled TVs), portable computers, such as laptops and tablet computers, and smartphones and other mobile devices, including further examples described below. These client devices may operate in a variety of operating environments. For example, some client computers may employ operating systems such as Microsoft's operating system, Unix operating system, or Android® manufactured by Apple Computer, Inc. or Google, Inc., as examples. These operating environments may be used to execute one or more browsing programs, such as browsers created by Microsoft, Google, or Mozilla, or other browser programs capable of accessing websites hosted by Internet servers, as described below.

[0015] ATSC 3.0 Publication A / 344, which is incorporated herein by reference, may be particularly relevant to the techniques described herein.

[0016] An ATSC 3.0 source component may include a broadcast transmission component and a server and / or gateway, which may include one or more processors that execute instructions that configure the source component to broadcast and / or transmit data over a network such as the Internet. Examples of client components and / or local ATSC 3.0 source components include gaming consoles such as the Sony PlayStation®, personal computers, etc.

[0017] Information may be exchanged between the client and the server over a network. For this purpose and for security, the server and / or client may include firewalls, load balancers, temporary storage, proxies, and other network infrastructure to enhance reliability and security.

[0018] As used herein, instructions refer to computer-implemented steps for processing information within a system. Instructions may be implemented in software, firmware, or hardware and may include any type of program step performed by a component of the system.

[0019] The processor can be a single-chip or multi-chip processor capable of implementing logic through various lines such as address lines, data lines and control lines, as well as registers and shift registers.

[0020] The software modules illustrated by the flowcharts and user interfaces herein may include various subroutines, procedures, etc. Without limiting the disclosure, logic referred to as being performed by a particular module may be redistributed among other software modules and / or combined into a single module and / or made available in a shareable library. While a flowchart format may be used, it should be understood that the software may also be implemented as a state machine or other logical method.

[0021] The principles described herein may be implemented as hardware, software, firmware, or a combination thereof, and thus, example components, blocks, modules, circuits, and steps are described in terms of their functionality.

[0022] In addition to those suggested above, the logic blocks, modules, and circuits may be implemented or performed using general purpose processors, digital signal processors (DSPs), field programmable gate arrays (FPGAs) or other programmable logic devices such as application specific integrated circuits (ASICs), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may be implemented by a controller, a state machine, or a combination of computing devices.

[0023] The functions and methods described below, when implemented in software, can be written in any suitable 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 random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disk storage, such as a digital versatile disk (DVD), magnetic disk storage, or other magnetic storage devices, including removable universal serial bus (USB) thumb drives. A connection can constitute the computer-readable medium. Such connections can include wired cables, including, by way of example, optical fiber, coaxial cable, digital subscriber line (DSL), and twisted pair cable.

[0024] Components included in one embodiment may be used in other embodiments in any suitable combination. For example, any of the various components described herein and / or illustrated in the figures may be combined, substituted, or excluded from other embodiments.

[0025] The phrase "having at least one of A, B, and C (and similarly, "having at least one of A, B, or C" and "having at least one of A, B, and C")" includes A only, B only, C only, both A and B, both A and C, both B and C, and / or all of A, B, and C, etc.

[0026] The present principles can employ a variety of machine learning models, including deep learning models. Machine learning models according to the present principles can use a variety of algorithms trained using methods including supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, feature learning, self-learning, and other forms of learning. Examples of such algorithms that can be implemented by computer circuitry include one or more neural networks, such as convolutional neural networks (CNNs), recurrent neural networks (RNNs), and a type of RNN known as a long short-term memory (LSTM) network. Support vector machines (SVMs) and Bayesian networks can also be considered examples of machine learning models.

[0027] Thus, as understood herein, performing machine learning can involve accessing the training data and then training a model based on the training data so that the model can process further data and make inferences. Thus, an artificial neural network / artificial intelligence model trained through machine learning can include an input layer, an output layer, and multiple hidden layers therebetween that are configured and weighted to make inferences regarding the appropriate output.

[0028] 1, an example of an ATSC 3.0 source component is designated as "broadcaster equipment" 10 and may include over-the-air (OTA) equipment 12 that broadcasts television data wirelessly via orthogonal frequency division multiplexing (OFDM) to multiple receivers 14, such as ATSC 3.0 televisions, typically in a one-to-many relationship. The one or more receivers 14 may communicate with one or more companion devices 16, such as remote controls, tablet computers, and mobile phones, via short-range links 18, which are typically wireless and may be implemented by Bluetooth®, Bluetooth Low Energy, other near-field communication (NFC) protocols, infrared (IR), etc.

[0029] One or more of the receivers 14 may also communicate, typically in a one-to-one relationship, with over-the-top (OTT) equipment 22 of the broadcast facility 10 via wired and / or wireless network links 20, such as the Internet or a content distribution network (CDN). The OTA equipment 12 may be co-located with the OTT equipment 22, or both facilities 12, 22 of the broadcast facility 10 may be remotely located and communicate with each other through suitable means. In either case, the receiver 14 may receive ATSC 3.0 television signals over the air via tuned ATSC 3.0 television channels, or related content, including television, over the air (broadband). Note that the computer devices described in all figures herein may include some or all of the components shown for the various devices in FIGS. 1 and 2.

[0030]

[0013] Referring now to Figure 2, details of example components shown in Figure 1 can be seen. Figure 2 illustrates an example protocol stack that can be implemented using a combination of hardware and software. A broadcaster can transmit a hybrid service delivery that delivers one or more program elements over a computer network (referred to herein as "broadband" and "over the top" (OTT)) and over the air (referred to herein as "broadcast" and "over the air" (OTA)) using the ATSC 3.0 protocol stack, appropriately modified for the broadcaster side, shown in Figure 2. Figure 2 also illustrates an example stack, including hardware that can be embodied by a receiver.

[0031] 2 from the perspective of a broadcast station facility 10, one or more processors 200 accessing one or more computer storage media 202, such as any memory or storage described herein, can be implemented to provide one or more software applications at a top-level application layer 204. The application layer 204 can include one or more software applications written in, for example, HTML5 / Javascript, that operate in a runtime environment. Applications in the application stack 204 can include, but are not limited to, a linear TV application, an interactive services application, a companion screen application, a personalization application, an emergency alert application, and a usage reporting application. Typically, applications are embodied in software that represents elements of the viewer experience, including video coding, audio coding, and the runtime environment. As an example, applications can be provided that allow users to control dialogue, use alternate audio tracks, and control audio parameters such as normalization and dynamic range.

[0032] Below the application layer 204 is the presentation layer 206. The presentation layer 206 includes a broadcast audio-video playback device called a media processing unit (MPU) 208 on the over-the-air (OTA) side, which, when implemented in a receiver, decodes and plays wirelessly broadcast audio-video content on one or more displays and speakers. The MPU 208 is configured to present the International Organization for Standardization (ISO) Base Media File Format (BMFF) data representation 210 and video in High Efficiency Video Coding (HEVC) with audio in, for example, Dolby Audio Compression (AC-4) format. ISO BMFF is a generic file structure for time-based media files, divided into "segments" and presentation metadata. Essentially, each file is a set of nested objects, each with its own type and length. The MPU 208 has access to a broadcast-side encrypted media extension (EME) / common encryption (CENC) module 212 to facilitate decryption.

[0033] 2 further shows that on the broadcast side, the presentation layer 206 can include signaling modules, including either a Moving Picture Experts Group (MPEG) Media Transport Protocol (MMTP) signaling module 214 or a real-time object delivery over unidirectional transport (ROUTE) signaling module 216, to deliver non-real-time (NRT) content 218 accessible to the application layer 204. NRT content can include, but is not limited to, stored alternative advertisements.

[0034] 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) players / decoders 220 to decode and play audio-video content from the Internet. To this end, the DASH players 220 can access an EME / CENC module 222 on the broadband side. The DASH content can be provided as DASH segments 224 in ISO / BMFF format.

[0035] The broadband side of the presentation layer 206, like the broadcast side, may contain NRT content in files 226 and signaling objects 228 that provide playback signaling.

[0036] Below the presentation layer 206 in the protocol stack is the session layer 230, which includes either the MMTP protocol 232 or the ROUTE protocol 234 on the broadcast side. Note that the ATSC standard provides the option of using MPEG MMT for transmission, but this is not shown here.

[0037] The session layer 230 includes the HTTP protocol 236, which can be implemented on the broadband side as HTTP-secure (HTTP(S)). The broadband side of the session layer 230 may also employ an HTTP proxy module 238 and a service list table (SLT) 240. The SLT 240 contains a table of signaling information used to build a basic service list and provide bootstrap discovery of broadcast content. The "ROUTE signaling" table contains media presentation descriptions (MPDs) delivered over the User Datagram Protocol (UDP) by the ROUTE transport protocol.

[0038] Below the session layer 230 in the protocol stack is a transport layer 242 for establishing low-latency, loss-tolerant connections. The transport layer 242 uses User Datagram Protocol (UDP) 244 on the broadcast side and Transmission Control Protocol (TCP) 246 on the broadband side. The non-limiting example protocol stack shown in FIG. 2 also includes a network layer 248 below the transport layer 242. The network layer 248 uses the ATSC link layer protocol (ALP) to encapsulate Internet Protocol (IP) in multicast delivery, which is typical on the broadcast side and unicast delivery on the broadband side. Below the network layer 248 is a physical layer 250, which includes broadcast transmit / receive equipment 252 and computer network interface(s) 254 for communicating over the respective physical media associated with both sides. Note that the ATSC link layer protocol (ALP) allows for extensions to MPEG-2, IPv6, etc.

[0039] The physical layer 250 converts ATSC 3.0 Link Layer Protocol (ALP) packets, which are comprised of Internet Protocol (IP) packets, for transmission over the relevant medium, adding forward error correction to enable error correction at the receiver, and may include modulation and demodulation modules to incorporate modulation and demodulation functions. The physical layer 250 converts bits into symbols for long-distance transmission and improved bandwidth efficiency. The physical layer 250 typically includes a wireless broadcast transmitter on the OTA side that broadcasts data over the air using Orthogonal Frequency Division Multiplexing (OFDM), and a computer transmission component on the OTT side that transmits data over the Internet.

[0040] On the broadband side, the DASH Industry Forum (DASH-IF) profile can be used, transmitted over various protocols in the protocol stack (HTTP / TCP / IP). Media files in the DASH-IF profile, which is based on ISO BMFF, can be used as a distribution, media encapsulation, and synchronization format for both broadcast and broadband distribution.

[0041] Typically, each receiver 14 includes a protocol stack that is complementary to the protocol stack of the broadcast station equipment.

[0042] Receiver 14 of FIG. 1 may include an Internet-enabled TV with an ATSC 3.0 TV tuner 256 (equivalent to a set-top box that controls a TV), as shown in FIG. 2. Receiver 14 may be an Android®-based system. Alternatively, receiver 14 may be implemented by a computerized Internet-enabled (“smart”) phone, a tablet computer, a notebook computer, a wearable computing device, or the like. Nevertheless, it should be understood that receiver 14 and / or other computers described herein are configured to implement the present principles (e.g., to communicate with other devices to implement the present principles, to execute the logic described herein, and to perform any other functions and / or operations described herein).

[0043] Accordingly, receiver 14 may be established with some or all of the components shown in FIG. 1 to implement such principles. For example, receiver 14 may include one or more displays 258, which may or may not be implemented with high-definition or ultra-high-definition “4K” or higher flat screens and may be touch-enabled to receive user input signals via touch on the display. 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 an audio receiver / microphone, for inputting audible commands to receiver 14, e.g., to control receiver 14. An exemplary receiver 14 may further include one or more network interfaces 264 for communicating over at least one network, such as the Internet, a WAN, a LAN, or a PAN, under the control of one or more processors 266. Thus, interface 264 may be a Wi-Fi transceiver, which is an example of a wireless computer network interface, such as, but not limited to, a mesh network transceiver. Interface 264 can be, but is not limited to, a Bluetooth® transceiver, a Zigbee® transceiver, an Infrared Data Association (IrDA) transceiver, a wireless USB transceiver, a wired USB, a wired LAN, a powerline, or a Multimedia over Coax Alliance (MoCA). It should be understood that processor 266 controls receiver 14 to implement the present principles, including other elements of receiver 14 described herein, such as controlling display 258 to present images and receive input. Furthermore, network interface 264 can be, for example, a wired or wireless modem or router, or other suitable interface, such as a wireless telephone transceiver or Wi-Fi transceiver as described above.

[0044] In addition to the above, receiver 14 may also include one or more input ports 268, such as a High-Definition Multimedia Interface (HDMI®) port or a USB port, for physically connecting to another CE device (using a wired connection), and / or a headphone port for connecting headphones to receiver 14 to present audio from receiver 14 to a user through the headphones. For example, input port 268 may be connected via wire or wireless to a cable or satellite source of audio-video content. Thus, the source may be a separate or integrated set-top box or satellite receiver. Alternatively, the source may be a game console or disc player.

[0045] Receiver 14 may further include one or more computer memories 270, such as non-transitory, disk-based or solid-state storage, in some cases embodied as a stand-alone device within the receiver chassis, or as a personal video recorder (PVR) or video disc player for playing audio-video (AV) programs, or as removable storage media, either internal or external to the receiver chassis. Also, in some embodiments, receiver 14 may include a position or location receiver 272, such as, but not limited to, a cellular telephone receiver, a global positioning satellite (GPS) receiver, and / or an altimeter, configured to receive geographic location information, for example, from at least one satellite or cellular telephone tower, and provide this information to processor 266 and / or determine the altitude at which receiver 14 is located with processor 266. However, it should be understood that other suitable position receivers other than a cellular telephone receiver, a GPS receiver, and / or an altimeter may be used in accordance with the present principles to determine the location of receiver 14, for example, in all three dimensions.

[0046] Continuing with the description of receiver 14, in some embodiments, receiver 14 may include one or more cameras 274, which may include one or more of a thermal imaging camera, a digital camera such as a webcam, and / or a camera integrated into receiver 14 and controllable by processor 266, for collecting photographs / images and / or videos in accordance with the present principles. Receiver 14 may also include a Bluetooth® transceiver 276 or other near field communication (NFC) element for communicating with other devices using Bluetooth® and / or NFC technology, respectively. An exemplary NFC element may be a radio frequency identification (RFID) element.

[0047] Additionally, the receiver 14 may include one or more auxiliary sensors 278 (e.g., motion sensors such as accelerometers, gyroscopes, cyclometers, or magnetic sensors, and combinations thereof, infrared (IR) sensors for receiving IR commands from a remote control device, optical sensors, speed and / or cadence sensors, gesture sensors for detecting gesture commands, etc.) that provide input to the processor 266. An IR sensor 280 may also be provided for receiving commands from a wireless remote control. A battery (not shown) may also be provided to power the receiver 14.

[0048] Companion device 16 may include some or all of the elements shown in connection with receiver 14 above.

[0049] The methods described herein may be implemented as software instructions executed by a processor, a suitably configured application specific integrated circuit (ASIC) or field programmable gate array (FPGA) module, or any other convenient method as would be understood by one of ordinary skill in the art. The software instructions, if employed, may be embodied in a non-transitory device such as a CD-ROM or flash drive. Alternatively, the software code instructions may be embodied in a transitory configuration such as a radio or optical signal, or via download over the internet.

[0050] Referring now to Figure 3, a simplified, non-limiting example digital TV system, such as an ATSC 3.0 system, is shown in Figure 3. In Figure 3, a mobile or fixed digital TV receiver, such as an ATSC 3.0 receiver 300, which may include some or all of the associated components described above in connection with Figures 1 and 2, is located in a boundary region 302 between a first and second ATSC 3.0 broadcast station or assembly 304, with signals from both stations 304 being picked up by receiver 300 within region 302. However, the present principles are not limited to boundary regions.

[0051] A first broadcast station 304 broadcasts a first ATSC 3.0 service ("Service A") on a first frequency 306, while a second broadcast station 304 broadcasts the same Service A on a second frequency 308 that is different from the first frequency 306. The receiver 300 picks up both frequencies, i.e., the receiver 300 picks up signals from both broadcast stations 304.

[0052] Figure 4 illustrates a non-limiting example embodiment of a digital TV receiver, such as an ATSC 3.0 receiver 400, which may include some or all of the associated components described above in connection with Figures 1 and 2. In the illustrated example, the ATSC 3.0 receiver 400 may be a fixed receiver, such as a receiver located in a home. In some examples, the ATSC 3.0 receiver 400 may be a mobile receiver, such as implemented in a mobile phone or located in a moving vehicle.

[0053] 4 includes a tuner 402 that transmits signals picked up from one or more antennas 406 to a demodulator 404. In the illustrated example, receiver 400 includes only one tuner, only one demodulator, and only one antenna.

[0054] In contrast, Figure 5 illustrates a non-limiting example embodiment of a digital TV receiver, such as an ATSC 3.0 receiver 500, which may include some or all of the associated components described above in connection with Figures 1 and 2. In the illustrated example, the ATSC 3.0 receiver 500 may be a mobile receiver, such as mounted in a mobile phone or located in a mobile vehicle. In some examples, the ATSC 3.0 receiver 500 may be a fixed receiver, such as a receiver located in a home.

[0055] The exemplary ATSC 3.0 receiver 500 shown in FIG. 5 includes multiple tuners 502 that transmit signals picked up from one or more antennas 506 to respective demodulators 504. In the illustrated non-limiting example, the ATSC 3.0 receiver 500 has two tuners and two demodulators, although it should be understood that a greater or lesser number of tuners / demodulators is also possible. In the illustrated non-limiting example, the ATSC 3.0 receiver 500 has four antennas, although it should be understood that a greater or lesser number of antennas is also possible. The receiver 500 can switch antenna inputs to the tuners, such that a first tuner receives signals from, for example, three antennas, a second tuner receives signals from a fourth antenna, and then the antenna inputs are swapped between tuners. Two antennas can also provide inputs to each respective tuner. All four antennas can also provide inputs to a single tuner. These and other antenna-tuner configurations can be changed on the fly during operation as needed.

[0056] Quality metrics of RF frequencies are described herein, and such quality metrics can be identified and stored. Some quality metrics, along with antenna factors, can also be referred to as reception parameters. Quality metrics can include, for example, signal-to-noise ratio (SNR) and error rate, which can be expressed, for example, by packet error rate (PEN). Antenna factors can include antenna directivity (omnidirectional, directional gain), tuning band (UHF, VHF, low VHF), front-to-back ratio, style (e.g., 20-mile Yagi, 60-mile Yagi), installation type (attic, outdoor 30 feet above ground), average terrain level altitude, cable line loss, splitter insertion loss, etc. Quality metrics can include resolution, such as whether the service is high-definition (HD) or standard-definition (SD). Quality metrics can also include bit rate and form factor, recognizing that not all HD is the same. Quality metrics can include content attributes such as whether a service supports foreign languages, accessibility signaling (e.g., where the sign is located), audio descriptions, and other content aspects. Quality metrics can include locality preference (e.g., a channel in a first region is strong, but a duplicate service from a second region can be given preference over the first region because all the ads are for the first region and not the second region the user desires). Quality metrics can include the quality of the user interface featured in the service.

[0057] In a non-limiting example, the SNR can be determined during a scan by looking at both the received signal strength at each receive frequency and any associated antenna gain / noise at that frequency and taking the quotient thereof. The error rate can be determined, for example, by determining the percentage of packets that are lost (by looking at the lost packet number) and / or by determining the percentage of received packets that contain errors as determined by an error correction algorithm.

[0058] Parallel receiver / server logic is shown in Figures 6 and 7. In an ATSC 3.0 environment, signal reception parameters are available to receivers (including consumer and professional receivers). These reception parameters and antenna coefficients, along with time and location data for each collected receiver, are collected and recorded by the receiver in block 600 and transmitted to one or more servers in block 602, where the parameters are received in block 700 of Figure 7. The server maintains a database and / or summary of reception characteristics. This aggregate data can be analyzed manually or automatically in block 702 of Figure 7 to identify a set of potentially receivable signals (based on reception parameters, time of day, location, geographic features, transmitter information, etc.) in block 704 of Figure 7. In block 604 of Figure 6, the receiver sends a query to the server, and in block 706 of Figure 7, the server responds by transmitting information indicating the set of potentially receivable signals. In block 606 of Figure 6, each receiver can reduce channel scan time by scanning only the more receivable channels or by scanning first.

[0059] Also, in block 708 of Figure 7, hard-to-receive locations (including hard-to-receive channels by specific location and, optionally, by time of day) are identified in the data collected by the server. These identifications can be used collectively to guide RF improvements (e.g., adding Single Frequency Network (SFN) transmitters) in block 710 of Figure 7. These identifications can also be provided to the receiver, for example, to avoid channel scanning of hard-to-receive channels when the receiver is at the associated location.

[0060] Additionally, at block 712, the server may provide the collected data that is used to provide multi-frequency network (MFN) data.

[0061] The above can be implemented by an ATSC 3.0 receiver in the field that has a return path connection to a database (either an internet connection or over-the-top, e.g., via Wi-Fi and / or 5G cellular telephone networks), collects the received data, and periodically or immediately provides the data to one or more servers that collect the data.

[0062] The aggregated reception parameters and location / time data in the server database described above can also be used to predict a signal strength forecast using assumed antenna coefficients, as shown in block 714 of Figure 7. This forecast is sent to a third party in block 716 of Figure 7 to indicate to the consumer the expected services at the individual's location provided by the third party. An example of a third party provider is "Rabbit Ears."

[0063] A machine learning (ML) model can be applied to the aggregated reception parameter / location / time data described in Figures 6 and 7 to return potentially acceptable channels in block 706 and difficult reception locations in block 708. The ML model can be trained using ground truth including time, location, one or more reception parameters and antenna coefficients, and a tag indicating whether the parameter-location-time tuple represents a potentially acceptable channel for the associated area / time period, a difficult channel for the associated area / time period, or neutral with respect to potentially acceptable reception or difficult reception.

[0064] The ground truth may also include the location, course, and speed of multiple virtual receivers, as well as virtual receiver parameters actually measured at the locations by the test vehicle. The ground truth may also include an indication of the channel frequency.

[0065] While the present principles have been described with reference to certain example embodiments, it will be understood that these embodiments are not intended to be limiting and that the subject matter claimed herein may be implemented using a variety of alternative configurations. [Explanation of symbols]

[0066] 10 Broadcasting Station Equipment 12 Over-the-air (OTA) equipment 14 Receiver 16 Companion Devices 18 Links 20 Links 22 Over-the-top (OTT) equipment 200 processors 202 Storage medium 204 Application Layer 206 Presentation Layer 208 MPU 210 ISO BMFF Data Representation 212 EME / CENC module 214 MMT-specific signaling 216 ROUTE-specific signaling 218 NRT files 220 DASH Player / Decoder 222 EME / CENC module 224 DASH segments 226 NRT files 228 Signaling Objects 230 Session Layer 232 MMTP Protocol 234 ROUTE Protocol 236 HTTP Protocol 238 HTTP Proxy Module 240 Service List Table (SLT) 242 Transport Layer 244 User Datagram Protocol (UDP) 246 Transmission Control Protocol (TCP) 248 Network Layer 250 Physical layer 252 Broadcast transmitting / receiving equipment 254 Computer Network Interface 256 ATSC3.0 TV Tuner 258 display 260 speakers 262 Input Device 264 Network Interface 266 processors 268 input ports 270 memory 272 Position or location receivers 274 Camera 276 Bluetooth® transceiver 278 Auxiliary Sensor 280 IR sensor 300 ATSC 3.0 receiver 302 Boundary area 304 First and Second ATSC 3.0 Broadcast Stations or Assemblies 306 First Frequency 308 Second Frequency 400 ATSC3.0 receiver 402 Tuner 404 Demodulator 406 Antenna 500 ATSC 3.0 receiver 502 Tuner 504 Demodulator 506 Antenna 600 Collect received parameters 602 parameters along with time and location data are sent to the server(s). 604 Query server(s) for possible signals that can be received 606 Scan possible channels first, or only scan them 700 Receive parameter / position / time data from receiver 702 Aggregation 704 Identify potentially receivable signals for the area(s) 706 Response to receiver query 708 Identifying difficult reception locations Led 710 RF improvements (addition of SFN transmitters) 712 data to provide MFN data 714 SS Prediction 716 Provided to third parties

Claims

1. 1. A method, in a digital television in which a plurality of receivers are capable of receiving broadcast signals from at least a first digital television broadcast assembly, comprising: receiving reception parameters and antenna coefficients for each of the broadcast channels from the plurality of receivers; identifying potentially receivable channels using at least said reception parameters; transmitting identification of potentially receivable channels to at least some of the plurality of receivers to enable the plurality of receivers to reduce channel scanning time; A method comprising:

2. 2. The method of claim 1, including the step of using at least one of said receivers to scan only said potentially receivable channels.

3. 2. The method of claim 1, including using at least one of the receivers to scan the potentially receivable channels and then scan channels other than the potentially receivable channels.

4. 2. The method of claim 1, further comprising the step of using at least one of said receivers to present at least one of said potentially receivable channels on at least one audio-video display device.

5. 10. The method of claim 1, wherein each of the receivers comprises an Advanced Television Systems Committee (ATSC) 3.0 receiver.

6. 2. The method of claim 1, further comprising associating reception parameters and antenna coefficients with the location and time at which the reception parameters were collected by each receiver, and wherein the potentially receivable channels are identified based on the reception parameters, the location and the time.

7. identifying hard-to-receive locations using the reception parameters and antenna coefficients; transmitting an identification of the hard-to-receive location to at least some of the plurality of receivers; 2. The method of claim 1, comprising:

8. providing data derived from the received parameters to provide multi-frequency network (MFN) data; 2. The method of claim 1, comprising:

9. 10. The method of claim 1, comprising identifying the potentially receivable channels at least in part using at least one machine learning (ML) model.

10. 1. An apparatus comprising: at least one receiver, said receiver comprising: transmitting at least one reception parameter and at least one antenna coefficient associated with digital television broadcast reception, along with at least one location and at least one time, to at least one wide area computer network; receiving at least one indication of at least one potentially receivable channel from the wide area computer network; scanning digital television broadcast channels using said instructions; It is configured as follows: An apparatus characterized in that

11. 11. The apparatus of claim 10, wherein the instructions are executable to scan only those potential channels indicated by the wide area computer network that are receivable.

12. 11. The apparatus of claim 10, wherein the instructions are executable to scan for possible receivable channels indicated by the wide area computer network and then scan for channels other than the possible receivable channels.

13. 11. The apparatus of claim 10, wherein the instructions are executable to present the potentially receivable channels on at least one audio-video display device.

14. 11. The apparatus of claim 10, wherein the receiver comprises an Advanced Television Systems Committee (ATSC) 3.0 receiver.

15. The command is, receiving, from the wide area computer network, identification of hard-to-reach locations; performing a channel scan based at least in part on the hard-to-receive locations; 11. The device according to claim 10, characterized in that it is operable to:

16. A digital television device, at least one server including at least one processor programmed with instructions, said instructions causing said processor to: receiving reception parameters and antenna coefficients for each of the broadcast channels from a plurality of receivers; identifying potentially receivable channels using the receive parameters and antenna coefficients; transmitting identification of potentially receivable channels to at least some of the plurality of receivers to enable the plurality of receivers to reduce channel scanning time; Configure it as follows: A digital television device characterized by:

17. 17. The digital television apparatus of claim 16, wherein each of the receivers comprises an Advanced Television Systems Committee (ATSC) 3.0 receiver.

18. The instruction:

17. The digital television apparatus of claim 16, wherein the apparatus is operable to associate reception parameters and antenna coefficients with the location and time at which the reception parameters were collected by each receiver, and the potentially receivable channels are identified based on the reception parameters, location and time.

19. The instruction: identifying hard-to-receive locations using the reception parameters and antenna coefficients; transmitting an identification of the hard-to-receive location to at least some of the plurality of receivers; 17. The digital television apparatus according to claim 16, wherein the digital television apparatus is operable to:

20. The instruction: identifying the potentially receivable channels at least in part using at least one machine learning (ML) model; 17. The digital television apparatus according to claim 16, wherein the digital television apparatus is operable to:

Images