<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:cf="https://www.futureplc.com/rss/content-flags"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/eas-alerts" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Eas-alerts ]]></title>
                <link>https://www.tvtechnology.com/tag/eas-alerts</link>
        <description><![CDATA[ All the latest eas-alerts content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Wed, 08 Apr 2026 19:39:35 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ FCC Extends Audible Crawl Rule Waiver for 18 Months ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/regulatory-legal/fcc-extends-audible-crawl-rule-waiver-for-18-months</link>
                                                                            <description>
                            <![CDATA[ Agency delays enforcement until Nov. 2027 of a rule requiring emergency information provided visually must be made audibly accessible ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">fYNgS52d3YBXgS74hBv4PR</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/6ij26v58WDrysCemifpp9d-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 08 Apr 2026 19:39:35 +0000</pubDate>                                                                                                                                <updated>Thu, 09 Apr 2026 22:53:44 +0000</updated>
                                                                                                                                            <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                    <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Broadcast]]></category>
                                                    <category><![CDATA[Platform]]></category>
                                                                                                                    <dc:creator><![CDATA[ George Winslow ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/DpfRvfTR4a9YTrjyaV72ze.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/6ij26v58WDrysCemifpp9d-1280-80.jpg">
                                                            <media:credit><![CDATA[Creative Commons]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Emergency Alert System]]></media:description>                                                            <media:text><![CDATA[Emergency Alert System]]></media:text>
                                <media:title type="plain"><![CDATA[Emergency Alert System]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/6ij26v58WDrysCemifpp9d-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON</strong>—The <a href="https://www.tvtechnology.com/tag/fcc" target="_blank">Federal Communications Commission</a>’s Media Bureau has issued a Memorandum and Order once again delaying the implementation of the so-called “Audible Crawl Rule.” <a href="https://www.tvtechnology.com/news/nab-seeks-delay-in-rules-requiring-audio-description-of-emergency-alert-graphics-maps" target="_blank">Implementation of the rule has been delayed six times in the past</a>. </p><p>The rule applies to “video programming distributors and video programming providers,” including TV stations, who must “provide an aural representation of visual, non-textual emergency information that is displayed during non-newscast programming, such as radar maps or other graphics, on a secondary audio stream” for persons who are blind or visually impaired. </p><p>The rule was adopted on April 8, 2013, with an original effective date of May 26, 2015, but has been waived and delayed “to the present day because a technical solution for automated descriptions of the information in such graphics does not exist,” the NAB said <a href="https://www.fcc.gov/ecfs/document/1115662625005/1" target="_blank">in a Nov. 15 2024 filing</a>. </p><p>As it subsequently examined the issue, the Media Bureau granted two temporary six-month extensions until May of 2026. </p><p>In granting a waver until November of 2027, the Bureau ruled that “the record shows `special circumstances’ warrant a waiver.  The Bureau continues to recognize the critical importance of making emergency information accessible to individuals who are blind or visually impaired.  We find that the best way to ensure the continued availability of emergency information is to extend the waiver that has been in place since 2015.  Compliance with the Audible Crawl Rule as it is currently written cannot be implemented through technical means with regard to visual but non-textual emergency information, and there is no indication that any such technical means will be available soon.”</p><p>“We grant the waiver for a 18-month period (through November 29, 2027) or until there is a ruling on the underlying Petition, whichever is sooner,” the Bureau added. “During the more than ten years that the successive waivers have been in place, the record indicates that there has been little progress in developing a workable technical compliance solution, and there is no indication of imminent progress.  A 18-month waiver will allow the Commission to consider the pending Petition, and it will allow the industry to consider compliance solutions.”   </p><p>The full Memorandum and Order is available <a href="https://www.fcc.gov/document/mb-extends-waiver-audible-crawl-rule-18-months" target="_blank">here</a>. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ FCC Proposes $504K Fine on Fox for EAS Violations ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/fcc-proposes-fining-fox-dollar504k-for-eas-violations</link>
                                                                            <description>
                            <![CDATA[ Commission penalizes network for transmitting EAS Tones during November 2021 NFL game ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">fkKLhkcBdBhRE6PB9SaWJP</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/rGfTWjxwZDiDed5hz8pbtg-1280-80.png" type="image/png" length="0"></enclosure>
                                                                        <pubDate>Wed, 25 Jan 2023 15:53:55 +0000</pubDate>                                                                                                                                <updated>Wed, 25 Jan 2023 18:44:07 +0000</updated>
                                                                                                                                            <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                                                                <author><![CDATA[ tom.butts@futurenet.com (Tom Butts) ]]></author>                    <dc:creator><![CDATA[ Tom Butts ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/Ym75XZxKuaGiZGj7nMGeGM.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/png" url="https://cdn.mos.cms.futurecdn.net/rGfTWjxwZDiDed5hz8pbtg-1280-80.png">
                                                            <media:credit><![CDATA[Fox Sports]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Fox Sports]]></media:description>                                                            <media:text><![CDATA[Fox Sports]]></media:text>
                                <media:title type="plain"><![CDATA[Fox Sports]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/rGfTWjxwZDiDed5hz8pbtg-1280-80.png" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON—</strong>The FCC has levied a fine of $504,000 against Fox for “willfully violating” commission rules on transmitting EAS Tones during regular programming. The violation occurred during an NFL promotional segment aired Nov. 28, 2021.</p><p>Fox described the promotional segment as a “short comedic advertisement” for an upcoming game, which was aired as part of the Fox NFL Sunday pre-game show. The promo used an approximately three-second excerpt of the EAS Tone commonly used to precede broadcast emergency alerts: two simultaneous tones of 853 Hz and 960 Hz and the network admitted that the three-second excerpt had been downloaded or recorded from a YouTube video.  </p><p>The network acknowledged that it had not obtained permission to air the tones that were broadcast over 18 of its owned-and-operated stations, and transmitted to 190 network affiliated stations nationwide.  It was also broadcast on Fox Sports Radio and on the “Fox Sports on XM” channel on Sirius XM.</p><p>FCC warned that such use of EAS Tones when unwarranted could lead to “alert fatigue,” in which viewers will dismiss EAS Tones during actual emergencies. </p><p>“Despite being shorter in duration than the full EAS Tones, the three-second EAS Tone used in the Promotional Segment possessed the same dual-tone frequency, pitch, and timbre as the actual EAS Tones, and was recognizable by viewers or listeners as substantially similar to the EAS Tones,” the commission said. “The Promotional Segment’s “comedic tone” also did not alter or neutralize its overall effect of falsely warning listeners and viewers of a non-existent emergency, as the EAS Tones were clearly audible, cognizable, and appropriated for a non-emergency use.  This manner of appropriation of the EAS Tones is exactly the type of simulation that the Commission’s rules seek to address and prohibit in order to avoid diluting the EAS Tones’ real meaning over time.”</p><p>Although fines starting at $8,000 are usually imposed by the commission, it said Fox’s violations were particularly egregious and deserved to be increased, noting that it was “not a minor violation.”</p><p>“Despite touting that it is fully knowledgeable and has a policy &apos;barring the improper use of the EAS Attention Signals,&apos; which was purportedly &apos;made known generally to employees of Fox involved in the production of programming,&apos; Fox admits that &apos;all personnel involved in creation and review of the Nov. 28 Segment … lacked full understanding of Fox’s policy against use of EAS Attention Signals.&apos;”  </p><p>It also criticized Fox for the way it handled the situation afterwards, noting that the network was required to notify the commission within 24 hours after it discovered its mistake and that just sending an email to the commission was not made in “good faith.” </p><p>Thirdly, it justified the fee increase by pointing out that Fox reported revenues of $4.44 billion in the relevant quarter. “Fox clearly has an ability to pay, and there is nothing in the record that would indicate that the penalty is otherwise excessive,” it said. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ FCC, Local Agencies to Test WEA Alerts in September ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/fcc-local-agencies-to-test-wea-alerts-in-september</link>
                                                                            <description>
                            <![CDATA[ Focus of alerts on Sept. 12 and 13 is on local performance ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">rQYdTZ79NABCxWn7YKme8o</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/ngmNfsKwihiMtW8muRRvPd-1280-80.jpeg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 01 Sep 2022 19:33:45 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                                                                                    <dc:creator><![CDATA[ Paul McLane ]]></dc:creator>                                                                                    <dc:source><![CDATA[ null ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/ngmNfsKwihiMtW8muRRvPd-1280-80.jpeg">
                                                            <media:credit><![CDATA[Getty]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Getty]]></media:description>                                                            <media:text><![CDATA[Getty]]></media:text>
                                <media:title type="plain"><![CDATA[Getty]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/ngmNfsKwihiMtW8muRRvPd-1280-80.jpeg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Local tests of Wireless Emergency Alerts will be held in September.</p><p>The FCC says it is working with several dozen state and local government agencies to assess the tests’ accuracy, and it is asking wireless providers to provide information on their performance.</p><p>Chairwoman Jessica Rosenworcel said in a statement, “Wireless Emergency Alerts are a life-saving tool, but emergency managers tell us that they need more information on the geographic accuracy of these alerts in order to use them with confidence.”</p><p>She said safety officials want to know that alerts will reliably reach the public “throughout — but not beyond — targeted areas during emergencies.” The tests are intended to assess geographic accuracy, reliability and speed.</p><p>For the tests on Sept. 12 and 13, each state and local agency partner will send a Wireless Emergency Alert to the public in a targeted local area that it selects.</p><p><em>[The list of test partners can be found on </em><a href="https://www.fcc.gov/document/fcc-grants-waiver-local-wireless-emergency-alert-performance-tests" target="_blank"><em>page 6 of the FCC order</em></a><em>, and includes target test areas and test dates and times.]</em></p><p>The alert will sound and appear on compatible mobile devices using participating wireless networks in that area.</p><p>“The alert message will make clear that it is only a test and contain a link for the recipient to complete a survey about their receipt of the alert,” the FCC stated.</p><p>“Each agency will have a control group of volunteers in the targeted geographic area complete the survey, and members of the public may also do so.”</p><p>Authorities send WEA alerts through FEMA’s Integrated Public Alert and Warning System to wireless providers, which push them on to compatible mobile devices. The FCC says participation by wireless providers is “voluntary but widespread.” Those providers must deliver the alerts to the area specified by the originator with no more than a 1/10 of a mile overshoot where technically feasible.</p><p>“According to industry estimates, approximately 60 percent of active smartphones in the U.S. support this ‘enhanced geotargeting’ functionality, with the number to increase as consumers replace their devices with newer models,” the FCC stated.</p><p>This is part of ongoing efforts by the FCC to improve WEA and EAS systems. In 2021 the commission worked with 11 agencies to assess the delivery of WEAs during a nationwide test.</p><p><em>This article originally appeared on TV Tech sister brand Radio World.</em></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ FCC Proposes Improvements to Emergency Alert System Messages ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/fcc-proposes-improvements-to-emergency-alert-system-messages</link>
                                                                            <description>
                            <![CDATA[ The Commission has passed a Notice of Proposed Rulemaking that would improve the clarity and accessibility of EAS messages and launched an inquiry into further improvements ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">bn25XJZWgKjDJhPvhVAkuU</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/NB8CTMkXutprpYo7P6VCPi-1280-80.png" type="image/png" length="0"></enclosure>
                                                                        <pubDate>Tue, 14 Dec 2021 17:52:28 +0000</pubDate>                                                                                                                                <updated>Tue, 14 Dec 2021 17:53:15 +0000</updated>
                                                                                                                                            <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                                                                                    <dc:creator><![CDATA[ George Winslow ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/DpfRvfTR4a9YTrjyaV72ze.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/png" url="https://cdn.mos.cms.futurecdn.net/NB8CTMkXutprpYo7P6VCPi-1280-80.png">
                                                            <media:credit><![CDATA[FEMA]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[FEMA]]></media:description>                                                            <media:text><![CDATA[FEMA]]></media:text>
                                <media:title type="plain"><![CDATA[FEMA]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/NB8CTMkXutprpYo7P6VCPi-1280-80.png" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON, D.C.</strong>—The Federal Communications Commission has adopted a Notice of Proposed Rulemaking that would improve the clarity and accessibility of visual Emergency Alert System messages to the public, particularly to people who are deaf or hard of hearing.</p><p>In addition, the FCC has adopted a Notice of Inquiry and has launched an examination of broader measures to enhance the system’s overall functionality and accessibility.</p><p>In the Notice of Proposed Rulemaking adopted on December 14, the Commission proposed rule changes to improve the clarity and descriptiveness of the visual message that appears on television during nationwide Emergency Alert System tests in order to better inform members of the public who are unable to access the test’s audio message.</p><p>The FCC also proposed to require broadcasters, cable systems, and other Emergency Alert System participants to check for and use, when available, the internet-based version of alerts, which offer superior visuals, rather than the legacy “over-the-air” version when transmitting alerts to the public. </p><p>In a Notice of Inquiry adopted on December 14, the Commission is seeking comment on whether the legacy Emergency Alert System architecture can be modified, augmented, or redesigned to enable government alert originators to relay more visual information as part of, or in parallel with, their alert message. </p><p>The Commission is also seeking comments on ways to improve the legacy Emergency Alert System architecture to enable more functionality within the system as a whole.</p><p>In a statement on the need to improve the accessibility of the EAS system Chairwoman Jessica Rosenworcel noted that “late last week, a tornado tore through Arkansas, Illinois, Kentucky, Mississippi, Missouri, and Tennessee,” providing “a stark reminder of just what devastating weather can do.”</p><p>“It is hard to know what kind of warning is adequate when freak weather like this comes along,” she admitted. “But we do know that we are seeing these kinds of storms with greater frequency.  And I think we have a responsibility to improve the warning systems we have, to get people the news they need in an emergency.” </p><p>One problem with the existing system, she highlighted, was that when EAS alerts are displayed on the TV screen, “they have both an audio component and a visual component. In other words, they feature both a recorded message and a text crawl. But because of the legacy television architecture of EAS, the audio component may not always match the visual text. This can mean that in some circumstances, less information may be conveyed to either those individuals who have access only to the visual component or to those who have access only to the audio component,” which “can cause real confusion” and create problems for people with disabilities. </p><p>To improve the system, Rosenworcel noted that “we propose to improve the script for visual text during nationwide tests of the legacy system” and make “changes to our rules that would bring similar clarity to nationwide tests using the newer, internet-based common alerting protocol, or CAP.  Then, because there is greater ability to include enhanced text with CAP alerts, we propose to require broadcasters to check to see if a CAP version of an alert is available when they receive an emergency alert over the legacy system.  Finally, we ask what additional steps can be taken to rethink the architecture of EAS and improve the functionality of the system as a whole.” </p><p>As part of the inquiry into improving EAS, she stressed that “we&apos;re looking for all the good ideas here, both big and small, because we know first-hand they can make a difference.  In fact, the agency’s Public Safety and Homeland Security Bureau has been in close contact with FEMA, state and local emergency managers, carriers, and broadcasters in the states the tornado visited last week.  We know that improving outreach is vital and that keeping our alerting practices up-to-date is essential—and that is what we seek to do here.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ NAB Doubts Streamers Can Provide EAS Alerts Reliably ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/nab-doubts-streamers-can-provide-eas-alerts-readily</link>
                                                                            <description>
                            <![CDATA[ Says technical challenges and policy questions make the proposal “infeasible” ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">bE93tN5DwuGEte5vtgWKjn</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/nsvyyz6J7t96dFHpMg3nH5-1280-80.png" type="image/png" length="0"></enclosure>
                                                                        <pubDate>Mon, 17 May 2021 15:46:42 +0000</pubDate>                                                                                                                                <updated>Mon, 17 May 2021 18:23:31 +0000</updated>
                                                                                                                                            <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                                                                                    <dc:creator><![CDATA[ Michael Balderston ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/png" url="https://cdn.mos.cms.futurecdn.net/nsvyyz6J7t96dFHpMg3nH5-1280-80.png">
                                                            <media:credit><![CDATA[FEMA]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[EAS]]></media:description>                                                            <media:text><![CDATA[EAS]]></media:text>
                                <media:title type="plain"><![CDATA[EAS]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/nsvyyz6J7t96dFHpMg3nH5-1280-80.png" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON—</strong>While acknowledging the benefits that would likely stem from expanding access to EAS alerts via internet services, including streaming platforms, NAB also does not believe that such an expansion is possible at this point in time.</p><p>The NAB shared its thoughts in comments to the FCC regarding the proposal to provide EAS alerts through the internet as laid out by the National Defense Authorization Act for Fiscal Year 2021 and the study that Congress requested of the proposition.</p><p>“At least for the time being, certain technical challenges and open policy questions make it extremely burdensome, and likely infeasible, to update the EAS system to enable alerts to consumers provided through the internet, including through streaming services,” NAB wrote.</p><p>Local broadcasters are the primary providers of EAS alerts currently and help ensure the reliability of the system, per NAB. While radio and TV stations are able to provide any alerts through their websites or through simulcasts of their stations, there are limitations. For instance, NAB says OTT viewers only get alerts when a station’s own programming is playing, meaning that no alert would appear during a commercial break like it would on traditional broadcast.</p><p>NAB says there are two main obstacles for pure-play online content streamers to participate in the existing EAS ecosystem. First, is the geographic service areas that streaming services offer, which are generally available wherever there is internet access. Streaming services do not typically incorporate any localized infrastructure that would allow them to monitor EAS alerts based on geography or even type, NAB argues. The association says streamers lack the infrastructure and local presence needed, and even if they did, the responsibility of monitoring such services across the country would likely be “extremely problematic.”</p><p>Second, NAB says that geo-targeting of EAS alerts would be “virtually impossible.” Most streaming services use software that does not specifically request or have access to a subscriber’s location data. As part of any installation of EAS equipment, streamers would need a tool for monitoring FIPS codes across the U.S. and to only deliver alerts to pertinent areas. “Such a mechanism neither exists nor could it be efficiently incorporated into current streaming systems.”</p><p>There are also potential issues with fixed-location internet service providers having trouble accurately pinpointing a user’s location, and the increase of consumers using virtual private networks to connect to the internet for increased privacy, with NAB saying 31% of current internet users rely on VPNs.</p><p>Without accurate location information, NAB believes that there could be instances where, for example, a viewer in Virginia sees an alert meant for California and becomes confused.</p><p>NAB says that this debate over expanding EAS to the internet is similar to the previous consideration of requiring EAS obligations to DBS providers, when the FCC recognized the technical difficulties that would require.</p><p>Beyond the technical obstacles, NAB says there are policy issues as well. Platforms like Netflix, Hulu and Spotify are generally unregulated by the FCC, it notes. In addition, many streaming services are based outside of the U.S. or are partially owned by foreign shareholders; and many streamers use hardware and servers that they do not directly control.</p><p>“All of these factors would raise questions of how the FCC could effectively extend the EAS rules to internet streamers, how streaming services could ensure the security and reliability of EAS operations and what would happen if they failed to execute EAS alerts,” NAB wrote.</p><p>NAB therefore believes that the FCC should report to Congress that enabling EAS alerts through the internet, and streamers, is “too complex and likely infeasible at this time.”</p><p>NAB’s full statement is <a href="https://www.nab.org/documents/filings/NAB_EAS_NOI_Comments_5-14-21.pdf" target="_blank"><u>available online</u></a>. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Digital Alert Systems Brings EAS to Kaltura Cloud TV ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/digital-alert-systems-brings-eas-to-kaltura-cloud-tv</link>
                                                                            <description>
                            <![CDATA[ EAS-NET protocol is now integrated into the Kaltura TV Platform. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">jV7BmNY3wSx5crYbUpQbVv</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 14 May 2019 18:23:01 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Cloud]]></category>
                                                    <category><![CDATA[Infrastructure]]></category>
                                                                                                                    <dc:creator><![CDATA[ Michael Balderston ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>DENVER & NEW YORK—</strong>EAS alerts have been brought to the cloud by Digital Alert Systems, which has announced that it has integrated its EAS-NET communications protocol to the Kaltura TV Platform, a cloud TV service.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="2frp25jWm24SGH8zmRjdAd" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd.jpg" mos="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>It is a requirement for North American operators and media companies to provide emergency alerts to viewers via their TV service. Through this integration, joint customers can comply with Emergency Alert System/Common Alerting Protocol regulations by providing critical emergency messages within their Cloud TV deployments.</p><p>Kaltura was able to support EAS-NET by boosting its push notification and in-app messaging capabilities. The Kaltura platform can now receive alert information over EAS-NET and dispatch the alert in real time to Cloud TV client applications, including mobile devices, managed STBs and unmanaged STBs. Viewers will be able to see the emergency messages as push notifications on connected screens when watching content or browsing on the app.</p><p>“We are in the business of helping our customers transform their legacy TV services into next-generation cloud and IP-based TV experiences,” said Gideon Gilboa, Kaltura senior vice president of product and marketing, Media and Telecom. “This includes all of the benefits of OTT—not only personalization, multiscreen apps and improved TCO and agility, but also the ‘nuts and bolts’ of traditional pay TV, such as EAS alerts.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>