AMHS Community Specification lek Gasztych ROCONTROL cember 2008, Chennai European Organisation for the Safety of Air Navigation
AMHS Community Specification Introduction ¨ Present the concept of the AMHS Community Specification development ¨ Describe the development process ¨ Present the current status of development ¨ Present the next steps 2
AMHS Community Specification Why develop a Community Specification? European Organisation for the Safety of Air Navigation
AMHS Community Specification European Commission Request ¨ EUROCONTROL is requested to assist the European Commission in the development of Community Specifications ¨ EUROCONTROL is requested to develop Specifications for the AMHS within the European Air Traffic Management Network (EATMN) 4 Request for the Development of AMHS Specifications; European Commission; 30/03/2007
AMHS Specification Essential Requirements SES interoperability Regulation (552/2004) Essential Requirements Implementing Rules Community Specifications (Voluntary Standards) 5 Drafts developed by EUROCONTROL as EC Regulations • Drawn up by the ESOs (CEN/CENELEC/ETSI) in cooperation with Eurocae on technical issues • Drawn up by EUROCONTROL on matters of operational coordination Recognized as Means of Compliance with the ER and/or IR
AMHS Specification Essential Requirements ¨ ¨ Safety ¨ Civil-military coordination ¨ Support of new concepts of operation ¨ Environmental constraints ¨ Principles governing the logical architecture ¨ Essential Requirements Seamless operation Principles governing the construction of systems Regulation (EC) No 552/2004; Annex II; Parts A&B Implementing Rules Community Specifications (Voluntary Standards) 6
AMHS Specification Essential Requirements ¨ Seamless Operation: ¨ Communication systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to achieve the required performances within a given volume of airspace or for a specific application, in particular in terms of communication processing time, integrity, availability and continuity of function. ¨ The communications network within the EATMN shall be such as to meet the requirements of quality of service, coverage and redundancy. 7 Regulation (EC) No 552/2004; Annex II, S 4 Communications systems
AMHS Specification Essential Requirements ¨ Support for new concepts of operation: ¨ Communication systems shall support the implementation of advanced, agreed and validated concepts of operation for all phases of flight. 8 Regulation (EC) No 552/2004; Annex II, S 4 Communications systems
AMHS Specification Essential Requirements ¨ Safety: ¨ ¨ In respect of appropriate ground-based systems, or parts thereof, these high levels of safety shall be enhanced by safety nets which shall be subject to agreed common performance characteristics. ¨ A harmonised set of safety requirements for the design, implementation, maintenance and operation of systems and their constituents, both for normal and degraded modes of operation, shall be defined with a view to achieving the agreed safety levels, for all phases of flight and for the entire EATMN. ¨ Systems shall be designed, built, maintained and operated, using the appropriate and validated procedures, in such a way that the tasks assigned to the control staff are compatible with human capabilities, in both the normal and degraded modes of operation, and are consistent with required safety levels. ¨ 9 Systems and operations of the EATMN shall achieve agreed high levels of safety. Agreed safety management and reporting methodologies shall be established to achieve this. Systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to be free from harmful interference in their normal operational environment. Regulation (EC) No 552/2004; Annex II, Part A: General Requirements
AMHS Specification Essential Requirements ¨ Civil-military co-ordination: ¨ The EATMN, its systems and their constituents shall support the progressive implementation of civil/military coordination, to the extent necessary for effective airspace and air traffic flow management, and the safe and efficient use of airspace by all users, through the application of the concept of the flexible use of airspace. ¨ To achieve these objectives, the EATMN, its systems and their constituents shall support the timely sharing of correct and consistent information covering all phases of flight, between civil and military parties. ¨ Account should be taken of national security requirements. 10 Regulation (EC) No 552/2004; Annex II, Part A: General Requirements
AMHS Specification Essential Requirements ¨ Environmental constraints: ¨ Systems and operations of the EATMN shall take into account the need to minimise environmental impact in accordance with Community legislation. 11 Regulation (EC) No 552/2004; Annex II, Part A: General Requirements
AMHS Specification Essential Requirements ¨ Principles governing the logical architecture of systems: ¨ Systems shall be designed and progressively integrated with the objective of achieving a coherent and increasingly harmonised, evolutionary and validated logical architecture within the EATMN. 12 Regulation (EC) No 552/2004; Annex II, Part A: General Requirements
AMHS Specification Essential Requirements ¨ Principles governing the construction of systems: ¨ Systems shall be designed, built and maintained on the grounds of sound engineering principles, in particular those relating to modularity, enabling interchangeability of constituents, high availability, and redundancy and fault tolerance of critical constituents. 13 Regulation (EC) No 552/2004; Annex II, Part A: General Requirements
AMHS Community Specification AMHS Positioning - Concept Supporting new concepts of operation Enabling OIs (SESAR / SWIM) Today’s infrastructure SES Regulations 14 evolution “Communication systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to achieve the required performances. . . for a specific application, in particular in terms of communication processing time, integrity, availability and continuity of function” Future infrastructure AMHS CS Presumption of compliance
AMHS Community Specification The Development Process European Organisation for the Safety of Air Navigation
AMHS Specification CS Development Process European Commission Request Initial Plan Specification Approach Step 1 Stakeholder soundings Stakeholder workshop to present options Step 2 CS Development Formal consultation Step 3 Summary of Responses CS update Eurocontrol support 16 Final Specification
AMHS Community Specification Review Stage European Commission Request Document review complete Initial Plan Updates and further reviews Initial Plan Contributions to the Review Group from ANSPs and industry Stakeholder discussion Step 1 Options Workshop Option 2 Questionnaire Step 2 17 CS Development Drafting Review Draft AMHS Spec
AMHS Community Specification AMHS CS Proposed Technical Content European Organisation for the Safety of Air Navigation
AMHS Community Specification AMHS Positioning - Messaging AFTN header Recording Binary content Extended message size Use of TCP/IP Basic ATSMHS ISPs EUR Profile Extended ATSMHS Security Use of Directory 19 X. 400 MHS Base Standards
AMHS Community Specification Document Structure u u Chapters in main body provide contextual guidance and point to the self contained annexes with normative requirements u Chapter 1 contains introductory material describing the purpose and scope of the specification u Chapter 2 describes the basic level of interoperability for AMHS u Chapter 3 describes the introduction to Directory systems and procedures u Chapter 4 describes the Security issues u 20 Specification is organised as a number of chapters and annexes Chapter 5 describes a suggested Security mechanism and procedures to support the Extended ATSMHS
AMHS Community Specification Document Structure u u Chapter 7 describes some of the transition and coexistence issues u Chapter 8 addresses traceability between the means of compliance in the AMHS CS and Single European Sky essential requirements u Chapter 9 describes the procedures for maintaining and updating the AMHS CS u 21 Chapter 6 describes additional requirements relating to implementation options, testing, and validation Chapter 10 contains a list of documents
AMHS Community Specification Document Structure u Annex A (normative) contains detailed requirements for the Air Traffic Services (ATS) Message Handling functionality at the level of the Basic ATSMHS. u Annex B (normative) contains detailed requirements for the ATS Message Handling functionality at the Extended ATSMHS level of service, requiring support of Functional Groups (FG) for the Basic ATSMHS (Basic FG), use of file transfer body parts for binary data exchange (FTBP FG), use of interpersonal messaging heading extensions (IHE FG) and use of Directory (DIR FG) Support of AMHS Security (SEC FG) is foreseen in the future u u 22 Annex C (normative) contains detailed requirements for Directory systems to support the DIR FG of the Extended ATSMHS Annex D (informative) indicates high level requirements for security mechanisms to support the SEC FG of the Extended ATSMHS
AMHS Community Specification Basic level of interoperability for AMHS u u ICAO Annex 10 is being updated to include ATN operation over the Internet Protocol Suite (ATN/IPS) u Both Doc 9880 and the ICAO EUR AMHS Manual (Doc 020) specify AMHS end systems making use of TCP/IP lower layers through an RFC 1006 interface for IPv 4 or RFC 2126 for IPv 6 u During transition phase, interoperability with legacy AFTN/CIDIN is achieved by the use of AFTN/AMHS gateways as specified in Doc 9880 u 23 The detailed technical provision for the AMHS are specified in ICAO doc 9880 Interoperability with Military AFTN usage can be achieved by using AFTN/AMHS Gateways or use of civil UAs. (Future MMHS/AMHS gateway could be envisaged – out of scope of this AMHS CS)
AMHS Community Specification Extended AMHS functionality u Use of File Transfer Body Parts (FTBP). This functional group enables the transfer of binary data between direct AMHS users u Use of IPM Heading Extensions (IHE). This functional group uses standard message fields instead of the AMHS-specific ATS Message Header which is required in the Basic ATSMHS u u 24 AMHS Security (SEC). This functional group enables support of the AMHS security policy, providing message origin authentication and content integrity assurance between direct AMHS users Use of Directory (DIR). This functional group enables support of the ATN Directory through the use of a DUA included in the AMHS End System
AMHS Community Specification Directory European Organisation for the Safety of Air Navigation
AMHS Community Specification General Directory Architecture DUA Chaining / Shadowing DUA DAP DSA 1 DSP, DISP 26 private data DAP DUA DIB from DSA 2 Country 1 DSA 2 from DSA 1 Country 2
AMHS Community Specification Directory - General Requirements (1) u Support of the AMHS Directory (DIR) functional group is required for full conformance to the Extended AMHS u DIR – Directory services allow user to obtain directory information about user application and services u DIR is composed of Directory Information Base (DIB) Directory System Agent (DSA) and Directory User Agent (DUA) u DIB is organised into a tree shaped hierarchy – Directory information Tree (DIT) u Each DSA shall: u Have a common schema for data being replicated u Support a common directory replication protocol u u 27 Each DSA shall implement Directory System Protocol (DSP) to allow chaining operation Each DSA shall implement Directory Information Shadowing Protocol (DISP) to support data shadowing
AMHS Community Specification Directory - General Requirements (2) u u Each DSA shall allow additional directory object classes to be included to allow the use of this service by other applications u Each DSA shall implement Directory Access Protocol (DAP) u 28 Each DSA shall support the bind operation using a minimum simple authentication for DAP, DSP and DISP as defined in the base standards The DSA may implement other access protocol based on LDAP v 3 or a proprietary protocol as a local issue without impact on interoperability
AMHS Community Specification Directory - Specific Requirements u Each Directory implementation shall support: u Name resolution u Distribution list (DL) expansion and management u Determination of user capabilities u AFTN/AMHS address conversion and publication u Retrieval of security certificates and CRLs u The Directory information tree exported by Border DSAs shall conform to the DIT structure defined in ICAO technical provisions for ATN Directory Services u Each directory implementation should support: u AMHS systems management information u Address book u Support for system configuration (MTA, Gateway) 29
AMHS Community Specification Initial Directory Architecture ANSP DMD Europe Directory Management Domain DSA External Directory Management Domains Country border DSA Manual Sync. AIRAC Cycle Ext. Border DSA AIRAC Cycle Europe AMC ANSP DMD AIRAC Cycle DSA Country border DSA ANSP DMD DSA 30
AMHS Community Specification Final Directory Architecture ANSP DMD Europe Directory Management Domain DSA External Directory Management Domains Country border DSA Ext. Border Sync. process DSA DISP Europe DSA ANSP DMD DISP DSA Country border DSA DISP or DSP Country border DSA ANSP DMD DSA 31
AMHS Community Specification Security European Organisation for the Safety of Air Navigation
AMHS Community Specification Security u It is recognised that the provision of AMHS Security services is not as advanced as other elements of the Extended ATSMHS u The security requirements in Annex D are to be considered as advisory indications of the evolutionary direction 33
AMHS Community Specification End-to-End Message Security Extended ATS MHS X. 400 envelope S 0 Security Class • Content integrity • Origin Authentication • Proof of delivery 34 Message content to be protected Message Origin Authentication Check Originator’s certificate (optional) Message hash, encrypted with private key Public key, signed by trusted CA Passed transparently through Message Transfer Service
AMHS Community Specification End-to-End Message Security Certification Authorities Issues certificates State A CA Name Public key State B CA State C CA Message signed by an originator in State A with that user’s private key can be verified by recipient in State C using the originator’s public key PKI enables recipient to trust that the public key is authentic Signed by CA Public Key Infrastructure (PKI) u u 35 Secure security key distribution Trust between security domains (States)
AMHS Community Specification Global AMHS Architecture including CA 36
AMHS Community Specification Security - General Requirements u Support of the AMHS Security (SEC) functional group is required for full conformance to the Extended AMHS u An AMHS implementation shall include protocol provisions as necessary to comply with the local security policy relating to aeronautical data access and interchange. u Implementations shall be conformant with the Extended AMHS and in particular the security aspects of ATN relevant for ground communication u The Extended AMHS explicitly provides the following security services between ATS Message User Agents: u u Message sequence integrity u Message origin authentication u 37 Content integrity Proof of delivery (when IPNs are used)
AMHS Community Specification Security - Specific Requirements (1) u u The TTP shall be conformant with the ETSI Guide EG 201 057, which defines the role and attribution of a TTP acting as a CA in a PKI u 38 Each State participating in the AMHS security scheme shall designate a Trusted Third Party (TTP) acting as a Root Certificate Authority (CA) which issues certificates and certificate revocation lists (CRLs) Each CA shall develop a Certificate Policy, conformant to the certificate policy defined in ETSI specification TS 101 456 v 1. 4. 3, that defines the creation, management and use of public key certificates that they issue
AMHS Community Specification Security - Specific Requirements (2) u u 39 The Certificate Policy and Certificate Practice Statement shall be aligned with the framework presented in RFC 3647 “Internet X. 509 Public Key Infrastructure Certificate Policy and Certification Practices Framework” The Certificate Policy and Certificate Practice Statements of a given State could be used by other States in establishing their trust relationships and operating policies such as cross certification
AMHS Community Specification Security - Specific Requirements (3) u u Each CA should distribute public key certificates and CRL using Directory Services u The cryptographic signing and hashing functions and parameter settings shall be conformant with ATN Security provisions (Elliptic Curve Cryptography – ECDSA) u 40 Each CA shall give simple access to the public certificate and CRL repository in its own domain The general certificate format used for ATN PKI certificates in Europe shall be conformant with the X. 509 Format with parameters defined in chapter 8. 4. 3 of the ATN Security provisions
AMHS Community Specification European PKI – Initial Phase CA ANSP j CA ANSP i European Community CA ANSP l CA ANSP k CA ANSP x 41
AMHS Community Specification Final European Public Key Infrastructure CA ANSP x CA CA ANSP i European Community ANSP j EU CA CA CA ANSP l ANSP k CA ANSP x 42
AMHS Community Specification The Next Steps for AMHS CS European Organisation for the Safety of Air Navigation
AMHS Community Specification The Next Steps – Review Stage European Commission Request Initial Plan Stakeholder discussion Step 1 Options Workshop Option 2 Questionnaire Step 2 CS Development Drafting Review Draft AMHS Spec Formal Consultation Step 3 Formal Workshop Summary of Responses AMHS Specification 44 Final Report
AMHS Community Specification The Next Steps – Formal Consultation draft of AMHS Specification to be issued in January 2009 Formal Workshop after April 2009 EUROCONTROL AMHS Specification send to European Commission by mid 2009 Formal Consultation Step 3 Formal Workshop Summary of Responses AMHS Specification 45 Final Report
AMHS Community Specification The End European Organisation for the Safety of Air Navigation
Скачать презентацию AMHS Community Specification lek Gasztych ROCONTROL cember 2008
5f47140f27ae9fd034e3f35f15f44c5d.ppt