<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/reception" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Reception ]]></title>
                <link>https://www.tvtechnology.com/tag/reception</link>
        <description><![CDATA[ All the latest reception content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Tue, 26 May 2020 14:09:59 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Receiving ATSC 3.0 ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinion/receiving-atsc-30</link>
                                                                            <description>
                            <![CDATA[ How is ATSC 3.0 reception different than ATSC 1.0? ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">oZmd94yehmNtfciBArMaLQ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/3z26U23ciCfRRdXEXiGNRg-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 26 May 2020 14:09:59 +0000</pubDate>                                                                                                                                <updated>Tue, 26 May 2020 15:37:09 +0000</updated>
                                                                                                                                            <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Doug Lung ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/Nxdj8SBR4GjWpaZtzQbRu3.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/3z26U23ciCfRRdXEXiGNRg-1280-80.jpg">
                                                            <media:credit><![CDATA[iStock]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/3z26U23ciCfRRdXEXiGNRg-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>In my column last month (<a href="https://www.tvtechnology.com/opinion/get-ready-for-atsc-30-but-dont-ignore-10">“Get Ready for ATSC 3.0, But Don’t Ignore 1.0”</a>), I compared ATSC 1.0 and ATSC 3.0 reception. While it is being rolled out, ATSC 3.0 is likely to require similar antennas to those currently used for ATSC 1.0 since signal-to-noise requirements are likely to be the same. I received some email from readers who complained that even though they had sufficient signal strength for ATSC 1.0 reception, multipath was a problem, and they were looking to ATSC 3.0 to fix that. In this column, I’ll show how ATSC 3.0 handles multipath differently than ATSC 1.0 and also look at some other features in ATSC 3.0 that broadcasters can use to improve reception.</p><h2 id="multipath-and-speeding-trains">MULTIPATH AND SPEEDING TRAINS</h2><p>Multipath occurs when multiple copies of the same signal reach the receiver. These copies could be from other transmitters in a distributed transmission system (DTS) or, more likely today, from reflections from other objects. These objects include stationary objects like buildings and bridges and moving objects like trucks and airplanes. The impact of multipath on reception depends on the difference in time and the difference in signal level between the signals. </p><p>ATSC 1.0 is a single carrier transmission system. One 8VSB carrier has to carry the ATSC data rate of 19.392 Mbps. Multipath is visible on a spectrum analyzer as ripple (Fig. 1) in the 8VSB spectrum. By measuring the ripple it is possible to determine the time difference between the signals creating the multipath. (See my Jan. 1, 2000 article “<a href="https://www.tvtechnology.com/opinions/comparing-8vsb-and-cofdm-for-dtv-broadcasting">Comparing 8VSB and COFDM for DTV Broadcasting</a>” for details on how to do this. Fig. 1 is missing, but is the same as Fig. 1 here.)</p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:688px;"><p class="vanilla-image-block" style="padding-top:78.63%;"><img id="k4EjPrtxYmVPFZDeMeNp64" name="f-DOUG Fig 1-June 2020.jpg" alt="&nbsp;Fig. 1: 8VSB Multipath Spectrum&nbsp;" src="https://cdn.mos.cms.futurecdn.net/k4EjPrtxYmVPFZDeMeNp64.jpg" mos="" align="middle" fullscreen="1" width="688" height="541" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/k4EjPrtxYmVPFZDeMeNp64.jpg' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="caption-text"> Fig. 1: 8VSB Multipath Spectrum  </span><span class="credit" itemprop="copyrightHolder">(Image credit: Doug Lung)</span></figcaption></figure><p>ATSC 1.0 receivers deal with multipath using adaptive equalizers. In the simplest sense, an adaptive equalizer digitally stores copies of the incoming signal and shifts them in time to cancel out the multipath. As a result, the range of multipath delays and signal levels an ATSC 1.0 receiver can handle is dependent on how much the receiver manufacturer is willing to spend on the equalizer. The “coupon-eligible” DTV converter boxes sold during the analog-to-digital transition had to meet certain standards, but those do not apply to TV sets sold today. This variability in receiver performance makes ATSC 1.0 DTS design difficult. </p><p>With ATSC 3.0’s OFDM, multipath performance is controlled by the broadcaster. In OFDM, the data is divided among thousands of carriers so each carrier has to carry a much smaller amount of data. Multipath appears as interference between OFDM symbols; ATSC 3.0 handles multipath by inserting a guard interval between symbols. The guard interval (GI) is created in the time domain by taking samples belonging to the last part of the OFDM symbol and prepending them as a cyclic prefix to the original symbol. </p><p>This extra information allows the receiver to fill in the information lost due to multipath. ATSC 3.0 offers 12 selections of GI sample size. The relationship between the number of samples and the allowable time difference between multipath signals depends on the number of carriers as explained in my Jan. 1, 2000, article. </p><p>For a detailed explanation the cyclic prefix and how it works, look up “<a href="https://dspillustrations.com/pages/posts/misc/the-cyclic-prefix-cp-in-ofdm.html">The Cyclic Prefix for OFDM”</a> at dspillustrations.com. This website also offers a digital communications tutorial using a computer sound card for hands-on experience. Fig. 2, which shows how the cyclic prefix is generated, is from this website. </p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:1079px;"><p class="vanilla-image-block" style="padding-top:43.93%;"><img id="gPV7QWcx4RTSzUgma5VhA4" name="f-DOUG Fig2-June 2020.png" alt="&nbsp;Fig. 2: Creating a Cyclic Prefix in an OFDM Symbol" src="https://cdn.mos.cms.futurecdn.net/gPV7QWcx4RTSzUgma5VhA4.png" mos="" align="middle" fullscreen="1" width="1079" height="474" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/gPV7QWcx4RTSzUgma5VhA4.png' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="caption-text"> Fig. 2: Creating a Cyclic Prefix in an OFDM Symbol </span><span class="credit" itemprop="copyrightHolder">(Image credit: DSP Illustrations)</span></figcaption></figure><p>The use of OFDM in ATSC 3.0 doesn’t eliminate the need for an equalizer to remove distortion in the signal caused by multipath or frequency response variations in the receive system itself. The ATSC 3.0 standard has pilot carriers with known characteristics that can be inserted at regular and scattered intervals in frequency and time to make equalization easier. More pilot carriers will make it easier to lock on the channel with varying multipath. </p><p>Adding guard interval reduces usable symbol time and adding pilots reduces the number of carriers available for data. The optimum guard interval depends on the maximum multipath time difference. Testing of ATSC-MH (mobile-handheld) in the San Francisco area found a very long echo from the San Francisco-Oakland Bay Bridge caused reception problems in some areas—a long guard interval would fix that. When multiple transmitters are used in a DTS, the spacing of the transmitters and the signal overlap will determine the guard interval required. The ONEMedia App (see details later) will provide the guard “distance” for a given system configuration. </p><p>There is another element to multipath, which I did not mention earlier—Doppler. Doppler is the change in frequency as an object moves towards or away an observer, (as with a train whistle increasing in pitch as it approaches and decreasing as it moves away). 8VSB performance with Doppler was poor and varied by receiver, resulting in some viewers losing reception due to reflections from planes passing overhead.</p><p>Reflections with Doppler can cause loss of an OFDM signal as well, but the standard offers options to deal with it. Earlier, I mentioned OFDM divides the data among many carriers. The FFT size options are 8K, 16K and 32K, roughly corresponding to 6,900, 13,800 or 27,600 carriers. A larger FFT size is more efficient, but because the carriers are spaced closer together it will be more susceptible to Doppler. An 8K FFT is most robust, allowing mobile reception at any terrestrial speed likely to be found in private or public transportation, at least in the United States.</p><p>The impact of reflections, either as static multipath or as Doppler, once outside the range of the FFT or guard interval to handle it, is the same as noise. As a result, a robust signal with a lower SNR (signal-to-noise ratio) requirement will be less affected by multipath or Doppler. One way to take advantage of this is to use an FFT of 16K with LDM. While the robust LDM layer will experience more Doppler interference with the 16K FFT, if the required SNR is much lower, it can still work in many mobile environments while preserving the benefit of a 16K FFT for the enhanced layer.</p><h2 id="impulse-noise">IMPULSE NOISE</h2><p>One problem that has plagued ATSC 1.0 reception, especially at VHF, is impulse noise. ATSC 1.0 has a data interleaver to spread data over time to reduce the impact of brief signal loss, but that time is limited to a small fraction of a second. ATSC 3.0 has three time interleaver modes: None, Convolutional Time Interleaver (CTI) and Hybrid Time Interleaver (HTI). Extended Time Interleaving (ETI) is available for physical layer pipes (PLPs) using QPSK. </p><p>The length of the interleaving depends on how the ATSC 3.0 PLP is configured, and can be much larger than that available with ATSC 1.0. With so many options, it will likely take extensive field-testing at VHF (perhaps including low VHF) to determine what configurations work best. Using CTI and HTI should not impact data capacity, but the longer the time interleaving, the greater the latency. </p><p>ATSC 3.0 also includes a frequency interleaver, which would aid in reception in the event a single carrier or group of carriers was interfered with or otherwise lost. </p><figure class="van-image-figure " data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:1277px;"><p class="vanilla-image-block" style="padding-top:94.60%;"><img id="FYkYn5XN7cYNpsPBpd58F4" name="f-DOUG Fig3-June 2020.png" alt="&nbsp;Fig. 3: ONEMedia ATSC 3.0 Capacity Calculator Screens" src="https://cdn.mos.cms.futurecdn.net/FYkYn5XN7cYNpsPBpd58F4.png" mos="" align="middle" fullscreen="1" width="1277" height="1208" attribution="" endorsement="" class="expandable"><a href='https://cdn.mos.cms.futurecdn.net/FYkYn5XN7cYNpsPBpd58F4.png' target='_blank' class='expand-button icon-expand-image icon' ></a></p></div></div><figcaption itemprop="caption description" class=""><span class="caption-text"> Fig. 3: ONEMedia ATSC 3.0 Capacity Calculator Screens </span><span class="credit" itemprop="copyrightHolder">(Image credit: ONEMedia)</span></figcaption></figure><p>To learn more about the options available in ATSC 3.0, see ATSC Recommended Practice A/327, “<a href="https://www.atsc.org/atsc-documents/a-3272018-guidelines-for-the-physical-layer-protocol/">Guidelines for the Physical Layer Protocol</a>,” available from the ATSC web page under “Recommended Practices.” To play around with the options, ONE Media (the Sinclair company focused on ATSC 3.0), has created the app “NextGen TV Calculator” to determine channel capacity and performance of an ATSC 3.0 signal with different configurations, including guard interval. Visit <a href="https://onemediallc.com/" target="_blank">onemediallc.com</a> for IoS and Android download links. Fig. 3 shows a sample of the input and output from the ONE Media app on Android. The input and output data extends above and below what’s shown in the screenshot. The output, for example, includes final required SNR under Gauss, Rice and Rayleigh channels for the configured input.</p><p><em>I welcome your comments and questions on ATSC 1.0, ATSC 3.0 or broadcast RF technology in general. Email me at </em><a href="mailto:dlung@transmitter.com" target="_blank">dlung@transmitter.com</a>. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ The Repack’s Impact on Reception ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinions/the-repacks-impact-on-reception</link>
                                                                            <description>
                            <![CDATA[ This month I decided to take a break from talking about TV transmission to focus on TV reception. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">dYBe9hFfL5PBJtJ1NmaBBZ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/vepqQFDU2JBDJ7zMjE3dD6-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 28 Oct 2016 14:00:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Doug Lung ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/Nxdj8SBR4GjWpaZtzQbRu3.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/vepqQFDU2JBDJ7zMjE3dD6-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/vepqQFDU2JBDJ7zMjE3dD6-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>This month I decided to take a break from talking about TV transmission to focus on TV reception. I receive emails from non-engineers with questions about TV transmission and reception who happen to stumble upon my articles.</p><p>People are starting to realize the incentive auction and repack will impact viewers’ TV reception. This month I’ll explain the impact of the incentive auction, channel sharing and the repack on over-the-air TV reception.</p><p>Stations may sell their spectrum and go away, meaning the programming they carried may no longer be available. Stations may sell their spectrum and “channel share” with another station. These stations’ primary channels will be available on another channel, perhaps at reduced quality, but some multicast channels on either of the stations sharing the channel may disappear.</p><p>Viewers who watch TV via translators or over LPTV stations may find they are no longer available. Finally, during repacking, stations’ coverage may change, temporarily or permanently, making reception more difficult in some areas.</p><p>Will your favorite DTV program channel disappear after the incentive auction? In part, that will depend on that channel’s popularity and viewership. When talking about “channels,” it is easy to get confused. A station has only one RF channel (their spectrum), but may run several virtual program channels on it—28.1, 28.2, 28.3, 28.4. These are transmitted in the same spectrum, but each takes some of the data bandwidth.</p><p>While stations can’t discuss their auction plans during the FCC’s quiet period, the value of the spectrum versus the value of the programming will likely determine whether or not the program channel survives the auction.</p><p><strong>CHANNEL SHARING MISUNDERSTOOD</strong><br/></p><p>Stations can sell their spectrum, but retain their license, through channel sharing. This is probably the most misunderstood aspect of the incentive auction. First, stations are not, strictly speaking, sharing spectrum. The “sharee” station has no spectrum; the sharer has 6 MHz, one full channel. An ATSC DTV channel cannot be less than 6 MHz. It cannot be divided. What can be divided is the data rate transmitted on that channel—19.392 Mbps.</p><p><br/>Viewers watching two or more stations sharing a channel are likely to notice some reduction in picture quality. How noticeable it is will depend on the total number of program streams sharing one RF channel; how many of the program streams are in HD; the way the bits are allocated between program streams; and the content on the channel.</p><p>In the early days of legacy ATSC, expert OTA viewers used TSReader software to see what bit rate stations were using to transmit their HDTV programs. Stations that sacrificed HDTV bit rates to add additional program streams were criticized. Now that some stations are transmitting two HDTV program streams and one or two SD program streams in the same 19.392 Mbps, most stations have at least one SD multicast, but there don’t seem to be as many complaints. Why?</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="mHqSoizpKmthqG3jp8BYnP" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/mHqSoizpKmthqG3jp8BYnP.jpg" mos="https://cdn.mos.cms.futurecdn.net/mHqSoizpKmthqG3jp8BYnP.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><em>Fig. 1: Statistical multiplexing bandwidth allotment</em> The answer is statistical multiplexing (“statmux”). Each program is given the bit rate it needs for the video on the air right now. If the scene isn’t changing—a talking head, for example, or slide without motion—the bandwidth can be used by other programs.</p><p>Statistical multiplexing allows multiple video streams to efficiently share limited bandwidth. Each HDTV stream can hit peak bit rates up to the amount left after all the minimum bit rate streams are assigned. Data is also required for audio and program information, but this is a fixed data rate. I’ll cover this in more detail in a future column. Fig. 1 shows the basic concept.</p><p>One key point—“statmux” and MPEG- 2 encoding technology has improved significantly since DTV broadcasting began. Stations that are channel sharing will have to spend some of their auction money to upgrade their encoding systems to the latest technology to minimize the impact channel sharing will have on video quality.</p><p>As I outlined in my earlier article on the incentive auction and repacking timeline, channel sharing will take place early in the process, within the first year of the 39-month deadline for completing the repack. Your favorite station may give up its spectrum and channel share, but if the station it shares with has good coverage, you won’t lose your programs, at least until the repacking begins.</p><p>There are multiple ways viewers could lose access to OTA programs during the repack. The first and worst impacts viewers that receive stations by translators or whose favorite programming happens to be available only on a low-power TV station. These stations are not protected during the repacking, and if they have a channel in the wireless band, they may not be able to find a replacement channel in the more densely packed TV band after the repack.</p><p><strong>WHERE’S THE MONEY?</strong><br/></p><p>While replacement channels may be available in rural areas, Congress and the FCC have allocated zero dollars to pay for the channel change and any new equipment that might be required. Local governments, civic organizations and public broadcasting stations may have trouble finding the money to make the channel change. I’m worried because all of my TV viewing when I’m home is from a PBS TV translator on Channel 50!</p><p><br/>Viewers in areas served by full-power stations may find they encounter reception problems during the repack. The reason is many, if not most, stations will have to use transmission facilities with less coverage than they have now while changing channels.<br/></p><p>Stations will construct interim facilities, which may later be used for backup, with lower antennas and less power so they can remove and replace the main antenna with one that will work on the new channel.<br/></p><p>In some markets, stations may be able to share a broadband antenna, which might result in less loss than a low-height, low-power antenna, but still not be as good as their original antenna.<br/></p><p>As I explained in my last column, FCC flexibility in allowing coverage increases in some areas could help stations with directional antenna patterns avoid major coverage loss if they need to share an antenna.<br/></p><p>If a large number of stations have to be repacked, given the limits of tower crew availability and weather, some stations may have to live with reduced coverage until late or even after the 39-month repack period ends. Stay tuned!<br/></p><p><em>I welcome your comments and questions. Email me at </em><em><br/><a href="mailto:dlung@transmitter.com">dlung@transmitter.com</a>.</em></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Survey: 17 Percent of U.S. Households Are OTA-Only ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/17-percent-of-us-households-are-otaonly</link>
                                                                            <description>
                            <![CDATA[ More and more folks are embracing over-the-air television. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">7GQRuxonXqKTbLUjHidcsd</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/F7oYWBDsuM9NgE95eCRidj-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 13 Jul 2016 10:45:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ posted by Deborah D. McAdams ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/F7oYWBDsuM9NgE95eCRidj-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/F7oYWBDsuM9NgE95eCRidj-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="ZAMAuAMCFsmM5mVmJiHuLj" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/ZAMAuAMCFsmM5mVmJiHuLj.jpg" mos="https://cdn.mos.cms.futurecdn.net/ZAMAuAMCFsmM5mVmJiHuLj.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><strong>NEW YORK</strong>—More and more folks are embracing over-the-air television. Recent findings from market researcher GfK indicate that 17 percent U.S. TV households rely on “broadcast-only” television reception, up from 15 percent in 2015. Concurrently 25 percent now have no cable and satellite reception.<br/><br/>“The fact that a statistically significant increase in broadcast-only reception occurred over just one year may be further proof that the cord-cutting/cord-never phenomenon is accelerating,” said David Tice, senior vice president in GfK’s Media & Entertainment practice. “If you include homes that have no TVs at all—about 3 percent of all households—then less than three quarters, or 73 percent, of U.S. homes continue to have pay TV service, with the attendant implications for all stakeholders—not just the pay TV services themselves, but also networks, content providers, and advertisers.”<br/><br/>The research, from GfK’s 2016 “Ownership and Trend Report” from <em>The Home Technology Monitor</em>, shows that 17 percent of U.S. TV households now rely on broadcast-only or over-the-air reception, up from 15 percent in 2015. Another 6 percent say they only use Internet services such as Netflix, Amazon Prime, Hulu, or YouTube and do not have traditional broadcast or pay TV reception at all; this compares with 4 percent a year ago.<br/><br/>Further, TV households with a resident between 18 and 34 years old are much more likely to be opting for alternatives to cable and satellite; 22 percent of these homes are using broadcast-only reception, versus 17 percent of all U.S. households, and 13 percent are only watching an Internet service on their TV sets, versus 6 percent of all TV homes. Overall, 38 percent of 18-to-34 households rely on some kind of alternative TV reception or video source, versus 25 percent of all homes.<br/><br/>On the other hand, households with at least one resident age 50 or above have higher rates of subscribing to cable or satellite services. More than eight in 10, or 82 percent, have some sort of pay TV subscription, versus 75 percent of all U.S. TV households. The difference comes almost exclusively in levels of cable subscription, with 46 percent of 50+ homes paying for cable reception, compared with a U.S. average of 41 percent.<br/><br/>Broadcast-only reception is more common in TV households earning under $30,000 per year—26 percent, versus 17 percent among all TV homes—and those with Hispanic residents—24 percent. Households with incomes of $50,000 a year or more post higher levels of satellite subscription—27 percent, compared to an average of 21 percent.<br/><br/>The study was conducted among 3,009 U.S. households, including representative levels of non-TV, non-internet, cell-phone-only, and Spanish dominant homes. <br/><br/><br/><br/><br/></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Eleven FCC Scenarios for The 600 MHz Band Plan ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/opinions/eleven-fcc-scenarios-for-the-600-mhz-band-plan</link>
                                                                            <description>
                            <![CDATA[ In its recent Report and Order, the FCC revealed 11 scenarios under consideration for a 600 MHz Band Plan following the spectrum auctions. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">4GUZ9GAWNCZLbgciKmBQWy</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/6he36ucNpcLV2E786Pnb6n-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 17 Feb 2015 06:00:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Opinion]]></category>
                                                    <category><![CDATA[Insights]]></category>
                                                                                                                    <dc:creator><![CDATA[ Charles W. Rhodes ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/6he36ucNpcLV2E786Pnb6n-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/6he36ucNpcLV2E786Pnb6n-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="oPZCsQTyH2va52MCDfWDvh" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/oPZCsQTyH2va52MCDfWDvh.jpg" mos="https://cdn.mos.cms.futurecdn.net/oPZCsQTyH2va52MCDfWDvh.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><em>Charles W. Rhodes</em> The FCC is proposing 11 scenarios for a 600 MHz Band Plan following the spectrum auctions. Which of these will be adopted will be determined by the outcome of the auction in 2016.</p><p>Each scenario for the 600 MHz band starts with Channel 21 (512–518 MHz). The highest channel number ranges from 26 to 44, depending on how much spectrum is offered for sale by broadcasters and then resold to broadband operators. The re-allocated spectrum is divided into blocks of 5 MHz each. There could be from two to 12 pairs of blocks. Pairs consist of one block for uplink transmissions from cellphones to base stations; and a second for downlink transmission by base stations to cellphones.</p><p><strong>INTER-SERVICE INTERFERENCE</strong><br/>I have restructured the data in Fig. 1 into Figs. 2 and 3. Fig. 2 shows the number of UHF TV channels after repacking. It varies from 6 to 23 depending on how many pairs of 5 MHz blocks are re-allocated after the auction.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="zQsE8CjQ2repWw3vrgiWUE" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/zQsE8CjQ2repWw3vrgiWUE.jpg" mos="https://cdn.mos.cms.futurecdn.net/zQsE8CjQ2repWw3vrgiWUE.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><em>Fig. 1: The graph is Fig. 23 of the FCC's <a href="https://apps.fcc.gov/edocs_public/attachmatch/FCC-14-50A1.pdf">June 2 R&O</a>, page 453. Light Blue: 5 MHz blocks of spectrum. Orange: Channel 37 reserved for radio astronomy and medical telemetry (hospitals). Diagonally shaded gray: guard bands. Blocks with numbers from 21–36 and 38–44 should be tinted light green. These are the remaining DTV channels. The numbers in a column on the left side are the amounts of spectrum broadcasters might offer to sell. The amount of spectrum that can be re-sold to broadband is less due to the need for guard bands in the 600 MHz band.</em></p><p>In Fig. 1, the striped cells with numbers of MHz; 11, 9, 7 or 3 represent the guard bands. There is an 11 MHz-wide guard band between the cellphone uplink blocks and the base station downlink blocks. There are also some smaller guard bands, notably, a 3 MHz-wide one adjacent to Channel 37; and a 7 MHz-wide guard band between some base station transmit blocks and DTV channels.</p><p>These guard bands are vital to protecting against what the FCC calls “Inter-Service Interference” or ISIX. Broadcasters are familiar with the fact that a DTV transmitter radiates power in both channels adjacent to the channel it is licensed to use. This is sometimes called sideband splatter, but it is actually third-order inter-modulation products generated in the high-power amplifier of a DTV transmitter; which gets past the transmitter RF mask filter and is radiated.</p><p>The 3 MHz guard bands on either side of Channel 37 (608-614 MHz), which is reserved for radio astronomy and medical telemetry, protect that channel from ISIX. The total bandwidth of all guard bands varies among the 11 FCC scenarios from 14 MHz to 28 MHz. I call such spectrum “lost” because, by definition, it cannot be used either by broadcasters or sold to broadband. Such spectrum is also lost as a source of revenue to the U.S. Treasury Department.<br/></p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="97FNUyjdEriZpVfpAZhhPf" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/97FNUyjdEriZpVfpAZhhPf.jpg" mos="https://cdn.mos.cms.futurecdn.net/97FNUyjdEriZpVfpAZhhPf.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><em>Fig. 2: Number of DTV channels after repacking as a function of the number of pairs of 5 MHz blocks available for auction.</em><strong>BEST LAID PLANS</strong><br/>I expect there will be pressure by white space advocates to let these guard bands also be used for white space services. That scares me because I recall the “good ol’ days” of Citizen’s Band mobile radios. Chaos soon reigned in the CB Band.</p><p>If the FCC chooses either eight or 11 pairs of 5 MHz blocks, it will have to purchase 28 MHz more spectrum from broadcasters than it will be able to resell to broadband operators. Since the commission is mandated not to lose money in these auctions, it will have to resell this spectrum at a price well above what it paid for the spectrum it purchased from broadcasters.</p><p>The 2012 law that authorized this auction requires the FCC to recover all costs of conducting it and requires the commission to turn over to the U.S. Treasury the net profits. I believe some of the billions of dollars expected from this spectrum auction will never be realized. I suspect that the estimated $44 billion of auction proceeds do not take into account the fact that some spectrum the FCC will buy cannot be resold because it must be used as guard intervals in the 600 MHz band plan.</p><p>The best case scenario from this perspective would have the FCC buy 84 MHz of spectrum and to resell 70 MHz of this spectrum. The minimum markup would be 84/70 or 20 percent. Administrative costs, the $1.75 billion to reimburse displaced broadcasters, and the profit for the U.S. Treasury will erode those billions of dollars promised to Congress.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="4dD2WUNcaXAsrStnhGWNYE" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/4dD2WUNcaXAsrStnhGWNYE.jpg" mos="https://cdn.mos.cms.futurecdn.net/4dD2WUNcaXAsrStnhGWNYE.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p><em>Fig. 3: “Lost UHF Band Spectrum” in MHz. as a function of the number of pairs of 5 MHz blocks available for auction. Note the steep increase in “Lost Spectrum” between 7 pairs and 8 pairs of 5 MHz auctionable blocks.</em> Fig. 3 plots the number of DTV channels in the 600 MHz band after repacking as a function of the number of pairs of 5 MHz blocks auctioned by the FCC. The outstanding feature of this plot is the steep decline in the number of DTV channels between the scenario with seven pairs of 5 MHz blocks (16 DTV channels) and the scenario with eight pairs of 5 MHz blocks. It would cost broadcasters four channels to allow one additional pair of 5 MHz blocks instead of seven pairs.</p><p>When all is said, it appears the best scenario identified by the FCC would provide seven pairs of 5 MHz blocks. This view has also been expressed by a number of cellphone operators according to the FCC.</p><p><strong>CELLPHONE DESIGN</strong><br/>The FCC report provides a very complete analysis of each of the 11 scenarios depicted in Fig. 1 (FCC 14–50, p. 453). As Fig. 1 shows, there are guard bands of 3, 7, 9 and 11 MHz between different kinds or signals. The 11 MHz guard bands between uplink and downlink signals are obviously needed to keep the transmitter output from getting into the receiver input. The others are also required to avoid third-order distortion products from causing interference. For example, the 3 MHz band stop filters keep received signals in Channels 36 or 38 out of Channel 37.</p><p>Every kind of filter attenuates every signal within its pass band (insertion loss). With each 1 dB of insertion loss, the receiver’s noise figure increases by 1 dB, and sensitivity decreases by 1 dB. Worse yet, where there is more than one filter in the signal path, the insertion loss of each filter is additive. In Fig. 1, you will see that each scenario requires at least one 11 MHz filter and some require two or three filters. Filters not only cost in receiver performance, they cannot be manufactured as an integrated circuit so they take up space and add slightly to the weight of handheld cellphones. The fewer the number of filters in a handheld cellphone, the less it will cost and weigh, all things cellphone users can appreciate. As Fig. 1 shows, the number of filters varies significantly for the various scenarios.</p><p>There is yet another variable of importance not shown in Fig. 1, but was covered in the FCC report. The bandwidth over which the antenna of a handheld cellphone is efficient varies between the scenarios in the FCC Plan for the 600 MHz Band. Antenna efficiency directly affects battery life (time between recharges), as well as the sensitivity of the receiver. Scenarios that provide more than eight pairs of 5 MHz blocks will involve these antenna bandwidth problems. Where the efficiency of a simple passive antenna is poor (lots of signal bandwidth), the antenna can be automatically tuned to improve its efficiency. However this automatic antenna tuner feature requires added circuitry and therefore adds to the manufacturing cost. The insertion loss of this reduces the power to the antenna, which translates to increased power drain on the battery when transmitting. When receiving, it adds desensitization of the received signal.</p><p>Stay tuned.</p><p><em>Charles Rhodes is a consultant in the field of television broadcast technologies and planning. He can be reached via email at</em><a href="mailto:cwr@bootit.com">cwr@bootit.com</a>.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>