1. IP and AMHS TRIALS- PLANIFICATION STRATEGY

2. INITIAL SITUATION
At the end of 2008, it was initiated an interoperability planning test between Aena and new ANSPs that have migrated to AMHS or that are planning to migrate to AMHS in a sort time frame.
First action was the identification of the IP infrastructure to be used.

3. GENERAL STEPS DESIGN PHASE
LAYER 1: Identify the physical infrastructure that will be used.
LAYER 3: Agree the network configuration
LAYER 7: Agree the AMHS configuration
Agree the network test that will be performed.
Agree the AMHS test that will be performed.
TEST PHASE
Perform some network test to assure the network connectivity.
Perform the AMHS trials
MIGRATION PHASE
Define coordinated procedures to carry out the migration in a coherent and compatible manner.

4. CONTACTs AMONG ANSPs
Contact among different ANSP have been initialized in two different forums. In the EUR-AFI Regions this project was materialized in a Task- Force, under the umbrella of the AEFMP group ( AEFMP IP-TF).
In the case of the Aena (Spain)-FAA(Argentina) initiative, it has born thanks to the good relations and understanding between both organizations.
The list of ANSP that have contacts in order to perform trials in short or medium term are:
AFI REGION
ONDA-MOROCCO
ENNA-ALGERIA
SAM REGION
FAA-ARGENTINA
EUR REGION
AENA - SPAIN
DSNA FRANCE
NAV- PORTUGAL

5. AENA- FAA ARGENTINA PROGRESS
DESIGN PHASE
Identify the physical infrastructure that will be used  DONE
IP NATIONAL DATA NETWORS
CAFSAT INFRAESTRUCTURE
Agree the network configuration  DONE
IP NATIONAL DATA NETWORS  DONE
CAFSAT INFRAESTRUCTURE  DONE
Agree the AMHS configuration  ON GOING
Agree the AMHS tests that will be performed  DONE
TEST PHASE
Perform some network test to assure the network connectivity  PARTIALLY DONE.
IP NATIONAL DATA NETWORS  DONE (9th week)
Perform AMHS trials  PENDING
MIGRATION PHASE
Define coordinated procedures to carry out the migration in a coherent and compatible manner  PENDING

6. AENA(SPAIN)- FAA (ARGENTINA) PHYSICAL INFRASTRUCTURE
AMHS test
REDAN WAN
AMHS operational
REDAN IP
BORDER ROUTER test
BORDER ROUTER operational
IPv6/FR
IPv4
C A F S A T
NAT-PT
FR switch
FR infrastructure
IP infrastructure
España

7. AENA ( SPAIN)- NAV(PORTUGAL) PROGRESS
DESIGN PHASE
Identify the physical infrastructure that will be used  DONE
Two options depending on the time frame.
Short Term Solution. Connecting IP NATIONAL DATA NETWORS using a TDMs COMMON INFRASTRUCTURE.  PARTIALLY DONE.
Long Term Solution. Using the PENs infrastructure.  PARTIALLY DONE.
Agree the network configuration -> ON GOING under the umbrella of the AEFMP IP Task Force (*)
IP NATIONAL DATA NETWORS
TDM COMMON CAFSAT INFRAESTRUCTURE
Agree the AMHS configuration -> DONE
Agree the AMHS test that will be performed -> DONE
(*) AEFMP is a Regional Plan composed of: Algeria, Spain, France, Morocco and Portugal.

8. AENA (SPAIN)- NAV (PORTUGAL) PROGRESS
TEST PHASE
Perform network tests to assure the network connectivity  ON GOING.
IP NATIONAL DATA NETWORS  ON GOING
PENs INFRAESTRUCTURE  Not yet Available.
Perform AMHS trials  PARTIALLY DONE
Three different phases defined.
First phase: Performing AMHS trials in a local environment.  DONE
Second phase: Performing AMHS trials using the interconnection of both national IP networks, Medium term solution  PENDING.
Third phase: Performing AMHS trials using the PENs infrastructure  PENDING.
MIGRATION PHASE
Define coordinated procedures to carry out the migration in a coherent and compatible manner  PARTIALLY DONE

9. AENA(SPAIN)- NAV (PORTUGAL) SHORT TERM PHYSICAL INFRASTRUCTURE
QSIG/R2
QSIG/R2
QSIG/R2
QSIG/R2
Data applications:
OLDI, AMHS, RADAR

10. AENA(SPAIN)- NAV (PORTUGAL) LONG TERM PHYSICAL INFRASTRUCTURE
PENS
BARCELONA
RINAL IP
REDAN IP
LISBOA
AEFMP
MADRID
REGIONAL
NETWORK
FARO
SEVILLA

11. AENA (SPAIN)- DSNA (FRANCE)- ONDA (MOROCCO)-ENNA (ALGERIA) PROGRESS
DESIGN PHASE
Identify the physical infrastructure that will be used  DONE
Agree the network configuration  DONE
Agree the AMHS configuration  PARTIALLY DONE
Agree the AMHS test that will be performed  DONE
TEST PHASE  AGREEDED
Perform network test to assure the network connectivity
Perform AMHS trials
MIGRATION PHASE  AGREEDED
Define coordinated procedures to carry out the migration in a coherent and compatible manner.

12. Potentially Aix-en Provence
AENA(SPAIN)- DSNA (FRANCE) MEDIUM AND LONG TERM PHYSICAL INFRASTRUCTURE
PENS
BARCELONA
Potentially ATHIS
Potentially Aix-en Provence
RENAR
REDAN IP
AEFMP
MADRID
REGIONAL
Potentially BOURDEOS
NETWORK
BARCELONA

13. AENA(SPAIN)- ONDA (MOROCCO) PHYSICAL INFRASTRUCTURE
AMHS test
REDAN WAN
AMHS operational
REDAN IP
BORDER ROUTER test
BORDER ROUTER operational
IPv6/FR
IPv4
C A F S A T
NAT-PT
FR switch
F.R. infrastructure
IP infrastructure
Spain

14. AENA(SPAIN)- ENNA (ARGELIA) PHYSICAL INFRASTRUCTURE
AMHS test
REDAN WAN
AMHS operational
REDAN IP
BORDER ROUTER test
BORDER ROUTER operational
IPv6/FR
IPv4
NAT-PT
Spain
64kbps LL
Algeria

15. Low level protocols
AENA (SPAIN)- DSNA (FRANCE)- ONDA (MOROCCO)-ENNA (ALGERIA)- NAV (PORTUGAL)
1.The low level protocol used in the communications stack by the members of the AEFMP group will be TCP/IP.
2. IPv4 protocol will be used by the application because it is the commercialized version by the COTs providers nevertheless the international IP connectivity will be made using IPv6.
3. ONDA and ENNA have formally requested to Eurocontrol a range of IPv6 address.
ONDA has been assigned an operational IPv6 address and a Pre-operational IPv6 address (for tests).
5. The connectivity solution will be partially supported by PENs, in long term for those countries where the PENs infrastructure will be available. In short and in medium term bilateral agreements will be done to performing AMHS trials.
Be aware about the amount of traffic exchanged and use this data for estimating the network resources required by the AMHS.

16. AMHS Address Specification Organisation name (CAAS only *)
AMHS Addressing
AENA (SPAIN)- DSNA (FRANCE)- ONDA (MOROCCO)-ENNA (ALGERIA)- NAV (PORTUGAL)
1. Is recommended to adopt the CAAS addressing scheme by the AEFMP members.
2. Is agreed to use the AMC facility in support of the AMHS implementation, according with the EANPG conclusion.
Use the information of how to announce minor and mayor changes in the AMHS addressing scheme that is named “Outline of proposed procedures for coordination between ICAO AMHS MD Register and AMC” included in the doc. “11WP27 - Inter-regional co-ordination activities”.
State
AMHS Address Specification
Name
Nationality Letters
Country name
ADMD name
PRMD name
Address scheme
Organisation name (CAAS only *)
Algeria DA XX
ICAO
CAAS
DAAA
Canary Islands (Spain) GC
AENA
see Table AENA
France LF
FRANCE
see Table FRANCE
Morocco GM
GMMM
Portugal (Madeira & Açores) LP
see Table
Spain GE LE

17. AMHS Routing
AENA (SPAIN)- DSNA (FRANCE)- ONDA (MOROCCO)-ENNA (ALGERIA) - NAV (PORTUGAL)
1.The short term proposal is to implement, as minimum, the current CIDIN routing/topology.
2.According with the current PENs implementation, a fully meshed topology will be possible in the Eur Region in medium term. As consequence, the topology among some members of the AEFMP will be “theoretically” fully meshed, in medium term.
3.In long term a different topology can be implemented among the AEFMP’s members. In order to choose the best one, it is needed to be aware about the real exchanged traffic.

18. Tests
AENA (SPAIN)- DSNA (FRANCE)- ONDA (MOROCCO)-ENNA (ALGERIA) - NAV (PORTUGAL)
1. A network infrastructure has to be agreed to perform the AMHS trials.
2. It is strongly recommended to perform interoperability trials as are collected in the Eur AMHS Manual, appendix E (bilateral and trilateral, if possible).
3. Additionally some conformance test could be performed, the test cases could be expanded based on bilateral agreements.
AMHS CONFIGURATION
TCP/IP AMHS Parameters
Item
RECOMENDED VALUE
REFERENCE
IP Address
tbd
Appendix C Configuration Parameters
TCP-port
102
X.400 and Upper Layer Parameters
Item
RECOMENDED VALUE
REFERENCE
MTA Name
MTA -Location Indicator of the MTA location - specific number of the MTA
8.2.2 Default values for international MTA names
MTA Password
ICAO- Location Indicator of the MTA location - specific number of the MTA
8.2.3 Default values for international MTA passwords
PSAP
not used not
Appendix F
3.2 Configuration Upper Layers
SSAP
Protocol type
X.400/1988
Connection
permanent
Dynamic
5.2 General requirements
5.2.5.
Maximum number of simultaneous P1 associations
Incoming
Outgoing 5
5.2 General requirements.
5.2.2.
Dialogue mode
Type of associations
monologue
two-way-alternate
Monologue
Appendix B
J.1 Introduction
Minimum message size support
2Mbytes
F.2.4.3

19. Thanks for your attention