EAS in Software? The FCC Prepares to Take a Closer Look

The commission wants to explore more changes to EAS and WEA

As we’re reporting elsewhere, the FCC this month is likely to require cybersecurity improvements to help protect the EAS system against hijacking. (Read that story.)

But the commission also plans to lay out several other important changes to the Emergency Alert System and Wireless Emergency Alerts. It has published the draft of a further notice of proposed rulemaking. If adopted on June 25, it will start taking feedback on its ideas.

One notable change would allow the implementation of EAS capabilities via software instead of hardware, though not in the cloud.

“Today, EAS still depends heavily on stand‑alone hardware located outside the core processing systems that broadcast, cable and satellite services now use daily,” the draft FNPRM states.

“We believe that as the industry shifts toward IP‑centric architectures, it is important that the commission consider whether there is an opportunity to modernize EAS processing better to support public safety and to improve operational efficiency for EAS participants.”

The National Association of Broadcasters has pressed the FCC to offer this option, and the idea has been a focus of much discussion among the broadcast alerting community. Now the FCC is taking the issue up officially and is about to invite public comment on a host of specific questions.

“We propose to allow EAS participants to install EAS software in a single device (e.g., a server or computer) that manages EAS functions within the EAS participant’s signal processing system,” the draft states.

“Alternatively, we propose to allow EAS software to be installed across multiple components within that system, thus enabling integration of different EAS functions across multiple system components.”

The draft proposes to require that the software be located at the participant’s local facility, which for broadcasters will mean the studio or transmitter site associated with its licensed service area.

This would prohibit EAS from being generated within cloud-based systems. The FCC said this is consistent with what the NAB has asked for.

The topic of EAS software is a complex one and it occupies 30 paragraphs of the further notice of proposed rulemaking, discussing numerous angles including testing and certification. The commission lays out many questions that it hopes the public will address in comments. Radio World will be exploring these further in weeks to come.

More ideas

The NPRM, if opened by the commission, also will propose to:

Require the authentication of EAS alerts before they are transmitted — “To better secure EAS against cyberattacks, we propose to require EAS participants to reject CAP EAS messages that do not include a valid digital signature.”

Establish a universal alert identification number — This would be “to improve the detection and blocking of duplicate alerts and ensure that WEAs are consistently sent to members of the public who newly enter an alert’s delivery area until the emergency ends.”

Eliminate “outdated WEA geotargeting exceptions that often cause alerts to be received in the wrong locations”

Expand geotargeting options for EAS — “We propose to improve the accuracy of EAS geotargeting by permitting, but not requiring, EAS participants to take advantage of detailed location information that is often available in CAP EAS messages.” Alerting authorities and EAS equipment manufacturers, the FCC said, believe EAS is being underutilized because of its limited geotargeting capabilities. Improvements to EAS geo-targeting could reduce alert fatigue and make alerts more relevant. The draft also proposes to consider new EAS location codes to make messages more understandable to local communities.

Require EAS and WEA to display symbols that match the type of emergency and improve the effectiveness of earthquake alerts to grab the public’s attention — “We expect that the use of symbols could potentially improve comprehension for people with disabilities and people with limited English reading proficiency, hasten public reactions to alerts and reduce milling.”

Retire the 90-character maximum versions of WEA messages

Here’s a link to the draft. The further notice of proposed rulemaking begins on page 25, paragraph 41.