Professional Documents
Culture Documents
Ed 136
Ed 136
ED-136
February 2009
ED-136
February 2009
© EUROCAE, 2009
i
FOREWORD
1 The document ED-136 “Voice over Internet Protocol (VoIP) Air Traffic
Management (ATM) System Operational and Technical Requirements” was
prepared by EUROCAE Working Group 67 and was accepted by the Council of
EUROCAE on 2 February 2009.
2 EUROCAE is an international non-profit making organisation. Membership is
open to manufacturers and users in Europe of equipment for aeronautics, trade
associations, national civil aviation administrations and non-European
organisations. Its work programme is principally directed to the preparation of
performance specifications and guidance documents for civil aviation
equipment, for adoption and use at European and world-wide levels.
3 The findings of EUROCAE are resolved after discussion among its members
and, where appropriate, in collaboration with RTCA Inc, Washington D.C. USA
and/or the Society of Automotive Engineers (SAE), Warrendale, PA, USA
through their appropriate committee.
4 The document represents “the minimum specification required for
Manufacturers and Users to assure Interoperability between VoIP ATM
Components”.
5 EUROCAE performance specifications are recommendations only. EUROCAE
is not an official body of the European governments; its recommendations are
valid statements of official policy only when adopted by a particular government
or conference of governments.
6 Copies of this document may be obtained from:
EUROCAE
102 rue Etienne Dolet
92240 MALAKOFF
France
Tel: 33 1 40 92 79 30
Fax: 33 1 46 55 62 65
Email: eurocae@eurocae.net
Web Site: www.eurocae.net
© EUROCAE, 2009
ii
TABLE OF CONTENTS
CHAPTER 1 INTRODUCTION .............................................................................................. 1
1.1 BACKGROUND ................................................................................................ 1
1.2 ED-136 PRESENTATION................................................................................. 3
1.3 TERMINOLOGY FOR REQUIREMENTS, RECOMMENDATIONS AND OPTIONS 3
CHAPTER 2 RADIO BASELINE REFERENCE CHAPTER .................................................. 4
2.1 DEFINITIONS ................................................................................................... 4
2.2 INTRODUCTION .............................................................................................. 7
2.2.1 Baseline model configuration diagrams ............................................ 8
2.3 RADIO SYSTEM PERFORMANCE REQUIREMENTS ................................... 15
2.4 RADIO SYSTEM FUNCTIONAL REQUIREMENTS ........................................ 17
2.5 DETECTION OF SIMULTANEOUS RADIO TRANSMISSIONS ...................... 27
2.5.1 Description ........................................................................................ 27
2.5.2 Principal Requirement – Safety Warning .......................................... 27
2.5.3 Case 1 – Two Frequencies F1 and F2 in Cross-Coupled Mode....... 27
2.5.4 Case 2 – One Ground Receiver........................................................ 28
2.5.5 Case 3 – Two Ground Receivers ...................................................... 29
2.5.6 Case 4– Simultaneous Pilot-Controller transmission........................ 31
CHAPTER 3 TELEPHONE BASELINE REFERENCE CHAPTER........................................ 32
3.1 DEFINITIONS ................................................................................................... 32
3.2 GROUND-GROUND VOICE COMMUNICATION SERVICES......................... 33
3.2.1 Communications within a FIR between ATSUs ................................ 33
3.2.2 Communications within a FIR between ATSUs and other Units....... 33
3.2.3 Communications between Flight Information Regions (FIRs)........... 34
3.2.4 Communications out of the ATS community ..................................... 34
3.3 PRIMARY USER GROUND TELEPHONE FACILITIES .................................. 34
3.3.1 Supervisory tones.............................................................................. 34
3.3.2 Direct Access (DA) ............................................................................ 35
3.3.3 Instantaneous Access (IA) ................................................................ 36
3.3.4 Indirect Access (IDA)......................................................................... 38
3.3.5 Call Priority ........................................................................................ 38
3.3.6 Instantaneous Access (IA) and Priority Call comparison .................. 39
3.3.7 Typical call handling behaviour of new call events to CWP in pre-defined
states ........................................................................................................... 41
3.3.8 Call Intrusion ..................................................................................... 42
3.3.9 Call Interruption ................................................................................. 43
3.3.10 Simultaneous Calls............................................................................ 43
3.3.11 Call Queuing Facility ......................................................................... 44
3.4 SUPPLEMENTARY TELEPHONE SERVICES................................................ 45
3.4.1 Inter-ATSU Supplementary Telephone Services .............................. 45
3.4.2 ATSU Internal Supplementary Telephone Services ......................... 45
3.5 ADDRESSING AND NUMBERING SCHEMES ............................................... 47
3.5.1 Numbering Schemes......................................................................... 47
3.5.2 Number or Address Assignment ....................................................... 47
3.5.3 Global Numbering Schemes ............................................................. 47
3.6 EXTERNAL CONNECTIONS AND PROTOCOLS........................................... 47
3.6.1 Signalling in an IP AGVN .................................................................. 47
3.6.2 External Connections and associated Protocols............................... 47
3.7 INTERWORKING WITH ATS LEGACY SYSTEMS ......................................... 49
3.8 CONNECTIVTY WITH PRIVATE AND PUBLIC TELEPHONE NETWORKS.. 50
3.9 INCOMING CALL BARRING AND RESTRICTION.......................................... 50
3.10 HANDLING OF OUTGOING CALLS / ROUTING CRITERIA .......................... 50
© EUROCAE, 2009
iii
© EUROCAE, 2009
iv
© EUROCAE, 2009
v
FIGURE INDEX
FIGURE 1: VIENNA AGREEMENT ......................................................................................................................... 2
FIGURE 2: CALL ESTABLISHMENT CONTROLLER –PILOT (GROUND – AIR) .................................................. 8
FIGURE 3: CALL ESTABLISHMENT PILOT –CONTROLLER (AIR – GROUND) .................................................. 9
FIGURE 4: PTT- A/C CALL INDICATION (ROUND-TRIP) DELAY ......................................................................... 9
FIGURE 5: CALL ESTABLISHMENT PILOT – PILOT (AIR-AIR) .......................................................................... 10
FIGURE 6: CALL ESTABLISHMENT CONTROLLER – PILOT(S) (GROUND–AIR WITH FREQUENCY CROSS
COUPLED) ............................................................................................................................................................ 11
FIGURE 7: CALL ESTABLISHMENT PILOT – CONTROLLER – PILOT (AIR–GROUND WITH FREQUENCY
CROSS COUPLED) .............................................................................................................................................. 12
FIGURE 8: CALL ESTABLISHMENT CONTROLLER–PILOT (GROUND – AIR WITH MULTI-CARRIER/CLIMAX)
.............................................................................................................................................................................. 13
FIGURE 9: CALL ESTABLISHMENT PILOT – CONTROLLER (AIR–GROUND WITH BEST SIGNAL
SELECTION) ......................................................................................................................................................... 14
FIGURE 10: SIGNALLING DELAY REQUIREMENT ............................................................................................ 15
FIGURE 11: VOICE DELAY REQUIREMENT (GROUND COMPONENTS)......................................................... 16
FIGURE 12: EXAMPLE OF ECHO INDUCTION CAUSED BY DELAYED RECEPTION OF SAME MESSAGE ON
DIFFERENT FREQUENCIES F1, F2 AND F3....................................................................................................... 19
FIGURE 13: SIMULTANEOUS TRANSMISSIONS WITH TWO FREQUENCIES IN CROSS-COUPLED MODE.27
FIGURE 14: ONE GROUND RECEIVER DETECTS BOTH SIGNALS OF A SIMULTANEOUS TRANSMISSION
.............................................................................................................................................................................. 28
FIGURE 15: TWO GROUND RECEIVERS EACH DETECT DIFFERENT SIGNALS OF A SIMULTANEOUS
TRANSMISSION ................................................................................................................................................... 29
FIGURE 16: DETECTION OF ADDITIONAL AIRCRAFT CALLS THROUGH TIME DIFFERENCE DIAGNOSIS
BETWEEN 2 SIGNALS FROM 2 RADIO STATIONS............................................................................................ 30
FIGURE 17: TWO GROUND RECEIVERS EACH DETECT BOTH SIGNALS OF A SIMULTANEOUS
TRANSMISSION ................................................................................................................................................... 30
FIGURE 18: SIMULTANEOUS TRANSMISSION BY PILOT AND CONTROLLER TRANSMISSION ON THE
SAME FREQUENCY............................................................................................................................................. 31
FIGURE 19: OPERATIONS, TECHNICAL ARCHITECTURE AND AVAILABILITY COMPLIANCE
METHODOLOGY .................................................................................................................................................. 56
FIGURE 20: ITU-T G.131 – TALKER ECHO TOLERANCE CURVES .................................................................. 60
FIGURE 21: USER AND SERVICE MANAGEMENT ............................................................................................ 64
FIGURE 22: ILLUSTRATION OF RADIO AND/OR TELEPHONE SYSTEM......................................................... 65
FIGURE 23: MANAGEMENT SERVICES WHEN APPLIED TO VIENNA AGREEMENT ..................................... 66
FIGURE 24: TELEPHONE ON-LINE RECONFIGURATION EXAMPLE ............................................................... 71
TABLE INDEX
TABLE 1 – COMMON FACILITY AND SERVICE REQUIREMENTS.................................................................... 18
TABLE 2 – SUPERVISORY TONE DEFINITION .................................................................................................. 34
TABLE 3 – INSTANTANEOUS CALL-PRIORITY CALL COMPARISON .............................................................. 39
TABLE 4 – CALL HANDLING BEHAVIOUR FOR PRE-DEFINED CWP STATES ON NEW CALL EVENTS....... 41
TABLE 5 – EXAMPLES OF GENERIC IDENTITIES ............................................................................................. 44
TABLE 6 – INTERFACE AND PROTOCOL SUPPORT DOCUMENTS ................................................................ 48
TABLE 7 – CIRCUIT-SWITCHED AND PACKET-SWITCHED CALL INTERWORKING ...................................... 49
TABLE 8 – ASSOCIATION BETWEEN CALL TYPES AND THE SIP PRIORITY HEADER FIELD ...................... 52
TABLE 9 – EXAMPLE OF VOICE SERVICES PRECEDENCE SCHEME ............................................................ 53
TABLE 10 – ITU-T G.109- RELATIONSHIP BETWEEN E-MODEL (R), MOS AND SPEECH TRANSMISSION
QUALITY CATEGORY .......................................................................................................................................... 59
TABLE 11 – ILLUSTRATION OF CROSS-COUPLING MODES FUNCTIONALITY.............................................. 87
TABLE 12 – CROSS-COUPLING COMBINATIONS- FREQUENCY F1D RECEIVED FIRST .............................. 88
TABLE 13 – CROSS-COUPLING COMBINATIONS- FREQUENCY F3S RECEIVED FIRST .............................. 88
© EUROCAE, 2009
vi
REQUIREMENTS INDEX
© EUROCAE, 2009
vii
© EUROCAE, 2009
viii
RECORDING
1 [REQ RECORDING] True and faithful representation of audio signal ............................................................... 58
2 [REQ RECORDING] Provision for 2 identical autonomous voice recordings .................................................... 58
3 [REQ RECORDING] Date & Timestamp Synchronization ................................................................................. 58
4 [REQ RECORDING] Entities for voice recording and location identification...................................................... 58
5 [REQ RECORDING] Voice recording all communications at CWP ................................................................... 58
VOICE QUALITY
1 [REQ VOICE QUALITY] Mean Opinion Score of A/G & G/G communications >4............................................ 59
2 [REQ VOICE QUALITY] Talker-echo tolerance compliant with ITU-T G.131 ................................................... 60
3 [REQ VOICE QUALITY] One-way voice delay (telephone)<150ms ................................................................. 61
4 [REQ VOICE QUALITY] One-Way voice delay (radio) <130ms ....................................................................... 61
5 [REQ VOICE QUALITY] Speech Clipping segments ≥64ms avoided,<64ms within 0.2% of active speech..... 61
6 [REQ VOICE QUALITY] Voice transmission characteristics............................................................................. 61
7 [REQ VOICE QUALITY] Ground-Ground voice frequency response............................................................... 61
8 [REQ VOICE QUALITY] Cross-Talk level <-60dBm0 for 1KHz test tone.......................................................... 62
9 [REQ VOICE QUALITY] Noise and Hum.......................................................................................................... 62
10 [REQ VOICE QUALITY] Total Distortion, including quantizing distortion ....................................................... 62
© EUROCAE, 2009
ix
35 [REQ SYS ENG] Speech Activity Detector with Pseudo Squelch signal generation ...................................... 73
36 [REQ SYS ENG] Automated Radio check during PTT ................................................................................... 73
37 [REQ SYS ENG] Automatic or manual channel check ................................................................................... 73
38 [REQ SYS ENG] VCS switching capabilities at Ground Radio Station........................................................... 74
39 [REQ SYS ENG] Alarm for non-selected frequencies .................................................................................... 74
40 [REQ SYS ENG] Automatic Gain Control for Tx & Rx speech levels ............................................................. 74
41 [REQ SYS ENG] Easy access to monitor VCS signalling............................................................................... 74
42 [REQ SYS ENG] Headset Operation .............................................................................................................. 74
43 [REQ SYS ENG] Date and Time reference source......................................................................................... 74
44 [REQ SYS ENG] Evolution (Modification/Upgrade) capability ........................................................................ 75
SECURITY
1 [REQ SECURITY] Radio and Telephone IP-voice packet authenticity .............................................................. 77
© EUROCAE, 2009
1
CHAPTER 1
INTRODUCTION
1.1 BACKGROUND
Ground-Ground (G-G) ATM voice systems have been based upon analogue and more
recently, digital Time Division Multiplexing / Pulsed Code Modulation (TDM/PCM)
technologies for many years.
Nowadays, however, convergence of voice and data into one multimedia network is a
popular trend with a variety of technical solutions available on the market. Following in
this direction ATM communication networks are adopting, by a process of gradual
evolution, a common infrastructure for voice and data services.
As the technology has developed IP Technology has now the true potential to fulfil
operational and technical ATM communication requirements - including those of voice
/ data convergence, Quality of Services (QoS), security and safety. There is also the
possibility that IP may deliver solutions that will, over time, bring about true savings in
investment and operating costs.
EUROCAE Working Group 67 (WG-67) undertook the mission to assess the feasibility
of using Voice over Internet Protocol (VoIP) for providing ATM voice services. The
group defined criteria, requirements and guidelines based upon the following
operational needs and constraints:
• Operational and Technical Air-Ground (A-G) and Ground-Ground (G-G) ATM
Voice system requirements
• Existing IP Voice protocols and signalling standards
• IP network capabilities for Voice services
• Security, Quality of Service (QoS), and Convergence (infrastructure, protocol,
applications)
• Existing IP Voice ATM system capabilities and service interfaces.
The following tasks were identified to fulfil the WG-67 mission:-
• Define ATM Systems and identify their components (Voice Communication
System / VCS, Ground Radio Station)
• Determine possible additional operational and technical ATM requirements for
new ATM voice systems, also taking into consideration A-G communications.
• Make recommendations to upgrade current standardisation documents.
• Develop a Technical Specification for a VoIP Voice ATM System including:
o Minimum performance and safety/security requirements for the system
and, if appropriate, for components;
o Interoperability requirements between IP components of the VoIP ATM
system;
o Minimum performance requirements of an IP Network to support ATM
Voice services;
o Guidelines for qualification tests of VoIP ATM systems and their
components.
Consequently the following four documents were delivered:
ED-136 - VoIP 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
© EUROCAE, 2009
2
The contents of all four documents are premised on the “Vienna Agreement” which
defines the different components of a VoIP ATM system and their mutual interfaces as
depicted in Figure 1.
VoIP components are interconnected through an IP network and suppliers are free to
define their internal architecture (IP/Ethernet, TDM/PCM - Time Division
Multiplexing/Pulsed Code Modulation,…). Between VoIP components, required
interfaces are defined to guarantee their functional and technical interoperability.
Therefore, VoIP ATM Systems are composed of:
• VoIP VCS Components performing Radio and / or Telephone functions,
including:
1. Controller Working Positions, assuring HMI including voice devices
(microphone and loudspeaker);
2. Possible local VCS Maintenance and Configuration stations;
3. Possible local Recording devices;
4. Possible LAN for local interconnection;
5. Possible Media Gateways to legacy systems (ATS-QSIG, ATS-R2, ATS-
No.5, PSTN, Radio analogue lines, …).
• VoIP Ground Radio Station Components performing AM VHF and UHF
Radio functions.
• VoIP Supervision System Components performing monitoring and control
functions.
• VoIP Recording Components performing recording functions.
• IP WAN Components performing interconnection services between two or
more different physical components.
© EUROCAE, 2009
3
© EUROCAE, 2009
4
CHAPTER 2
© EUROCAE, 2009
5
© EUROCAE, 2009
6
© EUROCAE, 2009
7
• Voice Delay: the one-way User-to-User voice delay between analogue system
interfaces (Example: Controller microphone to Pilot Earphone) once the call is
established.
• XC1 (Frequency coupling time): a timing parameter specifying the time taken
for a VCS (or other device) to couple one frequency to another. In practical
terms this is the time taken for an A/C Call (Squelch) signal as an input to the
VCS to be converted to a Push-To-Talk (PTT) signal as an output from the
VCS. (Refer to Figure 7).
• XC2 (Cross-coupled Push-To-Talk Inhibition Period): a timing parameter
specifying a period imposed by a VCS (or other device) during which
retransmission is inhibited after any transmission (within the cross-coupled
group) via the VCS has ended.
This inhibition is a technical solution necessary to prevent either cross-coupling
oscillation and/or blocking behaviour in cross-coupled mode.
• X-Couple (Cross-Coupling 2 or more radio frequencies): frequency cross-
coupling is a CWP selected function causing automatic retransmission of one
received signal on other pre-selected radio frequencies. With Cross-Coupling it
is possible to merge a number of physical radio frequencies into a kind of logical
frequency.
2.2 INTRODUCTION
The EUROCAE WORKING GROUP 67, SUB-GROUP 1 had the task of specifying
requirements relating to Air-Ground Radio. In order to progress this task it was found
essential to produce a Baseline Model of the current systems (how they are
configured today) underpinned by an agreed common set of terms and definitions.
The model produced covers all the known system configurations:
• ‘Basic’ air-ground radio communications
• Multi-carrier (Climax) operations
• Frequency Cross-Coupled operations
• Best-signal selection
• Combinations of these may also be modelled, for example:- Combined
Frequency Cross-Coupled & Multi-Carrier operations
The model, covering all the above configurations, is expanded by a series of figures
defined in section 2.2.1 below, in which each process (timing element) is labelled
such that all those that contribute to signalling and speech delays (latency effects) are
clearly identified. It must be noted, however, that some systems might not contain
every element or that the effective latency is either negligible or nil. Equally some
elements may be combined into a single process so that the model would have to be
adapted accordingly.
Where some timing elements are subject to defined Standards these have been
included in the model as ‘given’ parameters. For the remainder it is necessary to
include data from other sources such as technical specifications or actual
measurements. As a separate exercise EUROCAE Sub-Group 1 has obtained
measurement data from a number of European Air Navigation Service Providers
(ANSPs) such that ‘real-life’ data is available. It is this actual baseline data that Sub-
Group 1 has taken as guidance when formulating some of the Air-Ground Radio
Requirements.
Sub-Group 1 are also aware of similar activities which have taken place in relation to
the joint EUROCONTROL/FAA Study “Communications Operating Concept and
Requirements (COCR) of the Future Radio System”. Whereas Sub-Group 1 is not
concerned with Future Radio Systems it is considered highly-desirable that all the
parties concerned share a common view of current baseline system characteristics
and (of utmost importance) that the same terms and definitions are used.
© EUROCAE, 2009
8
© EUROCAE, 2009
9
© EUROCAE, 2009
10
© EUROCAE, 2009
11
© EUROCAE, 2009
12
© EUROCAE, 2009
13
© EUROCAE, 2009
14
© EUROCAE, 2009
15
The integrity of the association between signalling and speech for each individual transmitted
/ received message SHALL be preserved, totally, by the Radio System.
The Integrity of end-to-end signalling and addressing between the ground components of the
Radio System SHALL be assured in addition to the logical connection for the entire duration
of each transmission and reception.
E.g a Push-To-Talk (PTT) action, keys the intended Transmitter and nothing else.
The Transmitter Activation Delay (TAD) SHALL have a maximum value of 100mS.
Given: 20ms maximum for Transmitter Activation Time (TAT) is included within the 100ms
(refer to Figure 10 below)
© EUROCAE, 2009
16
The Aircraft Call Indication Delay (ACD) SHALL have a maximum value of 100mS.
Given #1: The A/C Indication Device activation/display time is excluded from this time but is
expected to be within the range 20 – 50 ms.
Given #2: 50ms maximum for Receiver Activation Time (RAT) is included within the 100ms.
(refer to Figure 10 above).
The voice delay for ground transmission components SHALL be a maximum of 130ms.
Given: Voice delay in the ground transmitter is 10ms and this is included in the 130ms.
(Refer to Figure 11 below)
7 [REQ RADIO PERFORMANCE] 10ms max Voice delay differential for Climax
operation
In Multi-Carrier/Climax operation the difference between the longest and the shortest voice
latencies for ground transmission components SHALL be a maximum of 10mS.
© EUROCAE, 2009
17
The voice delay for ground reception components SHALL be a maximum of 130 ms.
Given: Voice delay in the ground receiver is 10ms and this is included in the 130 ms.
(Refer to Figure 11 above)
For the speech signal transmitted from ground to air, clipping at both the start and end of
each transmitted voice message, SHALL not exceed 64 ms.
For each radio signal received at the CWP, clipping at both the start and end of each air to
ground received voice message, SHALL not exceed 64 ms.
Radio access at a CWP SHALL be activated by the operation of a key (the term ‘key’ is used
to refer to a single activation device such as a key, switch, button or icon), associated with a
particular frequency and an appropriate visual/audio indication SHALL be given to indicate
the selection made. The key enables a particular radio frequency to be in one of four basic
modes:
• Off/Deselected;
• Receive only (Rx);
• Transmit and Receive (Tx/Rx);
• Cross-coupled.
Additional modes could be used in special cases.
The normal operational situation is when only one controller transmits (PTT) on a given
frequency at any time. The following provisions apply:
a) It SHALL be possible for a mentor to override the transmission of a student by the
mentor operating his/her own PTT key specially enabled to do this. The student and
mentor usually employ a common CWP, but other configurations such as separate
CWPs are also possible.
b) Two or more (up to a maximum of seven) controllers (not necessarily co-located) may
share access to a common transmitter. By multi-party agreement, each controller
should be assigned one of three possible transmit access priority (TAP) levels:
Emergency (highest)
Priority
Normal (lowest)
In the event of simultaneous PTTs the controller with the highest overall TAP SHALL
seize the transmitter for exclusive use - even if it was already in use by another
controller.
c) In the event that two or more controllers, with equal TAPs, attempt to transmit
simultaneously on the same transmitter, the system SHALL transmit the summation of
all voice signals; this is an exceptional safety-related situation - for example in SAR
situations.
© EUROCAE, 2009
18
The system SHALL facilitate speechless communications (silent PTT and silent SQL
signalling). This entails the pilot and the Air Traffic Controller pressing their transmit button a
certain number of times using carrier wave only transmission to exchange information.
In situations where transmitters (Tx) and receivers (Rx) are remote from the main VCS
equipment, some form of Remote Control Functionality is required. This Remote Control
Functionality could be provided by separate Remote Control Equipment (RCE) or
incorporated into the IP Radio Gateway.
Depending on the Ground Radio Station architecture, transmission and reception facilities
may be located on separated sites and interconnected with different type of links (radio-link,
copper cables, optic fibre). Therefore, these various types of architecture SHALL be taken
into account in the radio gateway specification and in the medium term in the IP-compatible
transmitters (Tx) and receivers (Rx) specifications.
Table 1 below defines common requirements for two sets of facilities and services.
TABLE 1 – COMMON FACILITY AND SERVICE REQUIREMENTS
Tx / Rx SERVICES SITE MANAGEMENT INFORMATION
Voice Door contacts
Push-to-talk (PTT) Fire alarm
A/C call or Squelch Intruder alarm
Automatic Gain Control / signal
Power failure
strength
Equipment status
The IP radio gateway’s input and output SHALL be backwards compatible with any legacy
remote control systems.
Remote Control Functionality SHALL support and prioritise the essential functions of Audio,
PTT, Squelch and Automatic Gain Control / signal strength whereas other functions such as
equipment status, site management and info processing are optional and MAY be
supported.
Simultaneous reception of the same message on several different frequencies SHALL not
be distorted at the CWP.
The situation where one CWP (N°2) simultaneously receives (Rx) several frequencies that
are also in operation on a different CWP (N°1) (in Tx/Rx or cross-coupled modes) SHOULD
be considered carefully in a VoIP concept. The existing constant delays on a TDM network
may vary as a consequence of re-routing (neglecting the effects of jitter) and could render
the audio on CWP n°2 unintelligible. (Refer to Figure 12 below).
© EUROCAE, 2009
19
CWP 1 CWP 2
F1 Tx F1 Rx
F2 Tx F2 Rx
F3 Tx F3 Rx
Rx Controller voice F2
Tx Controller voice
Rx Controller voice F3
Tx Controller voice
Time line
The delay differential, as shown in Figure 12 above, SHALL NOT exceed 10ms.
A Radio Panel (or similar facility) at the CWP SHALL display the following information:
a) the current operating mode (see 1 [REQ RADIO FUNCTIONAL] Radio Access
Modes of Operation above);
b) Main or Standby radio selection;
c) an aircraft call (A/C) indication on the incoming frequency (or frequencies in case of
retransmission in cross-coupling mode).
The CWP Radio Panel SHALL display the technical state of each frequency (Out of service,
Degraded, Maintenance).
© EUROCAE, 2009
20
Within permitted operational conditions any key activation to change the current assigned
frequency mode, on a CWP, SHALL result in the change being fully effective within 300mS.
Examples:
• when a frequency is selected in Rx mode any received audio from an on-going aircraft
transmission is presented to the controller within 300ms;
• when a frequency is selected in Tx/Rx mode the frequency is usable for Tx operation
within 300ms.
NOTE 11: Current assigned frequency is one that has already being configured for
operational service at the CWP.
The CWP radio panel SHALL display any change of status of assigned frequencies within
300ms.
The controller SHALL be alerted, by means of distinctive and prominent visual and audible
alarms, in the event of the system undesirably isolating/disconnecting any facility.
Examples:
• an operational frequency;
• a CWP Radio Panel;
• a frequency in a Cross-Coupled group.
Each element of the system SHALL incorporate measures to ensure that any frequency is
not blocked (PTT, SQL, selection), undesirably, from being used by any authorized/permitted
user.
The Controller SHALL be provided with the facility to select two or more (up to a maximum
of 28) air-ground communication frequencies simultaneously. When the Push-To-Talk (PTT)
action is performed, communications SHALL be transmitted on all Tx/Rx-selected
frequencies to the aircraft.
When the Push-To-Talk (PTT) key is released, the Controller SHALL be provided with the
combined/mixed audio signals from all selected frequencies (except cross-coupled
frequencies).
© EUROCAE, 2009
21
Duplex and Simplex Cross-coupling facilities SHALL be provided (see Annex D).
NOTE 12: Frequency cross-coupling is a CWP-selected function causing automatic
retransmission of one received signal on other pre-selected radio
frequencies. With cross-coupling it is possible to merge a number of
physical radio frequencies into a kind of logical frequency.
The purpose of frequency cross-coupling is to help the Controller to work in
merged roles. This makes it easier to split and merge roles, and it improves
the Controller’s efficiency, avoiding simultaneous calls of pilots using
different frequencies.
The controller SHALL be able to select two or more (up to a maximum of 28) radio
frequencies in a cross-coupled group.
When an aircraft transmits on frequency ‘F1’ and is received on the ground, it SHALL be re-
transmitted on frequency ‘F2’. For the User on the ground at the CWP where coupling has
been enabled, when the user transmits on either frequency ‘F1’ or ‘F2’ transmissions SHALL
occur on both frequencies at the same time.
The original aircraft transmission on frequency ‘F1’ only SHALL be fed to the User at the
CWP where the cross-coupling has been enabled – not the received signal by re-
transmission on any other frequencies. The received transmission on frequency ‘F1’ is
termed the “incoming frequency”.
When an aircraft transmits on F1, retransmission SHALL occur on F2 and F3. Should an
aircraft call also occur on F2 during the retransmission, the corresponding voice signal (F2)
SHALL NOT be retransmitted so long as a voice signal on incoming frequency F1 is present.
At this time the incoming voice signal F2 SHALL always be presented to all other CWPs with
F2 selected.
As soon as there is no voice signal on F1 and after the Cross-coupled PTT Inhibition
Period “XC2” (see NOTE 13 below), cross coupling SHALL operate with F2 as the incoming
frequency.
NOTE 13: A definition of Cross-coupled PTT Inhibition Period “XC2” is given in 2.1
DEFINITIONS, its maximum value is defined in 5 [REQ RADIO
PERFROMANCE] as 250ms. XC2 is also shown in the radio parameter
timing diagram Figure 7.
Users SHALL be given clear indications of which frequencies are being employed in cross-
coupled mode.
© EUROCAE, 2009
22
In the event that a frequency is already cross-coupled on one CWP the system SHALL
prevent it being cross coupled at another CWP – regardless of its location (except if the
other CWP is on the same Sector Suite – depending on ANSP implementation). The system
SHALL also present clear information, on the CWP of the Controller being prevented from
cross coupling the frequency, that the cross-coupling procedure has been refused and thus
not executed.
When Cross-Coupling has been enabled at a CWP, the controller’s PTT SHALL take
precedence over any signals that are currently being re-transmitted (cross-coupling
retransmission is disabled for the duration of the controller’s PTT action plus the Cross-
coupled PTT Inhibition period “XC2” (see NOTE 13).
In cross-coupling mode, the display of the aircraft call /squelch at the CWP SHALL enable
the Controller to clearly distinguish between those calls received direct from the aircraft and
those arising from cross-coupling (re-transmission).
© EUROCAE, 2009
23
When employing the Multi-carrier operation (CLIMAX) function, time delay differences in
excess of 10ms, due to the transmission of signals to different radio sites, may result in
echoes on board aircraft. The System SHALL provide compensation so as to keep time
delay differences within the 10ms limit. The means of compensation SHALL not in itself
result in degradation of voice quality.
Climax compensation time is included in “Ground transmission voice delay”, see Chapter
2.3.
Best Signal Selection (BSS): A “Best Signal Selection” function SHALL be implemented in
the system to handle multi receiver frequencies. This function SHALL take into account the
audio signal quality and the relative delay between the incoming signals.
It SHALL be possible for Best Signal Selection (BSS) functionality for each nominal
frequency (see paragraph 2.1 DEFINITIONS) to be manually deselected at the CWP,
supervisor position or engineering management system.
It SHALL be possible to deselect one or more individual receivers from Best Signal Selection
(BSS) at the CWP, supervisor position or engineering management system.
In the event that a change of receiver is permitted after original Best Signal Selection (BSS)
operation, the intelligibility and integrity of the received signal to the controller SHALL not be
degraded.
E.g. 1) Intelligibility will be degraded if the delay between two received signals is sufficient to
cause syllable clipping or repeating.
E.g. 2) Integrity will be compromised in the event of reception from one aircraft being
replaced by the reception of another aircraft.
In situations where Best Signal Selection (BSS) is used, Time delay differences due to the
reception of the same signal received from different radio sites (see BIDD parameter in
timing diagram Figure 9) SHALL be compensated for if greater than BIDD Max.
In situations where mixed received signals are used in preference to Best Signal Selection
(BSS), time delay differences due to the reception of the same signal received from different
radio sites may result in echoes at CWP that SHALL be compensated for if greater than 10
ms.
A variation of differential delay SHALL not affect voice quality of the message received.
© EUROCAE, 2009
24
33 [REQ RADIO FUNCTIONAL] PTT & A/C call locked-on condition prevention
Avoidance of Press -To-Talk (PTT) and Aircraft Call (A/C Call) -Locked-On Conditions
Disregarding the permitted system latency effects, jitter and permitted transient delays: a
secure mechanism SHALL be implemented in the protocol between IP components so as to
ensure that the occurrence of abnormal PTT and A/C Call conditions, as described below is
rendered impossible by design. In case of such abnormal conditions, due to other reasons,
the terminal Equipment SHALL detect and correct these automatically.
1. Normal Conditions
PTT
A PTT action (press and hold) at a Controller Working Position results in the keying
(activation) of a transmitter at a remote radio station for the same duration as the original
PTT action.
A/C Call
The arrival of a continuous radio signal, of sufficient field strength, causes the operation of a
receiver mute/squelch device resulting in the activation of the A/C Call indicator at the
Controller Working Position for the same duration as the radio signal.
NOTE 14: In some cases the A/C Call indication at the CWP MAY be extended
deliberately, by some seconds, in order to reduce the possibility that an
A/C Call of short duration is not observed by the controller.
2. Abnormal (Locked-On) Conditions
PTT
Ceasing the PTT action does not result in the remote transmitter being un-keyed (de-
activated) so that the duration of transmitter operation exceeds that of the original PTT. In
severe cases the transmitter MAY remain activated for an indefinite period - a condition
termed “Locked-On”.
A/C Call
When the field strength of the received radio signal falls below the level for receiver
mute/squelch device operation the A/C Call at the Controller Working Position remains
activated so that the duration of the A/C Call condition exceeds that of the received radio
signal. In severe cases the A/C Call MAY remain activated for an indefinite period – a
condition termed “Locked-On”.
When transmitting, Side Tone is the User’s own speech fedback, at reduced level, into the
User’s ear-piece in Headsets (or other audio devices). Side tone can be generated locally by
the VCS or from speech received “off-air” via a receiver. The latter method has the
advantage of proving, to some extent, that the system is working but complexities associated
with audio delays, phase shifts and multiple receiver operation often precludes its use.
Local side tone MAY be a suitable solution if associated with a test of the “off-air” reception.
In this respect a self-proving mechanism (system loop check) SHALL be provided.
E.g. 1) PTT out results in an “off-air” Squelch being returned.
E.g. 2) Voice out results in “off-air” Voice being received.
The system SHALL support both duplex and simplex cross-coupling functionality. Definitions
of duplex and simplex cross-coupling are as follows:-
Duplex Mode
All received frequencies in Duplex Mode MAY be re-transmitted on all the other frequencies
in the Cross-Coupled Group - but only one at a time. The received frequency re-transmitted
is always presented at the CWP.
© EUROCAE, 2009
25
This mode would be used, for example, when Sectors are combined to be controlled from a
single position.
Simplex Mode
Received frequencies in Simplex Mode are never re-transmitted on other frequencies in the
Cross-Coupled Group.
This mode would be used, for example, when a Tower frequency (VHF) is re-transmitted on
a Ground Mobile frequency (UHF) so that mobiles MAY be aware of aircraft manoeuvres in
progress and intended.
Another application would be the re-transmission of a Civil Frequency on a Military
Frequency but not the other way round.
Further details on Cross Coupling are provided in the information paper attached as ANNEX
D - CROSS-COUPLING MODES OF OPERATION.
The following Requirements [36 to 40] will also be affected by those contained in ED-136
9 [REQ RADIO FUNCTIONAL] Frequency technical state info display,
When a User selects (see NOTE 15) a frequency (see NOTE 16) on a CWP or other
terminal, in receive mode, the system SHALL have the capability to make available to the
User certain information about the Rx status. The Information provided SHALL include (but
not necessarily be limited to) the following:
• Confirmation that the Rx is available and ready for use – including the existence or failure
of the logical link to the Rx site;
• The identity of the Rx selected.
To meet the individual requirements of ANSPs the availability of this facility, and its
associated attributes, SHALL be fully configurable by means of the System Management
facility.
NOTE 15: The action of ‘selecting’ pre-supposes that the frequency has already been
configured for use at the CWP by means of the System Management (or
other) facility.
NOTE 16: In the case of receiver selection the term ’frequency’ may either refer to a
single receiver or a group of receivers where one is selected by means of
BSS. As an example 36 [REQ RADIO FUNCTIONAL] Receiver Status
Notification above has been written as for a single Rx, for simplicity, but
must be interpreted so as to include a group of receivers as appropriate.
Similarly in the case of transmitter selection the term ’frequency’ may either
refer to a single transmitter or a group of transmitters. As an example 37
[REQ RADIO FUNCTIONAL] Transmitter Status Notification below has
been written as for a single Tx, for simplicity, but must be interpreted as to
include a group of transmitters.
When a User selects a frequency, in transmit mode, the system SHALL have the capability
to make available to the User certain information about the Tx status. The Information
provided SHALL include (but not necessarily be limited to) the following:
• All items as per 36 [REQ RADIO FUNCTIONAL] Receiver Status Notification above;
• Confirmation that the Tx is available and ready for use – including the existence of a
logical link to the Tx site;
© EUROCAE, 2009
26
In the event of a frequency selection action (as per 37 [REQ RADIO FUNCTIONAL]
Transmitter Status) being rejected Users SHALL be informed as to the cause of that
rejection. Possible causes for rejection SHALL include (but not necessarily limited to) the
following:
• The total number of Users with that transmitter selected would exceed the total
permissible (in accordance with ED-136 2 [REQ RADIO FUNCTIONAL] Transmit
Configuration description);
• The transmitter is not available.
It is assumed that the unavailability of a logical link (Tx and/or Rx) would be notified in
accordance with 36 [REQ RADIO FUNCTIONAL] Receiver Status Notification and 37
[REQ RADIO FUNCTIONAL] Transmitter Status Notification and 16 [REQ SYS
ENG] Detection of End-to-End Connection Loss.
A User who has already selected a radio frequency, in either Tx or Rx mode, SHALL be
informed as to the identity of other Users with access to the same frequency, when any of
those Users execute a PTT on that frequency. This information SHALL be maintained for
either the duration of the PTT or sustained for a minimum duration as set by the ANSP.
To meet the individual requirements of ANSPs, the availability of this facility and its
associated attributes, SHALL be fully configurable by means of the System Management
facility.
NOTE 17: The facilities provided in response to 40 [REQ RADIO FUNCTIONAL]
PTT identity notification above are in addition to the Aircraft Call indication
(see ED-136 Chapte 2.1 DEFINITIONS- A/C Call Indication). One
application of this is to provide means by which Users may distinguish
between transmissions originating from aircraft and those originating from
other Users.
© EUROCAE, 2009
27
Tx F1
Case 1
Rx F1
Cross
coupling
Audio from active
F1 (which
was received
first)
VCS Tx F2
Rx F2
© EUROCAE, 2009
28
Recommendation:
Receivers SHOULD include functionality to detect if two or more transmissions are present
on the same nominal frequency* at the same time. A message SHOULD be sent to the VCS
producing a warning indication at controller working position (CWP).
NOTE 20: This functionality SHOULD be pursued in future ground receivers and all
other associated system components
* The expression 'Nominal Frequency' is used to indicate that a numerical value is not
necessarily the precise frequency being used (see paragraph 2.1 DEFINITIONS)
Audio from Rx F1
strong signal
only
VCS
FIGURE 14: ONE GROUND RECEIVER DETECTS BOTH SIGNALS OF A SIMULTANEOUS
TRANSMISSION
Two aircraft are transmitting to the controller simultaneously. The difference in signal
strength makes the stronger signal suppress the weaker in the receiver. The result is
that the controller will hear only the strong signal and be unaware of the presence of
another aircraft call.
Recommendation:
Receivers SHOULD include functionality to detect if two or more transmissions are present
on the same nominal frequency* at the same time. A message SHOULD be sent to the VCS
producing a warning indication at the controller working position (CWP).
NOTE 21: This functionality SHOULD be pursued in future ground receivers and all
other associated system components
* The expression 'Nominal Frequency' is used to indicate that a numerical value is not
necessarily the precise frequency being used (see paragraph 2.1 DEFINITIONS).
© EUROCAE, 2009
29
Tx1 F1
Case 3a
Rx1 F1
Audio from
Best voted
only
VCS Tx2 F1
Rx2 F1
In this example the frequency is detected by two radio stations and the VCS uses Best
Signal Selection to determine the best received signal and present this to the
controller. In the example two aircraft try to call the controller at the same time – the
special case is that each aircraft call is only received by one receiver.
In many implementations of BSS, one signal is voted the best and presented to the
controller. The other signals from the other receivers are muted. In this situation, an
aircraft call may be lost.
Recommendations:
The VCS SHOULD employ one or more of the following methods:
Method 1: Audio from receivers not selected by BSS SHOULD be attenuated by 15dB and
presented to the controller mixed with the voted audio
Method 2: There will normally be a slight time difference between two aircraft calls reaching
the receivers. The VCS SHOULD implement a function to detect additional aircraft calls by
diagnosing the time difference between two signals on two radio stations as follows:
New calls detected on a new radio station more than (configurable delay Xms) after the first
aircraft call, is assumed to be a new aircraft and this signal will also be presented un-
attenuated to the controller mixed with the voted signal. This method only applies when an
aircraft call was received by a receiver that did not receive the call from the first aircraft. This
is illustrated in Figure 16 below:
Method 3: The VCS SHOULD do a correlation analysis between the signals received at the
various receivers to determine whether it is the same aircraft call
© EUROCAE, 2009
30
VOTING
Leg 1 voted.
1 Strength 3
2 Strength 2
3 Strength 2
300m s
2.5.5.2 Case 3b- Ground receivers each detect both signals of simultaneous
transmission
This case is a slight variation of Case 3a and can be illustrated as follows:
Tx1 F1
Case 3b
Rx1 F1
Audio from
Best voted
(+ the other
added?)
VCS Tx2 F1
Rx2 F1
FIGURE 17: TWO GROUND RECEIVERS EACH DETECT BOTH SIGNALS OF A SIMULTANEOUS
TRANSMISSION
In this case aircraft calls from all aircraft are received by both receivers on the
frequency (which is normally the case in a Terminal Control environment) and the
situation becomes similar to Case 2.
The same recommendations as for 2.5.4 Case 2 – One Ground Receiver apply.
© EUROCAE, 2009
31
Case 4
Tx F1
Controller hears: Rx F1
1) local sidetone,
or
2) off-air sidetone
VCS
FIGURE 18: SIMULTANEOUS TRANSMISSION BY PILOT AND CONTROLLER TRANSMISSION
ON THE SAME FREQUENCY
In this case an aircraft tries to call while the controller is transmitting. As local sidetone
will most probably be used in a VoIP environment, the controller will only hear his/her
own voice as it is looped back within the VCS. In other words, the controller will not be
able to detect the aircraft call by the audio.
The receiver’s ability to detect this situation is very similar to 2.5.3 Case 1 – Two
Frequencies F1 and F2 in Cross-Coupled Mode.
Recommendation:
Receivers SHOULD include functionality to detect that two transmissions are present on the
same nominal frequency at the same time. A message SHOULD be sent to the VCS
producing a warning indication at the controller working position (CWP).
NOTE 22: This functionality SHOULD be pursued in future ground receivers and all
other associated system components
© EUROCAE, 2009
CHAPTER 3
3.1 DEFINITIONS
The following terms apply within this chapter:
• Air Traffic Service Unit (ATSU): includes any location where the business of
air traffic management is conducted including airports, ACCs and Flight
Information Units
• Bi-lateral Agreement: the term 'Bi-lateral Agreement' refers to the appropriate
authorities within the 'A'-party and 'B'-party ANSPs;
• Busy:
Terminal Busy: The condition that arises when an incoming call has reached
the 'B'-party CWP but there is no resource available to present the call to the
User (refer to section 2.1 DEFINITIONS for User definition). The Terminal busy
condition should not arise on a DA call (refer to 3.3.2) or an IA call (refer to
3.3.3), but is possible for an IDA call (refer to 3.3.4) in the event that the
incoming call queue is full.
NOTE 23: The condition of "User busy" in the sense of the User being occupied with
other calls in progress while the call queue is not full, is not relevant to
these Requirements and is considered to be a matter of local operational
procedure.
Network Busy: The condition that arises when there is no spare capacity within
the network that is providing connectivity between one VCS and another. This
may arise as a consequence of either network congestion or (exceptionally) as
a result of a command from a System Management Terminal. Throughout these
Requirements, the term "congestion" is used synonymously with "network
busy".
• Call parties: The terms 'A'-party, 'B'-party and 'C'-party are used throughout
these requirements to identify the users involved in a telephone call, as follows:
o 'A'-party: the user who initiates a telephone call – the calling party;
o 'B'-party: the user who first receives the telephone call – the called party;
o 'C'-party: any other party involved in an established call.
• Dynamic display: A device used for the visual presentation of operational
information such as caller identities, call status and programmable touch-keys.
• External Facility: A supplementary telephone service or feature that is used
between two or more Air Traffic Services Units (ATSUs).
• Facility: The term 'facility' is used to describe the function to be carried out and
the term 'Feature' gives further details or the particular attributes of the Facility.
• Feature: Refer to Facility definition.
• Internal Facility: A supplementary telephone service or feature that is used
within the boundary of a single Air Traffic Services Unit (ATSU).
• Key: Throughout these Requirements, the term 'key' is used to refer to a single
activation device such as a key, switch, button or an icon
• Monitor/Monitoring: The Audio Monitor Facility is a means by which it is
possible for one Controller to be able to listen to the audio/voice activities at the
Working Position of another Controller who is usually not physically adjacent.
The primary purpose of Monitoring is to enable the Controller who is doing the
monitoring to be able to gain real-time situational awareness of the tasks being
carried out by the controller being monitored.
© EUROCAE, 2009
33
© EUROCAE, 2009
34
The various supervisory tones and announcements as detailed in the following table SHALL
apply.
TABLE 2 – SUPERVISORY TONE DEFINITION
Tone Purpose Frequency Period
(Hz)
Dial Returned to a user when that user indicates 425 continuous
to the system readiness to dial (for
example, taking the telephone set off-
hook).
Ringing Returned to the 'A'-party after successful 425 (1 s on,
call establishment and prior to call 4 s off), repeated
acceptance.
Terminal busy Returned to the 'A'-party if there is no 425 (0.5 s on,
resource available at the ‘B’-party CWP to 0.5 s off), repeated
present an incoming call.
Congestion Returned to the 'A'-party if a call cannot be 425/1000 (0.5 s each)
completed to the required 'B'-party due to repeated
all appropriate inter-VCS links being
occupied or otherwise unavailable.
Number Returned to the 'A'-party if a terminal is 1000 (0.5 s on,
Unobtainable "Out of Service" or the 'B'-party address is 0.5 s off), repeated
(Note 28) unassigned.
Interrupt Injected into the voice path to warn a party 1000 (40ms, 0.5s off) repeated
warning of the imminent priority interruption of an for up to 15s prior to
(Note 28) established call. forced disconnection
Intrusion Injected into the voice path to warn a party 1000 1 s on
warning of the imminent priority conferencing of an
(Note 28) established call
© EUROCAE, 2009
35
The need to make DA calls should be established by bi-lateral agreement, but SHALL be
supported as both Internal and External Facilities – including across ANSP/national borders.
3.3.2.1 Facility Description
The following facilities SHALL be provided:
a) With this facility the operation of a single key by the 'A'-party is all that is
required to initiate a call.
b) The 'B'-party address is assigned and configured (by means of system
management), in the 'A'-party VCS and is thus uniquely associated with a
particular key labelled with the ‘B’-party’s identity.
c) Dial tone and out-going signalling tones are not given to the 'A'-party.
d) Ringing tone should be given (and / or visually indicated).
e) Busy tone shall be given if appropriate.
f) Terminal Out-of-service shall be given should the call fail for any reason other
than Busy.
g) The 'B'-party is alerted to the presence of the incoming call by audio and or
visual means as determined by the 'B'-party VCS.
h) The 'A'-party identity is indicated to the 'B'-party either by association with a key
assigned and fixed semi-permanently in the 'B'-party VCS or by means of a
dynamic display.
i) The 'B'-party must accept the incoming call by means of a single action
associated with a key or dynamic display.
j) Due to either the exclusive, one-to-one, assignments of the keys between the
'A' and 'B' - parties or reserved capacity in the 'B'-party dynamic display, it is
abnormal for the 'A'-party to encounter the 'B'-party busy; this is a fundamental
attribute of the Direct Access Facility.
k) Under normal conditions the 'B'-party can receive one or more Direct Access
calls and by observing the identities of the respective 'A'-parties, together with
defined operational procedure or (more likely) operational experience, the
'B'-party will deal with each call appropriately in the appropriate sequence.
l) At the end of a call either the 'A'-party or the 'B'-party may be required to de-
select/clear.
© EUROCAE, 2009
36
The need to make IA calls should be established by bi-lateral agreement, but SHALL be
supported as both Internal and External Facilities – including across ANSP/national borders.
3.3.3.1 Facility Description
The following facilities SHALL be provided:
a) With this facility the operation of a single key by the 'A'-party is all that is
required to initiate a call; some ANSPs prefer, however, that it is necessary for
the 'A'-party to sustain the key operation for the duration of the call.
b) The 'B'-party address is assigned and configured (by means of system
management), in the 'A'-party VCS and is thus uniquely associated with a
particular key and labelled with the ‘B’-party’s identity.
c) Dial tone and out-going signalling tones are not given to the 'A'-party.
d) Ringing tone is not given to the 'A'-party.
e) 'Terminal Out-of-Service' tone is given to the 'A'-party should the call fail for any
reason including any busy conditions encountered.
NOTE 30: The above is the condition as specified in the “EUROCONTROL Voice
Communication System Procurement Guidelines” [13], but ANSPs may
specify ‘Terminal Busy’ or ‘Congestion’ in response to Operational
Requirements.
f) The arrival of the call from the 'A'-party to the 'B'-party causes, simultaneously,
the events detailed in paras g) to n) inclusive.
g) The 'A'-party identity is indicated to the 'B'-party either by association with a key
assigned and fixed semi-permanently in the 'B'-party VCS or by means of a
dynamic display. Due to the usually urgent nature of Instantaneous Access calls
any visual (and/or audible) alerts should be distinctive from other types of call.
h) An audible alert is generated at the 'B'-party VCS in accordance with the
following options:
• no audible alert;
• an alert of fixed duration;
• a continuous alert requiring a silencing action by the 'B'-party.
© EUROCAE, 2009
37
i) The 'B'-party VCS automatically accepts the incoming call without any
intervention required by the User; this occurs regardless of the 'B'-party being
engaged on any other type of call. Thus 'B'-party busy is totally abnormal and
should result in Terminal Out-of-Service tone being given to the 'A'-party. At this
stage the speech channel from the 'A'-party to the 'B'-party is established. The
'B'-party ANSP may decide to have any speech from the 'A'-party handled in
one (or more) of the following ways:
• connected in conference with other speech at the 'B'-party CWP;
• directed to a loudspeaker;
• directed to one side of a split-working headset;
• any other arrangement appropriate to the local operational procedures.
j) The establishment of the call as detailed in para a) above may also result in the
'A'-party having some Monitoring facilities of the 'B'-party's Controller Working
Position including ground - ground and air-ground radio communications. This
enables the 'A'-party to exercise discretion before passing the message.
Monitoring will require the prior establishment of a bi-lateral agreement if two
ANSPs are involved.
k) If monitoring is enabled the ‘A’-party’s CWP may hear any active ground and
radio voice calls at the ‘B’-party’s CWP. Details of which parties in the active
ground and radio calls are monitored is ANSP-specific.
l) If monitoring is disabled, the ‘A’-party’s CWP SHALL NOT hear any active
ground and radio voice calls at the ‘B’-party’s CWP.
m) The 'B'-party may respond to the 'A'-party by activation of a key associated with
the incoming call. This action enables the return speech path if it occurs during
the current call; otherwise, it is treated as a new Instantaneous Access call.
n) If the 'B'-party responds during the current call, this has the effect of preventing
the call from being cleared until both parties clear the call; without B-party
response, the call is cleared when the 'A'-Party terminates the IA-call.
o) Call clearing has no effect on other calls in progress at either the 'A'-party or the
'B'-party.
3.3.3.2 Monitoring Controller’s sidetone
To prevent either echoing or audio feedback Controller ‘A’’s sidetone SHOULD always
be generated locally and never included in the monitor from Controller ‘B’.
3.3.3.3 Prevention of Eavesdropping
The only time controller ‘B’s speech (microphone) SHALL be directly fed to controller ‘A’ is
when controller ‘B’ responds to an IA call by activating his reciprocal IA key; this is now
‘conversing’ and no longer ‘monitoring’.
In the event of no calls (radio & telephone) being active at the CWP of Controller ‘B’, and an
IA call is made from Controller ‘A’, Controller ‘A’ SHALL NOT hear whatever may be being
‘picked up’ by the microphone of Controller ‘B’.
3.3.3.4 Performance Criteria
© EUROCAE, 2009
38
(c) IA SHALL be clearly distinguishable from DA (refer to section 3.3.2) in any signalling
protocol.
(d) The maximum limit for incoming simultaneous IA calls to a single CWP SHALL be set
to 3. The ANSPs SHALL have the possibility to reduce this maximum limit. Any
attempted IA call beyond the third IA call SHALL result in a busy condition.
3.3.4 Indirect Access (IDA)
The Indirect Access (IDA) facility as described below SHALL be supported as both Internal
and External Facilities using, where required, both private (AGVN) and public (PSTN)
telephone services.
3.3.4.1 Facility Description
(a) The Indirect Access facility enables a 'A'-party to enter a complete 'B'-party
address on a telephone dialling keypad (or equivalent device) in order to select
a network and to cause a call attempt to be made to the supplied address. This
is equivalent to normal dialled telephone operation.
(b) Ringing tone and busy tone are given to the 'A'-party as appropriate. A suitable
mechanism (i.e., Terminal Out-of-service tone) shall be provided to inform the
'A'-party, should the call fail for any reason other than Busy.
(c) It may be possible for calls from more than one 'A'-party to be presented to a
'B'-party simultaneously. In such cases, the selection of the next call to be
answered by the 'B'-party is determined either directly by the 'B'-party or on the
basis of an operational parameter such as longest waiting time or the Priority of
the incoming call (see section 3.3.5)
(d) It is possible for either the 'B'-party or the 'A'-party to terminate an established
Indirect Access call.
(e) In addition to dialling the 'B'-party address in full (see ‘a’ above) the following
PBX-type Facilities are also used to establish Indirect Access calls:
• Abbreviated Dialling
Entering a short code (up to four digits, a character string of unrestricted
length or a specific labelled key) on a telephone dialling keypad (or
equivalent device), shall cause a call attempt to be made from the
'A'-party to a predefined 'B'-party associated with the supplied code;
• Last Number Redial
The operation of a key, shall cause a call attempt to be made from the
'A'-party to the 'B'-party to which the most recent previous call attempt
(successful or unsuccessful) was made;
3.3.5 Call Priority
The Call Priority facility as described below SHALL be supported for deployment as both
Internal and External Facilities – including across ANSP/national borders.
3.3.5.1 Description
The call priority facility is a means of attaching an indicator (or flag) to a telephone call
to show that it is "urgent" as opposed to "routine". It is intended for use when it is
necessary to make an urgent call concerning the safety of aircraft (i.e. an emergency
situation). Thus calls can be made with or without priority so that there are two types
as follows:
• Priority Calls;
• Routine Calls.
The ultimate decision and responsibility as to whether a call is a Priority rests with the
‘A’-party in accordance with local operational procedures.
© EUROCAE, 2009
39
The System SHALL cater for all the conditions as described in Table 3 below.
Priority calls and IA calls could occur Priority calls and IA calls could occur
simultaneously simultaneously.
© EUROCAE, 2009
40
Specification The operational requirements for the The operational requirements for the
“Instantaneous Access Facility” are “Intrusion by a Priority Call” are specified
specified in section 3.3.3. in section 3.3.8.
Establishment IA facility available in the VCSs involved Priority call facility available in the
conditions and IA key present on both user VCSs involved and Priority key present
terminals. on the calling user terminal.
Called party may be free or involved in Intrusion takes place only in the event
another active call (e.g. IA, Radio, that the called party is already involved
DA/IDA routine or DA/IDA priority call), in an active DA/IDA routine call
the actual status of the called party is between the called party and a third
irrelevant. user (unwanted user).
Simultaneity It is possible to have more than one Only one intrusion to a CWP at a time.
incoming IA call to a CWP and all The first Priority call is connected and
incoming IA calls have to be further incoming Priority calls are put in
established. alerting state on the called CWP.
© EUROCAE, 2009
41
3.3.7 Typical call handling behaviour of new call events to CWP in pre-defined states
Table 4 illustrates typical VCS call handling behaviour of new call events to a CWP
while the CWP is in a pre-defined state. The table is provided for information and
guidance.
TABLE 4 – CALL HANDLING BEHAVIOUR FOR PRE-DEFINED CWP STATES ON NEW CALL
EVENTS
Pre-defined CWP state New Call Event Call handling behaviour
Free (no calls) Routine DA/IDA call DA/IDA call is presented.
Routine DA/IDA call answered New Routine DA/IDA New DA/IDA call is presented.
call
Routine DA/IDA call answered Priority DA/IDA call Intrusion occurs, if allowed by ANSP
Priority DA/IDA call answered Routine DA/IDA call New DA/IDA call is presented.
Priority DA/IDA call answered New Priority DA/IDA call New Priority DA/IDA call is presented.
IA call in progress Routine DA/IDA call New Routine DA/IDA call is presented.
IA call in progress Priority DA/IDA call New Priority DA/IDA call is presented.
Routine DA/IDA call New Routine DA/IDA New Routine DA/IDA Call is
+ Priority DA/IDA call call presented.
answered
Routine DA/IDA call New Priority DA/IDA call New Priority DA/IDA Call is presented.
+ Priority DA/IDA call
answered
Routine DA/IDA call answered New Routine DA/IDA New DA/IDA call is presented.
+ IA call in progress call
DA/IDA call answered Priority DA/IDA call Intrusion occurs, if allowed by ANSP
+ IA call in progress
If Intrusion is not allowed by ANSP
the new Priority call is presented.
© EUROCAE, 2009
42
© EUROCAE, 2009
43
© EUROCAE, 2009
44
• all calls in the queue are in a calling (ringing) condition until answered;
• a manual process may be used for selecting the next call to be answered but this does
not preclude some form of first-in-first-out automatic selection;
• additional indications should be used to identify Priority Calls that have arrived in the
queue. Such indications might include a unique flag against the queue entry, a
different display attribute (e.g. flashing characters or a unique colour) and a distinctive
audible alert.
Although it will usually be IDA calls that are directed to the Call Queuing facility, in some
exceptional circumstances (most commonly fault or call diversion conditions), DA calls may
also be placed in a call queue. In these cases, it is recommended that some additional
means of identifying the call as a DA call is given.
© EUROCAE, 2009
45
© EUROCAE, 2009
46
© EUROCAE, 2009
47
A VCS SHALL support the following existing user numbering and addressing schemes:
- Numbering Scheme as defined in:
o “ICAO Manual on ATS Ground–Ground Voice Switching and Signalling”
(Chapter 2 Section 2.3) [1]
o EUROCONTROL document "ATS Ground Voice Network Implementation and
Planning Guidelines”. [14]
o EN 300 189 "Private Integrated Services Network (PISN); Addressing" [26]
- IP Addressing Scheme:
o Compliant with EUROCONTROL IPAX (Internet Protocol for Aeronautical
Exchange) address structure [20].
- Mnemonic Addressing Scheme
o Based on relevant ATS information (User, ATS sector, ATS radio frequency,
ATS radio site, ATSU, ICAO site identifier, ANSP or ATS Organisation).
3.5.2 Number or Address Assignment
Each end user SHALL be allocated one or more unique addresses or numbers within the
scope of the VCS addressing scheme.
3.5.3 Global Numbering Schemes
Compatibility with the current recommended ICAO numbering plan as specified in ICAO doc.
9804 SHALL apply [1]
The global PSTN numbering scheme SHALL comply with ITU-T E.164 [24]
3.6 EXTERNAL CONNECTIONS AND PROTOCOLS
© EUROCAE, 2009
48
Supporting documents:
ETSI ES 203 021 [37] and ETSI Advisory Notes EG 201 121 [42]
CB ITU-T Rec. Q.23 [58] ITU-T Rec. Q.24 [59] and ITU-T G.224 [52]
ETSI EN 300 659-1 [34] /EN 300 659-2 [35]
© EUROCAE, 2009
49
NOTE 34: The terms FXO and FXS are commonly used in North America while the
terms RIDO (PSTN/PBX) and DIRO (CB) are used more often in Europe.
This document considers FXS to be equivalent to DIRO (CB) and FXO to
be equivalent to RIDO (PSTN/PBX). The DIRO/FXS interface is used to
connect analogue terminal/stations to the VCS, allowing address
information to be Dialled-In from the terminal/station to VCS and providing
a Ring-Out Voltage towards to terminal/station. The RIDO/FXO interface is
also used to connect analogue terminal/stations to the VCS, but allows
Ring-in voltage from terminal/station to the VCS and then triggers address
information to be dialled out from the VCS towards another VCS.
3.7 INTERWORKING WITH ATS LEGACY SYSTEMS
The IP AGVN systems SHALL interwork with ATS-R2/ATS-QSIG based AGVN systems in
order to support calls originating in one environment and terminating in the other.
The VoIP VCSs SHALL guarantee call interworking with appropriate mapping of the call
signalling (i.e. user identification, terminal status, priority, call intrusion, call protection etc.)
and also necessary voice transcoding required between legacy circuit-switched AGVN
systems and IP AGVN systems and vice versa. The Table 7 below defines whether
interworking between the various signalling protocols and voice codecs is Mandatory
(SHALL) or Recommended (SHOULD).
Interworking with ATS-No.5-based AGVN systems is RECOMMENDED.
© EUROCAE, 2009
50
The IP AGVN systems SHALL enable users to establish external voice connections to both
PBX terminals and PSTN trunk lines.
Following ICAO Annex 10, Vol. II, Chap 2.2 “Telecommunication access” [5], all aeronautical
telecommunication stations, including end systems and intermediate systems SHALL be
protected from unauthorized direct or remote access.
3.9 INCOMING CALL BARRING AND RESTRICTION
When the VCS has connections to external networks it SHALL be possible to restrict or
block unwanted callers. For that purpose the VCS shall employ a way to either block (bar)
calls or re-route calls based on their Calling User Identity (CUI) in accordance with the
following requirements:-
1. The VCS SHALL be able to bar or restrict incoming calls based on their CUI.
2. The VCS SHALL be able to bar or restrict incoming calls without CUI.
3. The VCS SHALL employ a barring and restriction capability. Means SHALL be
available to define actions in respect with CUI (e.g. barring, restriction).
Wildcard designators SHALL be accepted in the CUI.
4. Calls that are defined to be barred SHALL be treated as calls to a busy or non-
allocated subscriber depending on network specification.
5. Calls that are defined to be restricted SHALL be routed according to a specified action
3.10 HANDLING OF OUTGOING CALLS / ROUTING CRITERIA
When either the VoIP Gateway (GW) or VCS employ connections to external networks
such as the PSTN, it is necessary to have the possibility of controlling how the
external networks are used for outgoing calls. Many VCS systems employ an
independent numbering scheme, and most external networks employ their own
independent numbering schemes. It is therefore necessary to provide a means of
translation (or mapping) between the internal numbering scheme and those employed
by external networks.
© EUROCAE, 2009
51
CHAPTER 4
© EUROCAE, 2009
52
In order to discriminate between different types of voice services (radio and telephone, for
example) during the call establishment phase, the following association between call types
and the SIP Priority Header field SHALL be provided.
TABLE 8 – ASSOCIATION BETWEEN CALL TYPES AND THE SIP PRIORITY HEADER FIELD
NOTE 35: The term “SIP Priority header field” as defined in Table 8 is different from
the term “Priority Call” as used in 3.3.5.1. A Priority call according to 4.4.2
is classed as an operational tactical or strategic call having its SIP Priority
Header field set to “emergency”, while a Routine call is classed as a
tactical, strategic or support call having its SIP Priority Header field set to
“Urgent”, “Normal” or “Non-Urgent” respectively depending on ANSP
requirement.
4.4.3 Precedence of Voice services
Functionality to discriminate between different operational types of voice services (radio and
telephone, for example) SHALL be provided at the link/network/transport OSI layers. Fifteen
types of service SHOULD be available.
© EUROCAE, 2009
53
The ANSPs are responsible to assign a precedence level to each type of voice service, but there is a
potential Safety hazard where there is no common scheme applied by all the ANSPs. There is,
therefore, a need for the ANSPs to agree on the setting of precedence levels for all services to be
carried on the IP network. An example of such a precedence scheme for voice services is as follows:
Packets containing IP-voice or IP-voice related signalling SHALL always be privileged while
passing through the network.
4.4.5 IP-voice / IP-data packet flow separation
IP-based networks carrying data and voice in a common network infrastructure SHALL
implement means to separate IP encapsulated voice packets from other IP-encapsulated
user applications in order to assure that voice is not affected by data traffic. The separation
MAY be performed by the physical or the logical network infrastructure.
4.4.6 No QoS degradation of IP-voice
© EUROCAE, 2009
54
Each ANSP is responsible to define a precedence scheme identifying the precedence levels
assigned to voice services and the system SHALL facilitate this.
Each ANSP SHOULD coordinate with adjacent ANSPs so as to ensure that their
precedence schemes are compatible. The meaning of “Compatible” is that there are no
conflicts that could impact on either safety or security.
4.4.8 Precedence of Voice packets during Congested or degraded network operation
In degraded network operation, IP-based networks carrying digital data and digitized voice in
a common network infrastructure SHALL implement means to assure precedence is always
given to voice packets and to prioritize the voice service with highest precedence given to
voice packets.
4.5 AVAILABILITY: ISSUES, GUIDANCE AND MAIN PRINCIPLES
4.5.1 Introduction
This sub-chapter has been compiled to:
• highlight the issues concerning availability;
• provide some guidance as to how high levels of availability may be achieved for
individual ATM facilities;
• detail the main principles to achieve high levels of availability.
The above approach is an alternative to specifying actual performance figures for
either individual systems or entire services. The reasons for this approach may be
summarised as follows:
• The concept of when a service is “unavailable” (taken to mean “declared unfit
for its intended purpose”) varies widely amongst ANSPs.
• The true boundary of what is encompassed by a precise availability figure is not
always clearly defined and understood – and again will vary amongst ANSPs.
• Theoretical prediction of availability may prove to have a wide margin of error.
• Specification of availability figures (for both individual systems and complete
services) is often done in a cautious manner such that the tendency is to over,
rather than under specify. System suppliers will often respond to this by over-
engineering with consequential costs.
The definition of service availability requirements is outside the scope of this ED-136
document.
4.5.2 Availability Issues
• It is, ultimately, the responsibility of each ANSP to determine what constitutes
safe practice, which includes the use of safe systems. The ANSP Regulatory
Authorities will demand evidence of safety analysis ‘cases’ being established. At
a lower level, responsibility rests with the ‘service provider‘ (see NOTE 36
below), who has to comply with prescribed availability requirements using the
facilities that are available to them.
NOTE 36: In this context the term ‘service provider’ implies the Authority responsible
for the provision of individual services – E.g.: Air-Ground Radio, Approach
Radar
• In the short-medium term it is assumed that CWPs and VCSs will continue to be
used without any major changes in system architecture and software, other than
those that arise through technological/commercial developments. Therefore the
current availabilities of these items will either be maintained or improved.
© EUROCAE, 2009
55
• The item which will be introduced in the short-medium term will be a new IP-
based network that provides connectivity between remote sites. It is this
network which will introduce a significant change in architecture replacing
services that previously would have been provided by the Public
Telecommunications Operators (Telcos). The availability of the IP-based
network, used for voice, is therefore the main point of concern as are the newly
developed and implemented ‘gateways’ which will provide IP interfaces to the
legacy systems.
• Should the assumptions above be valid, the IP-based network including any
gateway interfaces, will have to achieve an end-to-end availability that at least
matches that of a Telco for standard analogue and digital private circuits (i.e. in
the order of 99.8%).
• The ‘service provider’ recognises that a Telco is a common point of potential
failure and takes steps to mitigate this where alternatively-routed, back-up
circuits are judged to be necessary. In a similar manner, the IP-based network,
including any gateway interfaces, would need to equal the total availability of
two independently-routed circuits (one of which need not necessarily be via a
Telco), by employing for example a private microwave link etc.
4.5.3 Points of Guidance
• Both the ‘service providers’ and the IP Network Provider recognise that the IP
Network is a common point of potential failure, such that back-up services
SHOULD be adequately protected. Ground telephone for example is often the
designated back-up to be used in the event of an OLDI link failure. Steps need
to be taken therefore to avoid common points of potential failure.
• For radio applications the current practice of providing a standby radio system
(possibly with reduced functionality when compared with the ‘main’ radio
system) SHOULD continue.
• The IP Network SHOULD be designed so as to meet the requirements of Radio
applications (that have the most stringent criteria), taking into account the
standby radio systems that SHOULD also be provided.
• Some ANSPs and Safety Regulatory Authorities have adopted the Risk criteria
for radio as illustrated below:
Event
Sudden inability to provide any degree of air traffic control (including
contingency separation measures) within one or more airspace sectors for a
significant period of time.
Tolerability
Unacceptable.
Probability of Occurrence
Extremely improbable (i.e. Extremely unlikely, if not inconceivable to occur)
Quantitative Value per operational hour per sector < 10-7.
4.5.4 Illustrative Case Examples
Given below are two practical cases illustrating how the operational environment and
the architectural choices made by an ANSP will influence the required availability of
the VoIP system and/or of one of its components.
Case 1: The ANSP policy is to cover one ATC sector with one frequency using
2 radio locations (main and back-up), each location containing two sets of
redundant transmitters/receivers. Thus 4 sets of transmitters/receivers are
available to cover the sector.
Case 2: Only one transmitter and one receiver are available to cover an ATC
sector.
Conclusion: In case 2, the availability requirements of the single transmitter
and receiver equipment must be higher than in case 1 in order that the intended
service availability for both cases is the same.
© EUROCAE, 2009
56
© EUROCAE, 2009
57
CHAPTER 5
RECORDING
5.1 BACKGROUND
Given that recording of Controller Voice communications, the methodology employed
in their management and the quality of service requirements to be applied etc, are
currently subject to well-established ANSP practices, the following requirements relate
only to the possible impact of introducing IP-based technology.
Emphasis has therefore been placed on defining requirements to comply with existing
ICAO SARPs and what is foreseen in order to comply with National Regulatory
requirements.
5.2 RECORDING REQUIREMENTS’ ASSERTIONS
This section drafts out a framework of assertions under which recording SHALL be
undertaken.
Assertion #1
Only those requirements applicable to voice recording will be considered.
(e.g. radar data recording etc is outside the scope of WG-67)
Assertion #2
Only those requirements relating to the recording of voice communications associated
with Air Traffic Services Units (ATSUs), refer to NOTE 37 below, will be considered
i.e. all Operational Voice interactions (within and to/from the Operations Room) as
follows:-
• ATSU – ATSU communications;
• ATSU – radio stations;
• All communications within an ATSU relating to Air Traffic Management;
• All communications between the ATSU and the military units;
• All communications related to the management of emergencies;
• All communications to/from the Operational Areas;
• Controller working positions using local radios and standby facilities.
NOTE 37: The term ATSU is used to include any location where the business of air
traffic management is conducted including airports, ACCs and Flight
Information Units etc.
Assertion #3
The legal boundary within which recording will be performed is that of the ATSU.
Recording at other locations may be an ANSP specific requirement and outside the
scope of these requirements.
NOTE 38: ‘Legal’ Recording responsibilities rest within each individual ATSU –
subject to specific regulatory requirements.
5.3 RECORDING REQUIREMENTS
Within the framework stipulated in the section above this section details the actual
‘legal’ recording requirements. Reference is made to ICAO –Annex 10, Volume II,
Chapter 3.5 relating to recording of ATC communications [6].
© EUROCAE, 2009
58
The IP system SHALL, at all times, provide a means for recording voice which is a true and
faithful representation of the audio signals being presented at the points detailed in 4 [REQ
RECORDING] ENTITIES FOR VOICE RECORDING AND LOCATION IDENTIFICATION
below. (Audio quality SHALL neither be degraded nor improved).
The IP system SHALL provide a means by which two autonomous voice recordings can be
made. Both recordings SHALL be identical in all respects.
NOTE 39: The assumption here is that two recording devices would be required for
redundancy, maintenance purposes etc.
For the purposes of imprinting date and timestamp information with the recorded voice (in
order to enable the time and date of re-played voice messages to be precisely identified), the
IP System SHALL be synchronous with the date and time data source utilised by the
associated ATSU. (This is assumed to be Universal Time, Coordinated (UTC) to the
accuracy specified by ICAO [11]
The IP system SHALL provide a means by which recordings SHALL be made of voice
messages at the following entities:
• a specific controller working position;
• a specific radio receiver;
• a specific radio transmitter;
• a specific 3rd party.
The exact location of the entities above SHALL be identifiable and demonstrable with high
integrity during replay of the recordings.
Provisions SHALL be made to enable the recording of all communications at position level.
5.3.1 Short Term recording at CWP
To facilitate an instant re-play facility the system SHOULD provide a “short term
recording” functionality at the controller working position level for radio
communications.
© EUROCAE, 2009
59
CHAPTER 6
VOICE QUALITY
6.1 INTRODUCTION
The speech quality using VoIP in an ATM environment is an important aspect and the
requirements are presented from the user perception as well as technical
requirements on transmission characteristics.
The key requirement within this document is that of the subjective measurement
required. There are no requirements placed on items such as the speech coding
algorithm, jitter and packet loss although all of these things may affect the voice
quality. EUROCAE Document ED-137 ‘Interoperability Standards for VoIP ATM
Components’ [22] includes details as to how these items should be managed by the
G/G segment in order that compliance to key subjective measurement requirements
can be achieved.
6.2 REFERENCES
The following references defined in ANNEX A REFERENCES are applicable to this
chapter.
• E67-WP-DGAC-08-V01 Version 3 (06/06) DSNA Reference Paper:
Requirements for “Voice Quality” [47]
• ITU-T Recommendation G.109 (09/99): Definition of categories of speech
transmission quality [48]
• ITU-T Recommendation G.114 (05/03): Transmission Systems and Media,
Digital Systems and Networks - International telephone connections and
circuits – General Recommendations on the transmission quality for an entire
international telephone connection- One-way transmission time [49]
• ITU-T Recommendation G.116 (09/99): Transmission performance objectives
applicable to end-to-end international connections [50]
• ITU-T Recommendation G.131 (11/03): Talker echo and its control [51]
6.3 REQUIREMENTS
6.3.1 Voice Transmission Quality
1 [REQ VOICE QUALITY] Mean Opinion Score of A/G & G/G communications >4
The system SHALL achieve a Mean Opinion Score (MOS) > 4.0 (This is equivalent to
80 ≤ R < 100) for all air-ground and ground-ground communications.
TABLE 10 – ITU-T G.109- RELATIONSHIP BETWEEN E-MODEL (R), MOS AND SPEECH
TRANSMISSION QUALITY CATEGORY
Speech transmission
R-value range User satisfaction MOS
quality category
© EUROCAE, 2009
60
The system SHALL ensure that during any communication, the User’s own echo is within
the acceptable area of the ITU-T G.131 [51] recommendation as illustrated in Figure 20
below, for both telephone (reflected echo) and radio (sidetone).
© EUROCAE, 2009
61
The one-way voice delay for ground-ground communication between CWPs located within
the same or different ATSU’s SHALL be less than 150 ms, in compliance with ITU-T
recommendation G.114 (05/03) [49]
NOTE 40: ITU-T G.114 (05/03) Appendix II – Guidance on one-way delay for Voice
over IP states that for many intra-regional routes (e.g., within Africa,
Europe, North America) within the range of 5000 km or less, users of VoIP
connections are likely to experience mouth-to-ear delays <150 ms.
6.3.4 One-Way Voice delay (Radio)
The system SHALL comply with the 2.3 RADIO SYSTEM PERFORMANCE
REQUIREMENTS as defined in 6 [REQ RADIO PERFORMANCE] 130ms max Ground
Transmission Voice delay.
6.3.5 Syllable Clipping
Clipping in a speech network is when parts of a word are cut from a section of speech.
This normally occurs at the start and end of a section of speech but may also occur
during active speech.
6.3.6 Clipping Speech Segments
The voice transmission characteristics requirements SHALL apply to the voice channel only
and do not include microphone and headset characteristics.
The end to end transmission characteristic parameters SHALL be shared evenly between
the encoding end and the decoding end.
The requirements for transmission characteristics MAY not be realistically met if legacy
analogue lines/trunks (i.e. ITU-T M.1030 [54]) are used within the network.
6.3.8 Voice Frequency Response
The frequency response of any ground-ground connection SHALL be such that the gain at
any frequency between 300Hz and 3.4 kHz SHALL be within +1dB and -3.0dB of the gain at
1 kHz.
NOTE 41: The minimum frequency response of any air-ground connection should be
such that the gain at any frequency between 300Hz and 2.8 kHz should be
within +0.7dB and -3.0dB of the gain at 1 kHz.
© EUROCAE, 2009
62
6.3.9 Cross-Talk
8 [REQ VOICE QUALITY] Cross-Talk level <-60dBm0 for 1KHz test tone
The Crosstalk level on any voice circuit SHALL not exceed -60dBm0 when a 1 kHz test tone
is injected into any other voice circuit at a level of 10dB above nominal test tone level, with
all voice circuits correctly terminated. (The nominal test tone level is -10dBm0)
6.3.10 Noise and Hum
The residual noise and hum on any correctly terminated idle voice circuit SHALL not exceed
-60dBm0p.
6.3.11 Total Distortion, including quantizing distortion
The Total Distortion, including quantizing distortion SHALL comply with ITU-T G.712 [53].
© EUROCAE, 2009
63
CHAPTER 7
© EUROCAE, 2009
64
© EUROCAE, 2009
65
A topology view is provided in Figure 22. It illustrates the fact that even HMI elements
have to be considered separate entities providing management capabilities.
© EUROCAE, 2009
66
At the IfRadio/ interface the following services categories SHALL be provided as a minimum:
• HW/SW Configuration: identify and address a single HW component (e.g.
transmitter, receiver) and configure;
• HW/SW Status: identify and address a single HW component (e.g. transmitter,
receiver), register for status notification and provide status information on request;
© EUROCAE, 2009
67
• Audio Status: identify and address a single HW component (receiver), register for
status notification and provide status information on request;
• Radio Service Configuration: identify and address service and configure;
In addition it SHOULD support the following:
• Radio Service Availability: identify and address a radio service, register for status
notification and provide status information on request;
• User/Role/Mission Configuration: exchange User/Role/Mission information including
access rights.
At the IfRecording interface the following services categories SHALL be provided as a minimum:
• HW/SW Configuration: identify and address recording component and configure;
• HW/SW Status: identify and address recording component, register for status
notification and provide status information on request;
• Recording Service Configuration: identify and address the recording service and
configure.
In addition it SHOULD support the following:
• Recording Service Availability: identify and address a single service, register for
status notification and provide status information on request;
• User/Role/Mission Configuration: exchange User/Role/Mission information including
access rights.
Management activities SHALL use industry standards in minimum on the Vienna Agreement
Interfaces IfRadio, IFRecording and IFRadio/Telephone:
A management system SHALL support industry standards and SHOULD integrate the
different management capabilities into a single framework.
The design of the system SHALL ensure that no single point of failure can lead to a
complete outage of the whole system.
7.2.2 Statistics / General
The VCS system SHALL have integrated and sophisticated capabilities to collect and report
on statistical data both for incoming and outgoing calls as well as the system performance. It
will be comprehensive/flexible and SHOULD allow all data to be freely defined, processed
and arranged in any format. Comprehensive reporting facilities SHOULD be managed within
the system without need for extensive data processing outside the system.
© EUROCAE, 2009
68
For Incoming Calls it SHALL be possible to make detailed statistical analysis per CWP, per
group of CWPs, per calling number, per date, per week, per month etc.
Data for all the following fields SHALL be recorded in order that analysis can be made
relative to a date, time and CWP for each circumstance.
• The hourly, daily, weekly, monthly list of calls with time and date stamps;
• List of numbers called, together with the corresponding calling number (ATS-R2,
PSTN/ISDN or ISDN);
• The exact duration of each call in seconds;
• The exact time elapsed in seconds prior to an incoming call being answered;
• Time stamps for call transfers together with the number to which the call is transferred
• Maximum time to answer a call
• Mean time to answer a call.
• Maximum call duration prior to call termination.
• Number of unanswered calls with a detailed list showing the called and calling
numbers together with the alerting time period and the time elapsed before the call
was terminated by the originator.
• Telephone/ATS-R2 number of calling number.
• Name of position that answered the call.
• For unanswered calls, it SHALL be possible to distinguish the reason from the
following circumstances:
o Normal calls lost
o Calls to engaged CWPs
o Calls diverted to voice mail.
o Maximum time to call termination.
7.2.4 Statistics / Outgoing calls
For Outgoing calls it SHALL be possible to make detailed statistical analysis per CWP, per
group of CWPs, per destination, per date, per week, or per month etc.
Data for all the following fields SHALL be recorded in order that analysis can be made
relative to a date, time and CWP for each circumstance.
• The hourly, daily, weekly, monthly list of calls made per CWP with time and date
stamps.
• The exact duration of each call in seconds
7.2.5 Maximum number of CWPs
© EUROCAE, 2009
69
The system architecture SHALL permit the installation of redundant components in separate
locations.
7.2.8 System Circuit Check
The system SHALL provide means to automatically ensure all telephone and radio
interconnections are operational and ready for use by the end terminals (local battery lines
excluded).
7.2.9 Detection of End-to-End Connection Loss
The system SHALL check, continuously, that both telephone and radio call setups are
possible to all ATSU and Transmitter/Receiver locations that have been configured, such
that any end-to-end connection loss (i.e. caused by broken links, no bandwidth availability,
significant packet loss…) to these locations SHALL be detected within 3 seconds and the
event noted by the System Management facility within that time.
It is also expected that an occurrence of this event would be indicated to the User but, in
order to meet the individual requirements of ANSPs, the actual characteristics of this SHALL
be fully configurable by means of the System Management facility.
NOTE 44: This Requirement applies where digital links are used and is not intended
to introduce new line checking procedures, beyond those currently
deployed, where (legacy) analogue circuits are used.
7.2.10 Transit
The VCS SHALL have the ability to route an incoming call from one VCS (Preceding VCS)
to another VCS (Subsequent VCS).
7.2.11 Classes of Service
In order to differentiate between several operational types of voice services (radio and
telephone), system engineering SHALL provide the functionality to create different classes
of service. In the event of a failure inside the network resulting in a loss of bandwidth, the
system management SHALL provide the functionality to allow the call to proceed, or to
cancel the call, according to the available bandwidth and the class of service associated with
a radio or telephone call priority.
Each ANSP is responsible for assigning each existing priority call associated with a class of
service to a particular operational service type.
7.2.12 VCS on-line reconfiguration
7.2.12.1 Introduction
An Air Traffic Services Unit (ATSU) operates under constantly changing traffic loads
and operating conditions. It also has to deal with a number of different types of
emergency situation.
Predictable changes in traffic load are managed by appropriately combining certain
“sectors” and “user roles” during periods of low traffic and separating them during
periods of heavier traffic.
© EUROCAE, 2009
70
Sometimes one or more elements of an ATC CWP may be “out of service” due to
maintenance or technical problems. Such problems must be solved without any
disruption to air traffic control by transferring operation to another unused ATC CWP
or “sector suite”.
Such circumstances can be managed by an ON-LINE RECONFIGURATION feature
and the dynamic labelling address information.
7.2.12.2 Requirements
On-line Reconfiguration within a centre SHALL NOT have technical or operational impact on
adjacent centres.
On-line Reconfiguration within a centre SHALL NOT have impact on calls that are already
established;
22 [REQ SYS ENG] Routing method to establish calls during on-line re-
configuration
Incoming and outgoing telephone calls, being established during an on-line reconfiguration,
SHALL be routed to either the original destination or the new destination (after re-
configuration).
The following is an example of telephone online reconfiguration implementation, provided
only as information. Each ANSP remains responsible for the specification of its own
implementation.
© EUROCAE, 2009
71
User “A+B”
CA
(CWP3 keyboard)
DA EA FB
GB HA IA
The system SHALL have an audio mixing capability in order to handle simultaneous
telephone and radio calls. This functionality SHALL be available on each CWP. The choice
of what is heard by the controller is ANSP-specific, but SHALL be enabled through
configuration by means of the system management facility.
7.2.14 Loss of Power
In case of power loss, the Ground Telephone and Radio functions SHOULD be
capable of normal operation within 2 minutes of power recovery.
A convenient and ready means SHALL be provided whereby an engineer can perform a
routine end-to-end system check. This involves the ability to make radio transmission and
listen, in real time, to the output of the recording system for the radio channel under test.
© EUROCAE, 2009
72
The VCSs SHALL have interfaces to the “Public Switched Telephone Network” (PSTN),
permitting calls to be made to destinations outside the ATS Ground Voice Network in order
to provide link fall-back or simply as an alternative to the leased line scenario. This
functionality SHALL be restricted and controlled to ensure that unwanted external callers are
prevented from gaining access to trunk lines used for operational air traffic management.
7.5 RADIO SYSTEM ENGINEERING REQUIREMENTS
Depending on the Ground Radio Station architecture, transmission and reception facilities
could be located on separated sites and interconnected with different type of links (i.e. radio
link, copper cables, optic fibre etc)
These various types of architecture SHALL be covered by the radio gateway specification
and by the IP compatible transmitter/receiver specification.
An IP system (VCS and WAN) SHALL be designed to operate all the frequencies
simultaneously, whatever their operational mode. (with no access and bandwidth limitations).
There SHOULD be no architectural limitation on the total number of Frequencies and radio
channels possible.
The VCS SHALL support the following 3 options for Tx/Rx selection:
• Option 1: Individual transmitter and receiver selection is either a VCS or RCE
configurable parameter. The User has no means of selection available at the CWP.
• Option 2: The User selects at the CWP which transmitter and receiver combinations
are in use on each frequency. The quantity of transmitters and receivers locations and
permissible combinations, including default settings are specified by the ANSP.
• Option 3: The User selects at the CWP which transmitter and receiver locations
SHOULD be active. Best Signal Selection (BSS) MAY be used to automatically select
the specific receiver signal transferred to loudspeaker/headset.
By design the system SHALL provide the facility to use 28 radio frequencies in each cross-
coupled group. A system management configuration, the system SHALL provide the facility
to set this number between 2 and 28.
© EUROCAE, 2009
73
There SHALL be no limitation in the number of active cross-coupling groups at CWP level
and at VCS level.
35 [REQ SYS ENG] Speech Activity Detector with Pseudo Squelch signal
generation
A Speech Activity Detection (SAD) device SHALL be provided to safeguard against the
possibility that a voice signal is received without any squelch. In this eventuality, a “SAD
active” condition SHALL ensure that the speech is presented at the CWP in the same
manner as if the squelch had been received normally. The system management facility
SHALL provide means to activate the SAD functionality, set the SAD sensitivity, noise
immunity, reaction time and minimum operation time.
During each PTT activation, the VCS SHALL perform TX/RX-loop check by automatically
comparing outgoing TX-activation and audio with the activation of associated RX and
received off-air audio in order to detect any malfunctioning.
NOTE 45: In case of only local side tone being provided to the User, the test shall be
suitably designed in order that the received audio being checked is in
reality the received off-air audio.
The VCS SHALL provide the capability to regularly perform an automated (or manual)
TX/RX loop check on each configured radio channel, in order to detect any malfunctioning
prior to its operational use.
Some parameters MAY be configurable in order to allow the ANSP to minimize channel
load: for instance it is possible that the automated frequency check is performed during low
frequency usage i.e. during night time operation.
If automated, this check SHALL NOT interfere with any active radio call in progress.
NOTE 46: At the time of publication of this ED-136 document, this check is usually
performed by transmitting a 1 kHz tone in the air, which differs from the
check defined in the ICAO ANNEX 10, Vol. II, Ch. 5.1.3 [7]
recommendation stating that the check should be performed by
transmitting a voice message containing the frequency text, the locator and
the expression “frequency check”.
NOTE 47: This test may be started automatically on each frequency (key) selection
by the Controller, depending on the operational and technical procedures
employed by the ANSP.
© EUROCAE, 2009
74
In case of failure of any transmitters and/or receivers, the VCS SHALL provide the following
switching capabilities:
• Automatic switching to alternative transmitters and/or receivers which could be in
different locations to those that have failed.
• Manual switching or Manual switching inhibition of any transmitters and/or receivers.
In both cases, the need for switching SHALL be triggered by the VCS, based on alarm
conditions coming from the Ground Radio Station (GRS).
The system management facility SHALL provide means by which any round-trip propagation
delay may be taken into account to trigger an alarm. This delay SHALL be configurable by
maintenance personnel.
The system SHALL detect if certain frequencies (as configured by the System Management
Terminal) are not selected at any CWPs. If this is the case, at least an alarm SHALL be
generated. Further reaction is ANSP specific but MAY include Automatic re-selection.
40 [REQ SYS ENG] Automatic Gain Control for Tx & Rx speech levels
An “Automatic Gain Control” (AGC) device SHALL be implemented in both the VCS Tx and
Rx paths, the Tx equipment and the Rx equipment. The activation and de-activation of the
AGC SHALL be configurable.
It is recommended for an ANSP to use only one AGC device in each path.
AGC SHALL be implemented in the VCS in order to control the speech levels sent towards
transmitters and speech levels once received from receivers. AGC SHOULD also be
provided in both the transmitter and receiver equipment. The system management facility
SHALL be able to control all of these AGC facilities including levels, range, activation and
de-activation.
It is recommended that ANSPs activate only one AGC from the VCS to the antenna and one
AGC from the VCS to the CWP.
For maintenance purpose, the VCS SHALL enable easily access in order to display any
output/input signals such as: Call signalling, PTT, SQUELCH….
Regardless of whether the VCS is either a combined (both radio and telephone) type or
separated (radio or telephone) type, it SHALL employ a mixer function that permits the
controller to use their Headset device for both radio and telephone communications.
The Headset and Boom microphone interface SHOULD be ARINC 535A compliant [60]
The Hand-Held microphone interface SHOULD be ARINC 538 compliant.[61]
All the peripherals SHALL have direct access to a date & time reference source.
© EUROCAE, 2009
75
© EUROCAE, 2009
76
CHAPTER 8
SECURITY
8.1 INTRODUCTION
The concept of security has to be clearly separated from the concept of safety and
availability (for details regarding those aspects, refer to CHAPTER 4 of ED-136). The
ANSP should define and analyse the typical scenarios concerning system
configuration and system environment to meet their security requirements. Based on
this appropriate threat scenarios may be analysed (threats, risk, measures). The
resulting security requirements should address all security aspects (confidentiality,
integrity, availability, authenticity, non-repudiation) and should comprise all system
layers as integral parts of the whole concept. Security approach should consider use
of best practices and approved security mechanisms for the lower layers and then
define any necessary special requirements which should be realised in the application
layer.
In this chapter, security has the following meaning:
- A condition that results from the establishment and maintenance of protective
measures that ensures that the risk of violability, from hostile acts or
consequences of human errors, has been reduced to an acceptable level. Each
ANSP has the responsibility of determining this level and ensuring that it is, as a
minimum, maintained.
- The condition that prevents unauthorized persons from having access to a
specific resource in the IP system
8.2 ASSUMPTIONS
a) Voice communications will be carried on a ‘private’ network (see ‘e’ below) used
only for the purposes of Air Traffic Management (ATM) and is not a public
network. (This does not preclude the possible use of out-sourcing of network
provision and management).
b) Security in terms of adequate control of third parties (provision of out-sourced
network) is the responsibility of the ANSP.
c) Security in terms of physical access controls to the voice system and network
equipment is the responsibility of the ANSP.
d) Security in terms of ensuring that only competent staff may use or modify the
behaviour of the voice system and network is the responsibility of the ANSP.
e) EUROCONTROL member states will establish an IP network for data
applications known as the Pan-European Network Service (PENS). The core
architecture of PENS will be an ANSP Backbone, the Service Specifications of
which include Security Requirements. For information some details of these
security requirements are included in ANNEX C to this document. It is assumed
that all of the security aspects detailed in ANNEX C will be covered under the
PENS implementation.
8.3 SECURITY REQUIREMENTS
8.3.1 Integrity of IP-voice packets
Means SHOULD be applied to guarantee the integrity of packets carrying IP-voice or
IP-voice related information. As a minimum, corrupted or unauthorized modified
information elements SHOULD be detected.
8.3.2 Confidentiality of IP-voice information
Means SHOULD be applied to guarantee the confidentiality of IP-voice and IP-voice
related information exchanged via the network. As a minimum, confidentiality
compromises SHOULD be detectable by the application.
© EUROCAE, 2009
77
Packets addressing radio resources SHALL solely be accepted when originated by radio
resources. Packets addressing telephone resources SHALL solely be accepted when
originated by telephone resources. As a minimum, any uncertainties regarding authenticity
SHOULD be detectable by the application.
© EUROCAE, 2009
78
ANNEX A
REFERENCES
[1] ICAO “Manual on ATS Ground-Ground Voice Switching and Signalling“ (Doc
9804 AN/762)
[2] ICAO Convention on International Civil Aviation, Annex 10, Volumes I to V ,
Chapter 1: "Definitions”
[3] ICAO Convention on International Civil Aviation, Annex 10, Volume I,
Attachment F: "Guidance material concerning reliability and availability of radio
communications”
[4] ICAO Convention on International Civil Aviation, Annex 10, Volume I, Chapter
2.9: "Secondary power supply for communication systems”
[5] ICAO Convention on International Civil Aviation, Annex 10, Volume II, Chapter
2.2: “Telecommunication access”
[6] ICAO Convention on International Civil Aviation, Annex 10, Volume II, Chapter
3.5: "General Procedures for Recording of ATC communications”
[7] ICAO Convention on International Civil Aviation, Annex 10, Volume II, Chapter
5: "Aeronautical Mobile Voice Communications”
[8] ICAO Convention on International Civil Aviation, Annex 10, Volume III, Part II,
Chapter 4: "Aeronautical Speech Circuits”
[9] ICAO Convention on International Civil Aviation, Annex 11, Chapter 1:
"Definitions”
[10] ICAO Convention on International Civil Aviation, Annex 11, Chapter 6: "Air
Traffic Services Requirements for Communications”
[11] ICAO Convention on International Civil Aviation, Annex 5: “Units of
Measurement to be Used in Air and Ground Operations”
[12] EUROCONTROL ASM.ET1.ST18.1000-REP-01-00: "Guidelines for the
application of the ECAC Radar Separation Minima" Edition 2
[13] EUROCONTROL “Voice Communication System Procurement Guidelines”
Edition 2.0; EATM Info centre reference: 05/01/12-03
[14] EUROCONTROL: “ATS Ground Voice Network Implementation and Planning
Guidelines” Edition 1.0; EATM Info centre Reference: 05/01/12-02
[15] EUROCONTROL “ATS R2 and ATS No.5 protocol specification” Edition 1.0;
EATM Info centre Reference: 05/01/12-04
[16] EUROCONTROL “Interworking between ATS QSIG and ATS No.5 signalling
systems Edition 1.0; EATM Info centre Reference: 05/01/12-06
[17] EUROCONTROL “Interworking between ATS QSIG and ATS R2 signalling
systems” Edition 1.0; EATM Info centre Reference: 05/01/12-05
[18] EUROCONTROL Safety Regulatory Requirement (ESARR) 4 “Risk
Assessment and Mitigation in ATM”
[19] EUROCONTROL Action Plan for Air Ground Communications Safety” Ed 1.0
(05/06)
[20] EUROCONTROL iPAX/PM/DE-02 (11/04)
[21] CROBOCOM Task Force Conclusions Ed 1.0 (02/05): EUROCONTROL EATM
Info centre Reference 05/01/12-01
[22] EUROCAE ED-137 “INTEROPERABILITY STANDARDS FOR VoIP ATM
COMPONENTS, PART 2 : TELEPHONE”
[23] EUROCAE ED-23B (03/95): “Minimum Operational Performance Specification
for Airborne VHF Receiver – Transmitter operating in the Frequency Range
117.975 – 136.975 MHz”
[24] ITU-T Recommendation E.164 (1997): “The International Telecommunication
Numbering Plan
© EUROCAE, 2009
79
© EUROCAE, 2009
80
© EUROCAE, 2009
81
ANNEX B
ACRONYMS
A/C Aircraft
A/C TxRx Aircraft combined Transmitter/Receiver “Transceiver”
ACC Area Control Centre
ACD Aircraft Call indication Delay
AGC Automatic Gain Control
AGVN Air Traffic Services Ground Voice communications Network
A/G Air/Ground
AM Amplitude Modulation
ANSI American National Standards Institute
ANSP Air Navigation Service Provider
APP Approach
ARINC Aeronautical Radio Inc
ATC Air Traffic Control
ATIS Automatic Terminal Information Services
ATM Air Traffic Management
ATS Air Traffic Services
ATS-No.5 Air Traffic Services – No.5 signalling system
ATS-QSIG Air Traffic Services – Q reference point SIGnalling system
ATS-R2 Air Traffic Services – R2 signalling system
ATSU Air Traffic Services Unit
CB Central Battery
CED Call Establishment Delay
CFT Call For Tender
CLIMAX Multi-carrier Offset Transmission System
COCR Communications Operating Concept and Requirements
COMT Communications Team
CROBOCOM CROss BOrder COMmunications
CUI Calling User Identity
CWP Controller Working Position
DA Direct Access
DCCVC Direct Controller-Controller Voice Communication
DFS Deutsche Flugsicherung GmbH
DIRO Dial-In / Ring-Out
DSNA Direction des Services de la Navigation Aérienne
DSS1 Digital Subscriber Signalling No.1 (ISDN)
© EUROCAE, 2009
82
EC European Community
ECAC European Civil Aviation Conference
ECMA European Computer Manufacturers Association
E&M Earth and Mark (Ear and Mouth)
EN European Norm
ESARR EUROCONTROL Safety Regulatory Requirements
ETSI European Telecommunications Standards Institute
G/G Ground/Ground
Gnd Rx Ground Receiver
Gnd Tx Ground Transmitter
Gnd Ground
GPS Global Positioning System
GRS Ground Radio Station
GW Gateway
IA Instantaneous Access
ICAO International Civil Aviation Organization
ICCVC Instantaneous Controller-Controller Voice Communication
IDA InDirect Access
IETF Internet Engineering Task Force
IP Internet Protocol
ISDN Integrated Services Digital Network
ISO International Standards Organization
ITU-T International Telecommunication Union – Telecommunication standardization sector
OK OKay
OLDI On-line Data Interchange
© EUROCAE, 2009
83
© EUROCAE, 2009
84
TX Transmitter
X-couple Cross-Couple
© EUROCAE, 2009
85
ANNEX C
Section 6.2 of the reference document (classification General Public) includes the
following Security Requirements in an open Call For Tender (CFT):
a) The PEN SHALL be isolated from other customers’ of the Contractor (assumes
an out-sourced facility)
b) The Tenderer SHALL describe which mechanisms and measures will be
deployed to ensure that other customers of the Contractor cannot gain access
to the PEN nor see resources assigned to the PEN.
c) Any denial of service attack against the Contractor’s network resources
SHOULD not result in loss of performance or quality of service on PEN.
d) No PEN Customer traffic or routing information SHALL be divulged to any third
party.
e) All data transported over the PEN network service SHALL be delivered
unmodified.
f) The Tenderer SHALL describe which mechanisms and measures have been
deployed to prevent the duplication, deletion or modification of Customer data.
g) The Tenderer SHALL describe which mechanisms and measures have been
deployed to prevent the insertion of spoofed Customer data.
h) The Tenderer SHALL describe which mechanisms and measures have been
deployed to prevent the unauthorised recording and replay of Customer data
over the PEN.
i) The Tenderer SHALL indicate which traffic flows need to be recorded for the
purposes of PEN QoS reporting, PEN network management duties or legal
requirements.
j) The Tenderer SHALL describe whether specific transport ports and/or
communication protocols (EG ICMP) are blocked by default and whether these
can be enabled for the needs of the customer.
© EUROCAE, 2009
86
ANNEX D
© EUROCAE, 2009
87
Mode of Operation
© EUROCAE, 2009
88
Cross-Coupling Combinations
Pre-Configuration
Frequencies F1d, F2d and F3s are in a Cross-Coupled Group. F1d and F2d are in
Duplex Mode. F3s is in Simplex Mode.
© EUROCAE, 2009
89
ANNEX E
© EUROCAE, 2009