You are on page 1of 22

ATNS-3/2 International Civil Aviation Organization ATN Seminar and Third ATN Transition Task Force Meeting Singapore,

26-30 March 2001

Agenda Item: 3 ATN Ground-Ground Application

AIDC, ATS INTERFACILITY DATA COMMUNICATION


(Presented by Tetsuo Mizoguchi)

AIDC; ATS Interfacility Data Communication

ATN Seminor
Singapore March, 26-27, 2001

Tetsuo MIZOGUCHI (Japan)

Japan Civil Aviation Bureau


1

Table of Contents
AIDC :Scope, Functions AIDC Standards;
What are Standards? Why regional group needs Standards? Message Sets, Underlying communication infrastructures

ATN AIDC SARPs


Communication Protocols Associating Peer AIDCs Sending/Receiving Messages Remarks on AIDC Implementations Comparing APANPIRG AIDC ICD and ATN AIDC SARPs Transition Issue Coordinated/ Mutual Agreements between ATS Units/CAAs

Japan Civil Aviation Bureau


2

AIDC Scope, Functions


AIDC; Information exchange between ATS Units in support of ATS functions AIDC Functions; Notification, Coordination, and Transfer of Control.

FIR

FIR

ATS Unit

ATS Unit

AIDC

Japan Civil Aviation Bureau


3

AIDC Functions for one Flight


Notify Phase Coordinate Phase Transfer Phase
Time

Notification Message Coordination Message Transfer of Control Message

FIR Boundary

C(Controlling)ATS Unit
Japan Civil Aviation Bureau

R(receiving)ATS Unit
4

More than One Flight under AIDC ; a snapshot

Flight 4
Notify Phase

Flight 3

Flight 2

Flight 1
Transfer Phase

Coordinate Phase

Flight 1 Flight 2 C-ATSU Flight 3 Flight 4

Transfer of Control Coordination Coordination

Coordination Notification Notification

Notification

FIR Boundary

Notification

Japan Civil Aviation Bureau


5

Multiple Associations (One Association per Flight)over ATSU pair


Association 1 for Flight 1 Notification Coordination Transfer of Control

Association 2 for Flight 2 Notification Coordination Transfer of Control

Association 3 for Flight 3

C-ATSU

Notification

Coordination

Transfer of Control

R-ATSU

Association 4 for Flight 4 Notification Coordination Transfer of Control

Japan Civil Aviation Bureau


6

Establishing Associations & Messaging Phases

Establish Physical Connection For Each Flight Establish Association(Logical Connection) Messaging ; Notification ; Coordination ; Transfer of Control ; End of Messaging ; Close Association
Japan Civil Aviation Bureau
7

Sending and Responding


Sending Message

Response

Two Types of Responses Application Response (Technical Response) : Message sent is validated and accepted (AppAccept) or rejected due to errors(AppError) Operational Response : e.g. acceptance (CoordianteAccept) /rejection (CoordinateReject) of trajectory as proposed by CoordinateNegotiate

Japan Civil Aviation Bureau


8

Standards of AIDC;
Why we need Standards? Standardization; Protocol and Message Format (at Interface)

ATS Unit

Message

ATS Unit

ATS Unit

Message

Japan Civil Aviation Bureau


9

Protocol; Confirmed/Unconfirmed Services in Communication


Request Unconfirmed Service Indication

Request

Confirmed Service Indication

Confirmation Response

Japan Civil Aviation Bureau


1 0

Protocol; Application Response


User Logical Confirmation as Application Response
Request
Unconfirmed Service

Indication User Logical Confirmation Request

Unconfirmed Service

Indication C-ATSU Message

R-ATSU

Japan Civil Aviation Bureau


1 1

Communication Protocol (Abstract) State Machine


Protocol Machine State Transition
Event6 State 1 Event1 State 2 Event2 State 3 Event3 Event4 State 4 Event5 Event4 State 4 Event5 State 3 Event3 State 2 Event2 Event6 State 1 Event1

C-ATSU Message

R-ATSU

Japan Civil Aviation Bureau


1 2

ATN AIDC SARPs; Associating Peer AIDCs (1)


AIDC User AIDC User Interface AIDC User

AIDC Association
AIDC Messaging

AIDC Association
AIDC Messaging

ATN Communication Service Interface ATN Communication Infrastructure C-ATSU R-ATSU Message

Japan Civil Aviation Bureau


1 3

ATN AIDC SARPs; Associating Peer AIDCs(2)


AIDC USER STA0 IDLE NotifyRequest STA1 ASSOCIATION PENDING STA2 DATA TRANSFER End Request STA3 RELEASE PENDING
Japan Civil Aviation Bureau
1 4

Comm.Service

Association Establishing Association Confirm

C-ATSU

MESSAGING

ATN AIDC SARPs ; Sending/ Receiving Messages(1) Messages (APANPIRG Equivalent Message Subset)
Notification Notify Coordination Coordinate-Start Coordinate-Negotiate Coordinate-End Transfer of Control Transfer-Control (Confirmed Service) Asynchronous Information Transfer Termination End ( Cancel ) User-Abort Provider(Comm. Service)-Abort
Japan Civil Aviation Bureau
1 5

ATN AIDC SARPs ; Sending/ Receiving Messages(2)


C-ATSU AIDC

States & State Transitions for Messaging(Per Flight)


IDLE NOTIFY

R-ATSU AIDC

Notify ULC* CoordinateStart ULC*

Notify CoordinateStar t
RE-NEGOTIATING NEGOTIATING

CoordinateEnd ULC*
COORDINATED

TransferStart
TRANSFERRING

TransferStart ULC*

TransferAccepted ULC*
BACKWARD COORDINATING TRANSFERRED

*ULC; User Logical Confirmation


1 6

Japan Civil Aviation Bureau

ATN AIDC SARPs ; Sending/ Receiving Messages(3)


Confirmed Service; Transfer of Control
COORDINATED Sending TransferControl
Sending TransferControl ULC

COORDINATED

TRANSFERRING Confirmation

TRANSFERRING
Sending TransferControlAccept

Sending TransferControlAccept ULC TRANSFERRED C-ATSU Message TRANSFERRED R-ATSU

Japan Civil Aviation Bureau


1 7

Remarks on AIDC Implementation(1) ;AIDC Standards


Comparing APANPIRG AIDC ICD and ATN AIDC SARPs Use of AFTN vs ATN and Use of ODF; Optional Data Fields, in AFTN Header

ODF

ODF2

ODF3

ODF4

ODF5

CRC Time Stamp Message Reference

Use of ACSE(edition 2/3) in ATN ACSE(Ed 2) ACSE(Ed 3) Connection Per Flight

Message ID ACSE(Ed 2) ACSE(Ed 3)

Connection ATS Units Pair

Japan Civil Aviation Bureau


1 8

Remarks on AIDC Implementation(2) ;AIDC Standards Difference


More Rulings in AIDC for SARPs AIDC Implementation Most of Checking in Application for APANPIRG AIDC Implementation SARPs AIDC Application SARPs AIDC Flight Phase Ruling Message Sequence Ruling Flight Phase Ruling Message Sequence Ruling APANPIRG AIDC Application

Interacitve Dialogue Communication


Japan Civil Aviation Bureau

Messaging(Stored-Forward) Communication;AFTN

1 9

Remarks on AIDC Implementation(3); Transition


Transition Issues
From APANPIRG ICD Based AIDC Implementation To ATN SARPs Based AIDC Implementation

No impacts to Controller Interface are desirable AIDC User could be an application process, possibly mapping between Controller Interface and AIDC User Interface would be needed Message Format and Contents Differences
Message Type; No Surveillance Data Transfer in SARPs Message Parameters; Variables, Ranges, Resolutions; No many but some

Communication Performance, may not be same


Data Integrity Delay Availability

Communication Infrastructures
APANPIRG AIDC via AFTN/ATN Gateway may not be a transition solution Interoperability between APANPIRG AIDC over AFTN and SARPs AIDC over AMHS via AFTN/AMHS Gateway or AIDC adaptor, or New development needed

Japan Civil Aviation Bureau


2 0

Remarks on AIDC Implementation(4); Mutual Coordination


Coordinated Development with Other Applications, e.g. CPDLC Mutual Agreements between ATS Units/CAAs Agreement over Message Set to be used Agreement over flight related conditions dictating the invocation of AIDC services Agreement over the timing associated with the AIDC services AIDC Services Mutual Agreement Message Set Service Invocation Conditions Timing

Japan Civil Aviation Bureau


2 1