ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
AERONAUTICAL COMMUNICATIONS PANEL (ACP)
WORKING GROUP N – NETWORKING
SUBGROUP N3 – ATN GROUND–GROUND APPLICATIONS
9th MEETING – BRUSSELS, BELGIUM, 26th–30th JUNE 2006
Issues regarding AIDC as a result of OPLINKP1
Prepared by Chanyut PHRUKKUMWONG
Summary
The OPLINKP1 meeting has amended a number of documents. This also includes
Manual of Air Traffic Services Data Link Applications (Doc 9694) and PANS-ATM
(Doc 4444). As a result, existing AIDC protocols may have to be amended to make
them in line with OPLINKP1. This paper describes the comparison between
OPLINKP1’s AIDC and Doc 9705’s AIDC and identifies the points where the changes
in Doc 9705’s AIDC may be required.
1. Introduction
The OPLINKP1 has amended a number of documents regarding datalinks. This includes, for
instance, Annex 2, Annex 4, Annex 6, Annex 10, Annex 11, Annex 15, PANS-ABC (Doc
8400), PANS-ATM (Doc 4444), Manual of Air Traffic Services Data Link Applications (Doc
9694). Doc 4444 and Doc 9694 are the documents that show the details of the AIDC
protocol.
Some distinctions between OPLINKP1’s AIDC and Doc 9705’s AIDC exist. Hence, Doc
9705’s AIDC is required to be slightly changed in order to conform to the OPLINKP1’s AIDC.
Apart from the distinctions that exist between OPLINKP1’s AIDC and Doc 9705’s AIDC,
OPLINKP1’s Doc 9694 and OPLINKP1’s Doc 4444 do also have some discrepancies in
explaining the same AIDC concept.
This paper mainly identifies the points where Doc 9705’s AIDC may require to be changed.
Other minor discrepancies between OPLINKP1’s Doc 9694 and OPLINKP1’s Doc 4444 are
also pointed out.
2. References
[1]
[2]
[3]
[4]
OPLINKP1’s Doc 9694
OPLINKP1’s Doc 4444
Doc 9705, 3rd edition
Doc 9739, 2nd edition
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
[5] Asia/Pacific Regional Interface Control Document (ICD) for ATS Interfacility Data
Communication (AIDC), Version 2.0, August 2003.
3. Existing AIDC message sets in [1], [2] and [3]
[4444.1] --- [2]’s AIDC message set (section 11.4.2.5) = 22 messages
Notify
Coordinate Initial
Coordinate Negotiate
Coordinate Accept
Coordinate Reject
Coordinate Cancel
Coordinate Update
Coordinate Standby
Transfer Initiate
Transfer Conditions Proposal
Transfer Conditions Accept
Transfer Communication Request
Transfer Communication
Transfer Communication Assume
Transfer Control
Transfer Control Assume
General Point
General Executive Data
Free Text Emergency
Free Text General
Application Accept
Application Reject
[4444.2] --- [2]’s AIDC message set (Appendix 6, Table A6-1) = 22 messages
Notify
Coordinate Initial
Coordinate Negotiate
Coordinate Accept
Coordinate Reject
Coordinate Cancel
Coordinate Update
Coordinate Standby
Transfer Initiate
Transfer Conditions Proposal
Transfer Conditions Accept
Transfer Communication Request
Transfer Communication
Transfer Communication Assume
Transfer Control
Transfer Control Assume
General Point
General Executive Data
Free Text Emergency
Free Text General
Application Accept
Application Reject
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
[9694.1] --- [1]’s AIDC message set (Table VI-1-B1) = 22 messages
Notify
Coordinate Initial
Coordinate Negotiate
Coordinate Accept
Coordinate Reject
Coordinate Cancel
Coordinate Update
Coordinate Standby
Transfer Initiate
Transfer Conditions Proposal
Transfer Conditions Accept
Transfer Request
Transfer Communication
Transfer Communication Assume
Transfer Control
Transfer Control Assume
General Point
General Executive Data
Free Text Emergency
Free Text General
Application Accept
Application Reject
[9694.2] --- [1]’s AIDC message set (Table VI-4-1 to VI-4-6) = 22 messages
Notify
Coordinate Initial
Coordinate Negotiate
Coordinate Accept
Coordinate Reject
Coordinate Cancel
Coordinate Update
Coordinate Standby
Transfer Initiate
Transfer Conditions Proposal
Transfer Conditions Accept
Transfer Communication Request
Transfer Communication
Transfer Communication Assume
Transfer Control
Transfer Control Assume
General Point
General Executive Data
Free Text Emergency
Free Text General
Application Accept
Application Reject
[9705.1] --- [3]’s AIDC message set = 23 messages
Note: The messages shown hereunder is described at the level of abstract syntax of APDU’s
User Data parameter, except for User-confirmation AIDC-User service (AIDC-ucf AIDC-ASE
service) which shows at the level of APDU due to different levels of significance of
information.
Notify
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
CoordinateInitial
CoordinateNegotiate
CoordinateAccept
CoordinateReject
Cancel
CoordinateUpdate
CoordinateStandby
TransferInitiate
TransferConditionsProposal
TransferConditionsAccept
TransferRequest
TransferComm
TransferCommAssume
TransferControl
TransferControlAssume
TransferControlReject
GeneralPoint
GeneralExecutiveData
SurveillanceGeneral
EmergencyFreeText
GeneralFreeText
Result+ApplicationErrorData (aidc-ucf-apdu)
4. Differences between OPLINKP1’s AIDC and Doc 9705’s AIDC in terms of
message sets
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
[4444.1], [4444.2] and [9694.2] have exactly the same message set.
Transfer Request message in [9694.1] and TransferRequest in [9705.1] are different
from Transfer Communication Request message in [4444.1], [4444.2] and [9694.2].
[9705.1] has no Coordinate Cancel message but has Cancel message instead.
[9705.1] has TransferControlReject message in addition to those in [4444.1],
[4444.2], [9694.1] and [9694.2].
[9705.1] has TransferComm message that is identical to Transfer Communication
message in [4444.1], [4444.2], [9694.1] and [9694.2].
[9705.1] has TransferCommAssume message that is identical to Transfer
Communication Assume message in [4444.1], [4444.2], [9694.1] and [9694.2].
[9705.1] has additional SurveillanceGeneral message.
[9705.1] has Result+ApplicationErrorData message alone to be used for the same
purpose as Application Accept and Application Reject messages in [4444.1], [4444.2],
[9694.1] and [9694.2].
5. Proposed changes on the message sets
5.1
5.2
[9694.1]’s Transfer Request message should be changed to Transfer Communication
Request message.
[9705.1]’s Cancel message may be changed to CoordinateCancel message.
At page III-424:
From:
Cancel ::= SEQUENCE
{
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
……
}
To:
CoordinateCancel ::= SEQUENCE
{
……
}
At page III-418:
From:
AIDC-end-apdu ::= SEQUENCE
{
cancel
[0] Cancel
……
}
To:
AIDC-end-apdu ::= SEQUENCE
{
coordinateCancel
[0] CoordinateCancel
……
}
OPTIONAL,
OPTIONAL,
3.2.3.9.1.1.3.2 ………abstract syntax CoordinateCancel.
3.2.4.1.1.1 b) CoordinateCancel
5.3
[9705.1]’s TransferControlReject should be removed.
At page III-422:
Remove:
TransferControlReject ::= SEQUENCE
{
……
}
At page III-417:
Remove:
TransferControlData ::= CHOICE
{
……
}
At page III-417:
From:
AIDC-tfr-cntrl-Rsp-apdu ::= SEQUENCE
{
transfercontroldata
[0] TransferControlData,
……
}
To:
AIDC-tfr-cntrl-Rsp-apdu ::= SEQUENCE
{
transfercontroldata
[0] TransferControlAssume,
……
}
Removal of Result parameter from Table 3.2.3-11 and Table 3.2.4-11
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
Removal of section 3.2.3.7.1.4 and 3.2.4.2.12.1.3.
5.4
[9705.1]’s TransferComm message may be changed to Transfer Communication
message.
At page III-422:
From:
TransferComm ::= SEQUENCE
{
……
}
To:
TransferCommunication ::= SEQUENCE
{
……
}
At page III-418:
From:
AIDC-tfr-comm-apdu ::= SEQUENCE
{
transfercomm
[0] TransferComm,
……
}
To:
AIDC-tfr-comm-apdu ::= SEQUENCE
{
transfercommunication
[0] TransferCommunication,
……
}
3.2.3.7.8.1.4 Transfer Communication Information
3.2.3.7.8.1.4.2 ………abstract syntax TransferCommunication.
3.2.4.1.1.1 o) TransferCommunication
5.5
[9705.1]’s TransferCommAssume message may be changed to Transfer
Communication Assume message.
At page III-423:
From:
TransferCommAssume ::= SEQUENCE
{
……
}
To:
TransferCommunicationAssume ::= SEQUENCE
{
……
}
At page III-418:
From:
AIDC-tfr-comm-assm-apdu ::= SEQUENCE
{
transfercommassume
[0] TransferCommAssume,
……
}
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
To:
AIDC-tfr-comm-assm-apdu ::= SEQUENCE
{
transfercommunicationassume [0] TransferCommunicationAssume,
……
}
3.2.3.7.9.1.4.2 ………abstract syntax TransferCommunicationAssume.
3.2.4.1.1.1 p) TransferCommunicationAssume
5.6
[9705.1]’s TransferRequest message should be changed to Transfer Communication
Request message.
At page III-422:
From:
TransferRequest ::= SEQUENCE
{
……
}
To:
TransferCommunicationRequest ::= SEQUENCE
{
……
}
At page III-418:
From:
AIDC-tfr-rqst-apdu ::= SEQUENCE
{
transferrequest
[0] TransferRequest,
……
}
To:
AIDC-tfr-comm-rqst-apdu ::= SEQUENCE
{
transfercommunicationrequest [0] TransferCommunicationRequest,
……
}
At page III-418:
From:
MessageType ::= ENUMERATED
{
……
aidc-tfr-rqst-apdu
(7),
……
}
To:
MessageType ::= ENUMERATED
{
……
aidc-tfr-comm-rqst-apdu
(7),
……
}
At page III-415:
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
From:
AIDC-APDU ::= CHOICE
{
……
aidc-tfr-rqst-apdu
[7] AIDC-tfr-rqst-apdu,
……
}
To:
AIDC-APDU ::= CHOICE
{
……
aidc-tfr-comm-rqst-apdu
[7]
AIDC-tfr-comm-rqst-apdu,
……
}
3.2.3.2.1 h) Transfer-communication-request service as defined in 3.2.3.7.4.
3.2.3.7.4 to 3.2.3.7.4.1.3.2: change of Transfer-request to Transfer-communicationrequest
3.2.4.1.1.1 i) TransferCommunicationRequest
3.2.4.2.1.1 h) AIDC-tfr-comm-rqst service………
3.2.4.2.9 to 3.2.4.2.9.1.2: change of AIDC-tfr-rqst to AIDC-tfr-comm-rqst
3.2.5.3.1.9 to 3.2.5.3.1.9.2.1: change of Transfer-request to Transfercommunication-request
3.2.5.3.2.8 to 3.2.5.3.2.8.2.1: change of AIDC-tfr-rqst to AIDC-tfr-comm-rqst
5.7
[9705.1]’s SurveillanceGeneral message should be removed.
At page III-423:
Remove:
SurveillanceGeneral ::= SEQUENCE
{
……
}
At page III-418:
From:
InfoData ::= CHOICE
{
Generalexecutivedata
Generalpoint
Surveillancegeneral
Generalfreetext
Emergencyfreetext
…
}
To:
InfoData ::= CHOICE
{
Generalexecutivedata
Generalpoint
Generalfreetext
Emergencyfreetext
…
}
Remove 3.2.3.8.1.6.2 c)
[0]
[1]
[2]
[3]
[4]
GeneralExecutiveData,
GeneralPoint,
SurveillanceGeneral,
GeneralFreeText,
EmergencyFreeText,
[0]
[1]
[2]
[3]
GeneralExecutiveData,
GeneralPoint,
GeneralFreeText,
EmergencyFreeText,
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
Remove 3.2.4.1.1.1 s)
6. Differences between OPLINKP1’s AIDC and Doc 9705’s AIDC in terms of
message contents
This section shows the mapping of an AIDC message from each document and provides the
extent of the changes required on each message in each document.
6.1
Notify message corresponds to the existing message in each document as follows:
[4444.1]’s Notify message
[4444.2]’s Notify message
[9694.1]’s Notify message
[9694.2]’s Notify message
[9705.1]’s Notify message
[9705.1]’s Notify message’s contents have some distinctions which require changes.
6.2
Coordinate Initial message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Initial message
[4444.2]’s Coordinate Initial message
[9694.1]’s Coordinate Initial message
[9694.2]’s Coordinate Initial message
[9705.1]’s CoordinateInitial message
[9705.1]’s CoordinateInitial message’s contents have some distinctions which require
changes.
6.3
Coordinate Negotiate message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Negotiate message
[4444.2]’s Coordinate Negotiate message
[9694.1]’s Coordinate Negotiate message
[9694.2]’s Coordinate Negotiate message
[9705.1]’s CoordinateNegotiate message
[9705.1]’s CoordinateNegotiate message’s contents have some distinctions which require
changes.
6.4
Coordinate Accept message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Accept message
[4444.2]’s Coordinate Accept message
[9694.1]’s Coordinate Accept message
[9694.2]’s Coordinate Accept message
[9705.1]’s CoordinateAccept message
Further consideration is proposed for [4444.2] and [9694.2]. Currently, all three items within
the message are put as Optional, which is not practical for the implementation. There should
be at least Aircraft Identification to be mandatory within the message.
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
6.5
Coordinate Reject message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Reject message
[4444.2]’s Coordinate Reject message
[9694.1]’s Coordinate Reject message
[9694.2]’s Coordinate Reject message
[9705.1]’s CoordinateReject message
Further consideration is proposed for [4444.2] and [9694.2]. Currently, all three items within
the message are put as Optional, which is not practical for the implementation. There should
be at least Aircraft Identification to be mandatory within the message.
6.6
Coordinate Cancel message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Cancel message
[4444.2]’s Coordinate Cancel message
[9694.1]’s Coordinate Cancel message
[9694.2]’s Coordinate Cancel message
[9705.1]’s Cancel message
[9705.1]’s Cancel message’s contents have some distinctions which require changes.
6.7
Coordinate Update message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Update message
[4444.2]’s Coordinate Update message
[9694.1]’s Coordinate Update message
[9694.2]’s Coordinate Update message
[9705.1]’s CoordinateUpdate message
[9705.1]’s CoordinateUpdate message’s contents have some distinctions which require
changes.
6.8
Coordinate Standby message corresponds to the existing message in each
document as follows:
[4444.1]’s Coordinate Standby message
[4444.2]’s Coordinate Standby message
[9694.1]’s Coordinate Standby message
[9694.2]’s Coordinate Standby message
[9705.1]’s CoordinateStandby message
Further consideration is proposed for [4444.2] and [9694.2]. Currently, all three items within
the message are put as Optional, which is not practical for the implementation. There should
be at least Aircraft Identification to be mandatory within the message.
6.9
Transfer Initiate message corresponds to the existing message in each document
as follows:
[4444.1]’s Transfer Initiate message
[4444.2]’s Transfer Initiate message
[9694.1]’s Transfer Initiate message
[9694.2]’s Transfer Initiate message
[9705.1]’s TransferInitiate message
[9705.1]’s TransferInitiate message’s contents have some distinctions which require
changes.
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
6.10
Transfer Conditions Proposal message corresponds to the existing message in
each document as follows:
[4444.1]’s Transfer Conditions Proposal message
[4444.2]’s Transfer Conditions Proposal message
[9694.1]’s Transfer Conditions Proposal message
[9694.2]’s Transfer Conditions Proposal message
[9705.1]’s TransferConditionsProposal message
[9705.1]’s TransferConditionsProposal message’s contents have some distinctions which
require changes.
6.11
Transfer Conditions Accept message corresponds to the existing message in
each document as follows:
[4444.1]’s Transfer Conditions Accept message
[4444.2]’s Transfer Conditions Accept message
[9694.1]’s Transfer Conditions Accept message
[9694.2]’s Transfer Conditions Accept message
[9705.1]’s TransferConditionsAccept message
[9705.1]’s TransferConditionsAccept message’s contents have some distinctions which
require changes.
6.12
Transfer Communication Request message corresponds to the existing message
in each document as follows:
[4444.1]’s Transfer Communication Request message
[4444.2]’s Transfer Communication Request message
[9694.1]’s Transfer Request message
[9694.2]’s Transfer Communication Request message
[9705.1]’s TransferRequest message
[9705.1]’s TransferRequest message’s contents have some distinctions which require
changes.
6.13
Transfer Communication message corresponds to the existing message in each
document as follows:
[4444.1]’s Transfer Communication message
[4444.2]’s Transfer Communication message
[9694.1]’s Transfer Communication message
[9694.2]’s Transfer Communication message
[9705.1]’s TransferComm message
[9705.1]’s TransferComm message’s contents have some distinctions which require
changes.
6.14
Transfer Communication Assume message corresponds to the existing message
in each document as follows:
[4444.1]’s Transfer Communication Assume message
[4444.2]’s Transfer Communication Assume message
[9694.1]’s Transfer Communication Assume message
[9694.2]’s Transfer Communication Assume message
[9705.1]’s TransferCommAssume message
[9705.1]’s TransferCommAssume message’s contents have some distinctions which require
changes.
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
6.15
Transfer Control message corresponds to the existing message in each document
as follows:
[4444.1]’s Transfer Control message
[4444.2]’s Transfer Control message
[9694.1]’s Transfer Control message
[9694.2]’s Transfer Control message
[9705.1]’s TransferControl message
[9705.1]’s TransferControl message’s contents have some distinctions which require
changes.
6.16
Transfer Control Assume message corresponds to the existing message in each
document as follows:
[4444.1]’s Transfer Control Assume message
[4444.2]’s Transfer Control Assume message
[9694.1]’s Transfer Control Assume message
[9694.2]’s Transfer Control Assume message
[9705.1]’s TransferControlAssume message
[9705.1]’s TransferControlAssume message’s contents have some distinctions which require
changes.
6.17
General Point message corresponds to the existing message in each document as
follows:
[4444.1]’s General Point message
[4444.2]’s General Point message
[9694.1]’s General Point message
[9694.2]’s General Point message
[9705.1]’s GeneralPoint message
[9705.1]’s GeneralPoint message’s contents have some distinctions which require changes.
6.18
General Executive Data message corresponds to the existing message in each
document as follows:
[4444.1]’s General Executive Data message
[4444.2]’s General Executive Data message
[9694.1]’s General Executive Data message
[9694.2]’s General Executive Data message
[9705.1]’s GeneralExecutiveData message
[9705.1]’s GeneralExecutiveData message’s contents have some distinctions which require
changes.
6.19
Free Text Emergency message corresponds to the existing message in each
document as follows:
[4444.1]’s Free Text Emergency message
[4444.2]’s Free Text Emergency message
[9694.1]’s Free Text Emergency message
[9694.2]’s Free Text Emergency message
[9705.1]’s EmergencyFreeText message
The message content in each document is almost the same. No change is required.
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
6.20
Free Text General message corresponds to the existing message in each
document as follows:
[4444.1]’s Free Text General message
[4444.2]’s Free Text General message
[9694.1]’s Free Text General message
[9694.2]’s Free Text General message
[9705.1]’s GeneralFreeText message
The message content in each document is almost the same. No change is required.
6.21
Application Accept message corresponds to the existing message in each
document as follows:
[4444.1]’s Application Accept message
[4444.2]’s Application Accept message
[9694.1]’s Application Accept message
[9694.2]’s Application Accept message
[9705.1]’s aidc-ucf-apdu whose Result parameter has the abstract value “accepted”
The message content in each document is the same. No change is required.
6.22
Application Reject message corresponds to the existing message in each
document as follows:
[4444.1]’s Application Reject message
[4444.2]’s Application Reject message
[9694.1]’s Application Reject message
[9694.2]’s Application Reject message
[9705.1]’s aidc-ucf-apdu whose Result parameter has the abstract value “rejected”
The message content in each document is the same. No change is required. However, the
similarities exist only on the data range and resolution. That is, [4444.2] and [9694.2] do not
provide the error codes. Only [9705.1] does provide the error codes.
6.23 Boundary estimate information
Description about block level information, offset/deviation and speed control are identified in
[1]. [5] (sections 4.4, 4.5) has addressed these issues by adding more subfields within
boundary estimate field of each AIDC message. BoundaryEstimate data type in [3] (page III426) may therefore be modified in a similar manner.
7. Proposed changes on the message contents
7.1
Changes foreseen on [9705.1]’s Notify message are as follows:
- destinationAirport (type DestinationAirport) not set to OPTIONAL.
- aircraftNumberType (type AircraftNumberType) set to OPTIONAL
- Addition of OPTIONAL amendedDestination (type DestinationAerodrome)
7.2
Changes foreseen on [9705.1]’s CoordinateInitial message are as follows:
- destinationAirport (type DestinationAirport) not set to OPTIONAL.
- aircraftNumberType (type AircraftNumberType) set to OPTIONAL
- Addition of OPTIONAL amendedDestination (type DestinationAerodrome)
7.3
Changes foreseen on [9705.1]’s CoordinateNegotiate message are as follows:
- destinationAirport (type DestinationAirport) not set to OPTIONAL.
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
-
Addition of OPTIONAL flightRuleFlightType (type FlightRuleFlightType)
Addition of OPTIONAL beaconCode (type BeaconCode)
Addition of OPTIONAL aircraftNumberType (type AircraftNumberType)
Addition of OPTIONAL cnsEquipment (type CNSEquipment)
Addition of OPTIONAL otherInformation (type OtherInformation)
Addition of OPTIONAL amendedDestination (type DestinationAerodrome)
7.4
Change foreseen on [4444.2]’s and [9694.2]’s Coordinate Accept message is as
follows:
- There should be at least Aircraft Identification to be mandatory within the
message.
7.5
Change foreseen on [4444.2]’s and [9694.2]’s Coordinate Reject message is as
follows:
- There should be at least Aircraft Identification to be mandatory within the
message.
7.6
Changes foreseen on [9705.1]’s Cancel message are as follows:
- destinationAirport (type DestinationAirport) not set to OPTIONAL.
- Replacing OPTIONAL boundaryEstimate (type BoundaryEstimate) with
OPTIONAL fixName (type FixName)
7.7
Changes foreseen on [9705.1]’s CoordinateUpdate message are as follows:
- destinationAirport (type DestinationAirport) not set to OPTIONAL.
- Addition of OPTIONAL flightRuleFlightType (type FlightRuleFlightType)
- Addition of OPTIONAL aircraftNumberType (type AircraftNumberType)
- Addition of OPTIONAL cnsEquipment (type CNSEquipment)
- Addition of OPTIONAL otherInformation (type OtherInformation)
- Addition of OPTIONAL amendedDestination (type DestinationAerodrome)
7.8
Change foreseen on [4444.2]’s and [9694.2]’s Coordinate Standby message is as
follows:
- There should be at least Aircraft Identification to be mandatory within the
message.
7.9
Changes foreseen on [9705.1]’s TransferInitiate message are as follows:
- Removal of departure (type DepartureAirportTime)
- Removal of destination (type DestinationAirport)
7.10
Changes foreseen on [9705.1]’s TransferConditionsProposal message are as follows:
- Removal of departure (type DepartureAirportTime)
- Removal of destination (type DestinationAirport)
- Addition of OPTIONAL trackData (type TrackData)
7.11
Changes foreseen on [9705.1]’s TransferConditionsAccept message are as follows:
- Removal of departure (type DepartureAirportTime)
- Removal of destination (type DestinationAirport)
7.12
Changes foreseen on [9705.1]’s TransferRequest message are as follows:
- Removal of departure (type DepartureAirportTime)
- Removal of destination (type DestinationAirport)
7.13
Changes foreseen on [9705.1]’s TransferComm message are as follows:
- Removal of departure (type DepartureAirportTime)
- Removal of destination (type DestinationAirport)
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
-
Addition of OPTIONAL frequency (type Frequency)
Addition of OPTIONAL trackData (type TrackData)
7.14
Changes foreseen on [9705.1]’s TransferCommAssume message are as follows:
- Removal of departure (type DepartureAirportTime)
- Removal of destination (type DestinationAirport)
7.15
Changes foreseen on [9705.1]’s TransferControl message are as follows:
- departure (type DepartureAirportTime) set to OPTIONAL
7.16
Changes foreseen on [9705.1]’s TransferControlAssume message are as follows:
- departure (type DepartureAirportTime) set to OPTIONAL
7.17
Changes foreseen on [9705.1]’s GeneralPoint message are as follows:
- departure (type DepartureAirportTime) not set to OPTIONAL
- destinationAirport (type DestinationAirport) not set to OPTIONAL.
- flightRuleFlightType (type FlightRuleFlightType) set to OPTIONAL
- aircraftNumberType (type AircraftNumberType) set to OPTIONAL
- cnsEquipment (type CNSEquipment) set to OPTIONAL
- Addition of OPTIONAL trackData (type TrackData)
- Removal of functionalAddress (type FunctionalAddress)
- Addition of OPTIONAL functionalAddressSending (type FunctionalAddress)
- Addition of OPTIONAL functionalAddressReceiving (type FunctionalAddress)
7.18
Changes foreseen on [9705.1]’s GeneralExecutiveData message are as follows:
- executiveData (type ExecutiveData) set to OPTIONAL
- frequency (type Frequency) set to OPTIONAL
7.19
Changes foreseen on BoundaryEstimate data type in [3] (page III-426)
- Define the following new data types:
BlockLevel ::= SEQUENCE {
lowerLevel
[0]
upperLevel
[1]
}
Level,
Level
LEGSpeedMach ::= SEQUENCE {
leg
[0]
speedMach
[1]
}
SpeedTolerance,
SpeedMach
OPTIONAL
SpeedTolerance ::= ENUMERATED {
lessThan
(0),
exactly
(1),
greaterThan
(2)
}
OffTrack ::= SEQUENCE {
offTrackType
[0]
offTrackDistance
[1]
offTrackDirection
[2]
}
OffTrackType ::= ENUMERATED {
offset
(0),
OffTrackType,
Distance,
OffTrackDirection
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
weatherDeviation
(1)
}
OffTrackDirection ::= ENUMERATED {
leftSide
(0),
rightSide
(1),
eitherSide
(2)
}
-
Modify BoundaryEstimate data type as follows:
BoundaryEstimate ::= SEQUENCE {
boundaryFix
[0] Position,
crossingTime
[1] Time,
crossingLevel
[2] BlockLevel,
atwLevel
[3] ATWLevel
machTechnique
[4] LEGSpeedMach
offtrack
[5] OffTrack
}
OPTIONAL,
OPTIONAL,
OPTIONAL
Note: crossingLevel (type BlockLevel), may be specified as a single level or block of
level. If block of level is to be specified, both lowerLevel (type Level) and upperLevel
(type Level) shall be used. If single level is to be specified, only lowerLevel (type
Level) shall be used.
8. Differences between OPLINKP1’s AIDC and Doc 9705’s AIDC in terms of
communication state transition
The flight coordination states/phases in [1] and AIDC-ASE states in [3] have similarities on
the use of each state/phase, which may be shown as follows:
Flight coordination states/phases in [1]
(Figure VI-5-6)
Pre-Notify
Notify
Coodinating
Coordinate
Negotiating
Pre-Transferring
Transferring
Transfer
Backward Coordinating
AIDC-ASE states in [3]
=
=
=
=
=
=
=
=
=
IDLE
NOTIFY
NEGOTIATING
COORDINATED
RENEGOTIATING
PRE-TRANSFER
TRANSFERRING
TRANSFERRED
BACKWARD-COORDINATING
Some distinctions exist on the events associated with each state which may be described as
follows:
8.1
From Coordinate state to Negotiating state in [1], it allows the amendments to
coordination to be negotiated by means of a Coordinate Negotiate message (if the
amendments are not in accordance with the LOA), which can be either accepted or
rejected by using Coordinate Accept or Coordinate Reject message, respectively. If
the amendments are in accordance with the LOA, Coordinate Update message shall
be used instead, which shall always be accepted by Coordinate Accept message.
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
[3] allows the amendments to coordination only by means of CoordinateUpdate
message (from COORDINATED to RENEGOTIATING states).
8.2
From Coordinate state to Transferring state in [1], the event trigger can be either the
transmission of Transfer Control message or Transfer Communication message.
State change from COORDINATED to TRANSFERRING in [3] can be triggered only
by TransferControl message.
8.3
From Coordinate state to Pre-transferring state in [1], the event trigger can be either
the transmission of Transfer Initiate message or Transfer Conditions Proposal
message.
State change from COORDINATED to PRE-TRANSFER in [3] can be triggered only
by TransferInitiate message
8.4
From Transfer state to Backward Coordinating state in [1], the event trigger can be
either the transmission of Coordinate Update message or Coordinate Negotiate
message.
State change from TRANSFERRED to BACKWARD-COORDINATING in [3] can be
triggered only by CoordinateUpdate message
8.5
Within Backward Coordinating state in [1], coordination negotiation can be achieved
only by Coordinate Negotiate message.
Coordination negotiation within BACKWARD-COORDINATING state in [3] can be
achieved either by CoordinateNegotiate or CoordinateStandby message.
8.6
Within Pre-transferring state in [1], transfer of executive information (which may occur
at any time after initial coordination is completed) can be achieved by General
Executive Data message.
In [3], transfer of executive information (using GeneralExecutiveData message) is
described as one of the possible messages within the aidc-inf-tfr-apdu, which can be
sent at any time after the initial invocation of primitives of the Notify service or after
the initial invocation of the Coordinate-start service primitives when the Notify service
is not used.
9. Proposed changes on the communication state transition
According to 8.1 to 8.6, the following changes in [3] are foreseen:
9.1
3.2.6.1.11.1.1 It shall be valid to invoke the AIDC-crd-ngtt request primitive when
the AIDC-ASE protocol machine is in the NEGOTIATING state, or the
COORDINATED state, or the RE-NEGOTIATING, or the TRANSFERRED state, or
the BACKWARD-COORDINATING state.
9.2
3.2.6.1.12.1.1 It shall be valid to invoke the AIDC-DATA indication primitive with an
AIDC-crd-ngtt-apdu when the AIDC-ASE protocol machine is in the NEGOTIATING
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
state, or the COORDINATED state, or the RE-NEGOTIATING state, or the
TRANSFERRED state, or the BACKWARD-COORDINATING state.
9.3
3.2.6.1.13.1.1 It shall be valid to invoke the AIDC-crd-stndby request primitive when
the AIDC-ASE protocol machine is in the NEGOTIATING state, or the RENEGOTIATING state, or the BACKWARDCOORDINATING state.
9.4
3.2.6.1.14.1.1 It shall be valid to invoke the AIDC-DATA indication primitive with an
AIDC-crd-stndby-apdu when the AIDC-ASE protocol machine is in the
NEGOTIATING state, or the RE-NEGOTIATING state, or the BACKWARDCOORDINATING state.
9.5
3.2.6.1.19.1.1 It shall be valid to invoke the AIDC-tfr-prpsl request primitive when
the AIDC-ASE protocol machine is in the PRE-TRANSFER state, or the
COORDINATED state.
9.6
3.2.6.1.20.1.1 It shall be valid to invoke the AIDC-DATA indication primitive with an
AIDC-tfr-prpsl-apdu when the AIDC-ASE protocol machine is in the PRE-TRANSFER
state, or the COORDINATED state.
9.7
3.2.6.1.23.1.1 It shall be valid to invoke the AIDC-tfr-comm request primitive when
the AIDC-ASE protocol machine is in the PRE-TRANSFER state, or the
COORDINATED state.
9.8
3.2.6.1.24.1.1 It shall be valid to invoke the AIDC-DATA indication primitive with an
AIDC-tfr-comm apdu when the AIDC-ASE protocol machine is in the PRETRANSFER state, or the COORDINATED state.
9.9
3.2.6.1.33.2.1 b) 2) iv)
if in the COORDINATED state:
A) if the variable vr1 = coord-start, then:
I) enter RE-NEGOTIATING state.
B) if the variable vr1 = trns-init, then:
I) start the timer t3R; and
II) enter PRE-TRANSFER state.
C) if the variable vr1 = trns-start, then enter the TRANSFERRING state.
D) if the variable vr1 = trns-prpsl, then enter the PRE-TRANSFER state.
E) if the variable vr1 = trns-comm, then enter the TRANSFERRING state.
F) if the variable vr1 = end, then:
I) stop all timers; and
II) enter the IDLE state.
9.10
3.2.6.1.33.2.1 b) 2) viii)
if in the TRANSFERRED state:
A) if the variable vr1 = coord-start, then enter the BACKWARDCOORDINATING state.
B) if the variable vr1 = coord-negot, then enter the BACKWARDCOORDINATING state.
C) if the variable vr1 = end, then enter the IDLE state.
9.11
3.2.6.1.34.2.1 c) 1) vii)
if in the TRANSFERRED state:
A) if the variable vs1 = coord-start, then enter the state BACKWARDCOORDINATING state.
B) if the variable vs1 = coord-negot, then:
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
I) start the timer t1R; and
II) enter the BACKWARD-COORDINATING state.
C) if the variable vs1 = end, then enter IDLE state.
9.12
3.2.6.1.34.2.1 c) 1) iii)
if in the COORDINATED state:
A) if the variable vs1 = coord-start, then:
I) start the timer t1R; and
II) enter the RE-NEGOTIATING state.
B) if the variable vs1 = coord-negot, then:
I) start the timer t1R; and
II) enter the RE-NEGOTIATING state.
C) if the variable vs1 = trns-init, then enter the PRE-TRANSFER state.
D) if the variable vs1 = trns-prpsl, then:
I) start the timer t1R; and
II) enter the PRE-TRANSFER state.
E) if the variable vs1 = trns-comm, then:
I) start the timer t1R; and
II) enter the TRANSFERRING state.
F) if the variable vs1 = trns-start, then:
I) start the timer t1R; and
II) enter the TRANSFERRING state.
G) if the variable vs1 = end, then:
I) stop all timers;
II) start timer t2NC; and
III) enter the IDLE state.
10. Differences between OPLINKP1’s AIDC and Doc 9705’s AIDC in terms of the
purpose of each message
10.1
10.2
10.3
The purpose of Coordinate-negotiate service (an AIDC-user service that corresponds
to the AIDC-crd-ngtt AIDC-ASE service, aidc-crd-ngtt-apdu, and CoordinateNegotiate
message) described in 7.3.4.3 of [4] does not provide the following details: “the
amendments of coordination conditions are not in accordance with the LOA (letter of
agreement) or if the Coordinate Update is not in use”.
The purpose of Coordinate Standby message described in 11.4.2.5.10 of [2] and 2.7
of Appendix 6 of [2] do not provide the details about “extension of coordination
timeout”, as described in Table VI-4-2 of [1] and 7.3.4.4 of [4].
The purpose of Transfer Communication Request message described in 11.4.2.5.14
of [2] does not include the purpose of request for the transfer of control (Table VI-4-3
of [1] include both request for transfer of control and communication responsibility.).
11. Proposed changes on the purpose of each message
11.1
7.3.4.3 of [4] may be revised as follows:
“7.3.4.3.3 The Coordinate-negotiate service is used by an ATSU in a coordination
dialogue to negotiate or propose the revision to the agreed coordination conditions for
a flight that will be the subject of coordination and transfer when the amendments are
not in accordance with the LOA. At the same time the submitting ATSU provides
updated information about the flight.”
ACP WGN SGN3/9 WP_____
BRUSSELS, BELGIUM, 26th–30th JUNE 2006
11.2
11.4.2.5.10 of [2] may be revised as follows:
“11.4.2.5.10.1 The Coordinate Standby message shall be sent by the unit receiving a
Coordinate Initial or Coordinate Negotiate message to indicate to the sending unit that
their proposal has been received and will be responded to in due course. It could be
used for example, if the coordination message had to be referred for manual
processing or if further coordination had to be conducted with another unit and the
extension of coordination timeout values are then foreseen.”
2.7 of Appendix 6 of [2] may be revised as follows:
2.7.1 The Coordinate Standby message is used to indicate that the Coordinate Initial
or Coordinate Negotiate message has been received, the data has been referred to a
controller and/or other unit and an operational response will be sent in due course.
Extension of coordination timeout values are then foreseen.
11.3
11.4.2.5.14 of [2] may be revised as follows:
“11.4.2.5.14.1 The Transfer Communication Request message shall be transmitted
by the controller in the accepting unit to request the transfer of control and
communication of a flight. The message shall be used when the controller in the
accepting unit requires communication with the flight forthwith and indicates that the
controller in the transferring unit should transmit appropriate contact instructions to
the relevant aircraft……”
12. Proposed changes on other miscellaneous items
12.1
12.2
In the context of AIDC, the acronyms/abbreviations ATSU (ATS unit), C-ATSU
(controlling ATS unit), D-ATSU (downstream ATS unit), R-ATSU (receiving ATS unit),
or ATS unit(s) are always used. However, ATC units is present many times in [2],
which should be corrected.
11.2.2.2.1 in page H-54 of [2] is proposed to be changed as follows:
Where AIDC messages are transmitted via the ATN, the messages shall be
represented by using abstract syntax notation one (ASN.1). The ASN.1-represented
AIDC messages shall be encoded by using packed encoding rules (PER) during
message transmission.
13. Actions by the meeting
The meeting is invited to:
-
Note the differences and/or distinctions regarding AIDC as observed and identified in
this papers;
Discuss the corrections as proposed in sections 5, 7, 9, 11, 12;
Take necessary actions regarding amendment to AIDC part of ground-ground
application of ATN in Doc 9705.