<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ronald Quirk on Medium]]></title>
        <description><![CDATA[Stories by Ronald Quirk on Medium]]></description>
        <link>https://medium.com/@rquirk9?source=rss-7c93ad306cf3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VK3xQ2q7jr_8wHa1.</url>
            <title>Stories by Ronald Quirk on Medium</title>
            <link>https://medium.com/@rquirk9?source=rss-7c93ad306cf3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:29:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rquirk9/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[House Passes Self-Driving Car Bill, IoT Component Manufacturers Expect Booming Business]]></title>
            <link>https://medium.com/iotforall/house-passes-self-driving-car-bill-iot-component-manufacturers-expect-booming-business-3fc307812832?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fc307812832</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[law]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[self-driving-cars]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Fri, 29 Sep 2017 13:56:01 GMT</pubDate>
            <atom:updated>2017-09-29T13:56:01.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*6OxXgZ2hYGT5-eg5ijNTJQ.jpeg" /></figure><p>In a rare display of bipartisanship, the U.S. House of Representatives has passed a bill that will speed the development of self-driving automobiles. On September 6, 2017, the House unanimously passed the Safely Ensuring Lives Future Deployment in Vehicle Evolution Act (SELF-DRIVE Act).</p><p>Among other things, the SELF-DRIVE Act delineates the Federal Government’s roles in overseeing safety, testing, cybersecurity, and privacy matters of self-driving cars, mandates actions from auto manufacturers, and examines IoT component standards. The bill also preempts state laws that conflict with the Act and regulations that result from it.</p><p>The U.S. Senate is currently working on a companion bill, and reconciliation of the two bills is expected to rapidly proceed.</p><h3>IoT Market Should Thrive Under this Bill</h3><p>Congress’ newly reinvigorated efforts to hasten the deployment of self-driving cars has been cheered by suppliers of IoT self-driving car components, including software, sensor, and semiconductor manufacturers.</p><p>For example, a recent study by a reliable market research company concluded that the world market for automotive semiconductors will grow from the 2015 level of $30.3 billion to $41 billion in 2020. Markets for self-driving auto sensors and cameras are also expected to grow exponentially.</p><h3>More Regulations for Auto Manufacturers and IoT Component Suppliers</h3><p>While IoT component manufacturers should do quite well under the SELF-DRIVE Act, self-driving auto manufacturers will be subject to many new regulations. IoT components used in self-driving cars may also be subject to new standards. Nonetheless, there is much in the bill that will help make the U.S. a prime market for self-driving cars, as well as an important industry location for them.</p><h3>Key Provisions of the SELF-DRIVE Act</h3><h4>Exponential Increase in Self-Driving Car Permits</h4><p>The bill will increase the number of annual self-driving car permits granted by the National Highway Safety Administration (“NHTSA”) to auto manufacturers. The current limit is 2,500; under the bill that will increase to 25,000 in the first year after passage, up to 100,000 after three years.</p><p>Manufacturers will also be granted renewal expectancy. In order to obtain permits, manufacturers will need to demonstrate certain safety standards in their self-driving cars. Manufacturers will also be required to provide NHTSA with reports about any and all crashes in which their “permitted vehicles” are involved.</p><h4>Federal Preemption of Conflicting State Laws</h4><p>Under the bill, NHTSA will oversee and regulate the design, construction and performance of self-driving cars; all conflicting state laws will be preempted. This will create a uniform set of regulations; exempting auto and IoT suppliers from having to comply with a patchwork of state regulations. States will retain jurisdiction over insurance, safety and emissions inspections, insurance, and registration matters.</p><h4>New Safety Standards</h4><p>The SELF-DRIVE Act directs the Secretary of Transportation (“SoT”) to, within two years after the bill’s passage, issue a final rule requiring self-driving auto manufacturers to submit assessment certifications to NHTSA regarding how they are addressing safety issues that arise in their vehicles.</p><p>The bill also mandates that within one year after passage, the SoT must submit a rulemaking and “safety priority plan” detailing NHTSA’s safety priorities to both houses of Congress and the public. In addition to the safety priorities, the plan and rulemaking will contain information about objectives for additional performance standards of testing self-driving cars. IoT equipment standards will likely be updated as safety and performance standards of human-machine interface, sensors, actuators, and software will be evaluated.</p><p>The subject rulemaking proceeding must be initiated 18 months after passage of the bill. The safety priority plan will be updated every two years, or more frequently as determined by the SoT.</p><h4>Cybersecurity</h4><p>The bill requires that all self-driving auto manufacturers develop a written cybersecurity policy that details the manufacturer’s practices for detecting and responding to cyberattacks. The policy must include:</p><ul><li>A process for identifying, assessing, and mitigating reasonably foreseeable vulnerabilities from cyberattacks and unauthorized intrusions;</li><li>A process for taking preventative and corrective actions against vulnerabilities, including response plans, intrusion detection, and prevention systems;</li><li>Identification of a cybersecurity officer and point of contact for cybersecurity matters;</li><li>A process for limiting access to automated driving systems; and</li><li>A process for employee training and supervision for implementation and maintenance of the company’s cybersecurity policy.</li></ul><h3>Privacy</h3><p>The SELF-DRIVE Act also requires self-driving auto manufacturers to develop a written privacy plan to protect sensitive information about owners, operators, and occupants of self-driving cars. This privacy plan requires manufacturers to delineate the following:</p><ul><li>Practices concerning how pertinent information is collected, used, stored, and shared;</li><li>Choices offered to vehicle owners, operators, and occupants concerning the collection, use, storage and sharing of their information;</li><li>Data minimization, de-identification, and retention of information about the owners, occupants, and operators of their cars; and</li><li>Method(s) for providing notice to affected parties about the company’s privacy policy.</li></ul><p>Violations of the bill’s privacy requirements will be treated as unfair or deceptive acts or practices under the Federal Trade Commission Act. As such, the Federal Trade Commission will enforce the bill’s privacy provisions.</p><p>IoT For All Newsletter</p><p>Sign up for our weekly newsletter and exclusive content!</p><h4>Consumer Information Notice Requirements</h4><p>The bill tasks the SoT with conducting a study on the most effective means of informing consumers of the capabilities and limitations of self-driving cars. After the study is completed, the SoT will initiate a rulemaking proceeding to require manufacturers to inform consumers about the capabilities and limitations of their cars.</p><h4>Industry Council</h4><p>Within six months of enactment, the SELF-DRIVE Act requires the SoT to establish within the NHTSA a “Highly Automated Vehicle Council.” The Council’s duties include gathering information, developing technical advice, and presenting best practices recommendations to the SoT regarding all manner of regulatory concerns of self-driving cars…</p><p>The Council will include representatives from industry, academia, state and local authorities, engineers, consumer and safety advocates, environmental experts, and the NHTSA.</p><h4>Senate Actions</h4><p>In addition to drafting a companion bill to the SELF-DRIVE Act, the U.S. Senate is in the process of conducting hearings on regulating self-driving trucks and other commercial vehicles. The most recent hearing examined the benefits of automated truck safety technology, as well as the potential impact on jobs and the economy.</p><p>Senator John Thune (R-S.D.), Chairman of the Senate Committee on Commerce, Science, and Transportation has stated that the inclusion or exclusion of trucks, buses, and other heavy duty vehicles has been a key topic of discussion in the ongoing bipartisan efforts to implement self-driving vehicle legislation.</p><h3>Attention to Self-Driving Car Legislation is Critical</h3><p>Congress has prioritized self-driving vehicle legislation. With broad support from heavy hitters from Silicon Valley and Detroit, a final bill could be ready for the President’s signature within a matter of months. The resulting law and the regulations promulgated as a result will surely impact the IoT industry in a big way.</p><p>IoT components will be an important part of the safety, cybersecurity, and privacy aspects of the SELF-DRIVE Act and related legislation. Marashlian &amp; Donahue is keeping a close watch on all developments and will be providing updates to interested parties on a regular basis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*670v_MxiW00ZDQ6yoT8QQw.jpeg" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://www.iotforall.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://www.iotforall.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><p><em>Originally posted at </em><a href="https://www.iotforall.com/house-passes-self-drive-act-iot-implications/"><em>www.iotforall.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fc307812832" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/house-passes-self-driving-car-bill-iot-component-manufacturers-expect-booming-business-3fc307812832">House Passes Self-Driving Car Bill, IoT Component Manufacturers Expect Booming Business</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[E-Labeling IoT Devices: Don’t Cut Corners!]]></title>
            <link>https://medium.com/iotforall/e-labeling-iot-devices-dont-cut-corners-2dec77cf3385?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dec77cf3385</guid>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 18:03:40 GMT</pubDate>
            <atom:updated>2017-09-13T18:03:40.774Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>While many IoT manufacturers are understandably anxious to get their products to market, it is becoming increasingly unwise to cut corners on regulatory compliance.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VyfVkQQgb56Iixm17eCi5A.jpeg" /></figure><p>In furthering its efforts to modernize radiofrequency (RF) equipment regulations, the Federal Communications Commission (FCC) recently codified rules that permit electronic labeling (e-labeling) of RF devices, including Internet of Things (IoT) devices, as long as they have the capacity to digitally display the required regulatory information.[1]</p><p>While e-labeling can save IoT and other RF equipment suppliers money by, among other things, eliminating the cost of purchasing and affixing permanent labels to all their devices, the FCC will impose substantial fines and strict sanctions on suppliers that incorrectly implement e-labeling or otherwise violate its rules.</p><h3>The FCC’s Labeling Rules</h3><p>The FCC requires that parties responsible for FCC compliance (typically the manufacturer or importer), with limited exceptions, test and label RF devices before marketing or operating them in the U.S.[2] Transmitting RF devices that require FCC certification (“intentional radiators”) and non-transmitting RF devices that require self-authorization by the FCC’s new Supplier’s Declaration of Conformity procedures (“unintentional radiators”), must display labels containing company identification information, as well as regulatory compliance statements.[3]</p><p>Historically, the FCC has required that RF devices have “permanently affixed” labels prominently displayed on them.[4] If the devices were too small to accommodate a proper label, the FCC permitted the information to be listed in the user’s manual or on the box in which the device is contained.[5] The FCC also permitted e-labeling under certain limited circumstances.[6]</p><h3>New E-Labeling Rules</h3><p>The new rules codify the procedures that RF suppliers must follow if they wish to utilize e-labeling for their products. E-labeling is optional; suppliers may still use physical labels if they wish. The key provisions of the new rules are:</p><p>Information as to how to retrieve the compliance information &amp; company identification via the e-labeling must be provided to the user, either in the instruction manual, packaging material, or the company’s website. If the website is used, the packaging material must provide instructions as to how to access the website.[7]</p><p>No codes or special permission to access the e-labeling information may be used, and accessing that information may not require more than three steps from the device-setting menu.[8]</p><p>The e-labeling information must be programmed by the responsible party and secured so that third parties cannot modify it.[9]</p><p>The company’s “unique identifier” and information about the website that contains the relevant information must be printed on the device or its packaging.[10]</p><h3>Sanctions for Improper Labeling Can Include Losing Marketing Authority</h3><p>The FCC strictly enforces its RF equipment labeling rules. Historically, the FCC would levy fines on non-compliant suppliers and require them to implement compliance programs. Lately, the FCC has, in addition to imposing fines and sanctions, implemented a policy wherein RF equipment suppliers that violate the rules may lose their authorizations to market their products in the U.S.</p><p>Accordingly, it is more critical than ever for RF equipment suppliers to fully understand and comply with all of the FCC’s equipment authorization, marketing, and importation rules, as well as its labeling requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*zqL5yFaUPkhc3Hd6abFjVA.png" /></figure><h3>FCC Surveillance of RF Equipment</h3><p>The FCC’s Enforcement Bureau routinely scours the Internet and utilizes other methods to search for non-compliant RF equipment. When the FCC finds equipment that does not comply with its rules, it opens an investigation that subjects the responsible party to public exposure of rule violations and, as described above, often results in the imposition of fines and severe sanctions.</p><p>Moreover, the FCC’s rules require Telecommunications Certification Bodies (“TCBs”) to conduct post-market surveillance on at least five percent of the RF equipment they have certified.[11] This surveillance is intended to ensure that marketed RF equipment conforms to the technical parameters of equipment that was tested and certified.</p><p>TCBs conduct surveillance by obtaining samples of suspicious RF devices on the market, measuring the characteristics, and comparing them to the characteristics of the prototypes that were authorized.</p><p>Responsible parties whose RF devices are under surveillance must, upon request, provide the investigating TCB with a sample RF device or vouchers to purchase any sample device the TCB wishes in order to conduct its surveillance.</p><h3>Adopt Best Practices to Mitigate Chances of Rule Violations</h3><p>With the FCC now threatening “lifetime bans” on delinquent RF equipment suppliers, compliance is now more important than ever before. RF equipment suppliers, including IoT providers, are well advised to work with experienced professionals who understand the FCC rules in order to evaluate the risks of FCC rule violations and what they could mean to the company.</p><p>While many IoT manufacturers are understandably anxious to get their products to market, it is becoming increasingly unwise to cut corners on regulatory compliance. Savvy RF device suppliers not only understand the rules, they implement internal best practice procedures in order to mitigate the risk of FCC rule violations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*zqL5yFaUPkhc3Hd6abFjVA.png" /></figure><p>[1] See 47 C.F.R. § 2.935(a).</p><p>[2] See 47 C.F.R. § 15.19.</p><p>[3] See 47 C.F.R. §§ 2.1074, 2.1077, 15.19.</p><p>[4] See 47 C.F.R. § 15.19(a)(3), (b)(4).</p><p>[5] See 47 C.F.R. § 15.19(a)(5).</p><p>[6] See Amendment of Parts 0, 1, 2, and 15 of the Commission’s Rules Regarding Authorization of Radiofrequency Equipment, Notice of Proposed Rulemaking, 30 FCC Rcd. 7725 (2015) at ¶ 101.</p><p>[7] See 47 C.F.R. § 2.935(b). A copy of these instructions must also be provided in an application for equipment certification</p><p>[8] See 47 C.F.R. § 2.935(c). For example, step one would be a user accessing the device setting menu; step two would be accessing a sub-menu of legal information; and step three would be accessing a further sub-menu of FCC compliance information. See In the Matter of Parts 0, 1, 2, 15, and 18 of the Commission’s Rules Regarding Authorization of Radiofrequency Equipment, FCC 17–93 (Rel. July 14, 2017) at ¶ 31.</p><p>[9] See 47 C.F.R. § 2.935(e).</p><p>[10] See 47 C.F.R. § 2.935(f).</p><p>[11] See 47 C.F.R. § 2.962(g).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*zqL5yFaUPkhc3Hd6abFjVA.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><p><em>Originally published at </em><a href="https://www.iotforall.com/elabeling-iot-radiofrequency-devices/"><em>www.iotforall.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dec77cf3385" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/e-labeling-iot-devices-dont-cut-corners-2dec77cf3385">E-Labeling IoT Devices: Don’t Cut Corners!</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Let the FCC Take Away 3.5 GHz Shared Spectrum!]]></title>
            <link>https://medium.com/iotforall/dont-let-the-fcc-take-away-3-5-ghz-shared-spectrum-76101a3f894f?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/76101a3f894f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[law]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Fri, 04 Aug 2017 14:56:05 GMT</pubDate>
            <atom:updated>2017-08-04T14:56:05.346Z</atom:updated>
            <content:encoded><![CDATA[<h4>T-Mobile is proposing to eliminate unlicensed use of the spectrum, raising the barrier to entry for businesses seeking to utilize the 3.5 GHz band.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wlnUGQQNW_BUxhmwnHlLnQ.jpeg" /></figure><p><a href="https://iotforall.com/t-mobile-fcc-propoal-3-5-ghz-band/">As discussed in a previous post</a>, T-Mobile USA, Inc. (“T-Mobile”) is petitioning the FCC to gut the core purpose of the current rules governing the <a href="https://www.leverege.com/blogpost/what-is-cbrs-lte-3-5-ghz">3550–3700 MHz spectrum band </a>(“3.5 GHz” band), which is to lower the barrier of entry of smaller carriers into the wireless 5G business by allowing commercial shared use of 3.5 GHz via licensed and unlicensed allocation.</p><p>These rules are intended to pave the way for broadband providers, large and small, to implement new and innovative wireless broadband services.</p><p>T-Mobile wants the FCC to license the entire spectrum band and grant other favors to large wireless carriers. If adopted, <strong>T-Mobile’s proposal would virtually eliminate unlicensed use of the spectrum (except when they say so), thereby substantially raising the barrier to entry for businesses seeking to utilize the 3.5 GHz band, which is critical to the growth of 5G wireless broadband in the U.S.</strong></p><p>The FCC is soliciting public comment on T-Mobile’s Petition.</p><p>The initial comment period ended on July 24, 2017. Comments submitted revealed some disturbing trends. While many (mostly small) commenters opposed T-Mobile’s petition, a number of very powerful companies filed in support of some or all of T-Mobile’s proposals. These companies include AT&amp;T, Verizon, U.S. Cellular, Nokia, Qualcomm, Ericsson, and Boingo.</p><p>Because these corporations’ voices speak very loudly at the FCC,<strong> it is critical that any business that wishes to retain the current rules must file reply comments, opposing the positions of these corporate behemoths.</strong></p><p>Moreover, a recent public statement by FCC Commissioner O’Reilly provides a strong indication that he supports T-Mobile’s proposal. This increases the urgency of making your voices heard. Reply comments are due August 8, 2017.</p><h3>T-Mobile’s Proposed Rule Changes</h3><ul><li>Auction all 150 MHz of the 3.5 GHz band as PALs, restricting unlicensed use of the band “when it is not in use by PAL licensees.”</li><li>Eliminate the “seven PALs per license area” limitation.</li><li>Eliminate the three-year, non-renewable PAL term, replacing it with a ten-year license term with renewal expectancy.</li><li>Exponentially expand PAL license areas by eliminating the small census tract areas and replacing them with the much larger “Partial Economic Areas.”</li><li>Take away the little remaining unlicensed spectrum by eliminating the rule that (except in rural areas) when there is only one application for a PAL in a license area, no PAL will be assigned; the spectrum will remain accessible solely for shared GAA use.</li><li>Permit partitioning and disaggregation of PALs so that PA licensees can slice up their licenses any way they choose.</li></ul><p><strong>If T-Mobile’s proposals are adopted, the 3.5 GHz band will likely become the sole domain of the largest wireless carriers and equipment manufacturers.</strong> It is no surprise that they filed in support of T-Mobile’s petition.</p><p><em>Originally published at </em><a href="https://iotforall.com/fcc-shared-3-5-ghz-spectrum-t-mobile/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76101a3f894f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/dont-let-the-fcc-take-away-3-5-ghz-shared-spectrum-76101a3f894f">Don’t Let the FCC Take Away 3.5 GHz Shared Spectrum!</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Device Suppliers Beware]]></title>
            <link>https://medium.com/iotforall/iot-device-suppliers-beware-8bba826f1ae2?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bba826f1ae2</guid>
            <category><![CDATA[regulation]]></category>
            <category><![CDATA[law]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[humanity]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Tue, 25 Jul 2017 18:07:54 GMT</pubDate>
            <atom:updated>2017-08-03T19:11:34.431Z</atom:updated>
            <content:encoded><![CDATA[<h4>A High-Level Overview of the FCC ‘s Equipment Regulation Changes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DG81O9vHvFkMRqX6.jpg" /></figure><p>In its July 2017 Open Meeting, the Federal Communications Commission (“FCC”) voted to approve a <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2017/db0714/FCC-17-93A1.pdf">Report and Order</a> (“R&amp;O”) containing new rules that impact how RF equipment, manufacturers, vendors, importers, and distributors may conduct their businesses.</p><p>These rules particularly affect IoT equipment suppliers, which are subject to virtually all the new rules.</p><p>Prior to finalizing the new rules, the FCC emphasized the importance of them to the RF equipment industry, stating that the rules overhaul consists of a <em>“wide range of equipment approval issues of a technical, legal, and practical nature, impacting a diverse set of stakeholders, each of whom will need to closely analyze and consider the potential impact of the rule changes.”</em></p><h3>FCC Severely Penalizes Non-Compliant Equipment Suppliers</h3><p>Because the Communications Act and the FCC’s rules strictly prohibit (with limited exceptions) the marketing, testing, and operation of unauthorized RF equipment, it is critical that IoT stakeholders at all levels of the equipment supply chain be aware of the new rules. The FCC’s Enforcement Bureau will not hesitate to impose substantial monetary forfeitures and other sanctions on parties that violate the RF equipment rules.</p><p>For example, the FCC recently issued an <a href="https://apps.fcc.gov/edocs_public/attachmatch/DA-17-471A1.pdf">Order and Consent Decree</a>, imposing a steep fine and other sanctions on a manufacturer/distributor of LED light fixtures that failed to comply with the FCC’s equipment authorization rules before marketing a line of light fixtures. The devices reportedly caused interference to radio transmissions, which resulted in the FCC conducting an investigation of the manufacturer, who was found guilty of serious violations.</p><p>After the manufacturer fixed the interference problem and proactively complied with the FCC’s RF equipment rules, the FCC agreed to a consent decree to resolve the case. Specifically, the FCC agreed to terminate the investigation in exchange for the manufacturer agreeing to pay $90,000 to the U.S. Treasury and implement a strict compliance program.</p><p>More importantly for IoT suppliers, the FCC issued a threat to future RF equipment manufacturers and other responsible parties who market unauthorized equipment. Specifically, the FCC asserted its authority to conduct hearings and declare non-compliant RF equipment suppliers unqualified to hold any type of FCC authorization.</p><p>In other words, <strong>the FCC threatened to prevent RF equipment suppliers who violate FCC rules from ever legally marketing their products in the U.S., by denying them equipment authorizations.</strong></p><p>This is a critically important development. Because virtually all devices that generate RF energy (even passive devices such as sensors) are subject to FCC rules, this case underscores the importance of ensuring full compliance with FCC rules prior to marketing RF equipment in the U.S.</p><h3>New Rules are Just the Beginning of Equipment Regulatory Changes</h3><p>The rules put forth in the R&amp;O are only the start of many new regulatory changes for RF equipment suppliers. Rule changes affecting the following topics will be addressed in subsequent FCC proceedings:</p><ul><li>Modular component certification;</li><li>Responsible parties for refurbished devices</li><li>Software and firmware security requirements;</li><li>And confidentiality of information contained in RF equipment certification applications.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*wjzNtkNQwctlvmKP.png" /></figure><h3>High-Level Overview 4 of the FCC’s Equipment Regulation Changes</h3><h4>1) “Self-Approval” Authorization for Non-Transmitting RF Devices</h4><p><strong>Current Rules<br></strong>Most non-transmitting RF devices (unintentional radiators) are “self-authorized” by one of two procedures (depending on the specific type of the device): Verification and Declaration of Conformity (“DoC”).</p><p>These procedures are very similar, wherein the responsible party (“RP”) submits prototype to a lab for testing for compliance with FCC technical rules. If device passes, it is labeled and marketed. Nothing is submitted to FCC unless audited. The main differences are that with a DoC, the RP must use an FCC-accredited testing lab, include “compliance information statement” with each device, and include FCC logo on device’s label.</p><p><strong>New Rules</strong></p><ol><li>Combine elements of DoC &amp; Verification into one procedure: Supplier’s Declaration of Conformity (“SDoC”).</li><li>Eliminate the FCC-accredited lab requirement for any device subject to SDoC.</li><li>Eliminate the FCC logo requirement.</li><li>Require that all devices subject to SDoC contain lengthy compliance statements.</li></ol><h4>2) Importation Rules</h4><p><strong>Current Rules<br></strong>Importers of RF devices must declare that their devices have been tested and approved via the applicable authorization procedure or are being imported pursuant to one of the FCC-approved specific exemptions.</p><p>Declaration Requirements: No RF device may be imported unless the importer declares that the device meets the FCC rule requirements via: (a) electronic declaration at points of entry where electronic filing at U.S. Customs &amp; Border Protection (“CBP”) is available; and (b) where electronic filing is not available, importer must use FCC Form 740 and attach it to the CBP-required papers.</p><p>Trade Show Exemption for Unauthorized Devices: FCC permits the importation of 200 unauthorized devices for use in licensed service to be imported for trade show demonstration purposes, and 10 unauthorized devices intended for unlicensed use.</p><p>Importation of Unauthorized Devices for Personal Use Only: A total of three unauthorized devices for use in unlicensed services may be imported for personal use</p><p><strong>New Rules</strong></p><ol><li>Eliminate Form 740 filing requirements. Importers would no longer have to file information with the FCC specifying the import conditions on which they are relying.</li><li>The permitted number of unauthorized devices for trade show demonstration purposes would be increased to 400.</li><li>A total of three unauthorized devices intended for use in licensed services would be permitted, as long as those devices are for personal use only.</li></ol><h4>3) Measurement Requirements for RF Equipment Authorization</h4><p><strong>Current Rules<br> </strong>FCC will accept measurement data in accordance with three types of measurement procedures: (a) OET bulletins or reports published in its “Knowledge Database” (“KDB”); (b) those published by national engineering societies and acknowledged by the FCC; and © current measurement procedures accepted by the FCC.</p><p><strong>New Rules</strong></p><ol><li>Add acknowledgement in rules to permit reliance on advisory information contained in FCC’s online KDB publications.</li><li>Add references to specific sections of American National Standard for Compliance Testing of Transmitters (“ANSI”) C63.4–2014 and ANSI C63.10–2013 to address certain measurements for some unlicensed devices.</li><li>Combine current rules for RF measurement of composite systems into one rule (while retaining some references to applicable rules).</li><li>ANSI C63.26 — new standard for compliance testing for licensed devices. References to this standard could replace measurement in FCC rules for RF power output, modulation characteristics, occupied bandwidth, spurious emission at antenna terminals, field strength of spurious radiation, frequency stability and frequency spectrum.</li></ol><h4>4) E-Labeling</h4><p>The FCC has very strict rules about proper labeling of RF devices before they are placed on the market. Manufacturers of RF devices and other responsible parties have been subject to <a href="https://apps.fcc.gov/edocs_public/attachmatch/DA-08-1952A1.pdf">fines and sanctions</a> by the FCC for improper labeling of their devices.</p><p><strong>Current Rules<br></strong>The FCC requires that all RF equipment have “permanently affixed” labels, containing specific compliance information. The information varies, depending on the category of the device. If the devices is too small to accommodate a proper label, the FCC permits the information to be listed in the user’s manual or on the box in which the device is contained. The “FCC identifier” must be on the device itself, regardless of how small the device is.</p><p><strong>New Rules<br></strong>Any RF device that is equipped with an integrated electronic display screen or a device without such a screen that can operate in conjunction with a device that has a screen may display any labeling information required by the FCC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*mOhixyyC60v6o17b.png" /></figure><h3>Conclusion</h3><p>This is a high-level overview of some of the FCC’s equipment regulation changes. Due to the complexity and comprehensive nature of the proposed regulation changes, an exhaustive report is beyond the scope of this article.</p><p>All information provided in this article is “Informational Only” and should not be relied upon as legal advice. Decisions should not be made without first seeking the advice of experienced telecommunications counsel.</p><p><em>Originally published at </em><a href="https://iotforall.com/overview-fcc-equipment-regulation-changes/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bba826f1ae2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/iot-device-suppliers-beware-8bba826f1ae2">IoT Device Suppliers Beware</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is T-Mobile Trying to Slow Down 5G?]]></title>
            <link>https://medium.com/iotforall/why-is-t-mobile-trying-to-slow-down-5g-29d11b5ab723?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/29d11b5ab723</guid>
            <category><![CDATA[fcc]]></category>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Wed, 05 Jul 2017 14:01:33 GMT</pubDate>
            <atom:updated>2017-08-03T19:28:04.183Z</atom:updated>
            <content:encoded><![CDATA[<p>T-Mobile’s proposal to eliminate unlicensed use of 3.5 GHz band</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s_H_H24z_eVMncqWxXbfKA.jpeg" /></figure><p>In a last-minute attempt to eviscerate the core purpose of the rules governing the 3550–3700 MHz spectrum band (“3.5 GHz band”), T-Mobile USA, Inc. (“T-Mobile”) recently filed a Petition for Rulemaking (“Petition”), proposing that the FCC license the entire spectrum band and grant other favors to large wireless carriers.</p><p>If adopted, T-Mobile’s proposal would virtually eliminate unlicensed use of the spectrum, thereby substantially raising the barrier to entry for businesses seeking to utilize the 3.5 GHz band, which is critical to the growth of 5G wireless broadband in the U.S.</p><p>The FCC is soliciting public comment on T-Mobile’s Petition. Comments and reply comments are due by <strong>July 24, 2017</strong> and <strong>August 8, 2017</strong> respectively.</p><h3>Purpose of the 3.5 GHz Rules: A Level Playing Field</h3><p>The explosive growth in mobile broadband traffic and its concomitant strain on limited spectrum resources required the FCC to engage in creative frequency allocation. To that end, in April 2015 the FCC adopted rules to allow commercial shared use of 150 MHz of 3.5 GHz spectrum.</p><p>The FCC crafted its rules after a long and arduous rule making proceeding, wherein it considered ideas from three major traditions in spectrum management: flexible-use geographic licensing, site-based frequency coordination, and unlicensed authorization.</p><p>Ultimately, the FCC adopted a hybrid framework that selects, automatically, the best approach based on local supply and demand. As delineated below, where competitive rivalry for spectrum access is low, an unlicensed tier provides a low-cost entry point to the band. Where rivalry is high, auctions will resolve mutually exclusive applications in specific geographic areas for short-term (three year, non-renewable) licenses.</p><p>Finite-term licensing, and limiting the number of licenses per geographic area, facilitates evolution of the band and an ever-changing mix of licensed and unlicensed bandwidth over time. This will pave the way for broadband providers, large and small, to implement new and innovative wireless broadband services</p><h3>Current 3.5 GHz Band Rules</h3><p>The crux of the 3.5 GHz rules is the creation of a commercial radio service called <a href="https://iot-for-all.com/what-is-cbrs-lte-3-5-ghz/">Citizens Broadband Radio Service (“CBRS”)</a>. CBRS facilitates spectrum sharing by means of a three-tiered system.</p><p>Tier 1 consists of incumbent federal users (radiolocation and aeronautical radio navigation) and non-federal fixed satellite service (“FSS”) operators.</p><p>Tier 2 is for “Priority Access” operators, whose licenses (“PALs”) will be allocated by auction.</p><p>Tier 3 is reserved for General Authorized Access (“GAA”). GAA will be licensed “by rule,” meaning that any entity that qualifies as an FCC licensee may use FCC-authorized telecommunications equipment in the GAA band without having to obtain an individual spectrum license.</p><p>Unlicensed operators will have access to many frequencies (up to all 150 MHz in the band where no PALs are issued or in use, and up to 80 MHz when all PALs are in use) without having to incur the expense of bidding on spectrum.</p><p>Licensed operators will be subject to spectrum auctions, but because the “census tract” geographic service areas are very small, the per-license costs should be much less than licenses issued in other spectrum auctions.</p><p>Moreover, the CBRS structure will advance small cell and distributed antenna system (“DAS”) technologies, which mobile broadband operators can use to efficiently and economically extend their service coverage and increase their network capacities.</p><h3>T-Mobile’s Major Proposed Rule Changes</h3><ul><li>Auction all 150 MHz of the 3.5 GHz band as PALs, restricting unlicensed use of the band “when it is not in use by PAL licensees.”</li><li>Eliminate the “seven PALs per license area” limitation.</li><li>Eliminate the three-year, non-renewable PAL term, replacing it with a ten-year license term with renewal expectancy.</li><li>Exponentially expand PAL license areas by eliminating the small census tract areas and replacing them with the much larger “Partial Economic Areas.”</li><li>Take away the little remaining unlicensed spectrum by eliminating the rule that (except in rural areas) when there is only one application for a PAL in a license area, no PAL will be assigned; the spectrum will remain accessible solely for shared GAA use.</li><li>Permit partitioning and disaggregation of PALs so that PA licensees can slice up their licenses any way they choose.</li></ul><p>If T-Mobile’s proposals are adopted, the 3.5 GHz band will likely become the sole domain of the largest wireless carriers.</p><p>Among other things, smaller carriers that intend to bid on PALs will find themselves priced out of the market, while businesses that intend to use the unlicensed 3.5 GHz frequencies will be out of luck. Moreover, since most small cells are carrier-specific, the larger carriers will have a lock on critical parts of the 5G infrastructure.</p><p>Accordingly, it is critical that 5G stakeholders make their voices heard in this proceeding.</p><p><em>Originally published at </em><a href="https://iotforall.com/t-mobile-fcc-propoal-3-5-ghz-band/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29d11b5ab723" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/why-is-t-mobile-trying-to-slow-down-5g-29d11b5ab723">Why is T-Mobile Trying to Slow Down 5G?</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surviving the IoT Cyber Attack Pandemic]]></title>
            <link>https://medium.com/iotforall/surviving-the-iot-cyber-attack-pandemic-cce04f70ce2c?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cce04f70ce2c</guid>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[law]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 14:03:04 GMT</pubDate>
            <atom:updated>2017-08-03T19:42:27.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yEwXWTk0_c9CaGY2j-ctzQ.jpeg" /></figure><blockquote><em>“The Internet of Things is turning into a security nightmare.”</em></blockquote><p>So wrote Thomas Ricker, a respected systems engineer and deputy editor of the <em>The Verge</em>, in describing the enormous distributed denial of service (DDoS) attack that disabled wide swaths of the Internet in late September 2016. This is no hyperbole. Mr. Ricker’s statement succinctly describes the current state of Internet of Things devices’ vulnerability to cyber attack and hacking.</p><p>According to a leading report by Malwarebytes Labs, there were nearly 1 billion malware detections and incidents, affecting nearly 100 million devices in more than 200 countries, during the June to November 2016 period alone.</p><p>The United States is the top country for ransomware detections, as Americans are targeted because of their wide accessibility to technology and their ability to pay the ransom.</p><h3>Unprotected Devices Are Begging for an IoT Cyber Attack</h3><p>IoT devices are particularly vulnerable to cyber attacks from botnets — a network of private computers infected with malicious software and used to spread malware.</p><p>The aforementioned DDoS attack was orchestrated by a botnet that spread Mirai, an open-source malware, which compromised many IoT devices and home routers, with all of the infected devices being controlled by a single source. This brought down many well-known websites.</p><p>Less than a month later, Mirai was used to attack Dyn, an Internet infrastructure company that provides critical technology services to some of the Internet’s top destinations. This attack, which compromised security cameras, prevented millions of users from accessing popular sites such as Twitter, Reddit, and Netflix.</p><p>Mirai is a particularly insidious malware. It scours the Web for IoT devices protected by little more than factory-default usernames and passwords, using an internal database of default names and passwords to gain entry to connected devices. After gaining access, Mirai attacks by throwing junk traffic at an online target until it can no longer accommodate legitimate users.</p><p>It is unlikely that we have seen the last of Mirai. The hacker who created Mirai released the source code for it, thereby enabling anyone who wants to instigate a botnet attack to use the malware.</p><h3>Unsecured Firmware Can Be a Cesspool of Insecurity</h3><p>Passwords in IoT products are embedded in the firmware. Firmware is software that controls the basic functions of a particular device; all computing devices rely on it.</p><p>Devices such as smartphones and computers have operating systems, which help consumers manage the firmware. But devices without operating systems built in, such as routers and smart devices, render firmware difficult or even impossible for users to manage.</p><p>This scenario results in firmware potentially being a cesspool of insecurity.</p><p>Many manufacturers view building security protocols in their devices as an unnecessary expense that eats into their margins. Consumers rarely think about applying patches (i.e., software that fixes security vulnerabilities) or installing updates on their devices — and because consumers don’t demand firmware support, manufacturers don’t provide user-friendly ways to update firmware used in their IoT devices.</p><p>This kind of neglect has resulted in cyber bugs such as the Misfortune Cookie, which in 2014 was discovered in the firmware of more than 200 router models. This bug allows attackers to monitor Internet traffic channeled through an unsecured router, steal passwords and login credentials, and spread malware to other devices.</p><h3>Securing Firmware Is a Critical Cybersecurity Measure</h3><p>As firmware is the heart and soul that runs IoT and connected devices, securing it is key to reducing cyber risks. Manufacturers of IoT devices and other entities involved in securing, underwriting or litigating products that face cybersecurity risks should begin their examination with a firmware evaluation.</p><p>As there are numerous attack vectors, a constructive place to start is to employ an expert who can efficiently reverse-engineer firmware to reveal vulnerabilities ripe for remote exploitation by hackers, thieves, and state-sponsored actors. This process should be done at the design phase of any IoT device.</p><p>Another proactive step that IoT manufacturers should take to protect their devices is to employ engineers and developers that are able to think like cyber attackers and understand how to exploit their own devices. Security training on exploiting embedded software is the key to their success.</p><p>Effective embedded firmware security training is live, hands-on instruction that combines lectures and labs in which students hack off-the-shelf devices that are already on the market. Students will learn to protect their companies’ embedded devices and join others who have a stake in security.</p><p>The importance of having an IT staff solidly educated in cybersecurity is not only a good business practice but effectively required by law.</p><p>As discussed below, the Federal Trade Commission (FTC) includes security personnel practices in its IoT security guidelines and states’ attorneys general are taking action against IoT companies that do not secure their devices</p><h3>The Law Mandates Secure IoT Devices</h3><h4>The Federal Trade Commission</h4><p>As the number and powerful effects of IoT exploitations surge, companies must shore up their security on embedded devices to mitigate risk.</p><p>Failure to do so violates the Federal Trade Commission Act (FTC Act), which prohibits “unfair” and “deceptive” acts or practices affecting commerce. Violations of the FTC Act can result in substantial fines and other sanctions on the parties responsible for securing IoT devices — typically, the manufacturer, importer, or vendor.</p><p>The FTC has brought hundreds of cases in which it sought to protect the privacy and security of consumer information. In these enforcement actions, the FTC has alleged that various companies acted deceptively in violation of the FTC Act by, among other things, failing to provide reasonable security for consumer data.</p><p>One of these cases involved a company whose vulnerable software enabled hackers to use malware that allowed access to consumers’ usernames and passwords for financial accounts. The company informed its customers that updating the software would make its systems secure, but the updates only removed later versions of the software, leaving in place older software that could be easily hacked.</p><p>In order to mitigate the possibility of legal violations, the FTC has issued some recommended best practices for IoT device manufacturers. These include security by design, security risk assessments, security testing measures and security personnel practices.</p><h4>The Federal Communications Commission</h4><p>Late last year, the FCC commenced a rulemaking in which it sought comment from all interested stakeholders concerning the best methods to ensure the security of the IoT infrastructure. The FCC was fundamentally concerned with the roles and responsibilities each IoT stakeholder should have; it intended to promulgate new cybersecurity rules for IoT providers.</p><p>That proceeding began under former FCC Chairman Tom Wheeler. The new Chairman Ajit Pai discontinued the rulemaking with virtually no explanation. The FCC may recommence this proceeding, but as of this writing no specific timeline has been announced.</p><h4>Cybersecurity Laws May Be Written by State Attorneys General</h4><p>The New York State Attorney General recently took the unprecedented step of taking legal action against a wireless security company for failing to implement adequate security in its IoT devices. The case involved a wireless lock company, which ended in settlement after the company agreed, among other things, to implement a stringent cybersecurity compliance program.</p><p>The crux of the case is that the company’s locks had substantial security deficiencies, in spite of its advertising that the locks protected belongings by securing areas. This violated New York state laws that prohibit deceptive acts or practices and false advertising, and that give the Attorney General power to enjoin repeated fraudulent or illegal acts.</p><p>The lawsuit began when researchers reported in August 2016 that the company did not encrypt its users’ passwords when transmitted from a smartphone to the locks, and did not force users to reset default passwords, which could be discovered easily by brute force attacks.</p><p>The settlement requires the lock company to implement a comprehensive security program, including encrypting all passwords and prompting users to change default passwords during the initial setup.</p><h3>Endure and Thrive in the IoT Security Tsunami</h3><p>The IoT cyber attack pandemic is bad, and until IoT providers impose sufficient security measures in their devices, it will only get worse.</p><p>The importance of IoT suppliers evaluating and securing the firmware in their devices and taking other security measures cannot be overstated. Failure to do so leaves suppliers vulnerable to violations of the FTC Act and, increasingly, state laws.</p><p>IoT suppliers should also remain aware and informed of the ever-changing IoT regulatory and legal landscape. A good cybersecurity attorney can assist you with risk assessment and management, as well as best practices to ensure compliance with the latest laws policies.</p><p>The IoT security tsunami is real. IoT providers must understand the specific risks to their companies and work diligently to mitigate them. IoT companies that ignore the cybersecurity threats do so at their peril.</p><p><em>IoT attorney Ronald E. Quirk is the head of the </em><a href="http://www.commlawgroup.com/practices/43-internet-things"><em>Internet of Things &amp; Connected Devices Practice Group</em></a><em> at Marashlian &amp; Donahue PLLC, The CommLaw Group, where he focuses his practice on the serving the comprehensive needs of the burgeoning and complex Internet of Things industry.</em></p><p><em>Originally published at </em><a href="https://iotforall.com/iot-cyber-attack-pandemic/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cce04f70ce2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/surviving-the-iot-cyber-attack-pandemic-cce04f70ce2c">Surviving the IoT Cyber Attack Pandemic</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Equipment Suppliers Be Warned — FCC Strictly Enforces RF Equipment Rules]]></title>
            <link>https://medium.com/iotforall/iot-equipment-suppliers-be-warned-fcc-strictly-enforces-rf-equipment-rules-332198f0177f?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/332198f0177f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[fcc]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Fri, 09 Jun 2017 16:32:31 GMT</pubDate>
            <atom:updated>2017-08-03T20:00:42.094Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>In a recent release, the FCC threatened to prohibit non-compliant RF equipment suppliers, including IoT suppliers, from marketing their devices in the US.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*l-CR_00AY1yqFYOOl3sxdQ.jpeg" /></figure><p>In everyone’s favorite classic movie, the seemingly “Great and Powerful Oz” was revealed to be nothing more than a charlatan with feet of clay when a little dog pulled back the curtain that separated the Wizard from the outside world.</p><p>For IoT equipment suppliers, the Federal Communications Commission (“FCC”) is turning out to be the Wizard of Oz in reverse. This agency, which is publicly stating its intent to foster the growth of IoT, is quietly imposing brutal penalties on suppliers that don’t comply with its equipment authorization and marketing rules.</p><p>In a recent release, the FCC took the unprecedented action of threatening to prohibit non-compliant radiofrequency (“RF”) equipment suppliers, including IoT suppliers, from marketing their devices in the U.S.</p><h3>FCC’s Strictly Enforces its RF Equipment Rules</h3><p>On May 23, 2017 the FCC issued an <a href="https://apps.fcc.gov/edocs_public/attachmatch/DA-17-471A1.pdf">Order and Consent Decree</a>, imposing a steep fine and other penalties on an RF equipment manufacturer who failed to comply with the FCC’s testing and authorization rules before marketing its product.</p><p>A complaint was filed with the FCC, alleging that the devices caused interference to radio transmissions. This resulted in the FCC commencing an investigation and enforcement action against the manufacturer.</p><p>In an attempt to mitigate FCC sanctions, the manufacturer agreed to proactively comply with the FCC’s RF equipment rules. The parties subsequently agreed to a consent decree to resolve the case. Specifically, the FCC agreed to terminate the investigation in exchange for the manufacturer agreeing to pay $90,000 to the U.S. Treasury and implement a rigorous compliance program.</p><h3>FCC’s Extraordinary Threat to IoT Equipment Suppliers</h3><p>The FCC’s sanctions against the manufacturer are not unusual. The FCC often imposes steep fines (often running into six or seven figures) on non-compliant RF equipment suppliers, and requires them to take steps to comply with the rules going forward.</p><p>What is unusual is the warning the FCC issued to RF equipment suppliers that market unauthorized equipment in the future.</p><p>In the third paragraph of the Order, the FCC states:<em> “In the absence of material new evidence relating to this matter, we do not set for hearing the question of [the manufacturer’s] basic qualifications to hold or obtain any Commission license or authorization.”</em></p><p>This is a critical development that affects all IoT suppliers that market their devices in the U.S.</p><p>Because virtually all devices that generate RF energy (including transmitters, readers, and sensors) are subject to FCC authorization before they can be marketed, the FCC’s statement is an assertion of its authority to effectively prohibit non-compliant IoT equipment suppliers from selling their equipment in the U.S.</p><p>Hence, this case underscores the importance of IoT manufacturers and vendors fully complying with FCC rules prior to marketing their equipment.</p><h3>IoT Suppliers’ Compliance Requirements</h3><p>IoT operations are regulated under Part 15 of the FCC’s rules for low power devices. Devices that transmit RF energy are classified as “intentional radiators,” while most other devices that generate but do not transmit RF energy are classified as “unintentional radiators.”</p><p>Intentional radiators are authorized via the certification process. A certification is issued by an FCC-authorized Telecommunications Certification Body (“TCB”) based on representations and test data (illustrating compliance with the FCC’s RF emissions limits and other requirements) submitted by the applicant.</p><p>Any entity seeking to obtain certification of an RF device must comply with detailed FCC technical and administrative requirements. The certification and testing information is publicly posted on the FCC’s website.</p><p>Unintentional radiators are authorized by one of two “self-authorization” procedures: verification or declaration of conformity (“DoC”). These procedures are similar; they require the responsible party to submit prototypes of its device to an approved laboratory for testing to ensure compliance with the FCC’s rules.</p><p>If the device passes the test, the lab will issue a verification or DoC. The party doesn’t submit the authorization to the FCC, but must retain it and turn it over to the FCC if requested.</p><p>Regardless of the type of authorization, all RF devices must be properly labeled as compliant with the FCC rules before they’re marketed. Different labeling requirements are imposed, depending on the type of equipment.</p><h3>FCC Penalties for Non-Compliance</h3><p>The party seeking authorization — typically the manufacturer, vendor or importer — is the party responsible for ensuring compliance with the FCC’s rules.</p><p>Historically, if an RF device was marketed without proper authorization or was otherwise in violation of the FCC’s rules (including improper labeling or failure to label), as illustrated above, the responsible party would be subject to substantial monetary forfeitures, and other sanctions.</p><p>The most severe penalty the FCC has imposed on an RF equipment supplier was to order it to take its unauthorized equipment off the market. The FCC also ordered vendors to stop selling that equipment.</p><p>The recent FCC ruling adds an extra layer of enforcement concern.</p><p>By stating on the record that it could “de-authorize” RF equipment suppliers, the FCC has given notice to non-compliant suppliers that they could be <em>banned from ever legally marketing their products in the U.S.</em></p><h3>Post-Market Surveillance of IoT Equipment</h3><p>It’s critical for IoT equipment suppliers to take steps to ensure continued compliance once their products are on the market, even if they were properly authorized. The FCC requires TCBs to conduct post-market surveillance on at least five percent of the RF equipment they have certified.</p><p>This surveillance is intended to ensure that marketed RF equipment conforms to the technical parameters of the equipment that was tested and authorized. TCBs conduct surveillance by obtaining sample RF devices on the market, measuring the technical characteristics, and comparing them to that of the prototypes that were authorized.</p><p>If the marketed products are not FCC-compliant, the TCB notifies the FCC, which then conducts an investigation. Responsible parties whose RF devices are under surveillance must, upon request, provide the investigating TCB with a sample RF device or vouchers to purchase any sample device it wishes.</p><h3>Know How the FCC Works — Your Business Depends on It</h3><p>“Come back! Come back! Don’t go without me! Please come back!” Dorothy cried out as the Wizard of Oz’s hot air balloon goes off without her.</p><p>The Wizard replied, “I can’t come back, I don’t know how it works! Good-bye, folks!” And the Wizard sailed off into the stratosphere, never to return to Oz.</p><p><strong>FCC rule compliance is more important than ever.</strong></p><p>IoT equipment suppliers are well advised to work with experienced professionals who understand the FCC rules, in order to evaluate the risks of FCC rule violations and ensure compliance. Savvy IoT equipment suppliers should implement best practices for all their equipment so that the risk of FCC violations are minimized.</p><p>Additionally, any supplier that’s the subject of an FCC investigation that can show it has adopted best practices will probably avoid suffering the worst of the FCC’s penalties.</p><p>All IoT suppliers should understand how the FCC works and the most efficient means of complying with the rules. Suppliers that don’t understand or willfully ignore the FCC’s rules could suffer a fate similar to the Wizard’s, <em>i.e.</em>, exclusion from the U.S. market.</p><p>Written by IoT attorney Ronald E. (“Ron”) Quirk, head of the Internet of Things &amp; Connected Devices Practice Group at <a href="http://www.commlawgroup.com/">Marashlian &amp; Donahue PLLC, The CommLaw Group</a>, He can be reached at req@commlawgroup.com or +1 (703) 714–1305.</p><p><em>Originally published at </em><a href="https://iotforall.com/fcc-strictly-enforces-rf-equipment-rules/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=332198f0177f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/iot-equipment-suppliers-be-warned-fcc-strictly-enforces-rf-equipment-rules-332198f0177f">IoT Equipment Suppliers Be Warned — FCC Strictly Enforces RF Equipment Rules</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Equipment Suppliers Be Warned — FCC Strictly Enforces RF Equipment Rules]]></title>
            <link>https://medium.com/@rquirk9/iot-equipment-suppliers-be-warned-fcc-strictly-enforces-rf-equipment-rules-25b3251aae1c?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/25b3251aae1c</guid>
            <category><![CDATA[fcc]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Thu, 08 Jun 2017 02:04:04 GMT</pubDate>
            <atom:updated>2017-06-08T02:04:04.095Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In a recent release, the FCC threatened to prohibit non-compliant RF equipment suppliers, including IoT suppliers, from marketing their devices in the US.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*l-CR_00AY1yqFYOOl3sxdQ.jpeg" /></figure><p>In everyone’s favorite classic movie, the seemingly “Great and Powerful Oz” was revealed to be nothing more than a charlatan with feet of clay when a little dog pulled back the curtain that separated the Wizard from the outside world.</p><p>For IoT equipment suppliers, the Federal Communications Commission (“FCC”) is turning out to be the Wizard of Oz in reverse. This agency, which is publicly stating its intent to foster the growth of IoT, is quietly imposing brutal penalties on suppliers that don’t comply with its equipment authorization and marketing rules.</p><p>In a recent release, the FCC took the unprecedented action of threatening to prohibit non-compliant radiofrequency (“RF”) equipment suppliers, including IoT suppliers, from marketing their devices in the U.S.</p><p>On May 23, 2017 the FCC issued an <a href="https://apps.fcc.gov/edocs_public/attachmatch/DA-17-471A1.pdf">Order and Consent Decree</a>, imposing a steep fine and other penalties on an RF equipment manufacturer who failed to comply with the FCC’s testing and authorization rules before marketing its product.</p><p>A complaint was filed with the FCC, alleging that the devices caused interference to radio transmissions. This resulted in the FCC commencing an investigation and enforcement action against the manufacturer.</p><p>In an attempt to mitigate FCC sanctions, the manufacturer agreed to proactively comply with the FCC’s RF equipment rules. The parties subsequently agreed to a consent decree to resolve the case. Specifically, the FCC agreed to terminate the investigation in exchange for the manufacturer agreeing to pay $90,000 to the U.S. Treasury and implement a rigorous compliance program.</p><p>The FCC’s sanctions against the manufacturer are not unusual. The FCC often imposes steep fines (often running into six or seven figures) on non-compliant RF equipment suppliers, and requires them to take steps to comply with the rules going forward.</p><p>What is unusual is the warning the FCC issued to RF equipment suppliers that market unauthorized equipment in the future.</p><p>In the third paragraph of the Order, the FCC states:<em> “In the absence of material new evidence relating to this matter, we do not set for hearing the question of [the manufacturer’s] basic qualifications to hold or obtain any Commission license or authorization.”</em></p><p>This is a critical development that affects all IoT suppliers that market their devices in the U.S.</p><p>Because virtually all devices that generate RF energy (including transmitters, readers, and sensors) are subject to FCC authorization before they can be marketed, the FCC’s statement is an assertion of its authority to effectively prohibit non-compliant IoT equipment suppliers from selling their equipment in the U.S.</p><p>Hence, this case underscores the importance of IoT manufacturers and vendors fully complying with FCC rules prior to marketing their equipment.</p><p>IoT operations are regulated under Part 15 of the FCC’s rules for low power devices. Devices that transmit RF energy are classified as “intentional radiators,” while most other devices that generate but do not transmit RF energy are classified as “unintentional radiators.”</p><p>Intentional radiators are authorized via the certification process. A certification is issued by an FCC-authorized Telecommunications Certification Body (“TCB”) based on representations and test data (illustrating compliance with the FCC’s RF emissions limits and other requirements) submitted by the applicant.</p><p>Any entity seeking to obtain certification of an RF device must comply with detailed FCC technical and administrative requirements. The certification and testing information is publicly posted on the FCC’s website.</p><p>Unintentional radiators are authorized by one of two “self-authorization” procedures: verification or declaration of conformity (“DoC”). These procedures are similar; they require the responsible party to submit prototypes of its device to an approved laboratory for testing to ensure compliance with the FCC’s rules.</p><p>If the device passes the test, the lab will issue a verification or DoC. The party doesn’t submit the authorization to the FCC, but must retain it and turn it over to the FCC if requested.</p><p>Regardless of the type of authorization, all RF devices must be properly labeled as compliant with the FCC rules before they’re marketed. Different labeling requirements are imposed, depending on the type of equipment.</p><p>The party seeking authorization — typically the manufacturer, vendor or importer — is the party responsible for ensuring compliance with the FCC’s rules.</p><p>Historically, if an RF device was marketed without proper authorization or was otherwise in violation of the FCC’s rules (including improper labeling or failure to label), as illustrated above, the responsible party would be subject to substantial monetary forfeitures, and other sanctions.</p><p>The most severe penalty the FCC has imposed on an RF equipment supplier was to order it to take its unauthorized equipment off the market. The FCC also ordered vendors to stop selling that equipment.</p><p>The recent FCC ruling adds an extra layer of enforcement concern.</p><p>By stating on the record that it could “de-authorize” RF equipment suppliers, the FCC has given notice to non-compliant suppliers that they could be <em>banned from ever legally marketing their products in the U.S.</em></p><p>It’s critical for IoT equipment suppliers to take steps to ensure continued compliance once their products are on the market, even if they were properly authorized. The FCC requires TCBs to conduct post-market surveillance on at least five percent of the RF equipment they have certified.</p><p>This surveillance is intended to ensure that marketed RF equipment conforms to the technical parameters of the equipment that was tested and authorized. TCBs conduct surveillance by obtaining sample RF devices on the market, measuring the technical characteristics, and comparing them to that of the prototypes that were authorized.</p><p>If the marketed products are not FCC-compliant, the TCB notifies the FCC, which then conducts an investigation. Responsible parties whose RF devices are under surveillance must, upon request, provide the investigating TCB with a sample RF device or vouchers to purchase any sample device it wishes.</p><p>“Come back! Come back! Don’t go without me! Please come back!” Dorothy cried out as the Wizard of Oz’s hot air balloon goes off without her.</p><p>The Wizard replied, “I can’t come back, I don’t know how it works! Good-bye, folks!” And the Wizard sailed off into the stratosphere, never to return to Oz.</p><p><strong>FCC rule compliance is more important than ever.</strong></p><p>IoT equipment suppliers are well advised to work with experienced professionals who understand the FCC rules, in order to evaluate the risks of FCC rule violations and ensure compliance. Savvy IoT equipment suppliers should implement best practices for all their equipment so that the risk of FCC violations are minimized.</p><p>Additionally, any supplier that’s the subject of an FCC investigation that can show it has adopted best practices will probably avoid suffering the worst of the FCC’s penalties.</p><p>All IoT suppliers should understand how the FCC works and the most efficient means of complying with the rules. Suppliers that don’t understand or willfully ignore the FCC’s rules could suffer a fate similar to the Wizard’s, <em>i.e.</em>, exclusion from the U.S. market.</p><p>Last Week in the Future is our weekly newsletter, covering the latest and greatest in IoT, AI, and other tech fields from last week.</p><p><em>Originally published at </em><a href="https://iot-for-all.com/fcc-strictly-enforces-rf-equipment-rules/"><em>iot-for-all.com</em></a><em> on June 6, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25b3251aae1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Equipment Suppliers Be Warned — FCC Strictly Enforces RF Equipment Rules]]></title>
            <link>https://medium.com/@rquirk9/iot-equipment-suppliers-be-warned-fcc-strictly-enforces-rf-equipment-rules-b5dd10482369?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5dd10482369</guid>
            <category><![CDATA[fcc]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 03:37:44 GMT</pubDate>
            <atom:updated>2017-06-07T03:37:44.752Z</atom:updated>
            <content:encoded><![CDATA[<p>In everyone’s favorite classic movie, the seemingly “Great and Powerful Oz” was revealed to be nothing more than a charlatan with feet of clay when a little dog pulled back the curtain that separated the Wizard from the outside world.</p><p>For IoT equipment suppliers, the Federal Communications Commission (“FCC”) is turning out to be the Wizard of Oz in reverse. This agency, which is publicly stating its intent to foster the growth of IoT, is quietly imposing brutal penalties on suppliers that don’t comply with its equipment authorization and marketing rules.</p><p>In a recent release, the FCC took the unprecedented action of threatening to prohibit non-compliant radiofrequency (“RF”) equipment suppliers, including IoT suppliers, from marketing their devices in the U.S.</p><h3>FCC’s Strictly Enforces its RF Equipment Rules</h3><p>On May 23, 2017 the FCC issued an <a href="https://apps.fcc.gov/edocs_public/attachmatch/DA-17-471A1.pdf">Order and Consent Decree</a>, imposing a steep fine and other penalties on an RF equipment manufacturer who failed to comply with the FCC’s testing and authorization rules before marketing its product.</p><p>A complaint was filed with the FCC, alleging that the devices caused interference to radio transmissions. This resulted in the FCC commencing an investigation and enforcement action against the manufacturer.</p><p>In an attempt to mitigate FCC sanctions, the manufacturer agreed to proactively comply with the FCC’s RF equipment rules. The parties subsequently agreed to a consent decree to resolve the case. Specifically, the FCC agreed to terminate the investigation in exchange for the manufacturer agreeing to pay $90,000 to the U.S. Treasury and implement a rigorous compliance program.</p><h3>FCC’s Extraordinary Threat to IoT Equipment Suppliers</h3><p>The FCC’s sanctions against the manufacturer are not unusual. The FCC often imposes steep fines (often running into six or seven figures) on non-compliant RF equipment suppliers, and requires them to take steps to comply with the rules going forward.</p><p>What is unusual is the warning the FCC issued to RF equipment suppliers that market unauthorized equipment in the future.</p><p>In the third paragraph of the Order, the FCC states:<em> “In the absence of material new evidence relating to this matter, we do not set for hearing the question of [the manufacturer’s] basic qualifications to hold or obtain any Commission license or authorization.”</em></p><p>This is a critical development that affects all IoT suppliers that market their devices in the U.S.</p><p>Because virtually all devices that generate RF energy (including transmitters, readers, and sensors) are subject to FCC authorization before they can be marketed, the FCC’s statement is an assertion of its authority to effectively prohibit non-compliant IoT equipment suppliers from selling their equipment in the U.S.</p><p>Hence, this case underscores the importance of IoT manufacturers and vendors fully complying with FCC rules prior to marketing their equipment.</p><h3>IoT Suppliers’ Compliance Requirements</h3><p>IoT operations are regulated under Part 15 of the FCC’s rules for low power devices. Devices that transmit RF energy are classified as “intentional radiators,” while most other devices that generate but do not transmit RF energy are classified as “unintentional radiators.”</p><p>Intentional radiators are authorized via the certification process. A certification is issued by an FCC-authorized Telecommunications Certification Body (“TCB”) based on representations and test data (illustrating compliance with the FCC’s RF emissions limits and other requirements) submitted by the applicant.</p><p>Any entity seeking to obtain certification of an RF device must comply with detailed FCC technical and administrative requirements. The certification and testing information is publicly posted on the FCC’s website.</p><p>Unintentional radiators are authorized by one of two “self-authorization” procedures: verification or declaration of conformity (“DoC”). These procedures are similar; they require the responsible party to submit prototypes of its device to an approved laboratory for testing to ensure compliance with the FCC’s rules.</p><p>If the device passes the test, the lab will issue a verification or DoC. The party doesn’t submit the authorization to the FCC, but must retain it and turn it over to the FCC if requested.</p><p>Regardless of the type of authorization, all RF devices must be properly labeled as compliant with the FCC rules before they’re marketed. Different labeling requirements are imposed, depending on the type of equipment.</p><h3>FCC Penalties for Non-Compliance</h3><p>The party seeking authorization — typically the manufacturer, vendor or importer — is the party responsible for ensuring compliance with the FCC’s rules.</p><p>Historically, if an RF device was marketed without proper authorization or was otherwise in violation of the FCC’s rules (including improper labeling or failure to label), as illustrated above, the responsible party would be subject to substantial monetary forfeitures, and other sanctions.</p><p>The most severe penalty the FCC has imposed on an RF equipment supplier was to order it to take its unauthorized equipment off the market. The FCC also ordered vendors to stop selling that equipment.</p><p>The recent FCC ruling adds an extra layer of enforcement concern.</p><p>By stating on the record that it could “de-authorize” RF equipment suppliers, the FCC has given notice to non-compliant suppliers that they could be <em>banned from ever legally marketing their products in the U.S.</em></p><h3>Post-Market Surveillance of IoT Equipment</h3><p>It’s critical for IoT equipment suppliers to take steps to ensure continued compliance once their products are on the market, even if they were properly authorized. The FCC requires TCBs to conduct post-market surveillance on at least five percent of the RF equipment they have certified.</p><p>This surveillance is intended to ensure that marketed RF equipment conforms to the technical parameters of the equipment that was tested and authorized. TCBs conduct surveillance by obtaining sample RF devices on the market, measuring the technical characteristics, and comparing them to that of the prototypes that were authorized.</p><p>If the marketed products are not FCC-compliant, the TCB notifies the FCC, which then conducts an investigation. Responsible parties whose RF devices are under surveillance must, upon request, provide the investigating TCB with a sample RF device or vouchers to purchase any sample device it wishes.</p><h3>Know How the FCC Works — Your Business Depends on It</h3><p>“Come back! Come back! Don’t go without me! Please come back!” Dorothy cried out as the Wizard of Oz’s hot air balloon goes off without her.</p><p>The Wizard replied, “I can’t come back, I don’t know how it works! Good-bye, folks!” And the Wizard sailed off into the stratosphere, never to return to Oz.</p><p><strong>FCC rule compliance is more important than ever.</strong></p><p>IoT equipment suppliers are well advised to work with experienced professionals who understand the FCC rules, in order to evaluate the risks of FCC rule violations and ensure compliance. Savvy IoT equipment suppliers should implement best practices for all their equipment so that the risk of FCC violations are minimized.</p><p>Additionally, any supplier that’s the subject of an FCC investigation that can show it has adopted best practices will probably avoid suffering the worst of the FCC’s penalties.</p><p>All IoT suppliers should understand how the FCC works and the most efficient means of complying with the rules. Suppliers that don’t understand or willfully ignore the FCC’s rules could suffer a fate similar to the Wizard’s, <em>i.e.</em>, exclusion from the U.S. market.</p><h4>Written by IoT attorney Ronald E. (“Ron”) Quirk, head of the Internet of Things &amp; Connected Devices Practice Group at <a href="http://www.commlawgroup.com/">Marashlian &amp; Donahue PLLC, The CommLaw Group</a>, He can be reached at <a href="https://iot-for-all.com/cdn-cgi/l/email-protection">[email protected]</a> or +1 (703) 714–1305.</h4><h3>Sign up for IoT for All’s newsletter!</h3><p>Last Week in the Future is our weekly newsletter, covering the latest and greatest in IoT, AI, and other tech fields from last week.</p><p><em>Originally published at </em><a href="https://iot-for-all.com/fcc-strictly-enforces-rf-equipment-rules/"><em>iot-for-all.com</em></a><em> on June 6, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5dd10482369" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Equipment Suppliers Be Warned — FCC Strictly Enforces RF Equipment Rules]]></title>
            <link>https://medium.com/@rquirk9/iot-equipment-suppliers-be-warned-fcc-strictly-enforces-rf-equipment-rules-c2e4ab16d5cf?source=rss-7c93ad306cf3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2e4ab16d5cf</guid>
            <category><![CDATA[fcc]]></category>
            <dc:creator><![CDATA[Ronald Quirk]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 03:35:32 GMT</pubDate>
            <atom:updated>2017-06-07T03:35:32.399Z</atom:updated>
            <content:encoded><![CDATA[<p>In everyone’s favorite classic movie, the seemingly “Great and Powerful Oz” was revealed to be nothing more than a charlatan with feet of clay when a little dog pulled back the curtain that separated the Wizard from the outside world.</p><p>For IoT equipment suppliers, the Federal Communications Commission (“FCC”) is turning out to be the Wizard of Oz in reverse. This agency, which is publicly stating its intent to foster the growth of IoT, is quietly imposing brutal penalties on suppliers that don’t comply with its equipment authorization and marketing rules.</p><p>In a recent release, the FCC took the unprecedented action of threatening to prohibit non-compliant radiofrequency (“RF”) equipment suppliers, including IoT suppliers, from marketing their devices in the U.S.</p><h3>FCC’s Strictly Enforces its RF Equipment Rules</h3><p>On May 23, 2017 the FCC issued an <a href="https://apps.fcc.gov/edocs_public/attachmatch/DA-17-471A1.pdf">Order and Consent Decree</a>, imposing a steep fine and other penalties on an RF equipment manufacturer who failed to comply with the FCC’s testing and authorization rules before marketing its product.</p><p>A complaint was filed with the FCC, alleging that the devices caused interference to radio transmissions. This resulted in the FCC commencing an investigation and enforcement action against the manufacturer.</p><p>In an attempt to mitigate FCC sanctions, the manufacturer agreed to proactively comply with the FCC’s RF equipment rules. The parties subsequently agreed to a consent decree to resolve the case. Specifically, the FCC agreed to terminate the investigation in exchange for the manufacturer agreeing to pay $90,000 to the U.S. Treasury and implement a rigorous compliance program.</p><h3>FCC’s Extraordinary Threat to IoT Equipment Suppliers</h3><p>The FCC’s sanctions against the manufacturer are not unusual. The FCC often imposes steep fines (often running into six or seven figures) on non-compliant RF equipment suppliers, and requires them to take steps to comply with the rules going forward.</p><p>What is unusual is the warning the FCC issued to RF equipment suppliers that market unauthorized equipment in the future.</p><p>In the third paragraph of the Order, the FCC states:<em> “In the absence of material new evidence relating to this matter, we do not set for hearing the question of [the manufacturer’s] basic qualifications to hold or obtain any Commission license or authorization.”</em></p><p>This is a critical development that affects all IoT suppliers that market their devices in the U.S.</p><p>Because virtually all devices that generate RF energy (including transmitters, readers, and sensors) are subject to FCC authorization before they can be marketed, the FCC’s statement is an assertion of its authority to effectively prohibit non-compliant IoT equipment suppliers from selling their equipment in the U.S.</p><p>Hence, this case underscores the importance of IoT manufacturers and vendors fully complying with FCC rules prior to marketing their equipment.</p><h3>IoT Suppliers’ Compliance Requirements</h3><p>IoT operations are regulated under Part 15 of the FCC’s rules for low power devices. Devices that transmit RF energy are classified as “intentional radiators,” while most other devices that generate but do not transmit RF energy are classified as “unintentional radiators.”</p><p>Intentional radiators are authorized via the certification process. A certification is issued by an FCC-authorized Telecommunications Certification Body (“TCB”) based on representations and test data (illustrating compliance with the FCC’s RF emissions limits and other requirements) submitted by the applicant.</p><p>Any entity seeking to obtain certification of an RF device must comply with detailed FCC technical and administrative requirements. The certification and testing information is publicly posted on the FCC’s website.</p><p>Unintentional radiators are authorized by one of two “self-authorization” procedures: verification or declaration of conformity (“DoC”). These procedures are similar; they require the responsible party to submit prototypes of its device to an approved laboratory for testing to ensure compliance with the FCC’s rules.</p><p>If the device passes the test, the lab will issue a verification or DoC. The party doesn’t submit the authorization to the FCC, but must retain it and turn it over to the FCC if requested.</p><p>Regardless of the type of authorization, all RF devices must be properly labeled as compliant with the FCC rules before they’re marketed. Different labeling requirements are imposed, depending on the type of equipment.</p><h3>FCC Penalties for Non-Compliance</h3><p>The party seeking authorization — typically the manufacturer, vendor or importer — is the party responsible for ensuring compliance with the FCC’s rules.</p><p>Historically, if an RF device was marketed without proper authorization or was otherwise in violation of the FCC’s rules (including improper labeling or failure to label), as illustrated above, the responsible party would be subject to substantial monetary forfeitures, and other sanctions.</p><p>The most severe penalty the FCC has imposed on an RF equipment supplier was to order it to take its unauthorized equipment off the market. The FCC also ordered vendors to stop selling that equipment.</p><p>The recent FCC ruling adds an extra layer of enforcement concern.</p><p>By stating on the record that it could “de-authorize” RF equipment suppliers, the FCC has given notice to non-compliant suppliers that they could be <em>banned from ever legally marketing their products in the U.S.</em></p><h3>Post-Market Surveillance of IoT Equipment</h3><p>It’s critical for IoT equipment suppliers to take steps to ensure continued compliance once their products are on the market, even if they were properly authorized. The FCC requires TCBs to conduct post-market surveillance on at least five percent of the RF equipment they have certified.</p><p>This surveillance is intended to ensure that marketed RF equipment conforms to the technical parameters of the equipment that was tested and authorized. TCBs conduct surveillance by obtaining sample RF devices on the market, measuring the technical characteristics, and comparing them to that of the prototypes that were authorized.</p><p>If the marketed products are not FCC-compliant, the TCB notifies the FCC, which then conducts an investigation. Responsible parties whose RF devices are under surveillance must, upon request, provide the investigating TCB with a sample RF device or vouchers to purchase any sample device it wishes.</p><h3>Know How the FCC Works — Your Business Depends on It</h3><p>“Come back! Come back! Don’t go without me! Please come back!” Dorothy cried out as the Wizard of Oz’s hot air balloon goes off without her.</p><p>The Wizard replied, “I can’t come back, I don’t know how it works! Good-bye, folks!” And the Wizard sailed off into the stratosphere, never to return to Oz.</p><p><strong>FCC rule compliance is more important than ever.</strong></p><p>IoT equipment suppliers are well advised to work with experienced professionals who understand the FCC rules, in order to evaluate the risks of FCC rule violations and ensure compliance. Savvy IoT equipment suppliers should implement best practices for all their equipment so that the risk of FCC violations are minimized.</p><p>Additionally, any supplier that’s the subject of an FCC investigation that can show it has adopted best practices will probably avoid suffering the worst of the FCC’s penalties.</p><p>All IoT suppliers should understand how the FCC works and the most efficient means of complying with the rules. Suppliers that don’t understand or willfully ignore the FCC’s rules could suffer a fate similar to the Wizard’s, <em>i.e.</em>, exclusion from the U.S. market.</p><h4>Written by IoT attorney Ronald E. (“Ron”) Quirk, head of the Internet of Things &amp; Connected Devices Practice Group at <a href="http://www.commlawgroup.com/">Marashlian &amp; Donahue PLLC, The CommLaw Group</a>, He can be reached at <a href="https://iot-for-all.com/cdn-cgi/l/email-protection">[email protected]</a> or +1 (703) 714–1305.</h4><h3>Sign up for IoT for All’s newsletter!</h3><p>Last Week in the Future is our weekly newsletter, covering the latest and greatest in IoT, AI, and other tech fields from last week.</p><p><em>Originally published at </em><a href="https://iot-for-all.com/fcc-strictly-enforces-rf-equipment-rules/"><em>iot-for-all.com</em></a><em> on June 6, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2e4ab16d5cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>