FCC Seeks Criticism On CAP-based Messaging Formation In To EAS

You are here: Home Page » RF and Mobile » FCC seeks criticism on CAP-based messaging formation in to EAS

Jun 2, 2011 12:16 PM, By Phil Kurz

The Federal Communications Commission (FCC) May 25 adopted a Third Further Notice of Proposed Rulemaking looking criticism on draft changes to Part 11 manners ruling the Emergency Alert System (EAS).

The changes annotate the responsibility of EAS participants to routine inform messages formatted in the Common Alerting Protocol (CAP). The draft revisions look for to confederate CAP-based inform messaging in to the existing EAS and settle conditions to make easy passing from one to another to "next era inform mechanisms."

The observe seeks criticism in a few key areas, inclusive the range of the Part 11 revision; the responsibility to agree to CAP messages; EAS apparatus certification; the 180-day CAP accepting deadline; CAP messages originated by state governors; reworking the procedures for estimate Emergency Action Notifications (EANs); and diverse Part 11 revisions separate to CAP.

As connected to the range of the revision, the assignment draft in the observe that the concentration should be on creation certain CAP-encoded messages entered in to EAS are converted and processed in the same way as messages formatted in EAS Protocol.

The observe tentatively concludes the group should correct Part 11 manners to make coherent that EAS participants contingency be able to modify CAP-formatted messages in to EAS Protocol-compliant EAS messages "in adaptation with the ECIG Recommendations for a CAP EAS Implementation Guide, Version 1.0." The assignment seeks criticism on either it should enable EAS Participants to encounter the responsibility by deploying surrogate CAP conversion devices.

The observe moreover seeks criticism on either and how the group should soak up correspondence with CAP summary transcoding in to its existing acceptance scheme. It moreover asks for criticism on how to perform correspondence contrast and what mandate it should adopt for mutated EAS equipment. The observe moreover asks for criticism on either the assignment should categorize surrogate gadgets "as stand-alone gadgets theme to the same acceptance mandate as stand-alone decoders and encodes."

The assignment moreover asked for criticism in the observe on either the 180-day deadline for CAP correspondence (Sept. 30, 2011) should be lengthened or mutated so that it is triggered by an action other than the Federal Emergency Management Agency's embracing a cause of CAP.

Comments are due 30 days after announcement of the NPRM in the Federal Register. Reply explanation are due 45 days after announcement in the Federal Register.