1. Service Enhancement AMHS Implementation Workshop Chennai, India 15 th – 17 th December 2008

2. List of Topics Study of Impact of Directory Services Proposed AIDC over ATN/OSI

3. Directory Services SARPs ICAO Doc 9705 Edition 3 Sub- Volume 7 –Definition of Directory for the ATN environment –Directory Object Class Specification and Attributes for Directory Service Agent (DSA) and Directory User Agent (DUA) –Directory System Schema –Directory System Protocol

4. Directory Services Guidance Material ICAO Doc 9739 –AMHS Use of Directory –Functions Name Resolution; Distribution-list (DL) Expansion; Determination of User Capabilities; Address Conversion; and Retrieval of User Certificates

5. Impact of Directory Services Use/ User of Directory –What is the functions to be used within the region? Currently there are only recommended functions by the Guidance Material. –Who are the users? Currently only AMHS is the user, but can other system be a user also.

6. Impact of Directory Services Directory Service Agent –How many DSA should be installed within the region? –Where, who should be responsible? –How? –Resource? –What about Inter-Operability?

7. Impact of Directory Services Implementation Schedule –The service should be implemented in staged manner. –Each state shall coordinate with the DSA and schedule state’s implementation timeline.

8. Impact of Directory Services Managing On-going Uses –The Directory Service should be managed and coordinated within the region. –Inter-operability between region should be taken into consideration

9. AIDC in Asia/Pacific Region There are two variants of AIDC protocols within the Asia/Pacific Region –AFTN-based AIDC Protocol: The latest version is version 3.0 which was prepared by the AIDCTF in March 2007 and proposed in the APANPIRG/18 meeting in September 2007. –ATN-based AIDC Protocol: The ATN AIDC SARPs version 2.0 was approved by ACP and published in ICAO Doc 9880.

10. AFTN AIDC Control Logic

11. ATN AIDC Control Logic

12. AFTN AIDC Architecture

13. ATN AIDC Architecture

14. Proposed Architecture Propose to use AFTN AIDC. Create a communication protocol for exchange of AFTN AIDC messages between adjacent peers. The proposed protocol should utilize the ATN/OSI infrastructure. The proposed protocol should also be compatible with the ATN/IPS infrastructure in the future

15. Proposed Architecture

16. Proposed detailed architecture MTCU & CCF AFTN Comp AFTN AIDC System ATN Comp ATN Router MTCU & CCF AFTN Comp ATN Comp VTBBAAAAAABBAAAA VTBBAIDGAABBAIDG ….VTBBAAAA……………… ….. ….AABBAAAA……………… ….. Messages exchange ATN data exchange

17. Proposed detailed architecture 3 main components –AFTN Components – Handles AFTN-related issue, such as channel sequence numbering, last received, etc. –MTCU & CCF – Converts AFTN message to corresponding ATN messages. –ATN Components – Handles ATN/OSI communication for sending/receiving messages

18. Advantages AIDC is implemented as a blocked- oriented program. Could be used in both ATN/OSI and ATN/IPS environment. ATN/IPS can be added into another component under the MTCU/CCF AFTN AIDC has been implemented by states, therefore, this approach will be easier for adoption.

19. Issues to Consider Flight Message Transfer Protocol (FMTP) –EUROCONTROL has developed a protocol to handle exchange messages between flight data processing systems in a peer-to-peer manner. This protocol is considered a replacement of OLDI protocol for AIDC purposes. –Based on TCP/IP protocol. –Limited set of messages agreed by bi-lateral agreement.

20. Thank you