ATIS J-STD-102-2011 JOINT ATIS TIA CMAS FEDERAL ALERT GATEWAY TO CMSP GATEWAY INTERFACE TEST SPECIFICATION.pdf

1、 JOINT STANDARD J-STD-102 JOINT ATIS/TIA CMAS FEDERAL ALERT GATEWAY TO CMSP GATEWAY INTERFACE TEST 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

2、communications industry. More than 200 companies actively formulate standards in ATIS 17 Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platform

3、s and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partne

4、r for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more information, please visit . The Telecomm

5、unications Industry Association (TIA) is the leading trade association representing the global information and communications technology (ICT) industries through standards development, government affairs, business opportunities, market intelligence, certification and world-wide environmental regulat

6、ory compliance. With support from its 600 members, TIA enhances the business environment for companies involved in telecommunications, broadband, mobile wireless, information technology, networks, cable, satellite, unified communications, emergency communications and the greening of technology. TIA

7、is accredited by ANSI. Notice of Disclaimer October, 2009.1Ref 2 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.2Ref 3 Federal Information Processing Standards Public

8、ation 5-2, Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas; National Institute of Standards and Technology (NIST); May 1987.3Ref 4 IETF RFC 5280 Ref 4, Internet X.509 Public Key Infrastructure Certificate and Cert

9、ificate Revocation List (CRL) Profile; May 2008.4Ref 5 IETF RFC 2560, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol OCSP; June 1999.4Ref 6 IETF RFC 4301, Security Architecture for the Internet Protocol; December 2005.4Ref 7 IETF RFC 4303, IP Encapsulating Security Paylo

10、ad (ESP); December 2005.4Ref 8 IETF RFC 4306, Internet Key Exchange (IKEv2) Protocol; December 2005.4Ref 9 IETF RFC 4718, IKEv2 Clarifications and Implementation Guidelines; October 2006.4Ref 10 IETF RFC 4305, Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ES

11、P) and Authentication Header (AH); December 2005.4Ref 11 IETF RFC 3602, The AES-CBC Cipher Algorithm and Its Use with IPSec; September 2003.4Ref 12 IETF RFC 3447, Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1; February 2003.41This document is available from

12、 the Alliance for Telecommunications Industry Solutions (ATIS) 2This document is available from the Federal Communications Commission. 3This document is available from the National Institute of Technology and Standards (NIST). 4This document is available from the Internet Engineering Task Force (IET

13、F). J-STD-102 3 Ref 13 IETF RFC 4868, Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPSec; May 2007.4Ref 14 IETF RFC 2404, The Use of HMAC-SHA-1-96 within ESP and AH; November 1998.4Ref 15 IETF RFC 2616, Hypertext Transfer Protocol - HTTP/1.1; June 1999.4Ref 16 IETF RFC 1122, Requirements

14、for Internet Hosts Communication Layers; October 1989.4Ref 17 IETF RFC 793, Transmission Control Protocol; September 1981.4Ref 18 IETF STD 5 (RFC 791), Internet Protocol; September 1981.4Ref 19 IETF STD 5 (RFC 792), Internet Control Message Protocol; September 1981.4Ref 20 IETF RFC 2460, Internet Pr

15、otocol, Version 6 (IPv6) Specification; December 1998.4Ref 21 IETF RFC 2464, Transmission of IPv6 Packets over Ethernet Networks; December 1998.4Ref 22 IETF RFC 4291, IP Version 6 Addressing Architecture; February 2006.4Ref 23 IETF RFC 4443, Internet Control Message Protocol (ICMPv6) for the Interne

16、t Protocol Version 6 (IPv6); February 2006.4Ref 24 Federal Information Processing Standards Publication 180-3, Secure Hash Standard; National Institute of Standards and Technology (NIST); October, 2008.33 DEFINITIONS, ACRONYMS, or (b) to such classes of eligible users as to be effectively available

17、to a substantial portion of the public, as specified by regulation by the Federal Communications Commission. 3.1.2 CMSP Gateway: A CMSP administered system, identified by a unique IP address or Fully Qualified Domain Name (FQDN), interfacing to the Federal Alert Gateway and exchanging information pe

18、r this Standard. 3.1.3 CMSP Gateway Group: A CMSP Gateway Group is the set of CMSP Gateways whose IP addresses or Fully Qualified Domain Names are visible to the Federal Alert Gateway across the Reference Point “C” interface. A CMSP Gateway Group will consist of one or two CMSP Gateways. 3.1.4 Analy

19、sis Verification Method: This is a method in which hardware or software designs are compared with known scientific and technical principles, procedures, and practices to estimate the capability of the proposed design to meet the mission and system requirements. 3.1.5 Inspection Verification Method:

20、This method is used to determine compliance without using special laboratory equipment, procedures, or services and consists of a nondestructive static-state examination of hardware, software, and/or technical data and documentation. 3.1.6 Demonstration Verification Method: This is a method in which

21、 qualitative determination of properties is made for a configuration item, including software and/or the use of technical data and J-STD-102 4 documentation. The items being verified are observed, but not quantitatively measured, in a dynamic state. 3.1.7 Test Verification Method: This is a method i

22、n which performance is measured before, during, or after the controlled application of functional and/or environmental stimuli. Quantitative measurements are analyzed to determine the degree of compliance. The process uses standardized laboratory equipment, procedures, and/or services. 3.1.8 Operati

23、onal Testing: Operational testing is the field test, under realistic conditions, of any system or component, for determining that system or components overall effectiveness and suitability for use before field trials or general usage of the system or component. Operational testing provides informati

24、on for the overall assessment of how well a system will provide the desired capability when operated by typical users in the expected environment. 3.2 Acronyms Annex C, Expected CMAC Messages; and Annex D, Expected ACK Messages. This clause is divided into the following test case categories: Federal

25、 Alert Gateway Stand-Alone Test Cases CMAS Gateway Stand-Alone Test Cases Inter-Gateway Test Cases J-STD-102 16 5.1 Federal Alert Gateway Stand-Alone Test Cases This clause defines the test cases for the stand-alone Federal Alert Gateway testing. The test cases in this clause must be successfully co

26、mpleted before executing the inter-gateway test cases in 5.3, Inter-Gateway Test Cases. This clause contains the following stand-alone Federal Alert Gateway test case: CMAS-TC-101 test case for Federal Alert Gateway Profile Data 5.1.1 CMAS-TC-101 Federal Alert Gateway Profile Data Test The purpose o

27、f the Profile Data test procedure (CMAS-TC-101) is to verify that the required parameters and verifiable identities for the CMSP gateways are stored in CMSP Profile of the Federal Alert Gateway. Later inter-gateway tests in 5.3, Inter-Gateway Test Cases, verify that the connections are established i

28、n accordance with these profiles, identities verified, and secure tunnels established. 5.1.1.1 Items To Be Tested The following CMAS entities are to be tested with this test procedure: Federal Alert Gateway 5.1.1.2 Notes Connections are established between the Federal Alert Gateway and the CMSP Gate

29、way according to gateway profiles stored at each end. This test examines and verifies the contents of the stored gateway profiles. This is largely a test conducted by the method of inspection. 5.1.1.3 Test Tools No test tools are necessary to complete this test procedure. 5.1.1.4 Test Capabilities T

30、he following capabilities will be necessary to complete this test procedure: Federal Alert Gateway Test Capabilities: o Ability to display contents of CMSP Profiles 5.1.1.5 Test Personnel Test personnel in the following roles will conduct various test steps as part of this test procedure: Federal Te

31、st Support 5.1.1.6 Requirements Addressed The following requirements from the Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Specification are verified by this procedure. The full requirement text is included in Annex A, Summary of Reference Point “C” Interface Requirements. JCM

32、AS-C-RQMT-0100 J-STD-102 17 JCMAS-C-RQMT-0110 JCMAS-C-RQMT-0120 JCMAS-C-RQMT-0200 5.1.1.7 Prerequisites Conditions The following prerequisite conditions must be established prior to performing this test procedure: All required data for the CMSP Gateways must be previously stored in the CMSP Gateway

33、profile of the Federal Alert Gateway under test. Before this test case can be executed, all entry criteria under 4.5, Pre-Test Configuration Information, must be completed. This is necessary to ensure that all parties involved in testing activities are ready and that interface testing can start with

34、out delay. 5.1.1.8 Test Steps The following table defines the individual test steps that are performed sequentially to complete the test procedure. NOTE: Element values in the Expected Results column that are dependent on the actual test execution are specified with variables, such as CMAC Sent Date

35、-Time and are indicated with brackets. Further discussion is provided in Annex B, Input CAP Messages; Annex C, Expected CMAC Messages; and Annex D, Expected ACK Messages. Table 3: Steps for Test Case CMAS-TC-101 Federal Alert Gateway Profile Data Test STEP # ACTION PERFORMED: EXPECTED RESULTS RQMT I

36、D (JCMAS-C-RQMT #) STEP COMPLETION (PASS, FAIL, N/A) 1 Federal Test Support: Display the contents of the CMSP Profile for the CMSP Gateway Group under test, as stored in the Federal Alert Gateway. Contents of the CMSP Profile are displayed. RQMT-0100 2 Federal Test Support: Verify CMSP Name in the C

37、MSP Profile. Text string containing the unique identification of the CMSP. RQMT-0110 RQMT-0120 RQMT-0200 3 Federal Test Support: Verify CMSP Gateway A Address in the CMSP Profile. Valid IP address or Fully Qualified Domain Name for CMSP Gateway A. RQMT-0110 RQMT-0120 RQMT-0200 4 Federal Test Support

38、: Verify CMSP Gateway B Address alternate in the CMSP Profile. Blank if CMSP has only one gateway. Otherwise, valid IP address or Fully Qualified Domain Name for CMSP Gateway B. RQMT-0110 RQMT-0120 RQMT-0200 5 Federal Test Support: Verify Geo-Location Filtering in the CMSP Profile. “Yes” if this CMS

39、P wants messages to be filtered based on a list of states. “No” otherwise. RQMT-0110 RQMT-0120 RQMT-0200 J-STD-102 18 STEP # ACTION PERFORMED: EXPECTED RESULTS RQMT ID (JCMAS-C-RQMT #) STEP COMPLETION (PASS, FAIL, N/A) 6 Federal Test Support (conditional): Verify List of Geo-Location Filtering State

40、s in the CMSP Profile if Geo-Location Filtering is set to “Yes”. List of two-digit FIPS State Numeric Codes, per FIPS Publication 5-2 (FIPS 5-2) Ref 3, corresponding to the states in which the CMSP would like to receive alerts. If value of the Geo-Location Filtering attribute in the CMSP Profile in

41、step 5 above is “Yes”, then this list should contain at least one valid FIP State Numeric Code. If value of the Geo-Location Filtering attribute in the CMSP Profile in step 5 above is “No”, then this list should contain no entries. RQMT-0110 RQMT-0120 RQMT-0200 5.2 CMSP Gateway Stand-Alone Test Case

42、s This clause defines the test cases for the stand-alone CMSP Gateway testing. The test cases in this clause must be successfully completed before executing the inter-gateway test cases in 5.3, Inter-Gateway Test Cases. This clause contains the following stand-alone CMSP Gateway test cases: CMAS-TC-

43、201 test case for CMSP Gateway Profile Data 5.2.1 CMAS-TC-201 CMSP Gateway Profile Data Test The purpose of the Profile Data test procedure (CMAS-TC-201) is to verify that the required parameters and verifiable identities for the Federal Alert Gateways are stored in the Federal Alert Gateway Profile

44、 of the CMSP Gateway. Later inter-gateway tests in 5.3, Inter-Gateway Test Cases, verify that the connections are established in accordance with these profiles, identities verified and secure tunnels established. 5.2.1.1 Items To Be Tested The following CMAS entities are to be tested with this test

45、procedure: CMSP Gateway 5.2.1.2 Notes Connections are established between the Federal Alert Gateway and the CMSP Gateway according to gateway profiles stored at each end. This test examines and verifies the contents of the stored gateway profiles. This is largely a test conducted by the method of in

46、spection. 5.2.1.3 Test Tools No test tools are necessary to complete this test procedure. J-STD-102 19 5.2.1.4 Test Capabilities The following capabilities will be necessary to complete this test procedure. CMSP Gateway Test Capabilities: o Ability to display contents of the Federal Alert Gateway Pr

47、ofile. 5.2.1.5 Test Personnel Test personnel in the following roles will conduct various test steps as part of this test procedure: CMSP Test Support 5.2.1.6 Requirements Addressed The following requirements from the Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Specification a

48、re verified by this procedure. The full requirement text is included in Annex A, Summary of Reference Point “C” Interface Requirements. JCMAS-C-RQMT-0600 JCMAS-C-RQMT-0700 JCMAS-C-RQMT-0720 5.2.1.7 Prerequisites Conditions The following prerequisite conditions must be established prior to performing

49、 this test procedure: All required data for the Federal Alert Gateways must be previously stored in the Federal Alert Gateway Profile of the CMSP Gateway under test. Before this test case can be executed, all entry criteria under 4.5, Pre-Test Configuration Information, must be completed. This is necessary to ensure that all parties involved in testing activities are ready and that interface testing can start without delay.