 |
|
 |
|
 |
 |
|
The rules in this part are issued pursuant to the authority contained in the Warning, Alert, and Response Network Act, Title VI of the Security and Accountability for Every Port Act of 2006, Public Law 109–347, Titles I through III of the Communications Act of 1934, as amended, and Executive Order 13407 of June 26, 2006, Public Alert and Warning System, 71 FR 36975, June 26, 2006. § 10.2 Purpose.The rules in this part establish the requirements for participation in the voluntary Commercial Mobile Alert System. § 10.10 Definitions.(a) Alert Message. An Alert Message is a message that is intended to provide the recipient information regarding an emergency, and that meets the requirements for transmission by a Participating Commercial Mobile Service Provider under this part. (b) Common Alerting Protocol. The Common Alerting Protocol (CAP) refers to Organization for the Advancement of Structured Information Standards (OASIS) Standard CAP–V1.1, October 2005 (available at http://www.oasis-open.org/specs/index.php#capv1.1 ), or any subsequent version of CAP adopted by OASIS and implemented by the CMAS. (c) Commercial Mobile Alert System. The Commercial Mobile Alert System (CMAS) refers to the voluntary emergency alerting system established by this part, whereby Commercial Mobile Service Providers may elect to transmit Alert Messages to the public. (d) Commercial Mobile Service Provider. A Commercial Mobile Service Provider (or CMS Provider) is an FCC licensee providing commercial mobile service as defined in section 332(d)(1) of the Communications Act of 1934 (47 U.S.C. 332(d)(1)). Section 332(d)(1) defines the term commercial mobile service as any mobile service (as defined in 47 U.S.C. 153) that is provided for profit and makes interconnected service available to the public or to such classes of eligible users as to be effectively available to a substantial portion of the public, as specified by regulation by the Commission. (e) County and County Equivalent. The terms County and County Equivalent as used in this part are defined by Federal Information Processing Standards (FIPS) 6–4, which provides the names and codes that represent the counties and other entities treated as equivalent legal and/or statistical subdivisions of the 50 States, the District of Columbia, and the possessions and freely associated areas of the United States. Counties are considered to be the “first-order subdivisions” of each State and statistically equivalent entity, regardless of their local designations (county, parish, borough, etc. ). Thus, the following entities are considered to be equivalent to counties for legal and/or statistical purposes: The parishes of Louisiana; the boroughs and census areas of Alaska; the District of Columbia; the independent cities of Maryland, Missouri, Nevada, and Virginia; that part of Yellowstone National Park in Montana; and various entities in the possessions and associated areas. The FIPS codes and FIPS code documentation are available online at http://www.itl.nist.gov/fipspubs/index.htm . (f) Participating Commercial Mobile Service Provider. A Participating Commercial Mobile Service Provider (or a Participating CMS Provider) is a Commercial Mobile Service Provider that has voluntarily elected to transmit Alert Messages under subpart B of this part. (g) “C” Interface. The interface between the Alert Gateway and CMS provider Gateway. (h) CMS provider Gateway. The mechanism(s) that supports the “C” interface and associated protocols between the Alert Gateway and the CMS provider Gateway, and which performs the various functions associated with the authentication, management and dissemination of CMAS Alert Messages received from the Alert Gateway. (i) CMS provider infrastructure. The mechanism(s) that distribute received CMAS Alert Messages throughout the CMS provider's network, including cell site/paging transceivers and perform functions associated with authentication of interactions with the Mobile Device. (j) Mobile Devices. The subscriber equipment generally offered by CMS providers that supports the distribution of CMAS Alert Messages. [73 FR 43117, July 24, 2008, as amended at 73 FR 54525, Sept. 22, 2008] § 10.11 CMAS Implementation timeline.Notwithstanding anything in this part to the contrary, a participating CMS provider shall begin an 18 month period of development, testing and deployment of the CMAS in a manner consistent with the rules in this part no later than 10 months from the date that the Federal Alert Aggregator and Alert Gateway makes the Government Interface Design specifications available. [73 FR 54525, Sept. 22, 2008] Browse Next
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
