Transcript FAA Presentation - Columbia University

VoIP SYSTEMS for FAA
Henning Schulzrinne, Supreeth Subramanya, Xiaotao Wu
Department of Computer Science
Columbia University
Date: Feb 25, 2008
1 / 14
DISCUSSION FLOW
Part 1 – The Bigger Picture

What problem is the system trying to solve?

Why is the problem important?
Part 2 – Design of VoIP System

How is the system designed?
Part 3 – Conclusion

How well has the problem been solved?

Where do we go from here?
2 / 14
THE BIGGER PICTURE (1/3)
Federal Aviation Administration (FAA)

Agency of the U.S. DoT with authority to regulate and oversee all aspects of US civil aviation
FAA Academy

The education and training division of FAA

We’re working with a group responsible for training the Air Traffic Controllers (ATC)

ATC training levels – low fidelity, medium fidelity and high fidelity
Photos - http://www.cba.uri.edu/classrooms/pictures/computerlab.jpg & http://www.lockheedmartin.com/data/assets/10307.jpg
3 / 14
THE BIGGER PICTURE (2/3)
FAA Academy Communication System
Three parallel networks in every classroom and lab

Data Network (Fast or Gigabit Ethernet)

Voice Network (Analog, hardwired point-to-point connections)

Video Network (Graphical simulations)
Disadvantages

Difficult to add new training scenarios

Uses obsolete equipments, no longer available without custom manufacture
Solution – convergence of Data and Voice networks

Digital vs. analog

Better utilization of bandwidth

Reconfigurability in connections
I’m in
4 / 14
THE BIGGER PICTURE (3/3)
What are the ATCs trained on?

Learning to use air traffic control devices & displays

Communicating and coordinating with Pilots / ATCs

Many more aspects

Learning the air traffic rules

Developing a mental picture of
air-space and air-timing
Why should we care?

We are designing the communication system

We’ll have to use air traffic control devices and displays for input/output
Photo - http://www.aeroport.public.lu/pictures/en/administration/atc/atc_003.jpg
5 / 14
DESIGN OF VoIP SYSTEM (1/6)
Voice over IP (VoIP)
Routing of voice communication over an IP network (E.g., the Internet)
INTERNET
PC–to–PC (Microsoft NetMeeting)
INTERNET
PC–to–Phone (Skype)
INTERNET
Phone–to–Phone (International Calls)
6 / 14
DESIGN OF VoIP SYSTEM (2/6)
FAA Academy classroom

Consists of up to 26 configurable student positions (ATC, Pilot) and 1 instructor

Students and instructor use computer and push-to-talk (PTT) device

Instructor loads a flight scenario and teaches/tests the students
Single
Dual Sector
Sector
Scenario
7 / 14
DESIGN OF VoIP SYSTEM (3/6)
Communication Scenarios
1.
Radio Communication

2.
Point-to-point Communication

3.
Classroom supervisor may monitor students (i.e. listen to what they hear/talk)
Automatic Notification

5.
ATC communicates with neighboring ATCs during pilot handoff
Active Monitoring

4.
Broadcast mechanism for the ATC and all of the pilots in his sector
Real-time tracking of particular events
Recording

Ability to record a communication sessions with VCR-like controls (record, play, pause etc)
8 / 14
DESIGN OF VoIP SYSTEM (4/6)
User Interfaces and I/O Devices


Five rich graphical interfaces

Students – Pilots, ATCs

Instructors – Master Instructor, Position Instructors
Five I/O devices

Push -To -Talk (PTT)

Touch-screens

Foot-pedals

Speakers

Keyboard & mouse
ATC Control Screen
Foot Pedal
Push-To-Talk
9 / 14
DESIGN OF VoIP SYSTEM (5/6)
ATC
Position
Instructor
Master
Instructor
Pilot
IP Network
SIP proxy
server
RTSP
server
File
server
Presence
server
MAP
UA
Configuration
Database
SIP-CGI
Unified VoIP Server
The VoIP System Architecture
10 / 14
DESIGN OF VoIP SYSTEM (6/6)
Novel System Development Methodology

Design Philosophy – software prototyping




Allows rapid development, iterative requirements adaptation
Hardware – software integration

Wrap every piece of hardware and talk to the wrapper

Self-correcting design to recover from component failures
Standards-based solution

Built using the Internet standards (SIP, RTP, RTSP)

Can be integrated with PSTN telephones or any other VoIP system
Extensibility

Ability to integrate newer hardware and GUI

Ability to add / modify / configure communications
11 / 14
CONCLUSION (1/3)
The good


Columbia’s Thought-to-finish approach

Handled everything from design to development to deployment

5 onsite visits to FAA, Oklahoma + 2 VoIP training sessions
Success story

FAA VoIP deployed in 5 classrooms (2 more expected by year end)
The bad and the ugly (a.k.a. lessons learnt)

Prototype system vs. production system

Deployment environment, where users aren’t CS graduates

Remote debugging is a challenge (even for trivial issues)

Interference due to malfunctioning of associated systems
12 / 14
CONCLUSION (2/3)
The Road Ahead…



Know our system strengths

Standards-based voice communications system on data networks (e.g. the Internet)

Extensible, configurable design framework (to adapt to newer requirements)
Explore possibilities

Plethora of FAA classrooms that run 50-years old hardwired communication system

Corporate and other federal organizations that use old communication system
Our shortcomings

Limited resources (developer time, travel constraints)

Not a full-fledged product (a.k.a very limited support)
13 / 14
CONCLUSION (3/3)
Thank you
for your time and support
14 / 14