# Presentation: 069855

## AATT TO 24Communications System Architecture Development for Air Traffic Management and Aviation Weather Information Dissemination

- May, 2000

## Agenda

- Task Overview
- Requirements Collection
- Candidate Architecture Concepts
- Functional Architecture
- Current/Near Term Link Definition
- Communication Load Analysis
- Architecture  Alternatives
- Transition Schedules
- Gap Discussion
- Summary

- May, 2000

## AATT TO 24 Team

- SAIC:							Program Manager: Seana Gallagher
- Aeronautical Engineer: Matt Olson
- Consulting Engineer: John McKinley, Neal Blake
- ARINC:
- Technical Director: Doug Blythe
- Senior Engineer: Jacob Heletz, Griff Hamilton, Bill Kolb
- Program Manager: Al Homans
- TRW:
- Senior Comm. Engineer: Ken Zemrowski
- NAS Architect/Senior Engineer: Steve Decker
- Technical Director: Charlie Pate
- Chief Systems Engineer: Dr. Paul Carlock
- Senior Systems Engineer: Dean Johnson
- Crown Consulting

- May, 2000

## AATT TO 24 Team

- NASA Technical Direction
- NASA Glenn Research Center:
- COTR: Steve Mainger
- Program Manager: Konstantinos Martzaklis
- Robert Kerczewski
- NASA Langley Research Center:
- Jim Chamberlain
- Sheila Conway

- May, 2000

**Task 1**
- Identification
- of User Needs

**Task 2**
- Communications
- System
- Functional
- Requirements

**Task 3**
- Communications
- System
- Engineering
- Requirements

**Task 4**
- Preliminary
- Comm. System
- Architecture
- Concepts

**Task 5**
- 2015 AATT
- Architecture

**Task 6**
- 2007 ATM
- Architecture

**Task 7**
- 2007 AWIN
- Architecture

**Task 8**
- Transition

**Task 11**
- Areas for
- Research and
- Development

**Task 10**
- Communications
- Technology
-  Gaps

**Task 9**
- Current Data
- Links

**Final Report**
**May 26, 2000**

- May, 2000

## Task Relationship

- May, 2000

## Requirements Collection

- Master Source List

*FARs*
*Concept Documents*
*Industry Reports*

**Task 1**

*RTCA DO’s*
*FAA Requirements Documents*
*Consultant Studies and Reports*
*Concept Documents*

**Task 2**

*ATN SARPs*
*RTCA DO’s*
*FAA Requirements Documents*
*Consultant Studies and Reports*
*EuroControl Documents*

**Task 3**

**Task 1**
- Identification of User Needs

**Task 2**
- Communications
- System
- Functional
- Requirements

**Task 3**
- Communications
- System
- Engineering
- Requirements

- May, 2000

## Data Repository

**Functional Communications Requirements**

**Requirements Database**

- Airspace Users			  Message Characteristics
- Functional Capabilities		  Communications Requirements NAS
- Service Architecture		  Delay, Availability, Integrity
- System Level Requirements	  Source Traceability

**User Needs**

- May, 2000

## Database Screen

- May, 2000

## User Friendly Forms

- May, 2000

## Task 4

- Preliminary
- Candidate
- Comm. System
-  Architecture
- Concepts

- Task 4 developed a common base for architecture concepts.
- Mature to Present (Top Down)
- Benefits Driven (Based on Equipage)
- Evolutionary Path
- Architecture Selection Challenges

- May, 2000

## Air-Ground Comm Functional Architecture

**AIRCRAFT**

**OTHER**
**AUTHORIZED**
**USERS**

**NWIS**

**INTERNATIONAL**
**MILITARY**
**FBO’S**

**TV, RADIO**
**INTERNET**

**AUTOMET**

**CPC**

**CPDLC**

**DSSDL**

**ADS-B**

**POSITION/**
**INTENT**

**VOICE**

**MESSAGING**

**NEGOTIATION**

**AIRCRAFT**

**AOC**
**COMM**

**WEATHER**
**NAS**
** ****STATUS**

**AIRLINES**
**OPERATIONS**
**CENTER**

**AIR**
**TRAFFIC**
**CONTROL**

**OPERATIONS, MAINTENANCE**

**ADS-B**

**AIRBORNE WEATHER OBSERVATION**

**    ****FIS****  TIS  APAXS**

**Commercial**
**Service Provider**

- May, 2000

## Benefits Driven Concept

- Tactical Control

- Strategic CDM

- Automated
- Negotiation

- Broadcast

- 2-way

- Info
- Base

- DSS-
- based

- Human-
- based

- Air Traffic Control

- Aircraft

- Range of User Equipage

- DSSDL

- CPC
- CPDLC
- AOCDL

- CPC
- CPDLC

- Technical
- Concepts

- Static Data

- FIS

- TIS
- ADS-B
- FIS
- AUTOMET

- Aeronautical Operational Control

- AOCDL

- May, 2000

## Architecture Selection Challenges

- Conflicting Report Data - contributes to load estimate uncertainty
- Air Traffic forecasts
- Message definition, size, and frequency
- Selection of Hybrid Architecture should be driven by Cost, Schedule, or Performance considerations
- Cost not a consideration for this task
- 2007 Schedule not a driver - given no cost constraints
- Performance - function of a selected link - many unknowns
- ADS-B link decision - can have major impact on architecture selection
- SATCOM implementation - driven by commercial cabin services (could lead to class 1 Avionics cost/performance issues)
- FIS-B implementation - commercial design implementation can drive overall architecture

- May, 2000

## Begin with 2015 Analysis

**Task 5 AATT****2015 Architecture**

**Task 7 AWIN****2007****Architecture**

- 2015 AATT Mature State Drives 2007 AATT
- 2007 AWIN analysis conducted in context of 2007

**Task 6 AATT****2007 Architecture**

- May, 2000

## Process

- Analysis

- Functional
- Architecture

- Link
- Capabilities

- SYNTHESIS

- Viable
- Alternatives

- May, 2000

## Functional Analysis

- 9 Technical Concepts
- Defined Message categories and message types for each Technical Concept
- Concept Description
- Concept Diagram

- May, 2000

## Operational Concept - Tech Concept

- May, 2000

## Concept Description - Flight Information Service

- Aircraft continually receive dynamic Flight Information to enable common situational awareness
-  Weather Information
-  NAS Status
-  NAS Traffic Flow Status
- Note: 	We assume that static data will be loaded on 	aircraft via portable storage media prior to flight.

- May, 2000

## 2015 Flight Information Service - FIS 

- 2015 Flight Information Service - FIS

**SATCOM**

**Comm**
**I/F**

**SAT**
**COM**
**RCVR**

**VDL**
**RCVR**

**MFDS**

**OASIS**

**NOTAM**

**FIS**
**PROC**

**WARP**

**NAS / SUA**
**STATUS**

**NEXRAD**

**NWS**

**Wx**
**Vendor(s)**

**ADAS**

**Portable**
**Storage**
**Media**

**Wx**
**Sensor(s)**

**AAIS**

**ATIS**

**CSP**

**NWIS INTEGRATED**
**NETWORK**

**Ground-Based Pilot PC**

- May, 2000

##  FIS Products

- _Primary Source:_ Data Communications Requirements, Technology and Solutions for Aviation Weather Information Systems (Phase I Report), Lockheed Martin Aeronautical Systems 1999.
- _Assumptions:_
- Projected weather products are bit-mapped pictures in a multi-dimensional grid.
- Broadcast weather products represent computer generated, synthesized, integrated information.
- These products represent generic projections of products that will be available five to 10 years in the future.
- _Secondary Source:_ RTCA DO 237, Aeronautical Spectrum Planning, 1997

- May, 2000

## 2015 FIS Load Analysis Results

- _2-way_
- Worst case scenario:  En Route airspace with high density Terminal area and four major Airports

- _Broadcast_
- Regional scenario:  En Route airspace with 5 Terminal/Airport areas

- (K-bits per second)

- (K-bits per second)

- Note: (x) is domain multiplier

- Note: (x) is domain multiplier

- May, 2000

## 2015 FIS Viable Alternatives

- Broadcast is preferable for FIS
- VDL-B can support a regional broadcast of FIS data
- Allocation of only 2 frequencies per CSP poses coverage / interference problems for National implementation
- UAT, SATCOM can support Regional and National implementation

- May, 2000

## Concept Description - Automated Meteorological Transmission

- Aircraft report airborne weather data to improve weather nowcasting/forecasting.
- Also know as...
- MDCRS, E-MDCRS [NOAA, NWS]
- ACARS [NOAA, FSL]
- EPIREPS [NASA]
- AUTOMET definition is currently under the auspices of the RTCA SC 195
- Minimum Interoperability Standards (MIS) for Automated Meteorological Transmission (RTCA DO-252)
- wind, temperature, water vapor and turbulence.

- May, 2000

## Automated Meteorological Transmission - AUTOMET

**SATCOM**

**Comm**
**I/F**

**SAT**
**COM**
**XCVR**

**VDL**
**XCVR**

**UAT**
**XCVR**

**NWS**

**PROC**

**FSL**

**NASA**

**Wx**
**Sensor(s)**

**AOC**

**CSP**

**FMS**

- May, 2000

## 2015 AUTOMET Load Analysis Results

-  (K-bits per second)

- AUTOMET message contains
- Wind
- Temperature
- Humidity
- Turbulence
- Message size and frequency based on 1999 RTCA MIS
- Assume no AUTOMET in Airport Domain
- Worst case scenario:  En Route airspace with high density Terminal area

- Note: (x) is domain multiplier

- May, 2000

## 2015 AUTOMET Viable Alternatives

- AUTOMET type data currently delivered via ACARS network
- Assume transition to VDL-2 network
- VDL-2 national network operated by CSP since 2001
- VDL-2 single frequency effective data rate is 19.2 kbps.
- 4 frequencies used for AOCDL - 76.8 kbps
- This is sufficient to support the projected demand
- UAT, SATCOM could support the load requirement
- Unlikely use if existing network can support requirement

- May, 2000

## Concept Description - Controller/Pilot Voice Communication

- CPC supports tactical control and strategic CDM.
- CPC communication remains the foundation of air traffic control.
- It is critical to maintain a high quality, robust voice communication service.
- Digitized voice service can be combined with data service provided QOS is maintained

- May, 2000

## 2015 - CPC Controller/Pilot Voice Communication

- ATC
- Voice

**Voice**
**Switch**

**VHF**
**Voice**
**Radio**

- Pilot
- Voice

**FTI Comm**
**Network**

**VDL**
**Radio**

- Voice
- Data

- Existing
- A/G Radio

- NEXCOM
- RADIO

**Comm**
**Head**

- May, 2000

## 2015 CPC Load Analysis Results

- In 2015 most routine messages are sent via CPDLC
- Clearance Delivery
- Transfer of Communication
- Initial contact
- Altimeter
- Our Analysis assumed an average of 1.5 call-seconds per minute per flight

- Call-seconds per second

- May, 2000

## 2015 CPC Viable Alternatives

- Our communication load analysis indicates that a single VDL-3 sub-channel is sufficient to support controller pilot communication under worst case loading conditions.

- May, 2000

## 2015 Architecture Alternatives Summary

**2015 Architecture Alternatives Summary**

- May, 2000

## Top Down vs Bottom Up Architecture

- Top Down Architecture optimizes at the “system” level
- May contain sub-optimal solutions for 1 or more sub-systems
- For this task:  Minimize the number of radio’s on the aircraft and the ground infrastructure
- Bottom Up Architecture optimizes at the “sub-system” level
- Optimizes each sub-system without regard to total system
- For this task:  Select optimum radio

- May, 2000

## Top Down Observations

- Human / DSS ATC interfaces satisfied by VDL-3 Link - NAS Architecture Baseline
- CPC
- CPDLC
- DSSDL
- Human / AUTOMET AOC interfaces satisfied by VDL-2 Link - Consistent with current planning, Not in NAS Arch
- AOCDL
- AUTOMET
- Dynamic Information Base satisfied with Broadband Link - No integrated plan for NAS Broadband data
- FIS
- TIS
- ADS-B
- Broadband data solution can be Terrestrial or Space Based

-  (K-bits per second)

- May, 2000

## Broadband Data Considerations

- ADS-B link decision - can have major impact on Terrestrial vs Space based decision
- SATCOM implementation - driven by commercial cabin services (could lead to class 1 Avionics cost/performance issues)

- May, 2000

## 2015 Top Down Architecture - SATCOM Data

- Primary 2-way
- CPC / CPDLC / DSSDL

- Secondary 2-way
- AOC / AUTOMET

- Data Receive
- FIS / TIS / APAXS

- Data Transmit
- ADS-B

- SATCOM

- VDL-2

- VDL-3

- UAT
- VDL-4
- Mode-S

- CSP
- Network

- FTI
- Network

- CSP
- Network

- CSP
- Interface

- _Ground_

- _Link_

- _Aircraft_

- ADS-B
- Site

- FTI
- Network

- NEXCOM
- Site

- FTI
- Network

- May, 2000

## 2015 Top Down Architecture - UAT Data

- Primary 2-way
- CPC / CPDLC / DSSDL

- Secondary 2-way
- AOC / AUTOMET

- Data Receive
- FIS / TIS

- Data Transmit
- ADS-B

- UAT

- VDL-2

- VDL-3

- CSP
- Network

- FTI
- Network

- CSP
- Network

- CSP
- Interface

- _Ground_

- _Link_

- _Aircraft_

- SATCOM

- CSP Network

- APAXS

- ADS-B
- Site

- FTI
- Network

- NEXCOM
- Site

- FTI
- Network

- May, 2000

## Interim Architecture Development

- 2007 AATT Architecture driven by 2015 AATT Architecture
- Multiple Communication Solutions exist - pick solutions on the path to 2015 AATT
- 2007 AWIN Architecture part of the 2007 AATT Architecture
- FIS
- AUTOMET
- CPC

- May, 2000

## 2007 AATT CSA

- Human voice communications satisfied by VHF-AM
- CPC:  Transition to VDL-3
- ATC data message interfaces satisfied by VDL-2 Link - NAS Architecture Baseline
- CPDLC:  Transition to VDL-3
- DSSDL:  Transition to VDL-3
- Human / AUTOMET AOC interfaces satisfied by VDL-2 Link - No change from 2015, Not part of NAS Architecture
- AOCDL
- AUTOMET
- Dynamic Information Base satisfied with Multiple Links - No integrated plan for NAS Broadband data
- FIS:  CSP supports VDL-B and Broadband solution
- TIS:  Broadband solution
- ADS-B:  Follow ADS-B link decision

- May, 2000

## 2007 Architecture Alternatives Summary

**2007 Architecture Alternatives Summary**

- May, 2000

## 2007 Architecture - SATCOM Data

- Secondary 2-way
- CPDLC / DSSDL
- AOC / AUTOMET

- FIS - Regional

- Data Transmit
- ADS-B

- SATCOM

- VDL-2

- VHF-AM

- UAT
- VDL-4
- Mode-S

- NEXCOM
- Site

- CSP
- Network

- ADS-B
- Site

- FTI
- Network

- CSP
- Network

- CSP
- Interface

- _Ground_

- _Link_

- _Aircraft_

- VDL-B

- FIS / TIS / APAXS

- FTI
- Network

- FTI
- Network

- CPC - Voice

- May, 2000

## 2007 Architecture - UAT Data

- Secondary 2-way
- CPDLC / DSSDL
- AOC / AUTOMET

- FIS - Regional

- Data Transmit
- ADS-B

- UAT

- VDL-2

- VHF-AM

- NEXCOM
- Site

- CSP
- Network

- ADS-B
- Site

- FTI
- Network

- CSP
- Network

- CSP
- Interface

- _Ground_

- _Link_

- _Aircraft_

- VDL-B

- FIS / TIS

- FTI
- Network

- FTI
- Network

- CPC - Voice

- SATCOM

- CSP Network

- APAXS

- May, 2000

##  TASK 8

-  TASK 8
- Transition

- Defines the key milestones and activities for implementation of each of the technical concepts and communications links.

- May, 2000

## AATT Communication Architecture Schedule - FIS

**AATT Communication Architecture Schedule - FIS**

- 00

- 10

- 11

- 12

- 13

- 14

- 15

- 01

- 02

- 03

- 04

- 05

- 06

- 07

- 09

- 08

- Research

- Standards

- Systems

- Certification

- Research

- Standards

- Systems
- (data links)

- Research

- Standards

- Systems

- Ground-Comm

- Air-Ground Comm

- Avionics

**VDL-B**

**SATCOM Ant / Rcvr**

**Integrated Demo**

**FIS-B**

**SATCOM**

**V- SATCOM**

**Link Simulation**

**FIS-B**

**FIS-B**

**FIS-B SATCOM**

**FIS-B SATCOM**

**NAS Wide Info System**

**NWIS Data**

**AOC / CDM Network**

**WARP Wx Network**

**NWIS**

**System Operational time span**

**FIS Data Compression**

**FTI**

**UAT**

**UAT**

- c:\program files\microsoft office\templates\blank presentation.pot

- May, 2000

## AATT Communication Architecture Schedule - CPC

**AATT Communication Architecture Schedule - CPC**

- 00

- 10

- 11

- 12

- 13

- 14

- 15

- 01

- 02

- 03

- 04

- 05

- 06

- 07

- 09

- 08

- Research

- Standards

- Systems

- Certification

- Research

- Standards

- Systems
- (data links)

- Research

- Standards

- Systems

- Ground-Comm

- Air-Ground Comm

- Avionics

**VDL-3**

**VHF-AM**

** ****VDL-3 MMR**

**System Operational time span**

**VHF-AM**

**FTI**

**NWIS**

**Digital Radio VHF-AM**

**Integration of Voice and  Data**

**Voice and  Data Standards**

- c:\program files\microsoft office\templates\blank presentation.pot

- May, 2000

## AATT Communication Architecture Schedule - AUTOMET

**AATT Communication Architecture Schedule - AUTOMET**

- 00

- 10

- 11

- 12

- 13

- 14

- 15

- 01

- 02

- 03

- 04

- 05

- 06

- 07

- 09

- 08

- Research

- Standards

- Systems

- Certification

- Research

- Standards

- Systems
- (data links)

- Research

- Standards

- Systems

- Ground-Comm

- Air-Ground Comm

- Avionics

**VDL-2**

**VDL-2 MMR**

**AOCDL VDL-2**

**System Operational time span**

- c:\program files\microsoft office\templates\blank presentation.pot

- May, 2000

## Communications TechnologyGaps, Solution  Alternatives and Areas for R&D Tasks 10 & 11

- May, 2000

## Communications Technology Gaps & Solution Alternatives

**Task**** 10**

**Communications Technology Gaps & Solution Alternatives**

**SATCOM**

**Comm**

**I/F**

**SATCOM**

**RCVR**

**VDL-B**

**RCVR**

**MFDS**

**Portable**

**Storage**

**Media**

**Wx**

**Sensor(s)**

**MMR**

**AAIS**

**Commercial**

**Service **

**Provider**

**FAA**

**A**

**C**

**N**

**E**

**T**

**W**

**O**

**R**

**K**

- NWIS

- AWIN

- ATC

**Passenger **

**Services**

- May, 2000

## AATT TO 24 Challenges

-  Evolving Standards, concepts, product definitions, communications technologies and services (AUTOMET, EPiRep, VDL-B, UAT, VDL -4)
-  Variations and inconsistencies in documented message traffic and aircraft projections
-  Pending link decisions that could impact recommendations (ADS-B)
-  Concept definitions (NWIS, DAG)
-  Market drivers (APAX)

- May, 2000

## AATT TO24 Accomplishments

- Provided a framework for future decision making
- Provided a coherent structure for future research and analysis
- Collected, sorted and categorized input from multiple reports
- Provided traceability from user requirements to services and communications links through the use of functional capabilities and technical concepts
- Developed a repository for continued data collection
- Determined viable links for each service from a top down and bottom up perspective
- Identified key milestones for transition to 2015 AATT CSA
- Identified gap areas and solution candidates for further research

- May, 2000

## AATT TO 24 Status

-  Individual Task Reports Delivered:
- July 99-May 00
-  AATT TO24 Team Presentations:
- May, July, September, October, 1999
- January, February, March, 2000
-  Final Presentation:
-  May 10-11, 2000
-  Final Report:
-  May 26, 2000

- May, 2000

## AATT TO24

- May, 2000