2 INITIAL SITUATIONAt 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 configurationLAYER 7: Agree the AMHS configurationAgree the network test that will be performed.Agree the AMHS test that will be performed.TEST PHASEPerform some network test to assure the network connectivity.Perform the AMHS trialsMIGRATION PHASEDefine coordinated procedures to carry out the migration in a coherent and compatible manner.
4 CONTACTs AMONG ANSPsContact 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 REGIONONDA-MOROCCOENNA-ALGERIASAM REGIONFAA-ARGENTINAEUR REGIONAENA - SPAINDSNA FRANCENAV- PORTUGAL
5 AENA- FAA ARGENTINA PROGRESS DESIGN PHASEIdentify the physical infrastructure that will be used DONEIP NATIONAL DATA NETWORSCAFSAT INFRAESTRUCTUREAgree the network configuration DONEIP NATIONAL DATA NETWORS DONECAFSAT INFRAESTRUCTURE DONEAgree the AMHS configuration ON GOINGAgree the AMHS tests that will be performed DONETEST PHASEPerform some network test to assure the network connectivity PARTIALLY DONE.IP NATIONAL DATA NETWORS DONE (9th week)Perform AMHS trials PENDINGMIGRATION PHASEDefine coordinated procedures to carry out the migration in a coherent and compatible manner PENDING
6 AENA(SPAIN)- FAA (ARGENTINA) PHYSICAL INFRASTRUCTURE AMHS testREDAN WANAMHS operationalREDAN IPBORDER ROUTER testBORDER ROUTER operationalIPv6/FRIPv4C A F S A TNAT-PTFR switchFR infrastructureIP infrastructureEspaña
7 AENA ( SPAIN)- NAV(PORTUGAL) PROGRESS DESIGN PHASEIdentify the physical infrastructure that will be used DONETwo 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 NETWORSTDM COMMON CAFSAT INFRAESTRUCTUREAgree the AMHS configuration -> DONEAgree 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 PHASEPerform network tests to assure the network connectivity ON GOING.IP NATIONAL DATA NETWORS ON GOINGPENs INFRAESTRUCTURE Not yet Available.Perform AMHS trials PARTIALLY DONEThree different phases defined.First phase: Performing AMHS trials in a local environment. DONESecond 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 PHASEDefine 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/R2QSIG/R2QSIG/R2QSIG/R2Data applications:OLDI, AMHS, RADAR
10 AENA(SPAIN)- NAV (PORTUGAL) LONG TERM PHYSICAL INFRASTRUCTURE PENSBARCELONARINAL IPREDAN IPLISBOAAEFMPMADRIDREGIONALNETWORKFAROSEVILLA
11 AENA (SPAIN)- DSNA (FRANCE)- ONDA (MOROCCO)-ENNA (ALGERIA) PROGRESS DESIGN PHASEIdentify the physical infrastructure that will be used DONEAgree the network configuration DONEAgree the AMHS configuration PARTIALLY DONEAgree the AMHS test that will be performed DONETEST PHASE AGREEDEDPerform network test to assure the network connectivityPerform AMHS trialsMIGRATION PHASE AGREEDEDDefine 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 INFRASTRUCTUREPENSBARCELONAPotentially ATHISPotentially Aix-en ProvenceRENARREDAN IPAEFMPMADRIDREGIONALPotentially BOURDEOSNETWORKBARCELONA
13 AENA(SPAIN)- ONDA (MOROCCO) PHYSICAL INFRASTRUCTURE AMHS testREDAN WANAMHS operationalREDAN IPBORDER ROUTER testBORDER ROUTER operationalIPv6/FRIPv4C A F S A TNAT-PTFR switchF.R. infrastructureIP infrastructureSpain
15 Low level protocolsAENA (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 AddressingAENA (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”.StateAMHS Address SpecificationNameNationality LettersCountry nameADMD namePRMD nameAddress schemeOrganisation name (CAAS only *)AlgeriaDAXXICAOCAASDAAACanary Islands (Spain)GCAENAsee Table AENAFranceLFFRANCEsee Table FRANCEMoroccoGMGMMMPortugal (Madeira & Açores)LPsee TableSpainGELE
17 AMHS RoutingAENA (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 TestsAENA (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 CONFIGURATIONTCP/IP AMHS ParametersItemRECOMENDED VALUEREFERENCEIP AddresstbdAppendix C Configuration ParametersTCP-port102X.400 and Upper Layer ParametersItemRECOMENDED VALUEREFERENCEMTA NameMTA -Location Indicator of the MTA location - specific number of the MTA8.2.2 Default values for international MTA namesMTA PasswordICAO- Location Indicator of the MTA location - specific number of the MTA8.2.3 Default values for international MTA passwordsPSAPnot used notAppendix F3.2 Configuration Upper LayersSSAPProtocol typeX.400/1988ConnectionpermanentDynamic5.2 General requirements5.2.5.Maximum number of simultaneous P1 associationsIncomingOutgoing55.2 General requirements.5.2.2.Dialogue modeType of associationsmonologuetwo-way-alternateMonologueAppendix BJ.1 IntroductionMinimum message size support2MbytesF.2.4.3