A Reusable Software Component RSC Approach for the
A Reusable Software Component (RSC) Approach for the ATN Protocol Stack Presented by Thales Avionics ATN 2003 London, UK 23 -24 September 2003 ATN 2003 (London)
ACI’s Certifiable ATN RSC Baseline ACI: Pioneer in ICAO SARPs-compliant ATN Router RSCs n n ACI Partners: Honeywell, Thales ATM, Thales Avionics, Sofreavia Operational deployments for FAA CPDLC Projects w CSC DLAP and Miami ARTCC Ground BIS Router delivered 2000 w In operational service from 2002 for FAA Build I Program n Final release of basic ATN RSC delivered to ATNSI mid-2003 ACI ATN RSCs developed in close coordination with FAA n n ACI coordinated design planning and development with FAA TRUST team (AIR-120) FAA guidelines for RSC methodology FAA audits (SOI 1 -2 -3 -4) and DER follow-up assured that DO 178 B Level C RSC production objectives were met ATN 2003 (London) 2
If the ATN RSC is “done”, why evolve the RRI ? ATNSI/ACI RRI forms basis for an ATN RSC product line n n n RRI RSC specified (1996) for airborne/ground-based ATN OEM needs Problem: VDL/2 specifications not complete at RRI specification freeze Result: RRI RSC can be used for VDL/2, but efficiency-enhancing and DSP-specific VDL 2 optimizations are missing As software supplier to the avionics industry, Thales Avionics decided to develop a product line filling the VDL/2 gap… n n n Thales Avionics ATN VDL/2 RSC product derived from initial RRI RSC First RRI-based avionics ATN VDL/2 router furnished in 2002 Followed-on with first avionics build for in FAA Build 1 in 2003 ATN 2003 (London) 3
Thales Avionics DO 178 B Level C ATN RSC ASE RSC development CM, CPDLC, ADS RSCs RRI RSC development ACI & ATNSI Cert/Nav Authority Coordinate Certification & SOI/Audit VDL/2 RSC ATN VDL/2 RSC Cert/Nav Authority Common Certification Artifacts ATN 2003 (London) 4
VDL/2 Features in Thales Avionics ATN VDL/2 RSC Supports VDL Mode 2 Handoff n Acquisition and processing of ATN Handoff events in Internetworking and Subnetwork Dependent Convergence Function (SNDCF) layers Maintains subnetwork compression context after VDL RGS Handoff n n n Maintains PLP (X. 25) local references & connection information Avoids renegotiating and rebuilding mobile compression data Enhances transmission efficiency on the VDL 2 link Supports Call Redirection Facility n n Ground PLP (X 25) may redirect call to another router, allowing access to any VDL Mode 2 compliant sub-network Support for both DSPs w ARINC: Ground RTR X. 25 address references VPDN w SITA: Ground RTR X. 25 address redirected using X. 121 addressing facility n Supports balancing of traffic load & ensures inter-DSP compatibility ISH PDU processing compliant with current ARINC 631 policy ATN 2003 (London) 5
As an OEM, why use an RSC ? Move from the traditional software development and certification approach (specific development for a specific target) TO A reusable software approach, DO 178 B Level C AC 20 RSC solution n Platform independent solution w Multi-platform target w Stand-alone certification artifacts and life cycle data w Certification credit usable after first approval, on subsequent implementations n Transfer DO 178 B Level C RSC certification artifacts & life cycle data to desired development environment & target platform ATN 2003 (London) 6
The RSC Principle OEM Target 1 C RS loper ve De Target 2 DSP Proto 3 Host 1 Host 2 Ce rt Ap ifica pl tio ica n nt Ce r Au tific tho atio rity n m ste ator y S gr e Int RSC Certification ACCEPTANCE Certification & Navigation Authority Reuse in subsequent programs, by other applicants and/or integrators ATN 2003 (London) 7
From RSC to Integrator SYSTEM DOC. Planning Documents HLR CERTIFICATI ON 3 2 1 1 CERT/NAV Authority INTEGRATION Porting Guides 1. System Integrator Linkage Level C n SRS High Level testing SPEC EICD Verification traceability & Coverage SDD CODE TEST 1 IN A, B OUT LL testing Code RSC DEVELOPME NT Requirements Traceability ATN 2003 (London) High Level testing Level D n High level requirements to system requirements (ATN baseline requirements are ICAO SARPS and PICS) RSC plans to System planning documents 2. RSC defines required porting in Porting Guide - System Integrator builds porting links around RSC 3. System Integrator use RSC low level tests and functional tests – runs tests on OEM target 8
Ease of Portation STREAMS design levies minimal requirements on Hardware platform (minimum customization based on target OS) n Only two basic OS services need be made available thorough a specific customization module w Static Memory Management w Event Timers n n Simple data exchange mechanism among stack modules and application modules Also designed for partitioning between RRI and non-level C applications Designed to facilitate certification n Plans, artifacts, tests & instructions ready for certification re-use ATN 2003 (London) 9
How to get “airborne” with the Thales Avionics ATN RSC The hosting environment exists today… n n n VDR (compliant A 750 supporting VDL Mode 2 RF communication) A communications unit ready to host the ATN VDL/2 RSC Context Management and CPDLC applications with FAA/LINK 2000+ message sets (ED 110) ü Many aircraft are now ready for installation of the DO 178 B Level C certification-ready ATN VDL/2 RSC Communications Unit ATC CM/ ATN CPDLC AIR-GROUND HMI DATALINK FMS radio Flight Parameters ATN-VDL 2 ATN 2003 (London) 10
Thales Avionics ATN VDL/2 RSC allows OEMs & users to enter the Level C ATN world today ! CONTACTS Forrest Colliver Cedric D’Silva ATN 2003 (London) forrest. colliver@thales-avionics. com cedric. d-silva@thales-avionics. com 11
- Slides: 11