B1 Backwards Compatibility CSG October 2012, Long Beach, CA, USA F. Picard, EGIS AVIA

 CSG Actions from P15  P15-5 : Should B1 BC requiremens moved into a separate standard ?  P15-6 : CSG to provide a table(s) to correlate each possible operational configuration with the applicable Interoperability document sections(s). (This may include updating the “red/blue/green” diagram).  P15-7 : How does the CPDLC ASN.1 reflect the BC requirements ?  A CSG review of INTEROP Part 3 is required  Only 7 comments received P-15 Maastricht June 12

 BC material can be moved easily in a separate document, annex or stay in PU-20  2 sections have to move into PU-20 Part 1 (Introduction)  Identification of DL Systems  FANS 1/A  ED-100A / DO-258A  B1  ED-110B / DO-280B  IMP B1  European SES DL Implementing Rule  Identification of DL Configurations Action P15-5

Provided Service FANS FANS1/A Mono-lingual Ground Systems FANS ATN B1 ATN B2 FANS ATN B2 ATN B1 B1 DL ATN B2 B2 DL Bi-lingual B2 DL for B1 ATN B2 ATN B1 B2 DL for FANS ATN B2 FANS INTEROP In one glance Aircraft Systems ATN B2 ATN B1 Accommodation B1 DL for FANS ATN B1 FANS Accommodation

AIR  A1 FANS only  A3 B1 IMP only  A7 B2 only  A2 B1 IMP + FANS  A5 B2 + FANS  A4 B2 Acc. B1 IMP + FANS  A6 B2 Acc. B1 IMP GROUND  G1 FANS only  G3 B1 IMP only  G7 B2 only  G2 B1 IMP Acc. FANS  G4 B2 Acc. B1 IMP  G5 B2 Acc. FANS Data Link Configurations

P15-6: Traceability to Standards

B1B1 B1IMPB1IMP B2B2 B2 ONLY (new) B1 B2 ( kept) B1 only (removed, replaced) B1IMP (removed, replaced) B1IMP B2 (kept) B2 ONLY (replacement) Rules per Message Types 106 UM, 61 DM 25 UM, 9 DM 25 UM, 14 DM 53 UM, 27 DM 74 UM, 33 DM 87 UM, 40 DM

Uplink Messages B1B1 B1IMPB1IMP B2B2 B2 ONLY (new) B1 B2 ( kept) B1 only (removed, replaced) B1IMP (removed, replaced) B1IMP B2 (kept) B2 ONLY (replacement) FANS ATN B1 ATN B2 FANS ATN B2 ATN B1 AT B2 ATN B1 B2 DL for B1 ATN B2 ATN B1 N/A (never sent) Sent = received Sent as free text Sent as free text or B1 IMP Ground Acc. B2 / B1 IMP

Downlink Messages B2 ONLY (new,) B1 B2 ( kept) B1 only (removed, replaced) B1IMP (removed, replaced) B1IMP B2 (kept) B2 ONLY (replacement) B1B1 B1IMPB1IMP B2B2 Error (never sent) Received = sent Error (never sent) Never received FANS ATN B1 ATN B2 FANS ATN B2 ATN B1 AT B2 ATN B1 B2 DL for B1 ATN B2 ATN B1 Translated into DMR Ground Acc. B2 / B1 IMP

Uplink Messages B2 ONLY (new,) B1 B2 ( kept) B1 only (removed, replaced) B1IMP (removed, replaced) B1IMP B2 (kept) B2 ONLY (replacement) B1B1 B1IMPB1IMP B2B2 Error (never received) B1 IMP supported Sent = received N/A (never sent) FANS ATN B1 B1 DL ATN B2 ATN B1 Air Acc. B2 / B1 IMP

Downlink Messages B2 ONLY (new,) B1 B2 ( kept) B1 only (removed, replaced) B1IMP (removed, replaced) B1IMP B2 (kept) B2 ONLY (replacement) B1B1 B1IMPB1IMP B2B2 N/A (never sent) Supported Sent = received N/A (not B1 IMP) FANS ATN B1 B1 DL ATN B2 ATN B1 Air Acc. B2 / B1 IMP Sent as B1 IMP Error (not B1 IMP1)

P15-7: ASN.1 B1B1 B2B2  Solution #1: One single ASN.1 Module in PU-20  including all B1 and B2 messages  Used partially by B2 only systems  Each implementor extract the relevant part  Solution #2: Two ASN.1 Modules in PU-20  One B2 only ASN.1 PU-20 used by B2 only systems  One B1 + B2 in Acc. used by B2 systems accommodating B1 IMP  Consistency issue B1B1 B2B2 B2B2

 Rules for accommodating REPORT REQUEST from the ground when the datalink REPORT is not supported by the B1 A/C:  The ground sends a REPORT REQUEST  The Pilot responds by WILCO and the dialogue is “technically” closed  When conditions are met, the flight crew will provide the REPORT using voice  Is acceptable to initiate a dialogue via Datalink and to provide the requested “Data” via Voice? Open Issue