EAVOIP - Technical Submission Book-CS-POH-Vers03.doc working groups library/ACP-WG-N … · Web viewIn extreme case when no majority can be reached, the Technical Coordinator will

ACP SWG N1 – 10IP1007

May 2005

Version 03

4-16, avenue du Général Leclerc – 92260 Fontenay-aux-Roses (France)Tél. : 33 1 41 87 83 00 - Fax : 33 1 41 87 83 35

Siège social : 1 avenue Newton – 92142 Clamart Cedex (France)

WG67-2 Interoperability Subgroup CharterWG67 - EAVoIP Technical documentWG67-2 Interoperability Subgroup CharterWG67 - EAVoIP Technical document

EDITIONS - APPROVALS

SUCCESSIVE CHANGES

Index Date Issued dy DescriptionErreur !Nom depropriét

é dedocume

ntinconnu

. A

April 2005 CS - ISC Initial document

02A May 2005 CS-ISC Reconditionned file03 May 2005 CS-ISC Work package updated

APPROVALS

Name Position Company VisaWritten by H. Pottier System Engineer CS

Checked by CSApproved by CS

EAVoIPTechnical document

Ver 03May 2005

This document is the property of CS. It ca not be duplicated, disclosed to anybody without written authorization

Contents

1. INTRODUCTION.....................................................................................................................2

1.1. WG67 Overview.........................................................................................................................21.1.1. Background and Scope.........................................................................................................21.1.2. Bodies involved.......................................................................................................................21.1.3. WG67 works and possible applications.............................................................................3

1.2. European ATM VoIP presentation........................................................................................41.2.1. Motives.....................................................................................................................................41.2.2. Objectives................................................................................................................................4

2. THE INITIAL REFERENCE DOCUMENT...............................................................................5

2.1. Vienna Agreement....................................................................................................................5

2.2. Organisation and output documents related to Vienna Agreement...........................6

3. THE EAVOIP VCS PLATFORM PROPOSAL........................................................................7

3.1. The project organisation........................................................................................................7

3.2. VCS platform phase 1..............................................................................................................73.2.1. Radio........................................................................................................................................73.2.2. Telephone................................................................................................................................9

3.3. VCS platform phase 2............................................................................................................103.3.1. Radio......................................................................................................................................103.3.2. Telephone..............................................................................................................................12

3.4. VCS platform phase 3............................................................................................................143.4.1. Radio......................................................................................................................................143.4.2. Telephone..............................................................................................................................15

3.5. VCS platform phase 4............................................................................................................16

4. WORKPACKAGE (WP)........................................................................................................19

4.1. Phase organization................................................................................................................19

4.2. Working Package Organization..........................................................................................20

4.3. Project organisation..............................................................................................................21

4.4. Project logics...........................................................................................................................23

5. Estimated schedule...............................................................................................................24


Ver 03May 2005


Chapter Error! Style not defined.

2

1. Introduction

1.1.WG67 Overview

1.1.1. Background and ScopeComponents of Ground- Ground ATM voice systems are currently using digital (TDM/PCM - Time Division Multiplexing / Pulsed Code Modulation) or analogue technology, otherwise some Voice Air Traffic management (ATM) simulation systems already use Voice-over-Internet Protocol (VoIP) Technology. Convergence of voice and data into one multimedia network is observed on the market. As a consequence it can be said that the future ATM communication network will evolve into a common infrastructure for voice and data services. As a result of the above described technological trends, it can now be foreseen that the capability of Voice over IP Technology may fulfil and improve operational and technical ATM communication requirements, including voice / data convergence, specific Quality of Services (QoS), security and safety requirements, at a justifiable cost when compared with current digital (TDM/PCM) and analogue technologies.Eurocontrol EATM Ground-Ground Communications Strategy is foreseeing to integrate ATM IP Voice communications by 2010 in the on going ATM IP Data Network to build the Pan-European Network Services (PENS) for Data and Voice.Similar initiatives are known to be underway internationally.The decision to implement a new digital Voice Ground-Air link (i.e. controller-pilot radio link) to complement the current Amplitude Modulation Very High Frequency (AM-VHF) transmission is under discussion.

For these reasons, EUROCAE members decided to launch an ad-hoc WG: WG67, to provide technical and operational requirements for ATM VoIP Systems.

The WG67 work program is now defined. Four documents should be provided mid 2006:A first one defining operational and technical ATM VoIP VCS requirements;A second one defining components, belonging to ATM VoIP Systems, interoperability

requirements A third one defining Network requirements to interconnect ATM VoIP components ;A fourth one defining validation tests guide to prove ATM VoIP systems compliance to

previous documents.

1.1.2. Bodies involvedTo achieve these tasks, WG-67 will involve ANSPs, ATM Suppliers, Telecom Operators, 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.


Ver 03May 2005


Chapter Error! Style not defined. > Error! Style not defined. 3

1.1.3. WG67 works and possible applicationsEUROCAE WG-67 is created with the following tasks:

1.1.3.1. Analyse the situation regarding:

operational and technical Air-Ground (A/G) and Ground-Ground (G/G) ATM Voice system requirements

IP Voice protocols and signaling standardsIP networks capability for Voice services Security, QoS, Convergence (infrastructure, protocol, applications)

Existing IP Voice ATM systems and their service interfaces,

1.1.3.2. For ground-ground ATM communications WG 67 shall:

Define IP Voice ATM Systems and identify their components (Voice Communication System / VCS, Ground based Radio Station / GRS…) for these components suppliers are free to define internal technical solution

Determine possible additional operational and technical ATM requirements for new IP Voice ATM systems, also taking into consideration A/G communications.

Accordingly, make recommendations to upgrade current standardisation documents.Develop a Technical Specification for an IP Voice ATM System. This document should

be delivered within 2 years and will include:Minimum performance and safety / security requirements for the system and,

if appropriate, for componentsInteroperability requirements between IP components of the IP Voice ATM

systems Minimum performance requirements of an IP Network aimed to support Voice

in ATM.Guidelines for qualification tests of IP Voice ATM systems and IP Voice ATM

components;

1.1.3.3. For ground-ground segment of Air-Ground communications:

WG-67 shall be tasked with same tasks as 1.1.3.2) for the Ground segment of Air-Ground communications

1.1.3.4. For Air link communications:

WG 67 will monitor ATM Air link activities in order to stay in line with the right official AG evolution and to be able to adapt its work on eventual VoIP Air link field.


Ver 03May 2005



1.2. European ATM VoIP presentation

1.2.1. MotivesIf, mid 2006, WG67 EUROCAE documents will define ATM VoIP components requirements, the true compliance to these “standards” will have to be demonstrate by real trials.

So EAVoIP project aims from 2007 to 2009 at demonstrating by many European companies providing ATM VoIP components their interoperability on a specific telecommunications network.

Such a project will ensure:for European industry to pull ahead of on ATM VoIP Systemsto make European Single Sky easier through VCS interoperability

1.2.2. ObjectivesThe main EAVoIP objectives are within 30 months :

to provide an ATM VoIP System prototype compliant with EUROCAE WG67 requirements

to interconnect by a specific network interconnecting ATM VoIP components belonging to the previous prototype System

to verify and update WG67 EUROCAE documents becoming European Standards.


Ver 03May 2005



2. The initial reference document

2.1. Vienna Agreement

Vienna agreement define the limit of the specifications which have to be provided by WG67. This agreement will mainly take in account the interface between the different equipments as : VCS, Transceivers, Recorders and the network. The objective of this document is to limit the definition to interface and not to interact in the different manufacturer’s products.

The Vienna agreement may be resumed by the following figure on which are described the different borders between equipments and network.


Ver 03May 2005



2.2. Organisation and output documents related to Vienna Agreement

EUROCAE WG67 tasked subgroups to compile operational, technical, safety and Quality of Service (QoS) requirements for ATC telephone and radio voice services (SG1), to study interoperability demands when connecting equipment of several manufacturers via a wide area network (WAN) and also identifying necessary IP-protocol enhancements to cover the ATC requirements (SG2), to compile networking requirements to cover the performance, QoS and safety requirements (SG3), to define test and process measurement to check the performance of the different interfaces (SG4)

Linked to the 4 subgroups,4 main documents will be produced:Sub Group

identificationTask responsibility Output document

referenceWG67-1 Requirement Sub Group to define

VoIP ATM System operational and technical requirements

E67_Req_WG67-1_Vxx

WG67-2 Interoperability Sub Group) to propose first, IP standards to fulfill operational and technical requirements, secondly IP interfaces between IP components as defined in “Vienna Agreement”:

E67_Interop_WG67-2_Vxx

WG67-3 WAN Sub Group to write WAN requirements and performances to fulfill QoS required to interconnect IP components

E67_WAN_WG67-3_Vxx

WG67-4 Test and measurement Sub Group to propose method and process to qualify IP interfaces

E67_WAN_WG67-4_Vxx

All the produced documents will be the reference for implementation of an IP architecture able to interconnect the different VCS components .


Ver 03May 2005



3. The EAVoIP VCS platform proposal

3.1. The project organisationThe proposed VCS platform using an IP interface is the conclusion of the WG67 project. To reach this target, several phases will be necessary to have a step by step platform implementation allowing progressive tests and controls of the solution.

4 phases are planned in this project:Phase 1: Implementation and validation tests tools between IP interfaces and existing telephone and radio interfaces Phase 2:: Adaptation and transmission of a Radio voice and signalling to existing analog transceivers through IP network. Adaptation of Telephone signalling to Eurocontrol telephone ATSQSIG signalling through an IP network. Phase 3: Connection of a Radio VCS through an IP network to a real Transceiver

Connection of a Telephone VCS to another VCS through an IP networkPhase 4: Implementation of 3 VCS and 3 transceivers sites and interconnection using an IP WAN

3.2. VCS platform phase 1This phase consist of the development and implementation of testing tools allowing the validation of Radio and Telephone Interfaces using IP protocols

3.2.1. RadioObject of the testing tool:Control and validate the protocol and the performance of a Radio manufacturer interface or gateway on IP network.


Ver 03May 2005



INPUTS OUTPUTSE67_Interop_WG67-1_Vxx Radio partE67_Interop_WG67-2_Vxx Radio partE67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx Radio part

Hardware : IP test equipment with audio external interfacesSoftware: Simulation tool for radio activity

Audio transmit and receive control

Sniffer to identify the input and output messages on IP network

Performance measurment Management messages

definition and test

The output of this phase is to provide an IP Test Tool for Radio interface validation


Ver 03May 2005



3.2.2. TelephoneObject: IP testing toolControl and validate the protocol adaptation based on EUROCONTROL existing Telephone Signalling using IP interface or Gateway connected to an ATS-QSIG Test equipment

INPUTS OUTPUTSE67_Interop_WG67-1_Vxx Telephone partE67_Interop_WG67-2_Vxx Telephone partE67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx Telephone part

G703 Codirectional ATS-QSIG Tester

Hardware: IP interface Gateway with G703 codirectional digital interface

Software: Simulation tool for telephone activity

Telephone ATS-QSIG signalling emulation

Audio G728 transmit and receive control

Sniffer to identify the input and output messages on IP network

Performance measurment Management messages

definition and test

The output of this phase is to provide an IP Test Tool for Telephone interface validation


Ver 03May 2005



3.3. VCS platform phase 2This phase consist of the development and implementation of,

a radio gateway allowing the connection from a VCS or an IP VCS to a real transceiver through an IP networka telephone gateway allowing the connection from a VCS or an IP VCS to an ATS QSIG interface through an IP network

3.3.1. Radio Object of the Gateway interface:Control and validate the protocol , the performance and the real interface between a VCS and a Radio Transceiver.

- By using existing interface and remote control


Ver 03May 2005



By connecting an IP VCS to the Radio gateway interface through the IP WAN

INPUTS OUTPUTSE67_Interop_WG67-1_Vxx Radio partE67_Interop_WG67-2_Vxx Radio partE67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx Radio partAnalog radio interfaceTransceiver with analog interfaceRemote control unit using analog 4 wires inband signallingRadio VCS

Hardware Transparent Gateway with analog interface + Control signals and IP interface

Radio VCS IP adaptationSoftware: RTP protocol with CODEC

qualification Signaling control protocol Performance validation Management definition


Ver 03May 2005



3.3.2. TelephoneObject of the Gateway interface:Control and validate the protocol , the performance and the real interface with an ATS-QSIG access connected through a WAN IP network

Control and validate the protocol , the performance and the real interface with an IP VCS connected through a WAN IP network to an ATS QSIG interface


Ver 03May 2005



INPUTS OUTPUTSE67_Interop_WG67-1_Vxx Telephone partE67_Interop_WG67-2_Vxx Telephone partE67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx Telephone partVCS systemATS-QSIG equipment

Hardware Transparent Gateway with ATS- QSIG interface + Control signals and IP interface

Telephone VCS IP adaptationSoftware: RTP protocol with CODEC

qualification ATS QSIG Signaling control

protocol Performance validation Management definition


Ver 03May 2005



3.4. VCS platform phase 3This phase consist of the development and implementation of,

the connection from a VCS or an IP VCS to a real transceiver using an IP interface through a WAN networkthe connection between 2 x IP VCS through a WAN network

3.4.1. RadioObject of the Radio IP interface:To control and validate the protocol , the performances and the real interface between an IP VCS and Radio Transceivers using integrated equipments.. The test will have to qualify the radio functionnalities as CLIMAX, Coupling, Best Signal Selection

INPUTS OUTPUTSE67_Interop_WG67-1_Vxx Radio partE67_Interop_WG67-2_Vxx Radio partE67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx Radio partAnalog radio interfaceTransceiver with analog interfaceTransceivers with IP interfaceRadio IP VCSIP Radio GatewayRadio Test tools

Hardware IP Transceivers Radio VCS IP adaptation

Software: RTP protocol with CODEC qualification

Signaling control protocol Performance validation Radio Functionnamlities

(Climax, BSS, Coupling..) Radio Management control


Ver 03May 2005



3.4.2. TelephoneObject of the Telephone IP interface:To control and validate the protocol , the performances and the real interface between two IP VCS using integrated equipments.. The test will have to qualify the telephone functionnalities as EUROCONTROL functionnalities as: Called identification, Caller identification, Priority, interfunctionning with transit using R2 Eurocontrol and ATS QSIG

INPUTS OUTPUTSE67_Interop_WG67-1_Vxx Telephone partE67_Interop_WG67-2_Vxx Telephone partE67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx Telephone partIP VCS telephone systemsATS-QSIG interface adapterR2 Terminal or testerATS QSIG tester

Hardware Transparent Gateway with ATS-QSIG interface + Control signals

and IP interface 2 xTelephone VCS IP system

Software:RTP protocol with CODEC qualification ATS QSIG Signaling control protocol Telephone functionnalities validation: Call identification, routing, priority, transit, interfunctionnality with R2 Performance validation Management definition


Ver 03May 2005



3.5. VCS platform phase 4The objective of the phase 4 is to define a complete test system and to validate all the functionnalities necessary for ATC communication control. The phase 4 platform must be able to validate the following features:WAN: Complete Wan definition, Routing, Security, Availibility, Management, QOSVCS Telephone communication: using normal communication, transit , rerouting, priority, interconnection to existing system based on in use protocol as ATS QSIG or MFC R2VCS Radio communication with all existing functionnalities as: Monitoring, Trafic, Coupling, CLIMAX, BSS, Main/Backup, Radio managementTelephone and Radio Recording: using the IP network

Based on the proposed architecture, it will be possible to define any function used in ATC. The different VCS and TX/RX equipment may be located in different areas connected through the WAN.


Ver 03May 2005



The main features tested will be:TELEPHONE:

VCS IP interfaceATSQSIG-IP interfaceBasic CallPriority callPreemptionTransitReroutingTrunkingIntersignalling R2 ATSQSIGIntersignalling IP ATSQSIGAudio performanceQOS

RADIOVCS IP interfaceTransceiver IP interfaceTransceiver signalling and Audio to IP interfaceRadio MonitoringRadio TraficRadio CouplingCLIMAXBSSMain Stand ByAudio PerformanceTransceiver managementQOS

WANGeneral architectureManagement message definitionQOSServices

RECORDERRecorder to IP interfaceAudio protocol definitionSignalling definitionManagement


Ver 03May 2005



INPUTS OUTPUTSE67_Interop_WG67-1_Vxx E67_Interop_WG67-2_Vxx E67_WAN_WG67-3_VxxE67_TEST_WG67-4_Vxx IP VCS telephone systemsATS-QSIG interface adapterRadio interface adapterR2 Terminal or testerATS QSIG testerIP TransceiverAnalog transceiverOpen Network supervisionRadio IP test toolTelephone IP Test tool

Hardware Complete test Platform

Software: Complete VCS application ATS QSIG Signaling control

protocol Telephone functionnalities

validation: Radio functionnalities validation Recorder functionnalities validation Global Perrformance validation Network Management validation


Ver 03May 2005



4. Workpackage (WP)4.1. Phase organizationThe different phases of the program may be divided in elementary tasks. Each task may be done by one or several manufacturers or companies. The goal of this definition is to guarantee interoperability between different interfaces by developping the adaptation using different manufacturers.

For each task, the “Type” column will give indication that the work to do is applicable to Telephone, Radio, Recorder or Network .

Task Phase 1 Phase 2 Phase 3 Phase 4 Object of the WP TypeT1 X To provide and qualify Radio interface to IP network Radio

T2 X To provide and qualify Radio test tool connected to IP network Radio

T3 X To provide and qualify an ATS-QSIG to IP interface adapter Telephone

T4 X To provide and qualify a TelephoneTest tool connected to IP network Telephone

T5 X To define and to provide a basic network for connection to the different Radio and telephone interfaces Network

T6 X To provide an existing transceiver and a second Radio interface to IP network for radio test application Radio

T7 X

To provide and test a complete analog remote control system to validate the audio transmission through the IP network Radio

T8 X To validate a VCS connected to the Radio interface through the IP network. Radio

T9 X

To provide a second ATSQSIG to IP interface and to test the capability to transmit through the IP network an ATSQSIG signaling Telephone

T10 X To validate a Telephone VCS connected to the ATSQSIG inerface through the IP network Telephone

T11 X

To define and test and validate the messages from the VCS and Radio or telephone interface on the IP network using a supervision tool Network

T12 X To provide a complete integrated full IP ground interface transceiver Radio

T13 X To test a complete Radio VCS connected through the netwok using different IP transceiver equipments Radio

T14 X

To provide a second VCS with IP and MFC R2 interfaces connected to the network to IP ATS QSIG interface adapter and IP VCS Telephone

T15 X

To define a supervision system able to control Radio and Telephone IP interface of each equipment connected on the network Network

T16 XTo define and provide a complete Network able to connect the different area used for the test platform Network

T17 X To provide several IP transceivers Radio

T18 XTo define and provide a recorder connected on the nIP network Recorder

T19 XTo provide a complete open supervision system used to manage the network Network

T20 X To provide complete test on the different VCSTelephone/

Radio


Ver 03May 2005



4.2. Working Package OrganizationThe work packages (WP) will group different tasks sorted by type or based on project management organisation. . The following diagram shows the different WP including the project organisation.

The Tasks allocation for each WP will have to be done in accordance to the requirement and consensus of each EAVoIP participant

For example: the WP2 regarding the test bench will allocate the following tasks:T1,T2,T3,T4,T5


Ver 03May 2005



4.3. Project organisationAs shown in the following figure, the EAVoIP project Steering Committee is composed of the following principal members: the Technical Coordinator, the work package leaders and the Project Manager (PM). The Technical Coordinator will act as an intermediary between the European Commission and the management team while also being responsible for financial issues, to keep accounts of all aspects of the project and to ensure that the project follows the pre-signed contractual obligations.

Specifically the Technical Coordinator, assisted by the Project Manager, will perform the following tasks:

Supervision of the progress of the projects (tasks, milestones, budget) including regular visits of individual partner facilities;

Formulation of detailed project plan on a sub task/partner level including detailed budgeting and scheduling;

Set-up and maintenance of project documentation archive and project procedures manual;

Preparation, organisation, administration, minutes and follow up of scientific meetings;

Compilation of management summaries on the basis of status sheets, progress reports including mid-term assessment, task reports, annual reports and final report;

Collection and monitoring of individual partner administrative documents and


Ver 03May 2005



statements of expenditures, and transmission to the Commission, tracking of payments, which are to be made to each partner;

Coordination of communication between partners and co-ordination between the consortium and other parties.

The work package leaders will ensure that the objectives of the project are performed within the strategy of the work plans. This will entail accordance with the agreed milestones, production of deliverables and ensuring that the participant fulfil their commitments to work packages.

The Steering Committee will be in constant communication and will also meet twice a year. The decision-making process will be the result of either a collegial discussion, or a vote (one vote per member / two thirds majority). In extreme case when no majority can be reached, the Technical Coordinator will have the last word.

In close collaboration with the Technical Coordinator and in accordance with Commission requirements the Project Manager will take administrative actions, including periodic reports, audit documents, financial control, and preparation of work requests. Additionally the PM will prepare logistical, legal and administrative documents and communication of work tasks to be performed to the pertinent parties and aid in the co-ordination of the following activities.


Ver 03May 2005



4.4. Project logics

As shown in the following figure, the project logic will follow the 4 phases defined previously. Associated to the 4 phases, the management will have to verify that work are performed and results will be published ..


Ver 03May 2005



5. Estimated scheduleThe following GANT planning represent the estimated schedule for the different tasks, previously described, to be done.


Ver 03May 2005


Documents

EAVOIP - Technical Submission Book-CS-POH-Vers03.doc working groups library/ACP-WG-N … · Web viewIn extreme case when no majority can be reached, the Technical Coordinator will