RTCA SC-214/EUROCAE WG-78 by x51R6Z01

VIEWS: 0 PAGES: 259

									                                RTCA SC-214/EUROCAE WG-78
                Air Traffic Services Safety and Interoperability Requirements
                                                   General Information

Position Paper Number [assigned by Pub]:             Version: e.g. 1, 1.1   Date: e.g. 11 Nov 94     Comments Due to Author:

                                                                 I             26 June 2012
PU-30
FANS 1/A - Advanced
Services - INTEROP
Position Paper Title:                                                       Editor /email address:

FUTURE AIR NAVIGATION SYSTEM 1/A                                            Chris Collings /
ACCOMODATION FOR ADVANCED                                                   chris.collings@harris.com
SERVICES IN THE ATN ENVIRONMENT
INTEROPERABILITY STANDARD
Status:

                 New Material Review                                          Publication Integration

Abstract and Proposed Actions:

This new material provides the mature draft for INTEROP document “Interoperability Requirements
Standard For FANS 1/A-ATN Advanced ATS Data Communication”.
It contains the INTEROP requirements for the advanced ATS services (DLIC, ACL, ACM, DCL, and
AMC) and provides INTEROP guidance for ADS-S based services.
Coordinator and supporters are continuing to work on the document before releasing it for integration.



Key word(s) (optional):



                                                   Web site information
Web site location:                         Filename(s):

www.faa.gov/go/sc214                       PU-30-Draft-J_FANS_INTEROP_(26JUN12)PU-30-Draft-
                                           J_FANS_INTEROP_(26JUN12)-redline
Special posting instructions:
ii




                                       Distribution

Name                                  Org             Email Address

All RTCA SC-214/ EUROCAE WG-78 SG-3   RTCA/EUROCAE    sg3-dcs@eurocontrol.int
members

All RTCA SC-214/ EUROCAE WG-78        RTCA/EUROCAE    plenary @eurocontrol.int

DATACOMM Program                      FAA             Gregg.Anderson@faa.gov
        FUTURE AIR NAVIGATION SYSTEM 1/A
 ACCOMODATION FOR ADVANCED SERVICES IN THE ATN
    ENVIRONMENT INTEROPERABILITY STANDARD
        (FANS 1/A — ATS INTEROP STANDARD)




                     Version
                        I
                     DRAFT




RTCA/EUROCAE PU-30                             Prepared by:
Date: 26 June 2012             RTCA SC-214/EUROCAE WG-78
iv
                                                                TABLE OF CONTENTS

1      INTRODUCTION .......................................................................................... 1-171-12
1.1         Purpose ............................................................................................................................................... 1-171-12

1.2     Scope ................................................................................................................................................... 1-171-12
   1.2.1 ATN Ground System Providing ATS Datalink Services to FANS 1/A Aircraft............................. 1-181-13
   1.2.2 Ground Systems Providing ATS Datalink Services to Bilingual Aircraft....................................... 1-191-14

1.3         Relationships to other Documents .................................................................................................... 1-191-14

1.4     Description of this Document ........................................................................................................... 1-211-16
   1.4.1 Document Conventions ................................................................................................................... 1-211-16
   1.4.2 Document Organization .................................................................................................................. 1-221-17
   1.4.3 Acronyms and Glossary of Terms ................................................................................................... 1-221-17

1.5         References .......................................................................................................................................... 1-261-21


2      DESCRIPTION AND OPERATIONAL CONSIDERATIONS ........................ 2-272-22
2.1     Data Link Initiation Capability ........................................................................................................ 2-282-23
   2.1.1 ATN CM Application ..................................................................................................................... 2-282-23
   2.1.2 FANS 1/A AFN Application ........................................................................................................... 2-282-23

2.2     CPDLC Application .......................................................................................................................... 2-282-23
   2.2.1 ATN CPDLC Application ............................................................................................................... 2-282-23
   2.2.2 FANS 1/A CPDLC Application ...................................................................................................... 2-292-24

2.3     ADS-C Application Description ....................................................................................................... 2-292-24
   2.3.1 ATN ADS-C Application ................................................................................................................ 2-292-24
   2.3.2 FANS 1/A ADS Application ........................................................................................................... 2-292-24


3 ATN GROUND SYSTEM PROVIDING ATS DATALINK SERVICES TO FANS 1/A
AIRCRAFT .......................................................................................................... 3-303-25
3.1         COMMUNICATION REQUIREMENTS ....................................................................................... 3-303-25

3.2      REQUIREMENTS FOR DATA LINK APPLICATIONS............................................................. 3-313-26
   3.2.1 CM/AFN Application Requirements .............................................................................................. 3-323-27
      3.2.1.1 ATN CM and FANS 1/A AFN Primitives ............................................................................. 3-323-27
      3.2.1.2 ATN and FANS 1/A Primitive Parameters ............................................................................ 3-333-28
      3.2.1.3 ATN CM and FANS 1/A AFN Variables............................................................................... 3-363-31
      3.2.1.4 Timers..................................................................................................................................... 3-383-33
   3.2.2 CPDLC Application Requirements ................................................................................................. 3-393-34
      3.2.2.1 Time, Timestamp and Message Latency ................................................................................ 3-393-34
      3.2.2.2 ATN CPDLC Constructs and FANS 1/A ACARS IMIs ........................................................ 3-443-39
      3.2.2.3 High-Level Data Structures .................................................................................................... 3-513-46
      3.2.2.4 Message Attributes ................................................................................................................. 3-523-47
      3.2.2.5 LACK ..................................................................................................................................... 3-543-49
vi


       3.2.2.6         CPDLC Disabling/Enabling ................................................................................................... 3-563-51
       3.2.2.7         Message Header ..................................................................................................................... 3-573-52
       3.2.2.8         Uplink Message Elements ...................................................................................................... 3-583-53
       3.2.2.9         Downlink Message Elements ................................................................................................. 3-953-90
       3.2.2.10        Concatenating Messages Elements ..................................................................................... 3-1113-106
       3.2.2.11        Error Information ............................................................................................................... 3-1133-108
       3.2.2.12        Message Element Parameters and Data Type ..................................................................... 3-1243-119
       3.2.2.13        ATN and FANS 1/A Message Element Pairing ................................................................. 3-1573-152
       3.2.2.14        ATN UM with W/U resp and Corresponding FANS 1/A Messages with R resp ............... 3-1713-165
       3.2.2.15        ATN UM with A/N resp and Corresponding FANS 1/A Messages with R resp ................ 3-1713-165

3.3      DYNAMIC FUNCTIONS/OPERATIONS OF DATA LINK SERVICES ............................... 3-1733-167
   3.3.1 DLIC ........................................................................................................................................... 3-1733-167
      3.3.1.1  Scope and Objective ........................................................................................................... 3-1733-167
      3.3.1.2  DLIC Initiation Function .................................................................................................... 3-1743-168
      3.3.1.3  DLIC Contact Function ...................................................................................................... 3-1773-171
      3.3.1.4  DLIC Update Function ....................................................................................................... 3-1793-173
   3.3.2 CPDLC ........................................................................................................................................ 3-1813-175
      3.3.2.1  Timers in CPDLC-based services....................................................................................... 3-1813-175
      3.3.2.2  ATC Communication Management (ACM) Service .......................................................... 3-1863-180
      3.3.2.3  Clearance Request and Delivery (CRD) and Information Exchange and Reporting (IER) Services 3-
      1933-186
      3.3.2.4  Departure Clearance (DCL) Service................................................................................... 3-1933-186
      3.3.2.5  ATC Microphone Check (AMC) Service ........................................................................... 3-1973-190
      3.3.2.6  ITBO Service...................................................................................................................... 3-1973-190

3.4      Guidelines for ATN Ground System Use of FANS 1/A ADS-C Application ............................ 3-1983-191
   3.4.1 ADS-C Contracts ........................................................................................................................ 3-1983-191
   3.4.2 Uplink Functions ......................................................................................................................... 3-1993-192
      3.4.2.1   ADS Uplink Messages ....................................................................................................... 3-1993-192
      3.4.2.2   ADS Demand Contract Request ......................................................................................... 3-2013-194
      3.4.2.3   ADS Periodic Contract Request ......................................................................................... 3-2053-197
      3.4.2.4   ADS Event Contract Request ............................................................................................. 3-2083-200
      3.4.2.5   Vertical speed change event ............................................................................................... 3-2123-204
   3.4.3 Downlink Functions .................................................................................................................... 3-2153-207
      3.4.3.1   ADS Downlink Messages................................................................................................... 3-2153-207
      3.4.3.2   ADS Report ........................................................................................................................ 3-2173-209
      3.4.3.3   ADS ATN Reject / FANS Negative Ack ........................................................................... 3-2253-217
      3.4.3.4   ADS ATN Cancel Positive Ack / FANS Positive Ack ....................................................... 3-2273-219
      3.4.3.5   ADS ATN Cancel Negative Ack / FANS Negative Ack.................................................... 3-2273-219
      3.4.3.6   ADS Positive Acknowledgement ....................................................................................... 3-2283-220
      3.4.3.7   ADS Non-Compliance Notification ................................................................................... 3-2283-220
      3.4.3.8   Parameter Range and Resolution ........................................................................................ 3-2323-223
   3.4.4 Timers ......................................................................................................................................... 3-2373-228


4 GROUND SYSTEMS PROVIDING ATS DATALINK SERVICES TO BILINGUAL
AIRCRAFT ...................................................................................................... 4-2384-229

4.1        LOGON PROCEDURE FOR BILINGUAL AIRCRAFT ......................................................... 4-2384-229

4.2        BILINGUAL AIRCRAFT TRANSITING FROM FANS 1/A ATSU TO ATN ATSU ........... 4-2384-229
    4.2.1       ACM service ............................................................................................................................... 4-2384-229
    4.2.2       DLIC Contact procedure ............................................................................................................. 4-2384-229

4.3     BILINGUAL AIRCRAFT TRANSITING FROM ATN ATSU TO FANS 1/A ATSU .......... 4-2404-231
   4.3.1 ACM Service............................................................................................................................... 4-2404-231
   4.3.2 DLIC Contact procedure ............................................................................................................. 4-2404-231


1       INTRODUCTION ................................................................................................. 1-11

1.1         Purpose ...................................................................................................................................................... 1-11

1.2     Scope .......................................................................................................................................................... 1-11
   1.2.1 ATN Ground System Providing ATS Datalink Services to FANS 1/A Aircraft.................................... 1-12
   1.2.2 Ground Systems Providing ATS Datalink Services to Bilingual Aircraft.............................................. 1-13

1.3         Relationships to other Documents........................................................................................................... 1-13

1.4     Description of this Document .................................................................................................................. 1-15
   1.4.1 Document Conventions .......................................................................................................................... 1-15
   1.4.2 Document Organization ......................................................................................................................... 1-16
   1.4.3 Acronyms and Glossary of Terms .......................................................................................................... 1-16

1.5         References ................................................................................................................................................. 1-20


2       DESCRIPTION AND OPERATIONAL CONSIDERATIONS ............................... 2-21

2.1     Data Link Initiation Capability ............................................................................................................... 2-22
   2.1.1 ATN CM Application ............................................................................................................................ 2-22
   2.1.2 FANS 1/A AFN Application .................................................................................................................. 2-22

2.2     CPDLC Application ................................................................................................................................. 2-22
   2.2.1 ATN CPDLC Application ...................................................................................................................... 2-22
   2.2.2 FANS 1/A CPDLC Application ............................................................................................................. 2-23

2.3     ADS-C Application Description .............................................................................................................. 2-23
   2.3.1 ATN ADS-C Application ....................................................................................................................... 2-23
   2.3.2 FANS 1/A ADS Application .................................................................................................................. 2-23


3 ATN GROUND SYSTEM PROVIDING ATS DATALINK SERVICES TO FANS 1/A
AIRCRAFT ................................................................................................................. 3-24

3.1         COMMUNICATION REQUIREMENTS .............................................................................................. 3-24

3.2      REQUIREMENTS FOR DATA LINK APPLICATIONS.................................................................... 3-25
   3.2.1 CM/AFN Application Requirements ..................................................................................................... 3-26
      3.2.1.1 ATN CM and FANS 1/A AFN Primitives .................................................................................... 3-26
      3.2.1.2 ATN and FANS 1/A Primitive Parameters ................................................................................... 3-27
      3.2.1.3 ATN CM and FANS 1/A AFN Variables...................................................................................... 3-30
      3.2.1.4 Timers............................................................................................................................................ 3-32
   3.2.2 CPDLC Application Requirements ........................................................................................................ 3-33
      3.2.2.1 Time, Timestamp and Message Latency ....................................................................................... 3-33
      3.2.2.2 ATN CPDLC Constructs and FANS 1/A ACARS IMIs ............................................................... 3-38
viii


       3.2.2.3         High-Level Data Structures ........................................................................................................... 3-45
       3.2.2.4         Message Attributes ........................................................................................................................ 3-46
       3.2.2.5         LACK ............................................................................................................................................ 3-48
       3.2.2.6         CPDLC Disabling/Enabling .......................................................................................................... 3-50
       3.2.2.7         Message Header ............................................................................................................................ 3-51
       3.2.2.8         Uplink Message Elements ............................................................................................................. 3-52
       3.2.2.9         Downlink Message Elements ........................................................................................................ 3-89
       3.2.2.10        Concatenating Messages Elements .............................................................................................. 3-105
       3.2.2.11        Error Information ........................................................................................................................ 3-107
       3.2.2.12        Message Element Parameters and Data Type .............................................................................. 3-118
       3.2.2.13        ATN and FANS 1/A Message Element Pairing .......................................................................... 3-151
       3.2.2.14        ATN UM with W/U resp and Corresponding FANS 1/A Messages with R resp ........................ 3-164
       3.2.2.15        ATN UM with A/N resp and Corresponding FANS 1/A Messages with R resp ......................... 3-164

3.3      DYNAMIC FUNCTIONS/OPERATIONS OF DATA LINK SERVICES ........................................ 3-166
   3.3.1 DLIC .................................................................................................................................................... 3-166
      3.3.1.1 Scope and Objective .................................................................................................................... 3-166
      3.3.1.2 DLIC Initiation Function ............................................................................................................. 3-167
      3.3.1.3 DLIC Contact Function ............................................................................................................... 3-170
      3.3.1.4 DLIC Update Function ................................................................................................................ 3-172
   3.3.2 CPDLC ................................................................................................................................................. 3-174
      3.3.2.1 Timers in CPDLC-based services................................................................................................ 3-174
      3.3.2.2 ATC Communication Management (ACM) Service ................................................................... 3-179
      3.3.2.3 Clearance Request and Delivery (CRD) and Information Exchange and Reporting (IER) Services 3-
      185
      3.3.2.4 Departure Clearance (DCL) Service............................................................................................ 3-185
      3.3.2.5 ATC Microphone Check (AMC) Service .................................................................................... 3-189
      3.3.2.6 ITBO Service............................................................................................................................... 3-189

3.4      Guidelines for ATN Ground System Use of FANS 1/A ADS-C Application ..................................... 3-190
   3.4.1 ADS-C Contracts ................................................................................................................................. 3-190
   3.4.2 Uplink Functions .................................................................................................................................. 3-191
      3.4.2.1   ADS Uplink Messages ................................................................................................................ 3-191
      3.4.2.2   ADS Demand Contract Request .................................................................................................. 3-193
      3.4.2.3   ADS Periodic Contract Request .................................................................................................. 3-196
      3.4.2.4   ADS Event Contract Request ...................................................................................................... 3-199
      3.4.2.5   Vertical speed change event ........................................................................................................ 3-203
   3.4.3 Downlink Functions ............................................................................................................................. 3-206
      3.4.3.1   ADS Downlink Messages............................................................................................................ 3-206
      3.4.3.2   ADS Report ................................................................................................................................. 3-208
      3.4.3.3   ADS ATN Reject / FANS Negative Ack .................................................................................... 3-216
      3.4.3.4   ADS ATN Cancel Positive Ack / FANS Positive Ack ................................................................ 3-218
      3.4.3.5   ADS ATN Cancel Negative Ack / FANS Negative Ack............................................................. 3-218
      3.4.3.6   ADS Positive Acknowledgement ................................................................................................ 3-219
      3.4.3.7   ADS Non-Compliance Notification ............................................................................................ 3-219
      3.4.3.8   Parameter Range and Resolution ................................................................................................. 3-222
   3.4.4 Timers .................................................................................................................................................. 3-227


4 GROUND SYSTEMS PROVIDING ATS DATALINK SERVICES TO BILINGUAL
AIRCRAFT ............................................................................................................... 4-228
4.1        LOGON PROCEDURE FOR BILINGUAL AIRCRAFT .................................................................. 4-228

4.2     BILINGUAL AIRCRAFT TRANSITING FROM FANS 1/A ATSU TO ATN ATSU .................... 4-228
   4.2.1 ACM service ........................................................................................................................................ 4-228
   4.2.2 DLIC Contact procedure ...................................................................................................................... 4-228

4.3     BILINGUAL AIRCRAFT TRANSITING FROM ATN ATSU TO FANS 1/A ATSU ................... 4-230
   4.3.1 ACM Service........................................................................................................................................ 4-230
   4.3.2 DLIC Contact procedure ...................................................................................................................... 4-230
x


                                                   APPENDICES
Appendix A    MEMBERSHIP
Appendix B    HISTORY AND TERMS OF REFERENCE OF SC-214/WG-78
Appendix C    IMPROVEMENT SUGGESTION FORM
Appendix D    Interoperability Requirements Traceability Table
Appendix A    MEMBERSHIP
Appendix B    HISTORY AND TERMS OF REFERENCE OF SC-214/WG-78
Appendix C    IMPROVEMENT SUGGESTION FORM
Appendix D    Interoperability Requirements Traceability Table


                                                LIST OF FIGURES
Figure 1      Mixed Interoperability Requirements Applicability ..........................................1-181-13
Figure 2      Mixed technology environments.............................................................................1-201-15
Figure 3      SC-214 to FANS DCL Accommodation ............................................................3-1953-188
Figure 4      DLIC Contact procedure (FANS 1/A to ATN)...................................................4-2394-230
Figure 5      DLIC Contact procedure (ATN to FANS 1/A)...................................................4-2414-232
Figure 1      Mixed Interoperability Requirements Applicability ................................................. 1-12
Figure 2      Mixed technology environments.................................................................................... 1-14
Figure 3      SC-214 to FANS DCL Accommodation ..................................................................... 3-187
Figure 4      DLIC Contact procedure (FANS 1/A to ATN)............................................................ 4-229


                                                LIST OF TABLES
Table 2-1     Advanced data link services and applications.........................................................2-272-22
Table 3-1     SMI Downlink and Uplink relationship for FANS 1/A AFN, and CPDLC ...........3-313-26
Table 3-2     Valid label/sub-label/MFI/IMI/SMI combinations for FANS 1/A CPDLC uplink 3-313-26
Table 3-3     Valid label/sub-label/MFI/IMI/SMI combinations for FANS 1/A AFN uplink .....3-313-26
Table 3-4     ATN CM and FANS 1/A AFN primitives ..............................................................3-323-27
Table 3-5     Mapping of parameters into ATN CM primitives and FANS 1/A AFN primitives3-333-28
Table 3-6     ATN CM and FANS 1/A AFN variables ................................................................3-363-31
Table 3-7     ATN CM and FANS 1/A AFN timers ....................................................................3-383-33
Table 3-8     ATN and FANS 1/A CPDLC requirements for time source ..................................3-393-34
Table 3-9     ATN and FANS 1/A CPDLC requirements for timestamp generation...................3-403-35
Table 3-10    ATN and FANS 1/A CPDLC requirements for message latency ...........................3-413-36
Table 3-11    ATN CPDLC constructs and FANS 1/A CPDLC ACARS IMIs ...........................3-443-39
Table 3-12    ATN and FANS 1/A CPDLC high-level data structures ........................................3-513-46
Table 3-13    ATN and FANS 1/A CPDLC message attributes ...................................................3-523-47
Table 3-14:   LACK on Downlink Messages ...............................................................................3-543-49
Table 3-15:   LACK on Uplink Messages ....................................................................................3-553-50
Table 3-16    CPDLC Disabling/Enabling Functionality .............................................................3-563-51
Table 3-17    ATN and FANS 1/A CPDLC message headers ......................................................3-573-52
Table 3-18    ATN and FANS 1/A CPDLC uplink message elements.........................................3-583-53
Table 3-19    ATN and FANS 1/A CPDLC downlink message elements ....................................3-953-90
Table 3-20    High Level Concatenation Requirements ...........................................................3-1113-106
Table 3-21    ATN and FANS 1/A CPDLC responses to concatenated messages ...................3-1123-107
Table 3-22   ATN and FANS 1/A ERROR information requirements ...................................3-1133-108
Table 3-23   ATN and FANS 1/A uplink [error information] data type .................................3-1153-110
Table 3-24   ATN and FANS 1/A downlink [error information] data type ............................3-1163-111
Table 3-25   ATN and FANS 1/A further downlink error information ...................................3-1193-114
Table 3-26   ATN and FANS 1/A altitude data type ...............................................................3-1253-120
Table 3-27   ATN Level data type sent in FANS UM169 Free Text ......................................3-1263-121
Table 3-28   ATN and FANS 1/A distance data type ..............................................................3-1263-121
Table 3-29   ATN and FANS 1/A position data type ..............................................................3-1273-122
Table 3-30   ATN positionR data type sent in FANS UM169 Free Text ................................3-1283-123
Table 3-31   ATN and FANS 1/A speed data type ..................................................................3-1293-124
Table 3-32   ATN speed data type sent in FANS UM169 Free Text ......................................3-1313-126
Table 3-33   ATN and FANS 1/A distance offset data type....................................................3-1323-127
Table 3-34   ATN and FANS 1/A Time data type ..................................................................3-1333-128
Table 3-35   ATN Time data type sent in FANS UM169 Free Text .......................................3-1333-128
Table 3-36   ATN Timesec data type sent in FANS UM169 Free Text ..................................3-1333-128
Table 3-37   ATN and FANS 1/A vertical rate data type ........................................................3-1343-129
Table 3-38   ATN and FANS 1/A Facility data type...............................................................3-1353-130
Table 3-39   ATN and FANS 1/A ICAO facility designation data type .................................3-1353-130
Table 3-40   ATN Facility Designation data type sent in FANS UM169 Free Text ...............3-1363-131
Table 3-41   ATN and FANS 1/A Unit Id / Unit Name data type...........................................3-1373-132
Table 3-42   ATN unit name data type sent in FANS UM169 Free Text ...............................3-1383-132
Table 3-43   ATN Number of Degrees and FANS 1/A Degrees data type .............................3-1383-133
Table 3-44   ATN and FANS 1/A route clearance data type...................................................3-1393-133
Table 3-45   ATN and FANS 1/A published identifier data type............................................3-1413-136
Table 3-46   ATN and FANS 1/A place bearing distance data type .......................................3-1423-136
Table 3-47   ATN and FANS 1/A leg type data type ..............................................................3-1423-137
Table 3-48   ATN and FANS 1/A latitude/longitude data type...............................................3-1433-138
Table 3-49   ATN and FANS 1/A frequency data type ...........................................................3-1463-141
Table 3-50   ATN frequency data type sent in FANS UM169 Free Text ...............................3-1473-142
Table 3-51   ATN and FANS 1/A code data type ...................................................................3-1473-142
Table 3-52   ATN and FANS 1/A Departure clearanceR data type ........................................3-1483-142
Table 3-53   ATN and FANS 1/A Procedure Name data type ................................................3-1503-145
Table 3-54   ATN and FANS 1/A Altimeter data type ...........................................................3-1513-145
Table 3-55   ATN altimeter data type sent in FANS UM169 Free Text .................................3-1513-146
Table 3-56   ATN and FANS 1/A Atis Code data type ...........................................................3-1513-146
Table 3-57   ATN atis code data type sent in FANS UM169 Free Text .................................3-1523-146
Table 3-58   ATN and FANS 1/A To/From data type.............................................................3-1523-147
Table 3-59   ATN and FANS 1/A position report advanced data type ...................................3-1523-147
Table 3-60   ATN and FANS 1/A Remaining Fuel data type .................................................3-1543-149
Table 3-61   ATN and FANS 1/A Persons on Board data type...............................................3-1543-149
Table 3-62   ATN and FANS 1/A Version Number data type ................................................3-1553-149
Table 3-63   ATN and FANS 1/A temperature data type ........................................................3-1553-150
Table 3-64   ATN and FANS 1/A Vertical Change data type .................................................3-1563-150
Table 3-65   ATN and FANS 1/A Vertical Direction data type ..............................................3-1563-151
Table 3-66   ATN and FANS 1/A Turbulence data type.........................................................3-1573-151
Table 3-67   ATN and FANS 1/A RTA Time data type .........................................................3-1573-152
Table 3-68   Suggested ATN downlink message elements with Y response attribute ............3-1593-153
Table 3-69   ATN uplink message elements with Y response attribute ..................................3-1643-158
Table 3-70   ATN UM with W/U Resp and Corresponding FANS Messages with R Resp ...3-1713-165
Table 3-71   ATN UM with A/N Resp and Corresponding FANS Messages with R Resp ....3-1723-166
xii


Table 3-72    DLIC initiation using ATN CM and FANS 1/A AFN ........................................3-1743-168
Table 3-73    DLIC contact using ATN CM and FANS 1/A AFN ...........................................3-1773-171
Table 3-74    DLIC update using ATN CM and FANS 1/A AFN............................................3-1793-173
Table 3-75    CPDLC t-start timer ............................................................................................3-1813-175
Table 3-76    CPDLC tr Timer .................................................................................................3-1813-175
Table 3-77    CPDLC ttr Timer ................................................................................................3-1833-177
Table 3-78    CPDLC tts Timer ................................................................................................3-1843-178
Table 3-79    CPDLC t-CPDLC-end Timer .............................................................................3-1853-179
Table 3-80    UM160 NEXT DATA AUTHORITY ................................................................3-1863-180
Table 3-81    Sending the VCI..................................................................................................3-1873-181
Table 3-82    Acknowledging the VCI .....................................................................................3-1883-182
Table 3-83    LACK Prohibition...............................................................................................3-1893-183
Table 3-84    Enabling CPDLC ................................................................................................3-1903-184
Table 3-85    CPDLC Connection Establishment.....................................................................3-1913-185
Table 3-86    CPDLC Connection Termination .......................................................................3-1923-185
Table 3-87    DCL Revision Scenarios .....................................................................................3-1963-189
Table 3-88    ATN and FANS 1/A ADS-C Contracts ..............................................................3-1983-191
Table 3-89    ATN and FANS 1/A ADS uplink messages .......................................................3-1993-192
Table 3-90    ATN and FANS 1/A ADS-C Demand Contract Request variables ....................3-2013-194
Table 3-91    ATN and FANS 1/A ADS Periodic Contract Request variables ........................3-2053-197
Table 3-92    Lateral Deviation Change Event .........................................................................3-2103-202
Table 3-93    Vertical Speed Change Event .............................................................................3-2123-204
Table 3-94    Level/Altitude Range Event................................................................................3-2133-205
Table 3-95    Way-point Event .................................................................................................3-2143-206
Table 3-96    ATN and FANS 1/A ADS downlink messages ..................................................3-2153-207
Table 3-97    ATN and FANS 1/A ADS reports ......................................................................3-2173-209
Table 3-98    Basic Data Block / Basic ADS Group ................................................................3-2203-212
Table 3-99    Ground Vector / Earth Reference .......................................................................3-2203-212
Table 3-100   Air Vector / Air Reference..................................................................................3-2213-213
Table 3-101   Projected Profile data block / Predicted Route ...................................................3-2213-213
Table 3-102   Extended Projected Profile data block / Predicted route Group .........................3-2223-214
Table 3-103   Extended Projected Profile data block / Intermediate Projected Intent Group ...3-2233-215
Table 3-104   ATN Ground Vector / Earth Reference ..............................................................3-2243-216
Table 3-105   ATN ADS Reject / FANS 1/A Negative Ack .....................................................3-2253-217
Table 3-106   ATN ATN Cancel Negative Ack / FANS 1/A Positive Ack ..............................3-2273-219
Table 3-107   ATN ATN Cancel Negative Ack / FANS 1/A Negative Ack.............................3-2273-219
Table 3-108   ATN and FANS 1/A ADS positive acknowledgement .......................................3-2283-220
Table 3-109   ATN and FANS 1/A ADS non-compliance notification ....................................3-2283-220
Table 3-110   ATN and FANS 1/A ADS variables with range and resolution .........................3-2323-223
Table 2-1     Advanced data link services and applications................................................................ 2-21
Table 3-1     SMI Downlink and Uplink relationship for FANS 1/A AFN, and CPDLC .................. 3-25
Table 3-2     Valid label/sub-label/MFI/IMI/SMI combinations for FANS 1/A CPDLC uplink ....... 3-25
Table 3-3     Valid label/sub-label/MFI/IMI/SMI combinations for FANS 1/A AFN uplink ............ 3-25
Table 3-4     ATN CM and FANS 1/A AFN primitives ..................................................................... 3-26
Table 3-5     Mapping of parameters into ATN CM primitives and FANS 1/A AFN primitives ...... 3-27
Table 3-6     ATN CM and FANS 1/A AFN variables ....................................................................... 3-30
Table 3-7     ATN CM and FANS 1/A AFN timers ........................................................................... 3-32
Table 3-8     ATN and FANS 1/A CPDLC requirements for time source ......................................... 3-33
Table 3-9     ATN and FANS 1/A CPDLC requirements for timestamp generation.......................... 3-34
Table 3-10    ATN and FANS 1/A CPDLC requirements for message latency .................................. 3-35
Table 3-11    ATN CPDLC constructs and FANS 1/A CPDLC ACARS IMIs .................................. 3-38
Table 3-12    ATN and FANS 1/A CPDLC high-level data structures ............................................... 3-45
Table 3-13    ATN and FANS 1/A CPDLC message attributes .......................................................... 3-46
Table 3-14:   LACK on Downlink Messages ...................................................................................... 3-48
Table 3-15:   LACK on Uplink Messages ........................................................................................... 3-49
Table 3-16    CPDLC Disabling/Enabling Functionality .................................................................... 3-50
Table 3-17    ATN and FANS 1/A CPDLC message headers ............................................................. 3-51
Table 3-18    ATN and FANS 1/A CPDLC uplink message elements................................................ 3-52
Table 3-19    ATN and FANS 1/A CPDLC downlink message elements ........................................... 3-89
Table 3-21    High Level Concatenation Requirements .................................................................... 3-105
Table 3-22    ATN and FANS 1/A CPDLC responses to concatenated messages ............................ 3-106
Table 3-23    ATN and FANS 1/A ERROR information requirements ............................................ 3-107
Table 3-24    ATN and FANS 1/A uplink [error information] data type .......................................... 3-109
Table 3-25    ATN and FANS 1/A downlink [error information] data type ..................................... 3-110
Table 3-26    ATN and FANS 1/A further downlink error information ............................................ 3-113
Table 3-27    ATN and FANS 1/A altitude data type ........................................................................ 3-119
Table 3-28    ATN Level data type sent in FANS UM169 Free Text ............................................... 3-120
Table 3-29    ATN and FANS 1/A distance data type ....................................................................... 3-120
Table 3-30    ATN and FANS 1/A position data type ....................................................................... 3-121
Table 3-31    ATN positionR data type sent in FANS UM169 Free Text ......................................... 3-122
Table 3-32    ATN and FANS 1/A speed data type ........................................................................... 3-123
Table 3-33    ATN speed data type sent in FANS UM169 Free Text ............................................... 3-125
Table 3-34    ATN and FANS 1/A distance offset data type............................................................. 3-126
Table 3-35    ATN and FANS 1/A Time data type ........................................................................... 3-127
Table 3-36    ATN Time data type sent in FANS UM169 Free Text ................................................ 3-127
Table 3-37    ATN Timesec data type sent in FANS UM169 Free Text ........................................... 3-127
Table 3-38    ATN and FANS 1/A vertical rate data type ................................................................. 3-128
Table 3-39    ATN and FANS 1/A Facility data type........................................................................ 3-129
Table 3-40    ATN and FANS 1/A ICAO facility designation data type .......................................... 3-129
Table 3-41    ATN Facility Designation data type sent in FANS UM169 Free Text ........................ 3-130
Table 3-42    ATN and FANS 1/A Unit Id / Unit Name data type.................................................... 3-131
Table 3-43    ATN unit name data type sent in FANS UM169 Free Text ........................................ 3-132
Table 3-44    ATN Number of Degrees and FANS 1/A Degrees data type ...................................... 3-132
Table 3-45    ATN and FANS 1/A route clearance data type............................................................ 3-133
Table 3-46    ATN and FANS 1/A published identifier data type..................................................... 3-135
Table 3-47    ATN and FANS 1/A place bearing distance data type ................................................ 3-136
Table 3-48    ATN and FANS 1/A leg type data type ....................................................................... 3-136
Table 3-49    ATN and FANS 1/A latitude/longitude data type........................................................ 3-137
Table 3-50    ATN and FANS 1/A frequency data type .................................................................... 3-140
Table 3-51    ATN frequency data type sent in FANS UM169 Free Text ........................................ 3-141
Table 3-52    ATN and FANS 1/A code data type ............................................................................ 3-141
Table 3-53    ATN and FANS 1/A Departure clearanceR data type ................................................. 3-141
Table 3-54    ATN and FANS 1/A Procedure Name data type ......................................................... 3-144
Table 3-55    ATN and FANS 1/A Altimeter data type .................................................................... 3-144
Table 3-56    ATN altimeter data type sent in FANS UM169 Free Text .......................................... 3-145
Table 3-57    ATN and FANS 1/A Atis Code data type .................................................................... 3-145
Table 3-58    ATN atis code data type sent in FANS UM169 Free Text .......................................... 3-145
xiv


Table 3-59    ATN and FANS 1/A To/From data type...................................................................... 3-146
Table 3-60    ATN and FANS 1/A position report advanced data type ............................................ 3-146
Table 3-61    ATN and FANS 1/A Remaining Fuel data type .......................................................... 3-148
Table 3-62    ATN and FANS 1/A Persons on Board data type........................................................ 3-148
Table 3-63    ATN and FANS 1/A Version Number data type ......................................................... 3-148
Table 3-64    ATN and FANS 1/A temperature data type ................................................................. 3-149
Table 3-65    ATN and FANS 1/A Vertical Change data type .......................................................... 3-149
Table 3-66    ATN and FANS 1/A Vertical Direction data type ....................................................... 3-150
Table 3-67    ATN and FANS 1/A Turbulence data type.................................................................. 3-150
Table 3-68    ATN and FANS 1/A RTA Time data type .................................................................. 3-151
Table 3-69    Suggested ATN downlink message elements with Y response attribute ..................... 3-152
Table 3-70    ATN uplink message elements with Y response attribute ........................................... 3-157
Table 3-71    ATN UM with W/U Resp and Corresponding FANS Messages with R Resp ............ 3-164
Table 3-72    ATN UM with A/N Resp and Corresponding FANS Messages with R Resp ............. 3-165
Table 3-73    DLIC initiation using ATN CM and FANS 1/A AFN ................................................. 3-167
Table 3-74    DLIC contact using ATN CM and FANS 1/A AFN .................................................... 3-170
Table 3-75    DLIC update using ATN CM and FANS 1/A AFN..................................................... 3-172
Table 3-76    CPDLC t-start timer ..................................................................................................... 3-174
Table 3-77    CPDLC tr Timer .......................................................................................................... 3-174
Table 3-78    CPDLC ttr Timer ......................................................................................................... 3-176
Table 3-79    CPDLC tts Timer ......................................................................................................... 3-177
Table 3-80    CPDLC t-CPDLC-end Timer ...................................................................................... 3-178
Table 3-81    UM160 NEXT DATA AUTHORITY ......................................................................... 3-179
Table 3-82    Sending the VCI........................................................................................................... 3-180
Table 3-83    Acknowledging the VCI .............................................................................................. 3-181
Table 3-84    LACK Prohibition........................................................................................................ 3-182
Table 3-85    Enabling CPDLC ......................................................................................................... 3-182
Table 3-86    CPDLC Connection Establishment.............................................................................. 3-184
Table 3-87    CPDLC Connection Termination ................................................................................ 3-184
Table 3-88    DCL Revision Scenarios .............................................................................................. 3-188
Table 3-89    ATN and FANS 1/A ADS-C Contracts ....................................................................... 3-190
Table 3-90    ATN and FANS 1/A ADS uplink messages ................................................................ 3-191
Table 3-91    ATN and FANS 1/A ADS-C Demand Contract Request variables ............................. 3-193
Table 3-92    ATN and FANS 1/A ADS Periodic Contract Request variables ................................. 3-196
Table 3-93    Lateral Deviation Change Event .................................................................................. 3-201
Table 3-94    Vertical Speed Change Event ...................................................................................... 3-203
Table 3-95    Level/Altitude Range Event......................................................................................... 3-204
Table 3-96    Way-point Event .......................................................................................................... 3-205
Table 3-97    ATN and FANS 1/A ADS downlink messages ........................................................... 3-206
Table 3-98    ATN and FANS 1/A ADS reports ............................................................................... 3-208
Table 3-99    Basic Data Block / Basic ADS Group ......................................................................... 3-211
Table 3-100   Ground Vector / Earth Reference ................................................................................ 3-211
Table 3-101   Air Vector / Air Reference........................................................................................... 3-212
Table 3-102   Projected Profile data block / Predicted Route ............................................................ 3-212
Table 3-103   Extended Projected Profile data block / Predicted route Group .................................. 3-213
Table 3-104   Extended Projected Profile data block / Intermediate Projected Intent Group ............ 3-214
Table 3-105   ATN Ground Vector / Earth Reference ....................................................................... 3-215
Table 3-106   ATN ADS Reject / FANS 1/A Negative Ack .............................................................. 3-216
Table 3-107   ATN ATN Cancel Negative Ack / FANS 1/A Positive Ack ....................................... 3-218
Table 3-108   ATN ATN Cancel Negative Ack / FANS 1/A Negative Ack...................................... 3-218
Table 3-109   ATN and FANS 1/A ADS positive acknowledgement ................................................ 3-219
Table 3-110   ATN and FANS 1/A ADS non-compliance notification ............................................. 3-219
Table 3-111   ATN and FANS 1/A ADS variables with range and resolution .................................. 3-222
xvi




      This page intentionally left blank.
1     INTRODUCTION
      This standard was developed to enable air traffic service providers (ATSPs) to
      interoperate with FANS 1/A data link equipped aircraft. The standard is intended to
      support the goal of converging oceanic and continental data link applications.

1.1   Purpose
      This document provides the interoperability requirements for an aeronautical
      telecommunication network for advanced ATS data communication services (ATN)
      ground system that provides advanced air traffic data link services to future air navigation
      system 1/A (FANS 1/A) aircraft in oceanic and continental airspace.
      Note:     Based on DO-264/ED-78A, INTEROP and SPR standards provide
                recommendations intended for government organizations, conference of
                governments, or agencies having statutory jurisdiction over the use and
                provision of air traffic services supported by data communications. These
                recommendations are for use by such government organizations to enunciate
                official policy, related to such matters, in aeronautical information publications
                (AIPs), notices to airmen (NOTAMs), airplane flight manuals (AFMs), and
                operator specifications.

1.2   Scope
      This standard provides:
          a. Interoperability requirements for the ATN ground system to provide FANS 1/A
             aircraft advanced data link services, as defined by the Continental SPR Standard
             [PU-10]. See paragrap 1.2.1.
          b. Interoperability requirements to ensure seamless transition of ATS                      Comment [PF1]:
             communications for bilingual aircraft (i.e. aircraft equipped with FANS 1/A and         PDR #303 1)
             ATN data link technologies transitions from a FANS 1/A ground system to an
             ATN ground system or vice versa (e.g. FANS 1/A ground system providing data
             link services in an oceanic airspace and an ATN ground system providing data
             link services in a domestic airspace). See paragraph 1.2.2.
      Note 1: This standard provides a separated set of requirements for each of these two
              capabilities, which can be implemented and qualified independently.
      Note 2: Some ATN ATSUs might elect to comply with paragraph 3 only, with
              paragraph 4 only or with both paragraph 3 and paragraph 4. Some FANS 1/A
              ATSUs might elect to comply with paragraph 4. FANS 1/A & ATN bilingual
              aircraft might elect to comply with paragraph 4.
1-18


                                     Ground system                      Aircraft System
                                                                                      FANS 1/A &
                                                                                          ATN
                                   ATN        FANS 1/A       ATN         FANS 1/A
                                                                                       bilingual
                                                                                        aircraft

          § 3 ATN GROUND
         SYSTEM PROVIDING
                                                 Not          Not           Not              Not
           ATS DATALINK          Applicable
                                              Applicable   Applicable    Applicable       Applicable
        SERVICES TO FANS 1/A
              AIRCRAFT

        § 4 GROUND SYSTEMS
           PROVIDING ATS
                                                              Not           Not
         DATALINK SERVICES       Applicable   Applicable                                  Applicable
                                                           Applicable    Applicable
            TO BILINGUAL
              AIRCRAFT

                      Figure 1      Mixed Interoperability Requirements Applicability


1.2.1         ATN Ground System Providing ATS Datalink Services to FANS 1/A Aircraft
              This standard provides interoperability requirements for the ATN ground system to
              provide FANS 1/A aircraft advanced data link services, as defined by the Standard for
              Advanced ATS Data Communications SPR, taking into consideration ICAO material
              listed in paragraph 1.5. The following data link services are considered for the
              FANS 1/A aircraft:
                 Data Link Initiation Capability (DLIC),
                 ATC Communications Management (ACM),
                 Clearance Request and Delivery (CRD),
                 Information Exchange and Reporting (IER),
                 Position Reporting (PR),
                 4D Trajectory (4DTRAD (Initial Trajectory Based Operation)),
                 ATC Microphone Check (AMC), and
                 Departure Clearance (DCL).
              Note 1: This standard considers message elements of the CPDLC application that are
                      included in the “version 2” message set as defined by the ATS INTEROP
                      Standard to support advanced data link services and the FANS 1/A aircraft
                      emergency data communication capability. See paragraph 3.2.2.8 for the
                      uplink CPDLC message elements and paragraph 3.2.2.9 for the downlink
                      CPDLC message elements considered within the scope of this document.
              Note 2: This standard considers all the message element parameters and data types of
                      the CPDLC application that are included in the ATS INTEROP Standard for
                                                                                             1-19


                 the message elements in the “version 2” message set. See paragraph 3.2.2.12
                 for message element parameters and data types.
        Note 3: This standard does not consider some CPDLC-based services (D-TAXI, FIM)
                as defined in the Standard for Advanced ATS Data Communications SPR.
        Note 4: This standard does not consider the Flight Information Service (FIS)
                application (D-OTIS, D-RVR and D-HZWX).
        Note 5: The scope of this document has been determined based on the need at the time
                this standard was developed. This standard may be revised at a later time as
                experience is gained, and to expand the scope as the need arises to include, for
                example, the interoperability requirements to provide continental data link
                services to aircraft in a mixed technology environment, and the interoperability
                requirements for the FANS 1/A ground system to provide oceanic data link
                services to ATN aircraft.
        This standard addresses ADS-C by identifying the differences between the ATN and
        FANS1/A ADS-C protocols from the perspective of a Ground System willing to provide
        ADS-C services to both types of aircraft.
1.2.2   Ground Systems Providing ATS Datalink Services to Bilingual Aircraft
        This standard also provides Interoperability Requirements to ensure seamless transition
        of ATS communications when a transition between two adjacent airspaces requires the
        aircraft to switch between different ATS datalink technologies (e.g. FANS 1/A in oceanic
        area vs ATN in domestic area). These requirements will apply only for aircraft claiming
        the capability to adapt the technology used for ATS Datalink communications in avionics
        according to the flown area (so called, “Bilingual aircraft”).

1.3     Relationships to other Documents
        Figure 2Figure 2Figure 2 is used to illustrate the relationships between the standards. In   Formatted: Cross-Reference
        addition to ICAO material, this standard is intended for use in conjunction with the         Formatted: Cross-Reference
        following RTCA/EUROCAE documents:
           PU-10, ATS SPR (Safety and Performance Requirements Standard for Advanced
            ATS Data Communications) [ref d.], which provides the definition of the term,
            “advanced data link services,” as used in this document.
           DO-258A/ED-100A, FANS 1/A Interoperability (INTEROP) Standard [ref. c],
            which provides the definition of the terms, “FANS 1/A aircraft” and “FANS 1/A
            ground system,” as used in this document.
           PU-20, ATS INTEROP Standard [ref. b], which provides the definition of the terms,
            “ATN ground system” and “ATN aircraft,” as used in this document.
           DO-264/ED-78A, Guidelines for the Provision and Use of Air Traffic Services
            Supported by Data Communications [ref. a], for provides guidance material for
            implementation and approval of air traffic data link services.
1-20




                                              FANS Overview
                                                     Aircraft Systems


                                                                           DO-306/ED-122
                                                                             FANS 1/A
                                                                           Continental &
                                                                          Oceanic Services




             DO-258A                                                  DO-258A                      Interoperability &
             ED-100A                                                  ED-100A                       Accommodation
             FANS ACC      ED-YYY                   DO-280            DO-305                    DO-258A
               Interop     Interop                  ED-110B           ED-154                    ED-100A
              Scope of
             INTEROP




                        DO/ED-YYY                DO-290/ED-120                                DO-306/ED-122
                       Y3 (Over ATN)             ATN Baseline 1                                 FANS 1/A
                         Oceanic &             Continental Services                          Oceanic Services
                    Continental Services
                                                    Ground Systems


                                                                                                                                  Comment [PF2]:
                                           “Mixed Technology”Environments                                                         PDR 303 2)

                                                           Technology
                                                                                                                  Remarks
                                       Ground System                        Aircraft System

                                                                                FANS 1/A                        Initial Release
                                             ATN
                                                                           FANS 1/A & ATN
                                                                                                                    Rev A
                                                                           Bilingual Aircraft

                                                                                     ATN                        Not considered
                                           FANS 1/A
                                                                           FANS 1/A & ATN
                                                                                                                    Rev A
                                                                           Bilingual Aircraft

                                     Figure 2         Mixed technology environments


       This INTEROP standard is developed in accordance with the guidelines of
       DO-264/ED-78A taking into account experience gained from the production of other
       INTEROP Standards. For the ATN ground system intending to provide continental data
       link services to FANS 1/A aircraft, this INTEROP standard can be used as evidence of
       the interoperability assessment using a mixture of FANS 1/A and ATN Advanced
       Services Data Link technologies.
       This evidence provides the basis for qualifying implementations to the interoperability
       requirements for elements of the CNS/ATM system, taking into consideration the
       operational, safety, and performance requirements provided by the Standard for
                                                                                             1-21


        Advanced ATS Data Communications and relevant ICAO material. It is noted that this
        document alone does not satisfy all the requirements for approval and implementation.
        For example, a specific implementation will need to ensure compliance with the
        operational, safety, and performance requirements, provided in the Standard for
        Advanced ATS Data Communications, and other requirements stated by the appropriate
        regulatory authority. Applicants will have to show for approval that this INTEROP
        standard is viable for the relevant SPR standards as per Sections 5 and 6 of
        DO-264/ED-78A.
        Note:    When this INTEROP standard is recognized in AIPs, NOTAMs, AFMs, and
                 operator’s specifications, such recognition and other unique characteristics
                 affecting interoperability for a specific air traffic service provision, aircraft
                 type design, or operator’s operation can be found in the respective documents.

1.4     Description of this Document
1.4.1   Document Conventions
        The following conventions are used in this document:
        This document provides mandated criteria, i.e. the criteria are mandatory and no
        alternative may be applied to the ATN ground system providing advanced data link
        services to FANS 1/A aircraft. The mandated criteria take the form of interoperability
        requirements. Each requirement is prefaced with the nomenclature, IR-[x], where [x] is a
        sequential number. In some cases, the word “shall” appears in a statement that was taken
        from another document, e.g., the ATS INTEROP Standard or ICAO Doc 9880. These
        criteria are considered mandatory by their respective reference.
        Note:    In an approval context, the “shalls” are considered a mandated criterion if
                 the:
                  Applicant defines this standard, in conjunction with relevant INTEROP
                   standards, and any adaptation (Refer to RTCA DO-264/EUROCAE
                   ED-78A, paragraph 1.3.3), as the approval basis, and
                  Approval authority accepts this approval basis.
                 The approval basis defines the criteria for compliance. “Shoulds” are typically
                 used to describe guidelines for the processes used to produce elements of the
                 system or for meeting the mandated criterion.
        The use of the word “should” is not used in this document in any particular context other
        than normal use. Text that appears in this standard that is not prefaced by IR-[x] can
        have the following meaning:
            1)   To aid in the understanding of the mandatory criterion or as guidance material;
                 and
            2)   In cases where “No additional interoperability requirement” is stated in a table
                 row, no additional interoperability requirements are necessary for specific item
                 described in the row. It is noted, however, that the interoperability
                 requirements provided in the cross-referenced paragraphs for that item are
                 applicable.
1-22


        This document normally refers to the Standard for Advanced ATS Data Communications,
        the ATS Advanced Services INTEROP Standard (ATS INTEROP), and the FANS 1/A
        INTEROP Standard. In some cases, where these standards do not provide sufficient
        detail to describe the interoperability requirements, reference will be made to other
        documents. For example, in some cases direct reference is made to ICAO Doc 9880. In
        these cases, the reference is ICAO Doc 9880, as modified by the resolutions to the
        Problem Defect Reports (PDRs) provided in the ATS INTEROP Standard.
        This document refers to FANS 1/A+ as defined in DO-258A/ED-100A throughout the
        document as FANS 1/A.
1.4.2   Document Organization
           Section 1 – Provides an introduction to the Interoperability Requirements Standard
            for FANS-ATN systems.
           Section 2 – Provides FANS-ATN system description and operational considerations.
           Section 3 – Defines the interoperability requirements for ATN ground system
            providing ats datalink services to FANS 1/A aircraft.
                 Section 3.1 – Defines the interoperability requirements for the FANS-ATN
                  system Communication requirements.
                 Section 3.2 – Defines the interoperability requirements for the FANS-ATN
                  system requirements for Data Link Applications.
                 Section 3.3 – Defines the interoperability requirements for the FANS-ATN
                  system dynamic functions/operations of Data Link services.
                 Section 3.4 – Provides interoperability guidelines for the FANS-ATN system
                  providing ADS-C based Data Link services.
           Section 4 – Defines the interoperability requirements for ground systems providing
            ATS datalink services to bilingual aircraft.
           Appendix A – Lists the members of RTCA SC-214/EUROCAE WG-78.
           Appendix B – Provides the history of this document and its relationship to the terms
            of reference of SC-214/WG-78.
           Appendix C – Is an improvement suggestion form for this document.
1.4.3   Acronyms and Glossary of Terms
        The following acronyms and terms are consistent with those used in the
        DO-264/ED-78A, the SPR Standards, and the INTEROP Standards referenced in this
        document.
        ACRONYMS
        Acronym         Description


        ACM             ATC Communication Management (service)
                                                                                1-23


Acronym    Description
ADS        Automatic Dependent Surveillance
AFN        ATC Facility Notification
AMC        ATC Microphone Check (service)
ATC        Air Traffic Control
ATIS       Automatic Terminal Information Service
ATN        Aeronautical Telecommunication Network
ATS        Air Traffic Services
ATSP       Air Traffic Service Provider
ATSU       Air Traffic Service Unit
C-ATSU     Current/Controlling Air Traffic Service Unit
CDA        Current Data Authority
CM         Context Management
CNS/ATM    Communication, Navigation, and Surveillance/Air Traffic Management
CPDLC      Controller Pilot Data Link Communication
CRD        Clearance Request and Delivery
CSP        Communication Service Provider
D-ATIS     Data link Automatic Terminal Information Service
DCL        Departure Clearance (service)
DLIC       Data Link Initiation Capability (service)
DM         Downlink Message
DSC        Downstream Clearance (service)
EOBT       Estimated Off Block Time
ETD        Estimated Time of Departure
FIS        Flight Information Service
FMS        Fight Management System
FOM        Figure Of Merit
ICAO       International Civil Aviation Organization
IER        Information Exchange and Reporting
IMI        Imbedded Message Identifier
INTEROP    Interoperability Requirement Standard
Standard
LACK       Logical Acknowledgement
MAS        Message Assurance
1-24


       Acronym            Description
       MFI                Message Format Identifier
       NDA                Next Data Authority
       OSD                Operational Service Description
       PDU                Protocol Data Unit
       R-ATSU             Receiving Air Traffic Service Unit
       SMI                Standard Message Identifier
       SPR Standard       Safety and Performance Requirements Standard
       T-ATSU             Transferring Air Traffic Service Unit
       UM                 Uplink Message
       VCI                Voice Contact Information
       VHF                Very High Frequency
       WILCO              Will Comply



       GLOSSARY OF TERMS
       The terms used in this document specifically for Interoperability are defined below.
       Generic terms are defined in the SPR [ref. d].

       Term                             Definition
       Abstract Syntax Notation One Abstract syntax notation One is defined in ISO/IEC 8824-1. The
       (ASN.1)                      purpose of this notation is to enable data types to be defined,
                                    and values of those types specified, without determining their
                                    actual representation (encoding) for transfer by protocols. (Refer
                                    ICAO Doc 9705)
       Aeronautical                     A network comprising application entities and communication
       Telecommunication Network        services which allow ground, air-to-ground and avionics data
       (ATN)                            subnetworks to interoperate by adopting common interface
                                        services and protocols based on the International Organization
                                        for Standardization (ISO) open systems interconnection (OSI)
                                        reference model. (Refer ICAO Doc 9705)
       Aircraft address                 A unique combination of 24 bits available for assignment to an
                                        aircraft for the purpose of air-ground communications,
                                        navigation and surveillance. (Refer ICAO Doc 4444)
       Aircraft flight identification   A group of letters, figures or a combination thereof, which is
                                        either identical to, or the coded equivalent of the aircraft call
                                        sign to be used in air-ground communications, and which is
                                        used to identify the aircraft in ground-ground ATS
                                        communication. (Refer ICAO Doc 9705)
                                                                                                1-25


Term                        Definition
Aircraft identification     A group of letters, figures or a combination thereof, which is
                            either identical to, or the coded equivalent of the aircraft call
                            sign to be used in air-ground communications, and which is
                            used to identify the aircraft in ground-ground ATS
                            communication. (Refer ICAO Doc 4444)
Air Traffic Services Unit   A generic term meaning variously, ATC unit, flight information
(ATSU)                      centre, or ATC service area control services reporting office. In
                            this document, ATSU refers to both human operators (e.g.
                            controllers) and automated systems (e.g. data processing
                            systems) at an ATSU, unless specifically stated otherwise.
                            (Refer ICAO Doc 4444)
Bilingual aircraft          An aircraft implementing both FANS 1/A (in compliance with                 Comment [PF3]:
                                                                                                       PDR #303 3)
                            DO-258A/ED-100A) and ATN (in compliance with PU-20)
                            applications, capable of switching between the two technologies
                            to allow seamless ATS communications transition between two
                            adjacent ATSUs, one using FANS 1/A and the other using
                            ATN.
CPDLC message               A CPDLC message that includes data for the application user to
                            verify the integrity and the correct delivery of each individual
                            message.
Current ATS Unit (C-ATSU)   In ACM context: The ATSU that can exchange ATC
                            communications messages with an aircraft. (Refer the
                            Continental SPR Standard)
                            Controlling ATSU - The air traffic control unit exercising legal
                            authority over the initiation, continuation, diversion or
                            termination of flights and providing air traffic control service to
                            controlled flights in the control area under its jurisdiction.
                            (Refer Doc 9705)
Enabled                     In the context of CPDLC, refers to a connection, which has been
                            activated for operational exchanges. To become enabled, a
                            CPDLC connection must have CDA status in accordance with
                            the ATN INTEROP standard, or equivalent, when providing
                            data link services to FANS 1/A aircraft, as specified in this
                            document.
End System (ES)             A system that contains the human-machine interface,
                            application processing, and is distinct from system components
                            interfacing the communication services. (Refer the Continental
                            SPR Standard)
                            Note: This definition is modified from RTCA DO-
                            264/EUROCAE ED-78A to remove technological dependencies.
1-26


       Term                        Definition
       Receiving ATS Unit          In ACM context: The next ATSU that the aircraft will enter.
       (R-ATSU)                    (Refer the Continental SPR Standard)
                                   Receiving ATSU - The next air traffic control unit which is the
                                   process of accepting the control authority and communication
                                   responsibility for a flight transferred by the controlling ATSU
                                   (C-ATSU). (Refer ICAO Doc 9705)
       Transferring ATS Unit       In ACM context: The ATSU that the aircraft is about to leave.
       (T-ATSU)                    (Refer the Continental SPR Standard)




1.5    References
       The references cited in this INTEROP standard are listed below:
       a)   RTCA DO-264/EUROCAE ED-78A, Guidelines for Approval of the Provision and
            Use of Air Traffic Services Supported by Data Communications;
       b)   RTCA/EUROCAE PU-20, Interoperability Requirements Standard for Advanced
            ATS Data Communications (ATS INTEROP Standard);
       c)   RTCA DO-258A/EUROCAE ED-100A, Interoperability Requirements Standard for
            FANS1/A (FANS 1/A INTEROP Standard);
       d)   RTCA/EUROCAE PU-10, Safety and Performance Requirements Standard for
            Advanced ATS Data Communications;
       e)   ICAO Annex 2 — Rules of the Air;
       f)   ICAO Annex 10 — Aeronautical Telecommunications                        -   Volume        II
            (Communications Procedures including those with PANS status);
       g)   ICAO Annex 11 — Air Traffic Services;
       h)   ICAO Doc 4444, Edition 15 – Procedures for Air Navigation Services – Air Traffic
            Management; and
       i)   ICAO Doc 9880 Edition 1 – Manual of Technical Provisions for the Aeronautical
            Telecommunications Network (ATN).
                                                                                                2-27



2   DESCRIPTION AND OPERATIONAL CONSIDERATIONS
    This section provides a description and operational considerations for the ATN ground
    system providing FANS 1/A aircraft the advanced services data link services as defined
    in the Standard for Advanced ATS Data Communications and as limited by the scope of
    this document provided in paragraph 1.2.1.
    Table 2-1Table 2-1Table 2-1 presents a mapping between advanced data link services,                Formatted: Cross-Reference
    ATN applications and FANS 1/A applications. The table includes references to the                   Formatted: Cross-Reference
    paragraphs in this document that provide interoperability requirements for the ATN
    ground system providing continental data link services to FANS 1/A aircraft.
                  Table 2-1     Advanced data link services and applications

    Advanced Data      ATN Application      FANS 1/A           Reference
    Link Service                            Application
    DLIC               CM                   AFN                Paragraphs 3.2.1, 3.3.1
    ACM                CPDLC                CPDLC              Paragraphs 3.2.2, 3.3.2.2
    CRD, IER, OCL      CPDLC                CPDLC              Paragraphs 3.2.2, 3.3.2.3
    AMC                CPDLC                CPDLC              Paragraphs 3.2.2, 3.3.2.5
    DCL                CPDLC                CPDLC              Paragraphs 3.2.2, 3.3.2.4
    ITBO               CPDLC, ADS-C         CPDLC, ADS-C       Paragraphs 3.2.2, 3.3.2.6, 3.4
    PR                 CPDLC, ADS-C         CPDLC, ADS-C       Paragraphs 3.2.2, 3.4
    D-TAXI,                                                    Not provided to FANS1/A
    4DTRAD, FIM,                                               aircraft.
    D-OTIS, D-RVR,
    D-HZWX



    The ATN applications for the ground system and the aircraft are defined using Context
    Management (CM) and CPDLC applications, as defined in the ATS INTEROP Standard.
    The ATS INTEROP Standard provides a mapping to the data link services.
    The FANS 1/A applications for the ground system and the aircraft are defined in terms of
    the definition of the ATC Facility Notification (AFN) and CPDLC applications, as
    defined in the FANS 1/A INTEROP Standard. This document provides a mapping of
    these complete definitions to sequence of operations for the data link services using either
    the ATN or FANS 1/A technology. There are many similarities even though the
    nomenclatures are different. Both the ATN and the FANS 1/A technologies use similar
    methods for defining dynamic operation.
2-28


2.1     Data Link Initiation Capability
        The data link initiation capability is accomplished using CM by ATN aircraft, and using
        AFN by the FANS 1/A aircraft.
2.1.1   ATN CM Application
        The CM application enables an ATN ground system to become aware of an aircraft’s data
        link capabilities. The CM application does not establish communication between the
        airborne and ground peers of data link applications; this is done by the applications
        themselves. ATN aircraft provide the application name, address, and version number for
        each supported ground-initiated application. In addition, an ATN ground system requires
        that the aircraft provide flight plan association data. This information includes the airport
        departure (required), airport destination (required), and the estimated time of departure (if
        available). The ground system responds by providing the flight identification, application
        name and version number for each ground-initiated application that is used to provide a
        continental data link service.
        In addition to application name and version number, the ATN ground system provides the
        address information (for air-initiated applications) in the CM logon response.
        The ATN ground system and ATN aircraft use only the CM Logon, CM Contact, and
        CM Update operational functions and the CM Abort (user and provider) functions.
2.1.2   FANS 1/A AFN Application
        The ATS Facilities Notification (AFN) application enables an ATS ground system to
        become aware of an aircraft’s data link capabilities. The AFN does not establish
        communications between the airborne and ground peers of data link applications; this is
        done by the applications themselves. Airborne systems provide the flight identification,
        application name and version number for each supported application. AFN consists of an
        AFN Contact and a Contact Advisory function.

2.2     CPDLC Application
        The CPDLC application enables pilots and controllers to exchange messages via data
        link. The CPDLC application includes a set of clearance/information/request message
        elements used for air traffic control.
2.2.1   ATN CPDLC Application
        The ATN CPDLC application includes the message elements defined in the Advanced
        Service SPR.
        The ATN CPDLC message elements encompass level assignments, crossing constraints,
        route modifications and clearances, speed assignments, radio frequency assignments, and
        various requests for information. The pilot is provided with the capability to respond to
        messages, to request some types of clearances and information, and to report information.
        An uplink "free text" capability is also provided to exchange information not conforming
        to defined formats and to append information explaining error reasons. A downlink "free
        text" capability is also provided to only to append information explaining error reasons.
                                                                                               2-29


2.2.2   FANS 1/A CPDLC Application
        The FANS 1/A INTEROP Standard specifies a set of message elements, similar to the
        defined CPDLC message elements set in Doc 4444. FANS 1/A CPDLC message
        elements encompass altitude assignments, crossing constraints, lateral offset deviations,
        route modifications and clearances, speed assignments, radio frequency assignments, and
        various requests for information. The pilot is provided with the capability to respond to
        messages, to request clearances and information, to report information, and to
        declare/cancel an emergency. A "free text" capability is also provided to exchange
        information not conforming to defined formats.

2.3     ADS-C Application Description
        This appendix provides guidance for determining the interoperability requirements for the
        ATN ground system to use the FANS 1/A+ aircraft Automatic Dependent Surveillance
        (ADS-C) application.
        The ADS-C application is an air-ground ATS data link application, in which airborne
        systems transmit automatically data derived from onboard navigation and flight
        management systems in response to ground-initiated contract request. As a minimum, the
        data include three-dimensional position, the corresponding estimated time for the position
        data, and a Figure of Merit (FOM).
2.3.1   ATN ADS-C Application
        As defined in document the ATN INTEROP Standard, three contract types may be used:
        demand, event and periodic.
        The ADS report contains basic information (three-dimensional position, the
        corresponding estimated time for the position data, and a Figure of Merit). Additional
        data can be included: aircraft address and identification, air and ground vectors, projected
        and extended projected profiles, meteorological data, emergency/urgency status.
        All three contract types can be used in the ATN INTEROP Standard.
2.3.2   FANS 1/A ADS Application
        The FANS 1/A INTEROP Standard defines three contract types: Event, Periodic and
        Demand.
        FANS 1/A aircraft use two contract tag types: event and periodic. The FANS 1/A
        demand contract is a periodic contract with reporting rate set to 0.
        As a minimum, the ADS report consists of the basic group (three-dimensional position,
        the corresponding estimated time for the position data, and a Figure of Merit). Additional
        data can be included: flight and airframe identification, ground and air vectors,
        meteorological data, predicted route, fixed and intermediaite projected intent.
3-30



3      ATN GROUND SYSTEM PROVIDING ATS DATALINK SERVICES TO FANS
       1/A AIRCRAFT

3.1    COMMUNICATION REQUIREMENTS
       This section provides interoperability requirements for the FANS 1/A communication
       protocols and application addressing. These requirements are additional to those
       provided in the FANS 1/A INTEROP Standard or the ATS INTEROP Standard either
       specifically or by reference.
       IR-1             The ATN ground system shall support ACARS based Air-Ground
       communication protocols, as per the FANS 1/A Interoperability Standard.
       IR-2             The ATN ground system shall keep track of the SMI used and apply the
       corresponding uplink SMI (Ref [f]) for all uplinks to the FANS 1/A aircraft as shown in
       Table 3-1Table 3-1Table 3-1.                                                              Formatted: Cross-Reference, Font: 11 pt
       IR-3             When the FANS 1/A aircraft does not use an MFI in downlink messages,     Formatted: Cross-Reference, Font: 11 pt
       the ATN ground system shall use the appropriate uplink SMI (Ref [f]) for each
       application as given in Table 3-1Table 3-1Table 3-1.                                      Formatted: Cross-Reference, Font: 11 pt
       IR-4             When the FANS 1/A aircraft uses an MFI in downlink messages, the         Formatted: Cross-Reference, Font: 11 pt
       ATN ground system shall use the appropriate uplink SMI (Ref [f])/MFI for each uplink
       message as given in Table 3-2Table 3-2Table 3-2 and Table 3-3Table 3-3Table 3-3.          Formatted: Cross-Reference, Font: 11 pt

       The following notes apply to Table 3-1Table 3-1Table 3-1, Table 3-2Table 3-2Table 3-2,    Formatted: Cross-Reference, Font: 11 pt

       Table 3-3Table 3-3Table 3-3.                                                              Formatted: Cross-Reference, Font: 11 pt
                                                                                                 Formatted: Cross-Reference, Font: 11 pt
       Note 1: For SMI uplink, ‘x’ may take the value D, L, R, or 3.
                                                                                                 Formatted: Cross-Reference
       Note 2: For SMI downlink, ‘y’ may take the value L, R, or 3.
                                                                                                 Formatted: Cross-Reference
       Note 3: For label/sub-label, ‘z’ may take the value 1, 2, or 3.                           Formatted: Cross-Reference
       Note 4: The SMI of the AFN Contact (FN_CON) message can be used to determine the          Formatted: Cross-Reference
               appropriate addressing method for a particular aircraft.                          Formatted: Cross-Reference
       Note 5: ACARS uplink messages use a combination of label and sub-label to identify        Formatted: Cross-Reference
               the avionics device to which the message is being sent. The communication
               service provider converts the Standard Message Identifier (SMI) contained in
               the ground-ground message to the appropriate label/sub-label (and MFI)
               combination to allow the avionics to route the message to the appropriate
               airborne end-system.
                                                                                                    3-31


          Table 3-1      SMI Downlink and Uplink relationship for FANS 1/A AFN, and
                                                  CPDLC
      End System         AFN SMI                   CPDLC SMI                   ADS SMI
      Type
                         Uplink       Downlink     Uplink          Downlink    Uplink    Downlink


      ACARS              AFU          AFD          ATC             ATC         RAR       PAR
      management
      function (MU)
      Flight             FMx          FMy          FMx             FMy         FMx       FMy
      management
      system



          Table 3-2      Valid label/sub-label/MFI/IMI/SMI combinations for FANS 1/A
                                                 CPDLC uplink
      End System         CPDLC                                     ADS
      Type
                         Label/        MFI       IMI       SMI     Label/      MFI      IMI    SMI
                         Sub-label                                 Sub-label

      ACARS              AA            (none)    AT1       ATC     A6          (none)   ADS    RAR
      management                                 CR1
      function (MU)                              DR1
                                                 CC1
      Flight             H1/Mz         AA        AT1       FMx     H1/Mz       A6       ADS    FMx
      management                                 CR1
      system                                     DR1



      Table 3-3       Valid label/sub-label/MFI/IMI/SMI combinations for FANS 1/A AFN
                      uplink
             End System Type         AFN
                                     Label/       MFI        IMI         SMI
                                     Sub-label

             ACARS                   A0           (none)     AFN         AFU
             management
             function (MU)
             Flight management       H1/MD        A0         AFN         FMx
             system




3.2   REQUIREMENTS FOR DATA LINK APPLICATIONS
      This section provides the interoperability requirements to enable FANS 1/A applications
      on aircraft to use the advanced data link services provided by the ATN ground system.
3-32


          IR-5            The ATN ground system shall implement an ACARS compatible system
          (ACS) that will enable the ACARS network to support ATS applications (ACS provides
          formatting/addressing, cyclic redundancy check (CRC) integrity check and bit-to-
          hexadecimal conversion process), as per the FANS 1/A Interoperability Standard.
3.2.1     CM/AFN Application Requirements
3.2.1.1   ATN CM and FANS 1/A AFN Primitives
          Table 3-4Table 3-4Table 3-4 lists the ATN CM primitives along with the comparable               Formatted: Cross-Reference
          FANS 1/A AFN primitives.                                                                        Formatted: Cross-Reference



                          Table 3-4   ATN CM and FANS 1/A AFN primitives

          ATN CM Primitives      FANS 1/A AFN Primitives   Interoperability Requirement

          CM Logon Request       AFN Contact               None.

          CM Logon Response      AFN Acknowledge           None.

          CM Update              No equivalent.            The ATN ground system cannot issue an
                                                           update to the FANS 1/A aircraft.

          CM Contact Request     AFN Contact Advisory      None.

          CM Contact Response    AFN Response + AFN        IR-6               When expecting a CM
                                 Complete                  Contact response, the ATN ground system
                                                           shall be able to process the sequence of the
                                                           reception of AFN response and AFN
                                                           Complete.
                                                           Reception of the AFN Response followed by
                                                           AFN Complete is functionally equivalent to
                                                           the CM Contact Response.
                                                           When the AFN Complete is received, a
                                                           subsequent AFN Response can be ignored.

          CM Abort               No equivalent.            The ATN ground system cannot issue an abort
                                                           to the FANS 1/A aircraft. Both sides may
                                                           time-out.
                                                                                                               3-33


3.2.1.2   ATN and FANS 1/A Primitive Parameters
          Table 3-5Table 3-5Table 3-5 maps ATN CM primitive parameters to FANS 1/A AFN                                Formatted: Cross-Reference
          primitive parameters.                                                                                       Formatted: Cross-Reference



           Table 3-5     Mapping of parameters into ATN CM primitives and FANS 1/A AFN
                                                     primitives
          ATN CM Primitive                FANS 1/A AFN Primitives       Interoperability Requirement
          Parameters                      Parameters
          CMLogonRequest:                 AFN Message header:           IR-7                 The ATN ground
                                                                        system shall use the Flight ID and the
           Facility Designation             Flight ID
                                                                        Aircraft Registration to perform the flight
           Aircraft Address (24-bit         Aircraft Registration       plan association.
           address)                         24-bit aircraft address     The FANS 1/A aircraft does not provide
           Logon Request                    (optional)                  the Departure Airport and the Destination
           Aircraft Flight                Note: Some aircraft may       Airport used for the flight plan
           Identification                 provide the 24-bit aircraft   association when required.
           CM Long TSAP(Aircraft          address.                      The ATN ground system does not use the
           CM application address)          Timestamp                   class of communication.
           Ground-initiated application   AFN Contact:                  The FANS 1/A aircraft does not provide
           Information (for all             Aircraft Position           the Air-only-initiated application
           supported applications):                                     information.
                                            Active Flag
             Application name,              Application Name (for all
             Application address,           supported applications)
             Application version            Version Number (for all
             number                         supported applications)
           Air-only-initiated
           application
           Information (for all
           supported applications):
             Application name,
             Application version
             number
           Facility Designation
           (optional)
           Departure Airport
           Destination Airport
           ETD (optional)
           Class of Communication
           (optional)
3-34


       ATN CM Primitive               FANS 1/A AFN Primitives       Interoperability Requirement
       Parameters                     Parameters
       CMLogonResponse                AFN Message header:           IR-8                 The ATN ground
       (successful):                                                system shall generate the AFN
                                        Flight ID
                                                                    acknowledge containing an overall
       List of Application              Aircraft Registration       reason code fixed to (0) as a successful
       Information:
                                        24-bit aircraft address     CM logon response.
       Application name                 (optional)                  The airborne system uses facility
       Application version number     Note: Some aircraft may       designation or the ATC centre address to
       Application address            provide the 24-bit aircraft   associate the AFN acknowledge.
       Note: Application address is   address.                      The application version number cannot
       only given for air-initiated     Timestamp                   be provided in the AFN acknowledge. A
       applications                   AFN Acknowledge (positive):   positive AFN Acknowledgement is only
                                                                    sent when the ground system can support
                                        Overall Reason Code (0)     the application version number given in
                                        Facility Designation        the AFN Contact.
                                      Optional variables:           See paragraph 3.2.1.3 for use of name
                                        Application Name(s)         variable.
                                        Reason Code
                                      Originating ATC Centre
                                      Address (optional)
       Or                             Or
       CMLogonResponse (not           AFN Message header:           IR-9                The ATN ground
       successful):                                                 system shall generate the AFN
                                        Flight ID
                                                                    acknowledge containing an overall
       Note: In this case, the ATN      Aircraft Registration       reason code fixed to (non-0) as an
       ground system does not
                                        24-bit aircraft address     unsuccessful CM logon response.
       provide ground application
       information.                     (optional)                  In this case, the ATN ground system does
                                      Note: Some aircraft may       not provide application name variables in
                                      provide the 24-bit aircraft   a negative AFN acknowledge.
                                      address.
                                        Timestamp
                                      AFN Acknowledge (negative)
                                        Overall Reason Code (non
                                        0)
                                        Facility Designation
                                      Optional variables:
                                        Application Name(s)
                                        Reason Code
                                        Originating ATC Centre
                                        Address
                                                                                                  3-35


ATN CM Primitive                FANS 1/A AFN Primitives       Interoperability Requirement
Parameters                      Parameters
CMContactRequest:               AFN Message header:           IR-10              When requesting a
                                                              CMContactRequest, the ATN ground
 Aircraft Address                 Flight ID
                                                              system shall send the AFN Contact
 Facility Designation             Aircraft Registration       Advisory.
 Facility Designation (the        24-bit aircraft address     See paragraph 3.2.1.3 for use of
 next centre to be contacted)     (optional)                  variables.
 address (CM application        Note: Some aircraft may
 address representing the       provide the 24-bit aircraft
 next ATC centre to be          address.
 contacted)                       Timestamp
 Class of Communications        AFN Contact Advisory:
 (optional)
                                  Next Centre Address
                                  Active Flag
CMContactResponse               Positive indication:          IR-11                The ATN ground
(successful):                                                 system shall process the reception of an
                                AFN Message header:
                                                              AFN Complete (regardless of the reason
- Response (0)                    Flight ID                   code value) as the reception of a
                                  Aircraft Registration       successful CM Contact Response.
                                  24-bit aircraft address     The ATN ground system may ignore the
                                  (optional)                  reception of positive AFN Response.
                                Note: Some aircraft may       In the FANS 1/A INTEROP Standard,
                                provide the 24-bit aircraft   the AFN Complete indicates the result of
                                address.                      the AFN Logon with the next Centre. In
                                  Timestamp                   the ATS INTEROP Standard, a
                                                              successful CM Contact Response
                                AFN response                  indicates that the CM Logon has been
                                  Reason Code (0)             performed without any information on
                                                              the logon response.
                                And:                          The ATN ground system may ignore the
                                                              next Centre address parameter contained
                                                              in the AFN Complete message.
                                AFN Message header:
                                  Flight ID
                                  Aircraft Registration
                                  24-bit aircraft address
                                  (optional)
                                Note: Some aircraft may
                                provide the 24-bit aircraft
                                address.
                                  Timestamp
                                AFN Complete
                                  Next Centre Address
                                  Reason Code
3-36


          ATN CM Primitive             FANS 1/A AFN Primitives       Interoperability Requirement
          Parameters                   Parameters
          CMContactResponse            Negative indication:          IR-12             The ATN ground
          (unsuccessful):                                            system shall process the reception of a
                                       AFN Message header:
                                                                     negative AFN Response like the
          - Response (1)                 Flight ID                   reception of a negative CM Contact
                                         Aircraft Registration       Response.
                                         24-bit aircraft address
                                         (optional)
                                       Note: Some aircraft may
                                       provide the 24-bit aircraft
                                       address.
                                         Timestamp
                                       AFN response
                                         Reason Code (non-0)



3.2.1.3   ATN CM and FANS 1/A AFN Variables
          Table 3-6Table 3-6Table 3-6 maps the ATN CM variables to the comparable FANS 1/A                       Formatted: Cross-Reference
          AFN variables.                                                                                         Formatted: Cross-Reference



                           Table 3-6      ATN CM and FANS 1/A AFN variables
          ATN CM Variables             FANS 1/A AFN Variables        Interoperability Requirement
          Address (LongTSAP of Next    Next Centre Address           IR-13              The ATN ground
          Centre)                                                    system shall map the CM-address of the
                                                                     next ATC Centre to the next ATC Centre
                                                                     Address.
                                                                     IR-14              The ATN ground
                                                                     system shall process the address as the
                                                                     Next Centre address.
          No equivalent.               Originating ATC Centre        IR-15              When providing the
                                       address                       originating ATC centre address in the
                                                                     positive AFN acknowledgement, the
                                                                     ATN ground system shall set it as the
                                                                     same value as the ATC centre address
                                                                     received in the ACARS header of the
                                                                     AFN Contact.
          AP Address                   No equivalent.                None.
                                                                     Information is available in the ACARS
                                                                     Header.
                                                                     The Aircraft Registration and the SMI
                                                                     (representing MFI or label) and IMI serve
                                                                     as the application address for all
                                                                     applications (i.e. AFN, ADS and
                                                                     CPDLC).
                                                                                                       3-37


ATN CM Variables                FANS 1/A AFN Variables         Interoperability Requirement
AE Qualifier                    AP_name                        IR-16              The       ATN ground
(0)                             ADS                            system shall process the ADS application
(22)                            ATC                            name as an AE qualifier (0).
                                                               IR-17              The ATN ground
                                                               system shall process the ATC application
                                                               name as an AE qualifier (22).
AP Version                      Vers                           None.
Aircraft Address (24-bit        24-bit aircraft address        None.
ICAO aircraft address)          (optional)                     Some FANS 1/A aircraft may provide the
                                                               24-bit aircraft address. The 24-bit aircraft
                                                               address may be used locally, but not for
                                                               FANS 1/A aircraft addressing.
AircraftFlightIdentification    Flight ID                      None.
No equivalent.                  Active Flag                    IR-18                The ATN ground
                                                               system shall set the active flag to 1.
                                                               Active Flag is sent, but not used.
No equivalent.                  Aircraft Position              The ATN ground system may use locally
                                                               the aircraft position.
Class of Communications         No equivalent.                 None.
No equivalent.                  Overall Reason Code            See Table 3-5Table 3-5Table 3-5.               Formatted: Cross-Reference, Font: 9 pt

Response                        Reason Code                    See Table 3-5Table 3-5Table 3-5.               Formatted: Cross-Reference, Font: 9 pt
                                                                                                              Formatted: Cross-Reference, Font: 9 pt
DepartureAirport                No equivalent.                 None.
                                                                                                              Formatted: Cross-Reference, Font: 9 pt
DepartureTime                   No equivalent.                 None.
DestinationAirport              No equivalent.                 None.
FacilityDesignation (in the     ICAO Facility Designation (4   IR-19               The ATN ground
logon request header) (4 to 8   Character ICAO Code)           system shall use the facility designation
Character ICAO Code)                                           only with size 4 using the first four
                                                               letters.
FacilityDesignation (Optional No equivalent.                   NIR-1               The ATN ground             Comment [PF4]:
in the logon request primitive)                                system shall omit the Facility                 COMMENT #1277
                                                               Designation in the CMLogonRequest.
LongTSAP                        No equivalent.                 None.
                                                               Information is available in the ACARS
                                                               Header and message Header.
                                                               The Aircraft Registration and the SMI
                                                               (representing MFI or label) and IMI serve
                                                               as the application address for all
                                                               applications (i.e. AFN, ADS and
                                                               CPDLC).
No equivalent.                  Timestamp                      The ATN ground system may use locally
                                                               the timestamp.
3-38


3.2.1.4   Timers
          Table 3-7Table 3-7Table 3-7 lists the ATN CM timer along with the comparable                                  Formatted: Cross-Reference
          FANS 1/A AFN timer.                                                                                           Formatted: Cross-Reference



                               Table 3-7       ATN CM and FANS 1/A AFN timers

          ATN CM Timer                      FANS 1/A AFN Timer                  Interoperability Requirement

          Doc 9880 2.5.2                    ATST1 is used by the                None.
          A CM-ASE shall be capable of      FANS 1/A aircraft to detect the     The ATST1 timer is an airborne timer
          detecting when a timer expires.   absence of the AFN_ACK in           and is functionally equivalent to the
                                            response to an AFN Contact.         tlogon timer.
          tlogon = 4 minutes
                                                                                ATST1 timer is set at 10 minutes,
                                                                                being less stringent for the FANS 1/A
                                                                                aircraft than for the ATN aircraft.

          Doc 9880 2.5.2                    ATST2 is used to detect the         0The tcontact timer is functionally
          A CM-ASE shall be capable of      absence of the AFN Response         equivalent to ATST2+ATST3.
          detecting when a timer expires.   in response to an AFN Contact       For domestic airspace, the ATN value
                                            Advisory. When it is used, it       is used.
          tcontact = 8 minutes              should be set to 5mn.
                                            ATST3 is used to detect the
                                            absence of the AFN Complete
                                            in response to an AFN Contact
                                            Advisory. It is set on the
                                            reception of an AFN Response
                                            positive.
                                            When it is used, it should be set
                                            to 15mn.

          Doc 9880 2.5.2                    No equivalent                       None. Update, forward and end
          A CM-ASE shall be capable of                                          service not supported in FANS
          detecting when a timer expires.                                       environment.
          tupdate = 8 minutes
          tforward = 8 minutes
          tend = 8 minutes
                                                                                                      3-39


3.2.2       CPDLC Application Requirements
            IR-21          The ATN ground system shall have the capability to encode and decode
            message elements addressed to or received from the FANS 1/A aircraft following the
            ASN.1 definitions as given in DO-258A/ED-100A.
3.2.2.1     Time, Timestamp and Message Latency
3.2.2.1.1   Time Source
            Table 3-8Table 3-8Table 3-8 presents the operational requirement and comparable                  Formatted: Cross-Reference
            FANS 1/A CPDLC requirements for time source.                                                     Formatted: Cross-Reference



                    Table 3-8     ATN and FANS 1/A CPDLC requirements for time source
            ATN                   FANS 1/A                             Interoperability Requirement
            SR-AC-CPDLC-16        4.6.3.3 b). All downlink CPDLC        None.
            The aircraft system   messages shall contain a timestamp
            shall time stamp to   which indicates the originators send
            within one second     time and use a time source which is
            UTC each message      referenced to UTC.
            when it is released   4.6.3.3 c). All uplink CPDLC
            for onward            messages shall contain a timestamp
            transmission.         which indicates the originator send
                                  time to an accuracy of +/- one
                                  second, and use a time source which
                                  is synchronized to UTC within one
                                  second.
                                  Note: In the FANS 1/A INTEROP
                                  Standard, it is required that CPDLC
                                  downlink messages are referenced to
                                  UTC, but there is no required
                                  accuracy. It is assumed that the
                                  majority of aircraft are compliant to
                                  ICAO Annex 2 including the +/- one
                                  second accuracy.
3-40


3.2.2.1.2   Timestamp Generation
            Table 3-9Table 3-9Table 3-9 presents the operational requirement and comparable                         Formatted: Cross-Reference
            FANS 1/A CPDLC requirements for timestamp generation.                                                   Formatted: Cross-Reference



             Table 3-9     ATN and FANS 1/A CPDLC requirements for timestamp generation
            ATN                                            FANS 1/A           Interoperability Requirement

            CPC-OR-59: Each CPDLC message shall            No requirement     None.
            indicate the date (YYMMDD) and time            contained in the   ATN ground system implementers
            (HHMMSS) that the message is released by       FANS 1/A           must be aware that the FANS 1/A
            the controller, by the flight crew, or by a    INTEROP            aircraft may generate the timestamp
            system without human intervention, for         Standard.          according to local implementation.
            onward transmission
            Note 1: When the flight crew or controller
            sends a CPDLC message, the date and time
            will be when he/she authorizes the
            transmission of the CPDLC message (e.g., by
            pressing an “ENTER” key or by activation of
            a message release function in an interactive
            display).
            Note 2: For CPDLC messages generated by a
            system without human intervention, the date
            and time will be when the CPDLC application
            releases the completed CPDLC message to the
            communications system.
                                                                                                                     3-41


3.2.2.1.3         Message Latency
                  Table 3-10Table 3-10Table 3-10 presents the ATN and comparable FANS 1/A CPDLC                               Formatted: Cross-Reference
                  requirements for message latency.                                                                           Formatted: Cross-Reference
                        Table 3-10 ATN and FANS 1/A CPDLC requirements for message latency
            ATN                                       FANS 1/A                             Interoperability Requirement
            Aircraft requirements
                                                      4.6.6.9 Message Latency              IR-24 The ATN ground system
                                                                                           shall decode ErrorInformation
                                                      a. When a CPDLC timestamp is
                                                                                           value (10) + FREETEXT from the
                                                      present in a received message, and
                                                                                           FANS 1/A aircraft, which is
                                                      the difference between the
                                                                                           represented by ErrorInformation
                                                      timestamp and UTC exceeds the
                                                                                           (3) + FREE TEXT in the ATS
                                                      “late message” value, the aircraft
                                                                                           INTEROP Standard.
                                                      shall either provide an applicable
                                                      notification to the aircrew or       When processing the Urgency
                                                      discard the message and notify the   and/or Alert attributes, the ATN
                                                      originator with an ERROR +           ground system must take care of
                                                      FREE TEXT message. The [error        the differences between the
                                                      information] contained in such an    FANS 1/A INTEROP Standard and
                                                      ERROR message shall be assigned      ATS INTEROP Standard
                                                      a value of “invalidData” (10).       definitions; DM62 (URG U, Alert
                                                                                           L) in the FANS 1/A aircraft and
                                                                                           DM67 (Alert M) in the ATN
                                                                                           ground system.
                                                                                           See also paragraph 3.2.2.4 about
                                                                                           message attributes.
            CPC-IR 23 When the CPDLC Aircraft         b. In aircraft that reject a late    None.
            System receives a CPDLC message           uplink message and send an
            containing a timestamp indicating a       ERROR response, the avionics
            difference between the timestamp and      shall add free text DM67
            the reception time of more than the       containing the text “UPLINK
            latency value (e.g. either the value      DELAYED IN NETWORK AND
            received in UM340 LATENCY TIME            REJECTED - RESEND OR                                                    Comment [FP5]:
            VALUE or the default value when no        CONTACT BY VOICE“ to the                                                COMMENT #725, # 963
            UM340 has been received), it shall        ERROR response.                                                         PDR #75, #298 10), #313
            discard the message and send a CPDLC
            downlink message containing the
            concatenation of message element DM62
            (ERROR (error information)) with the
            choice (2) followed by message element
            DM98 (RESEND MESSAGE OR
            CONTACT BY VOICE).
            Note: The default value is 999 seconds.
3-42


       ATN                                        FANS 1/A                               Interoperability Requirement
       CPC-IR 19: If the ATSU or Aircraft         No equivalent.                         None.
       System receives a message containing a     c. Prior to the establishment of the   The FANS 1/A aircraft does not
       timestamp that indicates a future time     first CPDLC connection during          detect timestamps with a value
       greater than 2 seconds from the current    any flight, the “late message” value   greater than 2 seconds from the
       time, it shall:                            shall be set to a default value or     reception time.
       a) send a CPDLC uplink or downlink         the latency check shall be
       message containing the concatenation of    cancelled. The message latency
       message element UM159 or DM62              value shall be cancelled or reset to
       (ERROR (error information)) with the       the default value no later than at
       choice (0) followed by message element     the end of the flight, and may be
       UM183 (DOWNLINK TIMESTAMP                  cancelled or reset at the end of any
       INDICATES FUTURE TIME) or DM97             CPDLC connection.
       (UPLINK TIMESTAMP INDICATES                The aircraft shall provide a
       FUTURE TIME), and                          capability to modify the “late
       b)                  abort the CPDLC        message” value during flight.
       connection with Reason [time-out-of-       Note: This statement is not
       synchronization].                          intended to preclude automated
                                                  reset of the “late message” value,
                                                  based on e.g. ground uplinks or
                                                  database values.
                                                  d. (see ground requirements)
       Ground Requirements
                                                  d. When a ground system enables a      Setting and handling of the timers    Comment [PF6]:
       [All ACM Operating Methods]: The R-
                                                  CPDLC connection with an               and handling of the Response are a    PDR #196
       ATSU sends a CPDLC message UM340
       LATENCY TIME VALUE indicating              aircraft, the ground system shall      local matter.
       the latency value.                         uplink CPDLC message UM169             The ATN ground system sets the
                                                  [SET MAX UPLINK DELAY                  max uplink delay value as specified
       CPC-IR 24: When the ATSU System            VALUE TO XXX SEC], XXX                 in the SPR.
       receives a CPDLC message containing a      being the “late message” value
       timestamp indicating a difference          expressed in seconds.
       between the timestamp and reception        Note 1: “Enabling” a CPDLC
       time of more than the ground latency       connection refers to the point at
       value, it shall either                     which a ground system makes the
            a) Discard the received message       CPDLC connection available for
                  and send a CPDLC uplink         operational exchanges. It is based
                  message containing the          on automated restrictions in the       The free text message element
                  concatenation of message        ATSU that ensure operational           UM183 is not in the FANS 1/A
                  element UM159 (ERROR            CPDLC messages are only sent to        message set. See paragraph 3.2.2.8
                  (error information)) with the   an aircraft under the operational      for use of free text message
                  choice (2) followed by          control of one of its ATC sectors.     element.
                  message element UM183           The UM169 message needs to be
                  (RESEND MESSAGE OR              sent after the “enabling” point to
                  USE VOICE), or                  reduce the risk that the message is
            b) Display the received message       routinely rejected by the avionics
                  with an indication that the     because the transmitting ground
                  message is late.                system is not yet the CDA for that
                                                  aircraft at the time the system is
                                                  designed to send it.
                                                  Note 2: Uplink of the um169 late
                                                  value confirmation message needs
                                                  to take place any time a new link is
                                                  ‘enabled’. The ground system
                                                  therefore needs to include the
                                                                                                     3-43


ATN                                   FANS 1/A                             Interoperability Requirement
                                      uplink in the case of reconnection
                                      logic for re-establishing lost
                                      CPDLC connections, etc.
                                      Note 3: Treatment of the
                                      subsequent DM3 (‘ROGER’)
                                      response to the UM169 is a local
                                      matter.
ACM-OR 9 Whenever the latency value                                        See Table 3-18     ATN      and
changes, the ATSU shall send UM340                                         FANS 1/A CPDLC uplink message
indicating the latency value.                                              elementsTable 3-18 ATN      and
                                                                           FANS 1/A CPDLC uplink message
                                                                           elementsTable 3-18 ATN      and
                                                                           FANS 1/A CPDLC uplink message
                                                                           elements for use the sending of
                                                                           UM340 message element.
3.2.2.2            ATN CPDLC Constructs and FANS 1/A ACARS IMIs
                   Table 3-11Table 3-11Table 3-11 presents the ATN CPDLC constructs and comparable                          Formatted: Cross-Reference
                   FANS 1/A ACARS IMIs.                                                                                     Formatted: Cross-Reference



                        Table 3-11 ATN CPDLC constructs and FANS 1/A CPDLC ACARS IMIs
          ATN Constructs                 FANS 1/A ACARS IMIs             Interoperability Requirement
          Ground Initiated CPDLC-start   IMI CR1 UM163                   IR-26 When establishing a CPDLC connection,
          service (req/ind) (no UM       [icaofacilitydesignation]       the ATN ground system shall send an IMI CR1
          included)                      [tp4table]                      including FANS 1/A message element UM163.
          CPC-IR 95 The ATSU System      From 4.6.2.1                    The value for the [tp4table] parameter should be
          shall not include a CPDLC                                      set to enumerated 0 or 1 by the ATN ground
                                         Note 1: Only the ATS provider
          Message when invoking the                                      system.
                                         system can initiate
          CPDLC-start service request    connections.                    The FANS 1/A aircraft will reject the
          primitive.                                                     connection initiation if no or another message
                                         Note 2: A valid tp4table must
          CPC-IR 96 The CPDLC ATSU                                       element other than UM163 is contained.
                                         be supplied although
          System shall not request       ATCComm ignores it.
          security when invoking the
          CPDLC-start service request
          primitive.
          Ground Initiated CPDLC-start   IMI CC1 DM73                    IR-27 The ATN ground system shall convert
          service (rsp/cnf)              [versionnumber]                 IMI CC1 into a positive CPDLC-start
                                                                         confirmation.

                                         Or                              IR-28 The ATN ground system shall not
                                                                         provide data link services to FANS 1/A aircraft
                                         IMI DR1 DM62 (optional)         responding with a version number other than 1.

                                                                         IR-29 The ATN ground system shall convert
                                         Or
                                                                         the IMI DR1 received in response to the IMI
                                                                         CR1 into a CPDLC-start confirmation
                                         IMI DR1 DM64 (optional)         (rejected), except if the DM62 error
                                                                         information, received with DR1, contains the
                                                                         value (invalid data) or (insufficient data).

                                                                         IR-30 When receiving an IMI DR1 containing
                                                                         the message element DM64 in response to the
                                                                         IMI CR1, the ATN ground system shall convert
                                                                         the FANS 1/A response into a CPDLC-start
                                                                         Confirmation (rejected), setting the Reject
                                                                         Reason parameter to a CPDLC message with the
                                                                         ATN message element DM107 (NOT
                                                                         AUTHORISED NEXT DATA AUTHORITY).

                                                                         The FANS 1/A aircraft sends the same version
                                                                         number 1.
                                                                         When it has no CPDLC connection established
                                                                         yet, the FANS 1/A aircraft rejects a valid
                                                                         CPDLC connection request if no successful
                                                                         logon has been done before with the ground
                                                                         system having sent the CPDLC connection
                                                                         request.
                                                                         When it has a CPDLC connection established,
                                                                                                                 3-45



ATN Constructs                 FANS 1/A ACARS IMIs                Interoperability Requirement
                                                                  the FANS 1/A aircraft rejects a valid CPDLC
                                                                  connection request, if it is not coming from the
                                                                  ground system indicated to be the R-ATSU.
CPDLC-message service          IMI AT1 (any DM or UM)             IR-31 If no connection is established or in the
(any UM or DM)                                                    process of being established, upon receipt of any
                               4.6.2.1.1 If no connection is
                                                                  CPDLC message, the ATN ground system shall
                               established or in the process of
                                                                  ignore that message.
                               being established, upon receipt
                               of any CPDLC message, the
                               ATS Provider system shall          IR-32 If a "Connect Request" (IMI=CR1) is
                               ignore that message.               pending, upon receipt of a message other than
                                                                  the    corresponding    "Connect    Confirm"
                               4.6.2.1.2 If a "Connect            (IMI=CC1) or a “Disconnect Request”
                               Request" (IMI=CR1) is              (IMI=DR1), the ATN ground system shall
                               pending, upon receipt of a         ignore that message.
                               message other than the
                               corresponding "Connect
                               Confirm" (IMI=CC1) or a
                               “Disconnect Request”
                               (IMI=DR1), the ATS Provider
                               system shall ignore that
                               message.
CPDLC-end service (req/ind)    IMI AT1 UM161 END                  IR-33 When ending a CPDLC connection, the
(UM optional)                  SERVICE + UM (optional)            ATN ground system shall send IMI AT1
                                                                  UM161 END SERVICE + UM (optional) to the
Note: As per paragraph 4.3,    Note: See requirements in
                                                                  FANS 1/A aircraft.
UM message concatenated with   4.6.2.2.1 and 4.6.2.2.2.
CPDLC-end service in several                                      For sending to the FANS 1/A aircraft, these
ACM cases.                                                        optional message elements will be concatenated
                                                                  with UM161 message element.
CPDLC-end service (rsp/cnf)    IMI DR1                            IR-34 When the IMI DR1 is received as
(UM optional)                                                     response to single element message containing
                               Note: See requirements in
                                                                  UM161, the ATN ground system shall process
Note: As per paragraph 4.3,    4.6.2.2.1 and 4.6.2.2.2.
                                                                  it as a CPDLC-end-confirmation (accepted).
UM message concatenated with
CPDLC-end service in several
ACM cases.                                                        IR-173 When the T-ATSU receives IMI DR1
                                                                  and WILCO, the ATN ground system shall
                                                                  process IMI DR1 like a CPDLC-end-
                                                                  confirmation by the ground system.

                                                                  IR-35 Upon receipt of DM62 in the Disconnect
                                                                  Request, the ATN ground system shall not
                                                                  present the message to controllers.

                                                                  IR-36 When the IMI DR1 is received as a
                                                                  response to an uplink message, containing
                                                                  UM161 message element, if a DM62 is included
                                                                  in the Disconnect Request, the ATN ground
                                                                  system shall ignore the [error information].

                                                                  IR-37 When the IMI DR1 is received as
                                                                  response to a multiple-element message
                                                                  containing UM161 and any UM, the ATN
                                                                  ground system shall process it as a CPDLC-end-
                                                                  confirmation (accepted).
3-46


       ATN Constructs   FANS 1/A ACARS IMIs   Interoperability Requirement

                                              IR-38 The ATN ground system shall process
                                              the operational response(s) received prior to the
                                              IMI DR1.

                                              IR-39 When a DM1 UNABLE is received prior
                                              to the IMI DR1 in response to a multiple-
                                              element message containing UM161 and any
                                              UM, the ATN ground system shall process it as
                                              a CPDLC-end-confirmation (rejected).
                                                                                                  Comment [PF7]:
                                              This results in continued capability to exchange    COMMENT #1291
                                              operational messages with the T-ATSU.
                                              The ATN ground system should not process the
                                              IMI DR1 before the reception of the operational
                                              response(s) unless the dialogue timers expire.
                                              In case that there are pending uplink messages
                                              (see definition of pending uplink message in the
                                              FANS 1/A INTEROP Standard, paragraph
                                              4.6.6.4), when the aircraft receives the end
                                              service message, the FANS 1/A aircraft
                                              generates a disconnect request containing
                                              DM62, regardless of whether or not the END
                                              SERVICE is concatenated with another message
                                              element.
                                              If negative answer is selected by the crew to the
                                              concatenated UM161 and any UM, no
                                              subsequent IMI DR1 will be sent by the
                                              FANS 1/A aircraft.
                                              See paragraph 3.2.2.10.2 for the operational
                                              response(s) to the concatenations of UM161 and
                                              any UM.
                                                                                                              3-47



ATN Constructs                    FANS 1/A ACARS IMIs               Interoperability Requirement
Ground CPDLC-user-abort           4.6.2.2.2                         IR-40             When aborting a CPDLC
service                                                             connection, the ATN ground system shall send
                                  a) If an END SERVICE
(CPDLCUserAbort)                                                    IMI AT1 UM161 END SERVICE concatenated
                                  (uM161) message element is
Including commanded                                                 with UM159 (ERROR) with error information
                                  received as a component of a
termination                                                         set to ‘commanded-termination’.
                                  multiple element message and
                                  a WILCO (dM0) response is
                                  not a valid response for that     IR-41           When DM62 is received in
                                  message, send "Disconnect         the Disconnect Request, the ATN ground
CPC-IR 3 When aborts result       Request" (IMI=DR1)                system shall not present the message to
from a pilot or controller        containing a message with the     controllers.
explicit action, the CPDLC        ERROR [error information]
Aircraft System or the CPDLC      (dM62) message element with       IR-42               When the IMI DR1 and
ATSU System shall use the         the                               included DM62 is received as response to
abort reason “commanded           [endServiceWithNoValidResp        UM161 +UM159, the ATN ground system shall        Comment [PF8]:
termination”.                     onse] value for all connections   ignore the message.                              PDR #324
                                  and discard the message.
CPC-IR 6 When the Controller      Note: This procedure should       As per the FANS 1/A INTEROP Standard,
initiates termination, the ATSU   be used by the current ATC        paragraph 4.6.2.2.2, such a combination is
System shall transmit a           Data Authority to invoke an       processed as an abnormal disconnection.
CPDLC-user-abort request          abnormal connection               The FANS 1/A INTEROP Standard, paragraph
using the “commanded-             termination. The END              5.3.1.2, explains why uplink IMI DR1 should
termination” value (5) in the     SERVICE (uM161) message           not be used to disconnect.
Reason parameter                  element will be sent in
                                  combination with the ERROR
                                  [error information] (uM159)
                                  message element (a
                                  combination for which WILCO
                                  (dM0) is not a valid response).
                                  The suggested [error
                                  information] value is
                                  commandedTermination].
Air CPDLC-user-abort service      IMI DR1                           IR-43 When the IMI DR1 is received
(CPDLCUserAbort)                                                    unsolicited, the ATN ground system shall
                                                                    process it like an Air CPDLC-user-abort
                                  Or                                (undefined).

                                  IMI DR1 DM62 ERROR                IR-44 Upon receipt of DM62 in the Disconnect
                                  [error information]               Request, the ATN ground system shall not
                                                                    present the message to controllers.

                                  Or
                                                                IR-45 When receiving an IMI AT1 DM62
                                                                (duplicateMsgIdentification Number), the ATN
                                  IMI AT1 DM62 ERROR            ground system shall send IMI AT1 UM161
                                  (duplicateMsgIdentificationNu END SERVICE concatenated with UM159
                                  mber)                         (ERROR), with error information set to
                                                                ‘commanded-termination’,       and     internally
                                                                process the IMI AT1 DM62 as an Air CPDLC
                                                                User Abort (duplicate message identification
                                                                numbers (2)).
                                                                DR1 is considered unsolicited when it is
                                                                received while no ground-initiated CPDLC start,
                                                                end, or abort is in progress.
                                                                As per Ground CPDLC-user-abort service
3-48


       ATN Constructs                     FANS 1/A ACARS IMIs               Interoperability Requirement
                                                                            (CPDLCUserAbort) the response to UM161 +
                                                                            UM159 is ignored by the ground system.
       CPDLC-provider-abort-service       A DR1 DM62 (invalid data) is      IR-46             The ATN ground system
       (CPDLCProviderAbort)               sent by the FANS 1/A aircraft     shall process a DR1 DM62 (invalid data) as a
       initiated by the aircraft          only in response to a CR1         CPDLC Provider abort (invalid PDU).
                                          (Connection Request) when an
       Doc 9880, 3.5.4.3.1                error is encountered in the       The FANS 1/A aircraft will send an ERROR
       If the User Data parameter of a    message contained in the CR1.     (“invalid data”) but will not disconnect in the
       D-END confirmation with                                              following cases:
       Result parameter is set to the
       abstract value “rejected”, or if                                     • An invalid coded user data (FANS equivalent
       the User Data parameter of a D-                                      to PDU) is found in a AT1 IMI message (ATN
       START indication, a D-DATA                                           equivalent is a provider abort);
       indication, or a D-END                                               • An error is found during the processing at
       indication, does not contain a                                       application level (ATN equivalent also an
       valid PDU, the CPDLC- air-                                           ERROR).
       ASE shall:                                                           The ATN ground system will process the error
       …                                                                    (invalid data) received in IMI ATI like a
       b) Create an AircraftPDUs                                            CPDLC error message and consequently
       APDU with a                                                          remains connected. Refer to paragraph 0 for
       CPDLCProviderAbortReason                                             ERROR processing.
       [invalid-PDU] APDU message
       element,
       c) Invoke D-ABORT request
       with:
         1) the abstract value
       “provider” as the D-ABORT
       Originator parameter value, and
         2) the APDU as the D-ABORT
       User Data parameter value,”
                                          IMI DR1 DM62 (insufficient        IR-47 The ATN ground system shall process
       Doc 9880, 3.5.4.7.1
                                          data) is sent by the FANS 1/A     IMI DR1 DM62 (insufficient data) received in
       If the User Data parameter of a    aircraft when insufficient data   response to a IMI CR1 as a provider-abort
       D-START indication or D-           is received within a IMI CR1      (invalid PDU).
       DATA indication does not           to decode the included
       contain a PDU, the CPDLC-or        message.                          IR-48 The ATN ground system shall process
       air-ASE shall:                                                       IMI AT1 (insufficient data) as a provider-abort
                                          The FANS 1/A aircraft will
       …                                  downlink IMI AT1 DM62             (invalid PDU).
       b) Create an AircraftPDUs          (insufficient data) when an
       APDU with a                        uplink ATI is not correct and     When the FANS 1/A aircraft receives an uplink
       CPDLCProviderAbortReason           for the FANS 1/A aircraft in      message (IMI AT1) containing a
       [expected-PDU missing] APDU        the following case:               [routeclearance] parameter and in the
       message element,                   ATCComm receives an uplink        [routeinformationadditional] parameter the
       c) Invoke D-ABORT request          message (IMI AT1) containing      optional [waypointspeedaltitude] type with
       with:                              a [routeclearance] parameter      neither a [speed] type nor an [aTWaltitude] type
         1) the abstract value            and in the                        they also respond with IMI ATI (insufficient
       “provider” as the D-ABORT          [routeinformationadditional]      data).
       Originator parameter value, and    parameter the optional            In that case, the connection is aborted with a
                                          [waypointspeedaltitude] type      FANS1/A aircraft whereas an error is received
         2) the APDU as the D-ABORT
                                          with neither a [speed] type nor   and the CPDLC connection maintained with an
       User Data parameter value”,
                                          an [aTWaltitude] type.            ATN aircraft.
                                                                                                     3-49



ATN Constructs                      FANS 1/A ACARS IMIs   Interoperability Requirement
                                                          .
CPDLC-provider-abort-service        No equivalent.        IR-49 When the timer expires, the ATN ground
(CPDLCProviderAbort)                                      system shall abort the CPDLC connection,
initiated by the ground                                   sending UM161 END SERVICE concatenated
                                                          with UM159 (ERROR) with error information
Doc 9880, 3.5.6.1.1                                       ’commanded termination’ to the FANS 1/A
If a CPDLC-ground ASE                                     aircraft.
detects that a timer has expired,
that CPDLC- ground ASE                                    IR-50 The ATN ground system shall ignore the
shall:                                                    DR1 that will be received in response from the
…                                                         aircraft.
b) Create a GroundPDUs APDU
with a                                                    IR-51 The ATN ground system shall issue a
CPDLCProviderAbortReason                                  provider abort indication to the local ground
[timer-expired] APDU message                              user.
element,
c) Invoke D-ABORT request
with:
1) the abstract value “provider”
as the D-ABORT Originator
parameter value, and
2) the APDU as the D-ABORT
User Data parameter value

Doc 9880, 3.5.6.3.1              No equivalent.           When invalid coded data is detected in a IMI
                                                          AT1, the ATN ground system should respond
If the User Data parameter of a                           with UM159 (ERROR) with error information
D-END confirmation with                                   ‘invalid data.’
Result parameter set to the
abstract value “rejected”, a D-
START indication, a D-DATA
indication, or a D-END
indication, does not
contain a valid PDU, the
CPDLC-ground-ASE shall:
...
b) Create a GroundPDUs APDU
with a
CPDLCProviderAbortReason
[invalid-PDU]
APDU message element,
c) Invoke D-ABORT request
with:
1) the abstract value “provider”
as the D-ABORT Originator
parameter value,
and
2) the APDU as the D-ABORT
User Data parameter value,...
3-50


       ATN Constructs                    FANS 1/A ACARS IMIs            Interoperability Requirement
       No equivalent.                    IMI CC1 with invalid encoded   When invalid coded data is detected in an IMI
                                         user data                      CC1, the ATN ground system should abort the
                                                                        connection with UM161 concatenated with
                                                                        UM159 (ERROR) with error information‚
                                                                        ‘invalid data.’

       Doc 9880, 3.5.6.7.1               IMI AT1 without user data      When no user data is detected in an IMI AT1,
                                                                        the ATN ground system should respond UM159
       If the User Data parameter of a                                  (ERROR) with error information ‘insufficient
       D-START indication or a D-                                       data.’
       DATA indication does not
       contain a PDU, the CPDLC-
       ground-ASE shall:
       …
       d) If the CPDLC-ground-user is
       an active user, invoke CPDLC-
       provider-abort service
       indication with the abstract
       value “not-permitted PDU” as
       the CPDLC- provider-abort
       Reason parameter value.
       No equivalent.                    Unexpected IMI                 When any IMI is received whilst no connection
                                                                        is established or in the process of being
                                                                        established, the ATN ground system should
                                                                        disregard the message.
3.2.2.3          High-Level Data Structures
                 Table 3-12Table 3-12Table 3-12 compares the ATN CPDLC and FANS 1/A high-level                    Formatted: Cross-Reference
                 data structures.                                                                                 Formatted: Cross-Reference



                             Table 3-12 ATN and FANS 1/A CPDLC high-level data structures
          ATN                         FANS 1/A             Interoperability Requirement
          Applicable GroundPDUs:                           None.
           CPDLCUserAbortReason                            The FANS 1/A aircraft does not have the user or
           CPDLCProviderAbortReason                        provider abort PDUs. The FANS 1/A error reason codes
                                                           support some of the ATN aborts. The ATN aborts and
                                                           comparable FANS 1/A error reasons are shown in
                                                           paragraph 3.2.2.11.
           ICUplinkMessage            ATCuplinkmessage     In both the ATS INTEROP Standard and the FANS 1/A
                                                           INTEROP Standard, the ATC Uplink Message PDU
                                                           contains the uplink message elements choices.
          Applicable AircraftPDUs:                         None.
           CPDLCUserAbortReason                            The FANS 1/A aircraft does not have the user or
           CPDLCProviderAbortReason                        provider abort PDUs. The FANS 1/A error reason codes
                                                           support some of the ATN aborts. ATN aborts and
                                                           comparable FANS 1/A error reasons are shown in
                                                           paragraph 3.2.2.11.
           ICDownlinkMessage          ATCdownlinkmessage   In both the ATS INTEROP Standard and the FANS 1/A
                                                           INTEROP Standard the ATC Downlink Message PDU
                                                           contains the downlink message elements choices.
3-52

3.2.2.4            Message Attributes
                   In both ATN system and FANS 1/A system for some CPDLC messages, the message
                   attributes have changed between the ATN message elements and the FANS 1/A message
                   elements.
                   Table 3-13Table 3-13Table 3-13 compares the ATN CPDLC and FANS 1/A uplink and                       Formatted: Cross-Reference
                   downlink message attributes.                                                                        Formatted: Cross-Reference



                                 Table 3-13 ATN and FANS 1/A CPDLC message attributes
       ATN Message Attributes               FANS 1/A Message       Interoperability Requirement
                                            Attributes
       Response Attribute – Uplink          Response Attribute -
                                            Uplink
       W/U                                  W/U                    None.
       A/N                                  A/N                    None.
       R                                    R                      None.
                                                                   ATN systems permit UNABLE response message
                                                                   to R messages. An UNABLE response to R
                                                                   messages is not available in FANS 1/A.
                                                                   If an ATN ground system uses a message element
                                                                   with R response attribute, a procedure could be
                                                                   established to ensure that the pilot can express
                                                                   rejection of the message by voice and that the
                                                                   controller will not be mislead by the ROGER
                                                                   received.
                                                                   See paragraph 3.2.2.8, for use of messages with R
                                                                   response.
                                                                                                                    3-53



ATN Message Attributes                         FANS 1/A Message            Interoperability Requirement
                                               Attributes
N                                              NE                          IR-52 The ATN ground system shall be capable
                                                                           of accepting message reference numbers in all
Note: In the SPR Standard, when a message      Note: In the FANS 1/A
                                                                           ERROR messages.
with a N response attribute is received and    INTEROP Standard,
an error is detected then:                     when message with a NE
- If the message requires a logical            response attribute is       Note: This is to prevent the ATN ground system
acknowledgement, an ERROR response is          received and an error is    from rejecting a response ERROR messages
sent with a message reference number (the      detected, an ERROR          containing a reference number for a N message.
same as the FANS 1/A message without the       response is sent that may
logical acknowledgement).                      contain a message
                                               reference number.
- If the message does not permit a logical
acknowledgement, then an ERROR message
can be sent, but a reference number is
normally not included (exception see note
below). Thus the ERROR message will
normally not explicitly refer to the message
in error.
From the ATS INTEROP 3.3.2.4
Note 3: Some aircraft always include a
reference number matching the identification
number of the CPDLC message to which the
ERROR message refers. This is not Doc
9880 compliant when theCPDLC message in
error has an “N” response attribute and
does not require a LACK.
Y                                              Y                           None.
Response Attribute -Downlink                   Response Attribute -
                                               Downlink
Y                                              Y                           None.
N                                              N                           None.
3-54

3.2.2.5            LACK
                   A “LACK required” indication is not available in the FANS 1/A INTEROP Standard
                   definitions. Logical acknowledgements (LACKs) are not available in the FANS 1/A
                   aircraft.


3.2.2.5.1          LACK on Downlink Messages
                   Table 3-14Table 3-14Table 3-14 compares the FANS and ATN management of LACK                                Formatted: Underline
                   on Downlink Messages.                                                                                      Formatted: Underline
                                              Table 3-14: LACK on Downlink Messages
          ATN                                FANS 1/A                                Interoperability Requirement
                                                                                     IR-53              The    ATN   ground
                                                                                     system shall not generate LACK message
                                                                                     elements to the FANS 1/A aircraft in
                                                                                     response to downlink messages.
                                             Note:                 As LACKs are      No requirement.
                                             not supported by FANS 1/A aircraft,
                                             it is not necessary for an ATN ground
                                             system that does not support LACK,
                                             to send UM233 USE OF LACK
                                             PROHIBITED to FANS 1/A aircraft
                                             (see paragraph 4.2.8).
          CPC-IR 2 When the CPDLC            No equivalent.                          None.
          ATSU System receives a
          downlink message requiring a
          logical acknowledgement where
          the use of logical
          acknowledgement has been
          prohibited, then the ATSU
          System shall send a CPDLC
          message referencing the request,
          containing the concatenation of
          message element UM159
          (ERROR (error information))
          with the choice (0) followed by
          message element UM187
          (LOGICAL
          ACKNOWLEDGEMENT NOT
          ACCEPTED).
                                                                                                                      3-55



3.2.2.5.2         LACK on Uplink Messages
                  Table 3-16Table 3-16Table 3-16 compares the FANS and ATN management of LACK                                  Formatted: Underline
                  on Uplink Messages.                                                                                          Formatted: Underline
                                             Table 3-15: LACK on Uplink Messages
        ATN                                FANS 1/A                                Interoperability Requirement
                                                                                   IR-54 When sending a message to the
        CPC-OR-48 When a CPDLC is          Note: The FANS 1/A aircraft
                                                                                   FANS 1/A aircraft, if the ATN ground
        established, the aircraft system   transmits a Message Assurance (MA)
                                                                                   system uses LACKs, it shall translate the
        shall default to requesting        to the ground system by the data link
                                                                                   positive MA into a CPDLC downlink
        LACK.                              service provider (DSP) when the
                                                                                   message containing the message element
                                           FANS 1/A aircraft has confirmed to
                                                                                   DM100 (LACK) using the uplink message
                                           the DSP receipt of the entire
                                                                                   number as message reference number.
                                           message. This confirmation is
                                           generated prior to CRC and
                                           application level message checking.     NIR-2                 When     sending a
                                                                                   message to the FANS 1/A aircraft and the
                                           The MA is sent for every uplink         ATN ground system does not use LACKs,
                                           FANS 1/A message for which a            it shall discard the positive MA.
                                           confirmation is received.
                                           Note 1: The FANS 1/A aircraft may       NIR-3              Upon receipt of a
                                           transmit a MA followed by an            negative MA message from a FANS 1/A
                                           ERROR response for the same uplink      aircraft, the ATN ground system shall
                                           message                                 translate a negative MA into a CPDLC
                                                                                   downlink      message  containing  the
                                                                                   concatenation of message element DM62
                                                                                   (ERROR (error information)) with the
                                                                                   choice (0) followed by message element
                                                                                   DM98 (‘MESSAGE NOT DELIVERED')
                                                                                   using the uplink message number as
                                                                                   message reference number.

                  .
3-56

3.2.2.6            CPDLC Disabling/Enabling
                   Table 3-16Table 3-16Table 3-16 presents the interoperability requirements for CPDLC                 Formatted: Underline
                   disabling/enabling functionality available in the ATN ground system.                                Formatted: Underline



                   Table 3-16 CPDLC Disabling/Enabling Functionality
          ATN                                            FANS 1/A         Interoperability Requirement
          3.3.1.4                                       No equivalent.    None.
          Note. Some data link equipped ATSU Systems                      As per the FANS 1/A INTEROP Standard,
          allow CPDLC to be turned “In Use” (i.e.                         paragraph 4.6.2.2, when CPDLC has been
          CPDLC in use) and “Not In Use” (i.e.                            disabled for the whole ATSU, the
          CPDLC not in use) on an ATSU and/or sector                      FANS 1/A ground system sends IMI AT1
          basis. In both cases, the CPDLC connection                      UM161 END SERVICE concatenated
          is maintained. This capability may be used at                   with UM159 (ERROR) with error
          any time                                                        information ’commanded-termination’ to
                                                                          all FANS 1/A aircraft currently connected.
          When the R-Sector is not using CPDLC the       No equivalent.   None.
          R-ATSU sends CPDLC message UM287
          (CPDLC NOT IN USE UNTIL FURTER
          NOTIFICATION) indicating it is not using
          CPDLC.
          ACM-OR 6 When an ATSU/sector sets
          CPDLC to “Not in Use”, the ATSU system
          shall send a CPDLC message containing the
          message element UM287 CPDLC NOT IN
          USE UNTIL FURTHER NOTIFICATION.
          Note 4: An ATSU/sector may switch between No equivalent.        None.
          CPDLC “In Use”/ “Not In Use” as required.
          ACM-OR 6 When an ATSU/sector sets
          CPDLC to “Not in Use”, the ATSU system
          shall send a CPDLC message containing the
          message element UM287 CPDLC NOT IN
          USE UNTIL FURTHER NOTIFICATION.
          ACM-OR 7 When a sector sets CPDLC to “In
          Use”, the ATSU system shall send a CPDLC
          message containing the message element
          UM286 (CPDLC BACK IN USE).
          CPC-IR 11 When the ATSU System receives        No equivalent.   None.
          a CPDLC message (except for emergency
          messages), and CPDLC is not in use, then the
          ATSU System shall discard the message and
          send a CPDLC uplink message containing the
          concatenation of message element UM159
          (ERROR (error information)) with the choice
          (2) followed by message element UM183
          (CPDLC NOT IN USE AT THIS TIME -
          USE VOICE).
                                                                                                                      3-57



3.2.2.7            Message Header
                   Table 3-17Table 3-17Table 3-17 compares the ATN and FANS 1/A CPDLC message
                   headers.


                                  Table 3-17 ATN and FANS 1/A CPDLC message headers
          ATN Message Header              FANS 1/A Message Header         Interoperability Requirement
          Message Identification Number   Message Identification Number   None
          Message Reference Number        Message Reference Number        None
          (optional)                      (optional)
          Timestamp                       Timestamp (optional)            IR-57 The ATN ground system shall use its
                                                                          own system date source.
            Date (YYMMDD)
                                                                          Note 1: For downlink CPDLC messages, the
            Time (HHMMSS)                  HHMMSS
                                                                          ATN ground system has to take into
                                                                          consideration that the date is not available in
                                          Note: The optional item is      the FANS 1/A timestamp.
                                          always provided by the          Note 2: Around midnight, the ATN ground
                                          FANS 1/A aircraft.              system has to receive and process time
                                                                          information related to the previous day.
                                                                          Note 3: For uplink CPDLC messages, the
                                                                          ATN ground system cannot provide the date
                                                                          in uplink messages addressed to the
                                                                          FANS 1/A aircraft.
          An indication if logical        No equivalent.                  See paragraph 3.2.2.5 for LACK requirements
          acknowledgement is required                                     on downlink and uplink message elements.
3.2.2.8           Uplink Message Elements
                  Table 3-18Table 3-18Table 3-18 lists ATN uplink message elements, the corresponding
                  FANS 1/A uplink message elements, and related interoperability requirements.
                  Note. In Table 3-18Table 3-18Table 3-18, some uplink ATNmessage elements containing                        Comment [P9]:
                  parameters which are converted into free text. This is necessary when any ATN parameter is                 COMMENT #819
                  included as part of UM169 for transmission to the FANS 1/A aircraft. When a parameter is
                  converted to free text it is sent using IA5 characters. Thus there are no range and resolution             Formatted: Font: 10 pt, Italic
                  restrictions or checking, and any qualifiers (level in feet) must be indicated. The text in the table is   Formatted: Font: 10 pt, Italic
                  a suggestion, however all required information must be conveyed as ex.


                             Table 3-18 ATN and FANS 1/A CPDLC uplink message elements                                       Comment [P10]:
                                                                                                                             COMMENT #773, #818
          ATN Message Element           FANS 1/A Message Element        Interoperability Requirement
          UM0 UNABLE                    UM0 UNABLE                      None.
          UM1 STANDBY                   UM1 STANDBY                     None.
          UM2 REQUEST DEFERRED          UM2 REQUEST DEFERRED            None.
          UM3 ROGER                     UM3 ROGER                       None.
          UM4 AFFIRM                    UM4 AFFIRM                      None.
          UM5 NEGATIVE                  UM5 NEGATIVE                    None.
          UM7 EXPECT HIGHER AT          UM7 EXPECT CLIMB AT             None.                                                Comment [PF11]:
          TIME [time]                   [time]                                                                               PDR #263, #272
                                                                        Note. The displayed message text is different in
                                                                        FANS1/A.
          UM8R EXPECT HIGHER AT         UM8 EXPECT CLIMB AT                                                                  Comment [PF12]:
                                                                        NIR-J-IR 1                 When
          [positionR]                   [position]                                                                           PDR #272
                                                                            accommodating an ATN UM8R, the ATN
                                                                            ground system shall convert the ATN UM8R
                                                                            message element to the FANS 1/A UM8
                                                                            message element,
                                                                        See paragraph 3.2.2.12.3 for use of positionR
                                                                        parameter.
                                                                        Note. The displayed message text is different in
                                                                        FANS1/A.
          UM9 EXPECT LOWER AT           UM9 EXPECT DESCENT AT           None.                                                Comment [PF13]:
          TIME [time]                   [time]                                                                               PDR #263, #272
                                                                        Note. The displayed message text is different in
                                                                        FANS1/A.
          UM10R EXPECT LOWER AT         UM10 EXPECT DESCENT                                                                  Comment [PF14]:
                                                                        NIR-J-IR 2                 When
          [positionR]                   AT [position]                                                                        PDR #272
                                                                            accommodating an ATN UM10R, the ATN
                                                                            ground system shall convert the ATN
                                                                            UM10R message element to the FANS 1/A
                                                                            UM10 message element,
                                                                        See paragraph 3.2.2.12.3 for use of positionR
                                                                        parameter.
                                                                        Note. The displayed message text is different in
                                                                        FANS1/A.
                                                                                                  3-59


ATN Message Element       FANS 1/A Message Element     Interoperability Requirement
UM19 MAINTAIN [level]     UM19 MAINTAIN [altitude]     NIR-4              When accommodating an
                                                       ATN UM19 including a single level, the ATN
                                                       ground system shall convert the ATN UM19
                                                       message element to the FANS 1/A UM19 message
                                                       element.
                                                       See paragraph 3.2.2.12.1 for use of level
                                                       parameter.
UM19 MAINTAIN BLOCK       UM30 MAINTAIN BLOCK          IR-58              When accommodating an
[level] TO [level]        [altitude] TO [altitude]     ATN UM19 including a vertical range, the
                                                       ATN ground system shall convert the ATN UM19
                                                       message element to the FANS 1/A UM30 message
                                                       element.
                                                       See paragraph 3.2.2.12.1 for use of level
                                                       parameter.
UM20 CLIMB TO [level]     UM20 CLIMB TO AND            NIR-5              When accommodating an
                          MAINTAIN [altitude]          ATN UM20 including a single level, the ATN
                                                       ground system shall convert the ATN UM20
                                                       message element to the FANS 1/A UM20 message
                                                       element.
                                                       See paragraph 3.2.2.12.1 for use of level
                                                       parameter.
                                                       Note. The displayed message text is different in
                                                       FANS1/A.
UM20 CLIMB TO BLOCK       UM31 CLIMB TO AND         IR-59              When accommodating an              Comment [PF15]:
[level] TO [level]        MAINTAIN BLOCK [altitude] ATN UM20 including a vertical range, the ATN          PDR #266
                          TO [altitude]             ground system shall convert the ATN UM20
                                                    message element to the FANS 1/A UM31 message
                                                    element.
                                                    See paragraph 3.2.2.12.1 for use of level
                                                    parameter.
                                                    Note. The displayed message text is different in
                                                    FANS1/A.
UM21 AT OR AFTER TIME     UM21 AT [time] CLIMB TO   NIR-6              When accommodating an              Comment [PF16]:
[time] CLIMB TO [level]   AND MAINTAIN [altitude]   ATN UM21 including a single level, the ATN            PDR #263, #134 3)
                                                    ground system shall convert the ATN UM21
                                                    message element to the FANS 1/A UM21 message
                                                    element.
                                                    See paragraph 3.2.2.12.1 for use of level
                                                    parameter.
                                                    Note. The displayed message text is different in
                                                    FANS1/A.
UM21 AT OR AFTER TIME     None.                        NIR-7                The ATN ground system shall   Comment [PF17]:
[time] CLIMB TO BLOCK                                  reject the sending of a UM21 message element       PDR #266
[level] TO [level]                                     including a vertical range.
3-60


       ATN Message Element         FANS 1/A Message Element     Interoperability Requirement
       UM22R AFTER PASSING         UM22 AT [position] CLIMB     NIR-8              When accommodating an
       [position ATW] CLIMB TO     TO AND MAINTAIN              ATN UM22R including a single level and the
       [level]                     [altitude]                   positionATW parameter contains a positionR, the
                                                                ATN ground system shall convert the ATN
                                                                message UM22R to the FANS 1/A message
                                                                UM22.
                                                                See paragraph 3.2.2.12.3 for use of positionR
                                                                parameter.
                                                                See paragraph 3.2.2.12.1 for use of level
                                                                parameter.
                                                                Note. The displayed message text is different in
                                                                FANS1/A.
       UM22R AFTER PASSING         None                         NIR-9                The ATN ground system shall   Comment [PF18]:
       [position ATW] CLIMB TO                                  reject the sending of a UM22R message element      PDR #266, #268
       BLOCK [level] TO [level]                                 including a vertical range or an ATW Along Track
                                                                Position.
       UM23 DESCEND TO [level]     UM23 DESCEND TO AND          NIR-10               When accommodating an
                                   MAINTAIN [altitude]          ATN UM23 including a single level, the ATN
                                                                ground system shall convert the ATN UM23
                                                                message element to the FANS 1/A UM23 message
                                                                element.
                                                                See paragraph 3.2.2.12.1 for use of level
                                                                parameter.
                                                                Note. The displayed message text is different in
                                                                FANS1/A.
       UM23 DESCEND TO BLOCK       UM32 DESCEND TO AND       IR-60              When accommodating an              Comment [PF19]:
       [level] TO [level]          MAINTAIN BLOCK [altitude] ATN UM23 including a vertical range, the ATN          PDR #266
                                   TO [altitude]             ground system shall convert the ATN UM23
                                                             message element to the FANS 1/A UM32 message
                                                             element.
                                                             See paragraph 3.2.2.12.1 for use of level
                                                             parameter.
                                                             Note. The displayed message text is different in
                                                             FANS1/A.
       UM24 AT OR AFTER TIME       UM24 AT [time] DESCEND    NIR-11             When accommodating an
       [time] DESCEND TO [level]   TO [altitude]             ATN UM24 including a single level, the ATN
                                                             ground system shall convert the ATN UM24
                                                             message element to the FANS 1/A UM24 message
                                                             element.
                                                             See paragraph 3.2.2.12.1 for use of level
                                                             parameter.
                                                             Note. The displayed message text is different in
                                                             FANS1/A.
       UM24 AT OR AFTER TIME       None.                        NIR-12               The ATN ground system shall
       [time] DESCEND TO BLOCK                                  reject the sending of a UM24 message element
       [level] TO [level]                                       including a vertical range.
                                                                                                    3-61


ATN Message Element           FANS 1/A Message Element   Interoperability Requirement
UM25R AFTER PASSING           UM25 AT [position]         NIR-13             When accommodating an
[position ATW] DESCEND TO     DESCEND TO [altitude]      ATN UM25R including a single level and the
[level]                                                  positionATW parameter contains a positionR, the
                                                         ATN ground system shall convert the ATN
                                                         message UM25R to the FANS 1/A message
                                                         UM25.
                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                         parameter.
                                                         See paragraph 3.2.2.12.1 for use of level
                                                         parameter.
                                                         Note. The displayed message text is different in
                                                         FANS1/A.
UM25R AFTER PASSING           None.                      NIR-14               The ATN ground system shall
[position ATW] DESCEND TO                                reject the sending of a UM25R message element      Comment [PF20]:
BLOCK [level] TO [level]                                 including a vertical range or an ATW Along Track   PDR #266
                                                         Position.
UM26 CLIMB TO REACH           UM26 CLIMB TO REACH        NIR-15               When accommodating an
[level] AT OR BEFORE TIME     [altitude] BY [time]       ATN UM26 including a single level, the ATN
[time]                                                   ground system shall convert the ATN UM26
                                                         message element to the FANS 1/A UM26 message
                                                         element.
                                                         See paragraph 3.2.2.12.1 for use of level
                                                         parameter.
                                                         Note. The displayed message text is different in
                                                         FANS1/A.
UM26 CLIMB TO REACH           None.                      NIR-16               The ATN ground system shall   Comment [PF21]:
BLOCK [level] TO [level] AT                              reject the sending of a UM26 message element       PDR #266
OR BEFORE TIME [time]                                    including a vertical range.

UM27R CLIMB TO REACH          UM27 CLIMB TO REACH        NIR-17             When accommodating an
[level] BEFORE PASSING        [altitude] BY [position]   ATN UM27R including a single level and the
[position ATW]                                           positionATW parameter contains a positionR, the
                                                         ATN ground system shall convert the ATN
                                                         message UM27R to the FANS 1/A message
                                                         UM27.
                                                         See paragraph 3.2.2.12.1 for use of level
                                                         parameter.
                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                         parameter.
                                                         Note. The displayed message text is different in
                                                         FANS1/A.
UM27R CLIMB TO REACH          None.                      NIR-18               The ATN ground system shall
BLOCK [level] TO [level]                                 reject the sending of a UM27R message element
BEFORE PASSING [position                                 including a vertical range or an ATW Along Track
ATW]                                                     Position.
3-62


       ATN Message Element           FANS 1/A Message Element   Interoperability Requirement
       UM28 DESCEND TO REACH         UM28 DESCEND TO REACH NIR-19             When accommodating an
       [level] AT OR BEFORE TIME     [altitude] BY [time]  ATN UM28 including a single level, the ATN
       [time]                                              ground system shall convert the ATN UM28
                                                           message element to the FANS 1/A UM28 message
                                                           element.
                                                           See paragraph 3.2.2.12.1 for use of level
                                                           parameter.
                                                           Note. The displayed message text is different in
                                                           FANS1/A.
       UM28 DESCEND TO REACH         None.                      NIR-20               The ATN ground system shall   Comment [PF22]:
       BLOCK [level] TO [level] AT                              reject the sending of a UM28 message element       PDR #266
       OR BEFORE TIME [time]                                    including a vertical range.
       UM29R DESCEND TO REACH UM29 DESCEND TO REACH NIR-21                When accommodating an
       [level] BEFORE PASSING [altitude] BY [position] ATN UM29R including a single level and the
       [position ATW]                                  positionATW parameter contains a positionR, the
                                                       ATN ground system shall convert the ATN
                                                       message UM29R to the FANS 1/A message
                                                       UM29.
                                                       See paragraph 3.2.2.12.1 for use of level
                                                       parameter.
                                                       See paragraph 3.2.2.12.3 for use of positionR
                                                       parameter.
                                                       Note. The displayed message text is different in
                                                       FANS1/A.
       UM29R DESCEND TO REACH None.                             NIR-22               The ATN ground system shall   Comment [PF23]:
       BLOCK [level] TO LEVEL                                   reject the sending of a UM29R message element      PDR #266
       [level] BEFORE PASSING                                   including a vertical range or an ATW Along Track
       [position ATW]                                           Position.
       UM46R CROSS [position ATW] UM46 CROSS [position] AT      NIR-23             When accommodating an
       AT [level]                 [altitude]                    ATN UM46R including a single level and the
                                                                positionATW parameter contains a positionR, the
                                                                ATN ground system shall convert the ATN
                                                                message UM46R to the FANS 1/A message
                                                                UM46.
                                                                See paragraph 3.2.2.12.3 for use of positionR
                                                                parameter.
                                                                See paragraph 3.2.2.12.1 for use of level
                                                                parameter.
       UM46R CROSS [position ATW] None.                         NIR-24               The ATN ground system shall   Comment [PF24]:
       BETWEEN [level] AND [level]                              reject the sending of a UM46R message element      PDR #266
                                                                including a vertical range or an ATW Along Track
                                                                Position.
                                                                                                  3-63


ATN Message Element        FANS 1/A Message Element   Interoperability Requirement
UM47R CROSS [position ATW] UM47 CROSS [position] AT   NIR-25               When     the     positionATW
AT OR ABOVE [level single] OR ABOVE [altitude]        parameter contains a positionR, the ATN ground
                                                      system shall convert the ATN message UM47R to
                                                      the FANS 1/A message UM47.
                                                      See paragraph 3.2.2.12.3 for use of position
                                                      parameter.
                                                      See paragraph 3.2.2.12.1 for use of level single
                                                      parameter.
                                                      NIR-26               The ATN ground system shall
                                                      reject the sending of a UM47R message element
                                                      including an ATW Along Track Position.
UM48R CROSS [position ATW] UM48 CROSS [position] AT   NIR-27               When     the     positionATW
AT OR BELOW LEVEL [level OR BELOW [altitude]          parameter contains a positionR, the ATN ground
single]                                               system shall convert the ATN message UM48R to
                                                      the FANS 1/A message UM48.
                                                      See paragraph 3.2.2.12.3 for use of positionR
                                                      parameter.
                                                      See paragraph 3.2.2.12.1 for use of level single
                                                      parameter.
                                                      NIR-28               The ATN ground system shall
                                                      reject the sending of a UM48R message element
                                                      including an ATW Along Track Position.
UM51R CROSS [position ATW] UM51 CROSS [position] AT   NIR-29               When     the     positionATW
AT TIME [RTAtimesec]       [time]                     parameter contains a positionR, the ATN ground
                                                      system shall convert the ATN message UM51R to
                                                      the FANS 1/A message UM51.
                                                      See paragraph 3.2.2.12.3 for use of positionR
                                                      parameter.
                                                      See paragraph 3.2.2.12.33 for use of the            Comment [PF25]:
                                                      time/RTATimesec parameter.                          COMMENT #1218
                                                      Note. UM51R is not sent when a tolerance or
                                                      seconds are specified.
                                                      NIR-30               The ATN ground system shall
                                                      reject the sending of a UM51R message element
                                                      including an ATW Along Track Position or an
                                                      RTA tolerance.
UM52R CROSS [position ATW] UM52 CROSS [position] AT   NIR-31               When     the     positionATW
AT OR BEFORE TIME          OR BEFORE [time]           parameter contains a positionR, the ATN ground
[timesec]                                             system shall convert the ATN message UM52R to
                                                      the FANS 1/A message UM52.
                                                      See paragraph 3.2.2.12.3 for use of positionR
                                                      parameter.
                                                      See paragraph 3.2.2.12.7 for use of the
                                                      time/timesec parameter.
                                                      Note. UM52R is not sent when seconds are
                                                      specified in timesec.
                                                      NIR-32               The ATN ground system shall
                                                      reject the sending of a UM52R message element
                                                      including an ATW Along Track Position and an
                                                      indication of seconds.
3-64


       ATN Message Element        FANS 1/A Message Element    Interoperability Requirement
       UM53R CROSS [position ATW] UM53 CROSS [position] AT    NIR-33               When     the     positionATW
       AT OR AFTER TIME [timesec] OR AFTER [time]             parameter contains a positionR, the ATN ground
                                                              system shall convert the ATN message UM53R to
                                                              the FANS 1/A message UM53.
                                                              See paragraph 3.2.2.12.3 for use of positionR
                                                              parameter.
                                                              See paragraph 3.2.2.12.7 for use of the
                                                              time/timesec parameter.
                                                              Note. UM53R is not sent when seconds are
                                                              specified in timesec
                                                              NIR-34               The ATN ground system shall
                                                              reject the sending of a UM53R message element
                                                              including an ATW Along Track Position or an
                                                              indication of seconds.
       UM54R CROSS [position ATW] UM54 CROSS [position]       NIR-35               When     the     positionATW
       BETWEEN AT OR BEFORE       BETWEEN [time] AND [time]   parameter contains a positionR, the ATN ground
       TIME [timesec] AND AT OR                               system shall convert the ATN message UM54R to       Comment [PF26]:
       BEFORE TIME [timesec]                                  the FANS 1/A message UM54.                          COMMENT #1218
                                                              See paragraph 3.2.2.12.3 for use of positionR       PDR #295
                                                              parameter.
                                                              See paragraph 3.2.2.12.7 for use of the
                                                              time/timesec parameter.
                                                              Note. UM54R is not sent when seconds are
                                                              specified in timesec.
                                                              NIR-36               The ATN ground system shall
                                                              reject the sending of a UM54R message element
                                                              including an ATW Along Track Position or an
                                                              indication of seconds.
       UM55R CROSS [position ATW] UM55 CROSS [position] AT    NIR-37               When     the     positionATW
       AT [speed]                 [speed]                     parameter contains a positionR, the ATN ground
                                                              system shall convert the ATN message UM55R to
                                                              the FANS 1/A message UM55.
                                                              See paragraph 3.2.2.12.3 for use of positionR
                                                              parameter.
                                                              See paragraph 3.2.2.12.4 for use of speed
                                                              parameter.
                                                              NIR-38               The ATN ground system shall
                                                              reject the sending of a UM55R message element
                                                              including an ATW Along Track Position.
                                                              NIR-39               When     the     positionATW
       UM56R CROSS [position ATW] UM56 CROSS [position] AT
                                                              parameter contains a positionR, the ATN ground
       AT [speed] OR LESS         OR LESS THAN [speed]
                                                              system shall convert the ATN message UM56R to
                                                              the FANS 1/A message UM56.
                                                              See paragraph 3.2.2.12.3 for use of positionR
                                                              parameter.
                                                              See paragraph 3.2.2.12.4 for use of speed
                                                              parameter.
                                                              NIR-40               The ATN ground system shall
                                                              reject the sending of a UM56R message element
                                                              including an ATW Along Track Position.
                                                                                                     3-65


ATN Message Element           FANS 1/A Message Element   Interoperability Requirement
UM57R CROSS [position ATW] UM57 CROSS [position] AT      NIR-41               When     the     positionATW
AT [speed] OR GREATER      OR GREATER THAN [speed]       parameter contains a positionR, the ATN ground
                                                         system shall convert the ATN message UM57R to
                                                         the FANS 1/A message UM57.
                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                         parameter.
                                                         See paragraph 3.2.2.12.4 for use of speed
                                                         parameter.
                                                         NIR-42               The ATN ground system shall
                                                         reject the sending of a UM57R message element
                                                         including an ATW Along Track Position.
UM58R62R CROSS [position      UM58 CROSS [position] AT   NIR-43             When accommodating an
ATW] AT TIME [RTAtimesec]     [time] AT [altitude]       ATN UM58R62R including a single level and the
AT [level]                                               positionATW parameter contains a positionR, the
                              Or
                                                         ATN ground system shall convert the ATN
                              UM62 AT [time] CROSS       message UM58R62R to the FANS 1/A message
                              [position] AT AND          UM58.
                              MAINTAIN [altitude]
                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                         parameter.
                                                         See paragraph 3.2.2.12.33 for use of the            Comment [PF27]:
                                                         time/RTATimesec parameter.                          COMMENT #1218
                                                         See paragraph 3.2.2.12.1 for use of level
                                                         parameter.
                                                         Note. UM58R62R is not sent when an RTA
                                                         tolerance or seconds are specified.
UM58R62R CROSS [position      None.                      NIR-44               The ATN ground system shall
ATW] AT TIME [RTAtimesec]                                reject the sending of a UM58R62R message
BETWEEN [level] AND [level]                              element including a vertical range, an ATW Along    Comment [PF28]:
                                                         Track Position, an RTA tolerance or an indication   PDR #266
                                                         of seconds.
UM59R CROSS [position ATW] UM59 CROSS [position] AT      NIR-45               When accommodating an
AT OR BEFORE TIME          OR BEFORE [time] AT           ATN UM59R including a single level and the
[timesec] AT [level]       [altitude]                    positionATW parameter contains a positionR, the
                                                         ATN ground system shall convert the ATN
                                                         message UM59R to the FANS 1/A message
                                                         UM59.
                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                         parameter.
                                                         See paragraph 3.2.2.12.7 for use of the             Comment [PF29]:
                                                         time/timesec parameter.                             COMMENT #1218
                                                         Note. UM59R is not sent when seconds are
                                                         specified in timesec
                                                         See paragraph 3.2.2.12.1 for use of level
                                                         parameter.
UM59R CROSS [position ATW] None.                         NIR-46              The ATN ground system shall
AT OR BEFORE TIME                                        reject the sending of a UM59R message element
[timesec] BETWEEN [level]                                including a vertical range, an ATW Along Track      Comment [PF30]:
AND [level]                                              Position or an indication of seconds.               PDR #266
3-66


       ATN Message Element             FANS 1/A Message Element          Interoperability Requirement
       UM60R CROSS [position ATW] UM60 CROSS [position] AT               NIR-47              When accommodating an
       AT OR AFTER TIME           OR AFTER [time] AT                     ATN UM60R including a single level and the
       [RTAtimesec] AT [level]    [altitude]                             positionATW parameter contains a positionR, the
                                                                         ATN ground system shall convert the ATN
                                                                         message UM60R to the FANS 1/A message
                                                                         UM60.
                                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                                         parameter.
                                                                         See paragraph 3.2.2.12.33 for use of the           Comment [PF31]:
                                                                         time/RTATimesec parameter.                         COMMENT #1218
                                                                         See paragraph 3.2.2.12.1 for use of level
                                                                         parameter.
                                                                         Note. UM51R is not sent when a tolerance or
                                                                         seconds are specified.
       UM60R CROSS [position ATW] None.                                  NIR-48              The ATN ground system shall
       AT OR AFTER TIME                                                  reject the sending of a UM60R message element
       [RTAtimesec] BETWEEN                                              including a vertical range, an ATW Along Track
       [level] AND [level]                                               Position, an RTA tolerance or an indication of
                                                                         seconds.
       UM61R CROSS [position ATW] UM61 CROSS [position] AT               NIR-49              When accommodating an          Comment [PF32]:
       AT [level] AT [speed]      AND MAINTAIN [altitude]                ATN UM61R including a single level and the         PDR #268
                                  AT [speed]                             positionATW parameter contains a positionR, the
                                                                         ATN ground system shall convert the ATN
                                                                         message UM61R to the FANS 1/A message
                                                                         UM61.
                                                                         See paragraph 3.2.2.12.3 for use of positionR
                                                                         parameter.
                                                                         See paragraph 3.2.2.12.1 for use of level
                                                                         parameter.
                                                                         See paragraph 3.2.2.12.4 for use of speed
                                                                         parameter.
                                                                         Note. The displayed message text is different in
                                                                         FANS1/A.
       UM61R CROSS [position ATW] None.                                  NIR-50               The ATN ground system shall
       BETWEEN [level] AND [level]                                       reject the sending of a UM61R message element
       AT [speed]                                                        including a vertical range or an ATW Along Track
                                                                         Position.
                                                                         NIR-51              (deleted)                      Comment [PF33]:
                                                                                                                            PDR #342 1/

                                                                         NIR-52              (deleted)

       UM64R OFFSET [specified         UM64 OFFSET                       See paragraph 3.2.2.12.5 for use of specified
       distance] [direction side] OF   [distanceoffset] [direction] OF   distance / distance offset parameter.
       ROUTE                           ROUTE
                                                                                                                3-67


ATN Message Element           FANS 1/A Message Element          Interoperability Requirement

UM65R AT [position ATW]       UM65 AT [position] OFFSET         NIR-J-IR 3                 When
OFFSET [specified distance]   [distanceoffset] [direction] OF       accommodating an ATN UM65R including a
[direction side] OF ROUTE     ROUTE                                 positionATW parameter that contains a
                                                                    positionR, the ATN ground system shall
                                                                    convert the ATN UM65R message element to
                                                                    the FANS 1/A UM65 message element.
                                                                NIR-J-IR 4                    The ATN ground
                                                                    system shall reject the sending of a UM65R
                                                                    message element including a ATW Along
                                                                    Track Position.
                                                                See paragraph 3.2.2.12.3 for use of positionR
                                                                parameter.
                                                                See paragraph 3.2.2.12.5 for use of specified
                                                                distance / distance offset parameter.

UM66R AT TIME [time]          UM66 AT [time] OFFSET             See paragraph 3.2.2.12.5 for use of specified
OFFSET [specified distance]   [distanceoffset] [direction] OF   distance / distance offset parameter.
[direction side] OF ROUTE     ROUTE

                                                                None.                                                  Comment [PF34]:
UM67 REJOIN ROUTE             UM67 PROCEED BACK ON
                                                                                                                       PDR 280 23)
                              ROUTE

                                                                NIR-53               When     the    positionATW
UM68R REJOIN ROUTE            UM68 REJOIN ROUTE BY
                                                                parameter contains a positionR, the ATN ground
BEFORE PASSING [position      [position]
                                                                system shall convert the ATN message UM68R to
ATW]
                                                                the FANS 1/A message UM68.
                                                                See paragraph 3.2.2.12.3 for use of positionR
                                                                parameter.
                                                                 Note. The displayed message text is different in
                                                                FANS1/A.
                                                                NIR-54               The ATN ground system shall
                                                                reject the sending of a UM68 message element
                                                                including an ATW Along Track Position.
                                                                None.                                                  Comment [PF35]:
UM69 REJOIN ROUTE AT OR       UM69 REJOIN ROUTE BY
                                                                                                                       PDR #345 3)
BEFORE TIME [time]            [time]

                                                                                                                       Comment [PF36]:
UM70R EXPECT BACK ON          UM70 EXPECT BACK ON               NIR-J-IR 5                 When
                                                                                                                       PDR #135, #280 23)
ROUTE BEFORE PASSING          ROUTE BY [position]                   accommodating an ATN UM70R, the ATN
[position R]                                                        ground system shall convert the ATN
                                                                    UM70R message element to the FANS 1/A
                                                                    UM70 message element.
                                                                See paragraph 3.2.2.12.3 for use of positionR
                                                                parameter.
                                                                Note. The displayed message text is different in
                                                                FANS1/A.

UM71 EXPECT BACK ON           UM71 EXPECT BACK ON               None.
ROUTE BEFORE TIME [time]      ROUTE BY [time]                   Note. The displayed message text is different in
                                                                FANS1/A.
3-68


       ATN Message Element            FANS 1/A Message Element        Interoperability Requirement
       UM72 RESUME OWN                UM72 RESUME OWN                 None.
       NAVIGATION                     NAVIGATION
       UM73R [departure clearanceR]   UM80 CLEARED                    NIR-55               The ATN ground system shall
                                      [routeClearance] + UM169        convert the ATN message UM73R to the FANS
                                      [freetext] + UM158 ATIS [atis   1/A message UM80 + UM169 + UM158 +
                                      code] + UM123 SQUAWK            UM123 + UM19.
                                      [code] + UM19 MAINTAIN          See paragraph 3.2.2.12.19 for use of the departure   Comment [P37]:
                                      [altitude]                      clearance routing / predeparture clearance           COMMENT #811
                                                                      parameter.
       UM74R PROCEED DIRECT           UM74 PROCEED DIRECT             NIR-J-IR 6                 When
       TO [positionR]                 TO [position]                       accommodating an ATN UM74R, the ATN
                                                                          ground system shall convert the ATN
                                                                          UM74R message element to the FANS 1/A
                                                                          UM74 message element.
                                                                      See paragraph 3.2.2.12.2 or use of positionR
                                                                      parameter.
                                      UM75 WHEN ABLE                  NIR-56              (deleted)
                                      PROCEED DIRECT TO
                                      [position]

       UM76R AT TIME [time]           UM76 AT [time] PROCEED          NIR-J-IR 7                 When
       PROCEED DIRECT TO              DIRECT TO [position]                accommodating an ATN UM76R, the ATN
       [positionR]                                                        ground system shall convert the ATN
                                                                          UM76R message element to the FANS 1/A
                                                                          UM76 message element.
                                                                      See paragraph 3.2.2.12.3 for use of positionR
                                                                      parameter.

       UM77R AT [position ATW]        UM77 AT [position]              NIR-J-IR 8                 When
       PROCEED DIRECT TO              PROCEED DIRECT TO                   accommodating an ATN UM77R including
       [positionR]                    [position]                          the positionATW parameter that contains a
                                                                          positionR, the ATN ground system shall
                                                                          convert the ATN UM77R message element to
                                                                          the FANS 1/A UM77 message element.
                                                                      NIR-J-IR 9                    The ATN ground
                                                                          system shall reject the sending of a UM77R
                                                                          message element including an ATW Along
                                                                          Track Position.
                                                                      See paragraph 3.2.2.12.3 for use of positionR
                                                                      parameter.
       UM78R AT [level single]        UM78 AT [altitude]              NIR-J-IR 10                When
       PROCEED DIRECT TO              PROCEED DIRECT TO                   accommodating an ATN UM78R, the ATN
       [positionR]                    [position]                          ground system shall convert the ATN
                                                                          UM78R message element to the FANS 1/A
                                                                          UM78 message element.
                                                                      See paragraph 3.2.2.12.1 for use of level single
                                                                      parameter.
                                                                      See paragraph 3.2.2.12.3 for use of positionR
                                                                      parameter.
                                                                                                              3-69


ATN Message Element          FANS 1/A Message Element         Interoperability Requirement
UM79R CLEARED TO             UM79 CLEARED TO                 NIR-J-IR 11                When
[positionR] VIA [route       [position] VIA [routeclearance]     accommodating an ATN UM79R, the ATN
clearanceR]                                                      ground system shall convert the ATN
                                                                 UM79R message element to the FANS 1/A
                                                                 UM79 message element.
                                                              See paragraph 3.2.2.12.3 for use of positionR
                                                              parameter.
                                                              See paragraph 3.2.2.12.12 for use of route
                                                              clearanceR / route clearance parameter.
UM80R CLEARED [route         UM80 CLEARED                     NIR-J-IR 12                When
clearanceR]                  [routeclearance]                     accommodating an ATN UM80R, the ATN
                                                                  ground system shall convert the ATN UM0R
                                                                  message element to the FANS 1/A UM80
                                                                  message element.
                                                              See paragraph 3.2.2.12.12 for use of route
                                                              clearanceR /route clearance parameter.
UM81R CLEARED [procedure     UM81 CLEARED                     NIR-J-IR 13                When
nameR]                       [procedurename]                      accommodating an ATN UM81R, the ATN
                                                                  ground system shall convert the ATN
                                                                  UM81R message element to the FANS 1/A
                                                                  UM81 message element.
                                                              See paragraph 3.2.2.12.20 for use of procedure
                                                              nameR parameter.
UM82R CLEARED TO             UM82 CLEARED TO                  NIR-57               The ATN ground system shall
DEVIATE UP TO [lateral       DEVIATE UP TO                    reject the sending of the ATN message UM82R
deviation] OF ROUTE          [disanceoffset] [direction] OF   when       it    contains     more     than   one
                             ROUTE                            distanceSpecifiedDirection parameter.
                                                              See paragraph 3.2.2.12.5 for use of specified
                                                              distance / distance offset parameter.
                                                              See paragraph 3.2.2.12.6 for use of direction
                                                              parameter.
UM83R AT [position ATW]      UM83 AT [position]               NIR-J-IR 14                When
CLEARED [route clearanceR]   CLEARED [routeclearance]             accommodating an ATN UM83R including a
                                                                  positionATW parameter that contains a
                                                                  positionR, the ATN ground system shall
                                                                  convert the ATN UM83R message element
                                                                  to the FANS 1/A UM83 message element,
                                                              See paragraph 3.2.2.12.3 for use of positionR
                                                              parameter.
                                                              See paragraph 3.2.2.12.12 for use of route
                                                              clearanceR parameter.
UM84R AT [positionR]         UM84 AT [position]               See paragraph 3.2.2.12.3 for use of positionR
CLEARED [procedure nameR]    CLEARED [procedurename]          parameter.
                                                              See paragraph 3.2.2.12.20 for use of named
                                                              instruction parameter.
3-70


       ATN Message Element           FANS 1/A Message Element      Interoperability Requirement
       UM91R AT [positionR] HOLD     UM169 ‘AT [positionR]         NIR-58              The ATN ground system shall    Comment [PF38]:
       INBOUND TRACK [degrees]       HOLD INBOUND TRACK            convert the ATN UM91R message elements to the      COMMENT #1087
       [direction side] TURNS [leg   [degrees] [direction] TURNS   FANS 1/A UM169 message element.                    PR#142, #274
       type]                         [leg type]’                   See paragraph 3.2.2.12.3 for use of positionR
                                                                   parameter.
                                                                   Note. FANS1/A UM91 HOLD AT [position]
                                                                   MAINTAIN [altitude] INBOUND TRACK
                                                                   [degrees] [direction] TURNS [legtype] cannot be
                                                                   used because of altitude parameter.
       UM92R AT [positionR] HOLD     UM169 ‘AT [positionR]         NIR-59             The ATN ground system shall
       [directionO] AS PUBLISHED     HOLD [directionO] AS          convert the ATN UM92R message elements to the
                                     PUBLISHED’                    FANS 1/A UM169 message element.
                                                                   See paragraph 3.2.2.12.3 for use of positionR
                                                                   parameter.
                                                                   Note. FANS1/A UM92 HOLD AT [position] AS
                                                                   PUBLISHED MAINTAIN [altitude] cannot be
                                                                   used because of missing altitude parameter.
       UM93 EXPECT FURTHER           UM93 EXPECT FURTHER           None.                                              Comment [PF39]:
       CLEARANCE AT TIME [time]      CLEARANCE AT [time]                                                              PDR #263

       UM94R TURN [direction side]   UM94 TURN [direction]         NIR-60             The ATN ground system shall
       HEADING [degrees]             HEADING [degrees]             convert the ATN message UM94R to the FANS
                                                                   1/A message UM94.
                                                                   See paragraph 3.2.2.12.11 for use of degrees
                                                                   parameter.


       UM95R TURN [direction side]   UM95 TURN [direction]         NIR-61             The ATN ground system shall
       GROUND TRACK [degrees]        GROUND TRACK [degrees]        convert the ATN message UM95R to the FANS
       DEGREES                                                     1/A message UM95.
                                                                   See paragraph 3.2.2.12.11 for use of degrees
                                                                   parameter.
       UM96 CONTINUE PRESENT         UM96 FLY PRESENT              None.
       HEADING                       HEADING                       Note. The displayed message text is different in
                                                                   FANS1/A.
       UM97R AT [position ATW]       UM97 AT [position] FLY        NIR-62               When     the    positionATW
       FLY HEADING [degrees]         HEADING [degrees]             parameter contains a positionR, the ATN ground
                                                                   system shall convert the ATN message UM97R to
                                                                   the FANS 1/A message UM97.
                                                                   See paragraph 3.2.2.12.3 for use of positionR
                                                                   parameter.
                                                                   See paragraph 3.2.2.12.11 for use of degrees
                                                                   parameter.
                                                                   NIR-63               The ATN ground system shall
                                                                   reject the sending of a UM97R message element
                                                                   including an ATW Along Track Position.
                                                                                                       3-71


ATN Message Element        FANS 1/A Message Element   Interoperability Requirement
UM99R EXPECT [named        UM99 EXPECT                NIR-64              The ATN ground system shall
instruction]               [procedurename]            convert the ATN message UM99R to the FANS
                                                      1/A message UM99.
                                                      See paragraph 3.2.2.12.20 for use of named
                                                      instruction parameter.
                                                      Note. UM81R is not sent when the instruction
                                                      contains a clearance name
                           UM169 ‘EXPECT SPEED                                                                Comment [PF40]:
UM100R EXPECT SPEED                                   NIR-J-IR 15                 The ATN ground
                           CHANGE AT TIME [time]’                                                             PDR #263, #352
CHANGE AT TIME [time]                                     system shall convert the ATN UM100R
                                                          message into FANS 1/A UM169.
                                                      See paragraph 3.2.2.12.7 for use of time parameter
                                                      sent as a free text.
                                                      See paragraph 3.2.2.12.4 for use of speed
                                                      parameter.

UM101R EXPECT SPEED        UM169 ‘EXPECT SPEED        NIR-J-IR 16                When
CHANGE AT [positionR]      CHANGE AT [published           accommodating an ATN UM101R, the ATN
                           identifier name]’              ground system shall convert the ATN
                                                          UM101R message element to the FANS 1/A
                                                          UM169 message element.
                                                      See paragraph 3.2.2.12.2 for the syntax of the
                                                      ATN [positionR] parameter sent as a free text
                                                      parameter.

UM102R EXPECT SPEED        UM169 ‘EXPECT SPEED        NIR-J-IR 17                When
CHANGE AT [level single]   CHANGE AT [altitude]’          accommodating an ATN UM102R, the ATN
                                                          ground system shall convert the ATN
                                                          UM102R message element to the FANS 1/A
                                                          UM169 message element.
                                                      See paragraph 3.2.2.12.1 for use of level
                                                      parameter when sent as a free text.
UM106 MAINTAIN [speed]     UM106 MAINTAIN [speed]     See paragraph 3.2.2.12.4 for use of speed
                                                      parameter.
UM107 MAINTAIN PRESENT     UM107 MAINTAIN             None.
SPEED                      PRESENT SPEED
UM108 MAINTAIN [speed] OR UM108 MAINTAIN [speed]      See paragraph 3.2.2.12.4 for use of speed
GREATER                   OR GREATER                  parameter.
UM109 MAINTAIN [speed] OR UM109 MAINTAIN [speed]      See paragraph 3.2.2.12.4 for use of speed
LESS                      OR LESS                     parameter.
UM110 MAINTAIN [speed] TO UM110 MAINTAIN [speed]      See paragraph 3.2.2.12.4 for use of speed
[speed]                   TO [speed]                  parameter.
UM111R INCREASE SPEED      None.                      NIR-65               The ATN ground system shall
[speed delta]                                         reject the sending of a UM111R message element.
                                                      Note. Not viable. The use of FANS 1/A message
                                                      element UM169 to use the ATN message UM111R
                                                      is not considered a valid option in this document
                                                      (no free text UM with W/U response attribute).
3-72


       ATN Message Element             FANS 1/A Message Element     Interoperability Requirement
       UM113R REDUCE SPEED             None.                        NIR-66               The ATN ground system shall
       [speed delta]                                                reject the sending of a UM113R message element.
                                                                    Note. Not viable. The use of FANS 1/A message
                                                                    element UM169 to use the ATN message UM113R
                                                                    is not considered a valid option in this document
                                                                    (no free text UM with W/U response attribute).
       UM116 RESUME NORMAL             UM116 RESUME NORMAL          None.
       SPEED                           SPEED
       UM117 R CONTACT [unit id]       UM117 CONTACT                See paragraph 3.2.2.12.10 for use of unit id        Comment [PF41]:
       [frequency]                     [icaounitname] [frequency]   parameter.                                          PDR #276
                                                                    See paragraph 3.2.2.12.17 for use of frequency
                                                                    parameter.
       UM118R AT [position ground      UM118 AT [position]          NIR-67             When [position ground air]       Comment [PF42]:
       air] CONTACT [unit id]          CONTACT [icaounitname]       contains an AirPosition, the ATN ground system      PDR #276, #297
       [frequency]                     [frequency]                  shall convert the ATN message UM118R to the
                                                                    FANS 1/A message UM118.
                                                                    See paragraph 3.2.2.12.3 for use of positionR
                                                                    parameter.
                                                                    See paragraph 3.2.2.12.10 for use of unit id
                                                                    parameter.
                                                                    See paragraph 3.2.2.12.17 for use of frequency
                                                                    parameter.
                                                                    NIR-68             When [position ground air]
                                                                    contains a GroundLocation, the ATN ground
                                                                    system shall reject the sending of the ATN
                                                                    message UM118R.
       UM119R AT TIME [time]           UM119 AT [time] CONTACT      NIR-69             The ATN ground system shall      Comment [PF43]:
       CONTACT [unit id] [frequency]   [icaounitname] [frequency]   convert the ATN message UM119R to the FANS          PDR #276, #297
                                                                    1/A message UM119.
                                                                    See paragraph 3.2.2.12.10 for use of unit id
                                                                    parameter.
                                                                    See paragraph 3.2.2.12.17 for use of frequency
                                                                    parameter.
                                                                    NIR-70             (deleted)
       UM120R MONITOR [unit id]        UM120 MONITOR                See paragraph 3.2.2.12.10 for use of unit id        Comment [PF44]:
       [frequency]                     [icaounitname] [frequency]   parameter.                                          PDR #276
                                                                    See paragraph 3.2.2.12.17 for use of frequency
                                                                    parameter.
                                                                                                            3-73


ATN Message Element             FANS 1/A Message Element     Interoperability Requirement
UM121R AT [position ground      UM121 AT [position]          NIR-71             When [position ground air]         Comment [PF45]:
air] MONITOR [unit id]          MONITOR [icaounitname]       contains an AirPosition, the ATN ground system        PDR #276, #297
[frequency]                     [frequency]                  shall convert the ATN message UM121R to the
                                                             FANS 1/A message UM121.
                                                             See paragraph 3.2.2.12.3 for use of positionR
                                                             parameter.
                                                             See paragraph 3.2.2.12.10 for use of unit id
                                                             parameter.
                                                             See paragraph 3.2.2.12.17 for use of frequency
                                                             parameter.
                                                             NIR-72             When [position ground air]
                                                             contains a GroundLocation, the ATN ground
                                                             system shall reject the sending of the ATN
                                                             message UM121R.
UM122R AT TIME [time]           UM122 AT [time] MONITOR      NIR-73             The ATN ground system shall        Comment [PF46]:
MONITOR [unit id] [frequency]   [icaounitname] [frequency]   convert the ATN message UM122R to the FANS            PDR #276, #297
                                                             1/A message UM122.
                                                             See paragraph 3.2.2.12.10 for use of unit id
                                                             parameter.
                                                             See paragraph 3.2.2.12.17 for use of frequency
                                                             parameter.
                                                             NIR-74             (deleted)
UM123 SQUAWK [code]             UM123 SQUAWK                 See paragraph 3.2.2.12.18 for use of
                                [beaconcode]                 code/beaconcode parameter.
UM124 STOP SQUAWK               UM124 STOP SQUAWK            None.
UM125 SQUAWK MODE               UM125 ALTITUDE               None.
CHARLIE                         CHARLIE                      Note. The displayed message text is different in
                                                             FANS1/A.
UM126 STOP SQUAWK               UM126 STOP ALTITUDE          None.
MODE CHARLIE                    CHARLIE                      Note. The displayed message text is different in
                                                             FANS1/A.
UM127 REPORT BACK ON            UM127 REPORT BACK ON         None.
ROUTE                           ROUTE
                  Resp (W/U)                       Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                            and R responses.
UM128R REPORT LEAVING           UM128 REPORT LEAVING         See paragraph 3.2.2.12.1 for use of level single
[level single]                  [altitude]                   parameter.
                  Resp (W/U)                       Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                            and R responses.
UM129R REPORT                   UM129 REPORT LEVEL           See paragraph 3.2.2.12.1 for use of level single
MAINTAINING [level single]      [altitude]                   parameter.
                                                             Note. The displayed message text is different in
                                                             FANS1/A.
                  Resp (W/U)                       Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                            and R responses.
3-74


       ATN Message Element          FANS 1/A Message Element    Interoperability Requirement
       UM130R REPORT PASSING        UM130 REPORT PASSING        NIR-J-IR 18                When
       [positionR]                  [position]                      accommodating an ATN UM130R, the ATN
                                                                    ground system shall convert the ATN
                                                                    UM130R message element to the FANS 1/A
                                                                    UM130 message element.
                                                                See paragraph 3.2.2.12.3 for use of positionR
                                                                parameter.
                       Resp (W/U)                     Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                               and R responses.
       UM131 REPORT          UM131 REPORT                       None.
       ENDURANCE AND PERSONS REMAINING FUEL AND                 Note. The displayed message text is different in   Comment [PF47]:
       ON BOARD              PERSONS ON BOARD                   FANS1/A.                                           PDR #280

                         Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                              with message element attributes.
                                                              See paragraph 3.2.2.13.2 for processing message
                                                              elements with a “Y” response attribute.
       UM132 REPORT POSITION        UM132 CONFIRM               Note. The displayed message text is different in
                                    POSITION                    FANS1/A.
                         Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                              with message element attributes.
                                                              See paragraph 3.2.2.13.2 for processing message
                                                              elements with a “Y” response attribute.
       UM133 REPORT PRESENT         UM133 CONFIRM               Note. The displayed message text is different in
       LEVEL                        ALTITUDE                    FANS1/A.
                         Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                              with message element attributes.
                                                              See paragraph 3.2.2.13.2 for processing message
                                                              elements with a “Y” response attribute.
       UM134R REPORT [speed         UM134 CONFIRM SPEED         Note: The response received from a FANS 1/A
       types] SPEED                                             aircraft may not match the [speed types]
                                                                requested.
                                                                Note. The displayed message text is different in
                                                                FANS1/A.
                         Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                              with message element attributes.
                                                              See paragraph 3.2.2.13.2 for processing message
                                                              elements with a “Y” response attribute.
       UM135 CONFIRM ASSIGNED       UM135 CONFIRM               None.
       LEVEL                        ASSIGNED ALTITUDE
                         Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                              with message element attributes.
                                                              See paragraph 3.2.2.13.2 for processing message
                                                              elements with a “Y” response attribute.
                                                                                                     3-75


ATN Message Element          FANS 1/A Message Element    Interoperability Requirement
UM136 CONFIRM ASSIGNED       UM136 CONFIRM               None.
SPEED                        ASSIGNED SPEED
                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
UM137 CONFIRM ASSIGNED       UM137 CONFIRM               None.
ROUTE                        ASSIGNED ROUTE
                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
UM140 CONFIRM NEXT           UM140 CONFIRM NEXT          None.                                              Comment [PF48]:
WAYPOINT                     WAYPOINT                                                                       PDR #280 22)

                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
UM141 CONFIRM NEXT           UM141 CONFIRM NEXT          None.                                              Comment [PF49]:
WAYPOINT ETA                 WAYPOINT ETA                                                                   PDR #280 22)

                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
UM142 CONFIRM ENSUING        UM142 CONFIRM ENSUING None.                                                    Comment [PF50]:
WAYPOINT                     WAYPOINT                                                                       PDR #280 22)

                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
UM143 CONFIRM REQUEST        UM143 CONFIRM REQUEST None
                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
UM144 CONFIRM SQUAWK         UM144 CONFIRM SQUAWK None.
                  Resp (Y)                    Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                        with message element attributes.
                                                        See paragraph 3.2.2.13.2 for processing message
                                                        elements with a “Y” response attribute.
3-76


       ATN Message Element              FANS 1/A Message Element   Interoperability Requirement
       UM146 REPORT GROUND              UM146 CONFIRM GROUND       None.
       TRACK                            TRACK
                             Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                                  with message element attributes.
                                                                  See paragraph 3.2.2.13.2 for processing message
                                                                  elements with a “Y” response attribute.
       UM147 REQUEST POSITION           UM147 REQUEST POSITION None.
       REPORT                           REPORT
                             Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                                  with message element attributes.
                                                                  See paragraph 3.2.2.13.2 for processing message
                                                                  elements with a “Y” response attribute.
       UM148R WHEN CAN YOU              UM148 WHEN CAN YOU         See paragraph 3.2.2.12.1 for use of level single
       ACCEPT [level single]            ACCEPT [altitude]          parameter.
                             Resp (Y)                   Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                                  with message element attributes.
                                                                  See paragraph 3.2.2.13.2 for processing message
                                                                  elements with a “Y” response attribute.
       UM149R CAN YOU ACCEPT            UM149 CAN YOU ACCEPT       NIR-J-IR 19                When
       [level single] AT [positionR]    [altitude] AT [position]       accommodating an ATN UM149R, the ATN
                                                                       ground system shall convert the ATN
                                                                       UM149R message element to the FANS 1/A
                                                                       UM149 message element,
                                                                   See paragraph 3.2.2.12.1 for use of level single
                                                                   parameter.
                                                                   See paragraph 3.2.2.12.3 for use of positionR
                                                                   parameter.
       UM150R CAN YOU ACCEPT            UM150 CAN YOU ACCEPT       See paragraph 3.2.2.12.1 for use of level single
       [level single] AT TIME [time]    [altitude] AT [time]       parameter.
       UM151 WHEN CAN YOU               None.                      NIR-75               The ATN ground system shall   Comment [PF51]:
       ACCEPT [speed]                                              reject the sending of a UM151 message element.     COMMENT #1279
                                                                   Note. The required response downlink messages
                                                                   are not available in FANS 1/A.
                                                                                                       3-77


ATN Message Element           FANS 1/A Message Element   Interoperability Requirement
UM153R213R [facility          [UM169 ‘[ICAO facility     NIR-76              The ATN ground system shall
designationO] ALTIMETER       designation]’] +           convert the ATN UM153R213R message into
[altimeter] [timeO]                                      FANS 1/A UM153, optionally concatenated with         Comment [P52]:
                              UM153 [altimeter] +
                                                         one UM169 message when facility designation is       COMMENT #801
                              [UM169 ‘ ALTIMETER TIME    present and/or one UM169 message when time is        PDR #263, #271
                              [time]’]                   present.
                                                         See paragraph 3.2.2.12.9.2 for use of time
                                                         parameter sent as a free text.
                                                         See paragraph 3.2.2.12.7 for use of Facility
                                                         Designation parameter sent as a free text.
                                                         See paragraph 3.2.2.4, for processing message
                                                         attributes.
                                                         The R response attribute is not the same in the
                                                         ATS INTEROP Standard and the FANS 1/A
                                                         INTEROP Standard.
                                                         Processing the pilot’s UNABLE response is a
                                                         local matter.
UM154 ATS SURVEILLANCE        UM154 RADAR SERVICE        None.                                                Comment [PF53]:
SERVICE TERMINATED            TERMINATED                                                                      PDR #280 5), PDR 279 16) and (con’t)
                                                         Note. The displayed message text is different in
                                                         FANS1/A.
UM155R ATS                    UM169 ‘ATS                 None.
SURVEILLANCE                  SURVEILLANCE
ESTABLISHED                   ESTABLISHED’
UM156 ATS SURVEILLANCE        UM156 RADAR CONTACT        None.                                                Comment [PF54]:
CONTACT LOST                  LOST                                                                            PDR #280 17)
                                                         Note. The displayed message text is different in
                                                         FANS1/A.
UM157R CHECK STUCK            UM157 CHECK STUCK          NIR-77            When a frequency is provided,
MICROPHONE                    MICROPHONE [frequency]     the ATN ground system shall convert the ATN
[frequencyO.frequency]                                   UM157R message element into FANS 1/A
                                                         UM157 message element.
                                                         See paragraph 3.2.2.12.17 for use of frequency
                                                         parameter.
                                                         NIR-78            The ATN ground system shall
                                                         ignore the FANS ROGER/STANDBY response               Comment [P55]:
                                                         when received as answer to an ATN UM157R             COMMENT #897
                                                         accommodated to a FANS1/A UM157.
UM157R CHECK STUCK            UM169 ‘CHECK STUCK         NIR-79            When no frequency is
MICROPHONE                    MICROPHONE’                provided, the ATN ground system shall convert
[frequency.noValue]                                      the ATN UM157R message element into
                                                         FANS 1/A UM169 message element.

                   Resp (N)                     Resp (R) NIR-80             The ATN ground system shall       Comment [P56]:
                                                         ignore the FANS ROGER/STANDBY response               COMMENT 798
                                                         when received as a response to an ATN UM157R         Comment [P57]:
                                                         accommodated to a FANS1/A UM169.                     COMMENT #897
3-78


       ATN Message Element           FANS 1/A Message Element    Interoperability Requirement
       UM158R212R [airportO] ATIS    UM169 ‘[airport] ATIS       NIR-81             The ATN ground system shall
       [atis code]                   [ATISCode]’                 convert the ATN UM212 message into FANS 1/A
                                                                 UM169.
                                                                 See paragraph 3.2.2.12.9.2 for the syntax of the
                                                                 ATN [airport] parameter sent as a free text
                                                                 parameter.
                                                                 See paragraph 3.2.2.12.22 for the syntax of the
                                                                 ATN [atis code] parameter sent as a free text
                                                                 parameter.
       UM159 ERROR [error            UM159 ERROR [error          See paragraph 3.2.2.11.2 for use of error
       information]                  information]                information parameter.
       UM160 NEXT DATA               UM160 NEXT DATA             See paragraph 3.2.2.12.9 for use of facility
       AUTHORITY [facility           AUTHORITY                   parameter.
       designationO]                 [icaofacilitydesignation]
       UM162 MESSAGE NOT             UM169 ‘MESSAGE NOT          None.                                               Comment [PF58]:
       SUPPORTED BY THIS ATC         SUPPORTED BY THIS ATC                                                           PDR #357
       UNIT                          UNIT’
       UM164 WHEN READY              UM164 WHEN READY            None.
       UM166 DUE TO [traffic type]   UM166 DUE TO TRAFFIC        None.
       TRAFFIC                                                   Note: FANS 1/A does not use the [traffic type]
                                                                 parameter.
       UM167 DUE TO AIRSPACE         UM167 DUE TO AIRSPACE       None.
       RESTRICTION                   RESTRICTION
       UM169 [free text]             UM169 [free text]           None.
       UM171 CLIMB AT [vertical      UM171 CLIMB AT [vertical    See paragraph 3.2.2.12.8 for use of vertical rate   Comment [PF59]:
       rate] OR GREATER              rate] MINIMUM               parameter.                                          PDR 280 6)
                                                                 Note. The displayed message text is different in
                                                                 FANS1/A.
       UM172 CLIMB AT [vertical      UM172 CLIMB AT [vertical    See paragraph 3.2.2.12.8 for use of vertical rate   Comment [PF60]:
       rate] OR LESS                 rate] MAXIMUM               parameter.                                          PDR 280 6)
                                                                 Note. The displayed message text is different in
                                                                 FANS1/A.
       UM173 DESCEND AT [vertical    UM173 DESCEND AT            See paragraph 3.2.2.12.8 for use of vertical rate   Comment [PF61]:
       rate] OR GREATER              [vertical rate] MINIMUM     parameter.                                          PDR 280 6)
                                                                 Note. The displayed message text is different in
                                                                 FANS1/A.
       UM174 DESCEND AT [vertical    UM174 DESCEND AT            See paragraph 3.2.2.12.8 for use of vertical rate   Comment [PF62]:
       rate] OR LESS                 [vertical rate] MAXIMUM     parameter.                                          PDR 280 6)
                                                                 Note. The displayed message text is different in
                                                                 FANS1/A.


       UM179 SQUAWK IDENT            UM179 SQUAWK IDENT          None.
                                                                                                            3-79


ATN Message Element            FANS 1/A Message Element      Interoperability Requirement
UM180R REPORT REACHING UM180 REPORT REACHING NIR-82                   The ATN ground system shall
BLOCK [level single] TO [level BLOCK [altitude] TO convert the ATN message UM180R to the FANS
single]                        [altitude]          1/A message UM180.
                                                   See paragraph 3.2.2.12.1 for use of level single
                                                   parameter.
UM181R REPORT DISTANCE         UM181 REPORT DISTANCE                                                               Comment [PF63]:
                                                             NIR-J-IR 20                When
[to from] [positionR]          [to/from] [position]                                                                PDR #263, PDR #348
                                                                 accommodating an ATN UM181R, the ATN
                                                                 ground system shall convert the ATN
                                                                 UM181R message element to the FANS 1/A
                                                                 UM181 message element,
                                                             NIR-83             (deleted).
                                                             See paragraph 3.2.2.12.3 for use of position
                                                             parameter.
                    Resp (Y)                      Resp (NE) See paragraph 3.2.2.4 for processing differences
                                                            with message element attributes.
                                                            See paragraph 3.2.2.13.2 for processing message
                                                            elements with a “Y” response attribute.
UM183 [free text]              UM169 [freetext]             IR-74             The ATN ground system shall
                                                            convert ATN UM183 message into FANS1/A
                                                            UM169.
                                                            IR-75             The ATN ground system shall
                                                            use the same character string in FANS 1/A
                                                            UM169 as in ATN UM183.
                    Resp (N)                       Resp (R) IR-76             The ATN ground system shall
                                                            ignore the FANS1/A ROGER /STANDBY                      Comment [P64]:
                                                            response when received as a response to an             COMMENT #897
                                                            accommodated ATN UM183.
                                                                                                                   Comment [P65]:
UM187 [free text]              UM169 [freetext]             NIR-84            The ATN ground system shall          COMMENT #775
                                                            convert FANS 1/A UM187 message into ATN
                                                            UM169.
                                                            NIR-85            The ATN ground system shall
                                                            use the same character string in ATN UM169 as
                                                            in FANS 1/A UM187.
                    Resp (N)                       Resp (R) NIR-86            The ATN ground system shall
                                                            ignore the FANS1/A ROGER/STANDBY                       Comment [P66]:
                                                            response when received as a response to an             COMMENT #897
                                                            accommodated ATN UM187.
                                                                                                                   Comment [P67]:
UM188R AFTER PASSING           None.                         NIR-87               The ATN ground system shall      COMMENT #775
[positionR] MAINTAIN [speed]                                 reject the sending of a UM188R message element.
                                                             Note. Not viable. The use of FANS 1/A message
                                                             element UM169 to use the ATN message UM188R
                                                             is not considered a valid option in this document
                                                             (no free text UM with W/U response attribute).
UM189 ADJUST SPEED TO          None.                         NIR-88               The ATN ground system shall
[speed]                                                      reject the sending of a UM189 message element.
                                                             Note. Not viable. The use of FANS 1/A message
                                                             element UM169 to use the ATN message UM189
                                                             is not considered a valid option in this document
                                                             (no free text UM with W/U response attribute).
3-80


       ATN Message Element            FANS 1/A Message Element            Interoperability Requirement
       UM190 FLY HEADING              UM94 TURN [direction]               IR-77                When the ATN ground system
       [degrees]                      HEADING [degrees] where the         has current heading information and it can
                                      choice for the direction            distinguish the direction of the turn and use the
                                      parameter shall be set to [right]   appropriate choices [left] or [right], the ATN
                                      or [left]                           ground system shall convert ATN UM190
                                                                          message element into the FANS 1/A message
                                                                          element UM94.
                                                                          The use of the FANS 1/A message element
                                                                          UM169 to provide the message content of the
                                                                          ATN message element UM190 is not considered
                                                                          as a valid option (no free text UM with W/U
                                                                          response attribute).
                                                                          See paragraph 3.2.2.12.11 for use of degrees
                                                                          parameter.
                                                                          Note. The displayed message text is different in
                                                                          FANS1/A.
       UM191 AIR TRAFFIC              UM169 ‘AIR TRAFFIC                  NIR-89          The ATN ground system shall
       CONTROL SERVICE                CONTROL SERVICES                    convert the ATN UM191 message element into          Comment [PF68]:
       TERMINATED                     TERMINATED’                         FANS 1/A UM169 message element.                     PDR #280 7)

       UM192R REACH [level single]    None.                               NIR-90               The ATN ground system shall
       AT OR BEFORE TIME [time]                                           reject the sending of a UM192R message element.
                                                                          Note. Not viable. The use of FANS 1/A message
                                                                          element UM169 to use the ATN message UM192R
                                                                          is not considered a valid option in this document
                                                                          (no free text UM with W/U response attribute).
       UM196 [free text]              None                                NIR-91               The ATN ground system shall
                                                                          reject the sending of a UM196 message element.
                                                                          Note. Not viable.The use of FANS 1/A message
                                                                          element UM169 to use the ATN message element
                                                                          UM196 is not considered a valid option in this
                                                                          document (no free text UM with W/U response
                                                                          attribute).
                                      UM169 [freetext]                NIR-92             The ATN ground system shall
       UM199 [free text]
                                                                      convert ATN UM199 message into FANS1/A
                                                                      UM169 message element.
                                                                      NIR-93             The ATN ground system shall
                                                                      use the same character string in FANS1/A UM169
                                                                      as in ATN UM199.
                           Resp (N)                          Resp (R) NIR-94             The ATN ground system shall
                                                                      ignore the FANS1/A ROGER/STANDBY
                                                                      response when received as a response to an
                                                                      accommodated ATN UM199.

       UM200 REPORT                   None.                               NIR-95               The ATN ground system shall
                                                                          reject the sending of a UM200 message element.
       MAINTAINING.                                                                                                           Comment [PF69]:
                                                                          Note. Not viable. The use of FANS 1/A message       COMMENT #1281, PDR 10
                                                                          element UM169 to use the ATN message UM200
                                                                          is not considered a valid option in this document
                                                                          (message not automatically processed by avionics
                                                                          leading to aircrew workload).
                                                                                                          3-81


ATN Message Element              FANS 1/A Message Element     Interoperability Requirement
UM205 [free text]                UM169 [free text]            IR-80             The ATN ground system shall
                                                              convert the ATN message element UM205 into
                                                              the FANS 1/A message element UM169.
                    Resp (A/N)                       Resp (R) IR-81The ATN ground system shall process the
                                                              FANS ROGER response as a positive response to
                                                              the accommodated ATN message element
                                                              UM205.
                                                              Processing the pilot’s UNABLE response is a
                                                              local matter.
UM209R REACH [level single]      None.                        NIR-96               The ATN ground system shall
BEFORE PASSING [positionR]                                    reject the sending of a UM209R message element.
                                                              Note. Not viable. The use of FANS 1/A message
                                                              element UM169 to use the ATN message UM209R
                                                              is not considered a valid option in this document
                                                              (no free text UM with W/U response attribute).
UM211 REQUEST                    UM169 ‘REQUEST               IR-82              The ATN ground system shall
FORWARDED                        FORWARDED’                   convert the ATN UM211 message into FANS 1/A
                                                              UM169.
                      Resp (N)                       Resp (R) IR-83              When using FANS 1/A
                                                              UM169 to convert ATNUM211, the ATN ground
                                                              system shall ignore ROGER/STANDBY response
                                                              when received as answer to FANS 1/A UM169.
UM214R RVR [runway rvrR]         None.                        NIR-97               The ATN ground system shall
                                                              reject the sending of a UM151 message element.
                                                              Note. Not viable. The runwayRVR advanced            Comment [PF70]:
                                                              parameter is too complex to be translated into a    COMMENT #1248
                                                              free text.
UM215R TURN [direction side]     None.                        NIR-98               The ATN ground system shall
[number of degrees] DEGREES                                   reject the sending of a UM215R message element.
                                                              Note. Not viable.The use of FANS 1/A message
                                                              element UM169 to use the ATN message element
                                                              UM215R is not considered in this document as a
                                                              valid option (no free text UM with W/U response
                                                              attribute).
UM217 REPORT LANDING             None.                        NIR-99               The ATN ground system shall
                                                              reject the sending of a UM217 message element.
                                                              Note. Not viable. The response to ATN message
                                                              UM217 (DM102 LANDING REPORT) is not
                                                              available in FANS 1/A.
UM218 REQUEST ALREADY            UM169 ‘REQUEST         NIR-100          The ATN ground system shall
RECEIVED                         ALREADY RECEIVED’      convert the ATN UM218 message element into
                                                        FANS 1/A UM169 message element.
                      Resp (N)                 Resp (R) NIR-101          The ATN ground system shall              Comment [P71]:
                                                        ignore the FANS ROGER/STANDBY response to                 COMMENT #794
                                                        the accommodated ATN message UM218.
                                                                                                                  Comment [P72]:
UM222 NO SPEED                 UM169 ‘NO SPEED          IR-87            The ATN ground system shall              COMMENT #897
RESTRICTION                    RESTRICTION’             convert the ATN UM222 message element into
                                                        FANS 1/A UM169 message element.
3-82


       ATN Message Element          FANS 1/A Message Element    Interoperability Requirement
       UM223 REDUCE TO              None.                       NIR-102              The ATN ground system shall
       MINIMUM APPROACH                                         reject the sending of a UM233 message element.
       SPEED                                                    Note. Not viable. The use of FANS 1/A message
                                                                element UM169 to use the ATN message UM223
                                                                is not considered a valid option in this document
                                                                (no free text UM with W/U response attribute).
       UM224 NO DELAY               UM169 ‘NO DELAY             NIR-103              The ATN ground system shall
       EXPECTED                     EXPECTED’                   convert the ATN UM224 message element into
                                                                FANS 1/A UM169 message element.
       UM225 DELAY NOT              UM169 ‘DELAY NOT            NIR-104              The ATN ground system shall
       DETERMINED                   DETERMINED’                 convert the ATN UM225 message element into
                                                                FANS 1/A UM169 message element.
       UM226 EXPECT APPROACH        UM169 ‘EXPECT               NIR-105              The ATN ground system shall     Comment [PF73]:
       TIME [time]                  APPROACH TIME [time]’       convert the ATN UM226 message into FANS 1/A          PDR #263, #280 8/
                                                                UM169.
                                                                See paragraph 3.2.2.12.7 for use of time parameter
                                                                sent as a free text.
       UM227 LOGICAL                None                        See paragraph 3.2.2.5 for use of LACK.
       ACKNOWLEDGEMENT
       UM228R REPORT ETA            None.                       NIR-106              The ATN ground system shall
       [position ATW]                                           reject the sending of a UM228R message element.
                                                                Note. Not viable. The use of FANS 1/A message
                                                                element UM169 to use the ATN message UM228R
                                                                is not considered a valid option in this document.
                                                                The response message DM133 ETA                       Comment [PF74]:
                                                                [position][timesec] is not supported in FANS 1/A.    COMMENT #1238

       UM229 REPORT ALTERNATE None.                             NIR-107              The ATN ground system shall
       AERODROME                                                reject the sending of a UM229 message element.
                                                                Note. Not viable.The use of FANS 1/A message
                                                                element UM169 to use the ATN message UM229
                                                                is not considered a valid option in this document.
                                                                The response message DM105 ALTERNATE
                                                                AERODROME [airport] is not supported in FANS
                                                                1/A.
       UM230 IMMEDIATELY            UM 169 ‘IMMEDIATELY’        NIR-108          The ATN ground system shall
                                                                convert the ATN UM230 message element into
                                                                FANS 1/A UM169 message element only when
                                                                sent with a message element requiring a W/U
                                                                response.
       UM231 STATE PREFERRED        UM169 ‘STATE                IR-88            The ATN ground system shall
       LEVEL                        PREFERRED LEVEL’            convert the ATN message element UM231 into
                                                                the equivalent FANS 1/A message element
                                                                UM169.
                         Resp (Y)                     Resp (R) See paragraph 3.2.2.4 for processing differences
                                                               with message element attributes.
                                                               See paragraph 3.2.2.13.2 for processing message
                                                               elements with a “Y” response attribute.
                                                                                                        3-83


ATN Message Element             FANS 1/A Message Element    Interoperability Requirement
UM232 STATE TOP OF              UM169 ‘STATE TOP OF         IR-89           The ATN ground system shall
DESCENT                         DESCENT’                    convert the ATN message element UM232 into
                                                            FANS 1/A message element UM169.
                     Resp (Y)                     Resp (R) See paragraph 3.2.2.4 for processing differences
                                                           with message element attributes.
                                                           See paragraph 3.2.2.13.2 for processing message
                                                           elements with a “Y” response attribute.
UM233 USE OF LOGICAL            None                       IR-90               The ATN ground system shall
ACKNOWLEDGEMENT                                            prohibit the use of ATN UM233 USE OF LACK
PROHIBITED                                                 PROHIBITED for FANS 1/A aircraft.
                                                           See paragraph 3.2.2.5 on use of LACK.                Comment [PF75]:
                                                                                                                COMMENT #1291
UM234 FLIGHT PLAN NOT     UM169 ‘FLIGHT PLAN NOT NIR-109             The ATN ground system shall
HELD                      HELD’                     convert the ATN UM234 message element into
                                                    FANS 1/A UM169 message element.
                 Resp (N)                  Resp (R) NIR-110          The ATN ground system shall                Comment [P76]:
                                                    ignore the FANS ROGER/STANDBY response                      COMMENT #795 #897
                                                    to an accommodatedfor ATN message UM234                     Comment [P77]:
                                                    message element.                                            COMMENT #897
UM235 ROGER 7500          UM169 ‘ROGER 7500’        NIR-111          The ATN ground system shall
                                                    convert the ATN UM235 message element into
                                                    FANS 1/A UM169 message element.
                 Resp (N)                  Resp (R) NIR-112          The ATN ground system shall                Comment [P78]:
                                                    ignore the FANS ROGER /STANDBY response                     COMMENT #796 #897
                                                    to the accommodated ATN message element                     Comment [P79]:
                                                    UM235.                                                      COMMENT #897
UM236R LEAVE                    None.                       NIR-113              The ATN ground system shall
CONTROLLED AIRSPACE                                         reject the sending of a UM236R message element.
[leave instruction]                                         Note. Not viable. The use of FANS 1/A message
                                                            element UM169 to use the ATN message UM236
                                                            is not considered a valid option in this document
                                                            (no free text UM with W/U response attribute).
UM237 REQUEST AGAIN             UM169 ‘REQUEST AGAIN     IR-91               The ATN ground system shall
WITH NEXT UNIT                  WITH NEXT ATC UNIT’      convert the ATN message element UM237 into
                                                         the FANS 1/A message element UM169.
                  Resp (N)                      Resp (R) IR-92               The ATN ground system shall
                                                         ignore the FANS ROGER/STANDBY response                 Comment [P80]:
                                                         received as a response to the accommodated ATN         COMMENT #897
                                                         message element UM237.
UM238 SECONDARY            UM169 ‘SECONDARY              NIR-114             The ATN ground system shall
FREQUENCY [frequency]      FREQUENCY [xxx]’              convert the ATN UM238 message element into
                                                         FANS 1/A UM169 message element.
                           Where [xxx] = [frequency]
                                                         See paragraph 3.2.2.12.17 for the syntax of the
                                                         ATN frequency parameter sent as a free text
                                                         parameter.
UM239 STOP ADS-B           UM169 ‘STOP ADS-B             NIR-115             The ATN ground system shall
TRANSMISSION               TRANSMISSION’                 convert the ATN UM239 message element into
                                                         FANS 1/A UM169 message element.
                Resp (W/U)                      Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                         and R responses.
3-84


       ATN Message Element              FANS 1/A Message Element      Interoperability Requirement
       UM243 REPORT CLEAR OF            None.                         NIR-116              The ATN ground system shall
       WEATHER                                                        reject the sending of a UM243 message element.
                                                                      Note. Not viable. The use of FANS 1/A message
                                                                      element UM169 to use the ATN message UM243 is
                                                                      not considered a valid option in this document (no
                                                                      free text UM with W/U response attribute).
                                                                      In addition, the response message DM114 CLEAR
                                                                      OF WEATHER is not supported in FANS 1/A.
       UM245 EXPEDITE                   UM 169 ‘EXPEDITE’             NIR-117          The ATN ground system shall         Comment [PF81]:
                                                                      convert the ATN UM245 message element into           PDR #263, #267
                                                                      FANS 1/A UM169 message element only when
                                                                      sent with a message element requiring a W/U
                                                                      response.
       UM246 AT [level single]          None.                         NIR-118              The ATN ground system shall
       CLEARED TO DEVIATE UP                                          reject the sending of a UM246 message element.
       TO [lateral deviation] OF                                      Note. Not viable. The use of FANS 1/A message
       ROUTE                                                          element UM169 to use the ATN message UM246 is
                                                                      not considered a valid option in this document (no
                                                                      free text UM with W/U response attribute).
       UM247 WHEN ABLE                  UM169 ‘WHEN ABLE’             NIR-119         The ATN ground system shall          Comment [PF82]:
                                                                      convert the ATN UM247 message element into           PDR #263, #274, #277
                                                                      FANS 1/A UM169 message element.
                                                                      Note. See above when UM247 is concatenated
                                                                      with UM74R PROCEED DIRECT TO.
       UM261 REQUESTED LEVEL            UM169 ‘REQUESTED              NIR-120         The ATN ground system shall          Comment [PF83]:
       IS NOT AVAILABLE                 LEVEL IS NOT                  convert the ATN UM261 message element into           PDR #263, #293 1)
                                        AVAILABLE’                    FANS 1/A UM169 message element.

       UM262 HIGHER LEVEL IS            UM169 ‘HIGHER LEVEL IS        NIR-121         The ATN ground system shall          Comment [PF84]:
       NOT AVAILABLE                    NOT AVAILABLE’                convert the ATN UM262 message element into           PDR #293 2)
                                                                      FANS 1/A UM169 message element.
       UM263 LOWER LEVEL IS             UM169 ‘LOWER LEVEL IS         NIR-122         The ATN ground system shall          Comment [PF85]:
       NOT AVAILABLE                    NOT AVAILABLE’                convert the ATN UM263 message element into           PDR #263, #293 3)
                                                                      FANS 1/A UM169 message element.
       UM265R LEAVE [level single]      None.                         NIR-123              The ATN ground system shall     Comment [PF86]:
       AT OR BEFORE TIME [time]                                       reject the sending of a UM265R message element.      PDR #263, #293 4)
                                                                      Note. Not viable. The use of FANS 1/A message
                                                                      element UM169 to use the ATN message UM265R
                                                                      is not considered a valid option in this document
                                                                      (no free text UM with W/U response attribute).
       UM275 HAZARDEOUS                 None.                         NIR-124              The ATN ground system shall
       WEATHER [hzwx specification]                                   reject the sending of a UM275 message element.       Comment [PF87]:
                                                                      Note. D-HZWX is not provided to FANS.                PDR #293

                              Resp(R)                       Resp(R) See paragraph 3.2.2.4, for processing message
                                                                    attributes.
                                                                    The R response attribute is not the same in the
                                                                    ATS INTEROP Standard and the FANS 1/A
                                                                    INTEROP Standard.
                                                                    Processing the pilot’s UNABLE response is a
                                                                    local matter.
                                                                                                           3-85


ATN Message Element             FANS 1/A Message Element      Interoperability Requirement
UM284                                                         NIR-125            (delete).                         Comment [PF88]:
                                                                                                                   COMMENT #802
                                                                                                                   PDR #263, #293 5), #353
UM285 CURRENT ATC UNIT          UM169 ‘CURRENT ATC            NIR-126           The ATN ground system shall
[unit name]                     UNIT [unitId]’                convert the ATN UM285 message element into
                                                              FANS 1/A UM169 message element
                                Where
                                                              See paragraph 3.2.2.12.10 for the syntax of the
                                [unit     id]   = [facility   ATN unitId parameter sent as a free text
                                identification]   [facility   parameter.
                                function]


                     Resp (N)             Resp (R) NIR-127         The ATN ground system shall
                                                   ignore the FANS 1/A ROGER/STANDBY                               Comment [P89]:
                                                   response when received as a response to an                      COMMENT #897
                                                   accommodated ATNUM285.
                                                                                                                   Comment [P90]:
UM286 CPDLC BACK IN USE UM169 ‘CPDLC BACK IN       NIR-128         The ATN ground system shall                     COMMENT #804
                          USE’                     convert the ATN UM286 message element into
                                                   FANS 1/A UM169 message element
                 Resp (N)                 Resp (R) NIR-129         The ATN ground system shall
                                                   ignore the FANS 1/A ROGER/STANDBY                               Comment [P91]:
                                                   response when received as a response to an                      COMMENT #897
                                                   accommodated ATN UM286.
                                                                                                                   Comment [P92]:
UM287 CPDLC NOT IN USE    UM169 ‘CPDLC NOT IN USE NIR-130          The ATN ground system shall                     COMMENT #805
UNTIL FURTHER             UNTIL FURTHER            convert the ATN UM287 message element into
NOTIFICATION              NOTIFICATION’            FANS 1/A UM169 message element.

                     Resp (N)                   Resp (R) NIR-131            The ATN ground system shall
                                                         ignore the ROGER/STANDBY response when                    Comment [P93]:
                                                         received as a response to an accommodated ATN             COMMENT #897
                                                         UM287.
                                                                                                                   Comment [P94]:
UM288 VERIFY MONITORED UM169 ‘VERIFY                     NIR-132            The ATN ground system shall            COMMENT #806
FREQUENCY [frequency]      MONITORED FREQUENCY convert the ATN UM288 message element into
                           [xxx]’                        FANS 1/A UM169 message element.
                           Where [xxx] = [frequency]     See paragraph 3.2.2.12.17 for the syntax of the
                                                         ATN frequency parameter sent as a free text
                                                         parameter.
                Resp (A/N)                      Resp (R) See paragraph 3.2.2.15 for handling of the A/N
                                                         and R responses.
UM289 REST OF ROUTE        UM169 ‘REST OF ROUTE          NIR-133            The ATN ground system shall
UNCHANGED                  UNCHANGED’                    convert the ATN UM289 message element into
                                                         FANS 1/A UM169 message element.
UM290 DESCEND VIA [named None.                                NIR-134              The ATN ground system shall
instruction]                                                  reject the sending of a UM290 message element.       Comment [p95]:
                                                              Note. Not viable. The use of FANS 1/A message        PDR #83, #137
                                                              element UM169 to use the ATN message UM290 is
                                                              not considered a valid option in this document (no
                                                              free text UM with W/U response attribute).
3-86


       ATN Message Element           FANS 1/A Message Element    Interoperability Requirement
       UM292 AFTER PASSING           None.                       NIR-135              The ATN ground system shall
       [positionR] DESCEND VIA                                   reject the sending of a UM292 message element.
       [namedInstruction]                                        Note. Not viable. The use of FANS 1/A message        Comment [p96]:
                                                                 element UM169 to use the ATN message UM292 is        PDR #83, #137
                                                                 not considered a valid option in this document (no
                                                                 free text UM with W/U response attribute).
       UM293 CLIMB VIA               None.                       NIR-136              The ATN ground system shall
       [namedInstruction]                                        reject the sending of a UM293 message element.       Comment [p97]:
                                                                 Note. Not viable. The use of FANS 1/A message        PDR #83, #137
                                                                 element UM169 to use the ATN message UM293 is
                                                                 not considered a valid option in this document (no
                                                                 free text UM with W/U response attribute).
       UM294 WHICH LEVEL DO         UM169 ‘WHICH LEVEL DO        NIR-137            The ATN ground system shall
       YOU PREFER [level single] OR YOU PREFER [level] OR        convert the ATN message element UM294 into
       [level single]               [level]’                     the equivalent FANS 1/A message element
                                                                 UM169.
                                                                 See paragraph 3.2.2.12.1 for the syntax of the
                                                                 ATN level single parameter sent as a free text
                                                                 parameter.
       UM295 AFTER PASSING          None.                        NIR-138              The ATN ground system shall
       [positionR] CLIMB VIA [named                              reject the sending of a UM295 message element.
       instruction]                                              Note. Not viable. The use of FANS 1/A message        Comment [p98]:
                                                                 element UM169 to use the ATN message UM295 is        PDR #83, #137
                                                                 not considered a valid option in this document (no
                                                                 free text UM with W/U response attribute).
       UM296 MONITOR                 UM169 ‘MONITOR              NIR-139           The ATN ground system shall        Comment [PF99]:
       SECONDARY FREQUENCY           SECONDARY FREQUENCY         convert the ATN UM296 message element into           COMMENT #808
       [unit id][frequency]          [unit id][xxx]’             FANS 1/A UM169 message element.                      PDR #263, #270, #272

                                     Where [xxx] = [frequency]   See paragraph 3.2.2.12.17 for the syntax of the
                                                                 ATN frequency parameter sent as a free text
                                      [unit id] = [facility      parameter.
                                     identification] [facility   See paragraph 3.2.2.12.10 for the syntax of the
                                     function]                   ATN unitId parameter sent as a free text
                                                                 parameter.
       UM302 EXPECT [level           UM169 ‘EXPECT               NIR-140           The ATN ground system shall
       single][number of minutes]    [altitude][xxx] MINUTES     convert the ATN UM302 message into FANS 1/A
       AFTER DEPARTURE               AFTER DEPARTURE’            UM169.
                                     And [xxx] is [number of     See paragraph 3.2.2.12.1 for the syntax of the
                                     minutes] as nnn minutes.    ATN level single parameter sent as a free text
                                                                 parameter.
       UM303 CLEARED TO              None.                       NIR-141              The ATN ground system shall
       DEVIATE UP TO [number of                                  reject the sending of a UM303 message element.
       degrees] DEGREES [direction                               Note. Not viable. The use of FANS 1/A message
       side] OF ROUTE                                            element UM169 to use the ATN message UM303 is
                                                                 not considered a valid option in this document (no
                                                                 free text UM with W/U response attribute).
                                                                                                 3-87


ATN Message Element       FANS 1/A Message Element   Interoperability Requirement
UM306 MAINTAIN            None.                      NIR-142              The ATN ground system shall
MINIMUM CLEAN SPEED                                  reject the sending of a UM306 message element.
                                                     Note. Not viable. The use of FANS 1/A message
                                                     element UM169 to use the ATN message UM306
                                                     is not considered a valid option in this document
                                                     (no free text UM with W/U response attribute).
UM307 REPORT REQUIRED     None.                      NIR-143              The ATN ground system shall
RVR                                                  reject the sending of a UM307 message element.
                                                     Note. Not viable. The use of FANS 1/A message
                                                     element UM169 to use the ATN message UM307
                                                     is not considered a valid option in this document
                                                     (no free text DM pairing with Y response
                                                     attribute).
UM308 MAINTAIN            None.                      NIR-144              The ATN ground system shall    Comment [PF100]:
MAXIMUM SPEED                                        reject the sending of a UM308 message element.      PDR #280 14/
                                                     Note. Not viable. The use of FANS 1/A message
                                                     element UM169 to use the ATN message UM308
                                                     is not considered a valid option in this document
                                                     (no free text UM with W/U response attribute).
UM309 MAINTAIN            None.                      NIR-145              The ATN ground system shall
MINIMUM SPEED                                        reject the sending of a UM309 message element.
                                                     Note. Not viable. The use of FANS 1/A message
                                                     element UM169 to use the ATN message UM309
                                                     is not considered a valid option in this document
                                                     (no free text UM with W/U response attribute).
UM310 AT [level single]   None.                      NIR-146              The ATN ground system shall
MAINTAIN [speed]                                     reject the sending of a UM310 message element.
                                                     Note. Not viable. The use of FANS 1/A message
                                                     element UM169 to use the ATN message UM310
                                                     is not considered a valid option in this document
                                                     (no free text UM with W/U response attribute).

UM311 STARTUP APPROVED None.                         NIR-147              The ATN ground system shall
[assigned timeO]                                     reject the sending of a UM311 message element.
                                                     Note. D-TAXI is not provided to FANS aircraft.
UM312 CANCEL STARTUP      None.                      NIR-148              The ATN ground system shall
                                                     reject the sending of a UM312 message element.
                                                     Note. D-TAXI is not provided to FANS aircraft.
UM313 PUSH BACK           None.                      NIR-149              The ATN ground system shall
APPROVED                                             reject the sending of a UM313 message element.
[pushbackInformationO]                               Note. D-TAXI is not provided to FANS aircraft.
[assigned timeO]
3-88


       ATN Message Element            FANS 1/A Message Element         Interoperability Requirement
       UM314 EXPECT [clearance        UM73                             NIR-150            When the ATN message
       typeR][assigned time0]         [preDepartureClearance]:         UM314 is concatenated with the ATN message
                                      [timeDepartureEDCT]              UM73R and the parameter “clearance type”
                                                                       equals “departure” the ATN ground system shall
                                                                       convert the parameter “assigned time” to the
                                                                       FANS 1/A timeDepartureEDCT within the FANS
                                                                       1/A message element UM73.
                                                                       See paragraph 3.3.2.4.1 for use of the predeparture
                                                                       clearance parameter.
       UM315 EXPECT [taxi             None.                            NIR-151              The ATN ground system shall
       durationO] TAXI [taxi route]                                    reject the sending of a UM315 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM316R WHEN CAN YOU            None.                            NIR-152              The ATN ground system shall
       ACCEPT [clearance typeR]                                        reject the sending of a UM316 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM318 CROSS [ground            None.                            NIR-153              The ATN ground system shall
       location]                                                       reject the sending of a UM318 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM319 RUNWAY [runwayO]         None.                            NIR-154              The ATN ground system shall
       TAXI [taxi route]                                               reject the sending of a UM319 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM321 WHEN REACHING            None.                            NIR-155              The ATN ground system shall
       [ground location]                                               reject the sending of a UM321 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM322 HOLD POSITION            None.                            NIR-156              The ATN ground system shall
                                                                       reject the sending of a UM322 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM323 FOR DE ICING             None.                            NIR-157              The ATN ground system shall      Comment [PF101]:
                                                                       reject the sending of a UM323 message element.        PDR #280 15)
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM324 YOU ACCEPT               None.                            NIR-158              The ATN ground system shall      Comment [PF102]:
       INTERSECTION [intersection]                                     reject the sending of a UM324 message element.        PDR #296
       FOR RUNWAY [runway]                                             Note. D-TAXI is not provided to FANS aircraft.
       UM325 REVISED [revision        UM169 ‘REVISED [nnnn             NIR-159              The ATN ground system shall      Comment [PF103]:
       reasonO]                       reason]’ where nnnn is the       convert the ATN UM325 message into FANS 1/A           PDR #292
                                      textual format of the revision   UM169.
                                      reason when revision reason is   See paragraph 3.3.2.4.2 for use of UM325 in
                                      present                          DCL.

       UM326 DEPARTURES               None.                            NIR-160              The ATN ground system shall
       STOPPED                                                         reject the sending of a UM326 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM327 ENGINE SHUTDOWN          None.                            NIR-161              The ATN ground system shall
       PERMITTED                                                       reject the sending of a UM327 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
       UM328 [distance ground]        None.                            NIR-162              The ATN ground system shall
       AVAILABLE                                                       reject the sending of a UM328 message element.
                                                                       Note. D-TAXI is not provided to FANS aircraft.
                                                                                                             3-89


ATN Message Element            FANS 1/A Message Element         Interoperability Requirement
UM329 INTERSECTION             None.                            NIR-163              The ATN ground system shall
DEPARTURE [intersection]                                        reject the sending of a UM329 message element.
                                                                Note. D-TAXI is not provided to FANS aircraft.
UM333 HOLD SHORT [ground       None.                            NIR-164              The ATN ground system shall
location]                                                       reject the sending of a UM333 message element.
                                                                Note. D-TAXI is not provided to FANS aircraft.
UM334 IN THE CLIMB             UM169 ‘IN THE CLIMB’ +           NIR-165            The ATN ground system shall
MAINTAIN [speed schedule]      UM106 MAINTAIN [speed] +         convert the ATN message UM334 to the FANS
                               UM106 MAINTAIN [speed]           1/A free text message UM 169 concatenated with
                                                                a sequence of two FANS 1/A UM106 messages.
                                                                See paragraph 3.2.2.12.31 for the use of the speed
                                                                schedule parameter.
UM335 IN THE DESCENT           UM169 ‘IN THE DESCENT’           NIR-166            The ATN ground system shall
MAINTAIN [speed schedule]      + UM106 MAINTAIN [speed]         convert the ATN message UM335 to the FANS
                               + UM106 MAINTAIN [speed]         1/A free text message UM 169 concatenated with
                                                                a sequence of two FANS 1/A UM106 messages.
                                                                See paragraph 3.2.2.12.31 for the use of the speed
                                                                schedule parameter.
UM336 CANCEL TIME              None.                            NIR-167              The ATN ground system shall
CONSTRAINT FOR [position                                        reject the sending of a UM336 message element.
ATW]                                                            Note. Not viable. The use of FANS 1/A message
                                                                element UM169 to use the ATN message UM336
                                                                is not considered a valid option in this document
                                                                (no free text UM with W/U response attribute).
UM339 AT [position ATW]        None.                            NIR-168              The ATN ground system shall
CLEARED TO [positionR] VIA                                      reject the sending of a UM339 message element.
[route clearanceR]                                              Note. Not viable. The use of FANS 1/A message
                                                                element UM169 to use the ATN message UM339
                                                                is not considered a valid option in this document
                                                                (no free text UM with W/U response attribute).
UM340 LATENCY TIME             UM169 ‘SET MAX UPLINK            NIR-169             The ATN ground system shall
VALUE [value latency]          DELAY VALUE TO [xxx]             convert the ATN message UM340 to the FANS
                               SEC’                             1/A free text message UM 169.
                               Where [xxx] is [value latency]   NIR-170             The ATN ground system shall
                               as nnn seconds                   convert the ATN UM340 [value latency]
                                                                parameter to a charater string.

                    Resp (N)                         Resp (R) NIR-171            The ATN ground system shall
                                                              ignore the ROGER/STANDBY response when                 Comment [P104]:
                                                              received as a response to an accommodated ATN          COMMENT #897
                                                              UM340.
                                                                                                                     Comment [P105]:
                                                                                                                     COMMENT #806
3-90


       ATN Message Element              FANS 1/A Message Element         Interoperability Requirement
       UM341 ITP [aircraft reference    UM169 ‘ITP [aircraft reference NIR-172                 The ATN ground system shall     Comment [PF106]:
       list]                            list]’                             convert the ATN UM341 message into FANS 1/A         PDR 252
                                                                           UM169.
                                                                           NIR-173             When sending ATN UM341,
                                        With [aircraft reference list] as the ATN ground system shall include the
                                        one of the following:              parameters in the free text parameter of FANS 1/A
                                        “BEHIND [aircraft flight           UM169 as a string of characters.
                                        identification]”, “AHEAD OF
                                        [aircraft flight identification]”,
                                        “BEHIND [aircraft flight
                                        identification] AND BEHIND
                                        [aircraft flight identification]”,
                                        “AHEAD OF [aircraft flight
                                        identification] AND AHEAD
                                        OF [aircraft flight
                                        identification]” or “BEHIND
                                        [aircraft flight identification]
                                        AND AHEAD OF [aircraft
                                        flight identification]”
                             Resp (N)                    Resp (R) NIR-174              The ATN ground system shall
                                                                  ignore the ROGER/STANDBY response when                       Comment [P107]:
                                                                  received as a response to an accommodated ATN                COMMENT #897
                                                                  UM341.
                                                                                                                               Comment [P108]:
       UM345 REQUEST AGAIN         UM169 ‘REQUEST AGAIN           NIR-175              The ATN ground system shall             COMMENT #806
       AFTER PASSING [positionR]   AFTER PASSING [xxx]’           convert the ATN UM345 message element into
                                                                  the FANS 1/A UM169.                                          Comment [PF109]:
                                   Where [xxx] is a Published                                                                  PDR #293
                                   Identifier Name.               See paragraph 3.2.2.12.2 for the syntax of the
                                                                  ATN positionR parameter sent as a free text
                                                                  parameter.
                          Resp (N)                       Resp (R) NIR-176              The ATN ground system shall
                                                                  ignore the ROGER/STANDBY response when                       Comment [P110]:
                                                                  received as a response to an accommodated ATN                COMMENT #897
                                                                  UM345.
                                                                                                                               Comment [P111]:
       UM346 REQUEST AGAIN         UM169 ‘REQUEST AGAIN           NIR-177              The ATN ground system shall             COMMENT #806
       AFTER TIME [time]           AFTER TIME [time]’             convert the ATN UM246 message into FANS 1/A
                                                                  UM169.                                                       Comment [PF112]:
                                                                                                                               PDR #293
                                                                  See paragraph 3.2.2.12.7 for use of time parameter
                                                                  sent as a free text.

                             Resp (N)                         Resp (R) NIR-178            The ATN ground system shall
                                                                       ignore the ROGER/STANDBY response when                  Comment [P113]:
                                                                       received as a response to an accommodated ATN           COMMENT #897
                                                                       UM346.
                                                                                                                               Comment [P114]:
       UM347 REQUEST AGAIN              UM169 ‘REQUEST AGAIN             NIR-179            The ATN ground system shall        COMMENT #806
       AFTER REACHING [level            AFTER REACHING [level]’          convert the ATN message element UM347 into
                                                                                                                               Comment [PF115]:
       single]                                                           the equivalent FANS 1/A message element               PDR #293
                                                                         UM169.
                                                                         See paragraph 3.2.2.12.1for the syntax of the ATN
                                                                         level single parameter sent as a free text
                                                                         parameter.
                                                                                                             3-91


ATN Message Element             FANS 1/A Message Element        Interoperability Requirement
                     Resp (N)                          Resp (R) NIR-180            The ATN ground system shall
                                                                ignore the ROGER/STANDBY response when               Comment [P116]:
                                                                received as a response to an accommodated ATN        COMMENT #897
                                                                UM347.
                                                                                                                     Comment [P117]:
UM348 WHEN WILL YOU             None.                           NIR-181              The ATN ground system shall     COMMENT #806
MAINTAIN [level single]                                         reject the sending of a UM348 message element.       Comment [PF118]:
                                                                Note. Not viable. The use of FANS 1/A message        PDR #351
                                                                element UM169 to use the ATN message UM307
                                                                is not considered a valid option in this document
                                                                (no free text DM pairing with Y response
                                                                attribute).
UM349 REPORT SIGHTING           UM169 ‘REPORT SIGHTING          NIR-182              The ATN ground system shall
AND PASSING OPPOSITE            AND PASSING OPPOSITE            convert the ATN UM349 message into FANS 1/A
DIRECTION [aircraft type        DIRECTION [xxx] ETP             UM169.
traffic location] [etptime]     [time]’                         See paragraph 3.2.2.12.7 for use of time parameter   Comment [PF119]:
                                                                sent as a free text.                                 PDR #263, #299
                                Where [xxx] is the traffic
                                                                NIR-183             When sending ATN UM349,
                                description expressed as an
                                                                the ATN ground system shall include the traffic
                                aircraft type and/or a level
                                                                type and location and the time of passing
                                indicator.
                                                                parameters in the free text parameter of FANS 1/A
                                Example of the traffic          UM169 as a string of characters.
                                description:
                                B747 ABOVE                      NIR-184             After sending the converted
                                                                ATN message element UM349, the ATN ground
                                                                system shall technically close the dialogue upon
                                                                receipt of a FANS 1/A message element DM3.

                                                   NIR-185            After sending the converted
                                                   ATN message element UM349, the ATN ground
                                                   system shall process a FANS 1/A message
                                                   element DM67 containing ‘[traffic identification]
                                                   SIGHTED AND PASSED’ or                   ‘[traffic
                                                   identification] NOT SIGHTED’, as the response
                                                   to the ATN message element UM349.
                 Resp (N)               Resp (W/U) See paragraph 3.2.2.14 for handling of the W/U
                                                   and R responses.
UM351 RESPOND TO OPEN     UM169 ‘CHECK AND         NIR-186            The ATN ground system shall
CPDLC MESSAGES            RESPOND TO OPEN CPDLC convert the ATN UM351 message into FANS 1/A
                          MESSAGES’                UM169.

                     Resp (N)                          Resp (R) NIR-187            The ATN ground system shall
                                                                ignore the ROGER/STANDBY response when               Comment [P120]:
                                                                received as a response to an accommodated ATN        COMMENT #897
                                                                UM351.
                                                                                                                     Comment [P121]:
                                                                NIR-188            (deleted).                        COMMENT #806

UM353 EXPECT CPDLC              UM169 ‘EXPECT CPDLC             NIR-189              The ATN ground system shall
TRANSFER AT TIME [time]         TRANSFER AT [time]’             convert the ATN UM353 message into FANS 1/A          Comment [PF122]:
                                                                UM169.                                               PDR #263
                                                                See paragraph 3.2.2.12.7 for use of time parameter
                                                                sent as a free text.
3-92


       ATN Message Element                 FANS 1/A Message Element           Interoperability Requirement
       UM354 CPDLC WITH [Unit              UM169 ‘CPDLC WITH [Unit            NIR-190             The ATN ground system shall       Comment [PF123]:
       Id] NOT REQUIRED EXPECT             Id] NOT AVAILABLE                  convert the ATN UM354 message into FANS 1/A           PDR #280 13)
       NEXT CPDLC FACILITY [Unit           EXPECT NEXT CPDLC                  UM169.
       Id]                                 FACILITY [unit Id]’                NIR-191             When sending ATN UM354,
                                           [unit id] = [facility              the ATN ground system shall include the unit Id
                                           identification] [facility          parameters in the free text parameter of FANS 1/A
                                           function]                          UM169 as a string of characters.

       UM355 TRAFFIC IS [traffic           UM169 ‘TRAFFIC IS [xxx]’           NIR-192            The ATN ground system shall
       description]                                                           convert the ATN UM355 message into FANS 1/A
                                           [xxx] is the traffic description
                                                                              UM169.
                                           expressed as an
                                           aicraftflightidentification, an    NIR-193            When sending ATN UM355,
                                           aircrafttype and/or a level.       the ATN ground system shall include the traffic
                                                                              description parameter in the free text parameter of
                                           Example of the traffic             FANS 1/A UM169 as a string of characters.
                                           description:
                                           SIA228 B747 FL370
                                                                              NIR-194             (deleted)
                                                                              NIR-195             (deleted).

                                                                              NIR-196             (deleted).
       UM359 CONFIRM ADS-C                 UM169 ’CONFIRM ADS-C               NIR-197         The ATN ground system shall
       EMERGENCY                           EMERGENCY’                         convert the ATN UM359 message element into
                                                                              FANS 1/A UM169 message element.

                              Resp (A/N)                   Resp (R) See paragraph 3.2.2.15 for handling of the A/N
                                                                    and R responses.
       UM360 ACTIVATE ADS-C                UM169 ‘ACTIVATE ADS-C’ NIR-198             The ATN ground system shall
                                                                    convert the ATN UM360 message element into
                                                                    FANS 1/A UM169 message element.

                             Resp (W/U)         Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                         and R responses.
       UM361 ADS-C OUT OF      UM169 ‘ADS-C OUT OF       NIR-199           The ATN ground system shall
       SERVICE REVERT TO CPDLC SERVICE REVERT TO         convert the ATN UM361 message element into
       POSITION REPORTS        CPDLC POSITION            FANS 1/A UM169 message element.
                               REPORTS’
                             Resp (W/U)         Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                         and R responses.
       UM362 ADS-C OUT OF      UM169 ‘ADS-C OUT OF       NIR-200           The ATN ground system shall
       SERVICE REVERT TO VOICE SERVICE REVERT TO         convert the ATN UM362 message element into
       POSITION REPORTS        VOICE POSITION            FANS 1/A UM169 message element.
                               REPORTS’


                             Resp (W/U)                             Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                                             and R responses.
       UM363 RELAY TO [aircraft            UM169 ‘RELAY TO [aircraft NIR-201                   The ATN ground system shall
       flight identification] [unitId]     flight identification] [unitId]   convert the ATN UM363 message element into
       [relay text][frequency O]           [relayedText][frequency]’         FANS 1/A UM169 message element.
                                                                                                          3-93


ATN Message Element                 FANS 1/A Message Element   Interoperability Requirement
                       Resp (W/U)                     Resp (R) See paragraph 3.2.2.14 for handling of the W/U
                                                               and R responses.
UM364 SELECT TRAFFIC                None.                      NIR-202              The ATN ground system shall
[aircraft flight identification]                               reject the sending of a UM364 message element.
                                                               Note. FIM is not provided to FANS aircraft.
UM365 REPORT SELECTED               None.                      NIR-203              The ATN ground system shall
TRAFFIC                                                        reject the sending of a UM365 message element.
                                                               Note. FIM is not provided to FANS aircraft.
UM366 MAINTAIN CURRENT None.                                   NIR-204              The ATN ground system shall
DISTANCE SPACING                                               reject the sending of a UM366 message element.
BEHIND [aircraft flight                                        Note. FIM is not provided to FANS aircraft.
identification]
UM367 MAINTAIN CURRENT None.                                   NIR-205              The ATN ground system shall
TIME SPACING BEHIND                                            reject the sending of a UM367 message element.
[aircraft flight identification]                               Note. FIM is not provided to FANS aircraft.
UM368          FOR      INTERVAL None.                         NIR-206              The ATN ground system shall
SPACING CROSS [position                                        reject the sending of a UM368 message element.
ATW]         [spacing]     BEHIND
[aircraft flight identification]                               Note. FIM is not provided to FANS aircraft.
[routing] TERMINATE AT
[position ATW]
UM369 EXPECT INTERVAL None.                                    NIR-207              The ATN ground system shall
SPACING TO CROSS [position                                     reject the sending of a UM369 message element.
ATW] BEHIND [aircraft flight
identification]             [routing]                          Note. FIM is not provided to FANS aircraft.
TERMINATE AT [position
ATW] ASSIGNED SPACING
INTERVAL PENDING
UM370 WHEN ABLE                     None.                      NIR-208              The ATN ground system shall
INTERCEPT AT [position                                         reject the sending of a UM370 message element.
ATW]                                                           Note. FIM is not provided to FANS aircraft.
UM371 REPORT STARTING               None.                      NIR-209              The ATN ground system shall
SPACING                                                        reject the sending of a UM371 message element.
                                                               Note. FIM is not provided to FANS aircraft.
UM372 REPORT PLANNED                None.                      NIR-210              The ATN ground system shall
FINAL APPROACH SPEED                                           reject the sending of a UM372 message element.
                                                               Note. FIM is not provided to FANS aircraft.
UM373 CONTINUE SPACING              None.                      NIR-211              The ATN ground system shall
BEHIND [aircraft flight                                        reject the sending of a UM373 message element.
identification]                                                Note. FIM is not provided to FANS aircraft.
UM374 REPORT ASSIGNED               None.                      NIR-212              The ATN ground system shall
SPACING INTERVAL                                               reject the sending of a UM374 message element.
BEHIND [aircraft flight                                        Note. FIM is not provided to FANS aircraft.
identification]
UM375 REPORT CURRENT                None.                      NIR-213              The ATN ground system shall
SPACING INTERVAL                                               reject the sending of a UM375 message element.
BEHIND [aircraft flight                                        Note. FIM is not provided to FANS aircraft.
identification]
3-94


       ATN Message Element       FANS 1/A Message Element   Interoperability Requirement
       UM376 CANCEL SPACING      None.                      NIR-214              The ATN ground system shall
       BEHIND [aircraft flight                              reject the sending of a UM377 message element.
       identificationO]                                     Note. FIM is not provided to FANS aircraft.
3.2.2.9           Downlink Message Elements
                  The interoperability requirements for processing FANS 1/A downlink message elements
                  supporting AMC, IER, CRD, ITP, OCL, DCL and ACM are provided in paragraph
                  3.2.2.9.1. Guidance for processing FANS 1/A downlink emergency message elements is
                  provided in paragraph 3.2.2.9.2.
                  The ATN ground system may receive downlink message elements from FANS 1/A
                  aircraft that are not supported.
                  IR-242           When the ATN ground system receives any message element or any
                  message element parameter/data type that it does not support, the ATN ground system
                  shall reject the message and respond per paragraph 3.2.2.11.
3.2.2.9.1         CPDLC Downlink Message Elements
                  Table 3-19Table 3-19Table 3-19 lists the ATN downlink message elements supporting              Formatted: Cross-Reference
                  ACM, CRD, IER, DCL and AMC, the corresponding FANS 1/A downlink message                        Formatted: Cross-Reference
                  elements, and related interoperability requirements.


                           Table 3-19 ATN and FANS 1/A CPDLC downlink message elements
          FANS 1/A Message Element     ATN Message Element   Interoperability Requirement
          DM0 WILCO                    DM0 WILCO             None.
          DM1 UNABLE                   DM1 UNABLE            None.
          DM2 STANDBY                  DM2 STANDBY           None.
          DM3 ROGER                    DM3 ROGER             None.
          DM4 AFFIRM                   DM4 AFFIRM            None.                                               Comment [PF124]:
                                                                                                                 PDR #280 21)
          DM5 NEGATIVE                 DM5 NEGATIVE          None.
          DM6 REQUEST [altitude]       DM9 REQUEST           IR-XXX             The ATN ground system shall      Comment [PF125]:
                                       CLIMB [level]         convert the FANS 1/A message element DM6 into       PDR #347 4)
                                       Or                    the ATN DM9 or DM10 message when it can select
                                                             the correct message or reject it by sending UM169   Comment [PF126]:
                                                             ‘MESSAGE NOT SUPPORTED BY THIS ATC                  PDR #357
                                       DM10 REQUEST          UNIT’.
                                       DESCENT[level]        See paragraph 3.2.2.12.1 for use of altitude
                                                             parameter.
                                       Or

                                       None
          DM7 REQUEST BLOCK [altitude] DM9 REQUEST           IR-95              The ATN ground system shall
          TO [altitude]                CLIMB BLOCK [level]   convert the FANS 1/A message element DM7 into
                                       TO [level]            the ATN DM9 or DM10 message when it can select
                                       Or
                                                             the correct message or reject it by sending UM169   Comment [PF127]:
                                                             ‘MESSAGE NOT SUPPORTED BY THIS ATC                  PDR #357
                                                             UNIT’.
                                       DM10 REQUEST          See paragraph 3.2.2.12.1 for use of altitude
                                       DESCENT BLOCK         parameter.
                                       [level] TO [level]
                                       Or
FANS 1/A Message Element     ATN Message Element    Interoperability Requirement


                             None
DM8 REQUEST CRUISE CLIMB     None.                  NIR-215           The ATN Ground system shall
TO [altitude]                                       reject the FANS 1/A message DM8 by sending the
                                                    FANS UM169 ‘MESSAGE NOT SUPPORTED BY                 Comment [PF128]:
                                                    THIS ATC UNIT’.                                      PDR #357
                                                    Note. DM8 does not exist in ATN.                     Comment [PF129]:
                                                                                                         PDR #273
DM9 REQUEST CLIMB TO         DM9 REQUEST            NIR-216            (deleted).
[altitude]                   CLIMB [level]          See paragraph 3.2.2.12.1 for use of altitude         Comment [PF130]:
                                                                                                         PDR #345
                                                    parameter.
                                                    See paragraph 3.2.2.13.1 for processing message
                                                    elements with a “Y” response attribute.


DM10 REQUEST DESCENT TO      DM10 REQUEST           NIR-217            (deleted)                         Comment [PF131]:
[altitude]                   DESCENT[level]                                                              PDR #345
                                                    See paragraph 3.2.2.12.1 for use of altitude
                                                    parameter.
                                                    See paragraph 3.2.2.13.1 for processing message
                                                    elements with a “Y” response attribute.


DM11 AT [position] REQUEST   DM11R AT [positionR]   NIR-218             The ATN ground system shall      Comment [PF132]:
CLIMB TO [altitude]          REQUEST [level]        reject the FANS 1/A message element DM11             PDR #280 8), #335
                                                    containing a fixname, a navaid or an airport
                                                    parameter by sending UM169 ‘MESSAGE NOT              Comment [PF133]:
                                                    SUPPORTED BY THIS ATC UNIT’.                         PDR #357
                                                    Note: A FANS fixname, navaid or airport cannot be
                                                    translated into an ATN published identifierR.
                                                    NIR-219             The ATN ground system shall
                                                    convert the FANS 1/A message DM11 containing a
                                                    latlong or a placebearing parameter to ATN message
                                                    DM11R.
                                                    See paragraph 3.2.2.12.3 for use of position
                                                    parameter.
                                                    See paragraph 3.2.2.12.1 for use of altitude
                                                    parameter.
DM12 AT [position] REQUEST   DM11R AT [positionR]   NIR-220             The ATN ground system shall      Comment [PF134]:
DESCENT TO [altitude]        REQUEST [level]        reject the FANS 1/A message element DM12             PDR #280 8), #279 19), #335
                                                    containing a fixname, a navaid or an airport
                                                    parameter by sending UM169 ‘MESSAGE NOT              Comment [PF135]:
                                                    SUPPORTED BY THIS ATC UNIT’.                         PDR #357
                                                    Note: A FANS fixname, navaid or airport cannot be
                                                    translated into an ATN published identifierR.
                                                    NIR-221             The ATN ground system shall
                                                    convert the FANS 1/A message DM12 containing a
                                                    latlong or a placebearing parameter to ATN message
                                                    DM11R.
                                                    See paragraph 3.2.2.12.1 for use of altitude
                                                    parameter.
                                                    See paragraph 3.2.2.12.3 for use of positionR
                                                                                                              3-97



FANS 1/A Message Element          ATN Message Element        Interoperability Requirement
                                                             parameter.
                                                             Note: ATN message DM12 is replaced by ATN
                                                             message DM11R.
DM13 AT [time] REQUEST            DM13 AT TIME [time]        None.                                                   Comment [PF136]:
CLIMB TO [altitude]               REQUEST [level]                                                                    PDR #263, #280 8)
                                                             See paragraph 3.2.2.12.1 for use of altitude
                                                             parameter.
DM14 AT [time] REQUEST            DM13 AT TIME [time]        NIR-222            The ATN ground system shall          Comment [PF137]:
DESCENT TO [altitude]             REQUEST [level]            convert the FANS 1/A message DM14 to ATN                PDR #263, #280 8), #279 19)
                                                             message DM13.
                                                             See paragraph 3.2.2.12.1 for use of altitude
                                                             parameter.
                                                             Note: ATN message DM14 is replaced by ATN
                                                             message DM13.
DM15 REQUEST OFFSET               DM15 REQUEST               None.
[distanceoffset] [direction] OF   OFFSET [specified          See paragraph 3.2.2.12.5 for use of distance offset
ROUTE                             distance] [direction] OF   parameter.
                                  ROUTE
                                                             See paragraph 3.2.2.12.6 for use of direction
                                                             parameter.
DM16 AT [position] REQUEST        None.                      NIR-223            The ATN Ground system shall
OFFSET [distanceoffset]                                      reject the FANS 1/A message DM16 by sending
[direction] OF ROUTE                                         UM169 ‘MESSAGE NOT SUPPORTED BY THIS                    Comment [PF138]:
                                                             ATC UNIT’.                                              PDR #357
                                                             Note. DM16 does not exist in ATN.                       Comment [PF139]:
                                                                                                                     PDR #279 23)
DM17 AT [time] REQUEST            None.                      NIR-224            The ATN Ground system shall
OFFSET [distanceoffset]                                      reject the FANS 1/A message DM17 by sending
[direction] OF ROUTE                                         UM169 ‘MESSAGE NOT SUPPORTED BY THIS                    Comment [PF140]:
                                                             ATC UNIT’.                                              PDR #357
                                                             Note. DM17 does not exist in ATN                        Comment [PF141]:
                                                                                                                     PDR #263, PDR #279 23)
DM18 REQUEST [speed]              DM18 REQUEST               See paragraph 3.2.2.12.4 for use of speed parameter.
                                  [speed]                    See paragraph 3.2.2.13.1 for processing message
                                                             elements with a “Y” response attribute.
DM19 REQUEST [speed] TO           None.                      NIR-225          The ATN Ground system shall
[speed]                                                      reject the FANS 1/A message DM19 by sending
                                                             UM169 ‘MESSAGE NOT SUPPORTED BY THIS                    Comment [PF142]:
                                                             ATC UNIT’.                                              PDR #357
                                                             Note. DM19 does not exist in ATN.                       Comment [PF143]:
                                                                                                                     PDR #279 22)
DM20 REQUEST VOICE                DM21R REQUEST              NIR-J-IR 21                 The ATN ground
CONTACT                           VOICE CONTACT                  system shall convert the FANS 1/A message           Comment [PF144]:
                                  [frequencyO.NULL]              DM20 to ATN message DM21R using the                 PDR #346
                                                                 NULL frequency value..


DM21 REQUEST VOICE                DM21R REQUEST              None.
CONTACT [frequency]               VOICE CONTACT              See paragraph 3.2.2.12.17 for use of frequency
                                  [frequencyO.frequency]     parameter.
DM22 REQUEST DIRECT TO            DM22R REQUEST              NIR-J-IR 22                  The ATN ground
[position]                        DIRECT TO [positionR]          system shall reject the FANS 1/A message            Comment [PF145]:
                                                                                                                     PDR #335
FANS 1/A Message Element          ATN Message Element      Interoperability Requirement
                                                               element DM22 containing a fixname, a navaid
                                                               or an airport parameter by sending the FANS
                                                               UM169 ‘MESSAGE NOT SUPPORTED BY                    Comment [PF146]:
                                                               THIS ATC UNIT’.                                    PDR #357
                                                           Note: A FANS fixname, navaid or airport cannot be
                                                           translated into an ATN published identifier R.
                                                           NIR-226             The ATN ground system shall
                                                           convert the FANS 1/A message DM22 containing a
                                                           latlong or a placebearing parameter to an ATN
                                                           message DM22R.
                                                           See paragraph 3.2.2.12.3 for use of positionR
                                                           parameter.
                                                           See paragraph 3.2.2.13.1 for processing message
                                                           elements with a “Y” response attribute.
DM23 REQUEST [procedure           DM23R REQUEST            NIR-227            The ATN ground system shall         Comment [PF147]:
name]                             [namedInstruction]       convert the FANS 1/A message DM23 to ATN               COMMENT #1285
                                                           message DM23R.
                                                           See paragraph 3.2.2.12.20 for use of the procedure
                                                           name parameter.
DM24 REQUEST [route clearance] DM24R REQUEST               NIR-228            The ATN ground system shall         Comment [PF148]:
                               CLEARANCE [route            convert the FANS 1/A message DM24 to ATN               COMMENT #1286
                               clearanceR]                 message DM24R.
                                                           See paragraph 3.2.2.12.12 for use of route clearance
                                                           parameter.
DM25 REQUEST CLEARANCE            DM25R REQUEST            NIR-229            The ATN ground system shall set
                                  [clearance typeO]        the ATN [clearance typeO] parameter in DM25 to
                                  CLEARANCE                none when accommodating a FANS 1/A aircraft
                                                           sending DM25.
                                                           Note1: No [clearance type] parameter in FANS 1/A.
                                                           Note2. Use of DM25 in the context of departure
                                                           clearance is addressed in section XX.
DM26 REQUEST WEATHER              None.                    NIR-J-IR 23                 The ATN ground
DEVIATION TO [position] VIA                                    system shall reject the FANS 1/A message           Comment [PF149]:
[route clearance]                                              element DM26 by sending the FANS UM169             PDR #335, #347
                                                               ‘MESSAGE NOT SUPPORTED BY THIS ATC
                                                                                                                  Comment [PF150]:
                                                               UNIT’.                                             PDR #357

                                                           NIR-230            (deleted)
DM27 REQUEST WEATHER              DM27R REQUEST            NIR-231            The ATN ground system shall
DEVIATION UP TO                   WEATHER                  convert the FANS 1/A message DM27 to ATN
[distanceoffset] [direction] OF   DEVIATION UP TO          message DM27R.
ROUTE                             [lateral deviation] OF   See paragraph 3.2.2.12.5 for use of distance offset
                                  ROUTE                    parameter.
                                                           See paragraph 3.2.2.12.6 for use of direction
                                                           parameter.
                                                           See paragraph 3.2.2.13.1 for processing message
                                                           elements with a “Y” response attribute.
                                                                                                 3-99



FANS 1/A Message Element      ATN Message Element    Interoperability Requirement
DM28 LEAVING [altitude]       DM28R LEAVING          NIR-232            The ATN ground system shall
                              [level single]         convert the FANS 1/A message DM28 to ATN
                                                     message DM28R.
                                                     See paragraph 3.2.2.12.1 for use of altitude
                                                     parameter.
DM29 CLIMBING TO [altitude]   DM29R CLIMBING TO NIR-233            The ATN ground system shall
                              [level single]    convert the FANS 1/A message DM29 to ATN
                                                message DM29R.
                                                See paragraph 3.2.2.12.1 for use of altitude
                                                parameter.
DM30 DESCENDING TO            DM30R DESCENDING       NIR-234            The ATN ground system shall
[altitude]                    TO [level single]      convert the FANS 1/A message DM30 to ATN
                                                     message DM30R.
                                                     See paragraph 3.2.2.12.1 for use of altitude
                                                     parameter.
DM31 PASSING [position]       DM31R PASSING          NIR-J-IR 24                  The ATN ground
                              [positionR]                system shall reject the FANS 1/A message        Comment [PF151]:
                                                         element DM31 containing a fixname, a navaid     PDR #335
                                                         or an airport parameter by sending the FANS
                                                         UM169 ‘MESSAGE NOT SUPPORTED BY                 Comment [PF152]:
                                                         THIS ATC UNIT’.                                 PDR #357
                                                     Note: A FANS fixname, navaid or airport cannot be
                                                     translated into an ATN published identifier R.

                                                     NIR-235            The ATN ground system shall
                                                     convert the FANS 1/A message DM31 containing a
                                                     latlong or a placebearing parameter to an ATN
                                                     message DM31R.
                                                     See paragraph 3.2.2.12.3 for use of position
                                                     parameter.
DM32 PRESENT ALTITUDE         DM32R PRESENT          NIR-236             The ATN ground system shall
[altitude]                    LEVEL [level single]   convert the FANS 1/A message DM32 to ATN
                                                     message DM32R.
                                                     See paragraph 3.2.2.12.1 for use of altitude
                                                     parameter.
                                                     See paragraph 3.2.2.13.2 for use of this message
                                                     element as a response to a message element with a
                                                     “Y” response attribute.
DM33 PRESENT POSITION         DM33R PRESENT          NIR-J-IR 25                  The ATN ground
[position]                    POSITION [positionR]       system shall reject the FANS 1/A message        Comment [PF153]:
                                                         element DM33 containing a fixname, a navaid     PDR #335
                                                         or an airport parameter by sending the FANS
                                                         UM169 ‘MESSAGE NOT SUPPORTED BY                 Comment [PF154]:
                                                         THIS ATC UNIT’.                                 PDR #357
                                                     Note: A FANS fixname, navaid or airport cannot be
                                                     translated into an ATN published identifier R.

                                                     NIR-237           The ATN ground system shall
                                                     convert the FANS 1/A message DM33 containing a
                                                     latlong or a placebearing parameter to an ATN
FANS 1/A Message Element     ATN Message Element    Interoperability Requirement
                                                    message DM33R.
                                                    See paragraph 3.2.2.12.3 for use of position
                                                    parameter.
DM34 PRESENT SPEED [speed]   None.                  NIR-238            The ATN Ground system
                                                    shall reject the FANS 1/A message DM34 by
                                                    sending the FANS UM169 ‘MESSAGE NOT                    Comment [PF155]:
                                                    SUPPORTED BY THIS ATC UNIT’.                           PDR #357
                                                    Note. ATN DM34 does not exist.
DM35 PRESENT HEADING         None.                  NIR-239           The ATN Ground system shall
[degrees]                                           reject the FANS 1/A message DM35 by sending the
                                                    FANS UM169 ‘MESSAGE NOT SUPPORTED BY                   Comment [PF156]:
                                                    THIS ATC UNIT’.                                        PDR #357
                                                    Note. ATN DM35 does not exist.
DM36 PRESENT GROUND          DM36 PRESENT           None.
TRACK [degrees]              GROUND TRACK           See paragraph 3.2.2.12.11 for use of degrees
                             [degrees] DEGREES      parameter.
DM37 LEVEL [altitude]        DM37R                  NIR-240            The ATN ground system shall
                             MAINTAINING [level     convert the FANS 1/A message DM37 to ATN
                             single]                message DM37R.
                                                    See paragraph 3.2.2.12.1 for use of altitude
                                                    parameter.
DM38 ASSIGNED ALTITUDE       DM38 ASSIGNED          None.                                                  Comment [PF157]:
[altitude]                   LEVEL [level]                                                                 COMMENT #1287
                                                    See paragraph 3.2.2.12.1 for use of altitude
                                                    parameter.
                                                    See paragraph 3.2.2.13.2 for use of this message
                                                    element as a response to a message element with a
                                                    “Y” response attribute.
DM39 ASSIGNED SPEED [speed] DM39 ASSIGNED           None.
                            SPEED [speed]           See paragraph 3.2.2.12.4 for use of speed parameter.
DM40 ASSIGNED ROUTE [route   DM40R ASSIGNED         NIR-241            The ATN ground system shall         Comment [PF158]:
clearance]                   ROUTE [route           convert the FANS 1/A message DM40 to ATN               COMMENT #1230
                             clearanceR]            message DM40R.
                                                    See paragraph 3.2.2.12.12 for use of route clearance
                                                    parameter.
DM41 BACK ON ROUTE           DM41 BACK ON           None.
                             ROUTE
DM42 NEXT WAYPOINT           DM42R NEXT           NIR-J-IR 26                  The ATN ground
[position]                   WAYPOINT [positionR]     system shall reject the FANS 1/A message             Comment [PF159]:
                                                      element DM42 containing a fixname, a navaid          PDR #335
                                                      or an airport parameter by sending the FANS
                                                      UM169 ‘MESSAGE NOT SUPPORTED BY                      Comment [PF160]:
                                                      THIS ATC UNIT’.                                      PDR #357
                                                    Note: A FANS fixname, navaid or airport cannot be
                                                    translated into an ATN published identifier R.

                                                    NIR-242          The ATN ground system shall
                                                    convert the FANS 1/A message DM42 containing a
                                                                                               3-101



FANS 1/A Message Element   ATN Message Element   Interoperability Requirement
                                                 latlong or a placebearing parameter to an ATN
                                                 message DM42R.
                                                 See paragraph 3.2.2.12.3 for use of position
                                                 parameter.
DM43 NEXT WAYPOINT ETA      DM43R NEXT           IR-251             The ATN ground system shall
[time]                     WAYPOINT ETA          convert the FANS 1/A message DM43 to ATN
                           [timesec]             message DM43R.
                                                 See paragraph 3.2.2.12.7 for use of the time/timesec
                                                 parameter.
DM44 ENSUING WAYPOINT      DM44R NEXT PLUS       NIR-J-IR 27                  The ATN ground
[position]                 ONE WAYPOINT              system shall reject the FANS 1/A message             Comment [PF161]:
                           [positionR]               element DM44 containing a fixname, a navaid          PDR #335
                                                     or an airport parameter by sending the FANS
                                                     UM169 ‘MESSAGE NOT SUPPORTED BY                      Comment [PF162]:
                                                     THIS ATC UNIT’.                                      PDR #357
                                                 Note: A FANS fixname, navaid or airport cannot be
                                                 translated into an ATN published identifier R.

                                                 IR-251              The ATN ground system shall
                                                 convert the FANS 1/A message DM44 DM22
                                                 containing a latlong or a placebearing parameter to an
                                                 ATN message DM44R.
                                                 See paragraph 3.2.2.12.3 for use of position
                                                 parameter.
DM45 REPORTED WAYPOINT     None.                 NIR-243           The ATN Ground system shall
[position]                                       reject the FANS 1/A message DM45 by sending the
                                                 FANS UM169 ‘MESSAGE NOT SUPPORTED BY                     Comment [PF163]:
                                                 THIS ATC UNIT’.                                          PDR #357
                                                 Note. ATN DM45 does not exist.
DM46 REPORTED WAYPOINT     None.                 NIR-244            The ATN Ground system shall
[time]                                           reject the FANS 1/A message DM46 by sending the
                                                 FANS UM169 ‘MESSAGE NOT SUPPORTED BY                     Comment [PF164]:
                                                 THIS ATC UNIT’.                                          PDR #357
                                                 Note. ATN DM46 does not exist.
DM47 SQUAWKING             DM47 SQUAWKING        None.
[beaconcode]               [code]
DM48 POSITION REPORT       DM48R POSITION                                                                 Comment [PF165]:
                                                 NIR-J-IR 28                  The ATN ground
[position report]          REPORT [position                                                               COMMENT #1244
                                                     system shall reject the FANS 1/A message
                           reportR]                  element DM48 containing a fixname, a navaid          Comment [PF166]:
                                                     or an airport parameter by sending the FANS
                                                     UM169 ‘MESSAGE NOT SUPPORTED BY                      Comment [PF167]:
                                                     THIS ATC UNIT’.                                      PDR #357
                                                 Note: A FANS fixname, navaid or airport cannot be
                                                 translated into an ATN published identifier R.

                                                 NIR-245            The ATN ground system shall
                                                 convert the FANS 1/A message DM48 containing a
                                                 latlong or a placebearing parameter to an ATN
                                                 message DM48R.
                                                 See paragraph 3.2.2.12.24 for use of position report
FANS 1/A Message Element     ATN Message Element   Interoperability Requirement
                                                   parameter.
DM49 WHEN CAN WE EXPECT      DM49 WHEN CAN WE      None.
[speed]                      EXPECT [speed]        See paragraph 3.2.2.12.4 for use of speed parameter.
DM50 WHEN CAN WE EXPECT      None.                 NIR-246           The ATN Ground system shall
[speed] TO [speed]                                 reject the FANS 1/A message DM50 by sending the
                                                   FANS UM169 ‘MESSAGE NOT SUPPORTED BY                   Comment [PF168]:
                                                   THIS ATC UNIT’.                                        PDR #357
                                                   Note. ATN DM50 does not exist.                         Comment [PF169]:
                                                                                                          PDR #279 20)
DM51 WHEN CAN WE EXPECT      DM51 WHEN CAN WE      None.
BACK ON ROUTE                EXPECT BACK ON
                             ROUTE
DM52 WHEN CAN WE EXPECT      DM52 WHEN CAN WE      None.
LOWER LEVEL                  EXPECT LOWER
                             LEVEL
DM53 WHEN CAN WE EXPECT      DM53 WHEN CAN WE      None.
HIGHER LEVEL                 EXPECT HIGHER
                             LEVEL
DM54 WHEN CAN WE EXPECT      None.                 NIR-247           The ATN Ground system shall
CRUISE CLIMB TO [altitude]                         reject the FANS 1/A message DM54 by sending the
                                                   FANS UM169 ‘MESSAGE NOT SUPPORTED BY                   Comment [PF170]:
                                                   THIS ATC UNIT’.                                        PDR #357
                                                   Note. ATN DM54 does not exist.                         Comment [PF171]:
                                                                                                          PDR #273
                                                                                                            3-103



FANS 1/A Message Element              ATN Message Element    Interoperability Requirement
DM55 PAN PAN PAN                      DM55 PAN PAN PAN       None.
                            Resp(N)                 Resp(Y) See paragraph 3.2.2.9.2 for handling emergency
                                                            messages.
DM56 MAYDAY MAYDAY                    DM56 MAYDAY            None.
MAYDAY                                MAYDAY MAYDAY
                            Resp(N)                 Resp(Y) See paragraph 3.2.2.9.2 for handling emergency
                                                            messages.
DM57 [remaining fuel] OF FUEL         DM57[remaining fuel]   None.                                                  Comment [PF172]:
REMAINING AND [remaining              ENDURANCE AND                                                                 COMMENT #1245, PDR #263
                                                             See paragraph 3.2.2.12.25 for use of remaining fuel
souls] SOULS ON BOARD                 [personnes on board]   parameter.
                                      PERSONS ON BOARD
                                                             See paragraph 3.2.2.12.26 for use of remaining souls
                                                             parameter.
                            Resp(N)                 Resp(Y) See paragraph 3.2.2.9.2 for handling emergency
                                                            messages.
DM58 CANCEL EMERGENCY                 DM58 CANCEL            None.
                                      EMERGENCY
                            Resp(N)                 Resp(Y) See paragraph 3.2.2.9.2 for handling emergency
                                                            messages.

DM59 DIVERTING TO [position]          DM59R DIVERTING                                                               Comment [PF173]:
                                                             NIR-J-IR 29                  The ATN ground
VIA [routeclearance]                  TO [positionR] VIA                                                            COMMENT #1247
                                                                 system shall reject the FANS 1/A message           PDR #335
                                      [route clearanceR]         element DM22 containing a fixname, a navaid
                                                                 or an airport parameter by sending the FANS
                                                                 UM169 ‘MESSAGE NOT SUPPORTED BY                    Comment [PF174]:
                                                                 THIS ATC UNIT’.                                    PDR #357
                                                             Note: A FANS fixname, navaid or airport cannot be
                                                             translated into an ATN published identifier R.

                                                             NIR-248            The ATN ground system shall
                                                             convert the FANS 1/A message DM59 containing a
                                                             latlong or a placebearing parameter to an ATN
                                                             message DM59R.
                                                             See paragraph 3.2.2.12.3 for use of position
                                                             parameter.
                                                             See paragraph 3.2.2.12.12 for use of route clearance
                                                             parameter.
DM60 OFFSETTING                       DM60 OFFSETTING        None.
[distanceoffset] [direction] OF       [specified distance]   See paragraph 3.2.2.12.5 for use of distance offset
ROUTE                                 [direction] OF ROUTE   parameter.
                                                             See paragraph 3.2.2.12.6 for use of direction
                                                             parameter.
DM61 DESCENDING TO                    DM30R DESCENDING       NIR-249            The ATN ground system shall         Comment [PF175]:
[altitude]                            TO [level single]      convert the FANS 1/A message DM61 to ATN               PDR #279 31)
                                                             message DM30R.
                                                             See paragraph 3.2.2.12.1 for use of altitude
                                                             parameter.
DM62 ERROR [error information]        DM62 ERROR [error      None.
FANS 1/A Message Element      ATN Message Element   Interoperability Requirement
                              information]          See paragraph 3.2.2.11.3 for use of error information
                                                    parameter.
DM63 NOT CURRENT DATA         DM63 NOT CURRENT      None.
AUTHORITY                     DATA AUTHORITY
DM64 [facility designation]   DM107 NOT             NIR-250            The ATN ground system shall
                              AUTHORIZED NEXT       convert the FANS 1/A message DM64 to ATN
                              DATA AUTHORITY        message DM107.
                                                    See paragraph 3.2.2.2 for use of FANS 1/A message
                                                    element DM64 with ATN message element DM107.
DM65 DUE TO WEATHER           DM65R66R DUE TO       NIR-251             The ATN Ground system shall         Comment [PF176]:
                              [duetoreason]         convert the FANS 1/A message DM65 to ATN                PDR #294
                                                    message DM65R66R DUE TO [duetoReason] with
                                                    duetoreason set to “weather (0)”.
DM66 DUE TO AIRCRAFT          DM65R66R DUE TO       NIR-252             The ATN Ground system shall         Comment [PF177]:
PERFORMANCE                   [duetoreason]         convert the FANS 1/A message DM66 to ATN                PDR #294
                                                    message DM65R66R DUE TO [duetoReason] with
                                                    duetoreason set to “aircraftPerformance (1)”.
DM67 [free text]              DM98 [free text]      NIR-253           The ATN ground system shall           Comment [PF178]:
                                                    convert the FANS 1/A message DM67 to ATN                PDR #251
                                                    message DM98.
DM68 [free text]              None.                 NIR-254            The ATN Ground system shall
                                                    reject the FANS 1/A message DM68 by sending the
                                                    FANS UM169 ‘MESSAGE NOT SUPPORTED BY                    Comment [PF179]:
                                                    THIS ATC UNIT’.                                         PDR #357
                                                    Note. ATN DM68 does not exist.                          Comment [PF180]:
                                                                                                            PDR #279 34)
DM69 REQUEST VMC              None.                 NIR-255            The ATN Ground system shall
DESCENT                                             reject the FANS 1/A message DM69 by sending the         Comment [PF181]:
                                                                                                            PDR #279 25)
                                                    FANS UM169 ‘MESSAGE NOT SUPPORTED BY
                                                    THIS ATC UNIT’.                                         Comment [PF182]:
                                                    Note. ATN DM69 does not exist.                          PDR #357

DM70 REQUEST HEADING          DM70 REQUEST          None.
[degrees]                     HEADING [degrees]     See paragraph 3.2.2.12.11 for use of degrees
                                                    parameter.
DM71 REQUEST GROUND           DM71 REQUEST          None.
TRACK [degrees]               GROUND TRACK          See paragraph 3.2.2.12.11 for use of degrees
                              [degrees] DEGREES     parameter.
DM72 REACHING ALTITUDE        None.                 NIR-256            The ATN Ground system shall
[altitude]                                          reject the FANS 1/A message DM72.
                                                    Note. ATN DM72 is reserved
DM73 [versionnumber]          None.                 NIR-257             Except when sent during the
                                                    connection establishment (see IR-27), the ATN           Comment [PF183]:
                                                    Ground system shall reject the FANS 1/A message         COMMENT #1288, PDR 257
                                                    DM73.
                                                    Note. ATN DM73 does not exist.
DM74 MAINTAIN OWN             None.                 NIR-258            The ATN Ground system shall          Comment [PF184]:
SEPARATION AND VMC                                  reject the FANS 1/A message DM74 by sending the         PDR #279 25)
                                                                                             3-105



FANS 1/A Message Element    ATN Message Element    Interoperability Requirement
                                                   FANS UM169 ‘MESSAGE NOT SUPPORTED BY                Comment [PF185]:
                                                   THIS ATC UNIT’.                                     PDR #357
                                                   Note. ATN DM74 does not exist.
DM75 AT PILOTS DISCRETION   None.                                                                      Comment [PF186]:
                                                   NIR-J-IR 30                  The ATN ground
                                                                                                       PDR #347
                                                       system shall reject the FANS 1/A message
                                                       element DM75 containing a fixname, a navaid
                                                       or an airport parameter by sending the FANS
                                                       UM169 ‘MESSAGE NOT SUPPORTED BY                 Comment [PF187]:
                                                       THIS ATC UNIT’.                                 PDR #357

DM76 REACHING BLOCK         DM76R REACHING         NIR-259            The ATN ground system shall
[altitude]TO [altitude]     BLOCK [level] TO       convert the FANS 1/A message DM76 to the ATN
                            [level]                message DM76R.
                                                   See paragraph 3.2.2.12.1 for use of altitude
                                                   parameter.
DM77 ASSIGNED BLOCK         DM38 ASSIGNED          NIR-260              The ATN ground system shall
[altitude]TO [altitude]     LEVEL BLOCK [level]    convert the FANS 1/A message DM77 to the ATN
                            to [level]             message DM38 ASSIGNED LEVEL BLOCK [level]
                                                   to [level] using the BLOCK parameter for level.
                                                   See paragraph 3.2.2.12.1 for use of altitude
                                                   parameter.
                                                   Note: ATN message DM77 is replaced by ATN
                                                   message DM38.
DM78 AT [time] [distance]   DM78R [distance] [to                                                       Comment [PF188]:
                                                   NIR-J-IR 31                  The ATN ground
[tofrom][position]          from] [positionR]                                                          PDR #1305, #269, #335
                                                       system shall reject the FANS 1/A message
                                                       element DM78 containing a fixname, a navaid
                                                       or an airport parameter by sending the FANS
                                                       UM169 ‘MESSAGE NOT SUPPORTED BY                 Comment [PF189]:
                                                       THIS ATC UNIT’.                                 PDR #357
                                                   Note: A FANS fixname, navaid or airport cannot be
                                                   translated into an ATN published identifier R.

                                                   NIR-261           The ATN ground system shall
                                                   convert the FANS 1/A message DM78 containing a
                                                   latlong or a placebearing parameter to an ATN
                                                   message DM78R.

                                                   NIR-262            When converting FANS 1/A
                                                   message DM78 to ATN message DM78R, the ATN
                                                   ground system shall ignore the FANS 1/A [time]
                                                   message parameter.
                                                   See paragraph 3.2.2.12.3 for use of position
                                                   parameter.
                                                   See paragraph 3.2.2.12.5 for use of distance
                                                   parameter.
DM79 ATIS [atis code]       None                   NIR-263            The ATN Ground system shall
                                                   reject the FANS 1/A message DM79 by sending the
                                                   FANS UM169 ‘MESSAGE NOT SUPPORTED BY                Comment [PF190]:
                                                   THIS ATC UNIT’.                                     PDR #357
                                                   Note. ATN DM79 does not exist.
FANS 1/A Message Element              ATN Message Element       Interoperability Requirement
DM80 DEVIATING                        DM80 DEVIATING UP None.                                                            Comment [PF191]:
[distanceoffset][direction] OF        TO [specified distance] See paragraph 3.2.2.12.5 for use of distance offset        PDR #279 34)
ROUTE                                 [direction] OF ROUTE    parameter.
                                                              See paragraph 3.2.2.12.6 for use of direction
                                                              parameter.
                           Resp (N)                   Resp(Y)
DM67 ’WE CAN ACCEPT                                             IR-97                When the received free text         Comment [PF193]:
[altitude] AT [time or waypoint]’                               message is translated into a predefined message, the     PDR #269
                                      DM98
                                                                ATN ground system shall process the FANS 1/A
                                                                message element DM67 message element as follows:
                                      Or                        • when [freetext] parameter containing at least “WE
                                                                CANNOT ACCEPT”, convert it to ATN DM82R
                                                                message element containing the previously uplinked
                                      DM81R WE CAN                                                                       Comment [PF192]:
                                      ACCEPT [level single]     level in UM148R message;                                 COMMENT #1223, PDR 257 6), #PDR #263
Or                                    AT TIME [time]            • when [freetext] parameter containing “WE CAN
                                                                ACCEPT<altitude>” and the last four or five
                                                                characters do not represent a time value (four digits
DM67 ‘WE CANNOT ACCEPT                Or                        or four digits plus ´Z´ character), convert it to ATN
[altitude]’                           DM115 WE CAN              DM81R message element containing the time
                                      ACCEPT [level single]     corresponding to the downlinked freetext;
                                      AT [positionR]            . when [freetext] parameter containing “WE CAN
Note: These are preformatted free
text messages, per the FANS 1/A       Or                        ACCEPT<altitude>” and the last four or five
INTEROP Standard.                                               characters represent a time value (four digits or four
                                                                digits plus ´Z´ character), convert it to ATN DM115
                                      DM82R WE CANNOT
                                                                message element containing the waypoint
                                      ACCEPT [level single]
                                                                corresponding to the downlinked fixname;
                                                                • when [freetext] parameter equal to “WE CAN
                                                                ACCEPT <altitude> BY NOW,” convert it to ATN
                                                                DM81 message element, inserting the current time in
                                                                [time] field;
                                                                The processing of this free text message for use by
                                                                the ATN ground system and the controller is a local
                                                                matter. Any safety assessment associated with the
                                                                implementation of this free text functionality should
                                                                take into account the unreferenced nature of the
                                                                downlink free text reply, the potential for non-
                                                                standard message contents, the effects of intended
                                                                and unintended manipulation of the free text message
                                                                by the automation prior to use by the controller or
                                                                other functionality of the ATN ground system.
                                                                See paragraph 3.2.2.9 and 0 for further processing
                                                                and rejection response.
                                                                See paragraph 3.2.2.12.1 for use of level/altitude.
                                                                See paragraph 3.2.2.13.2 for use of this message
                                                                element as a response to a message element with a
                                                                “Y” response attribute.
DM67 ‘MONITORING [unit                DM89 Not Used
name] [frequency]’                                              NIR-264           The ATN ground system shall
                                                                discard the DM67 ‘MONITORING’ message                    Comment [PF194]:
Where                                                                                                                    COMMENT #1289, PDR 257
[unit name] = [facility
                                                                                                              3-107



FANS 1/A Message Element                  ATN Message Element    Interoperability Requirement
identification] [facility function]
[facility identification] = 4-
character ICAO code
[facility function] = any of the
ICAOfacilityfunction values of
CENTER, APPROACH, etc. per
the ATS INTEROP Standard
[frequency] = a VHF frequency as
nnn.nnn or an HF frequency as
nnnnn

Note: It is anticipated that
airborne automation (i.e.,
preformatted message rather than
the pilot typing the text) may be
necessary for message composition
and to ensure accuracy of the
message content. Consequently, it
is likely that not all aircraft will be
equipped with such automation.
DM67 [free text]                          DM98 [freetext]        IR-99                When the [freetext] parameter of   Comment [P195]:
                                                                 the DM67 FANS 1/A message element cannot be             COMMENT #779
                                                                 converted in ASN.1, the ATN ground system shall
                                                                 convert the FANS 1/A message element DM67 into
                                                                 the ATN message element DM98 and display the
                                                                 message to the controller.
                                                                 The processing of this free text message for use by
                                                                 the ATN ground system and the controller is a local
                                                                 matter. Any safety assessment associated with the
                                                                 implementation of this free text functionality should
                                                                 take into account the unreferenced nature of the
                                                                 downlink free text reply, the potential for non-
                                                                 standard message contents, the effects of intended
                                                                 and unintended manipulation of the free text message
                                                                 by the automation prior to use by the controller or
                                                                 other functionality of the ATN ground system.
                                                                 DM67 used as equivalent means to provide responses
                                                                 to UM148R, UM231, UM232
                                                                 See this table for use of DM67 as equivalent of
                                                                 DM106, DM134, DM81, DM82, DM89
                                                                 See paragraph 3.2.2.9 for rejection response.
                                                                 See paragraph 3.2.2.11 for use of DM67 with DM62.
DM67 ‘FL[level]’                          DM98                   IR-100              When the received free text         Comment [PF196]:
                                                                 message is translated into a predefined message, the    PDR #269
                                          Or
                                                                 ATN ground system shall convert the equivalent
Where                                     DM106R PREFERRED                                                               Comment [PF197]:
                                                                 FANS 1/A message element DM67 into the ATN              PDR #269, #251
[level] = character string (2 or 3        LEVEL [level single]   message element DM106 and display it in the form
characters) that represents an                                   used for an ATN message element DM106R.
integer from 30 to 600.                                          The content of DM67 as sent by the flight crew is
                                                                 aligned with established use in oceanic operations to
                                                                 obtain operational seamlessness.
                                                                 The processing of this free text message for use by
FANS 1/A Message Element           ATN Message Element   Interoperability Requirement
                                                         the ATN ground system and the controller is a local
                                                         matter. Any safety assessment associated with the
                                                         implementation of this free text functionality should
                                                         take into account the unreferenced nature of the
                                                         downlink free text reply, the potential for non-
                                                         standard message contents, the effects of intended
                                                         and unintended manipulation of the free text message
                                                         by the automation prior to use by the controller or
                                                         other functionality of the ATN ground system.
                                                         The displayed reply in this case (i.e. aligned with
                                                         DM106R) is different from what the flight crew
                                                         actually sent, but the intent/use of the message is the
                                                         same.
                                                         See paragraph 3.2.2.9 and 0 for further processing
                                                         and rejection response.
                                                         See paragraph 3.2.2.13.2 for use of this message
                                                         element as a response to a message element with a
                                                         “Y” response attribute.
DM64 [facility designation]        DM107 NOT             See paragraph 3.2.2.2 for use of FANS 1/A message
                                   AUTHORIZED NEXT       element DM64 with ATN message element DM107.
                                   DATA AUTHORITY
DM67 ‘TOD [time]’                  DM98                  IR-101               When the received free text          Comment [PF198]:
                                                         message is translated into a predefined message, the      PDR #251
                                                         ATN ground system shall convert the equivalent
Where                              Or                                                                              Comment [PF200]:
                                                         FANS 1/A message element DM67 into ATN                    PDR #269
[time] = [hh][mm][z]                                     message element DM109R110R111R and display it
                                                         in the form used for an ATN message element
[hh] = 2-character string that     DM109R110R111R                                                                  Comment [PF199]:
represents an integer between 00   TOP OF DESCENT        DM109R110R111R.                                           COMMENT #1239
and 23;                            TIME [timesec]        TOP OF DESCENT is abbreviated in the DM67 free            PDR #283
[mm] = 2-characters string that    [positionR]           text message to ease the burden of message
represents an integer between 00                         composition for the flight crew.
and 59; and                                              The processing of this free text message for use by
[z] = an optional character, Z.                          the ATN ground system and the controller is a local
                                                         matter. Any safety assessment associated with the
                                                         implementation of this free text functionality should
                                                         take into account the unreferenced nature of the
                                                         downlink free text reply, the potential for non-
                                                         standard message contents, the effects of intended
                                                         and unintended manipulation of the free text message
                                                         by the automation prior to use by the controller or
                                                         other functionality of the ATN ground system.
                                                         The displayed reply in this case (i.e. aligned with
                                                         DM109R110R111R) is different from what the flight
                                                         crew actually sent, but the intent/use of the message
                                                         is the same.
                                                         See paragraph 3.2.2.9 and 0 for further processing
                                                         and rejection response.
                                                         See paragraph 3.2.2.13.2 for use of this message
                                                         element as a response to a message element with a
                                                         “Y” response attribute.
                                                                                                              3-109



FANS 1/A Message Element              ATN Message Element        Interoperability Requirement
DM67 ‘ITP                             DM67                       NIR-265             When the received free text        Comment [PF201]:
[aircraftReferenceListDistance]’                                 message is translated into a predefined message, the   PDR #269
                                                                 ATN ground system shall convert the equivalent
                                      Or                         FANS 1/A message element DM67 into ATN
Where                                                            message element DM161 and display it in the form
[aircraftReferenceListDistance] is:   DM161 ITP [aircraft        used for an ATN message element DM161.
“[Distance] BEHIND [aircraft          reference distance list]
flight identification]”
OR
“[Distance] AHEAD OF [aircraft
flight identification]”
OR
“[Distance] BEHIND[aircraft flight
identification] AND [Distance]
BEHIND [aircraft flight
identification]”
OR
“[Distance] AHEAD OF [aircraft
flight identification] AND
[Distance] AHEAD OF [aircraft
flight identification]”
OR
“[Distance] BEHIND [aircraft
flight identification] AND
[Distance] AHEAD OF [aircraft
flight identification]”
3.2.2.9.2   Aircraft emergency data communication capability
            The Standard for Advanced ATS Data Communications includes provisions for the
            processing CPDLC emergency messages that the ground system may receive from the
            aircraft.
            Error! Reference source not found.Erreur ! Source du renvoi introuvable. lists the
            FANS 1/A emergency message elements.
            NIR-266        When the ATN ground system receives a message that contains any of
            the message elements DM57 [remaining fuel] OF FUEL REMAINING AND [souls on
            board] SOULS ON BOARD or DM58 CANCEL EMERGENCY, ATN ground system
            shall:
                a) Display the the message to the controller,
                b) Allow the controller to acknowledge receipt of the message by sending UM3
                   ROGER to the FANS 1/A aircraft.
            Note 1: The response attribute is “N” for FANS 1/A CPDLC emergency message
                    elements. The response attribute is “Y” for ICAO Doc 4444 emergency
                    message elements.
            Note 2: DM112 is not included in the FANS 1/A CPDLC message set.
            Note 3: While DM59, DM60, DM61, DM80 are included in the FANS 1/A CPDLC
                    message set, they are not processed as emergency message elements by ATN
                    ground system.


            NIR-267    When the ATN ground system receives the emergency message element         Comment [PF202]:
            DM55 PAN PAN PAN, the ATN ground system shall:                                       PDR #319

                a) Display the the message to the controller,
                b) Convert the controller’s acknowledgement message (ATN UM3 ROGER) to the
                   FANS 1/A message UM169 “ROGER PAN”.


            NIR-268   When the ATN ground system receives the emergency message element          Comment [PF203]:
            DM56 MAYDAY MAYDAY MAYDAY, the ATN ground system shall:                              PDR #319

                a) Display the the message to the controller,
                b) Convert the controller’s acknowledgement message (ATN UM3 ROGER) to the
                   FANS 1/A message UM169 “ROGER MAYDAY”.
                                                                                                                     3-111



3.2.2.10             Concatenating Messages Elements
3.2.2.10.1           High-Level Requirements
                     Table 3-20Table 3-20Table 3-20 presents the ATN and comparable FANS 1/A CPDLC                           Formatted: Underline
                     high-level requirements for concatenation of message elements.                                          Formatted: Underline



                                         Table 3-20 High Level Concatenation Requirements                                    Comment [PF204]:
                                                                                                                             Replace the table by a generic statement about
           Table ATN Concatenation rule               FANS 1/A             Interoperability Requirement                      FANS a/c accepting all combination of messages –
                                                                                                                             no specific interop requirement on the ground.
                                                      Concatenation rule
           CPC-OR-71 The NEXT DATA                    No equivalent.       Any message element concatenated with
           AUTHORITY [facility designationO]                               UM160 will be accepted by the FANS 1/A
           message element (uplink message                                 aircraft.
           element 160) shall be sent only as a                            See paragraph 3.2.2.8 for use of UM160.
           single message element CPDLC
           message.
           CPC-IR 33 When the CPDLC Aircraft          No equivalent.
           System receives a concatenated uplink
           CPDLC message that contains a
           UM160 NEXT DATA AUTHORITY,
           it shall discard the received CPDLC
           message and send a CPDLC downlink
           message containing the concatenation
           of message element DM62 (ERROR
           (error information)) with the choice (0)
           followed by message element DM98                                                                                  Comment [FP205]:
           NEXT DATA AUTHORITY                                                                                               Air Error #13 (OSD Table 5-10)
           PROHIBITED IN COMBINATION)
           CPC-OR-73 UM72 (RESUME OWN               No equivalent.         Any message element concatenated with
           NAVIGATION) shall not be sent                                   UM72 will be accepted by the FANS 1/A
           without concatenating it with one of the                        aircraft.
           following message elements: UM74R,                              See paragraph 3.2.2.8 for use of UM72,
           UM79R, or UM80R denoting the                                    UM74R, UM79R, and UM80R.
           position to be navigated to.
           CPC-IR 28 When the CPLC Aircraft         No equivalent.         Any message element concatenated with
           System rejects a CPDLC message                                  UM72 will be accepted by the FANS 1/A
           containing message element UM72                                 aircraft.
           RESUME OWN NAVIGATION                                           See paragraph 3.2.2.9 for use of DM62
           because it does not also contain one of                         and DM98.
           the following message elements:
           UM74R, UM79R, or UM80R it shall                                 See paragraph 3.2.2.11.3.1 for use of
           send a CPDLC downlink message                                   Downlink [error information] Parameter.
           containing the concatenation of
           message element DM62 (ERROR
           (error information)) with the choice (2)
           followed by message element DM98
           (MESSAGE DOES NOT CONTAIN
           THE POSITION TO BE NAVIGATED
           TO).
3-112

               Table ATN Concatenation rule              FANS 1/A               Interoperability Requirement
                                                         Concatenation rule
        CPC-IR 31 When the CPDLC Aircraft          No equivalent.        Any of a message element concatenated                        Comment [PF206]:
        System receives a concatenated uplink                            with UM325 will be accepted by the                           PDR #313
        CPDLC message that with a prohibited                             FANS 1/A aircraft.
        element order (e.g. UM325 at the end),                           See paragraph 3.2.2.8 for use of UM325.
        it shall discard the received CPDLC
        message and send a CPDLC downlink
        message containing the concatenation
        of message element DM62 (ERROR
        (error information)) with the choice (3)
        followed by message element DM98
        (ELEMENT ORDER PROHIBITED).



3.2.2.10.2        Responding to Concatenated Messages
                  Table 3-21Table 3-21Table 3-21 presents the ATN and comparable FANS 1/A CPDLC                                       Formatted: Cross-Reference
                  requirements for responses to concatenated messages.                                                                Formatted: Cross-Reference



                      Table 3-21 ATN and FANS 1/A CPDLC responses to concatenated messages
        ATN concatenation rule               FANS 1/A Concatenation    Interoperability Requirement
                                             rule
        CPC-IR 105 When responding           No equivalent.            IR-102               When receiving a single element DM0
        positively to a received                                       or DM1 as a response to the concatenated uplink message
        concatenated uplink message                                    containing message elements VCI and other UM, the
        containing message elements                                    ATN               ground             system           shall:
        VCI and other messages                                          accept the DM0 or DM1 single element message as
        requiring a response, the aircraft                             closure                     response,                   and
        shall respond with a                                            cancel the ‘tts’ timer (when used) on the basis of DM0
        concatenated downlink message                                  or DM1.
        containing DM0 WILCO and the                                   Some FANS 1/A aircraft will respond with single element
        response messages(s).                                          DM0 message and the DM38 is sent later as an
                                                                       unreferenced message.
                                                                       When the FANS 1/A aircraft sends the DM38 as an
                                                                       unreferenced message:
                                                                       • If the active connection is closed (DM0 sending), to the
                                                                       next Centre (R-ATSU) if any, when it becomes the CDA;
                                                                       • If the active connection remains active (DM1 sending),
                                                                       to the current Centre
                                                                       Any message element concatenated with UM120R will be
                                                                       accepted by the FANS 1/A aircraft.
                                                                       See paragraph 3.2.2.2 for use of CPDLC-End Service.
                                                                       See paragraph 3.2.2.8 for use of UM117R, UM120R and
                                                                       UM135.
                                                                                                                        3-113



3.2.2.11             Error Information
3.2.2.11.1           General Rules
                     Table 3-22Table 3-22Table 3-22 presents the general ATN and the comparable                                  Formatted: Cross-Reference
                     FANS 1/A ERROR information requirements.                                                                    Formatted: Cross-Reference



                                Table 3-22 ATN and FANS 1/A ERROR information requirements
           ATN ERROR information general rule                     FANS 1/A         Interoperability Requirement
                                                                  ERROR
                                                                  information
                                                                  general rule
           3.3.2 CPDLC Message Errors                             No equivalent.   See paragraph 3.2.2.11.2 for processing
           Note: Two types of errors are distinguished:                            Uplink errors using the [error information]
                                                                                   parameter.
           a) A "technical error" occurs when the local
           system detects that the peer system has not been                        See paragraph 3.2.2.11.3 for processing
           designed according to the ATN requirements. The                         Downlink errors using the [error
           error text is intended to be used for debugging                         information] parameter.
           purposes rather than displayed to the controller or
           pilot.
           b) An "operational error" occurs when the local
           system detects that the peer user does not behave
           according to the ATN requirements or local
           constraints prevent an operational response. The
           error text is intended for display to the controller
           or pilot to provide an explanation of the error
           situation.
           3.3.2.1 Composition of CPDLC Error Messages            No equivalent.   See paragraph 3.2.2.11.2 for processing
           CPC-IR 12 When the error case is specified in                           Uplink errors using the [error information]
           ICAO Documents 9880 or [PM-FIS], the system                             parameter.
           shall send a CPDLC Message containing an                                See paragraph 3.2.2.11.3 for processing
           ERROR message element alone (UM159 or                                   Downlink errors using the [error
           DM62) with the [error information] value as                             information] parameter.
           specified in ICAO Document 9880 (0 for
           "unrecognized message reference number", 1 for
           "logical acknowledgement not supported", 2 for
           "insufficient resources", 3 for "invalid message
           element combination" and 4 for "invalid message
           element").
3-114


        ATN ERROR information general rule                      FANS 1/A           Interoperability Requirement
                                                                ERROR
                                                                information
                                                                general rule
        CPC-IR 13 When the error case is specified in this No equivalent.          None.
        document, the system shall send a CPDLC                                    See paragraph 3.2.2.11.2 for processing
        Message containing an ERROR message element                                Uplink errors using the [error information]
        (UM159 or DM62) and a FREE TEXT message                                    parameter.
        element (UM183 or DM98) as follows :
                                                                                   See paragraph 3.2.2.11.3 for processing
        a) the error is a technical error, a CPDLC message                         Downlink errors using the [error
        containing an ERROR message element with                                   information] parameter.
        [error information] value (0) concatenated with a
        FREE TEXT message element describing the                                   See paragraph Error! Reference source not
        error;                                                                     found.Erreur ! Source du renvoi
                                                                                   introuvable.0 for the use of FREETEXT.
        b) the error is an operational error and is an
        extension of an error specified in Doc 9880 (“3”
        for invalid message element combination and “4”
        for invalid message element), a CPDLC message
        containing an ERROR message element with
        [error information] value (3) or (4) concatenated
        with a FREE TEXT message element describing
        the error; or
        c) the error is an operational error but is not an
        extension of an error specified in Doc 9880, a
        CPDLC message containing an ERROR message
        element with [error information] value (2)
        concatenated with a FREE TEXT message element
        describing the error.
        CPC-IR 16 When a CPDLC Message containing                 No equivalent.   See paragraph 3.2.2.11.2 for processing
        an ERROR message element concatenated with a                               Uplink errors using the [error information]
        FREE TEXT message element is received, the                                 parameter.
        Aircraft and Ground Systems shall perform the                              See paragraph 3.2.2.11.3 for processing
        display of the message based on the following                              Downlink errors using the [error
        rules:                                                                     information] parameter.
        a) When an UM187/DM97 ERROR message                                        See paragraph Error! Reference source not
        element with [error information] value (0)                                 found.Erreur ! Source du renvoi
        concatenated with a FREE TEXT message element                              introuvable.0 for the use of FREETEXT.
        is received (e.g. it is a technical error), it is a local
        decision whether to make or not to make the
        included free text available to the controller/pilot.
        b) When an UM183/DM98 ERROR message
        element with [error information] value (2), (3) or
        (4) concatenated with a FREE TEXT message
        element is received (e.g. it is an operational error),
        then the received free text is made available for
        display to the pilot/controller.
        CPC-IRec 1 The Aircraft and Ground Systems              No equivalent.     None.
        should not display the ERROR [error information]                           The FANS 1/A aircraft does not display the
        associated text (e.g. insufficient resources) when                         [error information] value.
        the FREE TEXT message element is appended to
        the error.
        CPC-IRec 2 When DM62 ERROR (4) (invalid
        message element) is received, the CPDLC ATSU
        System should display the message to the
        Controller as “UNDEFINED MESSAGE
                                                                                                                         3-115



        ATN ERROR information general rule                 FANS 1/A                 Interoperability Requirement
                                                           ERROR
                                                           information
                                                           general rule
        ELEMENT”.
        CPC-IRec 3 When UM159 ERROR (4) (invalid
        message element) is received,the CPDLC Aircraft
        System should display the message to the Aircrew
        as “UNDEFINED MESSAGE ELEMENT”.
        CPC-IR 14 The CPDLC Aircraft and Ground        No equivalent.               See paragraph 3.2.2.11.2 for processing
        systems shall be prohibited from appending the                              Uplink errors using the [error information]
        FREE TEXT message element to the ERROR with                                 parameter.
        [error information] value (1).                                              See paragraph 3.2.2.11.3 for processing
                                                                                    Downlink errors using the [error
                                                                                    information] parameter.
        CPC-IR 15 The CPDLC Aircraft and Ground            No equivalent.           None.
        systems shall be prohibited from sending an
        ERROR message in response to a LACK or
        ERROR message



3.2.2.11.2       Uplink Error Information – UM159 [error information] Parameter
                 Note:       The information provided in this paragraph together with the information in
                             paragraph 3.2.2.8 (Uplink message elements) for the use of FREE TEXT
                             message element UM183 or UM187 (Free Text) provides the means to
                             exchange UPLINK ERROR Information.
                 Table 3-23Table 3-23Table 3-23 presents the ATN and the comparable FANS 1/A                                      Formatted: Cross-Reference
                 UM159 error information parameter.                                                                               Formatted: Cross-Reference



                          Table 3-23 ATN and FANS 1/A uplink [error information] data type
        ATN UM159 Error                  FANS 1/A UM 159 Error              Interoperability Requirement
        Information Parameter            Information Parameter
        (0) Unrecognized message         (2) Unrecognized message           IR-103               The ATN ground system
        reference number                 reference number                   shall convert the ATN message element
                                                                            UM159 containing (0) Unrecognized message
                                                                            reference number to the FANS 1/A message
                                                                            element UM159 containing (2) Unrecognized
                                                                            message reference number.
                                                                            IR-104               If a technical error occurs,
                                                                            the ATN ground system shall send UM159 as
                                                                            a single element message to the FANS 1/A
                                                                            aircraft.
                                                                            This is done to avoid the FREE TEXT
                                                                            message being presented to the flight crew in
                                                                            case of a technical error.
        (1) Logical acknowledgement      None                               None.
        not accepted
3-116


        ATN UM159 Error                FANS 1/A UM 159 Error              Interoperability Requirement
        Information Parameter          Information Parameter
        (2) Insufficient resources     (5) Insufficient message storage   IR-105             The ATN ground system
                                       capacity                           shall convert the ATN message element
                                                                          UM159 containing (2) Insufficient resources
                                                                          to the FANS 1/A message element UM159
                                                                          containing (5) Insufficient message storage
                                                                          capacity.
        (3) Invalid Message Element    (0) Application error              IR-106             The ATN ground system
        Combination                                                       shall convert the ATN message element
                                                                          UM159 containing (3) Invalid Message
                                                                          Element Combination to the FANS 1/A
                                                                          message element UM159 containing (0)
                                                                          Application error.
        (4) Invalid Message Element    (10) Invalid data                  IR-107             The ATN ground system
                                                                          shall convert the ATN message element
                                                                          UM159 containing (4) Invalid Message
                                                                          Element to the FANS 1/A message element
                                                                          UM159 containing (10) Invalid data.



3.2.2.11.3        Downlink Error Information when DM62 is received as Single Element in IMI
                  AT1/DR1
                  Note:       The FANS 1/A aircraft concatenates DM62 with DM67 (Free Text) in one case,
                              which is presented in paragraph 3.2.2.1.3 - Message Latency.
3.2.2.11.3.1      Downlink [error information] Parameter
                  Table 3-24Table 3-24Table 3-24 presents the ATN and comparable FANS 1/A DM62                          Formatted: Cross-Reference
                  error information parameter.                                                                          Formatted: Cross-Reference



                          Table 3-24 ATN and FANS 1/A downlink [error information] data type
        ATN DM62 Error                FANS 1/A DM62 Error                 Interoperability Requirement
        Information Parameter         Information Parameter
        (3) Invalid message element   (0) Application error               IR-108             The ATN ground system
        combination                                                       shall process an AT1 IMI containing a DM62
                                                                          (application error) as a CPDLC message
                                                                          containing DM62 (invalid message element
                                                                          combination).
                                                                          The FANS 1/A aircrafts send a DM62
                                                                          ERROR ‘applicationError’ when an
                                                                          unsupported combination of uplink elements
                                                                          is received.
                                                                                                            3-117



ATN DM62 Error                    FANS 1/A DM62 Error            Interoperability Requirement
Information Parameter             Information Parameter
None                              (1) Duplicate message          None.
                                  identification number          As per “Air CPDLC-user-abort service
                                                                 (CPDLCUserAbort),“ ’Duplicate message
                                                                 identification number’ error information is
                                                                 sent in AT1 IMI by the FANS 1/A aircraft,
                                                                 but is considered as a connection abort by the
                                                                 ATN ground system.
                                                                 See Table 3-11Table 3-11Table 3-11, “Air           Formatted: Cross-Reference, Font: 9 pt
                                                                 CPDLC-user-abort service
                                                                 (CPDLCUserAbort)” for use of ‘Duplicate            Formatted: Cross-Reference, Font: 9 pt
                                                                 message identification number’ error
                                                                 information.
(0) Unrecognized message          (2) Unrecognized message       IR-109             The ATN ground system
reference number                  reference number               shall process an AT1 IMI containing a DM62
                                                                 (Unrecognized message reference number) as
                                                                 a CPDLC message containing DM62
                                                                 (Unrecognized message reference number).
CPC-IR 26 If the Aircraft or
the CPDLC ATSU System
receives a message that is not
an ERROR message element
and contains a message
reference number which is not
identical to any message
identification number currently
in use, the Aircraft or the
CPDLC ATSU System shall:
a) send a CPDLC downlink or
uplink message containing
message element DM62 or
UM159 (ERROR (error
information)) with the choice
(0)
[unrecognizedMsgReferenceN
umber], and
b) disregard the received
message.
None                              (3) End service with pending   As per the FANS 1/A INTEROP Standard,
                                  messages                       End service with pending messages, error
                                                                 information is only sent in an IMI -DR1.
                                                                 See Table 3-11Table 3-11Table 3-11, “Air           Formatted: Cross-Reference, Font: 9 pt
                                                                 CPDLC-user-abort service (unsolicited
                                                                 DR1),” for use of ‘End service with pending        Formatted: Cross-Reference, Font: 9 pt
                                                                 messages’ error information.
3-118


        ATN DM62 Error                     FANS 1/A DM62 Error                Interoperability Requirement
        Information Parameter              Information Parameter
        None                               (4) End service with no valid      As per the FANS 1/A INTEROP Standard,
                                           response                           ‘End service with no valid response’ error
                                                                              information is sent by the FANS 1/A aircraft
                                                                              in response to a ground CPDLC user abort.
                                                                              See Table 3-11Table 3-11Table 3-11,             Formatted: Cross-Reference, Font: 9 pt
                                                                              “Ground CPDLC-user-abort service,” for use
                                                                              of ‘End service with no valid response’ error   Formatted: Cross-Reference, Font: 9 pt
                                                                              information.
        (2) Insufficient resources         (5) Insufficient message storage   IR-110               The ATN ground system
                                           capacity                           shall process an AT1 IMI containing a DM62
                                                                              (Insufficient message storage capacity) as a
                                                                              CPDLC        message      containing  DM62
                                                                              (Insufficient resources).
        CPC-IR 20 If the Aircraft or
        the CPDLC ATSU System
        receives a message and has
        insufficient resources to handle
        the message, the Aircraft or
        the CPDLC ATSU System
        shall:
        a) send a CPDLC downlink or
        uplink message containing
        message element DM62 or
        UM159 (ERROR (error
        information)) with the choice
        (2) [insufficientResources],
        and
        b) disregard the received
        message.
        None                               (6) No available message            ‘No available message identification number’
                                           identification number              error information is only sent in an IMI DR1.
                                                                              See Table 3-11Table 3-11Table 3-11, “Air        Formatted: Cross-Reference, Font: 9 pt
                                                                              CPDLC-user-abort service (unsolicited
                                                                              DR1),” for use of ‘No available message         Formatted: Cross-Reference, Font: 9 pt
                                                                              identification number’ error information.
        None                               (7) Commanded termination           ‘Commanded termination’ error information
                                                                              is only sent in an IMI DR1.
                                                                              See Table 3-11Table 3-11Table 3-11, “Air        Formatted: Cross-Reference, Font: 9 pt
                                                                              CPDLC-user-abort service (unsolicited
                                                                              DR1),” for use of ’Commanded termination’       Formatted: Cross-Reference, Font: 9 pt
                                                                              error information.
        None                               (8) Insufficient Data              See Table 3-11Table 3-11Table 3-11, “Air        Formatted: Cross-Reference, Font: 9 pt
                                                                              CPDLC-user-abort service,” for use of           Formatted: Cross-Reference, Font: 9 pt
                                                                              ‘Insufficient Data’ error information.
        (3) Invalid message element        (9) Unexpected data                IR-111             The ATN ground system
        combination                                                           shall process an AT1 IMI containing a DM62
                                                                              (Unexpected data) as a CPDLC message
                                                                              containing DM62 (Invalid message element
                                                                              combination).
                                                                                                                3-119



        ATN DM62 Error                  FANS 1/A DM62 Error               Interoperability Requirement
        Information Parameter           Information Parameter
        (3) Invalid message element     (10) Invalid data                 IR-112             The ATN ground system
        combination                                                       shall process an AT1 IMI containing a DM62
                                                                          (Invalid data) as a CPDLC message
                                                                          containing DM62 (Invalid message element
                                                                          combination).



3.2.2.11.3.2     Further Downlink Error Information Case
                 Table 3-25Table 3-25Table 3-25 gives an indication of the FANS 1/A Downlink Error                      Formatted: Cross-Reference
                 Information Cases not mentioned elsewhere and the related interoperability requirements.               Formatted: Cross-Reference



                           Table 3-25 ATN and FANS 1/A further downlink error information
         ATN DOWNLINK Error cases                              FANS 1/A DOWNLINK          Interoperability
                                                               Error cases                Requirement
         CPC-IR 9 When the aircraft is in the CPDLC         No equivalent.                None.
         inhibited state and the Aircraft System receives a
         CPDLC-start indication, the Aircraft System shall
         reject the CPDLC-start request, the CPDLC-start
         response shall include a CPDLC message
         containing the concatenation of message element
         DM62 (ERROR (error information)) with the choice
         (0) followed by message element DM97 (FLIGHT
         CREW HAS INHIBITED CPDLC).
         CPC-IR 10 When reverting to the CPDLC inhibited                                  [error information]
         state,the CPDLC aircraft system shall abort all the
         active CPDLC connections, using the CPDLC-user
         abort request with the "undefined" value (0) in the
         Reason parameter.                                                                                              Comment [P207]:
                                                                                                                        COMMENT #910 PDR#49




         CPC-IR 17 When a CPDLC message is received          No equivalent.               None.
         that results in an error not defined in the ICAO
         Document 9880 and not defined explicitly elsewhere
         in this document, the Aircraft System shall discard
         the received message and send a CPDLC downlink
         message containing the concatenation of message
         element DM62 (ERROR (error information)) with
         the choice (0) (resp. choice (2)) followed by
         message element DM97 (resp. DM98) composed of
         the fixed text “Undefined ERROR” plus optionally a
         user-defined free text.
3-120


        ATN DOWNLINK Error cases                                   FANS 1/A DOWNLINK   Interoperability
                                                                   Error cases         Requirement
        CPC-IR 18 When a CPDLC message is received                 No equivalent.      None.
        that results in an error, that is not already covered in
        ICAO Document 9880, and not defined explicitly
        elsewhere in this document, the ATSU System shall
        discard the message and send a CPDLC uplink
        message containing the message element UM159
        (ERROR (error information)) with the choice (0)
        (resp. choice (2)) followed by message element
        UM183 (resp. UM183) composed of the fixed text
        “Undefined ERROR” plus optionally a user-defined
        free text
        CPC-IR 31 When the CPDLC Aircraft System              No equivalent.           See paragraph 3.2.2.11.3.1
        receives a concatenated uplink CPDLC message that                              for use of Downlink [error
        it does not support (invalid element order), it shall                          information] Parameter.
        discard the received CPDLC message and send a
        CPDLC downlink message containing the
        concatenation of message element DM62 (ERROR
        (error information)) with the choice (0) followed by
        message element DM98 (ELEMENT ORDER
        PROHIBITED).
        CPC-IR 32 When the CPDLC Aircraft System          Not applicable.              FANS1/A never receives
        receives a concatenated uplink CPDLC message that                              UM227.
        contains a UM227 LACK, it shall discard the
        received CPDLC message and send a CPDLC
        downlink message containing the concatenation of
        message element DM62 (ERROR (error
        information)) with the choice (3) followed by
        message element DM98 LOGICAL
        ACKNOWLEDGMENT PROHIBITED IN
        COMBINATION).
                                                                                                            3-121



ATN DOWNLINK Error cases                             FANS 1/A DOWNLINK               Interoperability
                                                     Error cases                     Requirement
CPC-IR 37 When the CPDLC Aircraft System             4.6.6.1.a)                      The FANS 1/A aircraft
receives a CPDLC message with at least one           If a message is received and    accepts all message elements
message element that it does not support, it shall   any message element number      which can be encoded
discard the received message and send a CPDLC        is not represented in section   following the FANS 1/A
downlink message containing the concatenation of     4.6.3.3, CPDLC shall send a     ASN.1 definitions in the
message element DM62 (ERROR (error                   message with the ERROR          FANS 1/A INTEROP
information)) with the choice (4) followed by        [error information] (uM159 or   Standard.
message element DM98 (MESSAGE NOT                    dM62) message element with      See paragraph 3.2.2.11.3.1
SUPPORTED BY THIS AIRCRAFT).                         the [invalidData] value and     for use of Downlink [error
                                                     discard the received message;   information] Parameter.
                                                     OR
                                                     4.6.6.8 a)
                                                     When a message error is
                                                     detected, CPDLC shall send a
                                                     response message containing
                                                     the ERROR [error
                                                     information] (uM159 or
                                                     dM62) message element with
                                                     the value selected in
                                                     accordance with the specific
                                                     requirements of section 4.6.
                                                     together with Appendix A
                                                     A.4.6 - 9 (IMI AT1)
                                                     For the FANS 1/A aircraft,
                                                     when ATCComm receives an
                                                     uplink messages that contains
                                                     a single message element that
                                                     is one of the following
                                                     UM163, UM165, UM166 or
                                                     UM167.
No equivalent                                         The FANS 1/A aircraft will     [error information]See
                                                     discard the received message    paragraph 3.2.2.11.3.1 for
                                                     and send a CPDLC downlink       use of Downlink [error
                                                     messag containing the           information] Parameter.
                                                     message element DM62            Note: Limit for many aircraft
                                                     ERROR [error information]       implementations has been
                                                     with error code, 5              noted to be 80 characters.
                                                     insufficientMsgStorageCapaci    Recommend limitingfree text
                                                     ty.                             uplink messages with IA5
                                                                                     String size greater than 80
                                                                                     characters.
3-122


        ATN DOWNLINK Error cases                               FANS 1/A DOWNLINK                Interoperability
                                                               Error cases                      Requirement
        No equivalent                                          4.6.6.1 d.                       See paragraph 3.2.2.11.3.1
                                                               If a message is received and     for use of Downlink [error
                                                               there are message elements       information] Parameter.
                                                               containing an IA5 string
                                                               character not supported,
                                                               CPDLC shall send a message
                                                               with the DM62 ERROR
                                                               message element
                                                               together with Appendix A.4.6
                                                               - 10 ..... [with
                                                               errorinformation] value set to
                                                               [invalidData]
        CPC-IR 58 When the Aircraft System receives a          4.6.6.2 Message Data Types       See paragraph 3.2.2.11.3.1
        CPDLC message containing data that it does not         If a message is received and     for use of Downlink [error
        support, it shall discard the received CPDLC           any message Data Type is not     information] Parameter.
        message and send a CPDLC downlink message              as represented in section
        containing the message element DM62 (ERROR             4.6.6.3, CPDLC shall send a
        (error information)) with the choice (0) followed by   message with message
        message element DM98 (TYPE OF DATA NOT                 element DM62 ERROR [with
        SUPPORTED BY THIS AIRCRAFT).                           errorinformation] value set to
                                                               [invalidData]
        CPC-IR 60 When the CPLC Aircraft System             No equivalent.                      See paragraph 3.2.2.11.3.1
        receives a CPDLC message and it does not support                                        for use of Downlink [error
        the message parameter combination, it shall discard                                     information] Parameter.
        the received CPDLC message and send a CPDLC
        downlink message containing the message element
        DM62 (ERROR (error information)) with the choice
        (0) followed by message element DM97
        (PROHIBITED DATA COMBINATION IN
        MESSAGE).
        CPC-IR 68 When the CPDLC Aircraft system               No equivalent.                   None.
        receives a CPDLC message with a message element
        containing the frequencyVHF data type not
        specifying a valid VHF channel designators, it shall
        discard the received CPDLC message and send a
        CPDLC downlink message containing the
        concatenation of message element DM62 (ERROR
        (error information)) with the choice (0) followed by
        message element DM98 (INVALID VALUE FOR
        VHF CHANNEL).
        CPC-IR 70 When the CPDLC Aircraft System             No equivalent.                     None.
        receives a CPDLC message containing message                                             The FANS 1/A aircraft does
        element UM79R containing any of the following:                                          not execute a check on the
        departure airport, departure runway or departure                                        validity of the VHF
        procedure, in the [route clearanceR] field, it shall                                    frequency communicated.
        discard the received message and send a CPDLC
        downlink message containing the message element
        DM62 (ERROR (error information)) with the choice
        (0) followed by message element DM97
        (PROHIBITED DATA COMBINATION IN
        MESSAGE).
                                                                                                                   3-123



ATN DOWNLINK Error cases                                 FANS 1/A DOWNLINK                Interoperability
                                                         Error cases                      Requirement
CPC-IR 71When the CPDLC Aircraft System          No equivalent.                           None.
receives a CPDLC message containing the message                                           The FANS 1/A aircraft does
element UM79R or message element UM80R that is                                            not reject the message in this
concatenated with message element UM74R, and if                                           case; airborne automation
it rejects the message because UM74R does not                                             (upload into FMS) may fail.
follow UM79R or UM80R, then it shall discard the
received message and send a CPDLC downlink
message containing the concatenation of message
element DM62 (ERROR (error information)) with
the choice (3)) followed by message element DM98
(ELEMENT ORDER PROHIBITED).
CPC-IR 72When the CPDLC Aircraft System                  No equivalent.                   None.
receives a CPDLC message with a message element                                           The FANS 1/A aircraft does
containing the ATSroutedesignator parameter in the                                        not reject the message in this
routeinformationR variable and the first occurrence                                       case; airborne automation
of this parameter is not preceded by a                                                    (upload into FMS) may fail.
publishedidentiferR parameter, then it shall discard
the received message and send a CPDLC downlink
message containing the concatenation of message
element DM62 (ERROR (error information)) with
the choice (0)) followed by message element DM97
(PROHIBITED DATA COMBINATION IN
MESSAGE)
CPC-IR 74 When the CPDLC Airborne system            No equivalent.                        None.
receives a CPDLC message with a message element,                                          The FANS 1/A aircraft does
containing the ATSroutedesignator parameter and                                           not reject the message in this
this parameter is not followed by a                                                       case; airborne automation
PublishedidentiferR parameter or a                                                        (upload into FMS) may fail.
ATSroutedesignator parameter, then it shall discard
the received message and send a CPDLC downlink
message containing the concatenation of message
element DM62 (ERROR (error information)) with
the choice (0) followed by message element DM97
(PROHIBITED DATA COMBINATION IN
MESSAGE).
CPC-IR 76 When the CPDLC Aircraft System                 4.6.6.1 d.                       See paragraph 3.2.2.11.3.1
receives a CPDLC message with a message element          If a message is received and     for use of Downlink [error
that contains an IRA5String with IRA5 characters         there are message elements       information] Parameter.
the Aircraft System does not support, it shall discard   containing an IA5 string
the received message and send a CPDLC downlink           character not supported,
message containing the concatenation of message          CPDLC shall send a message
element DM62 (ERROR (error information)) with            with the DM62 ERROR
the choice (0) followed by message element DM97          message element
(UNABLE TO DISPLAY CHARACTER).
                                                         together with Appendix A.4.6
                                                         - 10 ..... [with
                                                         errorinformation] value set to
                                                         [invalidData]
3-124


        ATN DOWNLINK Error cases                             FANS 1/A DOWNLINK                 Interoperability
                                                             Error cases                       Requirement
        CPC-IR 78 When the CPDLC Aircraft System                                               See paragraph 3.2.2.11.3.1
        receives a CPDLC message containing more than                                          for use of Downlink [error
        one message elements with a                                                            information] Parameter.
        routeClearanceAIndexR parameter, it shall discard
        the received message and send a CPDLC downlink
        message containing the concatenation of message
        element DM62 (ERROR (error information)) with
        the choice (0) followed by message element DM97
        (MORE THAN ONE ROUTE ELEMENTS IN A
        SINGLE MESSAGE).
        CPC-I-IR 3 When the CPDLC Aircraft System        No equivalent.
        receives a CPDLC message including an route
        clearanceR parameter in the CPDLC message
        header, it shall send a CPDLC downlink message
        containing the concatenation of message element
        DM62 (ERROR (error information)) with the choice
        (0) followed by message element DM97
        (PROHIBITED DATA COMBINATION IN
        MESSAGE).
        CPC-IR 83 When the CPDLC Aircraft System         No equivalent.                        DTAXI service not provided
        receives a CPDLC message containing more than                                          to FANS1/A aircraft.
        one D-TAXI UM330 [GraphicTaxiRoute] message
        element, it shall reject the CPDLC D-TAXI
        message by sending a CPDLC downlink message
        containing the concatenation of message element
        DM62 (ERROR (error information)) with the choice
        (0) followed by message element DM97 (DTAXI
        MESSAGE CONTAIN MORE THAN ONE
        GRAPHICAL ELEMENT).
        CPC-IR 85 Except for received UM defined after        No equivalent                    No extensibility marker in
        the extensibility marker, when any data is received                                    FANS1/A ASN.1.
        after the extensibility field and is not supported by
        the Aircraft System, the CPDLC Aircraft System
        shall send a CPDLC downlink message containing
        DM62 (ERROR (error information)) with the choice
        (0) and DM97 (EXTENSIBILITY DATA NOT
        SUPPORTED FOR THIS DATA TYPE).
        CPC-IR 86 When the CPDLC Aircraft system             4.6.2.1.1 a)- 2)                  The FANS 1/A aircraft will
        receives a CPDLC-start indication containing a       If the “Connect Request”          reject the connection
        CPDLC message and it accepts the start, it shall     (IMI=CR1) does not contain a      initiation ifno or another
        discard the received CPDLC message and include in    message with the                  message element than
        the positive CPDLC-start response a CPDLC            [icaofacilitydesignation]         UM163 is contained; see
        message containing the concatenation of message      [tp4table] (uM163) message        paragraph 4.3.2.1.
        element DM62 (ERROR (error information)) with        element only, send                See paragraph 3.2.2.11.3.1
        the choice (0) followed by message element DM98      “Disconnect Request”              for use of Downlink [error
        (MESSAGE NOT PERMITTED IN A START                    (IMI=DR1) containing a            information] Parameter.
        REQUEST).                                            message with the ERROR
                                                             [error information] (dM62)
                                                             message element with the
                                                             appropriate value specified, as
                                                             identified within section
                                                             4.6.6.8.
                                                                                                                3-125



3.2.2.12          Message Element Parameters and Data Type
3.2.2.12.1        Level/Altitude Parameter
                  The level parameter in ATN CPDLC messages is comparable to the altitude parameter in
                  FANS 1/A CPDLC messages. In ATN systems, any message that contains the level
                  parameter can contain a single level (LevelType) or a vertical range (Sequence of 2
                  LevelType). In FANS 1/A systems, the altitude parameter is always a single altitude.
                  Likewise, in ATN systems, the LevelSingle parameter is always a single level.
NIR-269            The ATN ground system shall reject the use of a vertical range to a FANS 1/A aircraft except for the
messages that have interoperability requirements associated with using a vertical range.
                  See paragraph 3.2.2.8 and paragraph 3.2.2.9 for interoperability requirements associated
                  with using a vertical range.
                  There are differences in the ATN choices of LevelType and the FANS 1/A choices of
                  Altitude. Where the ATN Level Type choices have comparable FANS 1/A Altitude
                  choices, there are differences in the parameter ranges and resolutions.
                  Table 3-26Table 3-26Table 3-26 presents the LevelType/Altitude differences between                      Formatted: Cross-Reference
                  ATN and FANS 1/A and the impact on the ATN ground system.                                               Formatted: Cross-Reference
                  Note: See paragraph 3.2.2.9 for processing downlink message elements containing the
                  following parameter/data types, which are not supported by the ATN ground system:
                                 FANS 1/A ‘Altitude qfe’ and ‘Altitude qfe meters,’ which are only used as a
                                  response to an uplink message.
                                 FANS 1/A ‘Altitude gnss’ and ‘Altitude gnss meters,’ which are only used
                                  as a response to an uplink message.
3-126

                    Table 3-26     ATN and FANS 1/A altitude data type
        ATN LevelType              FANS 1/A Altitude         Interoperability Requirement
        Level feet:                Altitude qnh:             NIR-270             The ATN ground
         Range: -600 to 70000       Range: 0 to 25000
                                                             system shall use the Level feet only with     Comment [P208]:
                                                             values from 0 feet to 25000 feet inclusive.   COMMENT #780
         Units: feet                Units: feet
         Resolution: 10             Resolution: 10
                                                             NIR-271             The ATN ground
                                                             system shall prohibit the use of Level feet
                                                             parameter not respecting the FANS 1/A
                                                             parameter range.
                                                             No additional interoperability requirement
                                                             for downlink message elements.
                                                             The ATN ground system can process the
                                                             altitude qnh choice from the FANS 1/A
                                                             aircraft.
        Level flight level:        Altitude flight level:    IR-114                The ATN ground
                                                             system shall use the Level Flight Level
         Range: 030 to 700          Range: 030 to 600
                                                             only with values from FL30 to FL600
         Units: hundreds of feet    Unit: hundreds of feet
                                                             inclusive.
         Resolution: 1              Resolution: 1
                                                             NIR-272               The ATN ground
                                                             system shall prohibit the use of Level
                                                             flight level parameter not respecting the
                                                             FANS 1/A parameter range.
                                                             No additional interoperability requirement
                                                             for downlink message elements.
                                                             The ATN ground system can process the
                                                             altitude flight level choice from the
                                                             FANS 1/A aircraft.
        Level meters:              Altitude qnh meters:      NIR-273           The ATN ground
                                                             system shall use the Level meters only
         Range: -30 to 25000        Range: 0 to 16000
                                                             with values from 0 feet to 16000 meters
         Units: meters              Units: meters
                                                             inclusive.
         Resolution: 1              Resolution: 1
                                                             NIR-274               The ATN ground
                                                             system shall prohibit the use of Level
                                                             meters parameter not respecting the
                                                             FANS 1/A parameter range.
                                                             No additional interoperability requirement
                                                             for downlink message elements.
                                                             The ATN ground system can process the
                                                             altitude flight level choice from the
                                                             FANS 1/A aircraft.
                                                                                                                          3-127



                 ATN LevelType                    FANS 1/A Altitude                Interoperability Requirement
                 Level flight level metric:       Altitude flight level metric:    NIR-275               The ATN ground
                                                                                   system shall use the Level Flight Level
                                                   Range: 100 to 2000
                                                                                   Metric only with values from FL100 to           Comment [PF209]:
                   Range: 100 to 2500              Unit: tens of meters                                                            COMMENT #1216, PDR 257 a)
                                                                                   FL2000 inclusive.
                   Units: tens of meters           Resolution: 10
                   Resolution: 10                                                  NIR-276               The ATN ground
                                                                                   system shall prohibit the use of Level
                                                                                   flight level metric parameter not
                                                                                   respecting the FANS 1/A parameter
                                                                                   range.
                                                                                   No additional interoperability requirement
                                                                                   for downlink message elements.
                                                                                   The ATN ground system can process the
                                                                                   altitude flight level choice from the
                                                                                   FANS 1/A aircraft.
                                                                                                                                   Comment [PF210]:
                             Table 3-27 ATN Level data type sent in FANS UM169 Free Text                                           PDR #258

                 ATN Level                        Free Text Format                   Interoperability Requirement
                 Level feet: -600 to 70000 feet                                      NIR-277              When including an
                                                                                     ATN [level] parameter in a FANS 1/A
                  Or
                                                                                     message element UM169, the ATN
                 Level flight level: 030 to 700     “FL[n]nn”                        ground system shall include a character
                 FL (feet)                        character string (2 or 3           string representing the level flight level.
                                                  characters) that represents an     Note. Other choices for [level] are not
                   Or                             integer from 30 to 700.            viable options.
                 Level meters: -30 to 25000                                          NIR-278              When including an
                 meters                                                              ATN [level] parameter in a FANS 1/A
                   Or                                                                message element UM169, the ATN
                                                                                     ground system shall prohibit the use of
                 Level flight level metric: 100
                                                                                     other unit than level flight level.
                 to 2500 FL (meter)
                   Or
                 Level flight level metric:
                    100 to 2500
                   Units: tens of meters
                   Resolution: 10



3.2.2.12.2      Distance Parameter
                The distance parameter in CPDLC message elements is comparable in ATN and
                FANS 1/A. There are differences in the parameter ranges and resolutions.
                Table 3-31Table 3-31Table 3-31 presents the distance Data Type differences between                                 Formatted: Cross-Reference
                ATN and FANS 1/A and the impact on the ATN ground system.                                                          Formatted: Cross-Reference
                                      Table 3-28 ATN and FANS 1/A distance data type
        ATN Distance                 FANS 1/A Distance                Interoperability Requirement
        Distance Nm:                 DistanceNm:                      None
         Range: 0 to 999.9            Range: 0 to 999.9
         Resolution: 0.1              Resolution: 0.1
         Unit: nm                     Unit: nm
3-128


        ATN Distance                FANS 1/A Distance             Interoperability Requirement
        Distance Km:                DistanceKm:                   NIR-279             The ATN ground system shall use
                                                                  the Distance only with the resolution equal to 1 km and
         Range: 0..2000              Range: 1 to 2024
                                                                  values of 1 to 1024 km inclusive.
         Resolution 0.25             Resolution 1
                                                                  NIR-280             The ATN ground system shall
         Unit: km                    Unit: km                     prohibit the use of the DistanceKm data type not
                                                                  respecting the FANS 1/A parameter resolution and
                                                                  range.
                                                                  No additional interoperability requirement for downlink
                                                                  message elements.
                                                                  Whether only input with the permitted resolution is
                                                                  enabled or a rounding mechanism is used is a local
                                                                  matter.

3.2.2.12.3      PositionR Parameter
                The ATN PositionR and FANS1/A Position parameter in CPDLC message elements are
                not the same. There are also differences in the ATN and the FANS 1/A parameter ranges
                and resolutions.
                Table 3-29 presents the PositionR / Position Data Type differences between ATN and
                FANS 1/A and the impact on the ATN ground system.


                                     Table 3-29 ATN and FANS 1/A position data type
                ATN PositionR                  FANS 1/A Position               Interoperability Requirement
                Published Identifier R:        Fixname                         NIR-281               The ATN ground
                                                                               system shall convert the Published
                                                  1 to 5 characters
                                                                               Identifier Name element of the ATN
                  Published Identifier Name
                                                                               Published IdentifierR parameter into the
                    1 to 5 characters
                                                                               FANS 1/A Fixname parameter.
                                                                               NIR-282               The ATN ground
                  Latitude and/or longitude                                                                                 Comment [PF211]:
                                                                               system shall ignore the Latitude and/or
                                                                                                                            PDR #335
                                                                               longitude in the ATN Published
                                                                               IdentifierR parameter.
                                                                               No additional interoperability
                                                                               requirement for downlink message
                                                                               elements.
                                                                               The use of Lat/Lon is mandatory by the
                                                                               SPR Standard, CPDLC-J-OR 1 for all
                                                                               CPDLC messages.
                                                                               The ATN ground system cannot process
                                                                               the fix name choice from the FANS 1/A
                                                                               aircraft (no lat/long parameter).
                                               Navaid                          The ATN ground system cannot process
                                                 1 to 4 characters             the Navaid choice from the FANS 1/A
                                                                               aircraft (no lat/long parameter).
                                               Airport                         The ATN ground system cannot process
                                                 4 characters                  the Airport choice from the FANS 1/A
                                                                               aircraft (no lat/long parameter).
                Latitude and/or Longitude      Latitude and Longitude          See paragraph 3.2.2.12.16 for use of
                                                                               latitude/longitude parameter.
                                                                                                      3-129



             ATN PositionR              FANS 1/A Position        Interoperability Requirement
             Place BearingR Distance    Place Bearing Distance   See paragraph 3.2.2.12.14 for use of
                                                                 Place BearingR Distance.




                     Table 3-30 ATN positionR data type sent in FANS UM169 Free Text
             ATN PositionR              Free Text Format         Interoperability Requirement
               Published Identifier R    a 1 to 5 char string    NIR-283              When including an
                                                                 ATN [positionR] parameter in a FANS
               LatitudeLongitude         None                    1/A message element UM169, the ATN
                                                                 ground system shall include a character
               Or                                                string representing the            location
                                                                 indicator of the facility designation for a
               Place Bearing Distance    None                    published identifier.
                                                                 Note. Other choices for [positionR]
                                                                 (place      bearing       distance     and
                                                                 latitude/longitude) are not viable
                                                                 options.
                                                                 NIR-284              When including an
                                                                 ATN [positionR] parameter in a FANS
                                                                 1/A message element UM169, the ATN
                                                                 ground system shall prohibit the use of
                                                                 place      bearing        distance     and
                                                                 latitude/longitude parameters included
                                                                 in the [positionR].




3.2.2.12.4   Speed Parameter
             The speed parameter in CPDLC message elements is comparable in ATN and FANS 1/A.
             There are differences in the ATN and the FANS 1/A choices of speed. Where the ATN
             and FANS 1/A speed choices are comparable there are differences in the parameter
             ranges and resolutions.
             Table 3-31Table 3-31Table 3-31 presents the speed Data Type differences between ATN               Formatted: Cross-Reference
             and FANS 1/A and the impact on the ATN ground system.                                             Formatted: Cross-Reference
3-130

                              Table 3-31      ATN and FANS 1/A speed data type
        ATN Speed                 FANS 1/A Speed           Interoperability Requirement
        Speed ground:             Speed ground:            IR-118              The ATN ground system shall use
                                                           the Speed Ground only with the resolution equal to 10
         Range: -50 to 2000        Range: 70 to 700
                                                           Knots and values of 70 to 700 Knots inclusive.
         Resolution: 1             Resolution 10
         Unit: knots               Unit: knots             IR-119              The ATN ground system shall
                                                           prohibit the use of the Speed Ground data not
                                                           respecting the FANS 1/A parameter resolution and
                                                           range.
                                                           No additional interoperability requirement for downlink
                                                           message elements.
                                                           Whether only input with the permitted resolution is
                                                           enabled or a rounding mechanism is used is a local
                                                           matter.
                                                           The ATN ground system can process the Speed Ground
                                                           choice from the FANS 1/A aircraft.
        Speed Ground Metric:      Speed ground metric:     NIR-285             The ATN ground system shall use
                                                           the Speed Ground Metric only with the resolution equal
         Range: -100 to 4000       Range: 100 to 2650
                                                           to 10 Kilometers/hour and values of 100 to 2650
         Resolution: 1             Resolution: 10
                                                           Kilometers/hour inclusive.
         Unit: Kilometers/Hour     Unit: Kilometers/Hour
                                                           NIR-286             The ATN ground system shall
                                                           prohibit the use of the Speed Ground Metric data not
                                                           respecting the FANS 1/A parameter resolution and
                                                           range.
                                                           No additional interoperability requirement for downlink
                                                           message elements.
                                                           Whether only input with the permitted resolution is
                                                           enabled or a rounding mechanism is used is a local
                                                           matter.
                                                           The ATN ground system can process the Speed Ground
                                                           Metric choice from the FANS 1/A aircraft.
        Speed indicated:          Speed indicated:         IR-120              The ATN ground system shall use
                                                           the Speed Indicated only with the resolution equal to 10
         Range: 0 to 400           Range: 70 to 380
                                                           Knots.
         Resolution: 1             Resolution: 10
         Unit: knots               Unit: knots             IR-121              The ATN ground system shall
                                                           prohibit the use of Speed Indicated data not respecting
                                                           the FANS 1/A parameter resolution and range.
                                                           No additional interoperability requirement for downlink
                                                           message elements.
                                                           Whether only input with the permitted resolution is
                                                           enabled or a rounding mechanism is used is a local
                                                           matter.
                                                           The ATN ground system can process the Speed
                                                           Indicated choice from the FANS 1/A aircraft.
                                                                                                   3-131



ATN Speed                 FANS 1/A Speed            Interoperability Requirement
Speed indicated metric:   Speed indicated metric:   NIR-287            The ATN ground system shall use
                                                    the Speed Indicated Metric only with the resolution
 Range: 0 to 800           Range: 100 to 1370
 Resolution: 1             Resolution: 10
                                                    equal to 10 Kilometers/Hour and values of 100 to 800      Comment [PF212]:
                                                    Kilometers/Hour inclusive.                                PDR #329
 Unit: kilometers/hour     Unit: kilometers/hour
                                                    NIR-288            The ATN ground system shall
                                                    prohibit the use of Speed Indicated Metric data not
                                                    respecting the FANS 1/A parameter resolution and
                                                    range.
                                                    NIR-289            The ATN ground system shall            Comment [PF213]:
                                                    reject a FANS 1/A downlink message that contains the      PDR #329
                                                    Speed indicated metric with a value greater than 800.
                                                    Whether only input with the permitted resolution is
                                                    enabled or a rounding mechanism is used is a local
                                                    matter.
                                                    The ATN ground system can process the Speed
                                                    Indicated Metric choice from the FANS 1/A aircraft.
Speed True:               Speed True:               NIR-290             The ATN ground system shall use
                                                    the Speed True only with the resolution equal to 10
 Range: 0 to 2000          Range: 70 to 700
                                                    Knots and values of 70 to 700 Knots inclusive.
 Resolution: 1             Resolution: 10
 Unit: Knots               Unit: Knots              NIR-291             The ATN ground system shall
                                                    prohibit the use of Speed True data not respecting the
                                                    FANS 1/A parameter resolution and range.
                                                    No additional interoperability requirement for downlink
                                                    message elements.
                                                    Whether only input with the permitted resolution is
                                                    enabled or a rounding mechanism is used is a local
                                                    matter.
                                                    The ATN ground system can process the Speed True
                                                    choice from the FANS 1/A aircraft.
Speed True Metric:        Speed True Metric:        NIR-292             The ATN ground system shall use
                                                    the Speed True Metric only with the resolution equal to
 Range: 0 to 4000          Range: 100 to 1370
                                                    10 Kilometers/Hour and values of 100 to 1370
 Resolution: 1             Resolution: 10
                                                    Kilometers/Hour inclusive.
 Unit: Kilometers/Hour     Unit: Kilometers/Hour
                                                    NIR-293             The ATN ground system shall
                                                    prohibit the use of Speed True Metric data not
                                                    respecting the FANS 1/A parameter resolution and
                                                    range.
                                                    No additional interoperability requirement for downlink
                                                    message elements.
                                                    Whether only input with the permitted resolution is
                                                    enabled or a rounding mechanism is used is a local
                                                    matter.
                                                    The ATN ground system can process the Speed True
                                                    Metric choice from the FANS 1/A aircraft.
3-132


        ATN Speed                  FANS 1/A Speed                  Interoperability Requirement
        Speed mach:                Speed mach:                     IR-122               The ATN ground system shall
                                                                   uplink the SpeedMach only with the resolution equal to
         Range .5 to 4.0            Range: .61 to .92
                                                                   0.01 and values of .61 to 4.0 Mach inclusive.
         Resolution: 0.001          Resolution: 0.01
         Unit: mach                 Unit: mach                     IR-123               When requiring Mach speeds in the
                                                                   range 0.61 to 0.92, the ATN ground system shall use
                                                                   the Speed mach data type to uplink the Speed mach
                                   Or                              parameter.
                                                                   IR-124               When requiring Mach speeds in the
                                                                   range 0.93 to 4.0, the ATN ground system shall use the
                                   Speed mach large
                                                                   Speed mach large data type to uplink the Speed mach
                                    Range: .93 to 6.04             parameter.
                                    Resolution: 0.01               IR-125               The ATN ground system shall
                                    Unit: mach                     prohibit the use of Speed Mach data not respecting the
                                                                   FANS 1/A parameter resolution and range.
                                                                   IR-126               When receiving a message element
                                                                   with the DataType choice Speed Mach Large
                                                                   containing a value higher than 4.0, the ATN ground
                                                                   system shall reject the message and respond per the
                                                                   ATS INTEROP Standard, paragraph 3.3.7.6.4.1.2, and
                                                                   this document, paragraph 3.2.2.11.                       Comment [P214]:
                                                                   Whether only input with the permitted resolution is      COMMENT #781
                                                                   enabled or a rounding mechanism is used is a local
                                                                   matter.



                             Table 3-32 ATN speed data type sent in FANS UM169 Free Text
                 ATN Speed                      Free Text Format                Interoperability Requirement
                 Speed ground: -50 to 2000                                      NIR-294            When including an
                                                                                ATN [speed] parameter in a FANS 1/A
                   knots                        [-][n][n][n]nKT GS              message element UM169, the ATN
                   Or
                                                                                ground system shall include a character
                 Speed Ground Metric: -100 to                                   string representing the speed value,
                 4000 Kilometers/Hour           [-][n][n][n]nKM/HR GS           speed type and speed unit using the
                   Or                                                           specified format.                           Comment [PF215]:
                 Speed indicated: 0 to 400                                                                                  PDR #258
                                                [n][n]nKT IAS
                 knots
                   Or
                 Speed indicated metric: 0 to   [n][n]nKM/HR IAS
                 800 kilometers/hour
                   Or
                 Speed True: 0 to 2000 Knots    [n][n][n]nKT TAS
                   Or
                 Speed True Metric: 0 to 4000
                 Kilometers/Hour                [n][n][n][n]nKM/HR TAS
                   Or
                 Speed mach: 0.5 to 4.000       [n/VOID].n[n]
                 mach
                                                                                                           3-133



3.2.2.12.5      Specified Distance/Distance Offset Parameter Message
                The specified distance parameter in ATN CPDLC messages is comparable to the distance
                offset parameter in FANS 1/A CPDLC messages. There are differences in the ATN and
                the FANS 1/A choices of distance offset. Where the ATN and FANS 1/A specified
                distance/distance offset choices are comparable there are differences in the parameter
                ranges and resolutions.
                Table 3-33Table 3-33Table 3-33 presents the specified distance/distance offset Data Type             Formatted: Cross-Reference
                differences between ATN and FANS 1/A and the impact on the ATN ground system.                        Formatted: Cross-Reference



                                 Table 3-33 ATN and FANS 1/A distance offset data type
        ATN Specified Distance      FANS 1/A Distance Offset   Interoperability Requirement
        Distance specified nm:      Distance offset nm:        IR-127              The ATN ground system shall
                                                               use the Distance Specified Nm only with values from
         Range: 1 to 250             Range: 1 to 128
                                                               1 to 128 Nm inclusive.
         Resolution: 1               Resolution: 1
         Unit: nautical miles        Unit: nautical miles      IR-128              The ATN ground system shall
                                                               prohibit the use of Distance Specified Nm not
                                                               respecting the FANS 1/A parameter range.
                                                               No additional interoperability requirement for
                                                               downlink message elements.
                                                               The ATN ground system can process the Distance
                                                               offset Nm from the FANS 1/A aircraft.
        Distance specified km:      Distance offset nm:        NIR-295            The ATN ground system shall
                                                               use the Distance Specified Km only with values from
        Range: 1 to 500             Range: 1 to 256
                                                               1 to 256 Km inclusive.
        Resolution: 1               Resolution: 1              NIR-296            The ATN ground system shall
        Unit: kilometers            Unit: kilometers           prohibit the use of Distance Specified Km not
                                                               respecting the FANS 1/A parameter range.
                                                               No additional interoperability requirement for
                                                               downlink message elements.
                                                               The ATN ground system can process the Distance
                                                               offset Nm from the FANS 1/A aircraft.



3.2.2.12.6      Direction Parameter Message
                The direction parameter in CPDLC message elements is identical in ATN and FANS 1/A.
                The enumerated values and definitions in ATN and FANS 1/A are identical.


3.2.2.12.7      Time/Timesec Parameter
                The timesec parameter in ATN CPDLC messages is comparable to the time parameter in
                FANS 1/A CPDLC messages. There are differences in the ATN and the FANS 1/A
                choices of timesec.
                Table 3-34Table 3-34Table 3-34 presents the time/timesec Data Type differences
                between ATN and FANS 1/A and the impact on the ATN ground system.
3-134



                                 Table 3-34 ATN and FANS 1/A Time data type
             ATN Timesec                    FANS 1/A Time        Interoperability Requirement
             TimeHours:                     TimeHours:           None.
              Range: 0 to 23                 Range: 0 to 23
              Resolution: 1                  Resolution: 1
              Unit: Hour                     Unit: Hour
             TimeMinutes:                   TimeMinutes:         None.
              Range: 0 to 59                 Range: 0 to 59
              Resolution: 1                  Resolution: 1
              Unit: Minute                   Unit: Minute
             TimeSeconds: (Optional)        None.                NIR-297          The ATN ground
                                                                 system shall prohibit the use of
              Range: 0 to 59
                                                                 TimeSeconds to a FANS 1/A aircraft
              Resolution: 1
                                                                 when timeSeconds are specified.
              Unit: Second



                        Table 3-35 ATN Time data type sent in FANS UM169 Free Text
             ATN Time                       Free Text Format      Interoperability Requirement
             TimeHours: 0 to 23 hour          hhmm                NIR-298            The ATN ground
                                                                  system shall include a 4 character string
             TimeMinutes: 0 to 59 minutes
                                                                  of converted integers in the time
                                                                  parameter.

                     Table 3-36 ATN Timesec data type sent in FANS UM169 Free Text
             ATN Timesec                    Free Text Format      Interoperability Requirement
             TimeHours: 0 to 23 hour          hhmm                NIR-299              When including an
                                                                  ATN [timesec] parameter in a FANS
             TimeMinutes: 0 to 59 minutes
                                                                  1/A message element UM169, the ATN
             TimeSeconds: (Optional) 0 to                         ground system shall include a 4
             59 Second                                            character string of converted integers in
                                                                  the time parameter.




3.2.2.12.8   Vertical Rate Parameter Message
             The vertical rate parameter in CPDLC message elements is comparable in ATN and
             FANS 1/A CPDLC messages. There are differences in the ATN and FANS 1/A choices
             of vertical rate. Where the ATN and FANS 1/A vertical rate choices are comparable there
             are differences in the parameter ranges and resolutions.
             Table 3-37Table 3-37Table 3-37 the vertical rate parameter differences between ATN               Formatted: Cross-Reference
             and FANS 1/A and the impact on the ATN ground system.                                            Formatted: Cross-Reference
                                                                                                              3-135



                                  Table 3-37 ATN and FANS 1/A vertical rate data type
        ATN Vertical Rate             FANS 1/A Vertical Rate       Interoperability Requirement
        Parameter                     Parameter
        Vertical rate English:        Vertical rate English:       IR-129               The ATN ground system shall
                                                                   use the Vertical Rate English only with the
         Range: 0 to 30000             Range: 0 to 6000
                                                                   resolution equal to 100 Feet/Minute and values of 0
         Resolution: 10                Resolution: 100
                                                                   to 6000 Feet/Minute inclusive.
         Unit: feet/minute             Unit: feet/minute
                                                                   IR-130               The ATN ground system shall
                                                                   prohibit the use of Vertical Rate English data not
                                                                   respecting the FANS 1/A parameter resolution and
                                                                   range.
                                                                   No additional interoperability requirement for
                                                                   downlink message elements.
                                                                   Whether only input with the permitted resolution is
                                                                   enabled or a rounding mechanism is used is a local
                                                                   matter.
                                                                   The ATN ground system can process the Vertical
                                                                   Rate English parameter from a FANS 1/A aircraft.
        Vertical rate Metric:         Vertical rate Metric:        NIR-300             The ATN ground system shall
                                                                   use the Vertical Rate Metric only with the
         Range: 0 to 10000             Range: 0 to 2000
                                                                   resolution equal to 10 Meters/Minute and values of
         Resolution: 10                Resolution: 10
                                                                   0 to 2000 Meters/Minute inclusive.
         Unit: meters/minute           Unit: meters/minute
                                                                   NIR-301             The ATN ground system shall
                                                                   prohibit the use of Vertical Rate Meters data not
                                                                   respecting the FANS 1/A parameter resolution and
                                                                   range.
                                                                   No additional interoperability requirement for
                                                                   downlink message elements.
                                                                   Whether only input with the permitted resolution is
                                                                   enabled or a rounding mechanism is used is a local
                                                                   matter.
                                                                   The ATN ground system can process the Vertical
                                                                   Rate Metric parameter from a FANS 1/A aircraft.



3.2.2.12.9        Facility and Facility Designation/ ICAO Facility Designation Parameter
                  The facility parameter in ATN allows message elements to be sent either without
                  specifying a facility designation or with specifying a facility designation; this option does
                  not exist in FANS 1/A.
                  The facility designation parameter or Data Type in ATN CPDLC messages is comparable
                  to the ICAO facility designation parameter in FANS 1/A.
                  The ATN facility designation parameter or Data Type and the FANS 1/A ICAO facility
                  designation parameter differ only in the number of characters that can be used to specify
                  a facility.
3.2.2.12.9.1      Facility Parameter
                  Table 3-38Table 3-38Table 3-38 the facility parameter differences between ATN and                      Formatted: Cross-Reference
                  FANS 1/A and the impact on the ATN ground system.                                                      Formatted: Cross-Reference
3-136



                                     Table 3-38 ATN and FANS 1/A Facility data type
               ATN Facility                  FANS 1/A                      Interoperability Requirement
               Facility                      No equivalent.                IR-131               The ATN ground
                                                                           system shall prohibit the use of null Data
                 (null) or
                                                                           Type.
                 Facility Designation
                   size: 4 to 8 characters                                 The ATN ground system has no
                                                                           possibility to cancel a previously sent
                                                                           Next Data Authority identification.
                                                                           See paragraph 3.2.2.12.9.2 for use of
                                                                           facility designation parameter.



3.2.2.12.9.2   Facility Designation / ICAO Facility Designation Data Type
               Table 3-39Table 3-39Table 3-39 present the facility designation and ICAO facility                        Formatted: Cross-Reference
               designation Data Type differences between ATN and FANS 1/A and the impact on the                         Formatted: Cross-Reference
               ATN ground system.


                        Table 3-39 ATN and FANS 1/A ICAO facility designation data type
               ATN Facility Designation       FANS 1/A ICAO Facility         Interoperability Requirement
                                              Designation
               Facility designation:          ICAO facility designation:     IR-132               The ATN ground
                                                                             system shall use the Facility
                 Size: 4 to 8 characters        Size: 4 characters
                                                                             Designation only with size 4, using
                                                                             the first 4 letters.
                                                                             No additional interoperability
                                                                             requirement for downlink message
                                                                             elements.
                                                                             The ATN ground system can process
                                                                             the ICAO Facility Designation from
                                                                             the FANS 1/A aircraft.
                                                                             Facility Designation is also a Data
                                                                             Type within the Unit Name
                                                                             Parameter.
                                                                             The truncation should be assessed for
                                                                             an ATN ground system that shares the
                                                                             same location indicator, but has a
                                                                             different function indicator.
                                                                                                      3-137



                Table 3-40 ATN Facility Designation data type sent in FANS UM169 Free Text
              ATN Facility Designation    Free Text Format          Interoperability Requirement
              Facility designation:       4 char string             NIR-302               When including an
                                                                    ATN [facility designation] parameter in
                Size: 4 to 8 characters
                                                                    a FANS 1/A message element UM169,
                                                                    the ATN ground system shall include a
                                                                    4 character string.
                                                                    Despite the use of free text, it is
                                                                    recommended to only use four letters
                                                                    because the FANS 1/A aircraft only
                                                                    displays four letters for facility
                                                                    indication to the flight crew.



3.2.2.12.10   Unit Id/ICAO Unit Name Parameter
              The unit ID parameter in ATN CPDLC message elements is comparable to the ICAO unit
              name parameter in FANS 1/A CPDLC message elements. There are differences in the
              ATN and the FANS 1/A parameter composition of unit ID / ICAO unit name. Where the
              ATN unit ID and FANS 1/A ICAO unit name parameter composition is comparable there
              are differences in the parameter designations.
              Table 3-41Table 3-41Table 3-41 presents the unit ID/ICAO unit name Data Type                    Formatted: Cross-Reference
              differences between ATN and FANS 1/A and the impact on the ATN ground system.                   Formatted: Cross-Reference
              Note. The same rules apply for the ATN Unit Id data type.
3-138

            Table 3-41              ATN and FANS 1/A Unit Id / Unit Name data type
        ATN Unit Id                       FANS 1/A ICAO Unit Name           Interoperability Requirement
        [0] Facility designation          ICAO facility identification      IR-133              When using the
        (optional):                                                         UnitIddata type, the ATN ground
                                          ICAO facility designation
                                                                            system shall convert the ATN
          Size: 4 to 8 characters           Size: 4 characters              parameter “Facility Name” to the
                                                                            FANS 1/A parameter “ICAO Facility
                                          Or                                Name.
                                                                            IR-134              The ATN ground
                                                                            system shall prohibit the use of
                                          ICAO facility name:               ‘radio’, ‘apron’, ‘info’, ‘ramp’,
        [1]Facility name                    Size: 3 to 18 characters        ‘flightwatch’, ‘aoc’, ‘deicing’ and
          Size: 3 to 18 characters                                          ‘flightService’ Data Types.
                                          ICAO facility function:           No additional interoperability
        [2] Facility functionR                                              requirement for downlink message
                                            centre                          elements.
          centre                            approach
          approach                          tower                           There are no FANS 1/A downlink
          tower                             final                           messages containing the ICAO unit
          final                             ground control                  name parameter.
          ground control                    clearance delivery
          clearance delivery                departure
          departure                         control
          control
          radio
          apron
          info
          ramp
          flightwatch
          aoc
         deicing
         flightService



                Table 3-42 ATN unit name data type sent in FANS UM169 Free Text
        ATN unit name Designation         Free Text Format                Interoperability Requirement
        Facility designation:             [facility identification] = 4- NIR-303              When including an
                                          character ICAO code            ATN [unit name] parameter in a FANS
          Size: 4 to 8 characters
                                                                         1/A message element UM169, the ATN
        Facility name                                                    ground system shall include the facility
          Size: 3 to 18 characters        None                           identification and the facility function.
        Facility function:                                               Note. The facilitname is ignored.
          Centre (0)                      [facility function] as a
          Approach (1)                    character string
          Tower (2)
          Final (3)
          ground control (4)
          clearance delivery (5)
          departure (6)
          control (7)
          radio (8)
          apron (9),
          info (10),
          ramp (11),
          flightwatch (12),
          aoc (13)
                                                                                                           3-139




3.2.2.12.11   Degrees and Number of Degrees Parameters
              The degrees parameter in CPDLC message elements are identical in ATN and
              FANS 1/A.
              Table 3-43Table 3-43Table 3-43 presents the differences between the Number of Degrees
              ATN parameter aand the Degrees FANS 1/A parameter and the impact on the ATN
              ground system.
                     Table 3-43 ATN Number of Degrees and FANS 1/A Degrees data type
              ATN Number of Degrees          FANS 1/A Degrees              Interoperability Requirement
                                             Degrees :                     NIR-304              The ATN ground
                                              Degrees magnetic,            system shall convert the ATN
                                              Or                           Number of Degrees ATN parameter
                                              Degrees true                 into the Degrees magnetic parameter.
              NumberOfDegrees                                              NIR-305              The ATN ground
               Range: 1 to 359                                             system shall reject a FANS 1/A
               Resolution: 1                 Degreesmagnetic :             downlink message that contains the
               Unit: degrees                  Range: 1 to 360              Degreestrue or Degressmagnetic equal
                                              Resolution: 1                to 360 when the FANS 1/A downlink
                                              Unit: degrees                message is converted into an ATN
                                                                           downlink message containing the
                                             Degreestrue :                 Number of Degrees parameter.
                                              Range: 1 to 360
                                              Resolution: 1
                                              Unit: degrees

3.2.2.12.12   Route Clearance / Route clearanceR Parameter
              Table 3-44Table 3-44Table 3-44 presents the route clearance Data Type differences                    Formatted: Cross-Reference
              between ATN and FANS 1/A and the impact on the ATN ground system.                                    Formatted: Cross-Reference



                             Table 3-44 ATN and FANS 1/A route clearance data type
              ATN Route ClearanceR            FANS 1/A Route Clearance      Interoperability Requirement
              [0] AirportDeparture            [0] AirportDeparture          None.
              [1] AirportDestination          [1] Airportdestination        None.
              [2] RunwayDeparture             [2] RunwayDeparture           None.
              [3] ProcedureDeparture          [3] Proceduredeparture        IR-135             (deleted)
                   ProcedureNameR                   Procedurename           See paragraph 3.2.2.12.20 for use of
                                                                            ProcedureNameR Data Type.

              [4] RunwayArrival               Runwayarrival                 None.
              [5] ProcedureApproach           [5] Procedureapproach         See paragraph 3.2.2.12.20 for use of
                   ProcedureNameR                    Proccedurename         ProcedureNameR Data Type.

              [6] ProcedureArrival            [6] Procedurearrival          See paragraph 3.2.2.12.20 for use of
                   ProcedureNameR                    Procedurename          ProcedureNameR Data Type.

              [7] Route InformationR (1..128) Route information (1..128)
3-140

        ATN Route ClearanceR            FANS 1/A Route Clearance       Interoperability Requirement
             Published IdentifierR       Published identifier          See paragraph 3.2.2.12.13 for use of
                                                                       published identifierR Data Type.

             Latitude Longitude          Latitude Longitude            See paragraph 3.2.2.12.16 for use of
                                                                       latitude/longitude Data Type.
             -                           PlaceBearingPlaceBearing      NIR-306              The ATN ground
                                                                       system shall reject a FANS 1/A
                                                                       downlink message that contains a
                                                                       route information element with a
                                                                       PlacebearingPlacebearing element.
             PlaceBearingR Distance      PlaceBearing Distance         See paragraph 3.2.2.12.14 for use of
                                                                       place bearing distance Data Type.
             ATS route designator        Airway Identifier             IR-136             The ATN ground
              Size: 2 to 7 characters     Size: 1 to 5 characters      system shall prohibit the use of ATS
                                                                       Route Designator Data Type with
                                                                       more than 5 characters length.
                 -                       Track detail                  NIR-307              The ATN ground
                                                                       system shall reject a FANS 1/A
                                                                       downlink message that contains a
                                                                       route information element with a
                                                                       Track detail element.
        [8] Route information           Route information additional
        additionalR

           [0]                          [0]
           aTWAlongTrackWaypoints       ATWalongtrackwaypointsequen    See paragraph 3.2.2.12.3 for use of
           R (1..8)                     ce (1..8)                      positionR parameter.
             PositionR                    Position                     See paragraph 3.2.2.12.4 for use of
             ATW Distance                 ATW Distance                 speed parameter.
               ATWDistancetolerance         ATWDistancetolearance      See paragraph 3.2.2.12.2 for use of
                 (plus or minus)              (plus or minus)          distance parameter.
               Distance                      Distance                  NIR-308              The ATN ground      Comment [PF216]:
                                                                       system shall reject the sending of the   PDR #360
             Speed (opt)                  Speed (opt)                  message when the level constraint is
              LevelConstraints (opt)       Level                       expressed as a level block
                Seq (2) level Or               none                    No additional interoperability
                ATW LevelS                   ATWLevelSequence (1..2)   requirement for ATWLevel/Altitude
                                                                       tolerance.
                   ATW tolerance             ATW altitude tolerance
                   LevelS                    altitude
                                                                                                  3-141



ATN Route ClearanceR            FANS 1/A Route Clearance          Interoperability Requirement
   [1] HoldatwaypointR (1..8)   Hold at waypoint :                IR-137               (deleted)
     PositionR                   Position                         See paragraph 3.2.2.12.3 for use of
                                                                  positionR parameter.
     Speed (low)                 Speed (low)
                                                                  See paragraph 3.2.2.12.4 for use of
      SEQ (2) OF levelS          ATW altitude
                                                                  speed parameter.
     Speed (high)                Speed (high)
                                                                  NIR-309              The ATN ground      Comment [PF218]:
     Direction                   Direction                        system shall reject the sending of the   PDR #360
     Degrees                     Degrees                          message when the level constraint is
                                                                  expressed as a level block
     Time (EFC time)             Time (EFC time)                                                           Comment [PF217]:
     Leg type                    Leg type                         See paragraph 3.2.2.12.6 for use of      PDR #263
                                                                  direction parameter.
                                                                  See paragraph 3.2.2.12.11 for use of
                                                                  degrees parameter.
                                                                  See paragraph 3.2.2.12.15 for use of
                                                                  leg type parameter.
   [2] Waypoint speed level R   Waypoint speed altitude (1..32): See paragraph 3.2.2.12.3 for use of
   (1..32)                                                       positionR parameter.
     PositionR                   Position                        See paragraph 3.2.2.12.4 for use of
     Speed (opt)                 Speed (opt)                     speed parameter.
     Level (opt)                 ATW altitude (opt) (1..2)       IR-310               The ATN ground       Comment [PF219]:
                                                                 system shall reject the sending of the    PDR #360
        Seq (2) level              None                          message when the level constraint is
        or                                                       expressed as a level block.
        ATW LevelS                 ATW altitude tolerance        No additional interoperability
           ATW tolerance           Altitude                      requirement for ATWLevel/Altitude
                                                                 tolerance.
            LevelS
                                                                 See paragraph 3.2.2.12.1 for use of
                                                                 level parameter.
     [3] RTA Required           RTA Required Time Arrival:        See paragraph 3.2.2.12.3 for use of
     TimeSec Arrival (1..32)                                      position parameter.
       PositionR                 Position                         See paragraph 3.2.2.12.7 for use of
       RTA timeSec                                                time/timesec parameter.
                                 RTA time
       RTA tolerance                                              No additional interoperability
                                 RTA tolerance                    requirement for time tolerance.
                                                                  Note: RTA Required TimeSec is only
                                                                  included in the ATN Route
                                                                  clearanceR Parameter.
[9] clearanceName               None.                             NIR-311              The ATN ground
                                                                  system shall reject the sending of the
                                                                  message when the optional ATN
                                                                  parameter clearanceName is
                                                                  populated.
[10] clearanceLimit             None.                             NIR-312              The ATN ground
                                                                  system shall reject the sending of the
                                                                  message when the optional ATN
                                                                  parameter clearanceLimit is
                                                                  populated.
3-142

     3.2.2.12.13         Published IdentifierR Parameter
               Table 3-45Table 3-45Table 3-45 presents the published identifier Data Type differences               Formatted: Cross-Reference
               between ATN and FANS 1/A and the impact on the ATN ground system.                                    Formatted: Cross-Reference



                                Table 3-45 ATN and FANS 1/A published identifier data type
                   ATN Published IdentifierR     FANS 1/A Published          Interoperability Requirement
                                                 Identifier
                   Published IdentifierR:        Published identifier:       None
                    Published Identifier Name:    Fix Name:                  No additional interoperability
                                                                             requirement for downlink message
                      1 à 5 characters              1 à 5 characters
                                                                             elements.
                    Latitude Longitude            Latitude Longitude (opt)
                                                                             The ATN Published Identifier part is
                                                                             equivalent to the FANS 1/A Fix Name
                                                                             parameter.
                                                                             The ATN ground system can process
                                                                             the fix name choice from the
                                                                             FANS 1/A aircraft.
                                                                             See paragraph 3.2.2.12.16 for use of
                                                                             latitude/longitude Data Type.



3.2.2.12.14    Place BearingR Distance Data Type
               Table 3-46Table 3-46Table 3-46 presents the Place Bearing Distance uplink Data Type                  Formatted: Cross-Reference
               differences between ATN and FANS 1/A and the impact on the ATN ground system.                        Formatted: Cross-Reference
                              Table 3-46 ATN and FANS 1/A place bearing distance data type
                   ATN Place Bearing Distance    FANS 1/A Place Bearing      Interoperability Requirement
                                                 Distance
                   Published identifierR         Published identifier        See paragraph 3.2.2.12.13 for use of
                   Degrees                       Degrees                     Published IdentifierR Data Type.
                   Distance                      Distance                    See paragraph 3.2.2.12.11 for use of
                                                                             degrees parameter.
                                                                             See paragraph 3.2.2.12.2 for use of
                                                                             distance parameter.



3.2.2.12.15    Leg Type Parameter
               Table 3-47Table 3-47Table 3-47 presents the leg type parameter differences between                   Formatted: Cross-Reference
               ATN and FANS 1/A and the impact on the ATN ground system.                                            Formatted: Cross-Reference
                                                                                       3-143



                       Table 3-47 ATN and FANS 1/A leg type data type
ATN Leg Type                    FANS 1/A Leg Type       Interoperability Requirement
Leg distance English:           Leg distance English:   IR-140              The ATN ground
                                                        system shall prohibit the use of Leg
 Range: 0 to 50                  Range: 1 to 99.9
                                                        Distance English with value 0.
 Resolution: 1                   Resolution: 0.1
 Unit: nautical mile             Unit: nautical mile    NIR-313             The ATN ground
                                                        system shall reject a FANS 1/A
                                                        downlink message that contains the
                                                        Leg distance English parameter that
                                                        does not respect the ATN range.
                                                        Note: Rounding is a local matter.
Leg distance Metric:            Leg distance Metric:    None.
 Range: 1 to 128                 Range: 1 to 128
 Resolution: 1                   Resolution: 1
 Unit: kilometer                 Unit: kilometer
Leg time:                       Leg time:               IR-141The ATN ground system shall
                                                        prohibit the use of Leg Time with
 Range: 1 to 10                  Range: 1 to 9.9
                                                        value 10.
 Resolution: 1                   Resolution: 0.1
 Unit: minutes                   Unit: minutes          Note: Rounding is a local matter.
3.2.2.12.16      Latitude/Longitude Parameter
                 Table 3-48Table 3-48Table 3-48 presents the Latitude/Longitude data type differences
                 between ATN and FANS 1/A and the impact on the ATN ground system.


                                Table 3-48 ATN and FANS 1/A latitude/longitude data type
        ATN Latitude Longitude              FANS 1/A Latitude            Interoperability Requirement
                                            Longitude
        Latitude:                           Latitude:                    IR-142               The ATN ground system
                                                                         shall provide both the Latitude and the
         Latitude type:                      Latitude degrees
                                                                         Longitude data variable.
            Latitude degrees, or             minutes latlon (optional)   IR-143               When receiving a message
            Latitude degrees minutes,        Latitude direction          with message element containing the data
            or                              Longitude:                   type minutes latlon and the value for latitude
                                                                         degrees is 90 or the value for longitude
            Latitude degrees minutes         Longitude degrees
                                                                         degrees is 180 and one of the minutes lat lon
            seconds                          minutes latlon (optional)   value is not 0, the ATN ground system shall
         Latitude direction                  Longitude direction         reject the message and respond per the ATS
        Longitude:                                                       INTEROP Standard, paragraph 3.3.7.6.4.1.2,
                                                                         and this document, paragraph 3.2.2.11            Comment [P220]:
         Longitude type:                                                 IR-144               When receiving a message    COMMENT #782
            Longitude degrees, or                                        with a message element containing the data
            Longitude degrees minutes, or                                type minutes latlon and the value for latitude
                                                                         degrees is 90 or the value for longitude
            Longitude degrees minutes
                                                                         degrees is 180, the ATN ground system shall
            seconds
                                                                         ignore the minutes latlon value and use the
         Longitude direction                                             latitude degrees type and/or the longitude
                                                                         degree type for further processing.
                                                                         See Latitude degrees, Latitude degrees
                                                                         minutes, Longitude degrees, and Longitude
                                                                         degrees minutes, in the following rows of this
                                                                         table for their use.
                                                                         No additional interoperability requirement for
                                                                         Latitude direction and Longitude direction.
                                                                         The Latitude and the Longitude are optional in
                                                                         the LatitudeLongitude Data Type in the ATS
                                                                         INTEROP Standard; both are required in the
                                                                         FANS 1/A INTEROP Standard.
                                                                         When ‘minutes latlon’ are omitted by the
                                                                         FANS 1/A aircraft, the ATN ground system
                                                                         can use the latitude/longitude degrees part of
                                                                         the latitude/longitude parameter in the
                                                                         latitude/longitude degrees choice of
                                                                         latitude/longitude type.
                                                                         When ‘minutes latlon’ are included by the
                                                                         FANS 1/A aircraft and the value of latitude
                                                                         degrees is not 90 and/or, longitude degrees is
                                                                         not 180, the ATN ground system can use the
                                                                         latitude/longitude parameter in the
                                                                         latitude/longitude degrees minutes choice of
                                                                         latitude/longitude type.
                                                                                                           3-145

ATN Latitude Longitude              FANS 1/A Latitude             Interoperability Requirement
                                    Longitude
Latitude degrees:                   Latitude degrees:             IR-145               The ATN ground system
                                                                  shall prohibit the use of resolutions finer than
 Range: 0 to 90                      Range: 0 to 90
                                                                  1.
 Resolution: .001                    Resolution: 1
 Unit: degrees                       Unit: degrees                See top row in this table for use of downlink
                                                                  message elements.
Latitude degrees minutes:           Latitude:                     IR-146               The ATN ground system
                                                                  shall prohibit the use of resolutions finer than
 Latitude whole degrees:             Latitude degrees
                                                                  0.1 in the Minutelatlon variable.
    Range: 0 to 89                      Range: 0 to 90
                                                                  See top row in this table for use of downlink
    Resolution: 1                       Resolution: 1
                                                                  message elements.
    Unit: degrees                       Unit: degrees
 Minutes latlon:                     Minutes latlon (optional):
    Range: 0 to 59.99                   Range: 0 to 59.9
    Resolution: .01                     Resolution: .1
    Unit: minutes                       Unit: minutes
Latitude degrees minutes seconds:   Latitude:                     IR-147              The ATN ground system
                                                                  shall prohibit the use of the LatitudeDMS
 Latitude whole degrees:
                                                                  Latitude Type choice.
    Range: 0 to 90                   Latitude degrees:
                                                                  No additional interoperability requirement for
    Resolution: 1                     Range: 0 to 90
                                                                  downlink message elements.
    Unit: degrees                     Resolution: 1
                                      Unit: degrees               This choice is not available in the FANS 1/A
 Latlon whole minutes:
                                                                  aircraft.
    Range: 0 to 59                   Minutes latlon (optional):
    Resolution: 1                     Range: 0 to 59.9
    Unit: minutes                     Resolution: .1
 Seconds latlon:                      Unit: minutes
    Range: 0 to 59
    Resolution: 1
    Unit: seconds
Longitude degrees:                  Longitude degrees:            IR-148               The ATN ground system
                                                                  shall prohibit the use of resolutions finer than
 Range: 0 to 180                     Range: 0 to 180
                                                                  1.
 Resolution: .001                    Resolution: 1
 Unit: degrees                       Unit: degrees                See top row in this table for use of downlink
                                                                  message elements.
Longitude degrees minutes:          Longitude:                    IR-149               The ATN ground system
                                                                  shall prohibit the use of resolutions finer than
 Longitude whole degrees:            Longitude degrees:
                                                                  0.1 in the Minutelatlon variable.
   Range: 0 to 179                     Range: 0 to 180
                                                                  See top row in this table for use of downlink
   Resolution: 1                       Resolution: 1
                                                                  message elements.
   Unit: degrees                       Unit: degrees
 Minutes latlon:                     Minutes latlon:
   Range: 0 to 59.99                   Range: 0 to 59.9
   Resolution: .01                     Resolution: .1
   Unit: minutes                       Unit: minutes
3-146


        ATN Latitude Longitude               FANS 1/A Latitude     Interoperability Requirement
                                             Longitude
        Longitude degrees minutes seconds:   Longitude:            IR-150              The ATN ground system
                                                                   shall prohibit the use of the LongitudeDMS
         Longitude whole degrees:             Longitude degrees:
                                                                   Longitude Type choice.
           Range: 0 to 179                      Range: 0 to 180
                                                                   No additional interoperability requirement for
           Resolution: 1                        Resolution: 1
                                                                   downlink message elements.
           Unit: degrees                        Unit: degrees
                                                                   This choice is not available in the FANS 1/A
         Latlon whole minutes:                Minutes latlon:
                                                                   aircraft.
           Range: 0 to 59                       Range: 0 to 59.9
           Resolution: 1                        Resolution: .1
           Unit: minutes
                                                Unit: minutes
         Seconds Latlon:
           Range: 0 to 59
           Resolution: 1
           Unit: seconds
3.2.2.12.17     Frequency Parameter
                The frequency parameter in CPDLC message elements is identical in ATN and
                FANS 1/A.
                Table 3-49Table 3-49Table 3-49 presents the ATN and FANS 1/A Frequency data type                         Formatted: Cross-Reference
                comparison and impact.                                                                                   Formatted: Cross-Reference
                                    Table 3-49 ATN and FANS 1/A frequency data type
        ATN Frequency                                  FANS 1/A Frequency        Interoperability Requirement
        FrequencyVHF                                   FrequencyVHF              NIR-314             The ATN ground
                                                                                 system shall only accept the
            Encoded Range: 23600-27398                     Encoded Range:
                                                                                 FrequencyVHF parameter only with
            Resolution: 1                                  117000-138000
                                                                                 the resolution equal to 0.005 MHz and
            Unit: 0.005 MHz                                Resolution: 1
                                                                                 decoded values 118.000MHz to
        Decoded Range: 118.000 MHz – 136.990               Unit: 0.001 MHz
                                                                                 136.990 MHz inclusive.
        MHz                                              Decoded Range:          NIR-315             The ATN ground
                                                         117.000 MHz – 138.000   system shall reject the use of
                                                         MHz                     FrequencyVHF data not respecting the
        Additional ATN ground system requirement:
                                                                                 ATN parameter resolution and range.
        3.3.7.6.4.3 The values contained in the data
        type frequencyVHF shall correspond to the                                No additional interoperability
        voice channel designators for VHF channels                               requirement for uplink message
        separated by 8.33khz and 25khz spacing, as                               elements.
        specified by the relevant provisions in ICAO                             Whether only input with the permitted
        Annex 10, Volume V, Chapter 4.1 (bis).                                   resolution is enabled or a rounding
                                                                                 mechanism is used is a local matter.


        FrequencyHF:                                   FrequencyHF:            None.
        Encoded Range: 2850 – 28000                    Encoded Range: 2850 –
        Resolution: 1                                  28000
        Unit: Kilohertz                                Resolution: 1
        Decoded Range: 2850 kHz – 28000 kHz            Unit: Kilohertz
                                                       Decoded Range: 2850 kHz
                                                       – 28000 kHz
        FrequencyUHF:                                  FrequencyUHF:             NIR-316             The ATN ground
                                                                                 system shall only accept the
        Encoded Range: 9000-15999                      Encoded Range: 225000-
                                                                                 FrequencyUHF parameter only with
        Resolution: 0.025                              399975
                                                                                 the resolution equal to 0.025 MHz and   Comment [PF221]:
        Unit: Megahertz                                Resolution: 0.001         decoded values 225.000MHz to            COMMENT #1226
        Decoded Range: 225.000 MHz - 399.975           Unit: Megahertz           399.975 MHz inclusive.
        MHz                                            Decoded Range: 225.000
                                                       MHz - 399.975 MHz
        FrequencySatChannel:                           FrequencySatChannel:      None.
        NumericString( SIZE(12) )                      NumericString( SIZE(12)
                                                       )
                       Table 3-50 ATN frequency data type sent in FANS UM169 Free Text
               ATN frequency                Free Text Format                Interoperability Requirement
               FrequencyVHF - 118.000       nnn.nnn                         NIR-317              When including an
               MHz – 136.990 MHz                                            ATN [frequency] parameter in a FANS
               Or                                                           1/A message element UM169, the ATN
                                                                            ground system shall include an integer
               FrequencyHF: 2850 kHz –      nnnnn                           converted to a string of characters.
               28000 kHz
               Or
               FrequencyUHF: 225.000 MHz
               - 399.975 MHz                nnn.nnn
               Or
               FrequencySatChannel:Numeri   12 numerical characters
               cString(SIZE(12) )



3.2.2.12.18    Code Parameter
               The code parameter in CPDLC message elements is identical in ATN and FANS 1/A.
               Table 3-51Table 3-51Table 3-51 presents ATN and FANS 1/A Code data type                                Formatted: Cross-Reference
               comparison and impact.                                                                                 Formatted: Cross-Reference
               Note:    See paragraph 3.2.2.9 for processing downlink message elements containing
                        the following parameter/data type, which is not supported by the ATN ground
                        system:
                            ATN ‘code’ and corresponding FANS 1/A ‘beaconcode’ in downlink
                             message elements.


                                  Table 3-51 ATN and FANS 1/A code data type
               ATN Code Parameter     FANS 1/A Code Parameter         Interoperability Requirement
               Code                   Beaconcode                      None.
                CodeOctaldigit         Beaconcodeoctaldigit           The naming is different. Range and resolution
                                                                      are identical.



3.2.2.12.19    Departure clearanceR Parameter
               Table 3-43 presents the Departure ClearanceR Parameter data type differences between
               ATN and FANS 1/A and the impact on the ATN ground system. Note the ATN
               Departure clearanceR parameter is only used in UM73R and is accommodated by FANS
               1/A message elements UM80 CLEARED [routeClearance], UM169 [freeText], UM123
               SQUAWK [code], UM158 ATIS [atis code], and UM19 MAINTAIN [altitude].


                         Table 3-52 ATN and FANS 1/A Departure clearanceR data type
     ATN Departure ClearanceR     FANS 1/A Parameter                      Interoperability Requirement
     Parameter
3-149


        ATN Departure ClearanceR        FANS 1/A Parameter                    Interoperability Requirement
        Parameter
        [0] clearedFrom                 UM80 CLEARED [routeClearance]         NIR-318             The ATN ground system shall
          Airport                                     airportDeparture        convert the ATN clearedFrom: Airport parameter to
                                                                              a FANS 1/A UM80 CLEARED [routeClearance]
                                                                              using the airportDeparture parameter.
        [0] clearedFrom                 None.                                 NIR-319             The ATN ground system shall
          Location                                                            prohibit sending the ATN clearedFrom: Location
                                                                              parameter to a FANS 1/A Aircraft.
        [1] clearedTo                     UM80 CLEARED [routeClearance]       NIR-320             The ATN ground system shall
          PositionR                                      airportDestination   convert the ATN clearedTo parameter to a FANS
                                                                              1/A UM80 CLEARED [routeClearance] using the
             PublishedIdentifier R                                            airportDestination parameter.
                  PublishedIdentifierName                                     NIR-321             The ATN ground system shall
                                                                              only allow sending clearedTo as Airport.
        [2] departureRoute              UM80 CLEARED [routeClearance]    NIR-322            The ATN ground system shall
          departureRouteData                          departureProcedure convert the ATN departureRoute:
                                                                         DepartureRouteData: departureProcedureSID
            departureProcedureSID                                        parameter to a FANS 1/A UM80 CLEARED
              procedureNameR                                             [routeClearance] using the departureProcedure
                                                                         parameter.
                                                                              NIR-323             (deleted)
        [2] departureRoute              UM169”Then As Filed”                  NIR-324             The ATN ground system shall
          departureRouteData                                                  convert the ATN ‘thenAsFiledIndicator’ parameter
                                                                              to a FANS 1/A UM169 [free text] message element
            thenAsFiledIndicator                                              with the text “Then As Filed”.
        [2] departureRoute              UM169”Route As Filed”                 NIR-325             The ATN ground system shall
          routeAsFiledIndicator                                               convert the ATN ‘routeAsFiledIndicator’ parameter
                                                                              to a FANS 1/A UM169 [free text] message element
                                                                              with the text “Route As Filed”.
        [3] departureLevels             UM19 MAINTAIN [altitude]              NIR-326            The ATN ground system shall
          maintainInitialLevel                                                convert the ATN departureLevels:
                                                                              maintainLevel:singleLevel parameter to a FANS
            level Single                                                      1/A UM19 MAINTAIN [altitude] message
                                                                              element.
                                                                              See paragraph 3.2.2.12.1 for use of level parameter.
        [3] departureLevels             UM169 “Expect Level [expectLevel]”    NIR-327             The ATN ground system shall
          expectLevel                                                         convert the ATN departureLevels: expectLevel:
                                                                              level single parameter to a FANS 1/A UM169 [free
            level single                                                      text] message element.
                                                                              NIR-328             The ATN ground system shall
                                                                              convert the ATN departureLevels: expectLevel
                                                                              parameter to a character string.
        [4] departureSpeed              UM169 “Departure Speed                NIR-329           The ATN ground system shall
          speed                         [departureSpeed]”                     convert the ATN departureSpeed:speed parameter
                                                                              to a FANS 1/A UM169 [free text] message
                                                                              element.
                                                                              NIR-330           The ATN ground system shall
                                                                              convert the ATN departureSpeed parameter to a
                                                                              character string.
     ATN Departure ClearanceR           FANS 1/A Parameter               Interoperability Requirement
     Parameter
     [5] departureHeading               UM169 “Departure Heading         NIR-331             The ATN ground system shall
                                        [departureHeading]”              convert the ATN departureHeading parameter to a
                                                                         FANS 1/A UM169 [free text] message element.
                                                                         NIR-332             The ATN ground system shall
                                                                         convert the ATN departureHeading: degrees
                                                                         parameter to a character string.
     [6] noDelayExpectedIndicator       UM169”No Delay Expedcted”        NIR-333           The ATN ground system shall
                                                                         convert the ATN ‘noDelayExpectedIndicator’
                                                                         parameter to a FANS 1/A UM169 [free text]
                                                                         message element with the text “No Delay
                                                                         Expected”.
     [7] additionalInformation          UM80 CLEARED [routeClearance]    NIR-334            The ATN ground system shall
       arrivalProcedure                               procedureArrival   convert the ATN additionalInformation:
                                                                         arrivalProcedure:procedureNameR parameter to a
         procedure Name R                                                FANS 1/A UM80 CLEARED [routeClearance]
                                                                         using the procedureArrival parameter.
     [7] additionalInformation          UM169”[freeText]”                NIR-335            The ATN ground system shall
       Special Instruction                                               convert the ATN
                                                                         additionalInformation:specialInstructions parameter
                                                                         to a FANS 1/A UM169 [free text] message
                                                                         element.
     [8] code                           UM123 SQUAWK [code]              NIR-336           The ATN ground system shall
                                                                         convert the ATN code parameter to a FANS 1/A
                                                                         UM123 SQUAWK [code] parameter.
     [9] atis                           UM158 ATIS [atis code]           NIR-337            The ATN ground system shall
                                                                         convert the ATN atis parameter to a FANS 1/A
                                                                         UM158 ATIS [code] parameter.
     [10] departureFrequency            UM169 “Departure Frequency       NIR-338           The ATN ground system shall
                                        [departureFrequency]”            convert the ATN departureFrequency parameter to
                                                                         a FANS 1/A UM169 [free text] message element.

                                                                         NIR-339             The ATN ground system shall
                                                                         convert the ATN departureFrequency parameter to
                                                                         a character string.




3.2.2.12.20      Named Instruction / Procedure Name Parameter
                 The named instruction parameter in ATN contains the ATN procedure name and
                 clearance name parameters. FANS 1/A does not have a parameter compatible with
                 clearance name.
                 NamedInstruction ::= CHOICE                                                                                   Comment [P222]:
                                                                                                                               COMMENT #970, PDR #83
                                    {
                                    clearanceName                    [0] ClearanceName,
                                    procedureName                    [1] ProcedureNameR,
3-151


                                  }
              NIR-340         The ATN ground system shall reject a message containing the named
              instruction parameter where the clearance name choice is used.
              The procedure name parameter in CPDLC message elements is comparable in ATN and
              FANS 1/A.
              Table 3-52 presents the ATN and FANS 1/A procedure name data type comparison and
              impact.
                                Table 3-53 ATN and FANS 1/A Procedure Name data type
              ATN Procedure NameR FANS 1/A Procedure Name                Interoperability Requirement
              Parameter           Parameter
                Runway (opt)             none                            NIR-341            The ATN ground system
                                                                         shall ignore the runway when present in the
                                                                         procedure nameR variable.
                ProcedureType             ProcedureType                  None.
                Procedure:                Procedure:                     NIR-342              The ATN ground system
                                                                         shall prohibit sending the Procedure data type
                String(1..20)             String(1..6)
                                                                         with a string length greater than 6.
                ProcedureTransition       ProcedureTransition            None.
                Additional Procedure      none                           NIR-343          The ATN ground system
                Information (opt)                                        shall ignore the additional procedure
                                                                         information when present in the procedure
                                                                         nameR variable.



3.2.2.12.21   Altimeter Parameter
              The altimeter parameter in CPDLC message elements is equivalent in ATN and FANS
              1/A.
              Table 3-54Table 3-54Table 3-54 presents the ATN and FANS 1/A altimeter data type
              comparison and impact.


                                   Table 3-54 ATN and FANS 1/A Altimeter data type
              ATN                           FANS 1/A                        Interoperability Requirement
              Altimeter Parameter           Altimeter Parameter
                altimeterEnglish:               altimeterEnglish:           None.
                  Range: 2200-3200                Range: 2200-3200
                  Resolution: 0.01                Resolution: 0.01
                  Unit: Inches Mercury            Unit: Inches Mercury
                altimeterMetric:                altimeterMetric:            None.
                  Range: 7500-12500               Range: 7500-12500
                  Resolution: 0.1                 Resolution: 0.1
                  Unit: Hectopascal               Unit: Hectopascal
                      Table 3-55 ATN altimeter data type sent in FANS UM169 Free Text
              ATN Altimeter code               Free Text Format           Interoperability Requirement
                altimeterEnglish: 22.00-                                  NIR-344              When including an
                32.00 Inches Mercury             “nn.nn INHG”             ATN [altimeter] parameter in a FANS
                                                                          1/A message element UM169, the ATN
                                                                          ground system shall include an integer
                Or                               Or                       converted to a string of characters

                altimeterMetric: 750.0-          “nnnn.n HP”
                1250.0 Hectopascal



3.2.2.12.22   Atis Code Parameter
              The atis code parameter in CPDLC message elements is equivalent in ATN and FANS
              1/A.
              Table 3-56Table 3-56Table 3-56 presents the ATN and FANS 1/A atis code data type
              comparison and impact.


                                 Table 3-56 ATN and FANS 1/A Atis Code data type
              ATN                          FANS 1/A               Interoperability Requirement
              Atis Code Parameter          Atis Code Parameter
                ATISCode:                   ATISCode:             None.
                String(1)                   String(1)




                       Table 3-57 ATN atis code data type sent in FANS UM169 Free Text
              ATN ATIS code                    Free Text Format           Interoperability Requirement
                ATIS code                        1 char string            NIR-345           When including an
                                                                          ATN [atis code] parameter in a FANS
                                                                          1/A message element UM169, the ATN
                                                                          ground system shall include it as a 1
                                                                          character string.




3.2.2.12.23   To/From Parameter
              The to/from parameter in CPDLC message elements is equivalent in ATN and FANS
              1/A.
              Table 3-58Table 3-58Table 3-58 presents the ATN and FANS 1/A To/From data type
              comparison and impact.
3-153


                                      Table 3-58 ATN and FANS 1/A To/From data type
                ATN                          FANS 1/A                      Interoperability Requirement
                To/From Parameter            To/From Parameter
                  To                          To                           None.
                  From                        From                         None.



3.2.2.12.24    Position ReportR Parameter
               The Position Report parameter in CPDLC message elements is comparable in ATN and
               FANS 1/A.
               Table 3-59Table 3-59Table 3-59 presents the ATN and FANS 1/A position report data
               type comparison and impact.


                           Table 3-59 ATN and FANS 1/A position report advanced data type
              ATN Position ReportR              FANS 1/A Position            Interoperability Requirement
              Parameter                         Parameter
              [0] Position Current              Position Current             See paragraph 3.2.2.12.3 for use of
                PositionR                        Position                    positionR parameter.

              [1] Time at Position Current      Time at Position Current     See paragraph 3.2.2.12.7 for use of the
                Timesec                           Time                       time/timesec parameter.

              [2] LevelS                        Altitude                     See paragraph 3.2.2.12.1 for use of level
                                                                             parameter.
              [3] Fix Next                      Fix Next                     See paragraph 3.2.2.12.3 for use of position
                PositionR                         Position                   parameter.

              [4] Time ETA at Fix Next          Time ETA at Fix Next         See paragraph 3.2.2.12.7 for use of the
                Timesec                           Time                       time/timesec parameter.

              [5] Fix Next Plus One             Fix Next Plus One            See paragraph 3.2.2.12.3 for use of position
                PositionR                         Position                   parameter.

              [6] Time ETA at Destination       Time ETA at Destination      See paragraph 3.2.2.12.7 for use of the
                Timesec                           Time                       time/timesec parameter.

              [7] Remaining Fuel                   Remaining Fuel            See paragraph 3.2.2.12.25 for use of the
                                                                             remaining fuel parameter.
              [8] Temperature                      Temperature               See paragraph 0 for use of the temperature
                                                                             parameter.
              [9] Winds                            Winds                     None.
              [10] TurbulenceR                     Turbulence                See paragraph 0 for use of the turbulence
                                                                             parameter.
              ATN Position ReportR           FANS 1/A Position        Interoperability Requirement
              Parameter                      Parameter
              [11] Icing                      Icing                   In FANS 1/A Icing selection [0] is trace and
                                                                      selection [0] is reserved in ATN.
                                                                      NIR-346               The     ATN     ground
                                                                      system shall ignore any icing parameter of
                                                                      trace.
                                                                      NIR-347               The     ATN     ground
                                                                      system shall send an error message to the
                                                                      aircraft indicating that trace is an
                                                                      unacceptable section for icing in an ATN
                                                                      system.
              [12] Speed                      Speed                   See paragraph 3.2.2.12.4 for use of speed
                                                                      parameter.
              [13] Speed Ground Type         Speed Ground             See paragraph 3.2.2.12.4 for use of speed
                Speed Ground                   Speed Ground           ground parameter.

              [14] Vertical Change           Vertical Change          See paragraph 3.2.2.12.29 for use of the
                Vertical Change               Vertical Change         vertical change parameter.

              [15] Track Angle               Track Angle              See paragraph 3.2.2.12.11 for use of
                Degrees                        Degrees                degrees parameter.

              [16] Heading                   True Heading             The naming is different.
                Degrees                        Degrees                See paragraph 3.2.2.12.11 for use of
                                                                      degrees parameter.
              [17] Distance                   Distance                See paragraph 3.2.2.12.5 for use of distance
                                                                      parameter.
              [18] Humidity                   Supplementary           FANS 1/A uses free text for the
                                              Information             supplementary information and ATN uses
                                                                      the Humidity parameter.
                                                                      NIR-348            The      ATN      ground
                                                                      system shall disregard any information
                                                                      entered in the supplementary information
                                                                      parameter.
                                                                      Note: Humidity will not be reported for
                                                                      FANS 1/A Aircraft.
              [19] Reported Waypoint         Reported Waypoint        See paragraph 3.2.2.12.3 for use of position
              Position                       Position                 parameter.
                PositionR                      Position
              [20] Reported Waypoint Time    Reported Waypoint Time   See paragraph 3.2.2.12.7 for use of the
                Timesec                       Time                    time/timesec parameter.

              [21] Reported Waypoint Level    Reported Waypoint       See paragraph 3.2.2.12.1 for use of level
                LevelS                        Altitude                parameter.
                                                      Altitude



3.2.2.12.25    Remaining Fuel Parameter
               The remaining fuel parameter in CPDLC message elements is equivalent in ATN and
               FANS 1/A.
3-155


              Table 3-60Table 3-60Table 3-60 presents the ATN and FANS 1/A remaining fuel data       Formatted: Underline
              type comparison and impact.                                                            Formatted: Underline
                           Table 3-60          ATN and FANS 1/A Remaining Fuel data type
              ATN Remaining Fuel     FANS 1/A Remaining Fuel   Interoperability Requirement
              Parameter              Parameter
                Time                    Time                   None.



3.2.2.12.26   Persons On Board / Remaining Souls Parameter
              The persons on board parameter in ATN CPDLC messages is equivalent to the remaining
              souls parameter in FANS 1/A CPDLC messages. Both parameter versions have the same
              data type and resolution.
              Table 3-61Table 3-61Table 3-61 presents the ATN and FANS 1/A persons on board data     Formatted: Underline
              type comparison and impact.                                                            Formatted: Underline
                       Table 3-61              ATN and FANS 1/A Persons on Board data type
              ATN Persons on Board   FANS 1/A Remaining Souls Interoperability Requirement
              Parameter              Parameter
                PersonsOnBoard          RemainingSouls         None.



3.2.2.12.27   Version Number Parameter
              The version number parameter in CPDLC message elements is equivalent in ATN and
              FANS 1/A.
              Table 3-62Table 3-62Table 3-62 presents the ATN and FANS 1/A version number data       Formatted: Underline
              type comparison and impact.                                                            Formatted: Underline
                       Table 3-62              ATN and FANS 1/A Version Number data type
              ATN Version Number     FANS 1/A Version Number   Interoperability Requirement
              Parameter              Parameter
                VersionNumber           VersionNumber          None.



3.2.2.12.28   Temperature Parameter
              The temperature parameter in CPDLC message elements in ATN requires a different
              unit, range, and resolution than the temperature parameter in CPDLC message elements
              in FANS 1/A.
              Table 3-63Table 3-63Table 3-63 presents the ATN and FANS 1/A temperature data type
              comparison and impact.
                                 Table 3-63 ATN and FANS 1/A temperature data type
       ATN Temperature Parameter       FANS 1/A temperature Parameter       Interoperability Requirement
         Temperature                     Temperaturec                       None.
               -Unit: Degree Celsius           -Unit: Degree Centigrade     The temperaturec parameter is never
               -Range: (-100…100)              -Range: (-80…47)             sent as an uplink.
               -Resolution: 1                  -Resolution: 1
                                         Temperaturef                       The temperaturef parameter is never
                                                                            sent as an uplink.
                                                -Unit: Degree Fahrenheit
                                                                            NIR-349             The ATN ground
                                                -Range: (-105…150)          system shall convert the FANS 1/A
                                         -Resolution: 1                     parameter temperaturef Fahrenheit
                                                                            temperature to the ATN temperature in
                                                                            Celsius when receiving a downlink
                                                                            from a FANS 1/A aircraft.
                                                                            Note: The FANS 1/A range in
                                                                            Fahrenheit is within the ATN range in
                                                                            Celsius.
                                                                            No additional interopability
                                                                            requirements for uplink.



3.2.2.12.29     Vertical Change Parameter
                The vertical change sequenced parameter in ATN CPDLC messages is identical to the
                vertical change parameter in the FANS 1/A CPDLC messages.
                Table 3-64Table 3-64Table 3-64 presents the ATN and FANS 1/A vertical change data
                type comparison and impact.
                Note: Differences in the vertical rate parameter must be accounted for when the vertical
                change parameter is used. See paragraph Error! Reference source not found.Erreur !
                Source du renvoi introuvable.Erreur ! Source du renvoi introuvable. for use of the
                vertical rate parameter.
                         Table 3-64              ATN and FANS 1/A Vertical Change data type
                 ATN Vertical Change   FANS 1/A Vertical Change     Interoperability Requirement
                 Parameter             Parameter
                  VerticalDirection      VerticalDirection          None.
                  VerticalRate           VerticalRate               See paragraph Error! Reference source not
                                                                    found.Erreur ! Source du renvoi introuvable.
                                                                    for use of the vertical rate parameter.



3.2.2.12.30     Vertical Direction Parameter
                The vertical direction parameter in ATN CPDLC messages is identical to the vertical
                direction parameter in the FANS 1/A CPDLC messages.
                Table 3-65Table 3-65Table 3-65 presents the ATN and FANS 1/A Vertical Direction                     Formatted: Underline
                data type comparison and impact.                                                                    Formatted: Underline
3-157


                          Table 3-65                   ATN and FANS 1/A Vertical Direction data type
                 ATN Vertical Direction   FANS 1/A Vertical          Interoperability Requirement
                 Parameter                Direction Parameter
                   Up                      Up                        None.
                   Down                    Down                      None.




3.2.2.12.31     Speed Schedule Parameter
                The Speed Schedule parameter is a sequence of two speed parameters.
NIR-350         The ATN ground system shall convert the Speed Schedule parameter into two speed parameters to
accommodate a FANS 1/A aircraft.
                See paragraph 3.2.2.12.4 for use of speed parameter.

3.2.2.12.32     Turbulence Parameter
                The turbulence parameter in ATN CPDLC messages is simular to the turbulence
                parameter in the FANS 1/A CPDLC messages.
                Table 3-65Table 3-65Table 3-65 presents the ATN and FANS 1/A Turbulence data type                    Formatted: Underline
                comparison and impact.                                                                               Formatted: Underline
                          Table 3-66                   ATN and FANS 1/A Turbulence data type
                 ATN Turbulence           FANS 1/A Turbulence        Interoperability Requirement
                 Enhanced Parameter       Parameter
                   Light (0)               Light (0)                 None.
                   Moderate (1)            Moderate (1)              None.
                   Severe (2)              Severe (2)                None.
                   Extreme (3)             No equivalent             The Turbulence parameter is never sent as an
                                                                     uplink.
                                                                     Note: The FANS 1/A range is within the ATN
                                                                     range.
                                                                     No additional interopability requirements for
                                                                     downlink.




3.2.2.12.33     Time/RTATimesec Parameter
                The RTATimesec parameter in ATN CPDLC messages is comparable to the time
                parameter in FANS 1/A CPDLC messages.
                Table 3-56 presents the time/RTATimesec Data Type differences between ATN and
                FANS 1/A and the impact on the ATN ground system.
                               Table 3-67 ATN and FANS 1/A RTA Time data type
             ATN RTATimesec              FANS 1/A Time             Interoperability Requirement
             time                         time                     See paragraph 3.2.2.12.7 for use of the
               Timesec                                             time/timesec parameter.
             RTATolerance (Optional)     None.                     NIR-351            The ATN ground
                                                                   system shall prohibit the sending of a
              Range: 0.1 to 15.0
                                                                   message containing a RTATimeSec to a
              Resolution: 0.1
                                                                   FANS     1/A     aircraft   when    an
              Unit: Minute
                                                                   RTATolerance is specified.




3.2.2.13     ATN and FANS 1/A Message Element Pairing
3.2.2.13.1   Downlink Message Elements
             Table 3-68Table 3-68Table 3-68 presents the Downlink message elements with Y                    Formatted: Cross-Reference
             Response attribute together with the expected responses and the impact on the ATN               Formatted: Cross-Reference
             ground system to support the FANS 1/A message elements.
             Note:       Only message elements that are in scope of this document per paragraph 1.2.1
                         are listed. See paragraph 3.2.2.9 for processing downlink message elements
                         that are not supported by the ATN ground system.


             See paragraph 3.2.2.8 for use of uplink message elements.
                                  Table 3-68 Suggested ATN downlink message elements with Y response attribute
ATN Message   ATN Response Message                                  FANS 1/A Msg     FANS 1/A Response Message
Element                                                             Element
              UM0 UNABLE                                            All DMs below    UM0 UNABLE
              UM1 STANDBY                                           responded with   UM1 STANDBY
              UM2 REQUEST DEFERRED                                  UNABLE           UM2 REQUEST DEFERRED                                  Comment [PF223]:
              UM162 MESSAGE NOT SUPPORTED BY THIS ATC UNIT                           UM169 ‘MESSAGE NOT SUPPORTED BY THIS ATC UNIT’        PDR #12
              UM211 REQUEST FORWARDED                                                UM169 ‘REQUEST FORWARDED’
                                                                                                                                           Comment [PF224]:
              UM218 REQUEST ALREADY RECEIVED                                         UM169 ‘REQUEST ALREADY RECEIVED’                      PDR #357
              UM234 FLIGHT PLAN NOT HELD                                             UM169 ‘FLIGHT PLAN NOT HELD’
              UM159 ERROR [error information] + UM 183 [freetext]                    UM159 ERROR [error information] + UM 169 [freetext]
              UM237 REQUEST AGAIN WITH NEXT ATC UNIT                                 UM169 ‘REQUEST AGAIN WITH NEXT ATC UNIT’
              UM3 ROGER                                             All DMs below    UM3 ROGER
              UM1 STANDBY                                           responded with   UM1 STANDBY
              UM159 ERROR [error information] + UM 183 [freetext]   ROGER            ERROR [error information] + UM 169 [freetext]
ATN Message        ATN Response Message                                    FANS 1/A Msg     FANS 1/A Response Message
Element                                                                    Element
DM9 REQUEST        UM7 EXPECT HIGHER AT [time]                             DM6 REQUEST      UM7 EXPECT CLIMB AT [time]
CLIMB TO [level]   UM8R EXPECT HIGHER AT [positionR]                       [altitude]       UM8 EXPECT CLIMB AT [position]
                   UM19 MAINTAIN [level]                                                    UM19 MAINTAIN [level]
                   UM20 CLIMB TO [level]                                                    UM20 CLIMB TO [level]
                   UM21 AT TIME [time] CLIMB TO [level]                    DM7 REQUEST      UM21 AT [time] CLIMB TO [level]
                                                                           BLOCK
                   UM22R AFTER PASSING [position ATW] CLIMB TO [level]                      UM22 AT [position] CLIMB TO [level]
                                                                           [altitude] TO
                   UM26 CLIMB TO REACH [level] AT OR BEFORE TIME [time]    [altitude]       UM26 CLIMB TO REACH [level] BY [time]
                   UM27R CLIMB TO REACH [level] BEFORE PASSING [position                    UM27 CLIMB TO REACH [level] BY [position]
                   ATW]
                   UM0 UNABLE + UM261 REQUESTED LEVEL IS NOT               DM9 REQUEST      UM0 UNABLE + UM169 ‘REQUESTED LEVEL IS NOT
                   AVAILABLE                                               CLIMB TO         AVAILABLE’
                   UM0 UNABLE + UM262 HIGHER LEVEL IS NOT                  [altitude]       UM0 UNABLE + UM169 ‘HIGHER LEVEL IS NOT
                   AVAILABLE                                                                AVAILABLE’
DM10 REQUEST       UM9 EXPECT LOWER AT [time]                              DM6 REQUEST      UM9 EXPECT DESCENT AT [time]
DESCEND TO         UM10R EXPECT LOWER AT [positionR]                       [altitude]       UM10 EXPECT DESCENT AT [position]
[level]            UM19 MAINTAIN [level]                                                    UM19 MAINTAIN [level]
                   UM23 DESCEND TO [level]                                                  UM23 DESCEND TO [level]
                   UM24 AT OR AFTER TIME [time] DESCEND TO [level]         DM7 REQUEST      UM24 AT [time] DESCEND TO [level]
                                                                           BLOCK
                   UM25R AT [position ATW] DESCEND TO [level]                               UM25 AT [position] DESCEND TO [level]
                                                                           [altitude] TO
                   UM28 DESCEND TO REACH [level] AT OR BEFORE TIME         [altitude]       UM28 DESCEND TO REACH [level] BY [time]
                   [time]
                   UM29R DESCEND TO REACH [level] BY [position ATW]                         UM29 DESCEND TO REACH [level] BY [position]
                   UM0 UNABLE+ UM261 REQUESTED LEVEL IS NOT                DM10             UM0 UNABLE + UM169 ‘REQUESTED LEVEL IS NOT
                   AVAILABLE                                               REQUEST          AVAILABLE’
                   UM0 UNABLE+ UM263 LOWER LEVEL IS NOT AVAILABLE          DESCEND TO       UM0 UNABLE + UM169 ‘LOWER LEVEL IS NOT
                                                                           [altitude]       AVAILABLE’
DM11R AT           UM22R AFTER PASSING [position ATW] CLIMB TO [level]     DM11 AT          UM22 AT [position] CLIMB TO [level]           Comment [PF225]:
[positionR]        UM25R AT [position ATW] DESCEND TO [level]              [position]       UM25 AT [position] DESCEND TO [level]         PDR #280 8)
REQUEST [level]    UM0 UNABLE + UM261 REQUESTED LEVEL IS NOT               REQUEST          UM0 UNABLE + UM169 ‘REQUESTED LEVEL IS NOT
                   AVAILABLE                                               CLIMB TO         AVAILABLE’
                   UM0 UNABLE + UM262 HIGHER LEVEL IS NOT                  [altitude]       UM0 UNABLE + UM169 ‘HIGHER LEVEL IS NOT
                   AVAILABLE                                                                AVAILABLE’
                   UM0 UNABLE + UM263 LOWER LEVEL IS NOT                   DM12 AT          UM0 UNABLE + UM169 ‘LOWER LEVEL IS NOT
                   AVAILABLE                                               [position]       AVAILABLE’
                                                                           REQUEST
                                                                           DESCENT TO
                                                                           [altitude]
                                                                                                                                          Comment [PF226]:
DM13 AT TIME       UM21 AT OR AFTER TIME [time] CLIMB TO [level]           DM13 AT [time]   UM21 AT [time] CLIMB TO [level]               PDR #263, PDR #280 8)
3-161


ATN Message             ATN Response Message                                          FANS 1/A Msg       FANS 1/A Response Message
Element                                                                               Element
[time] REQUEST          UM24 AT OR AFTER TIME [time] DESCEND TO [level]               REQUEST            UM24 AT [time] DESCEND TO [level]                           Comment [TE227]: 263 266 134
[level]                 UM0 UNABLE+UM261 REQUESTED LEVEL IS NOT                       CLIMB TO           UM0 UNABLE + UM169 ‘REQUESTED LEVEL IS NOT
                        AVAILABLE                                                     [altitude]         AVAILABLE’
                        UM0 UNABLE+UM 262 HIGHER LEVEL IS NOT AVAILABLE                                  UM0 UNABLE + UM169 ‘HIGHER LEVEL IS NOT
                        UM0 UNABLE+UM263 LOWER LEVEL IS NOT AVAILABLE                 DM14 AT [time]     AVAILABLE’
                                                                                      REQUEST            UM0 UNABLE + UM169 ‘LOWER LEVEL IS NOT
                                                                                      DESCENT TO         AVAILABLE’
                                                                                      [altitude]
DM15 REQUEST            UM64R OFFSET [specified distance] [direction side] OF ROUTE   DM15               UM64 OFFSET [specified distance] [direction] OF ROUTE
OFFSET [specified       UM65R AT [position ATW] OFFSET [specified distance]           REQUEST            UM65 AT [position] OFFSET [distanceoffset] [direction] OF
distance] [direction]   [direction side] OF ROUTE                                     OFFSET             ROUTE
OF ROUTE                UM66R AT TIME [time] OFFSET [specified distance] [direction   [distanceoffset]   UM66 AT [time] OFFSET [distanceoffset] [direction] OF
                        side] OF ROUTE                                                [direction] OF     ROUTE
                                                                                      ROUTE

DM18 REQUEST            UM100R EXPECT SPEED CHANGE AT [time]                          DM18               UM169 ‘EXPECT SPEED CHANGE AT [time]’
SPEED [speed]           UM101R EXPECT SPEED CHANGE AT [positionR]                     REQUEST            UM169 ‘EXPECT SPEED CHANGE AT [published identifier
                                                                                      SPEED [speed]      name]’
                        UM102R EXPECT SPEED CHANGE AT [level single]                                     UM169 ‘EXPECT SPEED CHANGE AT [altitude]’
                        UM106 MAINTAIN [speed]                                                           UM106 MAINTAIN [speed]
                        UM107 MAINTAIN PRESENT SPEED                                                     UM107 MAINTAIN PRESENT SPEED
                        UM108 MAINTAIN [speed] OR GREATER                                                UM108 MAINTAIN [speed] OR GREATER
                        UM109 MAINTAIN [speed] OR LESS                                                   UM109 MAINTAIN [speed] OR LESS
                        UM116 RESUME NORMAL SPEED                                                        UM116 RESUME NORMAL SPEED
                        UM222 NO SPEED RESTRICTION                                                       UM169 ‘NO SPEED RESTRICTION’

DM21R REQUEST           UM117R CONTACT [unitid] [frequency]                          DM20                UM117 CONTACT [unit name] [frequency]
VOICE CONTACT           UM118R AT [position ground air] CONTACT [unitid] [frequency] REQUEST             UM118 AT [position] CONTACT [unit name] [frequency]
[frequencyR]            UM119R AT [time] CONTACT [unitid] [frequency]                VOICE               UM119 AT [time] CONTACT [unit name] [frequency]
                                                                                     CONTACT

                                                                                      DM21
                                                                                      REQUEST
                                                                                      VOICE
                                                                                      CONTACT
                                                                                      [frequency]
ATN Message           ATN Response Message                                          FANS 1/A Msg       FANS 1/A Response Message
Element                                                                             Element
DM22R REQUEST         UM74R PROCEED DIRECT TO [position ATW]                        DM22               UM74 PROCEED DIRECT TO [position]
DIRECT TO             UM76R AT TIME [time] PROCEED DIRECT TO [positionR]            REQUEST            UM76 AT [time] PROCEED DIRECT TO [position]
[positionR]           UM77R AT [position ATW] PROCEED DIRECT TO [position R]        DIRECT TO
                      UM78R AT [level single] PROCEED DIRECT TO [positionR]         [position]       UM77 AT [position] PROCEED DIRECT TO [position]
                      UM96 CONTINUE PRESENT HEADING                                                  UM78 AT [level] PROCEED DIRECT TO [position]
                      UM190 FLY HEADING [degrees]                                                    UM96 CONTINUE PRESENT HEADING
                                                                                                     UM190 FLY HEADING [degrees]
DM23R REQUEST         UM81R CLEARED [procedure nameR]                               DM23             UM81 CLEARED [procedure name]
[named instruction]   UM84R AT [positionR] CLEARED [procedure nameR]                REQUEST          UM84 AT [position] CLEARED [procedureName]
                      UM99R EXPECT [named instruction]                              [procedure name] UM99 EXPECT [procedurename]
DM24R REQUEST         UM79R CLEARED TO [positionR] VIA [route clearanceR]           DM24           UM79 CLEARED TO [position] VIA [routeClearance]
CLEARANCE             UM80R CLEARED [route clearanceR]                              REQUEST [route UM80 CLEARED [route clearance]
[route clearanceR]    UM83R AT [position ATW] CLEARED [route clearanceR]            clearance]     UM83 AT [position] CLEARED [routeClearance]

DM25 REQUEST          UM314 EXPECT [clearance type=departure][assigned time0]       DM25               UM73 [preDepartureClearance] [timeDepartureEDCT]
[clearance                                                                          REQUEST
type=none]                                                                          CLEARANCE
CLEARANCE
DM27R REQUEST         UM64R OFFSET [specified distance] [direction side] OF ROUTE   DM27               UM64 OFFSET [distanceoffset] [direction] OF ROUTE
WEATHER               UM65R AT [position ATW] OFFSET [specified distance]           REQUEST            UM65 AT [position] OFFSET [distanceoffset] [direction] OF
DEVIATION UP          [direction side] OF ROUTE                                     WEATHER            ROUTE
TO [lateral           UM66R AT TIME [time] OFFSET [specified distance] [direction   DEVIATION UP       UM66 AT [time] OFFSET [distanceoffset] [direction] OF
deviation] OF         side] OF ROUTE                                                TO                 ROUTE
ROUTE                 UM82R CLEARED TO DEVIATE UP TO [lateral deviation] OF         [distanceoffset]   UM82 CLEARED TO DEVIATE UP TO [specified distance]
                      ROUTE                                                         [direction] OF     [direction] OF ROUTE
                                                                                    ROUTE
DM49 WHEN CAN UM100R EXPECT SPEED CHANGE AT TIME [time]                             DM49 WHEN          UM169 ‘EXPECT SPEED CHANGE AT TIME [time]’
WE EXPECT     UM101R EXPECT SPEED CHANGE AT [positionR]                             CAN WE             UM169 ‘EXPECT SPEED CHANGE AT [published identifier
[speed]                                                                             EXPECT [speed]     name]’
              UM102R EXPECT SPEED CHANGE AT [level single]                                             UM169 ‘EXPECT SPEED CHANGE AT [altitude]’
3-163


ATN Message     ATN Response Message                                 FANS 1/A Msg   FANS 1/A Response Message
Element                                                              Element
DM51 WHEN CAN UM67 PROCEED BACK ON ROUTE                             DM51 WHEN      UM67 PROCEED BACK ON ROUTE
WE EXPECT     UM68R REJOIN ROUTE BEFORE PASSING [position ATW]       CAN WE         UM68 REJOIN ROUTE BY [position]
BACK ON ROUTE UM69 REJOIN ROUTE AT OR BEFORE TIME [time]             EXPECT BACK    UM69 REJOIN ROUTE BY [time]                    Comment [PF228]:
              UM70R EXPECT BACK ON ROUTE BEFORE PASSING              ON ROUTE       UM70 EXPECT BACK ON ROUTE BY [position]        PDR #345 3)
              [position ATW]
DM52 WHEN CAN UM9 EXPECT LOWER AT TIME [time]                        DM52 WHEN      UM9 EXPECT DESCENT AT [time]
WE EXPECT     UM10R EXPECT LOWER AT [positionR]                      CAN WE         UM10 EXPECT DESCENT AT [position] TO
LOWER LEVEL                                                          EXPECT
                                                                     LOWER LEVEL
DM53 WHEN CAN UM7 EXPECT HIGHER AT TIME [time]                       DM53 WHEN      UM7 EXPECT CLIMB AT [time]
WE EXPECT     UM8R EXPECT HIGHER AT [positionR]                      CAN WE         UM8 EXPECT CLIMB AT [position]
HIGHER LEVEL                                                         EXPECT
                                                                     HIGHER LEVEL
DM70 REQUEST    UM94R TURN [direction side] HEADING [degrees]        DM70           UM94 TURN [direction] HEADING [degrees]
HEADING         UM97R AT [position ATW] FLY HEADING [degrees]        REQUEST        UM97 AT [position] FLY HEADING [degrees]
[degrees]       UM190 FLY HEADING [degrees]                          HEADING        UM190 FLY HEADING [degrees]
                UM0 UNABLE + UM96 CONTINUE PRESENT HEADING           [degrees]      UM0 UNABLE + UM96 CONTINUE PRESENT HEADING
DM71 REQUEST    UM95R TURN [direction side] GROUND TRACK [degrees]   DM71           UM95 TURN [direction] GROUND TRACK [degrees]
GROUND TRACK                                                         REQUEST
[degrees]                                                            GROUND
                                                                     TRACK
                                                                     [degrees]
3.2.2.13.2     Uplink Message Elements with Y Response Attribute
               Table 3-69Table 3-69Table 3-69 presents the Uplink message elements with Y Response attribute together with the expected                         Formatted: Cross-Reference
               responses, and the impact on the ATN ground system to support the FANS 1/A message elements.                                                     Formatted: Cross-Reference
               Note:      Only message elements with a Y response attribute that are in scope of this document per paragraph 1.2.1 are listed.


                                                Table 3-69 ATN uplink message elements with Y response attribute
ATN Message Element     ATN Response Message     FANS 1/A Message        FANS 1/A Response         Interoperability Requirement
                                                 Element                 Message
UM131 REPORT            DM57 [remaining fuel]    UM131 REPORT            DM57 [remainingfuel] OF   NIR-352              The ATN ground system shall accept a    Comment [PF229]:
ENDURANCE AND           ENDURANCE AND            REMAINING FUEL          FUEL REMAINING            DM57 downlink message received from the FANS 1/A             COMMENT #1246
PERSONS ON BOARD        [persons on board]       AND PERSONS ON          AND [remainingsouls]      aircraft after the sending of UM131 as the response to the
                        PERSONS ON BOARD         BOARD                   SOULS ON BOARD            UM131 message element.
                                                                                                   See paragraph 3.2.2.9 for use of downlink message
                                                                                                   elements.
             Resp (Y)                                        Resp (NE)                             The downlink message is not received as a response
                                                                                                   message (no message reference number) since UM131 has
                                                                                                   a NE response attribute in the FANS 1/A aircraft.
UM132 REPORT            DM33 PRESENT             UM132 CONFIRM           DM33 PRESENT              NIR-353              The ATN ground system shall accept a
POSITION                POSITION [positionR]     POSITION                POSITION [position]       DM33 downlink message received from the FANS 1/A             Comment [P230]:
                                                                                                   aircraft after the sending of UM132 as the response to the   COMMENT #812
                                                                                                   UM132 message element.
                                                                                                                                                                Comment [PF231]:
                                                                                                   See paragraph 3.2.2.9 for use of downlink message            COMMENT #1227
                                                                                                   elements.
             Resp (Y)                                        Resp (NE)                             The downlink message is not received as a response
                                                                                                   message (no message reference number) since UM132 has
                                                                                                   a NE response attribute in the FANS 1/A aircraft.
                                                                                                                                                   3-165

ATN Message Element     ATN Response Message   FANS 1/A Message        FANS 1/A Response     Interoperability Requirement
                                               Element                 Message
UM133 REPORT            DM32 PRESENT LEVEL     UM133 CONFIRM           DM32 PRESENT          IR-151               The ATN ground system shall accept a
PRESENT LEVEL           [level]                ALTITUDE                ALTITUDE [altitude]   DM32 downlink message received from the FANS 1/A
                                                                                             aircraft after the sending of UM133 as the response to the
                                                                                             UM133 message element although it does not refer (no
                                                                                             MRN) to the uplink (MIN).
                                                                                             See paragraph 3.2.2.9 for use of downlink message
                                                                                             elements.
             Resp (Y)                                      Resp (NE)                         The downlink message is not received as a response
                                                                                             message (no message reference number) since UM133 has
                                                                                             a NE response attribute in the FANS 1/A aircraft.
UM134R REPORT [speed DM113R     [speedTypes] UM134 CONFIRM             DM34 PRESENT SPEED    NIR-354              The ATN ground system shall accept a
types] SPEED         SPEED [speed]           SPEED                     [speed]               DM34 downlink message received from the FANS 1/A
                                                                                             aircraft after the sending of UM134 as the response to the
                     DM34 PRESENT SPEED                                                      UM134 message element.
                     [speed]
                                                                                             See paragraph 3.2.2.9 for use of downlink message
                                                                                             elements.
             Resp (Y)                                      Resp (NE)                         The downlink message is not received as a response
                                                                                             message (no message reference number) since UM134 has
                                                                                             a NE response attribute in the FANS 1/A aircraft.
UM135 CONFIRM           DM38 ASSIGNED          UM135 CONFIRM           DM38 ASSIGNED         IR-152               The ATN ground system shall accept a
ASSIGNED LEVEL          LEVEL[level]           ASSIGNED ALTITUDE       ALTITUDE[altitude]    DM38 downlink message received from the FANS 1/A
                                                                                             aircraft after the sending of UM133 as the response to the
                                                                       Or
                                                                                             UM133 message element although it does not refer (no
                                                                       DM77 ASSIGNED         MRN) to the uplink (MIN).
                                                                       BLOCK [altitude] TO
                                                                                             See paragraph 3.2.2.9 for use of downlink message
                                                                       [altitude]
                                                                                             elements.
             Resp (Y)                                      Resp (NE)                         The downlink message is not received as a response
                                                                                             message (no message reference number) since UM135 has
                                                                                             a NE response attribute in the FANS 1/A aircraft.
UM136 CONFIRM           DM39 ASSIGNED          UM136 CONFIRM           DM39 ASSIGNED         NIR-355              The ATN ground system shall accept a
ASSIGNED SPEED          SPEED [speed]          ASSIGNED SPEED          SPEED [speed]         DM39 downlink message received from the FANS 1/A
                                                                                             aircraft after the sending of UM136 as the response to the    Comment [P232]:
                                                                                             UM136 message element.                                        COMMENT #902, #1228
                                                                                             See paragraph 3.2.2.9 for use of downlink message
                                                                                             elements.
3-166

ATN Message Element     ATN Response Message   FANS 1/A Message        FANS 1/A Response        Interoperability Requirement
                                               Element                 Message
             Resp (Y)                                      Resp (NE)                            The downlink message is not received as a response
                                                                                                message (no message reference number) since UM136 has
                                                                                                a NE response attribute in the FANS 1/A aircraft.
UM137 CONFIRM           DM123 ASSIGNED         UM137 CONFIRM           DM40 ASSIGNED            NIR-356              The ATN ground system shall accept a    Comment [PF233]:
ASSIGNED ROUTE          ROUTE [route           ASSIGNED ROUTE          ROUTE [routeclearance]   DM40 downlink message received from the FANS 1/A             COMMENT #1229
                        clearanceR]                                                             aircraft after the sending of UM137 as the response to the
                                                                                                UM137 message element.
                                                                                                See paragraph 3.2.2.9 for use of downlink message
                                                                                                elements.
             Resp (Y)                                      Resp (NE)                            The downlink message is not received as a response
                                                                                                message (no message reference number) since UM137 has
                                                                                                a NE response attribute in the FANS 1/A aircraft.
UM140 VERIFY NEXT       DM42R NEXT             UM140 CONFIRM           DM42 NEXT                NIR-357              The ATN ground system shall accept a    Comment [PF234]:
WAYPOINT                WAYPOINT [positionR]   NEXT WAYPOINT           WAYPOINT [position]      DM42 downlink message received from the FANS 1/A             PDR #280 22)
                                                                                                aircraft after the sending of UM140 as the response to the
                                                                                                UM140 message element.
                                                                                                See paragraph 3.2.2.9 for use of downlink message
                                                                                                elements.
             Resp (Y)                                      Resp (NE)                            The downlink message is not received as a response
                                                                                                message (no message reference number) since UM140 has
                                                                                                a NE response attribute in the FANS 1/A aircraft.
UM141 VERIFY NEXT       DM43R NEXT             UM141 CONFIRM           DM43 NEXT                NIR-358              The ATN ground system shall accept a    Comment [PF235]:
WAYPOINT ETA            WAYPOINT ETA           NEXT WAYPOINT ETA       WAYPOINT ETA [time]      DM43 downlink message received from the FANS 1/A             PDR #280 22)
                        [timesec]                                                               aircraft after the sending of UM141 as the response to the
                                                                                                UM141 message element.
                                                                                                See paragraph 3.2.2.9 for use of downlink message
                                                                                                elements.
             Resp (Y)                                      Resp (NE)                            The downlink message is not received as a response
                                                                                                message (no message reference number) since UM141 has
                                                                                                a NE response attribute in the FANS 1/A aircraft.
                                                                                                                                                     3-167

ATN Message Element     ATN Response Message   FANS 1/A Message          FANS 1/A Response     Interoperability Requirement
                                               Element                   Message
UM142 VERIFY NEXT       DM44R NEXT PLUS        UM142 CONFIRM             DM44 ENSUING          NIR-359              The ATN ground system shall accept a     Comment [PF236]:
WAYPOINT                ONE WAYPOINT           ENSUING WAYPOINT          WAYPOINT [position]   DM44 downlink message received from the FANS 1/A              PDR #280 4 (cont), PDR #280 22)
                        [positionR]                                                            aircraft after the sending of UM142 as the response to the
                                                                                               UM142 message element.
                                                                                               See paragraph 3.2.2.9 for use of downlink message
                                                                                               elements.
             Resp (Y)                                        Resp (NE)                         The downlink message is not received as a response
                                                                                               message (no message reference number) since UM142 has
                                                                                               a NE response attribute in the FANS 1/A aircraft.
UM143 CONFIRM           Last downlink request sent UM143 CONFIRM         Multiple responses    None.
REQUEST                                            REQUEST               expected
             Resp (Y)                                        Resp (NE)                         The downlink message is not received as a response
                                                                                               message (no message reference number) since UM143 has
                                                                                               a NE response attribute in the FANS 1/A aircraft.
UM144 CONFIRM           DM47 SQUAWKING         UM144 CONFIRM             DM47 SQUAWKING        NIR-360              The ATN ground system shall accept a
SQUAWK                  [code]                 SQUAWK                    [beaconcode]          DM47 downlink message received from the FANS 1/A
                                                                                               aircraft after the sending of UM144 as the response to the
                                                                                               UM144 message element.
                                                                                               See paragraph 3.2.2.9 for use of downlink message
                                                                                               elements.
             Resp (Y)                                        Resp (NE)                         The downlink message is not received as a response
                                                                                               message (no message reference number) since UM144 has
                                                                                               a NE response attribute in the FANS 1/A aircraft.
UM146 REPORT            DM36 PRESENT           UM146 CONFIRM             DM36 PRESENT          NIR-361              The ATN ground system shall accept a
GROUND TRACK            GROUND TRACK           GROUND TRACK              GROUND TRACK          DM36 downlink message received from the FANS 1/A
                        [degrees]                                        [degrees]             aircraft after the sending of UM146 as the response to the
                                                                                               UM146 message element.
                                                                                               See paragraph 3.2.2.9 for use of downlink message
                                                                                               elements.
             Resp (Y)                                        Resp (NE)                         The downlink message is not received as a response
                                                                                               message (no message reference number) since UM146 has
                                                                                               a NE response attribute in the FANS 1/A aircraft.
3-168

ATN Message Element      ATN Response Message      FANS 1/A Message         FANS 1/A Response          Interoperability Requirement
                                                   Element                  Message
UM147 REQUEST            DM126 POSITION            UM147 REQUEST            DM48 POSITION              NIR-362              The ATN ground system shall accept a    Comment [PF237]:
POSITION REPORT          REPORT [position report   POSITION REPORT          REPORT [positionreport]    DM48 downlink message received from the FANS 1/A             COMMENT #1236
                         advanced]                                                                     aircraft after the sending of UM147 as the response to the
                                                                                                       UM147 message element.
                                                                                                       See paragraph 3.2.2.9 for use of downlink message
                                                                                                       elements.
              Resp (Y)                                          Resp (NE)                              The downlink message is not received as a response
                                                                                                       message (no message reference number) since UM147 has
                                                                                                       a NE response attribute in the FANS 1/A aircraft.
UM148R WHEN CAN          DM81 WE CAN               UM148 WHEN CAN           DM67 ’WE CAN               IR-153              The ATN ground system shall accept a
YOU ACCEPT [level        ACCEPT [level] AT         YOU ACCEPT [altitude]    ACCEPT [altitude] AT       DM67 downlink message received from the FANS 1/A
single]                  TIME [time]                                        [time or waypoint]         aircraft after the sending of UM148 and containing the
                                                                                                       given free text as the response to the UM148 message
                         DM82 WE CANNOT                                                                element.
                         ACCEPT [level]                                     Or
                                                                                                       DM81 and DM82 are not available in the FANS 1/A
                         DM115 WE CAN                                                                  aircraft.
                         ACCEPT [level] AT                                  DM67 ‘WE CANNOT            See paragraph 3.2.2.9 for use of downlink message
                         [positionR]                                        ACCEPT [altitude]          elements.
              Resp (Y)                                          Resp (NE)                              The FANS 1/A message element DM67 does not refer (no
                                                                                                       MRN) to the uplink (MIN).
UM151 WHEN CAN
YOU ACCEPT SPEED
[speed]
UM181R REPORT            DM78R [distance] [to      UM181 REPORT             DM78 AT                    NIR-363              The ATN ground system shall accept a    Comment [PF238]:
DISTANCE [to from]       from] [positionR]         DISTANCE [to/from]       [time][distance][toFrom]   DM78 downlink message received from the FANS 1/A             COMMENT #389, #1305
[positionR]                                        [position]               [position]                 aircraft after the sending of UM181 as the response to the
                                                                                                       UM181R message element.
                                                                                                       See paragraph 3.2.2.9 for use of downlink message
                                                                                                       elements.
              Resp (Y)                                          Resp (NE)                              The downlink message is not received as a response
                                                                                                       message (no message reference number) since UM181 has
                                                                                                       a NE response attribute in the FANS 1/A aircraft.
                                                                                                                                                    3-169

ATN Message Element     ATN Response Message   FANS 1/A Message         FANS 1/A Response      Interoperability Requirement
                                               Element                  Message
UM231 STATE             DM106 PREFERRED        UM169 ‘STATE             DM3 ROGER              IR-154              The ATN ground system shall process
PREFERRED LEVEL         LEVEL [level]          PREFERRED LEVEL’                                the FANS 1/A message element DM3 as a positive response
                                                                        DM67 ‘FL[level]’DM67                                                                Formatted: Danish (Denmark)
                                                                                               to the ATN message element UM231.
                                                                        ‘FL[level]’DM67
                                                                        ‘FL[level]’            IR-155              After sending the converted ATN          Formatted: Danish (Denmark)
                                                                                               message element UM231, the ATN ground system shall
                                                                                               technically close the dialogue upon receipt of a FANS 1/A
                                                                                               message element DM3.
                                                                                               IR-156              After sending the converted ATN
                                                                                               message element UM231, the ATN ground system shall
                                                                                               process a FANS 1/A message element DM67 containing,
                                                                                               FL [level], as the response to the ATN message element
                                                                                               UM231.
                                                                                               The operational response, using data link, is an
                                                                                               unreferenced FREE TEXT message. The indication of the
                                                                                               operational closure of the dialogue is a local matter.
                                                                                               See paragraph 3.2.2.9 for use and display of downlink
                                                                                               message elements.
             Resp (Y)                                        Resp (R)
UM232 STATE-TOP-OF- DM109R110R111R TOP         UM169 ‘STATE TOP OF      DM3 ROGER              IR-157              The ATN ground system shall process
DESCENT             OF DESCENT TIME            DESCENT’                                        the FANS 1/A message element DM3 as a positive response
                                                                        DM67 ‘TOD                                                                           Formatted: Danish (Denmark)
                    [timesec] [positionR]                                                      to the ATN message element UM232.
                                                                        [time]’DM67 ‘TOD
                                                                        [time]’DM67 ‘TOD       IR-158              After sending the converted ATN          Formatted: Danish (Denmark)
                                                                        [time]’                message element UM232, the ATN ground system shall
                                                                                               technically close the dialogue upon receipt of a FANS 1/A
                                                                                               message element DM3.
                                                                                               IR-159              After sending the converted ATN
                                                                                               message element UM232, the ATN ground system shall
                                                                                               process a FANS 1/A message element DM67 containing,
                                                                                               TOD [time], as the response to the ATN message element
                                                                                               UM232.
                                                                                               The operational response, using data link, is an
                                                                                               unreferenced FREE TEXT message. The indication of the
                                                                                               operational closure of the dialogue is a local matter.
                                                                                               See paragraph 3.2.2.9 for use and display of downlink
                                                                                               message elements.
3-170

ATN Message Element     ATN Response Message   FANS 1/A Message         FANS 1/A Response      Interoperability Requirement
                                               Element                  Message
             Resp (Y)                                        Resp (R)
UM294 WHICH LEVEL DM106 PREFERRED              UM169 ‘WHICH LEVEL       DM3 ROGER              NIR-364              The ATN ground system shall process    Comment [PF239]:
DO YOU PREFER [level] LEVEL [level]            DO YOU PREFER [leve]     DM67 ‘FL[level]’DM67   the FANS 1/A message element DM3 as a positive response     PDR #293
OR [level]                                     OR [level]’              ‘FL[level]’DM67        to the ATN message element UM294.
                                                                        ‘FL[level]’            NIR-365              After sending the converted ATN
                                                                                               message element UM294, the ATN ground system shall
                                                                                               technically close the dialogue upon receipt of a FANS 1/A
                                                                                               message element DM3.
                                                                                               NIR-366              After sending the converted ATN
                                                                                               message element UM294, the ATN ground system shall
                                                                                               process a FANS 1/A message element DM67 containing,
                                                                                               FL [level], as the response to the ATN message element
                                                                                               UM294.
                                                                                               The operational response, using data link, is an
                                                                                               unreferenced FREE TEXT message. The indication of the
                                                                                               operational closure of the dialogue is a local matter.
                                                                                               See paragraph 3.2.2.9 for use and display of downlink
                                                                                               message elements.
3.2.2.14         ATN UM with W/U resp and Corresponding FANS 1/A Messages with R resp
                 The ATN Uplink message elements in Table 3-70Table 3-70Table 3-70 have the
                 WILCO/UNABLE response messages, while the FANS 1/A message elements have the
                 ROGER response. ROGER may be substituted for WILCO/UNABLE only for the
                 messages in Table 3-70Table 3-70Table 3-70.
NIR-367           When an ATN message element requires a WILCO/UNABLE response and the matching FANS 1/A
message element requires a ROGER response, the ATN ground system shall convert the FANS 1/A response of ROGER to
WILCO.

NIR-368           When an ATN message element requires a WILCO/UNABLE response and the matching FANS 1/A
message element requires a ROGER response, the airborne crew shall use voice communications to transmit an UNABLE
response.



                   Table 3-70 ATN UM with W/U Resp and Corresponding FANS Messages with R
                                                        Resp                                                          Comment [PF240]:
                                                                                                                      List to be checked – some Ums are missing
              ATN Message Element with W/U Response             FANS Message Element with R Response
              UM127 REPORT BACK ON ROUTE                        UM127 REPORT BACK ON ROUTE
              UM128R REPORT LEAVING [level single]              UM128 REPORT LEAVING [altitude]
              UM129R REPORT MAINTAINING [level single]          UM129 REPORT LEVEL [altitude]
              UM130R REPORT PASSING [positionR]                 UM130 REPORT PASSING [position]
              UM239 STOP ADS-B TRANSMISSION                     UM169 ‘STOP ADS-B TRANSMISSION’
              UM349 REPORT SIGHTING AND PASSING                 UM169 ‘REPORT SIGHTING AND
              OPPOSITE DIRECTION [traffic type location]        PASSING OPPOSITE DIRECTION [xxx] ETP
              [etptime]                                         [time]’
              UM360 ACTIVATE ADS-C                              UM169 ‘ACTIVATE ADS-C’
              UM361 ADS-C OUT OF SERVICE REVERT TO              UM169 ‘ADS-C OUT OF SERVICE REVERT
              CPDLC POSITION REPORTS                            TO CPDLC POSITION REPORTS’
              UM362 ADS-C OUT OF SERVICE REVERT TO              UM169 ‘ADS-C OUT OF SERVICE REVERT
              VOICE POSITION REPORTS                            TO VOICE POSITION REPORTS’
              UM363 RELAY TO [aircraft flight identification]   UM169 ‘RELAY TO [aircraft flight
              [unitId] [relayedText]                            identification] [unitId] [relayedText]’



3.2.2.15         ATN UM with A/N resp and Corresponding FANS 1/A Messages with R resp
                 The ATN Uplink message elements in have the AFFIRM/NEGATIVE response
                 messages, while the FANS 1/A message elements have the ROGER response. ROGER
                 may be substituted for AFFIRM/NEGATIVE only for the messages in Table 3-71.
NIR-369           When an ATN message element requires a AFFIRM/NEGATIVE response and the matching FANS 1/A
message element requires a ROGER response, the ATN ground system shall convert the FANS 1/A response of ROGER to
AFFIRM.
NIR-370           When an ATN message element requires a WILCO/UNABLE response and the matching FANS 1/A
message element requires a ROGER response, the airborne crew shall use voice communications to transmit an NEGATIVE
response.
3-172
        Table 3-71    ATN UM with A/N Resp and Corresponding FANS Messages with R Resp
               ATN Message Element with A/N Response   FANS Message Element with R Response
               UM288 VERIFY MONITORED                  UM169 ‘VERIFY MONITORED
               FREQUENCY [frequency]                   FREQUENCY [frequency]’
               UM359 CONFIRM ADS-C EMERGENCY           UM169 ’CONFIRM ADS-C EMERGENCY’
3.3       DYNAMIC FUNCTIONS/OPERATIONS OF DATA LINK SERVICES
          This section provides the interoperability requirements as they relate to the dynamic
          behavior of the following data link services, as defined by the SPR Standard: DLIC,
          ACM, IER, CRD, ITP, OCL, DCL and AMC.
          Note: D-TAXI and D-OTIS data link services are not provided to FANS 1/A aircraft.
          The interoperability requirements are provided in tables, which also describe for each
          element of procedures supporting theof the data link services, the sequence of operations
          from a purely ATN interoperability perspective and a purely FANS 1/A interoperability
          perspective.
          The first column provides the sequence number for the operationassociated
          Interoperability Requirement or Recommendation (DO-305 IR or IRec). The second
          column describes the sequence and includes the interoperability requirements for the
          ATN ground system and ATN aircraft systems, while the third column provides the same
          information for the FANS 1/A ground system and the FANS 1/A aircraft system. The
          fourth column specifies the interoperability requirements and guidance material for the
          ATN ground system providing data link services to the FANS 1/A aircraft.
3.3.1     DLIC
          This section provides the interoperability requirements for the ATN ground system
          providing the DLIC data link service to the FANS 1/A aircraft. The DLIC service
          encompasses the following functions:
             Logon: data link application initiation and, when required, flight plan association;
             Contact: instructions to perform data link initiation with another specified ground
              system;
             Update: instruction to update the aircraft data link information.
3.3.1.1   Scope and Objective
          DLIC is the name of an air traffic service which uses the CM application to provide the
          necessary information to enable data link communications between ground and air
          systems, for applications such as CPDLC. To achieve unambiguous identification of the
          aircraft executing DLIC, in accordance with this standard, the aircraft provides its
          airframe identification (i.e. the aircraft 24 bit address), aircraft flight identification,
          departure airport, destination airport, and optionally estimated off block time (EOBT), as
          well as information about available air applications.
          Positive response to a CM-logon request does not indicate that the ATSU System will
          request or accept the establishment of a connection.
          The Advanced Services DLIC service encompasses the following functions:
             DLIC Initiation Function: data link application initiation and, when required, flight
              plan association,
             DLIC Contact Function: instructions to perform data link initiation with another
              specified ATSU System.
             DLIC Update Function: update the aircraft with data link application information.
3-174

                  Note: The Dissemination, and Ground forwarding functions are out of scope.
3.3.1.2           DLIC Initiation Function
                  The DLIC initiation function will be provided by all ATSUs that offer data link
                  application services.
                  Table 3-72Table 3-72Table 3-72 presents the sequence of operations for DLIC logon
                  using the ATN CM and FANS 1/A AFN, and specifies the related interoperability
                  requirements for the ATN ground system providing data link services to the FANS 1/A
                  aircraft.


                               Table 3-72 DLIC initiation using ATN CM and FANS 1/A AFN

          Step   ATN CM logon                                  FANS 1/A AFN                 Interoperability
                                                                                            Requirement
          1      Prior to entry into data link airspace, the   The aircrew manually         The FANS 1/A aircraft cannot
                 aircrew must ensure that the CM-logon         triggers the AFN contact,    request information from a
                 is triggered. The CM-logon provides the       providing the ground         facility other than that with
                 ATSU system with flight identification        system with flight           which AFN is being
                 data, which can be either pre-stored in       identification data, the     performed. This does not
                 the aircraft systems or entered by the        aircraft position, and for   create an issue unless a CM
                 aircrew, i.e.:                                each application             server architecture is in place.
                       - facility designation (about           available, its name and      See paragraph
                           which information is being          version.                     3.2.1.43.2.1.43.2.1.4 for use
                           requested),                         ATC centre address           of DLIC timer.
                       - CMLongTSAP (including 24-             Flight number
                           bit aircraft address),              Aircraft registration
                       - aircraft flight identification,       24-bit aircraft address
                       -    departure airport,                 (optional)
                       - destination airport,                  Note: Some aircraft may
                       - date/time departure ETD /             provide the 24-bit
                           estimated off block time            aircraft address.
                           (optional)                          Timestamp
                                                               Aircraft position
                 Note: These are synonymous, “EOBT”
                                                               Active flag
                 is used from here on.
                                                               Application name (for all
                 Plus                                          supported applications)
                       - the applications data : names,        Version number (for all
                           addresses (mandatory for            supported applications)
                           ground-initiated applications),     The FANS 1/A aircraft
                           versions, and optionally Class      set ATST1 (10mn) for
                           of Communications Service           the AFN Contact
                 using a CM-logon request.
                                                                                                       3-175

Step   ATN CM logon                                FANS 1/A AFN                Interoperability
                                                                               Requirement
2S     The ATSU system retains the                  Functionally equivalent.   None.
       applications data for use at the
       appropriate time. The ATSU system
       deletes and replaces all previously held
       applications data relating to this aircraft.
       Note: Within a domain of continuous
       data link airspace, the application data
       may be forwarded by ground co-
       ordination to subsequent ATSUs for use
       at a later stage of flight. The
       management of, and means to achieve
       this, are outside the scope of this
       standard.
3S     The ATSU system notifies the aircraft       The ground system           The conditions of the success
       of the success of the Logon process,        notifies the airborne       or failure of the logon process
       using a CM-logon response. The ATSU         system of the success of    is a local matter. The ATN
       system provides applications data for       the contact process,        ground system has to
       the applications it is able/willing to      using an AFN                determine if data provided in
       support:                                    acknowledgement             FANS 1/A AFN contact are
            - Application name(s)                  (FN_AK).                    sufficient to perform the
                                                   When the AFN                logon process.
            - Application Address(es)
                                                   acknowledgement is          See paragraph
            - Application version number(s)
                                                   received prior to the       3.2.1.43.2.1.43.2.1.4 for use
                                                   expiry of ATST1,            of DLIC timer.
                                                   ATST1 is cancelled
                                                   Note: Only the result of
                                                   the AFN Contact (reason
                                                   code) is relevant for the
                                                   FANS 1/A aircraft.
3F     The ATSU system notifies the aircraft       The ground system           The conditions of the success
       of the failure of the Logon process,        notifies the airborne       or failure of the logon process
       using a CM-logon response. The ATSU         system of the failure of    is a local matter. The ATN
       system does not include any                 the contact process,        ground system has to
       applications data in the response.          using an AFN                determine if data provided in
       Note. If the ground does not support        acknowledgement             FANS 1/A AFN contact are
       any of the applications requested by the    (FN_AK).                    sufficient to perform the
       aircraft, this is considered as a failure   When the AFN                logon process.
       of the logon process.                       acknowledgement is          See paragraph
                                                   received prior to the       3.2.1.43.2.1.43.2.1.4 for use
                                                   expiry of ATST1,            of DLIC timer.
                                                   ATST1 is cancelled
                                                   Note: Only the result of
                                                   the AFN Contact (reason
                                                   code) is relevant for the
                                                   FANS 1/A aircraft.
3-176

        Step   ATN CM logon                                 FANS 1/A AFN   Interoperability
                                                                           Requirement
        4      When the Logon was intiated by the                                             Comment [FP241]:
                                                                                              COMMENT #599
               fligth crew, the aircraft system notifies
               the flight crew about the success or
               failure of the Logon process.
               When CM-logon is successful, the
               aircraft retains applications data for use
               at the appropriate time.
                                                                                                                  3-177

3.3.1.3           DLIC Contact Function
                  Table 3-73Table 3-73Table 3-73 presents the DLIC CM Contact sequence of operations
                  using ATN CM and FANS 1/A AFN, and specifies the related interoperability
                  requirements for the ATN ground system providing data link services to the FANS 1/A
                  aircraft.


                               Table 3-73 DLIC contact using ATN CM and FANS 1/A AFN

          Step   ATN CM                                 FANS 1/A AFN                   Interoperability Requirement
          1      When required, e.g. prior to step 1    The ground system requests     The FANS 1/A INTEROP
                 of the transfer of communications      the airborne system to         Standard does not require an
                 (transmission of the NDA) the          contact the specified ground   order.
                 ATSU system requests the aircraft      system (B) FANS- address,      When a CM Contact request is
                 to contact the R-ATSU, using a         using an AFN Contact           issued and a timer is used, the
                 CM-contact request.                    Advisory (FN_CAD).             ATN ground system sets the
                 Note: Depending on bi-lateral          FANS 1/A ground system         timer to detect the absence of
                 agreements, and the availability of    sets ATST2 (5mn) to detect     an expected response.
                 ground-ground communications,          the absence of the AFN         When CM-contact request is
                 the CM-contact and transmission        Response and ATST3             not used,the ATN ground
                 of the NDA may have to be done at      (15mn) to detect the           system exchanges aircraft
                 a particular time and in a             absence of the AFN             application and address
                 particular order, to allow efficient   Complete in response to an     information (ATN or FANS
                 handovers. (Reversing the order        AFN Contact Advisory.          logon info) via ground-ground
                 presented above.)                                                     messages.
                                                                                       See paragraph
                                                                                       3.2.1.43.2.1.43.2.1.4 for use of
                                                                                       DLIC timer.
          2      On receipt of the CM-contact           Functionally equivalent.       None.
                 indication information, the aircraft
                 will automatically begin the CM
                 logon process at step 1 as
                 described in Table 4-3 with the R-
                 ATSU.
3-178

        Step   ATN CM                                 FANS 1/A AFN                   Interoperability Requirement
        3      The aircraft will advise the           The aircraft will advise the   IR-165               When using the
               initiating ATSU of the success or      initiating ATSU of the         ‘tts’ timer, the ATN ground system
                                                                                     shall cancel the ‘tts’ timer upon the
               failure of the requested contact,      success or failure of the
                                                                                     reception of negative AFN
               using a CM-contact response.           requested contact, in two      Response or AFN Complete.
               Note 1: The use of this information    steps:
                                                                                     The ATN ground system may
               is a matter of local procedures.       Step 1: Upon receipt of the    ignore the reception of positive
               Note 2: The aircraft will send a       AFN-Contact-Advisory           AFN Response regardless of
               positive CM-contact response only      (FN_ CAD), the aircraft        the reception prior or after the
               if the protocol of the CM Logon        automatically responds with    AFN Complete.
               with the R-ATSU is completed,          a downlink AFN Response
               regardless of the contents of the R-   (FN_RESP) indicating
               ATSU CM-logon response. If there       intent to perform the AFN
               is no CM-logon response from the       Logon and automatically
               R-ATSU then the aircraft indicates     goes through the same
               that the requested contact was         process as an initial DLIC
               unsuccessful.                          Logon with the R-ATSU.
                                                      Step 2: Once the AFN
                                                      Logon is performed with
                                                      the R_ATSU the aircraft
                                                      advise the initiating ATSU
                                                      of the result by sending the
                                                      downlink AFN Complete
                                                      (FN_COMP) message. The
                                                      FN_COMP contains the
                                                      next Centre address data
                                                      which is not use by the
                                                      FANS 1/A system.
                                                      FANS 1/A ground system
                                                      cancels ATST2 upon
                                                      reception of the AFN
                                                      Response in due time and
                                                      ATST3 upon reception of
                                                      the AFN Complete in due
                                                      time.
                                                                                                          3-179

          Step   ATN CM                                FANS 1/A AFN                Interoperability Requirement
                 Period of validity:                    Functionally equivalent.   None.
                 There are no protocol exchanges to
                 note the ending of the validity of
                 logon information; however, it is
                 important that neither aircraft nor
                 ATSU systems retain obsolete
                 application information about
                 communications partners after the
                 completion of communications.
                 For the aircraft, information should
                 be deleted no later than the end of
                 a flight.
                 Note 1: The aircraft may need to
                 retain logon information for a
                 number of Centres.
                 Note 2: The means of deleting
                 obsolete information for the ATSU
                 systems, and the timing of such
                 deletion, is outside the scope of this
                 standard.



3.3.1.4           DLIC Update Function
                  Table 3-64 presents the DLIC CM Update sequence of operations using ATN CM and
                  FANS 1/A AFN, and specifies the related interoperability requirements for the ATN
                  ground system providing data link services to the FANS 1/A aircraft.


                               Table 3-74 DLIC update using ATN CM and FANS 1/A AFN

          Step   ATN CM                                FANS 1/A AFN                Interoperability
                                                                                   Requirement
          1      When required, e.g. prior to step     No equivalent.
                 1a of the transfer of
                 communications (transmission of
                 the NDA - see section 4.3.5.7) the
                 ATSU system requests the
                 receiving ATSU to notify the
                 aircraft about its data link
                 capability, using a CM-update
                 request.
3-180

        Step   ATN CM                                  FANS 1/A AFN     Interoperability
                                                                        Requirement
        2      The ATSU system provides                No equivalent.
               applications data for the
               applications it is able/willing to
               support:
                   -    Application name(s),
                   -    Application Address(es),
                   -    Application version
                        number(s).
               The aircraft retains applications
               data for use at the appropriate time.
                                                                                                                     3-181


3.3.2               CPDLC
                    This section provides the interoperability requirements for the ATN ground system to
                    provide the ACM, IER, CRD, ITP, OCL, DCL and AMC data link services to the
                    FANS 1/A aircraft.


3.3.2.1             Timers in CPDLC-based services
3.3.2.1.1           CPDLC t-start timer
                                                   Table 3-75 CPDLC t-start timer

            ATN CPDLC Timers                     FANS 1/A CPDLC           Interoperability Requirement
                                                 Timers
            ‘t-start’ timer is an ASE timer in   No equivalent.           IR-160              The ATN ground system
            the DOC 9880 and is used for                                  shall set a 6-minute timer to detect the absence
                                                                          of a response after a CPDLC connection
            CPDLC connection
                                                                          request.
            establishment to detect the
            absence of a connection                                       This is required because the ‘connection
            confirmation from the aircraft                                inactivity’ timer is set to 16 minutes per
            system in an acceptable period                                the FANS 1/A INTEROP Standard,
            of time.                                                      paragraph 5.3.1.2.



3.3.2.1.2           CPDLC tr Timer
                                                     Table 3-76 CPDLC tr Timer

          ATN CPDLC                              FANS 1/A CPDLC           Interoperability Requirement
          ‘tr’ LACK timer is used by the         No equivalent.           IR-163             When using the ‘tr’timer,
          ATN ground system to detect the                                 the ATN ground system shall set ‘tr’ timer
                                                                          value per the ATS INTEROP Standard,
          absence of a Logical
                                                                          paragraph 4.1.1.3.                                 Comment [P242]:
          Acknowledgement (LACK)                                                                                             COMMENT #785
                                                                          See paragraph 3.2.2.5 for use of LACK.
          CPDLC-IRec 6 When tr is                No equivalent.           None.
          implemented, the CPDLC Aircraft        Note: tr is not
          system should use as value for the     implemented in FANS
          airborne timer tr 40 seconds for       1/A aircraft, CPDLC-
          the ACM, IER, CRD, AMC, ITP,           IRec 6 does not apply.
          D-TAXI and DCL services and 60
          seconds for OCL.
          CPDLC-IRec 7 When tr is            Same.                        None.
          implemented, the CPDLC ATSU                                     Note: not applicable for D-TAXI and
          system should use as value for the                              DSC.
          ground timer tr 40 seconds for the
          ACM, IER, CRD, AMC, ITP, D-
          TAXI and DCL services and 60
          seconds for OCL.
3-182

        ATN CPDLC                              FANS 1/A CPDLC           Interoperability Requirement
        CPC-IR 159 If the air timer tr is      No equivalent.         None.
        implemented, when a downlink           Note: tr is not
        message is sent and requires a         implemented in FANS
        LACK, the aircraft system shall        1/A aircraft, CPDLC-IR
        set tr.                                129 does not apply.
        Note: This is not applicable when
        the downlink message is sent on
        an accepted CPDLC-end response
        (e.g. WILCO response sent on an
        accepted CPDLC-end response in
        ACM).

        CPC-IR 160 If the air timer tr is      No equivalent.         None.
        implemented, when a LACK for           Note: tr is not
        the downlink message is received       implemented in FANS
        before the expiration of tr, the       1/A aircraft, CPDLC-IR
        CPDLC aircraft system shall            160 does not apply.
        cancel tr.
        CPC-IR 161 If the ground timer tr Same.                         None.
        is implemented, and the uplink
        message requires a LACK, the
        CPDLC ATSU system shall set tr.




        CPC-IR 162 If the ground timer tr      Not equivalent.          None.
        is implemented, when a LACK            Note: LACK is not
        for the uplink message is received     implemented in FANS
        before the expiration of tr, the       1/A aircraft.
        CPDLC ATSU system shall
        cancel tr.
        CPC-IR 163 When tr is                  Not equivalent.          None.
        implemented, upon expiry of tr,        Note 1: LACK is not
        the CPDLC Aircraft systrem shall       implemented in FANS
        send a notification to the sender of   1/A aircraft.
        the message requiring a LACK.
                                               Note 2: When tr is
        Note: When tr is implemented,          implemented, and when
        and when a LACK is received            a MA is received after
        after expiry of tr, the LACK may       expiry of tr, the
        be discarded.                          indication may be
                                               ignored.
                                                                                                          3-183

3.3.2.1.3        Ground CPDLC ttr Timer
                                                   Table 3-77 CPDLC ttr Timer

        ATN CPDLC                                     FANS 1/A CPDLC   Interoperability Requirement
        ‘ttr’ Termination timer (receiver) is used    No equivalent.   IR-162             The ATN ground
        by the ATN ground system to detect the                         system shall set the ‘ttr’ timer value
                                                                       per the ATS INTEROP Standard,
        absence of an CPDLC response from the
                                                                       paragraph 4.1.1.4.                         Comment [P243]:
        aircraft system in an acceptable period of                                                                COMMENT #784
        time.

        CPC-IR 164 The CPDLC ATSU system              Same.            None.
        shall implement the termination CPDLC
        timer ttr.
        Note: Operational values to be used for
        the ground CPDLC timer ttr are provided
        for each CPDLC data link service in the
        SPR.

        CPC-IR 165 When a downlink message            Same.            None.
        that does not have an N response attribute
        is received, the ATSU system shall set the
        ground CPDLC timer ttr.
        Note. When an uplink STANDBY message
        is sent in response to a downlink message
        before the expiration of the ground
        CPDLC timer ttr, the ATSU system may
        either cancel or reset the ground CPDLC
        timer ttr.

        CPC-IR 167 When an uplink message is          Same.            None.
        sent as a closure response to a downlink
        message before the expiration of the
        ground CPDLC timer ttr, the CPDL C
        ATSU system shall cancel the ground
        CPDLC timer ttr.

        Note 1. (OSD CPC-OR-28)The controller                          See Table 3-18 ATN and
        is notified of the timer expiration.                           FANS 1/A CPDLC uplink
                                                                       message elementsTable 3-18
        Note 2. Upon expiry of the ground CPDLC                                        ATN and
        timer ttr, some ground systems may                             FANS 1/A CPDLC uplink
        automatically send an um159 (ERROR                             message elementsTable 3-18
        (error information)) with the choice (2)                                       ATN and
        followed by message element UM183 (ATC                         FANS 1/A CPDLC uplink
        TIMEOUT - REPEAT REQUEST) or an                                message elements for use of UM0,
        (UNABLE followed by message element                            UM159 and UM183.
        UM183 (ATC TIMEOUT - REPEAT
        REQUEST) closing the dialogue.
3-184



3.3.2.1.4         CPDLC tts Timer
                                                     Table 3-78 CPDLC tts Timer

        ATN CPDLC                                     FANS 1/A CPDLC                 Interoperability
                                                                                     Requirement
        ‘tts’ Termination timer (sender) is used      No equivalent.                 IR-161              The ATN
        by the ATN ground system to detect the                                       ground system shall set the
                                                                                     ‘tts’ timer value per the ATS
        absence of an CPDLC response from the
                                                                                     INTEROP              Standard,
        aircraft system in an acceptable period of                                   paragraph 4.1.1.5.               Comment [P244]:
        time.                                                                                                         COMMENT #783

        CPC-IR 168 The CPDLC ATSU System              Same.                          None.
        shall implement the tts timer.

        CPC-IR 170 When a downlink message            No equivalent.                 None.
        is sent and does not have a N response        Note: tts is not implemented
        attribute, and the aircraft has               in FANS 1/A aircraft,
        implemented tts, the CPDLC aircraft           CPDLC-IR 119 does not
        system shall set the air CPDLC timer tts.     apply.

        CPC-IR 171 When an uplink STANDBY             No equivalent.                 None.
        message is received in response to a          Note: tts is not implemented
        downlink message before the expiration        in FANS 1/A aircraft,
        of the air CPDLC timer tts, and the           CPDLC-IR 171 does not
        aircraft has implemented tts, the CPDLC       apply.
        aircraft system shall cancel the air
        CPDLC timer tts.

        CPC-IR 172 When an uplink message is          No equivalent.                 None.
        a closure response received in response to    Note: tts is not implemented
        a downlink message before the expiration      in FANS 1/A aircraft,
        of the air CPDLC timer tts, and the           CPDLC-IR 172 does not
        aircraft has implemented tts, the CPDLC       apply.
        aircraft system shall cancel the air
        CPDLC timer tts

        CPC-IR 173 When an uplink message       Same.                                None.
        that does not contain an N response
        attribute is sent, the CPDLC ATSU
        system shall set the ground CPDLC timer
        tts.

        CPC-IR 174 When a downlink                    Same.                          None.
        STANDBY message is received in
        response to an uplink message before the
        expiration of the ground CPDLC timer
        tts, the CPDLC ATSU system shall reset
        the ground CPDLC timer tts.
                                                                                                          3-185

       ATN CPDLC                                     FANS 1/A CPDLC            Interoperability
                                                                               Requirement

       CPC-IR 175 When a downlink message         Same.                        None.
       is a closure response received in response
       to an uplink message before the
       expiration of the ground CPDLC timer
       tts, the CPDLC ATSU System shall
       cancel the ground CPDLC timer tts.
       Note 1. The controller or the flight crew
       is notified of the timer expiration (as per
       OSD).
       Note 2. Upon the expiry of tts, the
       sending system operator (flight crew or
       Controller) will revert to alternate
       procedures (e.g., voice) to complete the
       dialogue. Although operationally the
       dialogue is closed at this point,
       technically the dialogue remains open,
       until a response is received, or the
       connection is terminated. (i.e. the
       message identification number remains in
       use.)



3.3.2.1.5        CPDLC t-CPDLC-end Timer


                                            Table 3-79 CPDLC t-CPDLC-end Timer

ATN CPDLC                                            FANS 1/A         Interoperability Requirement
                                                     CPDLC
‘t-CPDLC-end’ timer is used by the ATN ground No equivalent.          IR-164           When using the
system after generation of an CPDLC-end request                       ‘t-CPDLC-end’ timer, the ATN
                                                                      ground    system     shall    set
to detect the absence of a CPDLC End
                                                                      ‘t-CPDLC-end’ timer value per the
Confirmation from the aircraft in an acceptable                       ATS INTEROP Standard, paragraph
period of time.                                                       4.1.1.6.                                    Comment [P245]:
                                                                                                                  COMMENT #786
3-186

ATN CPDLC                                         FANS 1/A         Interoperability Requirement
                                                  CPDLC

CPDLC-IRec 8 When t-CPDLC-end is                  No equivalent.   None.
implemented, the CPDLC ATSU system should                          See Table 3-75 CPDLC t-start
use 6 minutes for the value of the t-CPDLC-end.                    timerTable 3-75 CPDLC t-start
                                                                   timerTable 3-75 CPDLC t-start
                                                                   timer.

CPC-IR 176 When t-CPDLC-end is                    No equivalent.   None.
implemented, and when the ATSU System does
not receive a CPDLC-end confirmation prior to
expiration of the CPDLC-end timer (t-CPDLC-
end), the CPDLC ATSU System shall abort the
CPDLC connection with a CPDLC-user abort
(undefined).



3.3.2.2          ATC Communication Management (ACM) Service
                 The ACM Service provides automated assistance to the aircrew and current and next
                 controllers for conducting this transfer of ATC communications. The ACM Service
                 encompasses the transfer of all controller/aircrew communications, both the voice
                 channel and the new data communications channel used to accomplish the ACM Service.
                                                                                                            3-187

3.3.2.2.1       Requirements on UM160 NEXT DATA AUTHORITY


                                    Table 3-80 UM160 NEXT DATA AUTHORITY

        ATN CPDLC                                      FANS 1/A CPDLC          Interoperability Requirement



        ACM-OR 3 When the Current Data                 The choice              IR-166             When the NDA
        Authority (CDA) ATSU system needs to           (noFacility) is not     has been sent, the next centre
        designate an ATSU as the Next Data             available in FANS 1/A   changes and the T-ATSU is aware
                                                       INTEROP Standard.       that the R-ATSU is not providing
        Authority (NDA), it shall send the UM160
                                                                               data link services to FANS 1/A
        NEXT DATA AUTHORITY [facility
                                                                               aircraft, the ATN ground system
        designationO] specifying the facility
                                                                               shall resend UM160 (NDA) with
        designation of the NDA.
                                                                               the facility designator of the new R-
        ACM-OR 4 When the Current Data                                         ATSU.
        Authority (CDA) ATSU system has
        designated a ATSU as an NDA, and needs to                NOTE:         Note.    This   requirement        is
        change which ATSU is the Next Data                                     covering the non-availability of the
        Authority (NDA), it shall send the UM160                               choice ‘no facility’ in the
        NEXT DATA AUTHORITY [facility                                          FANS 1/A INTEROP Standard.
        designationO] specifying the facility
        designation of the changed NDA.
        ACM-OR 5 When the Current Data
        Authority (CDA) ATSU system has
        designated a ATSU as an NDA, and NDA
        cancellation is required, (i.e., there is no
        longer an NDA), the ATSU system shall
        send     the   UM160        NEXT      DATA
        AUTHORITY         [facility    designationO]
        without specifying a facility designation.
3-188



3.3.2.2.2        Management of the Data link Voice Contact Instruction (VCI)
                                                   Table 3-81 Sending the VCI

        ATN CPDLC                                      FANS 1/A CPDLC   Interoperability Requirement
        ACM-IR 17 When the T-ATSU/T-sector             Functionally     None.
        Controller triggers the transfer instruction   equivalent.      See Table 3-18 ATN and FANS 1/A
        to contact or monitor the R-ATSU/R-                             CPDLC uplink message elementsTable
        sector on the R-ATSU/R-sector voice                             3-18           ATN and FANS 1/A
        channel without requesting to close the                         CPDLC uplink message elementsTable
        CPDLC connection, the T-ATSU ground                             3-18           ATN and FANS 1/A
        system shall send the VCI message                               CPDLC uplink message elements for
        optionally concatenated with other                              use of VCI.
        message elements using the CPDLC-
        message request.
        Note: The VCI can be concatenated with
        other message elements
        ACM-IR18 When the T-ATSU/T-sector            Functionally       IR-167             When the T-ATSU
        Controller triggers the transfer instruction equivalent.        controller    initiates the  transfer
        to contact or monitor the R-ATSU/R-                             instruction (UM117R to UM122R), the
        sector on the R-ATSU/R-sector voice                             T-ATSU’s ground system shall
        channel requesting to close the CPDLC                           concatenate UM161 END SERVICE
        connection, the T-ATSU ground system                            with CONTACT or MONITOR
        shall send the VCI message optionally                           (UM117 to UM122).
        concatenated with other message elements
        using the CPDLC-end request.                                    IR-171            When the T-ATSU
        Note 1: The VCI can be concatenated with                        controller concatenates an uplink
        other message elements.                                         message (e.g. instruction UM135
                                                                        CONFIRM ASSIGNED LEVEL) with
        Note 2: Sending the transfer instruction in
                                                                        the transfer instruction, the T-ATSU’s
        a CPDLC-end request will prevent a
                                                                        ground system shall concatenate
        LACK to the WILCO of the transfer
                                                                        UM161       END       SERVICE     with
        instruction as per ICAO Document 9880 –
                                                                        CONTACT or MONITOR (UM117 to
        Chapter 5 Protocol Description
                                                                        UM122) and the uplink message.
                                                                        See Table 4-8 for additional
                                                                        requirement on CPDLC-end service.
        ACM-IR 19 Once the T-ATSU initiates      Same.
        the transfer instruction (VCI), it shall                        None.
        prohibit transmission of any other CPDLC
        messages unless and until:
             - receipt of an ERROR response, or
             - receipt of an UNABLE response.
                                                                                                     3-189

                                             Table 3-82 Acknowledging the VCI

        ATN CPDLC                                    FANS 1/A CPDLC           Interoperability Requirement

        ACM-IR 20 When the flight crew               No equivalent.           None.
        acknowledges the VCI with a STANDBY,         Note: Requirements not
        the aircraft system shall send a DM2         placed on FANS 1/A
        STANDBY not requiring a LACK using a         aircraft.
        CPDLC-message request.
        Note: As per ICAO Document 9880, it is
        not possible for ATSU Systems to send a
        LACK in response to STANDBY after
        CPDLC-end request.

        ACM-IR 21 When the flight crew         No equivalent.                 None.
        acknowledges the VCI with a WILCO, the Note: Requirements not
        aircraft system shall:                 placed on FANS 1/A
             send a DM0 WILCO response,       aircraft.

            confirm the CPDLC termination, if
        requested
        Note . The WILCO can be concatenated
        with another message element (e.g
        DM38).

        ACM-IR 22 When the flight crew               No equivalent.           None.
        acknowledges via VCI with a                  Note: Requirements not
        UNABLE/ERROR, the aircraft system            placed on FANS 1/A
        shall:                                       aircraft.
            send an UNABLE/ERROR
        response,
            reject the CPDLC termination, if
        requested.
        Note: This results in continued capability
        to exchange operational messages with
        the T-ATSU.



3.3.2.2.3        Requirements on DM99 CURRENT DATA AUTHORITY
                 DM99 is not available in FANS 1/A aircraft.
                 SPR and INTEROP Ground requirements related to DM99 do not apply.
3-190

3.3.2.2.4       Requirements on LACK prohibition
                Note. LACKs are not available in FANS 1/A aircraft.
                                                Table 3-83 LACK Prohibition
        ATN CPDLC                                  FANS 1/A CPDLC        Interoperability Requirement

        ACM-IR 28 The CPDLC R-ATSU System         No equivalent.         See Table 3-18 ATN and
        shall require a LACK for this message     Note 1: UM233 is not   FANS 1/A CPDLC uplink message
        when sending UM233 USE OF LACK            available in FANS      elementsTable 3-18
        PROHIBITED.                               1/A aircraft.                            ATN and
                                                                         FANS 1/A CPDLC uplink message
        Note: A LACK is required to protect       Note 2: Requirements
                                                                         elementsTable 3-18
        rejecting a downlink message requesting a not placed on FANS                       ATN and
        LACK sent prior to the receipt of UM233. 1/A aircraft.           FANS 1/A CPDLC uplink message
                                                                         elements for use of UM233.
                                                                         None.

        ACM-IR 29 Until the CPDLC R-ATSU           No equivalent.        None.
        System receives a LACK to UM233, it        Note: Requirements
        shall not reject any downlink message      not placed on FANS
        because it requires a LACK.                1/A aircraft.

        ACM-IR 230 After the CPDLC R-ATSU          No equivalent.        None.
        System receives a LACK to UM233, it        Note: Requirements
        shall reject any downlink messages         not placed on FANS
        requiring a LACK.                          1/A aircraft.

        CPDLC-OR-47 When the aircraft system       No equivalent.        None.
        receives UM233 USE OF LACK                 Note: Requirements
        PROHIBITED, it shall set all future        not placed on FANS
        downlinks for this CPDLC connection to     1/A aircraft.
        ‘LACK not required’.
                                                                                                             3-191

3.3.2.2.5       Enabling CPDLC


                                                Table 3-84 Enabling CPDLC

        ATN CPDLC                                    FANS 1/A CPDLC            Interoperability
                                                                               Requirement
        The R-ATSU considers CPDLC enabled            Functionally             Connect Confirm can be
        upon receipt of CPDLC message DM99                                     sufficient       for      some
                                                      equivalent.
        and satisfaction of required local conditions                          ATN ground        systems    to
        (if any).                                                              consider CPDLC as enabled
                                                      Other local conditions   (See also step 7). This can
                                                      for enabling CPDLC       lead to the rejection of uplink
                                                      include, for example,    messages by the FANS 1/A
                                                      ASSUME input,            aircraft, while R-ATSU is still
                                                      boundary proximity,      NDA.
                                                      etc.
                                                      Note: The FANS 1/A       IR-179           In addition
                                                      aircraft does not send   to other local conditions, the
                                                      DM89, DM99 or
                                                                               R-ATSU/initial ATSU shall
                                                      messages equivalent
                                                                               enable     CPDLC         using
                                                      to DM89 and DM99.
                                                                               “Connect Confirm” IMI CC1.

                                                     DM89, DM99 cannot IR-191 In addition to other
                                                     be used as a condition local conditions, the R-
                                                     for CPDLC enabled.     Sector’s ATN ground system
                                                                            shall enable CPDLC using
                                                                            “Connect Confirm” IMI CC1.
        Until CPDLC is enabled, the R-ATSU           Same.                     None.
        system prohibits sending any CPDLC
        messages other than UM3 STANDBY,
        UM2 REQUEST DEFFERED, UM0
        UNABLE, UM159 ERROR or UM 227
        LACK
                                                     Note: The FANS 1/A
        ACM-OR 2 With the exception of               aircraft does not send
        emergency messages, when an ATSU             DM99.
        receives a message requiring a response
                                                     Functionally
        prior to enabling CPDLC, it shall
                                                     equivalent.
        automatically respond with a STANDBY
        message
3-192

        ATN CPDLC                                       FANS 1/A CPDLC   Interoperability
                                                                         Requirement
        The R-ATSU sends a CPDLC message                                 None.
        UM340 indicating the latency value.                              See Table 3-18 ATN and
                                                                         FANS 1/A CPDLC uplink
                                                                         message elementsTable 3-18
                                                                                         ATN and
                                                                         FANS 1/A CPDLC uplink
                                                                         message elementsTable 3-18
                                                                                         ATN and
                                                                         FANS 1/A CPDLC uplink
                                                                         message elements for use of
                                                                         UM340.
        The R-ATSU system sends a CPDLC                                  None.
        message (UM285) indicating its facility                          See Table 3-18    ATN   and
        designation, facility name, facility function                    FANS 1/A       CPDLC  uplink
                                                                         message elementsTable 3-18
                                                                                           ATN   and
                                                                         FANS 1/A       CPDLC  uplink
                                                                         message elementsTable 3-18
                                                                                           ATN   and
                                                                         FANS 1/A       CPDLC  uplink
                                                                         message elements for use of
                                                                         UM285.

        The R-ATSU System shall indicate to the         Same.            None.
        Controller when CPDLC is enabled.




3.3.2.2.6        Handling CPDLC connections


                                        Table 3-85 CPDLC Connection Establishment

        ATN CPDLC                                         FANS 1/A       Interoperability Requirement
                                                          CPDLC
        CPC-IR 180 When the T-ATSU/T-sector               None.          See paragraph 4.2.2 for
        Controller triggers the establishment of a                       CPDLC start request
        CPDLC connection, the CPDL C T-ATSU                              requirements.
        ground system shall use the CPDLC-start
        request.
                                                                                    3-193




                              Table 3-86 CPDLC Connection Termination

ATN CPDLC                                  FANS 1/A      Interoperability Requirement
                                           CPDLC
CPC-IR 181 When the T-ATSU/T-sector        None.         IR-194 The T-ATSU’s ATN
Controller triggers the termination of a                 ground system shall send
CPDLC connection, the CPDLC T-ATSU                       FANS1/A UM161 (End
ground system shall use the CPDLC-end                    Service).
request.                                                 See paragraph 4.2.2 for
                                                         CPDLC end request
                                                         requirements.
3-194



3.3.2.3     Clearance Request and Delivery (CRD) and Information Exchange and Reporting
            (IER) Services
            This continental data link service describes airborne system/ATSU air-ground data
            communication procedures for operations for the ATN ground system for the following:
               Aircrew-initiated reports and clearance requests;
               Controller-initiated delivery of clearances, instructions and notifications to aircraft.
            The Clearance Request and Delivery (CRD) and Information Exchange and Reporting
            (IER) Services are equivalent in ATN and FANS 1/A.
            No additional Interoperability Requirements.
            Note: See sections 3.2.2.8 and 3.2.2.9       to see accommodation of specific CPDLC
            messages.


3.3.2.4     Departure Clearance (DCL) Service
            DCL is an air traffic service supported by CPDLC, which provides support for the
            following exchanges:
               Aircrew departure clearance requests and responses to ground; and
               Controller delivery of revised departure clearances to aircraft.


3.3.2.4.1   Accommodation of Departure Clearances
            The ATN ground system can accommodate FANS 1/A aircraft using the departure
            clearance service.
            The ATN departure clearance service uses the following ATN CPDLC messages:
                   UM73R [departure clearanceR]
                   UM79R CLEARED TO [positionR] VIA [route clearanceR],
                   UM80R CLEARED [route clearanceR],
                   UM83R UM83R AT [position ATW] CLEARED [route clearanceR] (for
                    revision only)
                   UM91R HOLD INBOUND TRACK [degrees] [direction side] TURNS [leg
                    type] LEGS
                   UM92R AT [positionR] HOLD [direction sideO] AS PUBLISHED
                   UM118R AT [position ground air] CONTACT [unit Id] [frequency] or UM119R
                    [timeGroundair] CONTACT [unit Id] [frequency]
                   UM311 STARTUP APPROVED [assigned timeO]
                   UM314 EXPECT [clearance typeR][assigned timeO]
                                                                                           3-195

                     UM224 NO DELAY EXPECTED
                     UM289 REST OF ROUTE UNCHANGED
                     UM325 REVISED [revision reasonO]                                              Comment [PF246]:
                                                                                                    PDR #292
              The ATN ground system can accommodate the FANS 1/A aircraft using the departure
              clearance service by sending the following FANS1/A CPDLC messages.
                     UM79 CLEARED           TO    [position]   VIA   [routeclearance]   (UM79R
                      Accommodation)
                     UM83 AT [position] CLEARED [routeclearance] (UM83R Accommodation)
                     UM80 CLEARED [routeClearance] (UM80R Accommodation)
                     UM123 SQUAWK [code] (UM73R Accommodation)
                     UM19 MAINTAIN [altitude] (UM73R Accommodation)
                     UM158 ATIS [atis code] (UM73R Accommodation)
                     UM169 [free text] (UM73R/UM325/UM224 Accommodation)
              The following ATN messages are not accommodated in the FANS 1/A departure
              clearance service. These messages are also part of the D-TAXI service.
                     UM118R AT [position ground air] CONTACT [unit Id] [frequency] or UM119R
                      [time ground air] CONTACT [unit Id] [frequency]
                     UM311 STARTUP APPROVED [assigned timeO]
                     UM91R HOLD INBOUND TRACK [degrees] [direction side] TURNS [leg
                      type] LEGS
                     UM92R AT [positionR] HOLD [direction sideO] AS PUBLISHED
NIR-371         The ATN ground system shall limit the number of UM169 [freeText] message elements
used in the Departure Clearance service such that the maximum number of concatenated DCL uplinks
does not exceed 5.
              Figure 3 describes the FANS 1/A DCL Service Accommodation.
3-196




                            Figure 3     SC-214 to FANS DCL Accommodation


3.3.2.4.2   Accommodation of Departure Clearance Revisions
            The Departure Clearance (DCL) Service revisions are different in ATN and FANS 1/A.
            In ATN, the revised departure clearance message UM73R is preceeded by the ATN
            message UM325 REVISED [revision reasonO]. A revision can be accommodated in
            FANS 1/A by appending a free text message UM169 “REVISED [revision reason]” to
            the start of a departure clearance. In ATN only the updated Departure Clearance fields
            will be sent in a DCL revision, in FANS 1/A all mandatory fields will be sent in the
            revision as well as any optional fields that have changed.
                                                                                                            3-197

NIR-372      The ATN ground system shall append the FANS 1/A free text message UM169
“REVISED [revisionReason]” as the first element of a revised departure clearance message.
                                                                                                                       Comment [PF247]:
             Table 3-87Table 3-87Table 3-87 describes the revision scenarios for Departure                             PDR #197
             Clearances using FANS 1/A+.
                                     Table 3-87 DCL Revision Scenarios
             ATN Revision   FANS Revision      Revision Case                         Interoperability
             Message        Message                                                  Requirement
             UM325          UM169              Change in departure clearance         When revising departure           Comment [PF248]:
             REVISED        REVISED            parameters (no change in route)       clearance parameters with no      PDR #331
             [revision      [revisionReason]                                         change in the route, the ATN
             reasonO] +     (+ optionally:                                           ground system sends the
             UM73R          UM169                                                    appropriate UM(s) including
                            [freetext],                                              the revised parameters to the
                            UM158 ATIS                                               FANS 1/A+ aircraft.
                            [atis code],
                            UM123                                                    See section 3.2.2.8 for
                            SQUAWK                                                   accommodation requirements
                            [code]                                                   for UM325 and UM73R
                            and/orUM19
                            MAINTAIN
                            [altitude])

             UM325          UM169              FANS 1/A UM80 CLEARED                 When revising the complete
             REVISED        REVISED            [routeclearance] is used for a        route of flight in a departure
             [revision      [revisionReason]   complete route revision.              clearance, the ATN ground
             reasonO] +     + UM80 (+                                                system sends UM80 with
             UM73R+UM80     optionally:                                              revised parameters to the
                            UM169                                                    FANS 1/A+ aircraft.
                            [freetext],
                            UM158 ATIS                                               See section 3.2.2.8 for
                            [atis code],                                             accommodation requirements
                            UM123                                                    for UM325 and UM73R
                            SQUAWK
                            [code]
                            and/orUM19
                            MAINTAIN
                            [altitude])

             UM325          UM79               FANS 1/A UM79 CLEARED TO              The ground system sends a
             REVISED                           [position] VIA [routeclearance] is    UM79 when the departure
             [revision                         used when the revision includes a     clearance revision includes a
             reasonO] +                        route change ending at the            route change ending at the
             UM73R+UM79R                       specified position (the “TO” point)   specified position.
                                               which is a point after the SID or
                                               the SID Transition (if these are      Note. The “TO” point is a
                                               present) up to and including the      point after the SID or the SID
                                               first point in the first Arrival,     Transition (if these are
                                               Approach, or associated Transition    present) up to and including
                                               in the aircraft’s active route.       the first point in the first
                                                                                     Arrival,       Approach,     or
                                                                                     associated Transition in the
                                                                                     aircraft’s active route.

                                                                                     The ground system does not
                                                                                     include an arrival airport in
3-198

                                                                                   UM79 when revising          a
                                                                                   departure clearance.

                                                                                   This scenario cannot occur for
                                                                                   a ground ATN system
                                                                                   accommodating revised DCL
                                                                                   UM73R for a FANS aircraft
            UM325           UM83            FANS1/A UM83 AT [position]             The ground system sends
            REVISED                         CLEARED [routeclearance] is            UM83 when the departure
            [revision                       used when the revision includes a      clearance revision includes a
            reasonO] +                      route change starting at a specified   route change starting at a
            UM73R+UM83R                     position (the “AT” point) which is     specified position.
                                            the last point in the SID or the SID
                                            Transition (if these are present) or   Note. The “AT” point is the
                                            any point after that, excluding any    last point in the SID or the
                                            point within the Arrival, Approach,    SID Transition (if these are
                                            or associated Transitions.             present) or any point after
                                                                                   that, excluding any point
                                                                                   within the Arrival, Approach,
                                                                                   or associated Transitions.
                                                                                   The ground system does not
                                                                                   include an arrival airport in
                                                                                   UM83 when revising a
                                                                                   departure clearance.



3.3.2.4.3   Departure Clearance Request
            The departure clearance request is different in ATN and FANS 1/A. In ATN departure
            clearances are requested via the new departure clearance request message DM139
            REQUEST DEPARTURE CLEARANCE [DepartureClearanceRequest]. In FANS 1/A
            departure clearances are requested using the DM25 REQUEST CLEARANCE message.


3.3.2.5     ATC Microphone Check (AMC) Service
            The AMC service provides controllers with the capability to uplink an instruction for
            aircraft to check that they are not blocking a voice channel. No aircrew acknowledgement
            of the instruction is required.
            The ATC Microphone Check (AMC) Service is equivalent in ATN and FANS 1/A.
            No additional Interoperability Requirements.
            Note: See sections 3.2.2.8 and3.2.2.9       to see accommodation of specific CPDLC
            messages.
3.3.2.6     ITBO Service
            The ITBO Service defined as a subset of the greater 4DTRAD service. A FANS 1/A
            aircraft may participate in the ITBO service using the CPDLC application optionally
            supplemented by ADS-C, given the differences identified above.
            If ADS-C is to be used for ITBO, the FANS 1/A aircraft and the ATS ground system
            must implement the ADS-C application as defined in DO-258A/ED-100A.
                                                                                                       3-199

        When a FANS 1/A aircraft participates in the ITBO service the time parameters are
        restricted to hours and minutes. This restriction needs to be taken into consideration when
        implementing ITBO for FANS 1/A aircraft.

3.4     Guidelines for ATN Ground System Use of FANS 1/A ADS-C Application
3.4.1   ADS-C Contracts
        Table 3-88Table 3-88Table 3-88 compares the ATN ADS contracts with the FANS 1/A
        contracts. The threee types of ADS-C contrats and the emergency mode are supported by
        both types of aircraft.


                           Table 3-88 ATN and FANS 1/A ADS-C Contracts

        ATN ADS-C Contract              FANS 1/A ADS-C                Interoperability Guidance
                                        Contract
        [PM-ADS] imposes that           [ED100A/DO258A]               No additional interoperability
        ATN aircraft support at least   implicitly imposes that the   guidance.
        one of the three types of       FANS 1/A aircraft support
        ADS-C contracts.                the three types of ADS
                                        contract.

        Note. See PM-ADS chapter        Note. See ED100A section
        8.                              4.5.1 NOTE.
        ADS-C Demand Contract           Demand Contract               Functionally equivalent.
        ADS-C Event Contract            Event Contract                Functionally equivalent.
        ADS-C Periodic Contract         Periodic Contract             Functionally equivalent.
        [SC-214 ATN INTEROP]            [ED100A/DO258A]             Functionally equivalent.
        imposes that the ATN            implicitly imposes that the
        ground system which             FANS 1/A ground system
        receives any ADS report         which supports periodic
        shall support the               contract or event contract
        Emergency/Urgency mode.         shall support the Emergency
        Note. See 3.2.6.2.1: Upon       Periodic Contract.
        receipt of an ADS report
        that has an emergency
        and/or urgency indication,
        the ATSU System shall
        notify an operator
3-200

3.4.2     Uplink Functions
3.4.2.1   ADS Uplink Messages
          Table 3-89Table 3-89Table 3-89 compares the ATN ADS-C uplink messages with the
          FANS 1/A ADS uplink messages. ADS uplink messages are similar for both types of
          aircraft, except the abort messages defined specifically to terminate the ATN
          connections, and the ground emergency contract that cannot be initiated by ATN ground
          system.


                          Table 3-89 ATN and FANS 1/A ADS uplink messages

          ATN ADS Uplink                  FANS 1/A ADS Request         Interoperability Guidance
          [0] ADS-cancel-all-contracts-   Tag (1): Cancel All          Functionally equivalent.
          PDU (terminates connection)     Contracts and Terminate
          Note. The aircraft              Connection Request
                                                                       With ATN aircraft, the ground
          automatically terminates the    Note. The aircraft sends a   system has to “cancel all
          dialogue.                       Disconnect Request with      contracts” only when periodic
                                          reason code 8.               and/or event contracts are in
                                                                       place.
                                                                       Note. The connection is
                                                                       automatically closed down by the
                                                                       aircraft when no ADS contract is
                                                                       in place.
                                                                       With FANS 1/A aircraft, the
                                                                       ground system has to “cancel all
                                                                       contracts and terminate the
                                                                       connection” even if no contract is
                                                                       in place.
          [1] ADS-cancel-contract-PDU     Tag (2): Cancel Contract Functionally equivalent.
          (terminates one contract)       Request
           CancelContract = event-        ADS Contract Request
               contract(0) or periodic-       Number
               contract(1)
          Note. The aircraft
          automatically terminates the
          dialogue when no contract
          remains.
          [2] ADS-contract-PDU
                    ADS Contract          Tag (7): Periodic Contract   Functionally equivalent.
                    Request               Request                      See paragraph 3.4.2.2 for
                     contract-type =                                  additional guideline on demand
                       demand                                          contract.
                    ADS Contract          Tag (8): Event Contract      Functionally equivalent.
                    Request               Request                      See paragraph 3.4.2.4 for
                     contract-type =                                  additional guideline on event
                       event                                           contract.
                                                                                     3-201

ATN ADS Uplink               FANS 1/A ADS Request       Interoperability Guidance
         ADS Contract      Tag (7): Periodic Contract   Functionally equivalent.
         Request           Request                      See paragraph 3.4.2.3 for
          Contract-type =                              additional guideline on periodic
            periodic                                    contract.
[3] ADS Provider Abort       No equivalent.             Not equivalent.
                                                        The ground system cannot issue
                                                        an abort to the FANS 1/A
                                                        aircraft.
[4] ADS User Abort           No equivalent.             Not equivalent.
                                                        The ground system cannot issue
                                                        an abort to the FANS 1/A
                                                        aircraft.
No equivalent                Tag (6): Cancel            Not equivalent.
                             Emergency Mode Request     The ground system cannot
                                                        request an ATN aircraft to cancel
                                                        the emergency mode.
No equivalent                Tag (9): Emergency         Not equivalent.
                             Periodic Contract          The ground system cannot
                                                        request an ATN aircraft to
                                                        modify an emergency mode.
3-202

3.4.2.2   ADS Demand Contract Request
          Table 6-3 compares the ADS-C Demand Contract Request parameters for ATN and
          FANS 1/A. Same data block types can be requested except for the extended projected
          profile. The ground system requests the projected profile for ATN aircraft or the aircraft
          intent for FANS aircraft resulting in a different data being reported. Aircraft intent cannot
          be requested for a number of way points.


             Table 3-90 ATN and FANS 1/A ADS-C Demand Contract Request variables

          ATN ADS Demand Contract FANS 1/A ADS Demand                Interoperability Guidance
          Request                 Contract Request
          DemandContractRequest           Tag (7): Periodic ADS      When issuing a Demand
                                          Request                    Contract request, the ground
                                                                     system sets the ADS request tag
                                                                     to (7) periodic.
                                          Tag (11): Reporting Rate   When issuing a Demand
                                          (optional)                 Contract request, the ground
                                           Scaling Factor = 0       system:
                                           Rate = N/A                includes the reporting rate
                                                                          tag in the contract request,
                                                                      sets the Scaling Factor value
                                                                          to (0).
                                                                     Note. The FANS 1/A aircraft
                                                                     does not use the rate parameter
                                                                     in the demand contract request.
          [0] Contract Number             Tag (7): Periodic ADS      Functionally equivalent.
                                          Request                    When issuing a Demand
                                           ADS Contract Request     Contract request, the ground
                                              Number                 system generates a new contract
                                                                     request number.
                                                                     The ATN ground system does
                                                                     not duplicate a contract request
                                                                     number already used for active
                                                                     contract on the same ADS
                                                                     connection.
                                                                     Note. See Table 3-110Table
                                                                     3-110Table 3-110 for additional
                                                                     guideline on the contract number
                                                                     parameter.
                                                                                          3-203

ATN ADS Demand Contract FANS 1/A ADS Demand                   Interoperability Guidance
Request                 Contract Request
[1] Aircraft-address (optional)   Tag (17) Airframe ID        When the aircraft address is
                                   Modulus                   desired, the ground system:
                                                               includes the Airframe ID
                                                                   group tag in the ADS
                                                                   Contract request.
                                                               may use a modulus different
                                                                   from zero in the demand
                                                                   contract request.
[2] Aircraft-identification       Tag (12) Flight Id          When the aircraft identification
(optional)                         Modulus                   address is desired, the ground
                                                              system:
                                                               includes the Flight ID group
                                                                   tag in the ADS Contract
                                                                   request.
                                                               may use a modulus different
                                                                   from zero in the demand
                                                                   contract request.
[3] Projected-profile (optional) Tag (13): Predicted Route    When the projected profile is
                                 (optional)                   desired, the ground system:
                                  Modulus                     includes the Predicted Route
                                                                   group tag in the ADS
                                                                   Contract request.
                                                               may use a modulus different
                                                                   from zero in the demand
                                                                   contract request.
[4] Ground-vector                 Tag (14): Earth Reference   When the ground vector is
                                  (optional)                  desired, the ground system:
                                   Modulus                    includes the Earth Reference
                                                                   group tag in the ADS
                                                                   Contract request.
                                                               may use a modulus different
                                                                   from zero in the demand
                                                                   contract request.
[5] Air-vector                    Tag (15): Air Reference     When the air vector is desired,
                                  (optional)                  the ground system:
                                   Modulus                    includes the Air Reference
                                                                   group tag in the ADS
                                                                   Contract request.
                                                               may use a modulus different
                                                                   from zero in the demand
                                                                   contract request.
3-204

        ATN ADS Demand Contract FANS 1/A ADS Demand                  Interoperability Guidance
        Request                 Contract Request
        [6] Met-info                     Tag (16): Meteorological    When the met info is desired, the
                                         (optional)                  ground system:
                                          Modulus                    includes the Meteorological
                                                                         group tag in the ADS
                                                                         Contract request.
                                                                      may use a modulus different
                                                                         from zero in the demand
                                                                         contract request.
        [7] Extended-projected-profile   No equivalent.              When the extended projected
        (optional)                                                   profile is desired, the ground
                                                                     system:
                                                                      includes the Predicted Route
                                         Tag (13): Predicted Route
                                                                          group tag or the Aircraft
                                         (optional)
                                                                          Intent Group tag in the ADS
                                          Modulus                        Contract request.
                                         or                           may use a modulus different
                                         Tag (21): Aircraft Intent        from zero in the demand
                                         (optional)                       contract request.
                                          Modulus                   Note. Use of the Predicted Route
                                          Aircraft Intent           Group (2 way-points) or the
                                              Projection Time        Intermediate Projected Intent
                                                                     Group (up to 10 way-points) in
                                                                     place of the Extended Project
                                                                     profile Group is a local matter.
                                                                     When requesting the Aircraft
                                                                     Intent group, the Intermediate
                                                                     Projected Intent group and the
                                                                     Fixed Projected Intent group will
                                                                     be provided by the FANS 1/A
                                                                     aircraft.
                                                                     The Fixed Projected Intent
                                                                     Group represents the position at
                                                                     the requested time in the Aircraft
                                                                     Intent group request.
        EPPWindow:                                                   See Table 3-110 ATN and              Formatted: Table text

         time-interval, or                                          FANS 1/A ADS variables with          Formatted: Cross-Reference
                                                                     range and resolution
                                                                     Table 3-110        ATN and           Formatted: Cross-Reference
                                                                     FANS 1/A ADS variables with
                                                                                                          Formatted: Table text
                                                                     range and resolution
                                                                     Table 3-110        ATN and
                                                                     FANS 1/A ADS variables with
                                                                     range and resolution
                                                                      for additional guidelines
                                                                     EPPWindow parameter.
                                                                          3-205

ATN ADS Demand Contract FANS 1/A ADS Demand   Interoperability Guidance
Request                 Contract Request
   number of way points   No equivalent
[8] Eta Min Max Request    No Equivalent      The ground system cannot
                                              request an ETA min max data
                                              block from a FANS 1/A aircraft.
3-206

3.4.2.3   ADS Periodic Contract Request
          Table 6-4 presents the ADS-C Periodic Contract Request parameters for ATN and
          FANS 1/A. Same data block types can be requested except for the extended projected
          profile. The ground system requests the projected profile for ATN aircraft or the aircraft
          intent for FANS aircraft resulting in a different data being reported. Aircraft intent cannot
          be requested for a number of way points.


               Table 3-91 ATN and FANS 1/A ADS Periodic Contract Request variables

          ATN ADS Periodic          FANS 1/A ADS Periodic           Interoperability Guidance
          Contract Request          Contract Request
          Periodic Contract         Tag (7): Periodic Contract      Equivalent.
          Request                   Request
          [0] Contract Number          ADS Contract Request       Functionally equivalent.
                                        Number                     When issuing a Periodic Contract
                                                                   request, the ground system generates a
                                    Note. A contract number of 255 new contract request number.
                                    indiccates an emergency        The ATN ground system does not
                                    contract.                      duplicate a contract request number
                                                                   already used for active contract on the
                                                                   same ADS connection.
                                                                   Note. See Table 3-110Table 3-110Table
                                                                   3-110 for additional guideline on the
                                                                   contract number parameter.
                                                                   Note. Emergency contract management
                                                                   is outside the scope of this document.
          [1] Reporting-rate        Tag (11): Reporting Rate        When issuing a Periodic Contract
              Reporting time       (optional)                      request, the ground system includes the
                                     Scaling Factor (SF)           reporting rate tag in the Contract
                                                                    request.
                                     Rate
                                                                    In FANS 1/A, if the reporting rate is not
                                                                    provided, the default reporting rate is
                                                                    304 seconds.
                                                                    In ATN, the fastest reporting rate is one
                                                                    second, while in FANS 1/A, the fastest
                                                                    reporting rate is 64 seconds.
                                                                    Note. It is unlikely that the ATN aircraft
                                                                    will meet the 1 second reporting
                                                                    interval.
                                                                    Note. See Table 3-110Table 3-110Table
                                                                    3-110 for additional guideline on the
                                                                    reporting time parameter
                                                                                        3-207

ATN ADS Periodic         FANS 1/A ADS Periodic           Interoperability Guidance
Contract Request         Contract Request
[2] Aircraft-address-    Tag (17) Airframe ID            When the aircraft address is desired, the
modulus (optional)       (optional)                      ground system includes the Airframe ID
                          Modulus                       group tag in the ADS Contract request.
                                                         Note. See Table 3-110Table 3-110Table
                                                         3-110 for additional guideline on the
                                                         modulus parameter.
[3] Aircraft-            Tag (12) Flight Id (optional)   When the aircraft identification address
identification-modulus    Modulus                       is desired, the ground system includes
(optional)                                               the Flight ID group tag in the ADS
                                                         Contract request.
                                                         Note. See Table 3-110Table 3-110Table
                                                         3-110 for additional guideline on the
                                                         modulus parameter.
[4] Projected-profile-   Tag (13): Predicted Route       When the projected profile is desired,
modulus (optional)       (optional)                      the ground system includes the
                          Modulus                       Predicted Route group tag in the ADS
                                                         Contract request.
                                                         Note. See Table 3-110Table 3-110Table
                                                         3-110 for additional guideline on the
                                                         modulus parameter.
[5] Ground-vector-       Tag (14): Earth Reference       When the ground vector is desired, the
modulus                  (optional)                      ground system includes the Earth
                          Modulus                       Reference group tag in the ADS
                                                         Contract request.
                                                         Note. See Table 3-110Table 3-110Table
                                                         3-110 for additional guideline on the
                                                         modulus parameter.
[6] Air-vector-modulus   Tag (15): Air Reference         When the air vector is desired, the
                         (optional)                      ground system includes the Air
                          Modulus                       Reference group tag in the ADS
                                                         Contract request.
                                                         Note. See Table 3-110Table 3-110Table
                                                         3-110 for additional guideline on the
                                                         modulus parameter.
[7] Met-info-modulus     Tag (16): Meteorological        When the met info is desired, the ground
                         (optional)                      system includes the Meteorological
                          Modulus                       group tag in the ADS Contract request.
                                                         Note. See Table 3-110Table 3-110Table
                                                         3-110 for additional guideline on the
                                                         modulus parameter.
3-208

        ATN ADS Periodic          FANS 1/A ADS Periodic          Interoperability Guidance
        Contract Request          Contract Request
        [8] Extended-projected-   No equivalent.                 When using the extended projected
        profile-modulus                                          profile modulus, the ground system
        (optional):                                              includes the Predicted Route group tag
                                  Tag (13): Predicted Route
         modulus,                                               or the Aircraft Intent Group tag in the
                                  (optional)
                                                                 ADS Contract request.
         EPP Window:              Modulus
                                                                 Note. Use of the Predicted Route Group
           time-interval, or     or                             (2 way-points) or the Intermediate
                                  Tag (21): Aircraft Intent      Projected Intent Group (up to 10 way-
                                  (optional)                     points) in place of the Extended Project
                                   Modulus                      profile Group is a local matter.
                                   Aircraft Intent Projection   When requesting the Aircraft Intent
                                       Time                      group, the Intermediate Projected Intent
                                                                 group and the Fixed Projected Intent
                                                                 group will be provided by the
                                                                 FANS 1/A aircraft.
                                                                 The Fixed Projected Intent Group
                                                                 represents the position at the requested
                                                                 time in the Aircraft Intent group request.
                                                                 See Table 3-110Table 3-110Table 3-110
                                                                 for additional guideline on modulus and
                                                                 EPP Window parameters.
           number of way         No equivalent                  The ground system cannot request the
            points                                               number of way points from a FANS 1/A
                                                                 aircraft.
        [9] Eta-min-max-          No equivalent                  The ground system cannot request an
             modulus                                             ETA min max data block from a FANS
                                                                 1/A aircraft.
                                                                                                    3-209

3.4.2.4   ADS Event Contract Request
          Table AP- 1Table AP- 1Table AP- 1 presents the ADS Event contract request for ATN                 Formatted: Cross-Reference
          and FANS 1/A. Only a limited number of events are common to both types of aircraft.               Formatted: Cross-Reference



                       Table AP- 1 ATN and FANS 1/A ADS Event contract request

          ATN ADS Event Contract        FANS 1/A ADS Event            Interoperability Guidance
          Request                       Contract Request
          Event Contract Request        Tag (8): Event ADS Request Equivalent.
          [0] Contract Number               ADS Contract Request     Functionally equivalent.
                                             Number                   When issuing a Periodic Contract
                                                                      request, the ground system
                                                                      generates a new contract request
                                                                      number.
                                                                      The ATN ground system does not
                                                                      duplicate a contract request
                                                                      number already used for active
                                                                      contract on the same ADS
                                                                      connection.
                                                                      Note. See Table 3-110Table
                                                                      3-110Table 3-110 for additional
                                                                      guideline on the contract number
                                                                      parameter.
          [1] EPPWindow (optional)      No equivalent                                                       Comment [PF249]:

          [2] Lateral-deviation-        Tag (10): lateral deviation   Equivalent event type.
          (optional)                    change (optional)             See paragraph 3.4.2.4.1 for
                                                                      lateral deviation change event
                                                                      management.
          [3] Vertical-speed (optional) Tag (18): vertical rate       Equivalent event type.
                                        change (optional)             See paragraph 3.4.2.5 for vertical
                                                                      rate change event management.
          [4] Level-range-change        Tag (19): altitude range      Equivalent event type.
          (optional)                    change (optional)             See paragraph 3.4.2.5.1 for
                                                                      level/altitude range change event
                                                                      management.
          [5] Way-point-change          Tag (20): Waypoint change     Equivalent event type.
          (optional)                    (optional)                    See paragraph 3.4.2.5.2 for
                                                                      waypoint change event
                                                                      management.
          [6] Air-speed-change          No equivalent                 Ground system cannot receive air
          (optional)                                                  speed change indication from
                                                                      FANS 1/A aircraft.
3-210

        ATN ADS Event Contract        FANS 1/A ADS Event          Interoperability Guidance
        Request                       Contract Request
        [7] Ground-speed-change       No equivalent               Ground system cannot receive
        (optional)                                                ground speed change indication
                                                                  from FANS 1/A aircraft.
        [8] epp-waypoint-sequenced Tag (20): Waypoint change      When using an extended projected
                                   (optional)                     profile change event contract, the
                                                                  ground system includes the
        [9] epp-waypoint-inserted     Tag (20): Waypoint change   Waypoint change tag in the ADS
                                      (optional)                  Contract request.
        [10] epp-way-pointdeleted     Tag (20): Waypoint change   Using the Waypoint change event
                                      (optional)                  will issue the provision of the
                                                                  Predicted Route group.
                                                                  Note. Use of the Predicted Route
                                                                  Group in place of the Extended
                                                                  Projected Profile Group is a local
                                                                  matter.
                                                                  See paragraph 3.4.2.5.2 for
                                                                  waypoint change event
                                                                  management.
        [11] epp-next-way-point-in-   No equivalent               Ground system cannot receive
        horizon                                                   next way point in horizon
                                                                  indication from FANS 1/A
                                                                  aircraft.
        [12] epp-lateral-offset-      No equivalent               Ground system cannot receive
        change                                                    lateral offset change indication
                                                                  from FANS 1/A aircraft.
        [13] epp-level-constraint-    No equivalent               Ground system cannot receive
        change                                                    level constraint change indication
                                                                  from FANS 1/A aircraft.
        [14] epp-speed-constraint-    No equivalent               Ground system cannot receive
        change                                                    speed constraint change indication
                                                                  from FANS 1/A aircraft.
        [15] epp-RTA-change           No equivalent               Ground system cannot receive
                                                                  RTA change indication from
                                                                  FANS 1/A aircraft.
        [16] epp-RTA-missed           No equivalent               Ground system cannot receive
                                                                  RTA missed change indication
                                                                  from FANS 1/A aircraft.
        [17] epp-tolerance-event      No equivalent               Ground system cannot receive
                                                                  EPP tolerance change indication
                                                                  from FANS 1/A aircraft.
        [18] fom-change (optional)    No equivalent               Ground system cannot receive
                                                                  fom change indication from FANS
                                                                  1/A aircraft.
                                                                                                 3-211

            ATN ADS Event Contract         FANS 1/A ADS Event      Interoperability Guidance
            Request                        Contract Request
            [19] level-change (optional)   No equivalent           Ground system cannot receive
                                                                   level change indication from
                                                                   FANS 1/A aircraft.
            [20] vertical-clearance-       No equivalent           Ground system cannot receive
            deviation (optional)                                   vertical deviation change
                                                                   indication from FANS 1/A
                                                                   aircraft.
            [21] out-of-vertical           No equivalent           Ground system cannot receive out
            boundaries (optional)                                  of vertical boundary change
                                                                   indication from FANS 1/A
                                                                   aircraft.
            [22] air-speed-range-          No equivalent           Ground system cannot receive air
            deviation                                              speed range change indication
                                                                   from FANS 1/A aircraft.



3.4.2.4.1   Lateral deviation change event
            Table 6-5 presents the ATN and FANS 1/A Lateral Deviation Change Event.
                                    Table 3-92 Lateral Deviation Change Event

            ATN                            FANS 1/A                Interoperability Guidance
            Request Parameters
               Left Lateral deviation        Lateral deviation   In FANS 1/A, the same threshold
                threshold                      threshold           is provided for left and right.
               Right Lateral deviation                            See Table 3-110Table 3-110Table
                threshold                                          3-110 for additional guideline on
               Offset tag (optional)                              the lateral deviation parameter.      Comment [PF250]:
                                                                                                         COMMENT #1076
            Event Report Parameters
               Basic Group                   Basic Group         See paragraph 3.4.3.2.1 for
               Ground vector                 Earth Reference     additional guidance on basic
                                                                   group.
                                                                   See paragraph 3.4.3.2.2 for
                                                                   additional guidance on ground
                                                                   vector / earth reference group.
            Trigerring Event                                       Equivalent
3-212

        ATN                             FANS 1/A                       Interoperability Guidance
           when the lateral                when the absolute value
            deviation of the aircraft        of the lateral distance
            relative to the active           between the aircraft's
            route of flight is more          actual position and the
            than the value of                aircraft's expected
            lateral-deviation-               position on the active
            change                           flight plan is greater
                                             than the lateral
                                             deviation threshold
                                        If the aircraft is flying an
                                        offset path, a Lateral
                                        Deviation event will be
                                        triggered if:
                                        a) An Event contract
                                        containing the Lateral
                                        Deviation Event is active;
                                        and
                                        b) The offset distance is
                                        greater than the Lateral
                                        Deviation Threshold.
                                        The report will be generated
                                        at the time the offset is
                                        activated.
        Reporting Rate                                                 Not equivalent
           once every 60 seconds          only one report
                                                                                                      3-213

3.4.2.5   Vertical speed change event
          Table 6-6 presents the ATN and FANS 1/A Vertical Speed Change Event.
                                   Table 3-93 Vertical Speed Change Event

          ATN                           FANS 1/A                        Interoperability Guidance
          Request Parameters                                            In FANS 1/A, the same threshold
                                                                        is provided for high and low.
                                                                        .
             High Vertical rate           Vertical rate change        Note. See Table 3-110Table
             Low Vertical rate             threshold                   3-110Table 3-110 for additional
                                                                        guideline on the vertical rate
                                                                        parameter.
          Event ADS Report                                              Equivalent


             Basic Group                  Basic Group                 See paragraph 3.4.3.2.1 for
             Ground vector                Tag (14): Earth             additional guidance on basic
                                            Reference Group             group.
                                                                        See paragraph 3.4.3.2.2 for
                                                                        additional guidance on ground
                                                                        vector / earth reference group.
          Trigerring Event                                              Equivalent.
             only when the aircraft’s     If the vertical rate
              rate of climb is greater      threshold is positive,
              than the value of             when the aircraft's rate
              vertical-rate-change          of climb is greater than
                                            the vertical rate
                                            threshold.
                                           If the vertical rate
                                            threshold is negative,
                                            when the aircraft's rate
                                            of climb is less than the
                                            vertical rate threshold
                                            (i.e. the aircraft is
                                            descending)
          Reporting Rate                                                Not equivalent
             once every 60 seconds        only one report
3-214

3.4.2.5.1   Level/Altitude range change event
            Table 6-7 presents the ATN and FANS 1/A Level/Altitude Event.


                                    Table 3-94 Level/Altitude Range Event

            ATN                          FANS 1/A                        Interoperability Guidance
            Request Parameters                                           Equivalent.
               Ceiling level                Ceiling altitude           Note. See Table 3-110Table
               Floor level                  Floor altitude             3-110Table 3-110 for additional
                                                                         guideline on the level/altitude
                                                                         parameter.
            Event ADS Report                                             Not equivalent, the ground vector
                                                                         is not downlinked.
               Basic Group                  Basic Group                See paragraph 3.4.3.2.1 for
               Ground vector                                            additional guidance on basic
                                                                         group.
            Trigerring Event                                             Equivalent
               when the aircraft’s level    when the aircraft's
                is greater than the value     altitude is greater than
                of ceiling, or less than      the altitude ceiling or
                the value of floor            less than the altitude
                                              floor
            Reporting Rate                                               Not equivalent
               once every 60 seconds        only one report
                                                                                                      3-215

3.4.2.5.2   Way-point change event
            Table 6-8 presents the ATN and FANS 1/A Way-point Event.


                                          Table 3-95 Way-point Event

            ATN                           FANS 1/A                       Interoperability Guidance
            Request Parameters
               none                         none                       Equivalent.
            Event ADS Report
               Basic Group                  Basic Group                See paragraph 3.4.3.2.1 for
               Projected Profile            Tag (13): Predicted        additional guidance on basic
                                              route Group                group.
                                                                         See paragraph 3.4.3.2.3 for
                                                                         additional guidance on projected
                                                                         profile / predicted route group.
            Trigerring Event
               whenever the aircraft’s      The waypoint change
                next way-point changes        event is triggered by a
                                              change to the next or
                                              next- plus-one waypoint
                                              (due to a flight plan
                                              change or waypoint
                                              sequence).
            Reporting Rate                                               Equivalent
               None, sequence of            The waypoint change
                waypoint                      event trigger remains in
                                              effect for all waypoint
                                              changes.
3-216

3.4.3     Downlink Functions
3.4.3.1   ADS Downlink Messages
          Table 6-9 compares the ATN ADS-C downlink messages with the FANS 1/A downlink
          messages.
                       Table 3-96 ATN and FANS 1/A ADS downlink messages

          ATN ADS Messages        FANS 1/A ADS Messages            Interoperability Guidance
          [0] ADS-report-PDU
          [1] ADS-accepted-PDU
              ADSReport           Tag (7): Periodic Report         Functionally equivalent.
               contract-type =                                    See paragraph 3.4.3.2 for
                 demand                                            additional guidance on ADS
                                                                   Report.
              ADSReport           Tag (10, 18, 19, 20) ADS Event   Functionally equivalent.
               contract-type =   reports                          See paragraph 3.4.3.2 for
                 event                                             additional guidance on ADS
                                                                   Report
              ADSReport           Tag (7): Periodic Report         Functionally equivalent.
               contract-type =                                    See paragraph 3.4.3.2 for
                 periodic                                          additional guidance on ADS
                                                                   Report
          [2] ADS-reject-PDU      Tag (4): Negative                Functionally equivalent.
                                  acknowledgement                  See paragraph 3.4.3.3 for
                                  Note. Following the generation   additional guidance on ADS
                                  of three consecutive Negative    Reject.
                                  Acknowledgements on the same
                                  connection, the FANS 1/A
                                  aircraft shall cancel all
                                  contracts on the respective
                                  connection and terminate that
                                  connection
          [3] ADS-ncn-PDU         Tag (5): Noncompliance           Functionally equivalent.
                                  Notification                     See paragraph 3.4.3.7 for
                                                                   additional guidance on non-
                                                                   compliance notification.
                                                                                            3-217

ATN ADS Messages           FANS 1/A ADS Messages                Interoperability Guidance
[4] ADS-Positive-          Tag (3): Acknowledgement             In the ATN ground system,
Acknowledgement-PDU        For a valid Demand contract          positive acknowledgement is
                           request, not containing the          only in use in Event and
                           Aircraft Intent Group, the only      Periodic contract types.
                           response shall be the                The ATN ground system would
                           “acknowledgement” assembled          be able to process the
                           with the ADS report in the same      “acknowledgement” assembled
                           ADS downlink message.                with the ADS report.
                           For a valid Demand contract          When requesting the Predicted
                           request containing the Aircraft      Route Group from the
                           Intent Route Group the initial       FANS 1/A aircraft if a “Positive
                           response shall be the                Acknowledgement” is sent, it is
                           “acknowledgement”. The               always sent with the Demand
                           acknowledgement is either sent       report.
                           in a separate ADS downlink           Some FANS 1/A aircraft send
                           message or assembled with the        the acknowledgement in an
                           ADS report in the same ADS           ADS message separate from the
                           downlink message.                    ATS report. Other FANS 1/A
                                                                aircraft send the
                                                                acknowledgement assembled
                                                                with the ADS report in the same
                                                                ADS downlink message.
                                                                The ATN “Positive
                                                                Acknowledgement” is always
                                                                included in ADS Demand
                                                                report.
                                                                See paragraph 3.4.3.6 for
                                                                additional guidance on ADS
                                                                Positive Acknowledgement
[5] ADS-cancel-positive-   Tag (3): Acknowledgement             Functionally equivalent.
acknowledgement-PDU        Note. Sent after the receipt of a    See paragraph 3.4.3.6 for
                           valid cancel event contract.         additional guidance on ADS
                                                                Cancel Positive
                                                                Acknowledgement
[6] ADS-cancel-negative    Tag (4): Negative                    Functionally equivalent.
acknowledgement-PDU        acknowledgement                      See paragraph 3.4.3.3 for
                           Note. Sent after the receipt of an   additional guidance on ADS
                           invalid cancel event contract.       Cancel Negative
                                                                Acknowledgement
[7] ADS-Provider-Abort-    No equivalent.                       The ground system cannot
PDU                                                             receive an abort from an
                                                                FANS 1/A aircraft.
[8] ADS-User-Abort-PDU No equivalent.                           The ground system cannot
                                                                receive an abort froman
                                                                FANS 1/A aircraft.
3-218

          ATN ADS Messages              FANS 1/A ADS Messages         Interoperability Guidance
          No equivalent.                Tag (9): Emergency Report     Not equivalent.
                                                                      In ATN, the emergency
                                                                      information is downlinked in
                                                                      each ADS-report, not as a
                                                                      separate downlink message.


          No equivalent.                Tag (6): Cancel Emergency     Functionally equivalent.
                                        Mode Indication               In ATN, the cancel indication is
                                                                      downlinked in each ADS-report,
                                                                      not as a separate downlink
                                                                      message.



          The FANS 1/A aircraft may concatenate different ADS reports in a single downlink
          message. The ATN ground system would be able to process multiple different ADS
          reports in a single downlink message.


3.4.3.2   ADS Report
          Table 6-10 presents the ATN and FANS 1/A ADS reports.
                                Table 3-97 ATN and FANS 1/A ADS reports

          ATN ADS Reports                FANS 1/A ADS Reports       Interoperability Guidance
          ADS report                     Tag (7): ADS report        Functionally equivalent.
                                         Periodic report            When the ADS-report is related to
                                         Or                         an ADS-Demand contract request,
                                         Tag (10, 18, 19, 20) ADS   the ATN ground system processes
                                         Event reports              the ADS report tag (7) as the
                                                                    reception of a Demand report.
                                                                    When the ADS-report is related to
                                                                    an ADS-Periodic contract request,
                                                                    the ATN ground system processes
                                                                    the ADS report tag (7) as the
                                                                    reception of a Periodic report.
                                                                    The ATN ground system
                                                                    processes the ADS report tags (10,
                                                                    18, 19, 20) as the reception of
                                                                    Event reports.
          [0, 1, 2] Basic Information       Basic ADS Group        Functionally equivalent.
                                                                    See paragraph 3.4.3.2.1 for
                                                                    additional guidance on basic
                                                                    group.
                                                                                      3-219

ATN ADS Reports           FANS 1/A ADS Reports         Interoperability Guidance
[3] Contract Number       Not equivalent.              Not equivalent.
                                                       FANS 1/A does not include the
                                                       contract number in the ADS
                                                       Report.
[4] Aircraft address      Tag (17) Airframe ID group   Functionally equivalent.
                                                       Note. See Table 3-110Table
                                                       3-110Table 3-110 for additional
                                                       guideline on the aircraft adress /
                                                       airframe id parameter.
[5] Aircraft Flight       Tag (12) Flight              Functionally equivalent.
Identification            Identification Group         Note. See Table 3-110Table
                                                       3-110Table 3-110 for additional
                                                       guideline on the aircraft id
                                                       parameter.
[6] Projected Profile     Tag (13) Predicted Route     Functionally equivalent.
                          Group                        See paragraph 3.4.3.2.4 for
                          Predicted Route Group        additional guidance on Projected
                                                       Profile / Predicted Route group.
[7] Ground vector         Tag (14): Earth Reference    Functionally equivalent.
                          Group                        See paragraph 3.4.3.2.2 for
                                                       additional guidance on ground
                                                       vector / earth reference group.
[8] Air vector            Tag (15): Air reference      Functionally equivalent.
                          Group                        See paragraph 3.4.3.2.3 for
                                                       additional guidance on ground
                                                       vector / earth reference group.
[9] Met info              Tag (16): Meteorological     Functionally equivalent.
                          Group                        See paragraph 3.4.3.2.7 for
                                                       additional guidance on MET
                                                       group.
[10] Extended Projected   Predicted Route Group        The ground system processes the
Profile                   Predicted Route Group Tag    Predicted Route Group Tag (13)
                          (13)                         as the reception of Extended
                                                       Projected Profile Group when it
                                                       results from an EPP request
                                                       translated into a Predicted Route
                                                       Request.
                                                       Only the next and next+1
                                                       waypoints are provided.
                                                       See paragraph 0 for additional
                                                       guidance on EPP / Predicted
                                                       Route.
3-220

        ATN ADS Reports           FANS 1/A ADS Reports        Interoperability Guidance
                                  Tag (22): Intermediate      The ground system processes the
                                  Projected Intent Group      Intermediate Predicted Intent
                                                              Group Tag (22) and the Fixed
                                                              Projected Intent Group tag (23) as
                                  And
                                                              the reception of Extended
                                                              Projected Profile Group when they
                                  Tag (23): Fixed Projected   results from an EPP request
                                  Intent Group                translated into an Aircraft Intent
                                                              request.
                                                              The Intermediate Projected Intent
                                                              group and the Fixed Projected
                                                              Intent group are provided by the
                                                              FANS 1/A aircraft.
                                                              If Intermediate Projected Intent is
                                                              used, then up to the next 10
                                                              waypoints are provided
                                                              Intermediate Projected Intent
                                                              group does not contain waypoint
                                                              where there is no change of
                                                              altitude or speed or track
                                                              (heading).
                                                              See paragraph 3.4.3.2.6 for
                                                              additional guidance on EPP /
                                                              Intermediate Project Intended
                                                              Group.


        [11] Emergency-urgency-   No equivalent               No equivalent
        status                                                The emergency information is
                                                              received from a FANS 1/A
                                                              aircraft in ADS emergency reports
                                                              through the establishment of an
                                                              emergency contract.
                                                                                                           3-221



3.4.3.2.1   Basic Group / Basic ADS Group
            Table 6-11 presents the ATN Basic Data Block / FANS 1/A Basic Group.
                                Table 3-98 Basic Data Block / Basic ADS Group

            ATN – Basic                    FANS 1/A – Basic                 Interoperability Guidance
            Parameters                                                      Equivalent
               ThreeDPosition                                              Latitude, Longitude,
               Latitude                      Latitude                     Altitude/level, timestamp range
                                                                            and resolution different.
               Longitude                     Longitude
                                                                            FOM data is different.
               Level (OPTIONAL)              Altitude
               Time                          Timestamp
                                                                            Note. See Table 3-110Table
               FOM                           FOM
                                                                            3-110Table 3-110 for additional
               Position accuracy             Position accuracy            guideline on latitude, longitude,
               Multiple units operating      TCAS Health                  level/altitude, timestamp, position
                                                                            accuracy parameters.
               Acas operational              Navigation System
                                               Redundancy


            Note. When an ADS report       When either the latitude or
            is received with the           the longitude for a position
            FOM/position accurancy=0,      are invalid, both shall be set
            the ATN ground system          to -180°. In the Basic
            shall disregard the position   Group, the FOM shall also
            and timestamp.                 be set to 0.
                                           When the timestamp is
                                           invalid, in the basic ADS
                                           Group, the FOM shall also
                                           be set to 0.

3.4.3.2.2   Ground Vector data block / Earth Reference Group
            Table 6-12 presents the ATN Ground Vector Data Block / FANS 1/A Earth Reference
            Group.
                                 Table 3-99 Ground Vector / Earth Reference

            ATN – Ground Vector            FANS 1/A – Earth                 Interoperability Guidance
                                           Reference
            Parameters                                                      Equivalent
               Track                         True Track                   Note. See Table 3-110Table
               Ground-speed                  Ground speed                 3-110Table 3-110 for additional
                                                                            guideline on track, ground speed
               Vertical rate                 Vertical rate
                                                                            and vertical rate parameters.
3-222

3.4.3.2.3   Air Vector data block / Air Reference Group
            Table 6-13 presents the ATN Air Vector Data Block / FANS 1/A Air Reference Group.
                                    Table 3-100 Air Vector / Air Reference

            ATN – Air Vector            FANS 1/A – Air Reference Interoperability Guidance
            Parameters                                             Equivalent
               Heading                    V, S, True Heading     Note. See Table 3-110Table
               Air speed                  Mach Speed             3-110Table 3-110 for additional
                                                                   guideline on heading, air speed
               Veritcal Rate              Vertical Rate
                                                                   and vertical rate parameters.



3.4.3.2.4   Projected Profile data block / Predicted route Group
            Table 6-14 presents the ATN Projected Profile Data Block / FANS 1/A Predicted route
            Group.
                           Table 3-101 Projected Profile data block / Predicted Route

            ATN – Projected Profile     FANS 1/A – Predicted       Interoperability Guidance
                                        Route
            Parameters                                             Functionally equivalent.
               Next Way-point:            Next Way-point:        Note. See Table 3-110Table
               Position                   Position               3-110Table 3-110 for additional
                                                                   guideline on position and time
               Name (OPTIONAL)            No equivalent          parameters.
               ETA (OPTIONAL)             ETA
               Next+1 Way-point:          Next+1 Way-point:
               Position                   Position
               Name (OPTIONAL)
               ETA (OPTIONAL)
                                                                                                   3-223



3.4.3.2.5   Extended Projected Profile data block / Predicted route Group
            Table 6-15 presents the ATN Extended Projected Profile Data Block / FANS 1/A
            Predicted route Group.
                Table 3-102 Extended Projected Profile data block / Predicted route Group

            ATN – Projected Profile    FANS 1/A – Predicted route       Interoperability Guidance
            Extended Projected Profile Predicted Route Group:
                                         Predicted Route Group Tag
                                         (13)
            Epp-computation-time       No equivalent
            For each waypoint (up to   For next waypoint and next + 1   If Predicted Route Group is used,
            128 waypoints)::           waypoint                         then the comparison can be done
                                                                        only for the data provided, up to
                                                                        the next 2 waypoints.


                Position                   Position                     Latitude, Longitude,
                       Latitude             Latitude                    Altitude/level, ETA timestamp
                                                                        range and resolution are different.
                       Longitude            Longitude
                                                                        See paragraph 3.4.3.8 for
                       Level                Altitude
                                                                        parameter range and resolution
                                                                        differences.
                Name                       Not equivalent.
                ETA                          ETA (at next waypoint
                                             only)


                Estimated Speed            Not equivalent.
                Vertical Type              Not equivalent.
                Lateral Type               Not equivalent.
                Level Constraints          Not equivalent.
                Speed restrictions         Not equivalent.
                RTA                        Not equivalent.
            Gross mass                 No equivalent.
            Gross mass at TOD          No equivalent.
            Speed schedule             No equivalent.
            Trajectory intent status   No equivalent.
            Crossover Levels           No equivalent
3-224

3.4.3.2.6   Extended Projected Profile data block / Intermediate Projected Intent Group
            Table 6-16 presents the ATN Extended Projected Profile Data Block / FANS 1/A
            Intermediate Projected Intent Group.
             Table 3-103 Extended Projected Profile data block / Intermediate Projected Intent
                                                        Group

            ATN – Projected Profile      FANS 1/A – Intermediate          Interoperability Guidance
                                         Projected Intent
            Extended Projected Profile    Intermediate projected intent   See paragraphs 3.4.3.2 for the use
                                          tag (22)                        of intermediate projected intent tag
                                                                          (22).

            For each waypoint (up to     Up to 10 waypoints               If Intermediate Projected Intent is
            128 waypoints)::                                              used, then the comparison can be
                                                                          done only the data provided, up to
                                                                          the next ten waypoints.
                Position                     Position


                      Latitude                 No equivalent            For the Extended Projected Profile,
                      Longitude                No equivalent            the ATN ground system may
                                                                          convert the information provided
                      Level                    Altitude
                                                                          in the Intermediate Projected
                                                Distance from previous   Intent Group into LAT/LON
                                                 waypoint                 reference.
                                                True Track from
                                                 previous waypoint
                ETA                          Projected time
                Estimated Speed              No equivalent
                Name                         No equivalent
                Vertical Type                No equivalent                The Intermediate Projected Intent
                                                                          Group may include waypoints
                                                                          (ATC compulsory waypoint and
                                                                          pilot/ company-inserted waypoint)
                                                                          and vertical profile points. The
                                                                          way point type is not identified in
                                                                          the intermediate projected intent
                                                                          report.
                                                                          Intermediate Projected Intent
                                                                          group does not contain waypoint
                                                                          where there is no change of
                                                                          altitude or speed or track
                                                                          (heading).
                Lateral Type                 No equivalent
                Level Constraints            No equivalent
                Speed restrictions           No equivalent
                                                                                               3-225

            ATN – Projected Profile     FANS 1/A – Intermediate      Interoperability Guidance
                                        Projected Intent
                RTA                          No equivalent
            Gross mass                  No equivalent
            Gross mass at TOD           No equivalent
            Speed schedule              No equivalent
            Trajectory intent status    No equivalent




3.4.3.2.7   MET data block / Meteorological Group
            Table 6-17 presents the ATN MET Data Block / FANS 1/A Meteorological Group.
                               Table 3-104 ATN Ground Vector / Earth Reference

            ATN – MET                    FANS 1/A –               Interoperability Guidance
                                         Meteorological Group
            Parameters                                            Not Equivalent
               Wind Speed                   Wind Speed          Note. See Table 3-110Table
               Wind direction               V, S, True Wind     3-110Table 3-110 for additional
                                              Direction           guideline on wind speed, air speed
                                                                  and vertical rate parameters.
               Wind quality Flag (O)        No equivalent                                            Comment [PF251]:
                                                                                                       PDR #321
               Temperature                  S, Temperature
               Turbulence (O)               No equivalent
               Humidity (O)                 No equivalent
3-226

3.4.3.3           ADS ATN Reject / FANS Negative Ack
                  Table 6-18 presents the ATN and FANS 1/A ADS reject.
                                  Table 3-105 ATN ADS Reject / FANS 1/A Negative Ack

          ATN ADS Reject             FANS 1/A ADS Negative Ack                     Interoperability Guidance
          [3] ADS reject             Tag (4): Negative acknowledgement             Functionally equivalent.
             ADS contract Number       ADS contract Request Number               ATN aircraft use the contract type
                                                                                   to associate the reject data with the
                                                                                   contract whereas the FANS aircraft
                                                                                   use the contract number.
                                                                                   Note. See Table 3-110Table
                                                                                   3-110Table 3-110 for additional
                                                                                   guideline on wind speed, air speed
                                                                                   and vertical rate parameters.
             Emergency Urgency         No equivalent
             Reject Details            Reason                                    FANS aircraft provide more
                                                                                   detailed reason on the reject cause.

             ADS service               No equivalent
              unavailable
             Undefined                 Duplicate on request group tag (1)
                                        Duplicate reporting rate tag (2)
                                        Event contract request with no data
                                         (3)
                                        Improper operational mode tag (4)
                                        Non-matching cancel contract
                                         number (5)
                                        Matching existing contract request
                                         number (6)
                                        Undefined contract request tag (7)
                                        Undefined error (8)
                                        Not enough data in request (9)
                                        Floor altitude >= ceiling altitude (10)
                                        Vertical rate change threshold equal
                                         to 0 (11)
                                        Aircraft intent projection time
                                         parameter equal to 0 (12)
                                        Lateral deviation change threshold
                                         equal to 0 (13)
                                                                                            3-227

ATN ADS Reject          FANS 1/A ADS Negative Ack                  Interoperability Guidance
   Maximum-capacity-      No equivalent                          When the aircraft receives an ADS
    exceeded                                                       service request while the maximum
                                                                   number of ADS connections are
                                                                   established:
                                                                    the FANS 1/A aircraft denies
                                                                       service by sending a
                                                                       Disconnect Request
                                                                       (IMI=DIS) with reason code 1,
                                                                    The ATN aircraft sends the
                                                                       reject reason Maximum-
                                                                       capacity-exceeded with the
                                                                       identity of the ground systems
                                                                       it is connected to.
   Invalid-waypoint       No equivalent
   No equivalent          Extended Data (only for reasons 1, 2   The ground system ignores the
                            and 7):                                extended data.
                           Duplicate optional message group
                            tag
                           Duplicate reporting Rate tag.
                           Undefined contract request tag
3-228

3.4.3.4   ADS ATN Cancel Positive Ack / FANS Positive Ack
          Table 6-19 presents the ATN and FANS 1/A ADS Positive Ack.
                 Table 3-106 ATN ATN Cancel Negative Ack / FANS 1/A Positive Ack

          ADS ATN Cancel Positive     FANS 1/A ADS Positive      Interoperability Guidance
          Ack                         Acknowledgement
          [3] ADS Cancel Negative     Tag (3): Acknowledgement   Functionally equivalent.
          Ack                                                    Note. ATN Neg Ack is not used for
                                                                 contract rejection (see ADS
                                                                 Reject).
             No equivalent              ADS Contract Request   Functionally equivalent.
                                          Numbe


             Request type               No equivalent
             Cancel-event-contract
             Cancel-periodic-
              contract



3.4.3.5   ADS ATN Cancel Negative Ack / FANS Negative Ack
          Table 6-20 presents the ATN and FANS 1/A ADS Negative Ack.
                Table 3-107 ATN ATN Cancel Negative Ack / FANS 1/A Negative Ack

          ADS ATN Cancel Negative FANS 1/A FANS Negative         Interoperability Guidance
          Ack                     Ack
          [3] ADS Cancel Negative     Tag (4): Negative          Functionally equivalent.
          Ack                         acknowledgement            Note. ATN Neg Ack is not used for
                                                                 contract rejection (see ADS
                                                                 Reject).
             No equivalent              ADS contract Request   Functionally equivalent.
                                          Number


             Request type               No equivalent
             Cancel-event-contract
             Cancel-periodic-
              contract
             Reject Reason              Reason
             No-such-contract           Non-matching cancel
                                          contract number (5)
                                                                                                    3-229



3.4.3.6   ADS Positive Acknowledgement
          Table 6-21 presents          the    ATN     ADS     and   comparable    FANS 1/A        positive
          acknowledgement.
                    Table 3-108 ATN and FANS 1/A ADS positive acknowledgement

          ATN ADS Positive              FANS 1/A ADS Positive          Interoperability Guidance
          Acknowledgement               Acknowledgement
          [5] ADS Positive              Tag (3): Acknowledgement       Functionally equivalent.
          Acknowledgement
             ADS contract Request          ADS Contract Request      ATN aircraft use the contract
              Number                         Number                    type to associate the reject data
              (OPTIONAL)                                               with the contract whereas the
                                                                       FANS aircraft use the contract
                                                                       number.
             Request Type:                 No equivalent
             event contract,
             periodic contract,
             demand contract,
             cancel event contract,
             cancel periodic
              contract,
             cancel all contracts.
          




3.4.3.7   ADS Non-Compliance Notification
          Table 6-22 presents the ATN ADS and cFANS 1/A non-compliance notifications.
                   Table 3-109 ATN and FANS 1/A ADS non-compliance notification

          ATN ADS Non-Compliance             FANS 1/A ADS Non-         Interoperability Guidance
          Notification                       Compliance Notification
                                             Message
          Non-compliance notification        Non-Compliance            Functionally equivalent.
                                             Notification Tag (5)
3-230

        ATN ADS Non-Compliance       FANS 1/A ADS Non-              Interoperability Guidance
        Notification                 Compliance Notification
                                     Message
        Contract number              ADS Contract Request           In the FANS 1/A, the ADS
                                     Number                         contract request number is used
                                                                    to identify what type of contract
                                                                    the ADS Non Compliance
                                                                    Notification refers.
                                                                    Note. See Table 3-110Table
                                                                    3-110Table 3-110 for additional
                                                                    guideline on the contract
                                                                    number parameter.
        Emergency Urgency            No equivalent                  The emergency information is
                                                                    received from a FANS 1/A
                                                                    aircraft in ADS emergency
                                                                    reports through the
                                                                    establishment of an emergency
                                                                    contract.
        EPP Limitations              No equivalent                  FANS 1/A Intermediaite
         epp-tol-range-difference                                  Projected Intent request does not
                                                                    include tolerance range,
         epp-waypoint-difference
                                                                    waypoint, reporting/monitoring
         epp-reporting-window-                                     window.
           difference
         epp-monitoring-window-
           difference
        Ncn type contract not        Number of Message              The ATN ground system would
        supported                    Groups                         use the ADS number of message
                                     Note: The “Number of           groups received in the Non
                                     Message Groups”                Compliance Notification to
                                     corresponds to the number      identify the number of on-
                                     of on-request groups or        request groups or events which
                                     events that cannot be          cannot be provided.
                                     complied by the FANS 1/A
                                     aircraft.
                                     Each message group is
                                     identified by a
                                     group/Event Tag.
                                     The repetition of the First
                                     Message Group variable
                                     gives the list of on-request
                                     groups or events tags that
                                     are not in compliance.
                                                                                            3-231

ATN ADS Non-Compliance         FANS 1/A ADS Non-               Interoperability Guidance
Notification                   Compliance Notification
                               Message
    Demand-ncn                Group Tags               Equivalent for data block
   For each data block, “not   For each data block,     supported by both ATN and
   available” indication                                FANS1/A.
                                Block Tag
                                “not
                                   available/undefined”
                                   indication
                                Parameters (see below)
      Event-ncn               Event Tags               Equivalent for event supported
                                Event Tag              by both ATN and FANS1/A.
                                For each data block,
                                   “not
                                   available/undefined”
                                   indication
                                Parameters (see below)
      Periodic-ncn
                                                                                                    Comment [PF252]:
                                                                                                    PDR #194
   notsupportedReportType      Group Tags
                               For each data block,
                                Block Tag
                                “not
                                   available/undefined”
                                   indication
                                Parameters (see below)
   supportedReportingRate      No equivalent                   The default reporting rate
                               When indicating that the        applies.
                               FANS 1/A aircraft is not
                               able to support the
                               requested reporting rate,
                               First Message group value
                               contains the reporting rate
                               tag (11) and the first bit of
                               the following octet is set to
                               1.
3-232

        ATN ADS Non-Compliance   FANS 1/A ADS Non-             Interoperability Guidance
        Notification             Compliance Notification
                                 Message
           No equivalent         Parameters                    The FANS 1/A aircraft also
                                 For each message group        indicates which parameters
                                 (one for each on-request      within each optional group
                                 groups or event that cannot   cannot be provided.
                                 be complied with):            The ATN ground system may
                                 - number of parameters,       ignore the number of parameters
                                                               and parameter number provided
                                 - parameter number.
                                                               in the Non-compliance
                                 Note: The FANS 1/A            notification.
                                 aircraft also indicates
                                                               Use of these parameters is a
                                 which parameters within
                                                               local matter.
                                 each optional group cannot
                                 be provided.
                                                                                                    3-233

3.4.3.8   Parameter Range and Resolution
          Table 6-23 compares the ATN and FANS 1/A ADS-C variables with range and
          resolution.
               Table 3-110 ATN and FANS 1/A ADS variables with range and resolution

          ATN ADS variables with       FANS 1/A ADS variables       Interoperability Guidance
          range and resolution         with range and resolution
          Aircraft address             Airframe ID                  Equivalent
           24-bit ICAO ID              24-bit ICAO ID
          Aircraft Identification      Flight Identification        Equivalent
           String SIZE (2..8)          String SIZE (8)                                                    Comment [PF253]:
                                                                                                            DPDR ##157
          Air Speed:                   Mach:                        The FANS 1/A variable does not
          Either                          Range: 0 to 4.095        contain IAS.
           Mach                           mach                     The FANS 1/A mach variable has
                                                                   smaller range and finer resolution.
             Range: 0.5 to 4 mach         Resolution: 0.0005
                                           mach
             Resolution: 0.001
              mach
             Ias
             Range: 0 to 1100 knots
             Resolution: 1 knot
             Mach and Ias


          Contract Number              Contract Number              Equivalent.
           Range: 0.255                Range: 0.255

                                       Note. The value (255) is
                                       reserved for the emergency
                                       periodic contract.
          EPP Window:                  Tag (21): Aircraft Intent
           Time-interval:             (optional)
             Range: 15 min to 20       Aircraft Intent
              hours                         Projection Time
                                                                 The FANS 1/A variable has smaller
             Resolution: 15 minutes      Range 0 – 255 minutes range and finer resolution.
                                          Resolution: 1 minute
             Number of waypoints:
             Range: 1 to 128                                       No equivalent. The ground system
                                                                    shall be aware that only up to 10
             Resolution: 1
                                                                    way-points can be reported by the
                                                                    FANS 1/A aircraft and for a
                                                                    maximum projected time of 255
                                                                    minutes.
3-234

        ATN ADS variables with     FANS 1/A ADS variables       Interoperability Guidance
        range and resolution       with range and resolution
        Ground Speed               Ground Speed               The FANS 1/A variable has a
           Range: -50 to 2200        Range: 0 to 4095 knots different range;
            knots                     Resolution: 0.5 knot
           Resolution: 0.5 knot
        Heading                    True Heading                 The FANS 1/A variable has a
           Range: 0.05 to 360        Range: -180 to           different heading reference and a
            degrees                    179.912°                 finer resolution.
           Resolution: 1 degree      Resolution: 0.08789°
        Lateral Deviation          Lateral Deviation Change     The FANS 1/A variable has smaller
        Threshold                  Threshold                    range and finer resolution.
           Range: 0.5 to 150 NM      Range: 0.125 to 31.875
                                       NM
           Resolution: 0.5 NM        Resolution: 0.125
        Latitude:                  Latitude:                    When using the Predicted route
         Range: -90 to +90          Range: -90 to +90           group or the Intermediate Projected
                                                                Intent group, the ATN ground
         Resolution: 0.1 seconds    Resolution: 0.00172
                                                                system would process the FANS
                                    degrees
                                                                range and resolution for the
                                   Default value: -180 (with    Latitude variable.
                                   FOM set to 0)
                                                                When using the Latitude variable,
                                                                the ATN ground system would not
                                                                use the Latitude variable when set
                                                                to default value.
                                                                The ATN variable has finer
                                                                resolution.
                                                                The algorithm to convert range and
                                                                resolution is a local matter.
                                                                The translation of the default value
                                                                is a local matter.
                                                                                         3-235

ATN ADS variables with     FANS 1/A ADS variables       Interoperability Guidance
range and resolution       with range and resolution
Level:                     Altitude:                    When using the Predicted route
 Range: -750 to +100000     Range: -131,072 to +        group or the Intermediate Projected
                            131,068                     Intent group, the ATN ground
 Resolution: 10 feet
                                                        system would process the
                            Resolution: 4 feet
                                                        FANS 1/A Range and resolution for
                           Default value: -131,072      the Altitude variable.
                                                        When using the Level variable, the
                                                        ATN ground system would not use
                                                        the Altitude variable when set to
                                                        default value.
                                                        The FANS 1/A variable has greater
                                                        range and finer resolution.
                                                        The algorithm to convert range and
                                                        resolution is a local matter.
                                                        The translation of the default value
                                                        is a local matter.
Longitude:                 Longitude:                   When using the Predicted route
 Range: -180 to +180        Range: -180 to +180         group or the Intermediate Projected
                                                        Intent group, the ATN ground
 Resolution: 0.1 seconds    Resolution: 0.00172
                                                        system would process the FANS
                            degrees
                                                        Range and resolution for the
                           Default value: - 180 (with   Longitude variable.
                           FOM set to 0)
                                                        When using the Longitude variable,
                                                        the ATN ground system would not
                                                        use the Longitude variable when set
                                                        to default value.
                                                        The ATN variable has finer
                                                        resolution.
                                                        The algorithm to convert range and
                                                        resolution is a local matter.
                                                        The translation of the default value
                                                        is a local matter.
Modulus:                   Modulus:                     No additional interoperability
 Range: 1 to 255           Range: O to 255            guidance.
 Resolution: 1             Resolution: 1
                           Default value: 255
                           Value 0 is to de-select a
                           group.
Position accuracy:         Position accuracy:           FOM values other than 0 are not
 Range: 0 to 7             Range: 0 to 7              used by continental data link
                                                        services.
 Resolution: 1             Resolution: 1
                           Default value: 0
3-236

        ATN ADS variables with      FANS 1/A ADS variables        Interoperability Guidance
        range and resolution        with range and resolution
        Reporting rate:             Report interval:              When using the ADS Periodic
         Seconds:                    Scaling factor 01:           contract, the ATN ground system
                                                                  would process the FANS range and
           Range: 1 to 59              Range: 1 to 64
                                                                  resolution for the Reporting Interval
           Resolution: 1 second        Resolution: 1 second       variable.
         Minutes:                    Scaling factor 10:           When using Reporting Interval
           Range: 1 to 120             Range: 8 to 512            variable, the ATN ground system
           Resolution: 1 minute        Resolution: 8 seconds      would not use the Reporting
                                                                  Interval variable when set to default
                                     Scaling factor 11:
                                                                  value.
                                       Range: 64 to 4096
                                                                  FANS 1/A variable range is greater.
                                       Resolution: 64 seconds     The translation of the default value
                                                                  is a local matter.
        Track                       True Track Angle:             The FANS 1/A variable has a
           Range: 0.1 to 360          Range: -180 to            different heading reference and a
            degrees                     179.912°                  less resolution.
           Resolution: 0.05           Resolution: 0.08789°
            degree
        Vertical Rate               Vertical Rate:                The FANS 1/A variable has a larger
           Range: -30000 to           Range: -32752 to          range but a less resolution.
            30000 feet/min              32752 feet/min
           Resolution: 10 feet/min    Resolution: 16 feet/min


        Distance:                   Distance:                     When converting the Intermediate
          Range: 1 to 8000           Range: 0 to 8191.750         Projected Intent group to the
                                                                  extended projected profile group,
          Resolution: 1 nautical     Resolution: 0.125 NM
                                                                  the ATN ground system would
          mile                      Default value: 8191.750       process the FANS range and
        Note: Not used in the ATN   NM                            resolution for the distance
        INTEROP Standard.                                         parameter.
                                                                  When using the ETA variable, ATN
                                                                  ground system would ignore the
                                                                  default value of the ETA variable.
                                                                  ATN variable resolution more
                                                                  restrictive.
                                                                  The “Distance” variable is provided
                                                                  in the Intermediate Projected Intend
                                                                  group.
                                                                                       3-237

ATN ADS variables with     FANS 1/A ADS variables        Interoperability Guidance
range and resolution       with range and resolution
ETA:                       ETA:                          When using the ETA variable, the
 Time:                      Range: 0 to 16382            ATN ground system would convert
                                                         the ETA variable Hour-Minute-
  Hours:                    Resolution: 1 second
                                                         Second.
    Range: 0 to 23         Default value: 16,383 sec
                                                         When using the ETA variable, the
    Resolution: 1                                        ATN ground system would ignore
  Minutes:                                               the ETA variable when set to
    Range: 0 to 59                                       default value.
    Resolution: 1                                        In the FANS 1/A INTEROP
                                                         Standard, ETA is the estimated time
  Seconds:
                                                         to go from the timestamp provided
    Range: 0 to 59                                       in the Basic data group.
    Resolution: 1
Projection time:           Projected time:               FANS 1/A variable range is greater
 Range: 1 to 240            Range: 0 to 16382            and resolution is finer.
 Resolution: 1 minute       Resolution: 1 second
                           Default value: 16382
Timestamp:                 Timestamp:                    When using the Timestamp
 Date:                      Range: 0 to 3599.875         variable, the ATN ground system
                                                         would convert the timestamp
   Year:                    Resolution: 0.125 seconds
                                                         variable in Hour-Minute-Second.
    Range: 1996 to 2095    Default value: FOM set to 0
                                                         When using the Timestamp
    Resolution: 1 year                                   variable, the ATN ground system
   Month:                                                would ignore the Timestamp
    Range: 1 to 12                                       variable when FOM is set to 0.
    Resolution: 1 month                                  FANS 1/A timestamp variable
                                                         provides time seconds relative to
   Day:
                                                         current hour.
    Range: 1 to 31
                                                         The date variable can be provided
    Resolution: 1 day                                    using local source.
 Time:
   Hours:
    Range: 0 to 23
    Resolution: 1 hour
   Minutes:
    Range: 0 to 59
    Resolution: 1 minute
   Seconds:
    Range: 0 to 59
    Resolution: 1 second
3-238

        ATN ADS variables with        FANS 1/A ADS variables         Interoperability Guidance
        range and resolution          with range and resolution
        Not used in the ATN           True Track angle               When using the Intermediate
        INTEROP Standard.               Range: -180° to              Projected Intent group, the ATN
                                        +179,912°                    ground system would process the
                                                                     FANS Range and resolution for the
                                        Resolution: 0,08789°
                                                                     True Track angle variable.
                                      Default value: valid bit set
                                                                     When using the True Track angle
                                      to 1
                                                                     variable, the ATN ground system
                                                                     would ignore the True Track angle
                                                                     variable when set to default value.



3.4.4   Timers
        Table AP- 2Table AP- 2Table AP- 2 presents the ATN ADS technical timers and
        comparable FANS 1/A timers.
                                 Table AP- 2 ATN and FANS 1/A ADS timers

        ATN ADS Timers                 FANS 1/A ADS Timers            Interoperability Guidance
        t-DC-1 (demand contract        No equivalent.
        request)
        t-DC-2 (demand contract        No equivalent.
        request+report)
        t-EC-1 (event contract         No equivalent.
        request)
        t-EC-2 (cancel contract        No equivalent.
        request)
        t-PC-1 (periodic contract      No equivalent.
        request)
        t-PC-2 (periodic report)       No equivalent.
        t-PC-3 (cancel contract        No equivalent.
        request)
        t-LI-1                         No equivalent.
        The connection is closed by Inactivity timer               Not equivalent.
        the aircraft when no contract 16 minutes.
        is in place.
                                      If the connection has been
                                      established and does not
                                      have a valid contract for
                                      sixteen consecutive minutes,
                                      the FANS aircraft terminates
                                      the connection.
                                                                                        4-239


4       GROUND SYSTEMS PROVIDING                    ATS    DATALINK         SERVICES      TO
        BILINGUAL AIRCRAFT
        This section provides additional Interoperability Requirements to allow provision of
        DLIC and ACM services to bilingual aircraft transiting between two adjacent airspaces
        implementing different ATS Datalink technologies (i.e. ATN on one side and FANS 1/A
        on the other).

4.1     LOGON PROCEDURE FOR BILINGUAL AIRCRAFT
        In order to send a CMA Logon to the ground, any aircraft has to retrieve the ground CM
        address of the targeted ATN R-ATSU from an avionics database.
        This avionics database includes CM addresses of ATN ground systems that have been
        released as per Continental SPR Standard, § 2.2.1.
        IR-NEW1 : When a Logon has to be initiated following a manual Flight Crew request,
        FANS 1/A & ATN bilingual aircraft shall send :
           if the CM address of the designated ATSU has been successfully retrieved from
            an avionics database, a CMA Logon request message,
           otherwise, an AFN Contact essage using the 4-characters ICAO Facility
            Designation of the designated ATSU.
        Note : Consequently, an ATSP that is notifying provision of ATN capability (by
        releasing its CM Address by AIP) will use ATN capability by default with a FANS 1/A &
        ATN bilingual aircraft.

4.2     BILINGUAL AIRCRAFT TRANSITING FROM FANS 1/A ATSU TO ATN ATSU
4.2.1   ACM service
        As per DO-258A/ED-100A, the FANS 1/A T-ATSU will send the UM160 NEXT DATA                Comment [PF254]:
        AUTHORITY to the aircraft, designating the ATN R-ATSU.                                   COMMENT #1330

        Note: If the R-ATSU has a facilityDesignation with more than 4 characters (as allowed
        by ICAO definition), the FANS 1/A T-ATSU will not be able to send UM160 to the
        aircraft. Execution of ACM service is not available in this case.
        IRec1: In order to maximise their ability to provide seamless transition from
        adjacent FANS 1/A ATSUs (if any), ATN ground ATSUs should use 4-characters ICAO
        Facility Designations for ATS Datalink service.
        Note 1: ICAO format definition for Facility Designation parameter is a 4 to 8
        characters string. Proposed naming rule is a restriction to the ICAO definition.
        Note 2: This restriction is not an issue based on current European Naming and
        Addressing plan (all known operational ATSUs only use 4-characters identifiers).
        Nevertheless, this requirement should be endorsed so that this statement remains true
        for future ATS Datalink deployment.
4.2.2   DLIC Contact procedure
        DLIC Contact procedure will be performed according to Figure 4-1.
4-240

                      Figure 4        DLIC Contact procedure (FANS 1/A to ATN)




                                              2                               4
                                             AFN                      CM Start Confirm
                                           Response                   (Logonresponse)
                                                 5                3
                            1
                                                  AFN      CM Start Request
                        AFN Contact
                                             Complete      (LogonRequest)
                         Advisory




                                 T-ATSU                                   R-ATSU
                                    FANS                                      ATN


        The critical step in this operating method lies in aircraft behaviour after receipt of the
        AFN Contact Advisory (1) and before the sending of the CMA Logon Request (3).
        In compliance with FANS 1/A definition, the AFN Contact Advisory (1) message has to
        include the 7-Characters address of the R-ATSU, but does not include the ICAO ID of
        the R-ATSU.
        In compliance with ATN definition, the CMA Logon Request (3) message has to be sent
        to the ATN address of the R-ATSU.
        Basically, when it receives an AFN Contact Advisory, FANS 1/A aircraft is
        automatically sending an AFN Logon to the receiving ATSU, using the 7-characters
        address provided in the AFN Contact Advisory message.
        In this transfer (FANS to ATN), the intended behaviour would be to trigger a CMA
        Logon Request towards the R-ATSU instead of the AFN Logon.
        NIR-373        When a FANS 1/A T-ATSU knows that the R-ATSU is using ATN, the
        T-ATSU shall send an AFN Contact Advisory message to the aircraft using the 7-
        characters address field as follows :
           Characters [1-4] filled with the 4-characters ICAO Facility Designation of the R-
            ATSU and
           Characters [5-7] filled with the fixed value “ATN”.
                                                                                        4-241

        Note 1: As an example, a FANS1/A T-ATSU transferring an aircraft to the ATN
        Maastricht UAC ATSU would have to send an AFN Contact Advisory with “EDYYATN” in
        the Next ATC Center field.
        Note 2: If the R-ATSU has a facilityDesignation with more than 4 characters (as
        allowed by ICAO definition), the FANS 1/A T-ATSU will not be able to initiate DLIC
        Contact function with the aircraft.
        NIR-374        When a Bilingual aircraft receives an AFN Contact Advisory message
        with the last three characters of the 7-characters address field equal to the fixed
        value “ATN”, the aircraft shall initiate the sending of a CMA Logon to the ATSU
        designated by the Characters [1-4] of the Next ATC Center field of the AFN Contact
        Advisory.
        Note: Sending of the CMA Logon will be done using the same mechanism as for
        manual Logon initiation by the Flight Crew (i.e. using the ground CM address retrieved
        from avionics database).
        NIR-375       When a Bilingual aircraft is not able to initiate a CM Logon procedure
        that was requested by AFN Contact Advisory message, it shall close the DLIC
        Contact procedure by sending a negative AFN Response (Reason Code 5) to the
        FANS 1/A T-ATSU.
        Note: This could occur when the aircraft is not able to retrieve the ground CM address
        of the ATN R-ATSU.
        NIR-376       When a Bilingual aircraft is able to initiate a CM Logon procedure
        that was requested by AFN Contact Advisory message, it shall send a positive AFN
        Response (Reason Code 0) to the FANS 1/A T-ATSU.
        NIR-377         When a Bilingual aircraft receives a CMA Logon Response as part of
        a transaction initiated by a FANS transferring ATSU, it shall close the AFN Contact
        Advisory procedure by sending an AFN Complete including the result of the CM
        Logon.

4.3     BILINGUAL AIRCRAFT TRANSITING FROM ATN ATSU TO FANS 1/A ATSU
4.3.1   ACM Service
        As per DO-280B/ED-110B, the ATN T-ATSU will send the UM#160 NEXT DATA                    Comment [PF255]:
        AUTHORITY to the aircraft, designating the FANS 1/A R-ATSU.                              COMMENT #1330

        No additional Interoperability Requirement.
4.3.2   DLIC Contact procedure
        DLIC Contact procedure will be performed according to Figure 4-2.
4-242

                    Figure 5          DLIC Contact procedure (ATN to FANS 1/A)




                                               4                   2

                                          CM Start Conf     AFN Logon Request
                          1                                                              3
                                        (ContactResponse)
                   CM Start Request                                             AFN Logon Response
                   (ContactRequest)




                              T-ATSU                                            R-ATSU
                              ATN B1                                            FANS


        The critical step in this operating method lies in aircraft behaviour after receipt of the
        CMA Contact Request (1) and before the sending of the AFN Logon Request (2).
        In compliance with ATN definition, the CMA Contact Request (1) message has to
        include (only parameters of interest are presented here) the ATN address of the R-ATSU
        and the 4-8 characters ICAO ID of the R-ATSU as mandatory parameters.
        In compliance with FANS 1/A definition, the AFN Logon Request (2) message has to be
        sent to the 7-Characters AFN address of the R-ATSU.
        Basically, when it receives an CMA Contact Request, the ATN aircraft is automatically
        sending an CMA Logon to the receiving ATSU, using the ATN CM address provided in
        the CMA Contact Request message.
        In this transfer (ATN to FANS), the intended behaviour would be to trigger an AFN            Comment [PF256]:
        Logon Request towards the R-ATSU instead of the CMA Logon Request.                           COMMENT #1332

        NIR-378         When an ATN T-ATSU knows that the R-ATSU is using FANS1/A
        technology, it shall send an CMA Contact Request message containing:
           the 7-characters AFN address of the R-ATSU in the facilityDesignation of the
            contactRequest parameter,
           a default value (all bytes equal to 0) in the address field of contactRequest
            parameter.
                                                                              4-243

NIR-379         When a Bilingual aircraft receives an CMA Contact Request message
containing a default ATN address (i.e. all bytes equal to 0), it shall initiate the
sending of an AFN Logon to the R-ATSU designated by the facilityDesignation field of
the received contactRequest parameter.
Note: Sending of the AFN Logon will be done by the aircraft using the same
mechanism as for the AFN Contact Advisory procedure since the CMA Contact Request
message contains the 7-characters AFN address of the R-ATSU.
NIR-380         When a Bilingual aircraft receives a AFN Logon Response as part of
a transaction initiated by an ATN T-ATSU, it shall close the DLIC Contact procedure
by sending an CM Contact Response.
4-244




        This page intentionally left blank.
Appendix A MEMBERSHIP
This page intentionally left blank.
                                                                                  Appendix A
                                                                                         A-1
                                   Appendix A     MEMBERSHIP


               RTCA Special Committee - 214/EUROCAE Working Group - 78
            Air Traffic Services (ATS) Safety and Interoperability Requirements


                        FANS 1/A – ATS INTEROPerability Standard
Chairmen:
Appendix B HISTORY AND TERMS OF REFERENCE OF SC-214/WG-78
This page intentionally left blank.
                                                              Appendix B
                                                                     B-1
      Appendix B     HISTORY AND TERMS OF REFERENCE OF SC-214/WG-78

B.1   Introduction


B.2   Terms of Reference
Appendix C IMPROVEMENT SUGGESTION FORM
This page intentionally left blank.
                                                                                      Appendix C
                                                                                             C-1
                            Appendix C       IMPROVEMENT SUGGESTION FORM


Name:            Company:

Address:

City:                                                                                    State,
Province:
Postal Code, Country:                                                         Date:

Phone:                                                                        FAX:

Email:
Document: ED-                    /DO-                              Revision   Sec:
             Page:                               Line:
[ ]             Documentation error (Format, punctuation, spelling)
[ ]             Content error
[ ]             Enhancement or refinement
Rationale (Describe the error or justification for enhancement):




Proposed change (Attach marked-up text or proposed rewrite):
Appendix D
D-2




Please provide any general comments for improvement of this document:




Return completed form to:
RTCA, Inc.                              OR               EUROCAE
Attention: DO-                                           Attention:   Secretary-General  ED-___
1828 L Street, Northwest, Suite 805                      102        rue        Etienne     Dolet
Washington, D. C. 20036-4001 USA                         92240       Malakoff      -    FRANCE
Email: info@rtca.org                                     Email: eurocae@eurocae.com
                                      Appendix C
                                             C-3




This page intentionally left blank.
                                                                           Appendix D
                                                                                  D-1
           Appendix D   Interoperability Requirements Traceability Table1


    DO-305 IR              SC-214 FANS INTEROP IR

    IR-1                   IR- 1

    IR-2                   IR- 2

    IR-3                   IR- 3

    IR-4                   IR- 4




1
  Editor’s note: Table to be updated during final review and comment period after SC-214
.validation period.

								
To top