The National Association of Broadcasters is reiterating its support for allowing the use of EAS software. But the association doesn’t want the FCC to reduce the time required to fix or replace defective EAS software, at least not yet.
As we’ve reported, the commission recently issued a Further Notice of Proposed Rulemaking (FNPRM) exploring possible rule changes for EAS and Wireless Emergency Alerts. In addition to proposing EAS software, the commission is looking at certain policy and technical updates to improve the effectiveness of EAS.
[Read Radio World’s four-part series about the proposals and questions in the FNPRM.]
The NAB is among those filing comments. The association applauded the commission for considering allowing EAS participants to install EAS software in a single device.
“The FCC correctly frames the proposed software-based EAS model as an opportunity to better integrate EAS into modern broadcasting IP-centric air chains, enhance public safety, and reduce unnecessary regulatory burdens on EAS participants,” NAB wrote.
A software approach, the NAB said, would facilitate remote EAS operations, monitoring and collection of performance data.
“This approach will also promote resiliency by enabling EAS operations to be located at multiple local or edge locations and will optimize maintenance by preventing the need to physically diagnose and repair problems within an EAS hardware device.”
The NAB believes that flexibility should be the watchword of a software-based model.
The FNPRM proposes allowing broadcasters to install EAS software in a single server or computer that manages a station’s EAS functions, or within multiple components to facilitate cross-system integration, which NAB is agreeable to.
“A software approach will promote resilient, redundant EAS operations that can be located at both a station’s studio or transmitter,” NAB wrote, “allowing immediate fail-over if the software’s primary location is inaccessible due to fire, flood, or other disaster.”
However, the NAB believes it would be “premature” to reduce the required time for repairing or replacing defective EAS software before notifying the commission.
Under current rules, participants may operate without defective EAS equipment pending its repair or replacement for 60 days without further FCC authority. The commission tentatively proposes to shorten this to 72 hours for those using software.
“There are still too many uncertainties around the implementation of EAS software to change the deadline at this time,” the NAB believes.
The commission said in the FNPRM that although 60 days is usually sufficient for the repair of hardware devices, a shorter amount of time seems reasonable for software that could be fixed with a patch or other remote solution.
NAB also said such a change is impractical since EAS participants test the functionality of their systems and review the logs of tests weekly at most.
Moreover, in many cases, a problem with a software-based model “could have nothing to do with the software itself, but instead [be] related to the server, computer or other hardware on which the software runs, or the firewall or some other component,” NAB wrote.
The association does believe that a shift from dedicated hardware boxes could help alleviate supply chain issues and encourage more vendors to enter the market.
The NAB says “a software approach could ease overall supply chain problems because software does not have to rely on the manufacture of the purpose-built, physical hardware components for new or replacement proprietary EAS boxes in which software is housed. Nor would EAS equipment have to be shipped to manufacturers or EAS Participants.”
The association also supports the FCC’s focus on the cybersecurity of EAS software. It says it believes a software approach will improve security by facilitating updates to address security vulnerabilities through a software patch instead of forcing personnel to upgrade all of their boxes manually or ship the products to a manufacturer.
NAB agrees with the FCC that EAS software should be tested and approved under a conformity assessment system.
It said it is optimistic that some of the Telecommunications Certification Bodies already approved by the FCC to certify EAS devices can perform conformity testing of software, or would develop this capability in response to demand.
The association generally supports other proposals in the FNPRM for improving the authentication and geotargeting of EAS alerts, using a universal alert identification number to reduce duplicative alerts, or integrating visual symbols into EAS.
The NAB does caution the commission against imposing additional mandates “that could outstrip the capabilities of existing EAS devices and require broadcasters to purchase new EAS equipment.”
The group asked the FCC to “avoid reducing the automated simplicity of EAS or limiting broadcasters’ ability to provide EAS alerts consistent with their journalistic judgement.”
Radio World will report shortly on other comments to the FCC. You can read filed comments in PS Docket 25-224 at the FCC site.
The deadline for reply comments is Sept. 29.
