ATIS/TIA-J-STD-102:2011

$78.00

Joint ATIS/TIA CMAS Federal Alert Gateway to CMSP Gateway Interface Test Specification

Published By	Publication Date	Number of Pages
TIA	2011	125

Guaranteed Safe Checkout

Category: TIA

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

Description

This Standard defines operational testing procedures for the
communications between the Federal Alert Gateway and the Commercial
Mobile Service Provider (CMSP) Gateway over the C-Interface. This
includes operational testing of all processing functionality within
the FEMA-administered Commercial Mobile Alert Service (CMAS)
entities and the CMSP-administered CMAS entities that directly
impacts communications over the C-Interface. Operational testing of
all other processing within the FEMA and CMSP entities including
the CMSP infrastructure 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 Required Monthly 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.

Additional information