Goto Section: 10.310 | 10.330 | Table of Contents

FCC 10.320
Revised as of September 1, 2021
Goto Year:2020 | 2022
  §  10.320   Provider alert gateway requirements.

   Link to an amendment published at  86 FR 46790 , Aug. 20, 2021.

   This section specifies the functions that each Participating Commercial
   Mobile Service provider is required to support and perform at its CMS
   provider gateways.

   (a) General. The CMS provider gateway must provide secure, redundant,
   and reliable connections to receive Alert Messages from the Federal
   alert gateway. Each CMS provider gateway must be identified by a unique
   IP address or domain name.

   (b) Authentication and validation. The CMS provider gateway must
   authenticate interactions with the Federal alert gateway, and validate
   Alert Message integrity and parameters. The CMS provider gateway must
   provide an error message immediately to the Federal alert gateway if a
   validation fails.

   (c) Security. The CMS provider gateway must support standardized
   IP-based security mechanisms such as a firewall, and support the
   defined WEA “C” interface and associated protocols between the Federal
   alert gateway and the CMS provider gateway.

   (d) Geographic targeting. The CMS provider gateway must determine
   whether the provider has elected to transmit an Alert Message within a
   specified alert area and, if so, map the Alert Message to an associated
   set of transmission sites.

   (e) Message management—(1) Formatting. The CMS provider gateway is not
   required to perform any formatting, reformatting, or translation of an
   Alert Message, except for transcoding a text, audio, video, or
   multimedia file into the format supported by mobile devices.

   (2) Reception. The CMS provider gateway must support a mechanism to
   stop and start Alert Message deliveries from the Federal alert gateway
   to the CMS provider gateway.

   (3) Prioritization. The CMS provider gateway must process an Alert
   Message on a first in-first out basis except for Presidential Alerts,
   which must be processed before all non-Presidential alerts.

   (4) Distribution. A Participating CMS provider must deploy one or more
   CMS provider gateways to support distribution of Alert Messages and to
   manage Alert Message traffic.

   (5) Retransmission. The CMS provider gateway must manage and execute
   Alert Message retransmission, and support a mechanism to manage
   congestion within the CMS provider's infrastructure.

   (f) CMS provider profile. The CMS provider gateway will provide profile
   information on the CMS provider for the Federal alert gateway to
   maintain at the Federal alert gateway. This profile information must be
   provided by an authorized CMS provider representative to the Federal
   alert gateway administrator. The profile information must include the
   data listed in Table 10.320(f) and must comply with the following

   (1) The information must be provided 30 days in advance of the date
   when the CMS provider begins to transmit WEA alerts.

   (2) Updates of any CMS provider profiles must be provided in writing at
   least 30 days in advance of the effective change date.

   Table 10.320(f)—CMSP Profile on Federal Alert Gateway
   Profile parameter Parameter election Description
   CMSP Name Unique identification of CMSP.
   CMSP gateway Address IP address or Domain Name
       Alternate IP address Optional and subject to implementation.
   Geo-Location Filtering  If “yes” the only CMAM issued in the
   listed states will be sent to the CMSP gateway.
   If “no”, all CMAM will be sent to the CMSP gateway.
   If yes, list of states CMAC Geocode for state List can be state name or
   abbreviated state name.

   (g) Alert logging. The CMS provider gateway must perform the following

   (1) Logging requirements. Log the CMAC attributes of all Alert Messages
   received at the CMS Provider Alert Gateway, including time stamps that
   verify when the message is received, and when it is retransmitted or
   rejected by the Participating CMS Provider Alert Gateway. If an Alert
   Message is rejected, a Participating CMS Provider is required to log
   the specific error code generated by the rejection.

   (2) Maintenance of logs. Participating CMS Providers are required to
   maintain a log of all active and cancelled Alert Messages for at least
   12 months after receipt of such alert or cancellation.

   (3) Availability of logs. Participating CMS Providers are required to
   make their alert logs available to the Commission and FEMA upon
   request. Participating CMS Providers are also required to make alert
   logs available to emergency management agencies that offer
   confidentiality protection at least equal to that provided by the
   federal Freedom of Information Act (FOIA) upon request, but only
   insofar as those logs pertain to Alert Messages initiated by that
   emergency management agency.

   [ 73 FR 43117 , July 24, 2008, as amended at  78 FR 16808 , Mar. 19, 2013;
    81 FR 75725 , Nov. 1, 2016]


Goto Section: 10.310 | 10.330

Goto Year: 2020 | 2022
CiteFind - See documents on FCC website that cite this rule

Want to support this service?

Report errors in this rule. Since these rules are converted to HTML by machine, it's possible errors have been made. Please help us improve these rules by clicking the Report FCC Rule Errors link to report an error.
Helping make public information public