APCS SIR Sect J Att J.1.4 Amend 3.docx

Federal Aviation Administration

U.S. Department of Transportation

VoICE APC System Traffic Load Generator Requirements November 15, 2022

Focal Point Air Traffic Organization (ATO) - Technical Operations Air Traffic Control (ATC) Communications Services Voice Switching and Recording Team, AJM-315

800 Independence Avenue SW

Washington, DC 20591

TABLE OF CONTENTS

i section 1: Introduction and overview Introduction and Overview This attachment describes the effort required for the development of the APC System Traffic Load Generator (ATLG) solution for use during the APC System Test Program.

section 2: functional requirements Functional Requirements The ATLG must contain all required software/hardware to perform all defined functions when connected via a networked interface.

The ATLG must contain all required software/hardware to perform all defined functions when connected via a legacy interface.

The ATLG must provide a Computer Human Interface (CHI) that allows authorized operators access to all features/functions.

The ATLG must interface to and communicate with the APC System without the use of additional tools.

The ATLG must interface to and communicate with the APC System without the use of additional test equipment.

The ATLG must be designed as an independent test solution separate from APC System hardware/software configuration items that satisfy requirements contained in Attachment J.1.1, VoICE APC System Technical Specification.

The development of the ATLG software must meet the requirements set forth in Attachment J.1.7, VoICE APC System Tool Software Requirements.

The ATLG must be designed to meet the maximum system sizing requirements listed in Table 3-6 while supporting traffic loads specified in Table 3-7 of Attachment J.1.1, VoICE APC System Technical Specification.

The ATLG must be configurable to provide test load conditions to verify the Setup/Teardown Throughput Timing Requirements listed in Table 3-8 of Attachment J.1.1, VoICE APC System Technical Specification during PBH call traffic loading as specified in Table 3-7.

The ATLG must be configurable to provide test load conditions to verify the Setup/Teardown Throughput Timing Requirements listed in Table 3-8 of Attachment J.1.1, VoICE APC System Technical Specification during PBM call traffic loading as specified in Table 3-7.

The ATLG must simulate the management and call traffic activity[footnoteRef:1] of APCs up to the sizing requirements listed in Table 3-7 of Attachment J.1.1, VoICE APC System Technical Specification. [1: APC management activity is defined as any network and/or data processing load placed on the APCS that does not pertain to placing and receiving calls. An example of this would be periodic status poll requests/responses to/from a management system. APC call traffic activity is defined as any network and/or data processing load placed on the APCS by APCs that supports call setup and audio transmission. Examples of this would include all SIP and RTP traffic to/from APCs.]

The ATLG must meet the PBH Call Distribution requirements listed in Table 3-7 of Attachment J.1.1, VoICE APC System Technical Specification.

The ATLG must meet the PBM Call Distribution requirements listed in Table 3-7 of Attachment J.1.1, VoICE APC System Technical Specification.

ATLG Throughput Timing Performance Measurement

1. The ATLG Throughput Timing Performance Measurement must allow users to configure the quantity and type of A/G interfaces to measure APC System throughput timing performance and grades of service to ensure compliance with Tables 3-7 and 3-8 of Attachment J.1.1, VoICE APC System Technical Specification.

The ATLG must manage call generation for throughput timing measurements.

The ATLG must initiate simultaneous performance measurement tests.

The ATLG must time stamp APC System events and responses with results recorded in milliseconds.

The ATLG must monitor time stamped events (start and stop times) at each point in the APC System architecture as defined in Section 3.2.4.2.1 of Attachment J.1.1, VoICE APC System Technical Specification to measure performance.

ATLG Call Traffic Loading Functions

1. The ATLG must simulate up to 200% Peak Busy Minute (PBM) and 200% Peak Busy Hour (PBH) call traffic load for up to maximum APC gateways allowed per Table 3-6 of Attachment J.1.1, VoICE APC System Technical Specification.

NOTE: Call traffic loads exceeding 100% PBM and PBH are not subject to the average holding times specified in Table 3-6 of Attachment J.1.1, APC System Technical Specification; all other parameters and notes specified in Table 3-6 remain applicable.

The ATLG must permit configurable system loading by the user with no larger than 10% increments up to the defined limit.

The ATLG must initiate and receive simultaneous A/G calls.

The ATLG must automatically run a self-test (Diagnostic/Error handling) after application start and to report the status of self-test.

ATLG Computer Human Interface (CHI) Functions

1. The ATLG must provide a computer Human Interface (CHI) that allows users access to all functions and features of the ATLG.

The CHI display must default to the English language.

The CHI must permit users to perform the following operations as a minimum:

1. Health status of ATLG components;

2. Obtain connectivity status of APC System components under test by the ATLG;

3. Display, print and save to file all reports in format compatible with the Microsoft Office suite of products;

4. Access and display stored data;

5. Specify system load increments;

6. Select load types to be executed (in any combination);

7. Manually start, stop, pause, resume, restart, and repeat throughput timing tests;

8. Dynamically display the percentage of APC System load rate achieved for each load type executed; and

9. Dynamically display the status and progress of throughput timing tests being executed.

ATLG Security ATLG Non-Functional Security Requirements The ATLG, must meet the following Non-Functional security requirements:

1. The Contractor must accommodate and support FAA audit of Contractor security processes, and provide supporting artifact of such processes when requested of the FAA.

The Contractor must ensure that only authorized personnel have access to software codes, documentation, passwords, authentication processes, hardware, and associated components of the ATLG during installation and testing.

The Contractor must safeguard the ATLG, including hardware, software, and documentation not yet installed in FAA facilities against damage, pilferage, unauthorized access, and modification.

The Contractor must deliver, install, and test the ATLG in a manner that maintains security against damage, pilferage, unauthorized access, and modification.

The Contractor must protect sensitive data, software, and hardware from unauthorized disclosure, access, and corruption at all times during production, storage, delivery, and installation.

The Contractor must notify the FAA immediately if unauthorized disclosure, access, or corruption occurs.

The Contractor must document the detailed system architecture, interfaces, ports, protocols, data flows, security functionality and capabilities in accordance with Section 5.2 of Attachment J.1.7 VoICE APC System Tool Software Requirements document.

On-Going Security Authorization Support The Contractor must support the FAA in yearly security authorization activities, to include providing as-requested technical information regarding system implementation changes of the security functionality of the system.

ATLG Functional Security Requirements Successful Login, Unsuccessful Logon Attempts, Logoff

1. The ATLG must provide tool access when the user has been successfully authenticated with a valid user account.

The ATLG must deny tool access when the user has not authenticated with a valid user account Session Lock

1. The ATLG must initiate a session lock (e.g., lock the screen) after 15 minutes of user inactivity.

The ATLG must retain the session lock until a user reauthenticates.

The ATLG must, when session lock is enabled, allow the user to resume the session by successful reauthentication.

Auditable Events

1. The ATLG must automatically generate an audit record for each system security event when the security event occurs.

The ATLG must generate audit records for unsuccessful login.

The ATLG must generate audit records for successful login.

The ATLG must generate audit records for logoff.

Content of Audit Records

1. The ATLG must generate audit records that contain the type of event.

The ATLG must generate audit records that contain the date of event.

The ATLG must generate audit records that contain the time of event.

Audit Storage Capacity The ATLG must allocate sufficient storage capacity to store at least the previous 90 days of audit records in online storage.

ATLG Test Reporting

1. The ATLG must provide results of APC System loading during the APC System Test Program that include but not limited to:

8. Start and stop time call traffic loading was active, in the format dd/mm/yyyy, hh:mm:ss;

8. Total time duration call traffic loading was active, in the format ddd:hh:mm:ss;

8. Number of call traffic actions per load type scheduled/attempted;

8. Number of call traffic actions per load type that were blocked/failed to complete;

8. Number of call traffic actions per load type successfully completed;

8. Total number of all call traffic actions (all load types) scheduled/attempted;

8. Total number of all call traffic actions (all load types) successfully completed;

8. Average PBM load rate percentage achieved over the total time duration call traffic loading was active;

8. Average PBH load rate percentage achieved over the total time duration call traffic loading was active;

8. Average PBM load rate percentage achieved over the last 60 minutes;

8. Average PBH load rate percentage achieved over the last 60 minutes;

8. Average PBM load rate percentage achieved over the last 12 hours;

8. Average PBH load rate percentage achieved over the last 12 hours;

8. Average PBM load rate percentage achieved over the last 24 hours;

8. Average PBH load rate percentage achieved over the last 24 hours.

1. The ATLG must provide results of each APC System throughput timing performance measurement taken during the APC System Test Program that include but are not limited to:

9. Name of the measurement taken;

9. Start and stop time throughput timing test was active, in the format dd/mm/yyyy, hh:mm:ss;

9. Total time duration throughput timing test was active, in the format hh:mm:ss;

9. Total number of measurements taken;

9. Number of measurements within specification per Table 3-8 of Attachment J.1.1, VoICE APC System Technical Specification;

9. Number of measurements exceeding the maximum response time per Table 3-8 of Attachment J.1.1, VoICE APC System Technical Specification;

9. Percentage of total number of measurements taken within specification per Table 3-8 of Attachment J.1.1, VoICE APC System Technical Specification; and

9. A delimited text file containing each performance measurements taken every iteration the test was run.

1. The ATLG must display and generate the following logs/reports:

10. Event Log Report containing as a minimum: time stamped entries for when loading and throughput timing tests are started and stopped.

10. Error Log Report containing as a minimum: time stamped entries for loading and throughput timing test failures; connection failures to APC System components under test; and ATLG component failures.

10. Call Traffic Loading Test Report containing as a minimum the metrics and call statistics specified in Section 2.5 a.

10. Throughput Timing Performance Measurement Test Report containing as a minimum the metrics and call statistics specified in 2.5 b.

10. All logs and reports must use English as the default language.

1. The ATLG must ensure that throughput timing reports can be generated based on the test results collected during the APC System Test Program.

1. The ATLG must generate the metrics and call statistics (Section 2.5 a. and b.) under all PBM test conditions.

1. The ATLG must generate the metrics and call statistics (Section 2.5 a. and b.) under all PBH test conditions.

1. The ATLG must display and report the metrics and call statistics generated for all PBM test conditions.

1. The ATLG must display and report the metrics and call statistics generated for all PBH test conditions.

1. The ATLG must report calls blocked during the throughput timing performance testing.

1. The ATLG must report connection status to the APC System components under test.

1. The ATLG must store test results and error logs.

1. The ATLG must store all events and errors generated at the time they occur.

1. The ATLG must report the Grade of Service (GOS).

Networked ATLG Test Reporting

1. The ATLG must report Call Detail Records and Quality metrics per call on APC System components utilized in throughput timing performance testing, including:

1. Call summary statistics, including but not limited to start time, duration, etc.

1. Round Trip Delay (RTD) statistics

1. One Way Delay (OWD) statistics

1. Packet – Packet Delay Variation

1. Signal Level

1. Signal Quality section 3: networked atlg-related functions Networked ATLG-related Functions The ATLG must be compliant with ED-137 as implemented in accordance with Attachment J.1.1, VoICE APC System Technical Specification.

Networked ATLG Call Generator

1. The ATLG must support the generation of simultaneous SIP sessions with the same APC.

1. The ATLG must support the generation of simultaneous SIP sessions with multiple APCs.

1. The ATLG must support the transmission of simultaneous RTP streams to different SIP sessions on the same APC.

1. The ATLG must support the transmission of simultaneous RTP streams to different SIP sessions on multiple APCs.

1. The ATLG must send and receive tones.

1. The ATLG must support Voice Coding as defined in Attachment J.1.1, VoICE APC System Technical Specification.

section 4: acronyms Acronyms

image1.jpeg