<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>CommLawBlog</title>
      <link>http://www.commlawblog.com/</link>
      <description />
      <language>en</language>
      <copyright>Copyright 2013</copyright>
      <lastBuildDate>Wed, 19 Jun 2013 16:07:59 -0500</lastBuildDate>
      <pubDate>Wed, 19 Jun 2013 16:07:59 -0500</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="commlawblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.commlawblog.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.commlawblog.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.commlawblog.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.commlawblog.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.commlawblog.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.commlawblog.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.commlawblog.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.commlawblog.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><item>
         <title>Fifth "White Space" Coordinator Begins Tests</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;LS telcom AG seeks to join the two coordinators operating and two others awaiting approval. &lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="100" vspace="5" hspace="5" height="114" align="left" alt="" src="http://www.commlawblog.com/uploads/image/designer-1.JPG" /&gt;TV &amp;ldquo;white space&amp;rdquo; devices operate on TV channels that are vacant in a given area. (On a map of frequency usage, these areas show up in white; hence the name.)&lt;/p&gt;
&lt;p&gt;These devices must avoid causing interference to active TV stations, certain wireless microphones, and certain TV reception sites.&amp;nbsp;To accomplish this, most are required to consult a complex and changing database that shows where they can safely operate.&lt;/p&gt;
&lt;p&gt;The FCC has identified ten administrators for the database, expected to operate competitively. Before receiving FCC approval, each candidate must run a live test of its operations, submit test reports to the FCC, and survive public comment.&lt;/p&gt;
&lt;p&gt;We here in the CommLawBlog bunker have covered &lt;a href="http://www.commlawblog.com/tags/database-administrator/"&gt;developments on the white space database coordination front&lt;/a&gt; for several years.&amp;nbsp;Most recently, those developments have been somewhat repetitive and our posts were all starting to look the same.&amp;nbsp;We tried to mix things up a bit with poetry (&lt;a href="http://www.commlawblog.com/2013/03/articles/unlicensed-operations-and-emer/fourth-white-space-database-coordinator-tees-up-tests/"&gt;limericks&lt;/a&gt;! a &lt;a href="http://www.commlawblog.com/2013/05/articles/broadcast/white-space-database-update/"&gt;haiku&lt;/a&gt;!) . . . but soon found the limit to our poetic abilities.&lt;/p&gt;
&lt;p&gt;So here&amp;rsquo;s what we plan to do going forward.&lt;/p&gt;&lt;p&gt;The table below reflects all the would-be database coordinators and all the steps on the way to FCC approval.&amp;nbsp;Each time there is a new development, we will post an updated version of the table.&amp;nbsp;Dates in the table reflect the dates of the FCC public notices relevant to the particular event. Clicking on a date brings up the respective public notice. The date shown in bold face red will always be the most recent event.&amp;nbsp;&lt;/p&gt;
&lt;table cellspacing="0" cellpadding="0" border="1" style="margin-left:55.25pt;border-collapse:collapse;border:none;"&gt;
    &lt;tbody&gt;
        &lt;tr&gt;
            &lt;td width="168" style="width:1.75in;border:solid black 1.0pt;padding:
            2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:
            &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Coordinator&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border:solid black 1.0pt;border-left:none;padding:
            2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:
            &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Test Started&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border:solid black 1.0pt;border-left:none;padding:
            2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:
            &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Test Finished; Comments Sought&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border:solid black 1.0pt;border-left:none;padding:
            2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:
            &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Coordinator Approved&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Comsearch&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Frequency   Finder Inc.&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Google   Inc.&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-297A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Feb. 27, 2013&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0529/DA-13-1220A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;May 29, 2013&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;LS telcom   AG&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;b&gt;&lt;span style="font-size:14.0pt;color:red"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1401A1.pdf"&gt;&lt;span style="font-size:11.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;;
            color:red"&gt;June 18, 2013&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Key   Bridge Global LLC&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-328A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;March 4, 2013&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0529/DA-13-1222A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;May 29, 2013&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Microsoft   Corp.&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Neustar   Inc.&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Spectrum   Bridge Inc.&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1534A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Sept. 14, 2011&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1872A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Nov. 10, 2011&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-2044A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Dec. 22, 2011&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Telcordia   Technologies&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1956A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Dec. 2, 2011&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-12-118A1.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Feb. 1, 2012&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p align="center" style="text-align:center"&gt;&lt;span style="font-size:11.0pt"&gt;&lt;a href="http://www.thedcoffice.com/late_releases_files/03-26-2012/DA%2012-466.pdf"&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;March 26, 2012&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
            &lt;/td&gt;
        &lt;/tr&gt;
        &lt;tr&gt;
            &lt;td width="168" valign="top" style="width:1.75in;border:solid black 1.0pt;border-top:none;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;
            &lt;p style="margin-left:7.75pt"&gt;&lt;b&gt;&lt;span style="font-size:9.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;WSdb   LLC&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;
            &lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.5pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
            &lt;td width="114" style="width:85.55pt;border-top:none;border-left:none;
            border-bottom:solid black 1.0pt;
            border-right:solid black 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt"&gt;&amp;nbsp;&lt;/td&gt;
        &lt;/tr&gt;
    &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;br /&gt;
Prosaic, perhaps, but far less taxing on our limited creative resources and, in the end, probably a more useful way of keeping our readers abreast of the overall database coordinator scene.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;[&lt;em&gt;Blogmeister's Note: We are hoping to work a deal with somebody (are you listening,  Starbucks and Chipotle?) so that, when the table has been completely filled up, our  readers will be able to print it out and present it for a free cup of  coffee or maybe a burrito.&amp;nbsp; Check back here for updates.&lt;/em&gt;]&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/KoKFM2HwZVs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/KoKFM2HwZVs/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/broadcast/fifth-white-space-coordinator-begins-tests/</guid>
         <category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/tags">Database Administrator</category><category domain="http://www.commlawblog.com/tags">Google, Inc.</category><category domain="http://www.commlawblog.com/tags">Key Bridge Global, LLC</category><category domain="http://www.commlawblog.com/tags">LS telcom AG</category><category domain="http://www.commlawblog.com/tags">Limericks</category><category domain="http://www.commlawblog.com/tags">Spectrum Bridge</category><category domain="http://www.commlawblog.com/tags">Telcordia Technologies</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/tags">White Space</category><category domain="http://www.commlawblog.com/tags">White Spaces</category>
         <pubDate>Wed, 19 Jun 2013 14:56:20 -0500</pubDate>
         <dc:creator>Mitchell Lazarus</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/broadcast/fifth-white-space-coordinator-begins-tests/</feedburner:origLink></item>
            <item>
         <title>Number, Please! Comment Deadlines Set in Telephone Numbering Proceeding</title>
         <description>&lt;p&gt;&lt;img width="100" vspace="5" hspace="5" height="85" align="left" alt="" src="http://www.commlawblog.com/uploads/image/telephone book-1.JPG" /&gt;In April &lt;a href="http://www.commlawblog.com/2013/04/articles/cellular/fcc-proposes-rule-changes-for-obtaining-telephone-numbers/"&gt;we reported&lt;/a&gt; on a &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-13-51A1.pdf"&gt;Notice of Proposed Rulemaking and Notice of Inquiry&lt;/a&gt; (&lt;i&gt;NPRM/NOI&lt;/i&gt;) in which the FCC has proposed changes in how telephone numbers are obtained by certain types of providers.&amp;nbsp;The ultimate upshot of the Commission&amp;rsquo;s proceeding could eventually mean serious changes in what we understand a telephone number to represent.&amp;nbsp;The &lt;i&gt;NPRM/NOI&lt;/i&gt; has now been &lt;a href="http://www.gpo.gov/fdsys/pkg/FR-2013-06-19/pdf/2013-13703.pdf"&gt;published in the Federal Register&lt;/a&gt;, which (as loyal readers should know by now) sets the deadlines for comments and reply comments.&amp;nbsp;Anyone interested in commenting has until &lt;b&gt;&lt;i&gt;July 19, 2013&lt;/i&gt;&lt;/b&gt;; reply comments are due by &lt;b&gt;&lt;i&gt;August 19&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/ghWHNOOUCBw" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/ghWHNOOUCBw/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/deadlines/number-please-comment-deadlines-set-in-telephone-numbering-proceeding/</guid>
         <category domain="http://www.commlawblog.com/articles">Cellular</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/articles">Internet</category><category domain="http://www.commlawblog.com/tags">Telephone numbers</category><category domain="http://www.commlawblog.com/tags">VoIP</category><category domain="http://www.commlawblog.com/tags">Voice over Internet Protocol</category><category domain="http://www.commlawblog.com/tags">Vonage</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category><category domain="http://www.commlawblog.com/articles">Wireline Telephony</category>
         <pubDate>Wed, 19 Jun 2013 04:40:12 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/deadlines/number-please-comment-deadlines-set-in-telephone-numbering-proceeding/</feedburner:origLink></item>
            <item>
         <title>Update: Comment Deadlines Set in Big House Burner Ban Proceeding</title>
         <description>&lt;p&gt;&lt;img width="100" vspace="5" hspace="5" height="119" align="left" src="http://www.commlawblog.com/uploads/image/inmate-cellphone-1.JPG" alt="" /&gt;&lt;a href="http://www.commlawblog.com/2013/05/articles/cellular/jailhouse-block-reprise-fcc-looks-to-ban-burners-from-the-big-house/"&gt;Last month we reported&lt;/a&gt; on a &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-13-58A1.pdf"&gt;Notice of Proposed Rulemaking&lt;/a&gt; (&lt;i&gt;NPRM&lt;/i&gt;) looking to address the problem of contraband cell phone use in prisons.&amp;nbsp;The &lt;i&gt;NPRM&lt;/i&gt; has now been &lt;a href="http://www.gpo.gov/fdsys/pkg/FR-2013-06-18/pdf/2013-14405.pdf"&gt;published in the Federal Register&lt;/a&gt;, which means that comment and reply comment deadlines have now been set.&amp;nbsp;If you&amp;rsquo;re looking to chip in your two cents&amp;rsquo; worth, you&amp;rsquo;ve got until &lt;b&gt;&lt;i&gt;July 18, 2013&lt;/i&gt;&lt;/b&gt; to file comments, and until &lt;b&gt;&lt;i&gt;August 2&lt;/i&gt;&lt;/b&gt; for reply comments.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/4Dm9wMLs2WA" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/4Dm9wMLs2WA/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/deadlines/update-comment-deadlines-set-in-big-house-burner-ban-proceeding/</guid>
         <category domain="http://www.commlawblog.com/tags">Cell phone jamming</category><category domain="http://www.commlawblog.com/tags">Cell phone use in prison</category><category domain="http://www.commlawblog.com/articles">Cellular</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/tags">Detection systems</category><category domain="http://www.commlawblog.com/articles">Enforcement Activities (Fines, Forfeitures, etc.)</category><category domain="http://www.commlawblog.com/articles">Internet</category><category domain="http://www.commlawblog.com/tags">Managed access systems</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category>
         <pubDate>Tue, 18 Jun 2013 04:19:48 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/deadlines/update-comment-deadlines-set-in-big-house-burner-ban-proceeding/</feedburner:origLink></item>
            <item>
         <title>Critical Infrastructure Proponents Seek Review of 14 GHz Turndown</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Pleading asks full Commission to reverse decision of three bureaus.        &lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="110" vspace="5" hspace="5" height="91" align="left" src="http://www.commlawblog.com/uploads/image/thumbs down-3.JPG" alt="" /&gt;We reported in May that &lt;a href="http://www.commlawblog.com/2013/05/articles/wireless-telephony/fcc-turns-down-use-of-140145-ghz-for-critical-infrastructure-communications/"&gt;three of the FCC&amp;rsquo;s bureaus turned down&lt;/a&gt;, after five years, a Petition for Rulemaking from the Utilities Telecom Council and Winchester Cator, LLC that asked the FCC to open the 14.0-14.5 GHz band for terrestrial point-to-point and point-to-multipoint critical infrastructure communications. It is probably not a coincidence that the FCC, just a few days before the rejection, had &lt;a href="http://www.commlawblog.com/2013/05/articles/internet/inflight-and-online-fcc-proposes-domestic-airtoground-system-for-airborne-wifi/"&gt;proposed use of this same band&lt;/a&gt;&amp;nbsp;for air-ground broadband systems to facilitate Internet service for airplane passengers.&lt;/p&gt;
&lt;p&gt;UTC and Winchester Cator have now filed an &lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022426166"&gt;Application for Review&lt;/a&gt; asking the full Commission to reverse the bureaus&amp;rsquo; decision. Comments are due on &lt;b&gt;&lt;i&gt;July 1, 2013&lt;/i&gt;&lt;/b&gt; and reply comments on &lt;b&gt;&lt;i&gt;July 11&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/zA-tWGOLFoY" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/zA-tWGOLFoY/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/deadlines/critical-infrastructure-proponents-seek-review-of-14-ghz-turndown/</guid>
         <category domain="http://www.commlawblog.com/tags">14.0-14.5 GHz</category><category domain="http://www.commlawblog.com/tags">Critical infrastructure industries</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/tags">Utilities Telecom Council</category><category domain="http://www.commlawblog.com/tags">Winchester Cator</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category>
         <pubDate>Mon, 17 Jun 2013 20:18:54 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/deadlines/critical-infrastructure-proponents-seek-review-of-14-ghz-turndown/</feedburner:origLink></item>
            <item>
         <title>5 GHz Reply Date Extended</title>
         <description>&lt;p&gt;&lt;strong&gt;&lt;em&gt;Reply comments in the proceeding on 5 GHz unlicensed operation are now due July 24.&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="90" vspace="5" hspace="5" height="65" align="left" alt="" src="http://www.commlawblog.com/uploads/image/spectrum chart-3 copy.jpg" /&gt;In February&amp;nbsp;&lt;a href="http://www.commlawblog.com/2013/02/articles/unlicensed-operations-and-emer/fcc-proposes-to-simplify-and-expand-unlicensed-5-ghz-use/"&gt;we reported&lt;/a&gt;&amp;nbsp;on an&amp;nbsp;&lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0220/FCC-13-22A1.pdf"&gt;FCC proposal&lt;/a&gt;&amp;nbsp;that would not only add new 5 GHz frequencies but also overhaul &amp;ndash; maybe even simplify &amp;ndash; a confusing stretch of the rules.&amp;nbsp;One possible upshot would be the opening up of 195 MHz of spectrum for Wi-Fi-type operation.&lt;/p&gt;
&lt;p&gt;Comments were filed on May 28. &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1388A1.pdf"&gt;The FCC has extended the date&lt;/a&gt; for reply comments, originally June 24, to &lt;b&gt;&lt;i&gt;July 24&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/nx2kholmVu4" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/nx2kholmVu4/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/deadlines/5-ghz-reply-date-extended/</guid>
         <category domain="http://www.commlawblog.com/tags">5 GHz</category><category domain="http://www.commlawblog.com/tags">5.15-5.825 GHz</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/tags">Middle Class Tax Relief and Job Creation Act of 2012</category><category domain="http://www.commlawblog.com/tags">U-NII</category><category domain="http://www.commlawblog.com/tags">Unlicensed National Information Infrastructure</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category>
         <pubDate>Mon, 17 Jun 2013 19:51:32 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/deadlines/5-ghz-reply-date-extended/</feedburner:origLink></item>
            <item>
         <title>FCC to LPFM Applicants: Let the Uploading Begin!</title>
         <description>&lt;p&gt;&lt;b&gt;&lt;i&gt;Media Bureau announces LPFM filing window opening October 15 and closing October 29 (at 6:00 p.m. EDT); applications may be uploaded, but not filed, starting now&lt;/i&gt;&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="126" vspace="5" hspace="5" height="96" align="left" src="http://www.commlawblog.com/uploads/image/gulliver-lilliput-1.JPG" alt="" /&gt;Attention all you LPFM wannabes.&amp;nbsp;Mark your calendars, get your CDBS and FRN account information in order, stock up on NoDoz&amp;reg; and let the games begin &amp;ndash; because the count-down has started.&amp;nbsp;The &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1385A1.pdf"&gt;Media Bureau has announced&lt;/a&gt; that, on &lt;b&gt;&lt;i&gt;October 15, 2013&lt;/i&gt;&lt;/b&gt;, the first LPFM filing window in more than a decade will be flung open, and will stay open until &lt;b&gt;&lt;i&gt;6:00 p.m. (EDT) on October&amp;nbsp;29, 2013&lt;/i&gt;&lt;/b&gt;.&amp;nbsp;The window will permit the filing of applications for new LPFM stations and major changes to existing stations.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;While applications can&amp;rsquo;t be filed until October 15, they may be uploaded to CDBS anytime between now and then &amp;ndash; which gives would-be LPFM applicants plenty of time to undertake searches for channels and transmitter sites and prep their apps in anticipation of the opening of the window.&lt;/p&gt;
&lt;p&gt;A few important threshold factors to keep in mind:&lt;/p&gt;&lt;p&gt;&lt;b&gt;&lt;i&gt;Eligibility.&amp;nbsp;&lt;/i&gt;&lt;/b&gt;Eligibility to file an LPFM application is limited to three specific categories of applicant: (1) nonprofit educational organizations (NEOs); (2) Tribe or Tribally-controlled organizations (Tribes); and (3) state or local governments or non-government entities proposing to provide a &amp;ldquo;noncommercial public safety radio service to protect the safety of life, health, or property&amp;rdquo; (Public Safety Applicants).&amp;nbsp;Nobody else gets a crack.&lt;/p&gt;
&lt;p&gt;Any NEO may file only one application in this window, and Tribes may file no more than two.&amp;nbsp;Public Safety Applicants may file more than one, but if they do so, they must designate one as the &amp;ldquo;priority&amp;rdquo; application; non-&amp;ldquo;priority&amp;rdquo; applications will be dismissed if timely mutually exclusive applications from other applicants are submitted.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If an NEO applicant files more than one application, all but the first one in the door will be tossed as &amp;ldquo;conflicting&amp;rdquo; pursuant to &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=a7e1912c2ce62723879d9e50fda2027e&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:4.0.1.1.2.8.1.81&amp;amp;idno=47"&gt;Section 73.3518&lt;/a&gt; of the rules.&amp;nbsp;While the Bureau&amp;rsquo;s public notice does not expressly address the point, &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=99add124d07c8b3a749cdc6cf8f2a01c&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:4.0.1.1.2.7.1.18&amp;amp;idno=47"&gt;Section 73.855&lt;/a&gt; of the rules prohibits any person or entity from holding attributable interests in more than one LPFM station.&amp;nbsp;And &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=99add124d07c8b3a749cdc6cf8f2a01c&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:4.0.1.1.2.7.1.20&amp;amp;idno=47"&gt;Section 73.860&lt;/a&gt; prohibits all cross-ownership of full-service and LPFM stations, although it does permit some very limited cross-ownership of LPFM and FM translators. The application form (&lt;a href="http://transition.fcc.gov/Forms/Form318/318.pdf"&gt;Form 318&lt;/a&gt;) is set up to ferret out information about such things.&lt;/p&gt;
&lt;p&gt;One more eligibility consideration: applicants must be &amp;ldquo;local&amp;rdquo; as that concept is defined in &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=99add124d07c8b3a749cdc6cf8f2a01c&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:4.0.1.1.2.7.1.16&amp;amp;idno=47"&gt;Section 73.853 of the rules&lt;/a&gt;.&amp;nbsp;Since that definition is particularly detailed in its requirements, we strongly suggest that prospective applicants thoroughly familiarize themselves with it before getting too deep into the project.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;Protection Requirements&lt;/i&gt;&lt;/b&gt;.&amp;nbsp;LPFM applications will have to protect: all existing vacant FM allotments; &lt;b&gt;&lt;i&gt;and&lt;/i&gt;&lt;/b&gt; all outstanding FM, FM Translator, FM Booster and TV Channel 6 authorizations; &lt;b&gt;&lt;i&gt;and&lt;/i&gt;&lt;/b&gt; all applications for any of those services that were on file prior to June 17, 2013 (the date of the public notice announcing the filing window).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;Form 318.&lt;/i&gt;&lt;/b&gt;&amp;nbsp;If you want to file in this window, you&amp;rsquo;ve got to use the April, 2013 version of Form 318.&amp;nbsp;Since you have to file through CDBS, and since that version of the form is presumably the only one currently available, that shouldn&amp;rsquo;t be a problem.&amp;nbsp;No filing fee is required.&amp;nbsp;The public notice instructs applicants that CDBS will give them a confirmation that their applications have been &amp;ldquo;successfully filed&amp;rdquo; and that, unless they get such a notice screen, they should take steps to determine whether their applications really have been filed.&lt;/p&gt;
&lt;p&gt;The Bureau also cautions that applicants should not share the CDBS account passwords with anyone not authorized to modify their proposals.&amp;nbsp;Bear in mind that applications filed during the window period will &lt;b&gt;&lt;i&gt;not&lt;/i&gt;&lt;/b&gt; be publicly available until &lt;b&gt;&lt;i&gt;after&lt;/i&gt;&lt;/b&gt; the window closes.&amp;nbsp;&lt;br /&gt;
&lt;b&gt;&lt;i&gt;&lt;br /&gt;
Return of &amp;ldquo;Letter Perfect&amp;rdquo;.&lt;/i&gt;&lt;/b&gt;&amp;nbsp;In what appears to be a variation on the &amp;ldquo;letter perfect&amp;rdquo; standard of days gone by, any application that is &amp;ldquo;incomplete&amp;rdquo; or &amp;ldquo;patently defective&amp;rdquo; or that does not afford the requisite protection will be dismissed with no opportunity to correct the deficiency.&amp;nbsp;Such dismissals will occur &lt;i&gt;after&lt;/i&gt; the window closes; until then (&lt;i&gt;i.e.&lt;/i&gt;, until 6:00 p.m. (EDT) on October 29), applicants &lt;b&gt;&lt;i&gt;will&lt;/i&gt;&lt;/b&gt; be able to amend their previously uploaded-and-filed applications.&amp;nbsp;(You do that by opening a new Form 318 and checking &amp;ldquo;Amendment to pending application&amp;rdquo; in response to the &amp;ldquo;Application Purpose&amp;rdquo; question, &lt;i&gt;i.e.&lt;/i&gt;, Section I, Question 3.)&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;Looking for an LPFM Channel?&lt;/i&gt;&lt;/b&gt;&amp;nbsp;The Bureau&amp;rsquo;s notice directs prospective applicants to the Bureau&amp;rsquo;s &lt;a href="http://www.fcc.gov/encyclopedia/low-power-fm-lpfm-channel-finder"&gt;on-line LPFM Channel Finder&lt;/a&gt;, which has been updated to include &lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2012/db1204/FCC-12-144A1.pdf"&gt;technical changes adopted last November.&lt;/a&gt;&amp;nbsp;Be mindful, though, that the Channel Finder is &amp;ldquo;intended solely to assist LPFM applicants in tentatively identifying available FM channels.&amp;rdquo;&amp;nbsp;In other words, anybody using that facility should (in classic Reaganesque terms) be sure to &amp;ldquo;trust, but verify&amp;rdquo;.&amp;nbsp;Hiring a competent consulting engineer would be a good start.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Once the window has closed, the Bureau&amp;rsquo;s staff will weed through them, toss the defective ones, and group the rest according to mutual exclusivity.&amp;nbsp;MX applicants will apparently be given the opportunity to resolve their conflict through settlement, although the precise metes and bounds of such settlements aren&amp;rsquo;t described in the notice.&amp;nbsp;MX groups that don&amp;rsquo;t get resolved that way will be subject to the &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=99add124d07c8b3a749cdc6cf8f2a01c&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:4.0.1.1.2.7.1.24&amp;amp;idno=47"&gt;Commission&amp;rsquo;s point system&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The formal announcement of an October 15 LPFM window is a testament to the way the Audio Division has played the very difficult FM translator/LPFM hand that it was dealt by the Commission, the courts and the Congress.&amp;nbsp;Last November the Commission set October 15 as its target date, but to get there, the Division had to dispose of several thousand FM translator applications that had been hanging around since 2003.&amp;nbsp;To be perfectly honest, we here in the CommLawBlog bunker were, um, skeptical about the October 15 goal.&amp;nbsp;But, while it&amp;rsquo;s still possible that, as we get closer to October 15, there might be some slippage, the Bureau is obviously confident enough at this point to issue the notice and get the ball rolling. Props to them for getting that far.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/SjL6e2-Sir8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/SjL6e2-Sir8/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/broadcast/fcc-to-lpfm-applicants-let-the-uploading-begin/</guid>
         <category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/tags">LPFM filing window</category>
         <pubDate>Mon, 17 Jun 2013 16:05:32 -0500</pubDate>
         <dc:creator>Harry Cole</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/broadcast/fcc-to-lpfm-applicants-let-the-uploading-begin/</feedburner:origLink></item>
            <item>
         <title>FCC Proposes Tripled Fine for Unauthorized Two-Way Radios</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Base forfeiture tripled because offender is a multi-billion dollar global enterprise.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="150" vspace="5" hspace="5" height="118" align="left" alt="" src="http://www.commlawblog.com/uploads/image/bill worries-1.JPG" /&gt;&lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0613/FCC-13-83A1.pdf"&gt;Here&amp;rsquo;s another reminder&lt;/a&gt; to stay on top of the licensing paperwork. Especially if your company is successful.&lt;/p&gt;
&lt;p&gt;A company called Remel, Inc. manufactures and supplies microbiology products for clinical, industrial, and research laboratories. Its corporate parent, Thermo Fisher Scientific, Inc., is a global supplier of analytical instruments, laboratory and diagnostic equipment, chemicals and reagents, and related products and services.&lt;/p&gt;
&lt;p&gt;The companies, like many others, use two-way radios. They say their radio supplier told them, incorrectly, that the radios did not require an FCC a license. (Apparently this happens a lot.) On finding out that a license is in fact required, the companies turned the radios off and applied to the FCC for a license on a different frequency for a higher-powered radio, which the FCC subsequently granted.&lt;/p&gt;
&lt;p&gt;The FCC remained concerned, though, about the period of unlicensed operation, which spanned some nine years. Moreover, a frequency the companies used over that time was allocated to the General Mobile Radio Service (GMRS), a service intended for use by individuals, not companies. GMRS radios are popular with families on camping trips, and the like. In fact, &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=dff4add0e51d5b72138ae4856b224b17&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:5.0.1.1.5.1.139.3&amp;amp;idno=47"&gt;only individuals, and not companies&lt;/a&gt;, are eligible for a GMRS license.&lt;/p&gt;
&lt;p&gt;Not many individuals bother, though. Our friends over at &lt;a href="http://www.spectrumwiki.com/Index.aspx"&gt;SpectrumWiki.com&lt;/a&gt; note that the fee for a GMRS license is many times the cost of the radio equipment, so that only a very small fraction of GMRS operators actually obtain one. (Our law partner Peter Tannenwald wishes it known that he shelled out the eighty bucks and is duly licensed.)&lt;/p&gt;
&lt;p&gt;The FCC could have acknowledged that Remel and Thermo Fisher made an honest mistake and fixed it, and then let the matter drop, or possibly charged a small forfeiture. Instead it &lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0613/FCC-13-83A1.pdf"&gt;proposed a forfeiture of $30,000&lt;/a&gt;. The FCC also emphasized that Remel and Thermo Fisher, not being individuals, would not have been eligible for a GMRS license. This put the FCC &lt;a href="http://www.commlawblog.com/2011/06/articles/enforcement-activities-fines-f/fcc-fines-man-for-not-having-an-unobtainable-license/"&gt;once again&lt;/a&gt; in the odd position of imposing sanctions for failing to obtain a license that the FCC would not have granted.&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=cb9c7f48109f11da6c8b6b3947b4dd8c&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:1.0.1.1.2.1.151.49&amp;amp;idno=47"&gt;base forfeiture&lt;/a&gt; for operating without a license is $10,000. The FCC tripled that on the ground that Thermo Fisher is a &amp;ldquo;multi-billion dollar global enterprise&amp;rdquo; and so &amp;ldquo;should expect the assessment of higher forfeitures for violations.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The takeaway: Check your licenses. Don&amp;rsquo;t ever believe your radio supplier. And prepare for extra penalties if your company makes a lot of money.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/ZVyo4271v6s" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/ZVyo4271v6s/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/enforcement-activities-fines-f/fcc-proposes-tripled-fine-for-unauthorized-twoway-radios/</guid>
         <category domain="http://www.commlawblog.com/articles">Enforcement Activities (Fines, Forfeitures, etc.)</category><category domain="http://www.commlawblog.com/tags">GMRS</category><category domain="http://www.commlawblog.com/tags">Remel, Inc.</category><category domain="http://www.commlawblog.com/tags">Thermo Fisher Scientific, Inc.</category><category domain="http://www.commlawblog.com/tags">forfeitures</category>
         <pubDate>Fri, 14 Jun 2013 14:51:31 -0500</pubDate>
         <dc:creator>Mitchell Lazarus</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/enforcement-activities-fines-f/fcc-proposes-tripled-fine-for-unauthorized-twoway-radios/</feedburner:origLink></item>
            <item>
         <title>Raisin' Defenses at the FCC</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;A Supreme Court case offers a possible route to appealing a forfeiture without having to pay it first.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="175" vspace="5" hspace="5" height="119" align="left" src="http://www.commlawblog.com/uploads/image/raisins-2.jpg" alt="" /&gt;A pair of California raisin farmers might have made it easier to challenge an FCC forfeiture.&lt;/p&gt;
&lt;p&gt;A party dinged with a forfeiture that it thinks is unfair now has two options under the Communications Act. One is to challenge the forfeiture order directly in the Court of Appeals. The problem with that approach is that, as a condition to getting into the Court of Appeals, the challenger must first pay the forfeiture. Since forfeitures can reach up into six and seven figures and, let&amp;rsquo;s face it, not everyone has that much spare cash lying around, that condition poses a serious disincentive to direct appeals.&lt;/p&gt;
&lt;p&gt;The other option is to not pay the forfeiture and wait for the FCC (assisted by their friends from the Department of Justice) to bring suit in your nearest federal District Court. In that case, the burden is on the government to prove that you are in fact really liable for the forfeiture, which gives you an arguable advantage going in. But &lt;a href="http://www.commlawblog.com/2012/08/articles/broadcast/fifth-circuit-short-circuit-court-of-appeals-limits-rights-of-fcc-forfeiture-defendants/"&gt;at least one appellate court&lt;/a&gt; has held that a party choosing this option is not allowed to raise the full panoply of defenses that might normally be available in challenging the forfeiture.&lt;/p&gt;
&lt;p&gt;What does this have to do with raisins?&lt;/p&gt;&lt;p&gt;Enter Marvin and Laura Horne, mom-and-pop raisin growers, who failed to turn over a stated portion of their crop, as required, to the Department of Agriculture&amp;rsquo;s Raisin Administrative Committee. (Who knew that raisin growers are required, by a Great Depression-era law, to turn over a percentage of their crop to the government? &lt;a href="http://www.gpo.gov/fdsys/pkg/USCOURTS-caed-1_08-cv-01549/pdf/USCOURTS-caed-1_08-cv-01549-5.pdf"&gt;Details here&lt;/a&gt; &amp;ndash; it&amp;rsquo;s worth the read, because you can&amp;rsquo;t make this stuff up.) The powers-that-be in the Agriculture Department were not pleased, and they brought the enforcement hammer down. The fines and penalties for the Hornes&amp;rsquo; alleged offense totaled more than $650,000.&lt;/p&gt;
&lt;p&gt;Mr. and Ms. Horne sought to challenge these sanctions, arguing in part that the requirement to surrender their raisins was an unconstitutional &amp;ldquo;taking&amp;rdquo; under the Fifth Amendment.&lt;/p&gt;
&lt;p&gt;Their dispute reached the U.S. Supreme Court on the question of how the Hornes could bring their case: (1) by a direct challenge through the routine federal courts (the Hornes&amp;rsquo; preference); or (2) by paying the fines and penalties and suing to get the money back in a different court under &lt;a href="http://en.wikipedia.org/wiki/Tucker_Act"&gt;the Tucker Act&lt;/a&gt;, which governs many kinds of claims against the federal government.&lt;/p&gt;
&lt;p&gt;The Ninth Circuit had concluded that, if the Hornes wanted to press their &amp;ldquo;taking&amp;rdquo; argument, they would have to do it under the Tucker Act &lt;i&gt;after&lt;/i&gt; paying the penalties because otherwise their claim, in an ironic turn of judicial phrase for a raisin-related case, would be &amp;ldquo;unripe&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.supremecourt.gov/opinions/12pdf/12-123_c07d.pdf"&gt;A unanimous Supreme Court&lt;/a&gt; reversed that holding. It found that the Hornes could and should have been permitted to make their &amp;ldquo;taking&amp;rdquo; argument in their direct challenge to the Agriculture Department&amp;rsquo;s enforcement efforts, rather than having to wait to raise that argument in a separate Tucker Act lawsuit after the fine was paid. The Supremes said in passing, and of interest to us:&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;In the case of an administrative enforcement proceed&amp;shy;ing, when a party raises a constitutional defense to an assessed fine, it would make little sense to require the party to pay the fine in one proceeding and then turn around and sue for recovery of that same money in another proceeding.&lt;/p&gt;
&lt;p&gt;The regulatory scheme (and related judicial review provisions) governing the raisin business are very different from those of the Communications Act, so it&amp;rsquo;s by no means a given that the Supreme Court&amp;rsquo;s decision will necessarily be applicable to FCC enforcement actions. But the quoted passage could arguably be read to apply in that context, at least where the target of an FCC fine mounts a constitutional defense. The &lt;i&gt;Horne&lt;/i&gt; case thus opens the possibility that an FCC forfeiture defendant &amp;ndash; especially one with a constitutional defense &amp;ndash; might get directly into the Court of Appeals without first paying the forfeiture. That could afford a small but important tilt in the balance between the FCC and the people it regulates.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/XoQGD8OhZLU" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/XoQGD8OhZLU/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/enforcement-activities-fines-f/raisin-defenses-at-the-fcc/</guid>
         <category domain="http://www.commlawblog.com/tags">Appeal of forfeiture orders</category><category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/articles">Cable</category><category domain="http://www.commlawblog.com/articles">Cellular</category><category domain="http://www.commlawblog.com/articles">Enforcement Activities (Fines, Forfeitures, etc.)</category><category domain="http://www.commlawblog.com/tags">Horne v. Dept. of Agriculture</category><category domain="http://www.commlawblog.com/tags">Raisin Administrative Committee</category><category domain="http://www.commlawblog.com/tags">Raisins</category><category domain="http://www.commlawblog.com/tags">Supreme Court</category><category domain="http://www.commlawblog.com/tags">Tucker Act</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category><category domain="http://www.commlawblog.com/articles">Wireline Telephony</category><category domain="http://www.commlawblog.com/tags">forfeitures</category>
         <pubDate>Fri, 14 Jun 2013 12:32:31 -0500</pubDate>
         <dc:creator>Jon Markman</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/enforcement-activities-fines-f/raisin-defenses-at-the-fcc/</feedburner:origLink></item>
            <item>
         <title>Update: Reconsideration Sought in Experimental Licensing Order</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Three petitions seek minor adjustments to rules.        &lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="90" vspace="5" hspace="5" height="104" align="left" src="http://www.commlawblog.com/uploads/image/experimental-1.JPG" alt="" /&gt;The FCC&amp;rsquo;s order from last January &lt;a href="http://www.commlawblog.com/2013/02/articles/unlicensed-operations-and-emer/fcc-overhauls-experimental-radio-rules/"&gt;expanding the scope of experimental licenses&lt;/a&gt; has drawn three petitions for reconsideration. Considering the broad reach of the order, the fact that only three were filed is a testament to the FCC&amp;rsquo;s foresight.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022419330"&gt;Sirius XM Radio and EchoStar Technologies&lt;/a&gt;, which provide satellite services to the public, seek a clarification and expansion of the term &amp;ldquo;emergency notifications,&amp;rdquo;&amp;nbsp;the bands for which receive special protection from experimental licensees.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022419313"&gt;Medtronic, Inc&lt;/a&gt;., which develops medical devices, wants expanded eligibility for Medical Testing Experimental Radio Licenses to include all sponsors and sponsor-investigators as defined by the FDA, and requests a clarification that cost reimbursement for clinical trials is not a violation of the equipment marketing rules.&lt;/p&gt;
&lt;p&gt;Our friend Michael Marcus of &lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022416291"&gt;Marcus Spectrum Solutions LLC&lt;/a&gt; wants the &amp;ldquo;passive bands,&amp;rdquo; including those used for radio astronomy, made available to experimental licensees at frequencies above 100 GHz.&lt;/p&gt;
&lt;p&gt;The FCC has put these on &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-321472A1.pdf"&gt;public notice&lt;/a&gt;. Comment due dates must await publication in the Federal Register. Watch this space.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/V5cQLygw91Y" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/V5cQLygw91Y/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/unlicensed-operations-and-emer/update-reconsideration-sought-in-experimental-licensing-order/</guid>
         <category domain="http://www.commlawblog.com/tags">Compliance Testing License</category><category domain="http://www.commlawblog.com/tags">EchoStar Technologies</category><category domain="http://www.commlawblog.com/tags">Experimental licensing</category><category domain="http://www.commlawblog.com/tags">Innovation Zones</category><category domain="http://www.commlawblog.com/tags">Marcus Spectrum Solutions</category><category domain="http://www.commlawblog.com/tags">Market Trials</category><category domain="http://www.commlawblog.com/tags">Medical Testing License</category><category domain="http://www.commlawblog.com/tags">Medtronic</category><category domain="http://www.commlawblog.com/tags">Michael Marcus</category><category domain="http://www.commlawblog.com/tags">Program Experimental License</category><category domain="http://www.commlawblog.com/tags">Sirius XM</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category>
         <pubDate>Wed, 12 Jun 2013 14:22:26 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/unlicensed-operations-and-emer/update-reconsideration-sought-in-experimental-licensing-order/</feedburner:origLink></item>
            <item>
         <title>Aero Freq Leaks: A Potentially Expensive Problem for Non-Cable MVPDs</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Citation issued to Florida motel serves as reminder of possible penalties for leaky cable systems.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img width="100" vspace="5" hspace="5" height="115" align="left" src="http://www.commlawblog.com/uploads/image/cable tv-1.JPG" alt="" /&gt;If you&amp;rsquo;re a school, or a hotel, or a hospital, or some other operation offering in-house cable TV service, you may be subject to a six-figure FCC fine, even though you might not think that you&amp;rsquo;re subject to the long arm of the FCC&amp;rsquo;s enforcement machine.&amp;nbsp; The Commission has been kind enough to issue us all a reminder of that &amp;ndash; in the form of a &amp;ldquo;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1339A1.pdf"&gt;Citation and Order&lt;/a&gt;&amp;rdquo; directed to the Parkway Inn Motel in sunny Miami Springs, Florida.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;From &lt;a href="http://www.parkwayinn-miami.com/"&gt;its website&lt;/a&gt; you might not think the Parkway Inn (Motto: &amp;ldquo;Your Satisfaction is our Main Purpose&amp;rdquo;) would attract the FCC&amp;rsquo;s attention, but it did.&amp;nbsp; According to FCC inspectors, the Parkway&amp;rsquo;s video system was leaking big-time (in one case by a factor of &lt;i&gt;more than 100 times&lt;/i&gt; the permitted level) on a couple of aeronautical frequencies.&amp;nbsp; Yikes!&lt;/p&gt;
&lt;p&gt;As our faithful readers may recall, last August &lt;a href="http://www.commlawblog.com/2012/08/articles/cable/fcc-to-noncable-mvpds-aero-freqs-no-leaks/"&gt;we reported on an FCC public notice&lt;/a&gt; warning &amp;ldquo;non-cable MVPDs&amp;rdquo; of their obligations relative to their useof aeronautical frequency bands.&amp;nbsp; The notice &amp;ndash; issued in connection with three separate citations notifying, respectively, an inn, an elder care facility, and a rehabilitation hospital, that they were all in violation of the rules &amp;ndash; was an effort to get the word out to other unsuspecting non-cable MVPDs.&lt;/p&gt;
&lt;p&gt;The FCC&amp;rsquo;s notice, and our related post, apparently weren&amp;rsquo;t entirely successful, since not everyone got the message &amp;ndash; at least the Parkway Inn Motel didn&amp;rsquo;t.&lt;/p&gt;&lt;p&gt;The FCC has warned the folks at the Parkway that they&amp;rsquo;re currently breaking the law and that, if they don&amp;rsquo;t fix things, they could be tapped for a fine of more than $100,000.&amp;nbsp; They&amp;rsquo;d have to sell a lot of potato chips out of their mini-bars to cover that.&lt;/p&gt;
&lt;p&gt;Since the FCC is clearly still targeting non-cable MVPDs, we figure it&amp;rsquo;s a good idea to provide a brief refresher course to help non-cable MVPDs recognize that they are, in fact, non-cable MVPDs, and that they need to take appropriate steps to avoid problems with the FCC.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;Am I a &amp;ldquo;non-cable MVPD&amp;rdquo;? &lt;/i&gt;&lt;/b&gt;You may be one, but not know it.&amp;nbsp; A non-cable MVPD is an entity (other than a cable TV company) that &amp;ldquo;engage[s] in the business of making available for purchase, by subscribers or customers, multiple channels of video programming.&amp;rdquo;&amp;nbsp; Generally, a non-cable MVPD system does not have to cross a public right of way to deliver its programming. This could include universities, hotels, apartment complexes, prisons, office buildings, and other facilities with in-house systems providing multiple channels of video programming available to subscribers or consumers.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;What are aeronautical frequencies, and what&amp;rsquo;s the problem?&lt;/i&gt;&lt;/b&gt;&amp;nbsp; The frequencies are the equivalent of analog cable channels 14-16, 25-53, and 98-99 (for the tech savvy, that&amp;rsquo;s 108-137 MHz and 225-400 MHz). They&amp;rsquo;re the same frequencies used by aircraft for certain operational functions.&amp;nbsp; Gaps in MVPD video systems could allow signals to leak out and interfere with the operation of nearby aircraft. That would not be a good thing.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;What are MVPDs supposed to do? &lt;/i&gt;&lt;/b&gt;&amp;nbsp;All MVPDs must notify the FCC (on Form 321) &lt;b&gt;&lt;i&gt;before&lt;/i&gt;&lt;/b&gt; they transmit on any of the aeronautical radio channels, if the average power level on any of those channels hits certain levels.&amp;nbsp; (The specifics of the leakage rules may be found in &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=aec37db57c764a291662f1b231609e5e&amp;amp;rgn=div6&amp;amp;view=text&amp;amp;node=47:4.0.1.1.4.11&amp;amp;idno=47"&gt;Sections 76.610- 76.616 of the rules&lt;/a&gt;; the monitoring and reporting rules are in &lt;a href="http://www.ecfr.gov/cgi-bin/retrieveECFR?gp=&amp;amp;SID=ca1ef8ad726dd7b67ae15cffbf42394d&amp;amp;r=SECTION&amp;amp;n=47y4.0.1.1.4.22.1.5"&gt;Section 76.1804&lt;/a&gt;.&amp;nbsp; Be warned, though &amp;ndash; those rules are highly technical.) In addition, all MVPDs must regularly &amp;ndash; at least once yearly &amp;ndash; monitor their systems for leakage in the aeronautical bands. Since that requires specialized monitoring equipment and a skilled technician, it&amp;rsquo;s easier said than done, but it must be done if an MVPD is to comply with its obligations (and avoid citations from the FCC).&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The moral of the story: if you&amp;rsquo;re a non-cable MVPD, consider yourself warned, again, about aeronautical frequency compliance issues.&amp;nbsp; Calls to an engineer to measure for spectrum leakage, and to a communications attorney, may be in order.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/dzL5ICHC4vM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/dzL5ICHC4vM/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/cable/aero-freq-leaks-a-potentially-expensive-problem-for-noncable-mvpds/</guid>
         <category domain="http://www.commlawblog.com/tags">
"Parkway</category><category domain="http://www.commlawblog.com/tags">108-137 MHz</category><category domain="http://www.commlawblog.com/tags">225-400 MHz</category><category domain="http://www.commlawblog.com/tags">Aeronautical frequencies</category><category domain="http://www.commlawblog.com/articles">Cable</category><category domain="http://www.commlawblog.com/articles">Enforcement Activities (Fines, Forfeitures, etc.)</category><category domain="http://www.commlawblog.com/tags">Form 320</category><category domain="http://www.commlawblog.com/tags">Form 321</category><category domain="http://www.commlawblog.com/tags">Inn</category><category domain="http://www.commlawblog.com/tags">Motel"</category><category domain="http://www.commlawblog.com/tags">Multichannel video programming distributor</category><category domain="http://www.commlawblog.com/tags">Non-cable MVPDs</category><category domain="http://www.commlawblog.com/tags">Section 76.611</category><category domain="http://www.commlawblog.com/tags">Signal leakage</category><category domain="http://www.commlawblog.com/tags">Universities</category>
         <pubDate>Tue, 11 Jun 2013 18:09:33 -0500</pubDate>
         <dc:creator>Paul J. Feldman</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/cable/aero-freq-leaks-a-potentially-expensive-problem-for-noncable-mvpds/</feedburner:origLink></item>
            <item>
         <title>Effective Date of Revised "Auditory Assistance Device" Rules Set</title>
         <description>&lt;p&gt;&lt;img width="65" vspace="5" hspace="5" height="90" align="left" src="http://www.commlawblog.com/uploads/image/dictionary - language-1.JPG" alt="" /&gt;&lt;a href="http://www.commlawblog.com/2013/05/articles/unlicensed-operations-and-emer/help-for-the-languageimpaired/"&gt;Last month we reported&lt;/a&gt; on an &lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0502/FCC-13-59A1.pdf"&gt;FCC decision&lt;/a&gt; to allow the use of Auditory Assistance Devices for simultaneous language translation.&amp;nbsp;That decision &amp;ndash; which involved some technical rule changes as well as the expansion of permissible uses to include translation &amp;ndash; has now been &lt;a href="http://www.gpo.gov/fdsys/pkg/FR-2013-06-11/pdf/2013-13696.pdf"&gt;published in the Federal Register&lt;/a&gt;, which means that the effective date of the new rules has been established.&amp;nbsp;That effective date is &lt;b&gt;&lt;i&gt;July 11, 2013&lt;/i&gt;&lt;/b&gt;.&amp;nbsp; Use of 72-76 MHz band devices for language translation will be permitted as of that date.&amp;nbsp; The technical rule changes -- which require compliance with tighter out-of-band emission limits -- will apply to new equipment certification applications filed on or after January 11, 2015, and to importation, marketing and installation on or after July 11, 2016.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/CxsV-NDPx1Q" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/CxsV-NDPx1Q/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/unlicensed-operations-and-emer/effective-date-of-revised-auditory-assistance-device-rules-set/</guid>
         <category domain="http://www.commlawblog.com/tags">72-76 MHz band</category><category domain="http://www.commlawblog.com/tags">Assistive listening device</category><category domain="http://www.commlawblog.com/tags">Auditory assistance device</category><category domain="http://www.commlawblog.com/tags">Handicap</category><category domain="http://www.commlawblog.com/tags">Hard of hearing</category><category domain="http://www.commlawblog.com/tags">Hearing impaired</category><category domain="http://www.commlawblog.com/tags">Part 15</category><category domain="http://www.commlawblog.com/tags">Simultaneous language translation</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/tags">Williams Sound</category>
         <pubDate>Tue, 11 Jun 2013 04:36:43 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/unlicensed-operations-and-emer/effective-date-of-revised-auditory-assistance-device-rules-set/</feedburner:origLink></item>
            <item>
         <title>Update: Comment Periods in Receiver Standards Inquiry Extended</title>
         <description>&lt;p&gt;&lt;img width="90" vspace="5" hspace="5" height="104" align="left" src="http://www.commlawblog.com/uploads/image/experimental-1.JPG" alt="" /&gt;&lt;a href="http://www.commlawblog.com/2013/05/articles/deadlines/fcc-seeks-comment-on-receiver-standards-again/"&gt;Last month we noted&lt;/a&gt; that the FCC (through its Office of Engineering and Technology) had &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-801A1.pdf"&gt;requested comment on a white paper&lt;/a&gt; concerning technical standards for radio receivers, produced by its Technological Advisory Committee and entitled &amp;ldquo;&lt;a href="http://transition.fcc.gov/bureaus/oet/tac/tacdocs/WhitePaperTACInterferenceLimitsv1.0.pdf"&gt;Interference Limits Policy: The use of harm claim thresholds to improve the interference tolerance of wireless systems&lt;/a&gt;.&amp;rdquo;&amp;nbsp;The basic idea is to add flexibility to the notion of &amp;ldquo;interference&amp;rdquo; from a nearby band.&lt;/p&gt;
&lt;p&gt;The questions posed in the white paper are a matter of potentially major consequence.&amp;nbsp;Probably because of that, three entities that have occasionally found themselves at odds on a number of substantive regulatory issues found common ground here, at least with respect to the need for more time to respond to the FCC&amp;rsquo;s invitation for comments: the National Association of Broadcasters, the Consumer Electronics Association, and the GPS Innovation Alliance filed a joint request for more time.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1344A1.pdf"&gt;That request has been granted&lt;/a&gt;.&amp;nbsp;As a result, comments are now due by &lt;b&gt;&lt;i&gt;July 22, 2013&lt;/i&gt;&lt;/b&gt; and reply comments by &lt;b&gt;&lt;i&gt;August 7&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/6F_WKov4wAI" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/6F_WKov4wAI/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/broadcast/update-comment-periods-in-receiver-standards-inquiry-extended/</guid>
         <category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/articles">Cellular</category><category domain="http://www.commlawblog.com/tags">Receiver selectivity</category><category domain="http://www.commlawblog.com/tags">Technical Advisory Committee</category><category domain="http://www.commlawblog.com/tags">Technical receiver standards</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category>
         <pubDate>Mon, 10 Jun 2013 13:49:37 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/broadcast/update-comment-periods-in-receiver-standards-inquiry-extended/</feedburner:origLink></item>
            <item>
         <title>Quad Erat Demonstrandum? FCC Seeks Comment on MMTC Study</title>
         <description>&lt;p&gt;&lt;img width="100" vspace="5" hspace="5" height="96" align="left" alt="" src="http://www.commlawblog.com/uploads/image/sisyphus.JPG" /&gt;Despite the FCC&amp;rsquo;s efforts in its 2002 and 2006 quadrennial review proceedings to relax (or maybe even eliminate) its newspaper-broadcast cross-ownership (NBCO) prohibition, that prohibition is still alive and kicking after nearly 40 years.&amp;nbsp;In the 2010 quadrennial the NBCO is again in the Commission&amp;rsquo;s sights.&amp;nbsp;And now the Minority Media and Telecommunications Council (MMTC) has provided arguable impetus for the Commission to try to pull the trigger, again.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022419395"&gt;MMTC has submitted&lt;/a&gt; a specially-commissioned study entitled &lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022419396"&gt;&amp;ldquo;The Impact of Cross Media Ownership on Minority/Women Owned Broadcast Stations&amp;rdquo;&lt;/a&gt; (Study).&amp;nbsp;Prepared by well-respected BIA/Kelsey Chief Economist Mark Fratrik, the Study presents evidence that &amp;ldquo;the impact of cross-media ownership on minority and women broadcast ownership is probably negligible&amp;rdquo;.&amp;nbsp;In other words, the Commission could probably dump the NBCO without having to worry about adversely affecting minority- or female-owned stations.&amp;nbsp;Since the FCC&amp;rsquo;s 2002 and 2006 quad efforts were criticized (by, among others, &lt;a href="http://www.commlawblog.com/2011/07/articles/broadcast/the-third-circuit-strikes-again/"&gt;the U.S. Court of Appeals for the Third Circuit&lt;/a&gt;) because of the Commission&amp;rsquo;s supposed lack of attention to minority/female considerations, the Study helps fill in that arguable gap.&lt;/p&gt;
&lt;p&gt;Based on questionnaire responses provided by only a relatively limited sample of broadcast stations, the Study is, by its own terms, &amp;ldquo;not dispositive&amp;rdquo;.&amp;nbsp;Still, in light of its sponsor and its author, it may be viewed as a significant contribution to the record.&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1317A2.pdf"&gt;FCC has invited public input&lt;/a&gt; on the Study.&amp;nbsp;Comments are due by &lt;b&gt;&lt;i&gt;July 22, 2013&lt;/i&gt;&lt;/b&gt;; reply comments by &lt;b&gt;&lt;i&gt;August 6&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/mtGKx-dtXPc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/mtGKx-dtXPc/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/deadlines/quad-erat-demonstrandum-fcc-seeks-comment-on-mmtc-study/</guid>
         <category domain="http://www.commlawblog.com/tags">BIA/Kelsey</category><category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/tags">MMTC</category><category domain="http://www.commlawblog.com/tags">MMTC Cross-Ownership Study</category><category domain="http://www.commlawblog.com/tags">Mark Fratrik</category><category domain="http://www.commlawblog.com/tags">Media attribution</category><category domain="http://www.commlawblog.com/tags">Minority Media and Telecommunications Council</category><category domain="http://www.commlawblog.com/tags">Newspaper-broadcast cross-ownership</category><category domain="http://www.commlawblog.com/tags">Ownership limits</category><category domain="http://www.commlawblog.com/tags">Quadrennial Review</category><category domain="http://www.commlawblog.com/tags">Supreme Court</category><category domain="http://www.commlawblog.com/tags">Third Circuit</category>
         <pubDate>Sun, 09 Jun 2013 14:40:05 -0500</pubDate>
         <dc:creator>Harry Cole</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/deadlines/quad-erat-demonstrandum-fcc-seeks-comment-on-mmtc-study/</feedburner:origLink></item>
            <item>
         <title>FCC Authorizes Progeny over Part 15 Objections</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Location service company is deemed to have satisfied the requirement that it not cause unacceptable interference to unlicensed devices.    &lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="150" vspace="5" hspace="5" height="147" align="left" alt="" src="http://www.commlawblog.com/uploads/image/rubber stamp-1.JPG" /&gt;&lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-13-78A1.pdf"&gt;The FCC has authorized Progeny LMS, LLC&lt;/a&gt; to begin commercial operation of its Location and Monitoring Service (LMS) network. Progeny&amp;rsquo;s system uses part of the 902-928 MHz band, which is heavily occupied by unlicensed devices regulated under Part 15 of the FCC rules. The FCC action came over vigorous objection from the companies that make and use Part 15 equipment.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;So what?&amp;rdquo; knowledgeable readers will ask. After all, unlicensed devices always have to accept interference from licensed services like LMS.&lt;/p&gt;
&lt;p&gt;Not quite always. When the FCC authorized LMS back in 1995, the 902-928 MHz band was already home to a very large array of unlicensed devices serving both consumers and industry. (Their number, variety, and importance have increased many-fold in the years since.) To ensure that LMS did not obliterate unlicensed usage, the FCC adopted a &lt;a href="http://www.ecfr.gov/cgi/t/text/text-idx?c=ecfr&amp;amp;SID=1f099c44f53e2314f15d5a52e7541b63&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:5.0.1.1.3.12.111.3&amp;amp;idno=47"&gt;unique rule&lt;/a&gt;: certain LMS licenses are &amp;ldquo;conditioned upon the licensee&amp;rsquo;s ability to demonstrate through actual field tests that their systems do not cause unacceptable levels of interference to [Part 15] devices.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Fast forward to 2011, when LMS licensee Progeny requested and &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-2036A1.pdf"&gt;was granted a waiver&lt;/a&gt; that permitted one-way service and the location of assets other than vehicles. The waiver grant re-triggered the field testing requirement. Progeny conducted four sets of tests and submitted the results to the FCC, which then duly &lt;a href="http://www.commlawblog.com/2012/02/articles/unlicensed-operations-and-emer/fcc-seeks-comment-on-interference-into-unlicensed-devices/"&gt;requested comments&lt;/a&gt; about the results. Providers of unlicensed wireless Internet service and manufacturers of unlicensed automatic meter reading equipment &amp;ndash; both of which require reliable operation &amp;ndash; &lt;a href="http://www.commlawblog.com/2012/04/articles/unlicensed-operations-and-emer/controversy-flares-over-interference-to-unlicensed-devices/"&gt;challenged the conclusions&lt;/a&gt;. They claimed the tests used too few unlicensed devices, non-representative devices, and conditions artificially rigged to understate interference.&lt;/p&gt;&lt;p&gt;At the request of the FCC staff, Progeny and some of the Part 15 interests conducted &lt;a href="http://www.commlawblog.com/2012/11/articles/unlicensed-operations-and-emer/tests-show-threat-to-900-mhz-unlicensed-band-or-do-they/"&gt;further tests&lt;/a&gt; on meter-reading and Internet delivery equipment. The FCC &lt;a href="http://www.commlawblog.com/2012/11/articles/unlicensed-operations-and-emer/update-progeny-vs-unlicensed-users-fcc-invites-public-comment/"&gt;requested further comment&lt;/a&gt;. Again, the two sides disagreed on how to interpret the results. Along with claiming actual interference, the Part 15 companies continued to insist that Progeny&amp;rsquo;s tests omitted a large range of unlicensed devices and conditions, and that more testing is needed to properly evaluate the impact of Progeny&amp;rsquo;s transmitters.&lt;/p&gt;
&lt;p&gt;The FCC has now &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-13-78A1.pdf"&gt;dismissed those arguments&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Part of the dispute turns on the requirement that Progeny not cause &amp;ldquo;unacceptable levels&amp;rdquo; of interference to unlicensed devices. The FCC has never before spelled out what that means. Now, it tells us the &amp;ldquo;unacceptable levels&amp;rdquo; limitation calls on LMS licensees merely to &amp;ldquo;minimize&amp;rdquo; interference to Part 15, but not necessarily to eliminate it altogether. A different reading, says the FCC, would elevate Part 15 in status above LMS, which the rules never intended. Moreover, the FCC goes on, unlicensed users should know to expect some level of interference, and have the option of using equipment that is capable of shifting to other parts of the band when needed. Progeny need not test with every type of Part 15 device, the FCC adds, as that could result in endless rounds of testing.&lt;/p&gt;
&lt;p&gt;Progeny offered to: report periodically on its build-out and any interference complaints it receives; establish a toll-free help desk for Part 15 users experiencing interference; and, if it constructs in rural areas, work with local wireless Internet service providers on mitigating interference. The FCC required the first two conditions and encouraged the third.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;Editorial comment&lt;/i&gt;&lt;/b&gt;: The enormous success of the FCC&amp;rsquo;s rules permitting &amp;ndash; indeed, promoting &amp;ndash; unlicensed operations has, ironically, caused problems for the agency. When the most-used parts of the current regime took effect in 1985, no one dreamed that unlicensed radio devices would become as prevalent as they are now. Because these devices have always been required to accept interference, the initial uses focused on applications that did not require great reliability. But as the decades went by, and the technologies used in Part 15 equipment evolved to become more robust against interference, the devices found use in more critical applications, including the control of overhead cranes, pipeline systems, and electric utilities.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Robust,&amp;rdquo; though, is a relative term. Equipment that works perfectly well in the pre-existing 902-928 MHz environment of ISM, federal radar, amateur radio, and other Part 15 devices may falter when exposed to new interference sources, such as LMS. Yes, the rules say Part 15 users must accept interference and operate at their own risk; and yes, Progeny has a legal right to deploy, if it satisfies the field test requirement. Still, Part 15 equipment has become so important to so many industries &amp;ndash; and to the economy generally &amp;ndash; that it may have earned a higher status in the spectrum.&lt;/p&gt;
&lt;p&gt;(FHH represented clients in this proceeding.)&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/6gXqi8Srrao" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/6gXqi8Srrao/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/unlicensed-operations-and-emer/fcc-authorizes-progeny-over-part-15-objections/</guid>
         <category domain="http://www.commlawblog.com/tags">902-928 MHz</category><category domain="http://www.commlawblog.com/tags">Itron</category><category domain="http://www.commlawblog.com/tags">LMS</category><category domain="http://www.commlawblog.com/tags">Landis+Gyr</category><category domain="http://www.commlawblog.com/tags">Location and Monitoring Service</category><category domain="http://www.commlawblog.com/tags">Progeny LMS, LLC</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/tags">WISPA</category><category domain="http://www.commlawblog.com/tags">Wireless Internet Service Providers Association</category>
         <pubDate>Sat, 08 Jun 2013 13:24:41 -0500</pubDate>
         <dc:creator>Mitchell Lazarus</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/unlicensed-operations-and-emer/fcc-authorizes-progeny-over-part-15-objections/</feedburner:origLink></item>
            <item>
         <title>Internet-on-Airplanes: Comments Due on Reconsideration Request</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Open issues concern licensing, earth station technical requirements.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="126" vspace="5" hspace="5" height="103" align="left" src="http://www.commlawblog.com/uploads/image/plane radar-3.jpg" alt="" /&gt;People who like to watch &lt;a href="http://m.wimp.com/scarythings/"&gt;silly cat videos&lt;/a&gt; on airplanes no doubt were pleased with the FCC&amp;rsquo;s &lt;a href="http://www.commlawblog.com/2012/12/articles/internet/fcc-boots-up-internet-service-in-airplanes/"&gt;decision last December &lt;/a&gt;that regularized satellite service to and from aircraft in flight. No doubt even more pleased are the satellite providers, which now have access to a promising market: bored people strapped into their seats without much else to do.&lt;/p&gt;
&lt;p&gt;Aircraft manufacturers, too, are enthusiastic about the prospect of the new service &amp;ndash; at least, the folks at Boeing are. So much so that they have filed a &lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022113676"&gt;petition for reconsideration and clarification&lt;/a&gt; &amp;ldquo;applaud[ing]&amp;rdquo; the Commission for its Earth Stations Aboard Aircraft initiative, but asking for several tweaks to the rules on licensing requirements and earth station technical specifics. Thanks to a &lt;a href="http://www.gpo.gov/fdsys/pkg/FR-2013-06-07/pdf/2013-13529.pdf"&gt;notice in the Federal Register&lt;/a&gt;, we can tell you that comments on the requested changes are due on &lt;b&gt;&lt;i&gt;June 24, 2013&lt;/i&gt;&lt;/b&gt; and reply comments on &lt;b&gt;&lt;i&gt;July 2&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/Pqwag2U1AzY" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/Pqwag2U1AzY/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/wireless-telephony/internetonairplanes-comments-due-on-reconsideration-request/</guid>
         <category domain="http://www.commlawblog.com/tags">10.95-11.2 GHz</category><category domain="http://www.commlawblog.com/tags">11.45-11.7 GHz</category><category domain="http://www.commlawblog.com/tags">11.7-12.2 GHz</category><category domain="http://www.commlawblog.com/tags">4.0-14.5 GHz</category><category domain="http://www.commlawblog.com/tags">ESAA</category><category domain="http://www.commlawblog.com/tags">Earth Stations Aboard Aircraft</category><category domain="http://www.commlawblog.com/tags">FSS</category><category domain="http://www.commlawblog.com/tags">Fixed Satellite Service</category><category domain="http://www.commlawblog.com/tags">Internet service on aircraft</category><category domain="http://www.commlawblog.com/tags">Internet-on-Airplanes</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category>
         <pubDate>Fri, 07 Jun 2013 08:55:33 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/wireless-telephony/internetonairplanes-comments-due-on-reconsideration-request/</feedburner:origLink></item>
            <item>
         <title>Health Effects of Radio Waves: Effective Date of New Rules Set, Also Comment Deadlines</title>
         <description>&lt;p&gt;&lt;img width="175" vspace="5" hspace="5" height="175" align="left" alt="" src="http://www.commlawblog.com/uploads/image/FCC RF NOI-1.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.commlawblog.com/2013/04/articles/cellular/fcc-looks-at-health-effects-of-radio-waves/"&gt;Back in April we reported&lt;/a&gt; on the &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-13-39A1.pdf"&gt;FCC&amp;rsquo;s most recent foray&lt;/a&gt; into the thorny issue of health effects of radio waves.&amp;nbsp;The FCC adopted minor tweaks to its existing rules, proposed further tweaks, and sought comments on broader issues, including the controversial question of whether the current radio-frequency exposure limits are safe, and if not, what they should be.&lt;/p&gt;
&lt;p&gt;The document has now been published in the Federal Register, in two separate parts. The &lt;a href="http://www.gpo.gov/fdsys/pkg/FR-2013-06-04/pdf/2013-12716.pdf"&gt;first part&lt;/a&gt; sets out the newly adopted rules; the &lt;a href="http://www.gpo.gov/fdsys/pkg/FR-2013-06-04/pdf/2013-12713.pdf"&gt;second part&lt;/a&gt; poses the questions on which the Commission has requested comment.&lt;/p&gt;
&lt;p&gt;Publication in the Federal Register establishes both (a) the effective date of the rule changes that were adopted and (b) the deadlines for comments on the out-for-comment questions.&amp;nbsp;The adopted changes will become effective on &lt;b&gt;&lt;i&gt;August 5, 2013&lt;/i&gt;&lt;/b&gt;.&amp;nbsp;Comments will be due on &lt;b&gt;&lt;i&gt;September 3, 2013&lt;/i&gt;&lt;/b&gt;, and reply comments on &lt;b&gt;&lt;i&gt;November 1&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/uPnfcOfkPik" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/uPnfcOfkPik/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/deadlines/health-effects-of-radio-waves-effective-date-of-new-rules-set-also-comment-deadlines/</guid>
         <category domain="http://www.commlawblog.com/articles">Cellular</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/tags">Health effects of radiofrequency</category><category domain="http://www.commlawblog.com/tags">OET Bulletin 65 Supplement C</category><category domain="http://www.commlawblog.com/tags">RF</category><category domain="http://www.commlawblog.com/tags">Radiofrequency</category><category domain="http://www.commlawblog.com/tags">Radiofrequency exposure limits</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category>
         <pubDate>Tue, 04 Jun 2013 04:15:43 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/deadlines/health-effects-of-radio-waves-effective-date-of-new-rules-set-also-comment-deadlines/</feedburner:origLink></item>
            <item>
         <title>FEMA WEA PSA's 'R' OK!</title>
         <description>&lt;p&gt;&lt;b&gt;&lt;i&gt;In response to non-request for waiver, Public Safety and Homeland Security Bureau waives rules that may not need to be waived.&lt;/i&gt;&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="125" vspace="5" hspace="5" height="134" align="left" src="http://www.commlawblog.com/uploads/image/thumbs up-1.JPG" alt="" /&gt;Broadcasters may be asked (many apparently already have been asked) by the Federal Emergency Management Agency (FEMA) to broadcast some PSA&amp;rsquo;s relating to the (relatively) new Wireless Emergency Alert (WEA) system.&amp;nbsp;While some broadcasters have reacted to that request with understandable &amp;ndash; and legitimate &amp;ndash; reluctance, the FCC&amp;rsquo;s &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1301A1.pdf"&gt;Public Safety and Homeland Security Bureau has now assured us that the PSA&amp;rsquo;s are OK for broadcast&lt;/a&gt;. . . as long as certain conditions are met.&lt;/p&gt;
&lt;p&gt;The bottom line here is relatively simple; getting there, though, requires a surprising amount of explanation.&lt;/p&gt;
&lt;p&gt;For years, FEMA and the FCC and others have been working to improve the overall ability of government officials to alert the citizenry to emergency situations.&amp;nbsp;&amp;nbsp; Broadcasters have observed one aspect of that effort in the &lt;a href="http://www.commlawblog.com/2012/02/articles/broadcast/fcc-addresses-captosame-conversion-other-eas-issues/"&gt;overhaul of the Emergency Alert System&lt;/a&gt;. &amp;nbsp;On the non-broadcast side, the FCC established the WEA system, through which the guv&amp;rsquo;mint can send geographically-targeted emergency messages direct to individuals&amp;rsquo; mobile devices.&amp;nbsp;The WEA has already been triggered in a wide range of situations &amp;ndash; hurricanes, tornadoes, terrorist threats, missing persons, etc. &amp;ndash; and has, according to the FCC, &amp;ldquo;proven to be a valuable tool&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;So what&amp;rsquo;s the problem?&lt;/p&gt;&lt;p&gt;When the WEA system is triggered, it sends out an &amp;ldquo;Attention Signal&amp;rdquo; to all mobile devices serviced by carriers participating in the system.&amp;nbsp;That signal apparently sounds an awful lot like the standard two-tone EAS signal familiar to the broadcast audience.&amp;nbsp;In addition, the signal is accompanied by a unique &amp;ldquo;vibration cadence&amp;rdquo; (we don&amp;rsquo;t know exactly what that feels like, but it&amp;rsquo;s probably worth checking out on a number of levels).&amp;nbsp;The goal, obviously, is to get the attention of the person with the mobile device.&lt;/p&gt;
&lt;p&gt;The good news is that the attention signal apparently works because it gets the user&amp;rsquo;s attention.&amp;nbsp;The bad news is that a lot of users apparently don&amp;rsquo;t want their attention to be gotten.&amp;nbsp;FEMA reports that &amp;ldquo;many people are startled or annoyed when hearing the WEA attention signal for the first time&amp;rdquo; and, worse yet, many have inquired about &amp;ldquo;opting-out&amp;rdquo; of the WEA system.&lt;/p&gt;
&lt;p&gt;What&amp;rsquo;s an agency to do?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The answer is obvious: Prepare a bunch of PSA&amp;rsquo;s to convince the (supposedly) &amp;ldquo;confused&amp;rdquo; and (certainly) &amp;ldquo;annoyed&amp;rdquo; Great Unwashed that, rather than opting out, they should embrace the WEA Attention Signal.&amp;nbsp;And how better to do that than to include the Attention Signal itself within the PSA?&lt;/p&gt;
&lt;p&gt;Experienced broadcasters will see where this is going.&lt;/p&gt;
&lt;p&gt;It is well-established &amp;ndash; in &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=5ab4332823128dfa8b5695630028007c&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:1.0.1.1.12.3.231.5&amp;amp;idno=47"&gt;Section 11.45 of the rules&lt;/a&gt; &amp;ndash; that broadcasters are &lt;b&gt;&lt;i&gt;not&lt;/i&gt;&lt;/b&gt; supposed to broadcast EAS tones except in times of true emergency (or in connection with routine EAS tests). &amp;nbsp;(Rationale: The FCC does not want to &amp;ldquo;dissipate[ ]&amp;rdquo; the &amp;ldquo;attention grabbing value&amp;rdquo; of the alert.) &amp;nbsp;But there is no corresponding prohibition against broadcasting WEA Attention Signals.&amp;nbsp;The closest rule on that score is &lt;a href="http://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&amp;amp;SID=ff0d03c89381d657020bed96a279ee4d&amp;amp;rgn=div8&amp;amp;view=text&amp;amp;node=47:1.0.1.1.11.5.231.3&amp;amp;idno=47"&gt;Section 10.520&lt;/a&gt;, which says nothing at all about broadcasting.&amp;nbsp;Still, because WEA signals so closely resemble EAS tones, a number of broadcasters presumably didn&amp;rsquo;t want to take the chance that the WEA signal might be mistaken for the EAS tones, leading to forfeiture notices and other unpleasantness.&amp;nbsp;So they told FEMA &amp;ldquo;thanks but no thanks&amp;rdquo; when asked to air the FEMA PSA&amp;rsquo;s that included the WEA signals.&amp;nbsp;The utility of the PSA component of FEMA&amp;rsquo;s effort to win public buy-in for the WEA system was thus threatened.&lt;/p&gt;
&lt;p&gt;Since the problem appeared to arise from the FCC&amp;rsquo;s rules, FEMA wrote to the Bureau, asking for its &amp;ldquo;support in allaying the concerns . . . about playing a PSA that includes&amp;rdquo; the Attention Signal.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Bureau, happy to play ball with FEMA, has agreed essentially to waive whatever rules might need to be waived to encourage the broadcast of the PSA&amp;rsquo;s.&lt;/p&gt;
&lt;p&gt;The result is an interesting exercise in bureaucratic contortionism.&amp;nbsp;Consider these elements:&amp;nbsp;First, FEMA&amp;rsquo;s letter did not include any explicit request for any waivers; rather it just asked for the Bureau&amp;rsquo;s support.&amp;nbsp;Second, the lack of a waiver request makes sense because there is no regulatory prohibition against the broadcast of WEA Attention Signals, so no waiver was technically necessary.&amp;nbsp;Third, the Bureau&amp;rsquo;s goal here appears to be to convince broadcasters that they can and should ignore the instinct that screams &amp;ldquo;Danger &amp;ndash; Likely Rule Violation Dead Ahead&amp;rdquo;, an instinct you&amp;rsquo;d think the FCC would want to encourage.&amp;nbsp;And fourth, FEMA (with the Bureau&amp;rsquo;s help) is trying to convince people that they really shouldn&amp;rsquo;t be annoyed or confused when their mobile devices suddenly start to emit annoying and confusing signals.&lt;/p&gt;
&lt;p&gt;The bottom line?&amp;nbsp;An artful paragraph in which, on its own motion, the Bureau has granted&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;a limited waiver of Sections 11.45 and 10.520 of the Commission&amp;rsquo;s rules, for a period of one year from the release date of this Order, to allow the broadcast or transmission of the WEA Attention Signal in PSAs produced as part of FEMA&amp;rsquo;s WEA public education campaign. In doing so, we recommend that FEMA take steps to ensure that such PSAs clearly state that they are part of FEMA&amp;rsquo;s public education campaign.&lt;/p&gt;
&lt;p&gt;The Bureau also cautioned that, in order to be permissible, FEMA&amp;rsquo;s PSA&amp;rsquo;s should not &amp;ldquo;predictably lead the public into concluding that an actual alert is being transmitted&amp;rdquo;.&amp;nbsp;Example?&amp;nbsp;&amp;ldquo;[L]eading off a PSA with a WEA Attention Signal, without warning.&amp;rdquo;&amp;nbsp;The Bureau concedes that that could be &amp;ldquo;an effective attention-getting device&amp;rdquo;, but it&amp;rsquo;s nevertheless &lt;i&gt;verboten&lt;/i&gt; because of the &amp;ldquo;predictable effect it could have&amp;rdquo; on the audience.&lt;/p&gt;
&lt;p&gt;As silly as this bureaucratic dance might seem, the government&amp;rsquo;s heart is in the right place here.&amp;nbsp;With mounting meteorological devastation across the country, not to mention potentially catastrophic accidents (&lt;i&gt;e.g.&lt;/i&gt;, three major railroad incidents in less than two weeks) and the constant threat of terrorism, the government&amp;rsquo;s ability to notify citizens of imminent danger is a matter of some legitimate urgency.&amp;nbsp;That being the case, though, you might have thought that FEMA and the FCC would have worked out such details as public promotion of its WEA program &lt;i&gt;before&lt;/i&gt; launching the program.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/yWXV5MyWpxs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/yWXV5MyWpxs/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/06/articles/broadcast/fema-wea-psas-r-ok/</guid>
         <category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/articles">Cellular</category><category domain="http://www.commlawblog.com/articles">Enforcement Activities (Fines, Forfeitures, etc.)</category><category domain="http://www.commlawblog.com/tags">FEMA</category><category domain="http://www.commlawblog.com/tags">Federal Emergency Management Agency</category><category domain="http://www.commlawblog.com/tags">PSA</category><category domain="http://www.commlawblog.com/tags">WEA Attention Signal</category><category domain="http://www.commlawblog.com/tags">Wireless Emergency Alert</category><category domain="http://www.commlawblog.com/articles">Wireless Telephony</category>
         <pubDate>Sat, 01 Jun 2013 22:29:51 -0500</pubDate>
         <dc:creator>Harry Cole</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/06/articles/broadcast/fema-wea-psas-r-ok/</feedburner:origLink></item>
            <item>
         <title>FCC Bars Transfer of New Kinds of Experimental License</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;The task of ascertaining eligibility is sufficiently complex that the FCC would rather start fresh with an application for a new license.    &lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="100" hspace="5" height="116" align="left" src="http://www.commlawblog.com/uploads/image/experimental-1.JPG" alt="" /&gt;Last February, when the FCC overhauled its rules to create &lt;a href="http://www.commlawblog.com/2013/02/articles/unlicensed-operations-and-emer/fcc-overhauls-experimental-radio-rules/"&gt;new kinds of experimental licenses&lt;/a&gt;, it omitted mention of whether the licenses could be transferred to another party, as by assignment or transfer of control. Now &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-13-76A1.pdf"&gt;the FCC has spoken&lt;/a&gt;. The answer is no.&lt;/p&gt;
&lt;p&gt;The February order set up three new categories:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&amp;quot;program experimental licenses&amp;quot; for certain colleges and universities, research laboratories, manufacturers, and health care institutions;&lt;/li&gt;
    &lt;li&gt;&amp;quot;compliance testing licenses&amp;quot; for FCC-recognized test labs; and&lt;/li&gt;
    &lt;li&gt;&amp;quot;medical testing licenses&amp;quot; for health care facilities conducting clinical trials of wireless medical technologies.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each of these categories has its own stringent standards for eligibility. None has yet taken effect, pending approval by the Office of Management and Budget. (The FCC left unchanged the current species of experimental license, which is available to pretty much anyone.)&lt;/p&gt;
&lt;p&gt;The FCC has now decided that licenses in the three new categories may &lt;b&gt;&lt;i&gt;not&lt;/i&gt;&lt;/b&gt; be assigned or transferred. The task of ascertaining eligibility is sufficiently complex that the FCC would rather start fresh with an application for a new license.&lt;/p&gt;
&lt;p&gt;The ruling sets up a potentially deadly trap for companies that acquire others, or that transfer technology-related assets. Ordinarily the two companies&amp;rsquo; lawyers go through a well-worn routine of filing requests to assign or transfer two-way radio licenses, FCC certifications, and various other commonplace authorizations. (Transactions involving broadcast, satellite, and some wireless licenses are more complex.) Now, though the acquiring company may have to take on the additional step of applying anew for its own program experimental, compliance testing, or medical testing license. Processing at the FCC may take time. Worse, we can foresee situations in which the acquiring company may not qualify for the license.&lt;/p&gt;
&lt;p&gt;Our best advice: plan ahead.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/wmbLwNHdje8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/wmbLwNHdje8/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/05/articles/unlicensed-operations-and-emer/fcc-bars-transfer-of-new-kinds-of-experimental-license/</guid>
         <category domain="http://www.commlawblog.com/tags">Compliance Testing License</category><category domain="http://www.commlawblog.com/tags">Experimental licensing</category><category domain="http://www.commlawblog.com/tags">Innovation Zones</category><category domain="http://www.commlawblog.com/tags">Market Trials</category><category domain="http://www.commlawblog.com/tags">Medical Testing License</category><category domain="http://www.commlawblog.com/tags">Program Experimental License</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category>
         <pubDate>Thu, 30 May 2013 19:36:08 -0500</pubDate>
         <dc:creator>Mitchell Lazarus</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/05/articles/unlicensed-operations-and-emer/fcc-bars-transfer-of-new-kinds-of-experimental-license/</feedburner:origLink></item>
            <item>
         <title>LoPo TV Warning: White Space Devices Are Coming - Have You Updated Your CDBS Information?</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Special CDBS website unveiled as FCC tries to help rebroadcasting low power stations secure the protection to which they&amp;rsquo;re entitled.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="100" vspace="5" hspace="5" height="139" align="left" alt="" src="http://www.commlawblog.com/uploads/image/shield-1.JPG" /&gt;If you&amp;rsquo;re the licensee of an LPTV or a TV Translator or a Class A TV station &amp;ndash; collectively for our purposes here, &amp;ldquo;low power stations&amp;rdquo; &amp;ndash; that rebroadcasts the over-the-air signal of another station, the FCC&amp;rsquo;s trying to help you out.&amp;nbsp;&amp;nbsp; In the near future, TV white space devices will take to the air, creating a potential source of interference to your ability to receive the signals you rebroadcast.&amp;nbsp;As the FCC proceeds with &lt;a href="http://www.commlawblog.com/2009/12/articles/unlicensed-operations-and-emer/get-out-your-crayons-and-glue-stick-its-designadatabase-time/"&gt;tests of databases&lt;/a&gt; to control those white space devices, it has simplified the steps necessary to ensure the protection to which you are entitled from those devices.&lt;/p&gt;
&lt;p&gt;White space devices, as we hope you know by now, operate in locally vacant TV channels.&amp;nbsp;They are required to protect not only household TV reception but also various other facilities, including some (but &lt;i&gt;not&lt;/i&gt; all) low power stations that rebroadcast the signals of other TV stations.&amp;nbsp;These stations receive two kinds of protection.&amp;nbsp;White space devices (except for those at very low power) are not permitted to operate inside or close to the stations&amp;rsquo; service contours &amp;ndash; a matter not at issue here.&amp;nbsp;Also protected, and the subject of this post, are the &lt;i&gt;receivers&lt;/i&gt; these stations use to pick up the signal of the originating station for rebroadcast.&lt;/p&gt;
&lt;p&gt;White space devices will have to consult a special database to identify available channels.&amp;nbsp;That database in turn will draw on CDBS to identify low-power stations whose receivers are entitled to protection.&lt;/p&gt;
&lt;p&gt;A &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1221A1.pdf"&gt;public notice&lt;/a&gt; announces a &lt;a href="https://apps.fcc.gov/oet/translator/"&gt;special web page&lt;/a&gt; at which qualifying stations can register their receiver channels into the FCC&amp;rsquo;s CDBS system.&lt;/p&gt;
&lt;p&gt;For protection purposes, low power stations fall into one of three distinct situations:&lt;/p&gt;&lt;ol&gt;
    &lt;li&gt;&amp;nbsp;Low power stations located within the protected service contour of the originating station they rebroadcast &amp;ndash; these low power stations are automatically protected under the umbrella of the originating station.&lt;/li&gt;
    &lt;li&gt;Low power stations located outside the protected service contour of their originating stations, but within 80 km of the originating station&amp;rsquo;s service contour &amp;ndash; these low power stations are entitled to protection from white space devices, but &lt;b&gt;&lt;i&gt;only if&lt;/i&gt;&lt;/b&gt; the low power station&amp;rsquo;s facilities have been properly entered in CDBS.&lt;/li&gt;
    &lt;li&gt;Low power stations located more than 80 km beyond their originating station&amp;rsquo;s protected service contour &amp;ndash; these low power stations are not entitled to protection &lt;i&gt;unless&lt;/i&gt; the FCC has granted a waiver.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The FCC reminds low power stations, particularly those in the second group described above above (or in the third group with waivers), to make sure that their CDBS entries are current and correct.&amp;nbsp;When full-power stations changed channels as part of the 2009 digital transition, and low power stations adjusted their receivers accordingly, many forgot to tell the FCC.&amp;nbsp;Since protection of those receivers from white space devices will be dependent on the information for those stations in CDBS, this is a good time to visit &lt;a href="https://apps.fcc.gov/oet/translator/"&gt;the FCC&amp;rsquo;s new web page&lt;/a&gt; and make sure all the information there is current and accurate.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/R0CA4rlz1UM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/R0CA4rlz1UM/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/05/articles/broadcast/lopo-tv-warning-white-space-devices-are-coming-have-you-updated-your-cdbs-information/</guid>
         <category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/tags">CDBS</category><category domain="http://www.commlawblog.com/tags">Class A Television</category><category domain="http://www.commlawblog.com/tags">Low power television</category><category domain="http://www.commlawblog.com/tags">TV band database</category><category domain="http://www.commlawblog.com/tags">TV translators</category><category domain="http://www.commlawblog.com/tags">TVBD</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/tags">White Space</category>
         <pubDate>Wed, 29 May 2013 21:10:22 -0500</pubDate>
         <dc:creator>FHH Law</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/05/articles/broadcast/lopo-tv-warning-white-space-devices-are-coming-have-you-updated-your-cdbs-information/</feedburner:origLink></item>
            <item>
         <title>White Space Database Update</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;The FCC requests comment on white space database tests recently conducted by Google, Inc. and Key Bridge Global LLC. &lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img width="100" vspace="5" hspace="5" height="114" align="left" src="http://www.commlawblog.com/uploads/image/designer-1.JPG" alt="" /&gt;In separate public notices, the FCC has asked for comment on white space database tests recently conducted by &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1220A1.pdf"&gt;Google, Inc&lt;/a&gt;. and &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1222A1.pdf"&gt;Key Bridge Global LLC&lt;/a&gt;. (The FCC paperwork misidentifies the second company as &amp;quot;Keybridge Global Inc.&amp;quot;) Their respective test reports are &lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022311805"&gt;here&lt;/a&gt; and &lt;a href="http://apps.fcc.gov/ecfs/document/view?id=7022308039"&gt;here&lt;/a&gt;. Mark your scorecards: once approved, these will be database managers numbers 3 and 4.&lt;/p&gt;
&lt;p&gt;Prior CommLawBlog entries on these tests are &lt;a href="http://www.commlawblog.com/2013/02/articles/unlicensed-operations-and-emer/third-white-space-database-coordinator-to-begin-tests/"&gt;here&lt;/a&gt; and &lt;a href="http://www.commlawblog.com/2013/03/articles/unlicensed-operations-and-emer/fourth-white-space-database-coordinator-tees-up-tests/"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Comments on both tests are due on &lt;b&gt;&lt;i&gt;June 13, 2013&lt;/i&gt;&lt;/b&gt; and reply comments in &lt;b&gt;&lt;i&gt;June 20&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;For background on the databases and what they do, &lt;a href="http://www.commlawblog.com/2010/09/articles/broadcast/fcc-okays-white-space-devices/"&gt;see this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;[&lt;i&gt;Blogmeister&amp;rsquo;s Note:&amp;nbsp;In keeping with the practice we introduced with &lt;a href="http://www.commlawblog.com/2013/03/articles/unlicensed-operations-and-emer/fourth-white-space-database-coordinator-tees-up-tests/"&gt;our last white space database post&lt;/a&gt;, we have sought to capture the essence of these recent developments poetically&lt;/i&gt;:&lt;/p&gt;
&lt;p style="margin-left: 120px;"&gt;&lt;b&gt;An FCC Haiku to the Public&lt;/b&gt;&lt;/p&gt;
&lt;p style="margin-left: 120px;"&gt;&lt;strong&gt;Key Bridge and &lt;/strong&gt;&lt;b&gt;Google&lt;/b&gt;&lt;b&gt;&lt;br /&gt;
filed database test reports.&lt;br /&gt;
&lt;/b&gt;&lt;b&gt;Comments? &amp;nbsp;We&amp;rsquo;re all ears.&lt;/b&gt;]&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/CommLawBlog/~4/ImNV1u6i66U" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/CommLawBlog/~3/ImNV1u6i66U/</link>
         <guid isPermaLink="false">http://www.commlawblog.com/2013/05/articles/broadcast/white-space-database-update/</guid>
         <category domain="http://www.commlawblog.com/articles">Broadcast</category><category domain="http://www.commlawblog.com/tags">Database Administrator</category><category domain="http://www.commlawblog.com/articles">Deadlines</category><category domain="http://www.commlawblog.com/tags">Google, Inc.</category><category domain="http://www.commlawblog.com/tags">Haiku</category><category domain="http://www.commlawblog.com/tags">Key Bridge Global, LLC</category><category domain="http://www.commlawblog.com/tags">Keybridge Global Inc.</category><category domain="http://www.commlawblog.com/tags">Spectrum Bridge</category><category domain="http://www.commlawblog.com/tags">Telcordia Technologies</category><category domain="http://www.commlawblog.com/articles">Unlicensed Operations and Emerging Technologies</category><category domain="http://www.commlawblog.com/tags">White Space</category><category domain="http://www.commlawblog.com/tags">White Spaces</category>
         <pubDate>Wed, 29 May 2013 14:58:08 -0500</pubDate>
         <dc:creator>Mitchell Lazarus</dc:creator>
      
      <feedburner:origLink>http://www.commlawblog.com/2013/05/articles/broadcast/white-space-database-update/</feedburner:origLink></item>
      
   </channel>
</rss>
