EUROCAE WG67

EDs 136, 137, 138, 139

Status and Progress
Presentation to Voice Communications Workshop
Prepared and presented by EUROCAE WG67 chairman Guy POTIRON (DSNA)

With support from WG67 members and specially from

Chris Clegg (ECTL), Hervé Pottier (CS), Armin Biegel (DFS) and Hansjoerg Seipp (DFS)

Brussels 2009 February 4th

1
 Background and scope

ƒ Components of Ground-Ground ATM voice systems are currently

using digital (TDM/PCM - Time Division Multiplexing / Pulsed Code
Modulation) or analogue technology
ƒ Convergence of voice and data into one multimedia network is
observed on the market.
ƒ Voice over IP Technology may fulfil and improve operational and
technical ATM voice communication requirements,
ƒ Pan-European Network Services (PENS) will be offering IP Voice
communications capability from 2010, for ATM purposes anytime
afterwards

2
 WG67 works
ƒ Define IP Voice ATM Systems and identify their components
(Voice Communication System / VCS, Telephone Ground-
Ground communication, Ground based Radio Station /
Recording, Supervision)

ƒ Four documents written by the different subgroups have been created to fullfill
the WG67 objectives:
– ED136 (SG1): Voice over Internet Protocol (VoIP)
Air Traffic Management (ATM) System Operational and Technical Requirements

– ED137 (SG2): Interoperability Standards for VoIP ATM Components

• Part 1: Radio
• Part 2: Telephone
• Part 3: Recording
• Part 4: Supervision

– ED138 (SG3): Network Requirements and Performances for VoIP ATM Systems
• Part 1: Network Specification
• Part 2: Network Design Guideline

– ED139 (SG4): Qualification tests for VoIP ATM Components and Systems 3
 Bodies involved

ƒ European ANSPs : ACG, AENA, Belgocontrol, DFS, DSNA, ENAV, LVNL, NATS,
ROMATSA
ƒ FAA
ƒ European ATM Suppliers: VCS and GRS
ƒ Telecom equipment suppliers: CISCO, NORTEL
ƒ Telecom Operators: SITA
ƒ RTCA and appropriate regulators and standardisation bodies (ICAO,
Eurocontrol, ITU, ETSI …)
ƒ Liaison with military will be maintained by organisations such as Eurocontrol,
Suppliers…
ƒ Results of WG 67 are anticipated to be presented to ICAO panel ANC for
consideration as international recommendations.

ƒ TORs approved on July 2004

by EUROCAE Council 4
 Vienna Agreement
Define IP Voice ATM Systems and identify their components (Voice
Communication System / VCS, Ground based Radio Station / GRS…)

5
 WG67 deliverables

ƒ ED-136 – Voice over IP ATM System Operational and Technical Requirements

to define and develop VoIP ATM System operational and technical requirements

ƒ ED-137 - Interoperability Standards for VoIP ATM Components

to define first, IP standards to fulfil operational and technical requirements,
secondly to develop IP interfaces between IP components as defined in “Vienna
Agreement”

ƒ ED-138 - Network Requirements and Performances for VoIP ATM Systems

to define and develop Network requirements and performances to fulfil QoS
required to interconnect IP components

ƒ ED-139 - Qualification tests for VoIP ATM Components and Systems

to define and develop validation requirements for VoIP ATM System and
Components
6
 ED 136, 137, 138
DEVELOPMENT, APPROVAL & PLANNING
PROCESS

WG : Final Draft 1: Internal WG67 consensus: Draft on web and sent to

December 2006-March 2008 worldwide CAC (Civil Aviation Community)

Enlarged Request for comments (comments sheet

Consultation filled) from CAC: Analysis of all comments by
May 2008-July 2008 WG67 and draft amendment as required by
SGs
WG Final Draft 2 taking in
account comments from CAC
December 2008 Final Draft 2 and summary of comment
analysis to Council

Eurocae Council Approval:

February 2009
Publication:
7
February 2009
 ED-136
Voice over IP ATM System Operational and
Technical Requirements

8
 Requirements – Two Principle Subjects

ƒ Ground Telephone
ƒ Radio

9
 Ground Telephone

Example

ƒ Instantaneous Access (IA) Calls

- established within 1 second or less for 99% of

call attempts (ICAO Doc 9804 Table 1-1)
- called party position monitoring

10
 Radio

Possibly the first attempt at definitive Requirements?

ƒ First task
produce baseline reference model of current
systems
ƒ Second task
obtain performance data (actual & standards)

11
 Baseline Model - Scope

•‘Basic’ air-ground radio

•Multi-carrier (Climax)

•Frequency Cross-Coupled

•Best-signal selection (BSS)

12
Signalling Requirement
80 ms 20 ms

100 ms

50 ms 50 ms

100 ms
13
Voice Latency Requirement
120 ms 10 ms

130 ms

105 ms 25 ms

130 ms
14
 Radio – Special Notes

ƒ Requirements are the most stringent for Hi-Density

Airspace (and may be relaxed for other applications)

ƒ Now incorporated into the ECTL/FAA doc ‘Comms

Operating Concept & Requirements (COCR) V2’

15
 ED
ED 137
137

Interoperability
Interoperability Standards
Standards
for
for VoIP
VoIP ATM
ATM Components
Components

16
 ED137 specification domains
•ED 137-1
•ED 137-2 •Radio
•Telephone

•ED137-3
•Recording

17
ED
ED 137-1
137-1
RADIO
RADIO

18
 RADIO signalling principles
ƒ Session initialization based on SIP protocol (RFC 3261)
– SIP allow to adress dynamically any radio
– Call initiation is done through SIP mechanism. Voice is managed
through RTP Extender.

ƒ Permanent monitoring of the session by using « keep alive

message » between Ground radio equipment and VCS site
ƒ Audio protocol: Based on RTP/RTCP (RFC 3550).
ƒ Radio Control signalling using additional informations added in
RTP protocol (RTP Extender field):
– PTT, A/C
– Audio quality index
– Time stamp parameters for CLIMAX use
– Reserved field for future or proprietary use
ƒ Proposed CODEC: G711 , and optional G728 or G729 19
Radio to VCS Communication principles

20
 RTP Extender principles

Ethernet/UDP Packets Ethernet/UDP Packets

~ Ethernet/IP
~
- PTT (8 possible values)
- Reserved for future Use

Ethernet/UDP Packets Ethernet/UDP Packets

~ Ethernet/IP
~
Audio

- A/C (Aircraft Call)

- Reception quality index
- CLIMAX Time stamp
21
- PTT Control
- Reserved for future or proprietary Use
 ED137-2
ED137-2
TELEPHONE
TELEPHONE

22
 TELEPHONE signalling principles

ƒ Session initialization based on SIP protocol (RFC 3261)

– SIP allow to adress dynamically any correspondent
– Call initiation is done through SIP mechanism. Voice is managed
through RTP Extender.
ƒ Audio protocol: Based on RTP/RTCP (RFC 3550).
ƒ Proposed CODEC: G711 , and optional G728 or G729
ƒ Signalling interworking between:
– Eurocontrol ATS-R2 and SIP
– ATS-R 5 and SIP
– ATS-QSIG and SIP
ƒ Additional features as Priority Call, Instantaneous Call and
Conference Call specified for existing and future VCS
communication architecture implementation.

23
 TELEPHONE Protocol Stack
Application and System Control

Interworking function

SIP Suite

Supplementary Services
(Intrusion, Instantaneous Access, Call hold, Conference…) Audio
coding
functions
RTCP
ATS-QSIG
ATS-No.5
ATS-R2

Basic SIP
+ Extension headers
+ Added Methods
+ Message Body (SDP) RTP

TCP/TLS UDP

IP

IP network lower layers 24

 TELEPHONE Interoperability
ƒ interoperability with existing VCS through IP
network

– VCS Å SIP Æ VCS

– VCS ÅSIP Æ ATS-R2
– VCS ÅSIP Æ ATS-R5 VCS

– VCS ÅSIP Æ ATS-QSIG SIP

ATS R2
Interface VCS
WAN
VCS
SIP ATS R5
SIP Interface VCS
ATS QSIG
interface VCS

25
 ED137-3
ED137-3
RECORDING
RECORDING

26
 RECORDING
ƒ Today: recording is provided by the VCS.
ƒ The ED137-3 document allow to make profit of the ETHERNET functionalities by
specifying the audio communication frame to a recorder.
ƒ Radio Recording is based on active sessions opened from clients (User Terminal,
Radio Transmitter/Receiver or specific 3rd party devices) to one recording device

ƒ User Terminals participating a Telephone G/G communication session have to

provide a single audio stream that summarizes all incoming (IN) and outgoing (OUT)
audio streams.

27
 RECORDING

ƒ Session initialization with recorder is based on SIP protocol (RFC 3261)

ƒ RTSP based on RFC 2326 is proposed to establish, terminate and
modify recording sessions
ƒ Record data include the following information:
– Voice
– Telephone call identification
– Radio channel identification
– Time
– Connecting and release time
– Priority
– Direction (Incoming-Outgoing)

28
 ED 138

Network Requirements and

Performances for VoIP ATM Systems

29
 ED138
The purpose of ED138 is to specify the network requirements and
the needs of VoIP network services for ATM applications - including
IP Adressing and Security - that are to provide the necessary high
levels of availability, integrity, performance and Quality of Service
(QoS) for VoIP in ATM applications.

ED-138 is divided into two parts:

ƒ ED-138 Part 1
– Network Specification
– Security Policy
– IP Addressing Plan

ƒ ED-138 Part 2
– Network Design Guideline
30
 Network Specification

Network Specification

ƒ 40 Requirements for the different network domains have

been defined
ƒ All Requirements can be fulfilled with COTS products –
there is no need for any new inventions
31
 IP Security
Technical Security Policy
ƒ Required security architecture and component mechanisms
ƒ Different security zones are defined with different requirements

Security
Zone 1
IP Core Provider
Responsibility of

IP Core
IP Core could
IP Core IP Core IP Core

Security
Edge Edge Edge be PENS
Zone 2

Possible Interconnections
ANSPs/Organizations
Responsibility of

Organization Organization Organization

Edge Edge Edge
Security
Zone 3 Organization Organization Organization
(WAN) (WAN) (WAN) Admin
Networ
LAN LAN LAN

32
 IP Addressing
IP Addressing Scheme
ƒ Totally based on PAX TF * results.
ƒ Usage of IPv6 is mandatory for full interworking
RIPE Responsibilty
(32 bits)

3 13 13 3 3 13 16 64

FP TLA ID Sub-TLA Res. NLA ID SLA ID Interface ID

Net. v4/ Site

F1 F2 LAN ESI
Prefix v6 Location
3 bits 7 bits 1 bit 5 bits variable bits variable bits 64 bits

Common Responsibilty ANSP Authority

(Coordination Body) (80 bits)
(16 bits)

The IPv6 addressing scheme is regularly presented to the EUROCONTROL EATM Communication Team
33
* EUROCONTROL EATM Internet Protocol for Aeronautical Exchange Task Force
 Network Design Guideline
ƒ The purpose of ED138 Part 2 is to give solutions and guidelines to fulfill the
requirements.
ƒ The document also supports to understand existing standards
ƒ More than 200 pages give a comprehensive overview about VoIP architecture,
protocols and network designs.

Simple tasks
scheduling

..
.

Complex tasks
r marking

b
Edge router: DSCP Data

• Traffic Classification
• Policing
• Shaping
Core router:
• Buffering and Scheduling based on marking at edge
• Assured Forwarding
34
 ED 139

Qualification tests for VoIP ATM

Components and Systems
to be published mid 2009

35
 ED 139 target:
how to validate components and interfaces

9 9
9 9
9

9 9
9
9
36
 A Step by Step Validation

System
level
s s
re
o g Equipment
pr
n level
t io
a
lid Network level
Va

Interface level
37
 Test validation definition

Pass

ED 136-
Requirements Environment

Test
Vali- Device
ED 137- cases
dation under
Specifications &
Guide- test
Proce-
lines
dures
ED 138-
Specifications Fail

38
 Hands on (interoperability test)
and forecast

ƒ 1st Plugtests in March 2008 (stage 1)

http://www.etsi.org/WebSite/NewsandEvents/2008_04_EUROCAE.aspx

ƒ 2nd Plugtest in March 2009 (stage 1 and

2)
http://www.etsi.org/plugtests/eurocae2/eurocae.htm

ƒ VoIP- R2 & ATS-QSIG Gateway Test in

autumn 2009
39
 EDs STATUS (February 2009)

ƒ three documents with a common reference to

« Vienna Agreement » are published by
EUROCAE for utilization within VoIP ATM
System:
– ED-136 - Voice ATM System Operational and
Technical Requirements
– ED-137 - Interoperability Standards for VoIP
ATM Components
– ED-138 - Network Requirements and
Performances for VoIP ATM Systems
ƒ ED-139 - Qualification tests for VoIP ATM
Components and Systems should be
published mid 2009 40
 Actions to go further to
Implementation phase
ƒ ED 136, 137, 138 validation through ETSI
Plugtests and SESAR Projects with support
of ED 139
ƒ Define and developp VoIP ESSI from ED 136,
137 and 138
ƒ To include ED 136, 137, 138 within ICAO
SARPS for GG Voice (including GG segment
for AG communication)
ƒ To start validation of ATM VOIP over PENS
from 2010
41
 ATM VoIP standardisation
a necessary Role for each Body
ƒ Every European Organization was and is needed:
– EUROCAE mixing closely and friendly in the same forum (WG, SGs,
Review Team) all stakeholders:
• Users expressing operational requirements and validating technical
solutions proposed by Industry
• Industry proposing technical solutions fulfilling operational requirements
and limiting over-specified requirements from users
– ETSI allowing, thanks technical (IP) skills and neutral arbitration furing
short Interoperability Plugtests, to accelerate maturation of draft
standards : very good efficiency/cost ratio
– SJU and EUROCONTROL standard validation
– EUROCONTROL preparation of global ICAO standardization, European
Single Sky Implementation (ESSI) objective definition and follow-up
– EU/EC for European legal framework : IR?, CS?, ..

Conclusion: Cooperation is needed between all these Bodies

42
 Thank you for your attention

EUROCAE
The European Organisation for Civil Aviation Equipment
102, rue Etienne Dolet 92240-Malakoff (France)

Phone: +33 1 40 92 79 30 Web site: www.eurocae.eu

43