1 / 13

B1 Backwards Compatibility

B1 Backwards Compatibility. CSG October 2012, Long Beach, CA, USA F. Picard, EGIS AVIA. P-15 Maastricht June 12. CSG Actions from P15 P15-5 : Should B1 BC requiremens moved into a separate standard ?

hedva
Télécharger la présentation

B1 Backwards Compatibility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. P-15 Maastricht June 12 • CSG Actions from P15 • P15-5: Should B1 BC requiremensmovedinto 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 isrequired • Only 7 commentsreceived

  3. Action P15-5 • BC materialcanbemovedeasily 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 ImplementingRule • Identification of DL Configurations

  4. INTEROP In one glance A4 A2 A5 AircraftSystems Bi-lingual Accommodation Mono-lingual A1 A3 A7 FANS ATN B1 ATN B2 A6 ATN B2 FANS ATN B1 Provided Service FANS1/A B1 DL for FANS B1 DL B2 DL for B1 B2 DL B2 DL for FANS FANS ATN B1 FANS FANS Accommodation FANS FANS ATN B1 G2 G5 G4 ATN B1 ATN B2 ATN B2 ATN B2 ATN B2 ATN B1 FANS Mono-lingual ATN B2 G1 G3 G7 GroundSystems

  5. Data Link Configurations AIR GROUND G1FANS only G3 B1 IMP only G7 B2 only G2 B1 IMP Acc. FANS G4 B2 Acc. B1 IMP G5 B2 Acc. FANS • 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

  6. P15-6: Traceability to Standards

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

  8. GroundAcc. B2 / B1 IMP Uplink Messages B1 B1 only(removed, replaced) N/A (never sent) N/A (never sent) B1IMP(removed, replaced) B1 IMP A3 ATN B1 AT B2 FANS ATN B1 B1IMP B2(kept) B2 Sent = received B2 DL for B1 G7 ATN B1 FANS ATN B1 Sent as free text B1 B2 (kept) ATN B2 ATN B2 ATN B2 B2 ONLY (new) Sent as free text B2 ONLY (replacement) Sent as free text or B1 IMP

  9. GroundAcc. B2 / B1 IMP Downlink Messages B1 B1 only(removed, replaced) Error (never sent) B1IMP(removed, replaced) B1 IMP Translatedinto DMR A3 ATN B1 AT B2 FANS ATN B1 B1IMP B2(kept) B2 Received = sent B2 DL for B1 G7 ATN B1 FANS ATN B1 Error (never sent) B1 B2 (kept) ATN B2 ATN B2 ATN B2 B2 ONLY (new,) Never received B2 ONLY (replacement) Never received

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

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

  12. P15-7: ASN.1 B1 B1 B2 B2 B2 • Solution #1: One single ASN.1 Module in PU-20 • including all B1 and B2 messages • Usedpartially by B2 onlysystems • Eachimplementorextract the relevant part • Solution #2: Two ASN.1 Modules in PU-20 • One B2 only ASN.1 PU-20 used by B2 onlysystems • One B1 + B2 in Acc. used by B2 systemsaccommodating B1 IMP • Consistency issue

  13. Open Issue • 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?

More Related