Safety Management System Implementation
Download
Report
Transcript Safety Management System Implementation
Service Enhancement
AMHS Implementation Workshop
Chennai, India
15th – 17th December 2008
List of Topics
• Study of Impact of Directory Services
• Proposed AIDC over ATN/OSI
Directory Services
• SARPs ICAO Doc 9705 Edition 3 SubVolume 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
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
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.
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?
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.
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
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.
AFTN AIDC Control Logic
ATN AIDC Control Logic
AFTN AIDC Architecture
A ID C
App
A ID C
App
T e xt
M e ssa g e s
T e xt
M e ssa g e s
AFT N
S e r vice
AF T N
S e r vice
AFTN
S w it ch
AFTN
S w it ch
AFTN
S w it ch
A e r o n a u tica l F ixe d
T e le co m m u n ica tio n
N e tw o r k
( A F T N)
ATN AIDC Architecture
AIDC
App
CF
ASN.1
Defined
Messages
AIDC
App
AIDC
ASE
CF
AIDC
ASE
ACSE
ACSE
FB Pres
FB Session
TP4
CLNP
FB Pres
FB Session
TP4
CLNP
ATN
RTR
ATN
RTR
ATN
RTR
Aeronautical
TelecommunicationS
Network
(ATN)
ASN.1
Defined
Messages
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
Proposed Architecture
Text
Messages
AIDC
App
AIDC
App
TP4
CLNP
TP4
CLNP
ATN
RTR
ATN
RTR
ATN
RTR
Aeronautical
TelecommunicationS
Network
(ATN)
Text
Messages
Proposed detailed architecture
AFTN AIDC
System
AFTN AIDC
System
Messages exchange
VTBBAAAA
AABBAAAA
AFTN
Comp
VTBBAIDG
AABBAIDG
MTCU &
CCF
AFTN
Comp
MTCU &
CCF
….VTBBAAAA……………… ATN Comp
…..
ATN Comp
ATN Router
….AABBAAAA………………
…..
ATN Router
ATN data exchange
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
Advantages
• AIDC is implemented as a blockedoriented 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.
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.
Thank you