Provide PDF Format
ATIS J-STD-102
- Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Text Specification
- standard by Alliance for Telecommunication Industry Solutions, 01/01/2011
- Publisher: ATIS
$193.00$385.00
This Standard defines the operational testing procedures for communications between the Federal Alert Gateway and the Commercial Mobile Service Provider (CMSP) Gateway over the Reference Point "C" Interface including any processing functionality within the FEMA-administered Commercial Mobile Alert Service (CMAS) entities and within the CMSP-administered CMAS entities that directly impact communications over the Reference Point "C" Interface.
Purpose:
The purpose of interface testing is to evaluate whether systems or components transmit data and control information correctly to each other. In addition, the tests defined in this Standard may be used during regression testing when updates are made to either the Federal Alert Gateway or the CMSP Gateway.
Specifically, the Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Testing Specification defines a set of tests to verify the following minimal set of functionality during interface and regression testing:
This Standard is not intended to define test cases for the complete development lifecycle, nor is it intended to provide complete requirements verification or complete compliance testing. Requirements verification testing is typically performed during the unit, integration, and system testing phases and is beyond the scope of this Standard.
Purpose:
The purpose of interface testing is to evaluate whether systems or components transmit data and control information correctly to each other. In addition, the tests defined in this Standard may be used during regression testing when updates are made to either the Federal Alert Gateway or the CMSP Gateway.
Specifically, the Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Testing Specification defines a set of tests to verify the following minimal set of functionality during interface and regression testing:
- Ability to complete the C-Interface startup procedures:
- Ability to bring up the IPSec tunnel.
- Ability to bring up the TCP/IP connection.
- Ability to receive, process, and acknowledge valid CMAS Alert, Update, Cancel, and RequiredMonthly Test (RMT) messages.
- Ability to handle transmission control cease and resume messages.
- Ability to handle link test messages.
- Ability to perform CAP retrieval.
This Standard is not intended to define test cases for the complete development lifecycle, nor is it intended to provide complete requirements verification or complete compliance testing. Requirements verification testing is typically performed during the unit, integration, and system testing phases and is beyond the scope of this Standard.