Minimum Aviation System Performance Standards for Aircraft ...

3.3 System Application Requirements
3.4 Subsystem Requirements
3.4.1 Subsystem Requirements for ASSAP (Dave Elliott)
ASSAP is the surveillance and separation assurance processing component of ASA.
ASSAP processes incoming data from own-ship, and other aircraft/vehicles (A/V), and
derives information for display on the CDTI. Flight crew command and control inputs
that affect application functions are also processed by ASSAP. In the future, ASSAP is
expected to provide alerting and guidance information to the flight crew via the CDTI.
The two major functions of ASSAP are surveillance processing and applications
processing. Functional requirements for ASSAP are described in §3.4.1.4.
Surveillance processing:
• Establishes tracks from ADS-B, ADS-R, and TIS-B traffic reports
• Cross-references traffic from different surveillance sources (ADS-B, ADS-R,
TIS-B, and TCAS)
• Estimates track state (e.g., position, velocity), and track quality
• Deletes tracks that are beyond the maximum allowable coast time for any ASA
applications
Applications processing:
• Determines the appropriateness of track information for various applications, and
forwards the track data to the CDTI
• May performs alerting functions in future applications
• May derive guidance information in future applications
Each ASA transmit participant should input to ASSAP the highest quality state data that
is available on-board; this information should be the same as that used for ADS-B
transmission. ASSAP assesses own-ship performance and transmitted data quality as
specified in Table x.y and assesses received traffic data quality as specified in Table x.y
to determine if an active application can be supported.
Figure 3.4.1 summarizes ASSAP input / output interfaces to other subsystems and
indicates the sections where the interface, functional, and performance requirements can
be found in this document.
© 20xx, RTCA, Inc.
87