ATIS 0700006-2010 CMAS via GSM UMTS Cell Broadcast Service Specification.pdf

1、 ATIS-0700006 ATIS Standard on - CMAS VIA GSM/UMTS CELL BROADCAST SERVICE SPECIFICATION ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry.

2、More than 250 companies actively formulate standards in ATIS 18 Committees, covering issues including: IPTV, Service Oriented Networks, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, and Billing and Operational Support. In addition, numerous Incubators, Focus and Explorat

3、ory Groups address emerging industry priorities including “Green”, IP Downloadable Security, Next Generation Carrier Interconnect, IPv6 and Convergence. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the Int

4、ernational Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, please visit . Notice of Disclaimer April 9, 2008.1Ref 2 3GPP TS 23.041, 3rd Generation Partnership Project; Technical Specifi

5、cation Group Core Network and Terminals; Technical realization of Cell Broadcast Service (CBS).21This document is available from the Federal Communications Commission. ATIS-0700006 2 Ref 3 3GPP TS 25.419, 3rd Generation Partnership Project; Technical Specification Group RAN; UTRAN Iu-BC Interface: S

6、ervice Area Broadcast Protocol (SABP).2Ref 4 ATIS-0700007, Implementation Guidelines and Best Practices for GSM/UMTS Cell Broadcast Service Specification; October 2009.6Ref 5 Common Alerting Protocol, v. 1.1; OASIS Standard CAP-V1.1; October 2005.3Ref 6 Federal Information Processing Standards Publi

7、cation 6-4, Counties and Equivalent Entities of the United States, its Possessions and Associated Areas; National Institute of Standards and Technology (NIST); August 1990.4Ref 7 WARN Act, Security and Accountability For Every Port Act of 2006 (SAFE Port Act), Pub.L. 109-347, Title VI-Commercial Mob

8、ile Service Alerts (WARN Act).5Ref 8 J-STD-101, Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Specification; October 2009.6Ref 9 J-STD-100, Joint ATIS/TIA CMAS Mobile Device Behavior Specification; January 30, 2009.6Ref 10 3GPP TS 23.038, 3rd Generation Partnership Project; Tec

9、hnical Specification Group Core Network and Terminals; Alphabets and language-specific information.2Ref 11 ISO/IEC 10646:2003, Information technology - Universal Multiple-Octet Coded Character Set (UCS); 2003.7Ref 12 FCC 08-164, Federal Communications Commission Second Report and Order and Further N

10、otice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System; July 8, 2008.1 Ref 13 FCC 08-184, Federal Communications Commission Third Report and Order and Further Notice of Proposed Rulemaking In the Matter of The Commercial Mobile Alert System; August 7th, 2008.1 Ref 14 FCC 08

11、-166, Federal Communications Commission Order on Reconsideration and Erratum In the Matter of The Commercial Mobile Alert System; July 15, 2008.1 Ref 15 3GPP TS 25.324, 3rd Generation Partnership Project; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Broadca

12、st/Multicast Control (BMC).2 Ref 16 ATIS-0700008, Cell Broadcast Entity (CBE) to Cell Broadcast Center (CBC) Interface Specification; March 2010.6Ref 17 3GPP TR 25.925, 3rd Generation Partnership Project; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio i

13、nterface for broadcast/multicast service.2 Ref 18 3GPP TS 44.012, 3rd Generation Partnership Project; 3rd Generation Partnership Project; Technical Specification Group GSM EDGE Radio Access Network; Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface.22This document is

14、 available from the 3rdGeneration Partnership Project (3GPP) 3This document is available from the Organization for the Advancement of Structured Information Standards (OASIS). 4This document is available from the National Institute of Technology and Standards (NIST). 5This document is available from

15、 the U.S. Government Printing Office 6This document is available from the Alliance for Telecommunications Industry Solutions (ATIS) 7This document is available from the International Organization for Standardization (ISO) ATIS-0700006 3 3 DEFINITIONS, ACRONYMS, the boroughs and census areas of Alask

16、a; 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 . 3.1.6 Participating C

17、ommercial 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. 3.2 Acronyms Emergency alert formatting, classes, and elements: Participating CMS P

18、roviders must transmit three classes of alerts - Presidential, Imminent Threat, and AMBER alerts; Geographic targeting (geo-targeting): Participating CMS Providers generally are required to target alerts at the county-level as recommended by the CMSAAC; Accessibility for people with disabilities and

19、 the elderly: Participating CMS Providers must include an audio attention signal and vibration cadence on CMAS-capable handsets; Multi-language Alerting: Participating CMS Providers will not be required at this time to transmit alerts in languages other than English; Availability of CMAS alerts whil

20、e roaming: Subscribers receiving services pursuant to a roaming agreement will receive alert messages on the roamed upon network if the operator of the roamed upon network is a Participating CMS provider and the subscribers mobile device is configured for and technically capable of receiving alert m

21、essages from the roamed upon network; and Preemption of calls in progress: CMAS alerts may not preempt a voice or data session in progress. The First Report and Order Ref 1 specifies rules governing those sections of the CMAS architecture that are within the control of electing CMS providers. These

22、include the CMS Provider Gateway, CMS provider infrastructure, and CMS provider handsets. The rules require each individual CMS Provider Gateway to be able to receive alerts from the Federal Alert Gateway over a secure interface (i.e., Reference Point “C” Interface). NOTE: On July 14th, 2008, the FC

23、C issued an Order on Reconsideration and Erratum Ref 14. 4.2.2 FCC Second Report and Order The FCC released the Second Report and Order for the Commercial Mobile Alert System on July 8, 2008 Ref 12. In the Second Report and Order, the FCC developed rules to be in compliance with section 602(c) of th

24、e WARN Act, which require non-commercial educational (NCE) and public broadcast television station licensees and permittees “to install necessary equipment and technologies on, or as part of, any broadcast television digital signal transmitter to enable the distribution of geographically ATIS-070000

25、6 7 targeted alerts by commercial mobile service providers that have elected to transmit emergency alerts . . .”. The Second Report and Order also defines rules to implement section 602(f) of the WARN Act which requires “technical testing for commercial mobile service providers that elect to transmi

26、t emergency alerts and for the devices and equipment used by such providers for transmitting such alerts”. This technical testing is defined by the FCC rules to be a “Required Monthly Test” and “Periodic Interface Testing”. The Required Monthly Test (RMT) is initiated by the Federal Alert Gateway Ad

27、ministrator, and defines rules for the CMSP to schedule the distribution of the RMT to their CMAS coverage area over a 24 hour period commencing upon receipt of the RMT at the CMSP Gateway. A CMSP may provide mobile devices with the capability of receiving RMT messages. A Participating CMS Provider

28、may provide mobile devices with the capability of receiving Required Monthly Test (RMT) messages. The FCC does not require that CMS providers make available mobile devices that support reception of the required monthly test. The FCC does, however, allow CMS providers to choose to do so. CMS provider

29、s that choose not to make the required monthly test available to subscribers must find alternate methods of ensuring that subscriber handsets will be able to receive CMAS alert messages. These alternative methods are beyond the scope of these standards. The Periodic Interface Testing is a test messa

30、ge between the Federal Alert Gateway and the CMSP Gateway, and is intended to ensure the availability/viability of both gateway functions. The Periodic Interface Test is not designed to test the CMSPs infrastructure nor the mobile devices. The CMSP Gateway shall send an acknowledgement to the Federa

31、l Alert Gateway upon receipt of such an interface test message. 4.2.3 FCC Third Report and Order The FCC released the Third Report and Order for the Commercial Mobile Alert System on August 7, 2008 Ref 13. In the Third Report and Order, the FCC adopted rules implementing Section 602(b) of the WARN A

32、ct. Specifically, the Third Report and Order adopts: Notification requirements for CMS providers that elect not to participate, or to participate only in part, with respect to new and existing subscribers; Procedures by which CMS providers may elect to transmit emergency alerts and to withdraw such

33、elections; A rule governing the provision of alert opt-out capabilities for subscribers; and A compliance timeline under which participating CMS providers must begin CMAS deployment. The rule governing the provision of alert opt-out capabilities for subscribers specifies: CMS providers may provide t

34、heir subscribers with the option to opt out of both, or either, the “Child Abduction Emergency/AMBER Alert” and “Imminent Threat Alert” classes of Alert Messages. CMS providers shall provide their subscribers with a clear indication of what each option means, and provide examples of the types of mes

35、sages the customer may not receive as a result of opting-out. ATIS-0700006 8 Requirements and specifications for the subscribers right to opt out as defined in the Third Report and Order may be found in the Joint ATIS/TIA CMAS Mobile Device Behavior Specification Ref 9. 4.3 Full Reference Diagram Th

36、e following is the functional reference model diagram from Section III.B.10 of the FCC First Report and Order for the Commercial Mobile Alert System, FCC 08-99 Ref 1: Figure 1: CMAS Reference Architecture 5 REQUIREMENTS The Cell Broadcast Service (CBS) supporting CMAS shall support the technical rea

37、lization as specified in 3GPP TS 23.041 Ref 2. This clause will identify requirements specific to the mapping of the CMAS service to the cell broadcast service that are not evident in existing 3GPP specifications. 5.1 Cell Broadcast Center (CBC) Requirements The general requirements for a CBC are sp

38、ecified in 3GPP TS 23.041 Ref 2. The requirements for the CBC interface with the CMSP Gateway are defined in the ATIS Cell Broadcast Entity (CBE) to Cell Broadcast Center (CBC) Interface Specification Ref 16. This clause defines the CBC requirements for the support of CMAS via Cell Broadcast Service

39、: 1. The CBC shall support the ATIS Cell Broadcast Entity (CBE) to Cell Broadcast Center (CBC) Interface Specification Ref 16. 2. The CBC shall retain the information to identify the BSC/RNCs for an Alert until the Alert is cancelled or the Alert expires. ATIS-0700006 9 3. The CBC shall determine th

40、e set of cells in the target area of the CMAS Alert where the message is to be broadcast as defined in 3GPP TS 23.041 Ref 2 (e.g., list of cell sites, location areas, service areas) based upon the geo-target information (e.g., geo-code, polygon, circle) provided to the CBC by the CMSP Gateway. 4. A

41、CBC shall have the capability to adjust the CBE-requested retransmission frequency and duration depending on network conditions or operator policy. 5. The CBC in conjunction with the capabilities of the GSM and UMTS radio networks shall perform retransmissions of the CMAS alert message based upon th

42、e retransmission information provided by the CMSP Gateway. 6. The Cell Broadcast Centers shall have the capability to be deployed in either an active-active or an active-standby server configuration with synchronization of transactional states between the multiple associated Cell Broadcast Centers.

43、7. It shall not be treated or reported as an error condition or as an invalid CMAS alert message if none of the cell sites serviced by the CBC are within the alert area of the CMAS alert message. 8. The CBC shall manage the generation of the Serial Number for an alert message and the Serial Number s

44、hall be unique for a given Message ID per 3GPP TS 23.041 Ref 2. 9. The CBC shall accept CBS messages which contain the CBS message IDs assigned to CMAS only if that CBS message has been received from an authorized CMSP Gateway. NOTE: The method for the CBC to authorize the CMSP Gateway and any assoc

45、iated error handling is beyond the scope of this Standard. 5.2 CMSP Gateway Requirements The requirements for the CMSP Gateway interface with the Federal Alert Gateway are defined in the Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Specification Ref 8. The requirements for the

46、 CMSP Gateway with the CBC are defined in the ATIS Cell Broadcast Entity (CBE) to Cell Broadcast Center (CBC) Interface Specification Ref 16. This clause defines the CMSP Gateway requirements for the support of Cell Broadcast for CMAS Alerts: 1. The CMSP Gateway shall appear as a Cell Broadcast Enti

47、ty in the Cell Broadcast Service network architecture, and thus shall support the CBE to CBC interface defined in the ATIS Cell Broadcast Entity (CBE) to Cell Broadcast Center (CBC) Interface Specification Ref 16. 2. The CMSP Gateway shall provide the CBC with the geo-target information (e.g., geo-c

48、ode, polygon, circle) associated with the specified alert. As such, the CMSP Gateway is not required to know the cell sites supported by the CBCs. 3. The CMSP Gateway shall have the capability to send each CMAS alert message to all or some of the CBCs served by the CMSP Gateway. 4. The CMSP Gateway

49、shall be responsible for defining the frequency and duration of the retransmissions of CMAS alert messages. The CMSP Gateway calculation of the CMAS alert message frequency and duration will be based upon CMSP policies and upon the expiration date and time of the CMAS alert message. The CMSP Gateway will provide the retransmission information to the CBC. 5. The CMSP Gateways shall have the capability to be deployed in either an active-active or an active-standby server configuration with syn