CN116724554A - ATSC 3 application context switching and sharing - Google Patents

Abstract

Techniques for extending and/or improving the Advanced Television Systems Committee (ATSC) 3.0 television protocol in terms of robustly delivering next generation broadcast television services are described. When a switch is automatically made from presenting a service on a first frequency (306) to presenting a service on a second frequency (308), such as when the mobile receiver (300) is moving across a boundary region between two broadcasters (304), the current broadcaster application is notified (804/904/1000) and, depending on the context, can continue to execute (806) or send (906/1004) data to the new broadcaster application.

Description

ATSC 3 application context switching and sharing

Technical Field

The present application relates to technological advances that necessarily stem in computer technology and are directed to digital television, and more particularly, to Advanced Television Systems Committee (ATSC) 3.0.

Background

The Advanced Television Systems Committee (ATSC) 3.0 standard suite is a collection of more than ten industry technology standards for delivering next generation broadcast television as indicated in a/300. ATSC 3.0 supports delivery of a wide range of television services (including television video, interactive services, non-real-time delivery of data, and customized advertising) to a large number of receiving devices (from ultra-high definition televisions to wireless telephones). ATSC 3.0 also schedules coordination between broadcast content (referred to as "over the air") and related broadband delivery 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 easily incorporated without requiring any thorough modification of the relevant technology standards.

As understood herein, an ATSC 3.0 receiver scans for services included in a reception area containing two or more frequencies carrying the same or equivalent services, as may occur in a boundary area where broadcast signals from two regional ATSC 3.0 broadcaster stations overlap. These boundary regions exist in a multi-frequency network (MFN).

Disclosure of Invention

As further understood herein, when an ATSC 3.0 receiver is changing service (channel) from one channel with an associated broadcaster application to another, the receiver is expected to check to see if the new channel has the broadcaster application signaled and if present and the broadcaster application of the new channel has the same "context ID" or "application context ID" as the old channel, the original broadcaster application continues to run without interruption. However, without the present principles, the broadcaster application can only receive notifications of service changes due to user actions. Furthermore, when two broadcaster applications have different context ids (or have the same context id but different Uniform Resource Locators (URLs)) but are related applications (e.g., stations in a collaborative vicinity), an outgoing broadcaster application may want to send data to an incoming broadcaster application. Thus, while the ATSC a/344:2021 standard includes mechanisms for broadcasters to apply requests and receive notifications of service (channel) changes, this has significant limitations around context ids, user action initiated actions, and application URLs without the present principles. The present principles solve the following problems: coordination is performed between broadcaster applications when automated tuning is performed, such as when crossing border regions in a multi-frequency network (MFN), to promote a well-integrated viewer experience for both collaborative broadcasters in the same broadcast region and for collaborative broadcasters in neighboring broadcast regions.

Accordingly, in a digital television in which at least one receiver is capable of receiving broadcast signals from at least a first digital television broadcast component and a second digital television broadcast component, a method includes: the presentation of the first digital TV service is automatically switched from a first frequency (hand off) to a second frequency. In response to converting the presentation, the method includes: the method includes signaling to a first Broadcaster Application (BA) associated with a first frequency that a presentation is to be converted or is being converted, and selectively transmitting data associated with the first BA to a second BA associated with a second frequency.

In some embodiments, the method may include: it is identified whether a context ID associated with the first BA is the same as a context ID associated with the second BA. If desired, in response to the context IDs of the first BA and the second BA being the same, the method may include: the first BA is continued to be executed in the process of automatically switching the presentation of the first digital TV service from the first frequency to the second frequency.

In some implementations, a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the method includes: the first BA is switched from the first URL to the second URL in response to the context IDs of the first BA and the second BA being the same. In other implementations, a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the method includes: in response to the context IDs of the first BA and the second BA being the same, data associated with the first BA is sent to the second BA and the second BA is executed to present the first service.

In some implementations, the method includes: in response to the transition presentation, data associated with the first BA is sent to the second BA regardless of whether the context ID of the first BA is the same as the context ID of the second BA and regardless of whether the first BA and the second BA have a common Uniform Resource Locator (URL).

In an example implementation, the condition for changing the frequency includes the first tuner losing the first signal. In other example implementations, the condition for changing the frequency includes degradation of the first signal. In still other example implementations, the condition for changing the frequency includes a quality of the second signal exceeding a quality of the first signal.

Note that in some embodiments, the first BA may inform the receiver that data should be transferred to the second BA if this occurs, and then the first BA keeps the data up to date or calls APIs periodically to update the receiver what the data needs to be transferred is.

In another aspect, an apparatus includes: at least one receiver configured to: a first Digital Television (DTV) service is received on a first frequency, the first DTV service is presented on at least one audio video display device, and the first DTV service is received on a second frequency. The receiver is configured to: in response to at least one transition condition being met, switching from rendering the first DTV service received on the first frequency to rendering the first DTV service received on the second frequency, and signaling the switching to a first Broadcaster Application (BA) associated with the first frequency.

In another aspect, an apparatus includes: at least one receiver having at least one processor programmed with instructions to configure the processor to: a first Broadcaster Application (BA) is executed to present, on at least one Audio Video (AV) display device, a first service received on a first frequency. The first service includes at least one digital television service. The instructions are executable to: the method includes automatically switching from presenting a first service received on a first frequency to presenting a first service received on a second frequency associated with a second BA, and signaling the switching to the first BA.

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:

drawings

FIG. 1 illustrates an Advanced Television Systems Committee (ATSC) 3.0 system;

FIG. 2 illustrates components of the device shown in FIG. 1;

FIG. 3 illustrates an example particular system;

fig. 4 illustrates a first example embodiment of a digital TV receiver;

FIG. 5 illustrates a second exemplary embodiment of a digital TV receiver;

FIG. 6 illustrates example transmitter logic in an example flow chart format consistent with the present principles;

FIG. 7 illustrates example receiver logic in an example flow chart format consistent with the present principles; and is also provided with

Fig. 8-10 illustrate logic in accordance with techniques for broadcaster application signaling according to automatic conversion from fig. 7 in accordance with an example flowchart format consistent with the present principles.

Detailed Description

The present disclosure relates to technological advances in digital television, such as in Advanced Television Systems Committee (ATSC) 3.0 television. An example system herein may include an ATSC 3.0 source component and a client component that are connected via broadcast and/or over a network such that data may be exchanged between the client component and the ATSC 3.0 source component. The client component may include one or more computing devices including portable televisions (e.g., smart TVs, internet-enabled TVs), portable computers (such as laptops)Computers and tablet computers) and other mobile devices, including smartphones and additional examples discussed below. These client devices may operate with a variety of operating environments. For example, some client computers may employ an operating system from Microsoft or Unix operating system or an operating system produced by Apple Computer or Google (such as). 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 programs that may access websites hosted by Internet servers discussed below.

ATSC 3.0 publication a/344, which is incorporated herein by reference, may be particularly relevant to the techniques described herein.

The ATSC 3.0 source component may comprise a broadcast transmission component and server and/or gateway that may include one or more processors executing instructions that configure the source component to broadcast and/or transmit data over a network such as the internet. By, for example, sonySuch as a game console, personal computer, etc., to instantiate a client component and/or a local ATSC 3.0 source component.

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 and proxy agents, and other network infrastructure for reliability and security.

As used herein, instructions refer to computer-implemented steps for processing information in a system. The instructions may be implemented in software, firmware, or hardware and include any type of programmed steps performed by components of the system.

The processor may be a single-chip or multi-chip processor capable of executing logic through various lines, such as address lines, data lines, and control lines, as well as registers and shift registers.

Software modules described herein by way of flow charts and user interfaces may include various subroutines, procedures, and the like. Without limiting the disclosure, the logic stated as being executed by a particular module may be reassigned to other software modules and/or combined together in a single module and/or available in a shareable library. Although flow chart formats may be used, it should be understood that software may be implemented as a state machine or other logic method.

The present principles described herein may be implemented as hardware, software, firmware, or a combination thereof; thus, the illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality.

In addition to what has been mentioned above, logic blocks, modules, and circuits may 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 may be implemented as a combination of controllers or state machines or computing devices.

When implemented in software, the functions and methods described hereinafter may be written in a suitable language such as, but not limited to, hyperText markup language (HTML) -5,Javascript, c# or c++, and the functions and methods may 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 disk read-only memory (CD-ROM) or other optical disk storage such as Digital Versatile Disks (DVD), magnetic disk storage or other magnetic storage devices including removable thumb drives, and the like.The connection may establish a computer readable medium. By way of example, such connections may include hardwired cables including fiber optic and coaxial lines and Digital Subscriber Lines (DSL) and twisted pairs.

The 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 depicted in the figures may be combined, interchanged, or excluded from other embodiments.

The recitations of "having at least one of A, B and C" (likewise, "having at least one of A, B or C" and "having at least one of A, B, C") include a alone a, a alone B, a alone C, 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 apparatus" 10 and may include an over-the-air (OTA) apparatus 12 for broadcasting television data wirelessly, typically in a one-to-many relationship, via Orthogonal Frequency Division Multiplexing (OFDM) to a plurality of receivers 14, such as ATSC 3.0 television. One or more receivers 14 may be accessible byBluetooth low energy, other Near Field Communication (NFC) protocols, infrared (IR), etc. implemented short-range, typically wireless, links 18 communicate with one or more companion devices 16 such as remote controls, tablet computers, mobile telephones, etc.

Further, one or more receivers 14 may communicate with an over-the-top (OTT) device 22 of the broadcaster device 10 via a wired and/or wireless network link 20, such as the internet, typically in a one-to-one relationship. The OTA device 12 may be co-located with the OTT device 22 or both sides 12, 22 of the broadcaster device 10 may be remote from each other and may communicate with each other by suitable means. In any event, receiver 14 may receive an ATSC 3.0 television signal over the OTA by tuning to an ATSC 3.0 television channel and may also receive related content, including television, over the OTT (wideband). Note that the computerized devices described in all of the figures herein may include some or all of the components set forth for the various devices in fig. 1 and 2.

Referring now to FIG. 2, details of an example of the components shown in FIG. 1 can 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 in fig. 2 and appropriately modified for the broadcaster side, the broadcaster can send a 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)) and via wireless broadcasting (referred to herein as "broadcast" and "over the air" (OTA)). Fig. 2 also illustrates an example stack with hardware that can be implemented by the receiver.

According to the broadcaster device 10 disclosure of fig. 2, one or more processors 200 accessing one or more computer storage media 202 (such as any memory or storage device described herein) may be implemented to provide one or more software applications in a top application layer 204. The application layer 204 may include one or more software applications running in a runtime environment, written in, for example, HTML 5/Javascript. Applications in the application stack 204 may include, but are not limited to, a linear TV application, an interactive service application, a companion screen application, a personalization application, an emergency alert application, and a usage reporting application. Applications are typically implemented in software that represents elements of the viewer experience, including video encoding, audio encoding, and runtime environments. As an example, applications may be provided that enable a user to control conversations, use alternate tracks, control audio parameters (such as normalization and dynamic range), and so forth.

Below the application layer 204 is a presentation layer 206. On the broadcast (OTA) side, the presentation layer 206 includes a broadcast audio-video playback device called a Media Processing Unit (MPU) 208, which Media Processing Unit (MPU) 208, when implemented in a receiver, decodes and plays back the audio-video content of the wireless broadcast on one or more displays and speakers. The MPU 208 is configured to present an International organization for standardization (ISO) Base Media File Format (BMFF) data representation 210 and video with High Efficiency Video Coding (HEVC) of audio, for example, in dolby Audio compression (AC-4) format. ISO BMFF is a generic file structure for time-based media files that is divided into "segments" and represents metadata. Each file is essentially a collection of nested objects, each object having a type and a length. To facilitate decryption, the MPU 208 may access a broadcast side Encrypted Media Extension (EME)/Common Encryption (CENC) module 212.

Fig. 2 further illustrates: on the broadcast side, the presentation layer 206 may include signaling modules including a Moving Picture Experts Group (MPEG) media transport (MMT) protocol (MMTP) signaling module 214 or a real-time object delivery over unidirectional transport (ROUTE) signaling module 216 for delivering non-real-time (NRT) content 218 accessible to the application 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 may include one or more dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) players/decoders 220 for decoding and playing audio-video content from the internet. To this end, DASH player 220 may access broadband side EME/CENC module 222. DASH content may be provided as DASH segments 224 in ISO/BMFF format.

As in the case of the broadcast side, the broadband side of the presentation layer 206 may include NRT content in a file 226 and may also include a signaling object 228 for providing playback signaling.

Below the presentation layer 206 in the protocol stack is a session layer 230. On the broadcast side, the session layer 230 includes an MMT protocol 232 or ROUTE protocol 234. Note that the ATSC standard provides the option of using MPEG MMT for transmission, although it is not shown here.

On the broadband side, the session layer 230 includes the HTTP protocol 236, which may be implemented as secure HTTP (S)). The broadcast side of the session layer 230 may also employ an HTTP proxy module 238 and a Service List Table (SLT) 240. The SLT 240 includes a table of signaling information for establishing a basic service list and providing guided discovery of broadcast content. The Media Presentation Description (MPD) is included in a "ROUTE signaling" table delivered by the ROUTE transport protocol over User Datagram Protocol (UDP).

In the protocol stack, the transport layer 242 is below the session layer 230 for establishing low latency and loss tolerant connections. On the broadcast side, the transport layer 242 uses UDP 244, and on the broadband side, the transport layer 242 uses 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. Network layer 248 uses Internet Protocol (IP) on both sides for IP packet communications, with multicast delivery being typical on the broadcast side and unicast on the broadband side.

Below the network layer 248 is a physical layer 250, the physical layer 250 including broadcast transmitting/receiving means 252 and computer network interface(s) 254 for communicating over respective physical media associated with both sides. The physical layer 250 converts Internet Protocol (IP) packets to be suitable for transmission over the relevant medium and may add forward error correction functionality to enable error correction at the receiver and include modulation and demodulation modules to incorporate the modulation and demodulation functionality. This converts bits into symbols for long distance transmission and increases bandwidth efficiency. On the OTA side, the physical layer 250 typically includes a wireless broadcast transmitter to wirelessly broadcast data using Orthogonal Frequency Division Multiplexing (OFDM), while on the OTT side, the physical layer 250 includes a computer transmission component to transmit data over the internet.

DASH industry forum (DASH-IF) profiles sent over various protocols (HTTP/TCP/IP) in the protocol stack may be used on the broadband side. Media files in the ISO BMFF based DASH-IF profile may be used as delivery, media encapsulation and synchronization formats for both broadcast and broadband delivery.

Each receiver 14 typically includes a protocol stack that is complementary to the protocol stack of the broadcaster device.

As shown in fig. 2, the receiver 14 in fig. 1 may include an internet-enabled TV with an ATSC 3.0TV tuner (equivalently, a set top box that controls the TV) 256. The receiver 14 may be based onIs a system of (a). Alternatively, the receiver 14 may be Internet enabled by computerized means("smart") phones, tablet computers, notebook computers, wearable computerized devices, etc. Regardless, it should be understood that the receiver 14 and/or other computers described herein are configured to perform the present principles (e.g., communicate with other devices to perform the present principles, execute the logic described herein, and perform any other functions and/or operations described herein).

Thus, to perform such principles, the receiver 14 may be established by some or all of the components shown in fig. 1. For example, the receiver 14 may include one or more displays 258, the one or more displays 258 may be implemented as high-definition or ultra-high-definition "4K" or higher flat screens, and the one or more displays 258 may or may not be touch-enabled for receiving user input signals via touches on the displays. The receiver 14 may also include one or more speakers 260 for outputting audio in accordance with the present principles and at least one additional input device 262 (such as, for example, an audio receiver/microphone) for inputting audible commands to the receiver 14 to control the receiver 14. The example receiver 14 may also include one or more network interfaces 264 for communicating over at least one network (such as the internet, WAN, LAN, PAN, etc.) under the control of one or more processors 266. Thus, interface 264 may be, but is not limited to, a Wi-Fi transceiver, such as, but not limited to, a mesh network transceiver, as an example of a wireless computer network interface. Interface 264 may be, but is not limited toTransceiver, < - > on>Transceivers, infrared data association (IrDA) transceivers, wireless USB transceivers, wired USB, wired LAN, power line, or multimedia over coax alliance (MoCA). It should be appreciated that the processor 266 controls the receiver 14 to perform the present principles, including other elements of the receiver 14 described herein, such as, for example, controlling the display 258 to present an image on the display 258 and from thereAn input is received. Further, note that network interface 264 may be, for example, a wired or wireless modem or router or other suitable interface, such as, for example, a wireless telephone transceiver or Wi-Fi transceiver as described above, or the like.

In addition to the foregoing, 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 for physically connecting (using a wired connection) to another CE device and/or a headset port for connecting a headset to the receiver 14 to present audio from the receiver 14 to a user through the headset. For example, the input port 268 may be connected via a wire or wirelessly to a satellite source or cable of audiovisual 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 a disk player.

The receiver 14 may also include one or more computer memories 270, such as disk-based or solid state storage that is not a transitory signal, in some cases the one or more computer memories 270 are implemented as stand-alone devices in the chassis of the receiver, or as a personal video recording device (PVR) or video disk player inside or outside the chassis of the receiver for playback of Audio Video (AV) programs, or as a removable memory medium. Further, in some embodiments, the receiver 14 may include a positioning or location receiver 272, such as, but not limited to, a cellular telephone receiver, a Global Positioning Satellite (GPS) receiver, and/or an altimeter, the positioning or location receiver 272 being configured to receive geolocation information, for example, from at least one satellite or cellular telephone tower, and provide the information to the processor 266 and/or in conjunction with the processor 266 determine the altitude at which the receiver 14 is disposed. However, it should be understood that another suitable positioning receiver 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 position of the receiver 14, for example in all three dimensions.

Continuing with the description of the receiver 14, in some embodiments, the receiver 14 may include one or more cameras 274 that are one or more phasesThe machine 274 may include one or more of the following cameras: 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 capture pictures/images and/or video in accordance with the present principles. May also include on the receiver 14Transceiver 276 or other Near Field Communication (NFC) element for use with +.>And/or NFC technology with other devices. An example NFC element may be a Radio Frequency Identification (RFID) element.

Further, the receiver 14 may include one or more auxiliary sensors 278 (such as motion sensors, such as accelerometers, gyroscopes, gyrometers, or magnetic sensors and combinations thereof), infrared (IR) sensors for receiving IR commands from a remote control, optical sensors, speed and/or cadence sensors, gesture sensors (for sensing gesture commands), and the like, which provide inputs to the processor 266. An IR sensor 280 may be provided to receive commands from a wireless remote control. A battery (not shown) may be provided to power the receiver 14.

The companion device 16 may contain some or all of the elements shown with respect to the receiver 14 described above.

The methods described herein may be implemented as software instructions executed by a processor, as suitably configured Application Specific Integrated Circuits (ASICs) or Field Programmable Gate Array (FPGA) modules, or in any other convenient manner as will be appreciated by those skilled in the art. Where software instructions are employed, the software instructions may be implemented in a non-transitory device such as a CD ROM or flash drive. Alternatively, the software code instructions may be implemented in a transitory arrangement (such as a radio or optical signal) or via download over the internet.

Referring now to fig. 3, a simplified digital TV system, such as an ATSC 3.0 system, is shown. In fig. 3, a mobile or stationary digital TV receiver (such as ATSC 3.0 receiver 300), which may include any or all of the related components discussed above with respect to fig. 1 and 2, is located in a border region 302 between first and second ATSC 3.0 broadcast stations or components 304, signals from both broadcast stations 304 being picked up by the receiver 300 in region 302. A first ATSC 3.0 service ("service a") is broadcast from a first broadcast station 304 over a first frequency 306 and the same service a or equivalent service B is broadcast from a second broadcast station 304 over a second frequency 308 that is different from the first frequency 306. The receiver 300 picks up two frequencies, i.e., the receiver 300 picks up signals from two broadcasting stations 304.

Fig. 4 illustrates an example non-limiting embodiment of a digital TV receiver (such as ATSC 3.0 receiver 400) that may include any or all of the related components discussed above with respect to fig. 1 and 2. In the example shown, ATSC 3.0 receiver 400 may be a stationary receiver, such as a receiver located inside a home. In some examples, ATSC 3.0 receiver 400 may be a mobile receiver, for example, as implemented in a mobile phone or disposed in a moving vehicle.

The example ATSC 3.0 receiver 400 shown in fig. 4 includes a tuner 402, which tuner 402 transmits signals picked up by the tuner from one or more antennas 406 to a demodulator 404. In the example shown, receiver 400 includes one and only one tuner, one and only one demodulator, and one and only one antenna.

In contrast, fig. 5 illustrates an example non-limiting embodiment of a digital TV receiver (such as ATSC 3.0 receiver 500) that may include any or all of the related components discussed above with respect to fig. 1 and 2. In the example shown, ATSC 3.0 receiver 500 may be a mobile receiver, for example, as implemented in a mobile phone or disposed in a moving vehicle. In some examples, ATSC 3.0 receiver 500 may be a stationary receiver, such as a receiver located inside a home.

The example ATSC 3.0 receiver 500 shown in fig. 5 includes a plurality of tuners 502 that transmit signals picked up by the tuners from one or more antennas 506 to respective demodulators 504. In the non-limiting example shown, ATSC 3.0 receiver 500 has two tuners and two demodulators, it being understood that the receiver may have a greater or lesser number of tuners/demodulators. In the non-limiting example shown, ATSC 3.0 receiver 500 has four antennas, it being understood that the receiver may have a greater or lesser number of antennas. The receiver 500 may have the capability to switch the antenna inputs to the tuners such that a first tuner may receive signals from, for example, three antennas and a second tuner may receive signals from a fourth antenna, and then may switch to exchange antenna inputs between tuners. Two antennas may provide inputs to each respective tuner. All four antennas may provide inputs to a single tuner. These and other antenna-tuner configurations may be dynamically changed during operation as desired. The antenna may be moveable relative to the receiver.

Quality metrics of RF frequencies are discussed herein and may be identified and stored. Quality metrics may include, for example, signal-to-noise ratio (SNR) and error rate as may be represented by, for example, packet Error Number (PEN). The quality metric may include resolution, e.g., whether the service has High Definition (HD) or Standard Definition (SD). The quality metric may also include a bit rate and a form factor, recognizing that not all HD are identical. Quality metrics may include content attributes such as whether the service supports foreign language, accessibility signaling (e.g., where to sign), audio descriptions, and other content aspects. The quality metrics may include a location preference (such as a second region where the first region is stronger in channel, but all advertisements are preferred to the first region rather than the user so that duplicate services from the second region may be preferential to the first region). The quality metric may include a quality of a user interface carried in the service.

In a non-limiting example, during a scan, SNR can be determined by recording both the received signal strength of each received frequency and any accompanying noise on that frequency and determining the quotient thereof. The error rate may be determined, for example, by determining the percentage of packets lost (by recording the lost packet number) and/or by determining the percentage of received packets having errors therein as determined by an error correction algorithm.

Fig. 6 illustrates logic executable by a transmitter (such as an OTA transmitter or OTT transmitter) to transmit a service on one or more frequencies, including in the example of fig. 6 transmitting service "a" on frequency "a". Moving to block 602, the transmitter or another transmitter in the system also transmits ("signals") a list of services, such as services in a list of services table (SLT), and a corresponding RF frequency and one or more duplicate services on a different frequency.

Fig. 7 illustrates receiver logic consistent with the present principles. Beginning at block 700, a first service carried on a first frequency ("a") from a broadcaster is received and presented on an AV device. Proceeding to decision state 702, the receiver uses, for example, one or more of the quality metrics described herein to determine whether repeated, partial, equivalent, or preferred broadcasts of a first service received on a different frequency ("B") from a different transmitter, typically while traversing a boundary region, have a higher signal quality than the first frequency (a), and the receiver performs an automatic transition from rendering the first service from frequency a to rendering the service received on frequency B at block 704. Otherwise, the receiver continues to present content from the first frequency (a) at block 700.

Note that in an example implementation, the condition for changing the frequency may include the first tuner losing the first signal (frequency) entirely. In other example implementations, the condition for changing the frequency may include the first signal degradation being below a threshold. In still other example implementations, as discussed above, the condition for changing the frequency includes the quality of the second signal (frequency) exceeding the quality of the first signal (frequency).

Fig. 8-10 illustrate various conditional techniques for broadcaster application management according to automatic service switching from block 704 of fig. 7. A Broadcaster Application (BA) is typically downloaded from a broadcaster by an ATSC 3.0 receiver using ROUTE/DASH or MMT to perform various functions. The broadcaster application may include a downloaded series of interrelated documents that are intended to run in the application environment and perform one or more functions, such as providing interactivity or targeted ad insertion. The documents of the application may include, but are not limited to, HTML, javaScript, CSS, XML and multimedia files. The application may access other data that is not part of the application itself. The broadcaster application can distinguish itself from other applications by its ability to support localized interactivity without a broadband connection. BA refers to client-side functionality of a broader web application that provides interactive services. This distinction is made because the broadcaster only sends the client side document and code.

State 800 is formulated in a decision flow format, it being understood that state logic may likewise be used to indicate that fig. 8 is suitable for service transitions from block 704, wherein an existing (pre-transition) BA (broadcaster application "a" in fig. 8) has the same context ID as a new (post-transition) BA (broadcaster application "B" in fig. 8) when tuning from channel a to channel B is the result of an automated process. If this condition is not met, the logic of FIG. 8 terminates at state 802. However, if the condition at state 800 is met, the logic moves to block 804 to notify broadcaster application A that the service is changing. During and after the transition of the service to the new frequency, the broadcaster application a may continue to be executed at state 806 without interruption.

Note that the context ID is a unique Uniform Resource Identifier (URI) signaled in the broadcast and that the unique Uniform Resource Identifier (URI) determines which resources are provided by the receiver processor to the associated broadcaster application. The resource may be associated with multiple application context identifiers, but the BA is associated with only a single context ID. The context ID may be further specified in the HTML entry page location description (HELD) section of "Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0.0," DASH Industry Forum, "DASH-IF, which is incorporated by reference herein.

Fig. 9 illustrates another condition of automatic service conversion. Fig. 9 begins at state 900 and proceeds to block 902 in the second option or proceeds directly to decision diamond 904 in the first option ("option" means "embodiment"). At block 902, BA provisioning and/or update data associated with a first frequency a is passed to a second (alternative) BA associated with a second frequency B. From block 902 in the second option or directly from start state 900 in the first option, the logic moves to diamond 904 to determine whether the first BA and the second BA have been signaled to have both the same application context ID and the same Uniform Resource List (URL). If so, the logic ends at state 906 (essentially implying the logic of FIG. 8).

On the other hand, if the first BA and the second BA do not have the same context ID or do not have the same URL, logic in the first option (embodiment) flows to block 908 to inform the first BA associated with frequency a that the tuned frequency is changing. Moving to block 910, in this option, a response is received from the first BA, the response including data to be passed to the second BA (i.e., the BA of the new (second) frequency B).

From block 910 in the first option or directly from the negative result of the test at decision diamond 904 in the second option, the logic reaches state 912 to terminate the first BA and then initiates the second BA at state 914. At block 916, the application from the first BA is transferred to the second BA at block 916. The logic then ends at state 906.

Fig. 10 illustrates still another condition for managing BAs during an automatic service transition. At block 1000, when automatically tuning from one frequency carrying a service to another frequency carrying the same service as might occur, for example, when a mobile receiver is passing through a boundary region between two transmitters, an existing BA ("a") on the original frequency is notified of the impending transition. Moving to block 1002, the original BA ("a") is notified that it must or may (i.e., is forced or optional) provide data to a receiver, which then provides the data to a second frequency broadcaster application ("B") at block 1004. This process can be used regardless of whether the context ID of BA "a" is the same as the context ID of BA "B" and regardless of whether these BAs have the same URL as each other.

It should be understood that while the present principles have been described with reference to some example embodiments, these are not intended to be limiting and various alternative arrangements may be used to implement the subject matter claimed herein.

Claims (20)

1. In a digital television in which at least one receiver is capable of receiving broadcast signals from at least a first digital television broadcast component and a second digital television broadcast component, a method comprising:

automatically converting the presentation of the first digital TV service from the first frequency to the second frequency;

in response to converting the presentation, signaling to a first Broadcaster Application (BA) associated with the first frequency that the presentation is to be converted or is being converted; and

data associated with the first BA is selectively transmitted to a second BA associated with the second frequency.

2. The method according to claim 1, comprising: it is identified whether a context ID associated with the first BA is the same as a context ID associated with the second BA.

3. The method according to claim 2, comprising: in response to the context IDs of the first BA and the second BA being the same, the first BA continues to be executed in automatically transitioning presentation of the first digital TV service from the first frequency to the second frequency.

4. The method of claim 2, wherein a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the method comprises: the first BA is switched from the first URL to the second URL in response to the context IDs of the first BA and the second BA being the same.

5. The method of claim 2, wherein a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the method comprises: in response to the context IDs of the first BA and the second BA being the same, data associated with the first BA is sent to the second BA and the second BA is executed to present the first service.

6. The method according to claim 1, comprising: in response to the transition presentation, data associated with the first BA is sent to the second BA regardless of whether the context ID of the first BA is the same as the context ID of the second BA and regardless of whether the first BA and the second BA have a common Uniform Resource Locator (URL).

7. The method according to claim 1, comprising: in response to the loss of the first frequency, automatically converting the presentation of the first digital TV service from the first frequency to the second frequency.

8. The method according to claim 1, comprising: in response to the degradation of the first frequency, automatically converting the presentation of the first digital TV service from the first frequency to the second frequency.

9. The method according to claim 1, comprising: in response to the quality of the second frequency exceeding the quality of the first signal, automatically converting the presentation of the first digital TV service from the first frequency to the second frequency.

10. An apparatus, comprising:

at least one receiver configured to:

receiving a first Digital Television (DTV) service on a first frequency;

presenting a first DTV service on at least one audio video display device;

receiving a first DTV service on a second frequency;

switching from rendering the first DTV service received on the first frequency to rendering the first DTV service received on the second frequency in response to at least one transition condition being satisfied; and

the handover is signaled to a first Broadcaster Application (BA) associated with the first frequency.

11. The apparatus of claim 10, wherein the receiver is configured to:

data associated with the first BA is selectively transmitted to a second BA associated with the second frequency.

12. The apparatus of claim 11, wherein the receiver is configured to: it is identified whether a context ID associated with the first BA is the same as a context ID associated with the second BA.

13. The apparatus of claim 12, wherein the receiver is configured to: in response to the context IDs of the first BA and the second BA being the same, the first BA continues to be executed in automatically transitioning presentation of the first digital TV service from the first frequency to the second frequency.

14. The apparatus of claim 12, wherein a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the receiver is configured to: the first BA is switched from the first URL to the second URL in response to the context IDs of the first BA and the second BA being the same.

15. The apparatus of claim 12, wherein a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the receiver is configured to: in response to the context IDs of the first BA and the second BA being the same, data associated with the first BA is sent to the second BA and the second BA is executed to present the first service.

16. The apparatus of claim 10, wherein the receiver is configured to: in response to the transition presentation, data associated with the first BA is sent to a second BA associated with the second frequency regardless of whether the context ID of the first BA is the same as the context ID of the second BA and regardless of whether the first BA and the second BA have a common Uniform Resource Locator (URL).

17. An apparatus, comprising:

at least one receiver comprising at least one processor programmed with instructions to configure the processor to:

executing a first Broadcaster Application (BA) to present, on at least one Audio Video (AV) display device, a first service received on a first frequency, the first service comprising at least one digital television service;

automatically switching from rendering the first service received on the first frequency to rendering the first service received on a second frequency associated with the second BA; and

the handover is signaled to the first BA.

18. The apparatus of claim 17, wherein the instructions are executable to:

data associated with the first BA is selectively transmitted to the second BA.

19. The apparatus of claim 17, wherein a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the instructions are executable to: the first BA is switched from the first URL to the second URL in response to the context IDs of the first BA and the second BA being the same.

20. The apparatus of claim 17, wherein a first BA is associated with a first Unified Resource List (URL) and a second BA is associated with a second URL, and the instructions are executable to: in response to the context IDs of the first BA and the second BA being the same, data associated with the first BA is sent to the second BA and the second BA is executed to present the first service.