1 / 28

SC-214/WG-78 SG-3 ATN INTEROP Standard

SC-214/WG-78 SG-3 ATN INTEROP Standard. Plenary 6: 8 – 12 December 2008 Toulouse, France. About this presentation. Work has started in February 2008 (Plenary #3, Phoenix) 6 meetings and 5 telecons 360 SG-3 comments addressed (INTEROP_comment.xls) Version 0.12 available for SC/WG review

jalene
Download Presentation

SC-214/WG-78 SG-3 ATN INTEROP Standard

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. SC-214/WG-78 SG-3ATN INTEROP Standard Plenary 6: 8 – 12 December 2008Toulouse, France

  2. About this presentation • Work has started in February 2008 (Plenary #3, Phoenix) • 6 meetings and 5 telecons • 360 SG-3 comments addressed (INTEROP_comment.xls) • Version 0.12 available for SC/WG review • Topics addressed • At Plenary #5: Question on the differences between ED-110A / SC-214 INTEROP documents • Open Issues • Remaining tasks

  3. Main changes with ED-110B/DO-280B • A different set of DL Continental services, Oceanic services addressed • Synchronization of OSD and INTEROP production • Technical control over the message sets • 2nd generation of standards: backwards compatibility addressed

  4. ED-110B/DO-280B to ED/DO-YYY 1 – INTRODUCTION 2 – GENERAL ATN REQUIREMENTS 3 – REQUIREMENTS ON ATN APPLICATIONS 4 – REQUIREMENTS ON CONTINENTAL DL SERVICES ANNEX A – Doc 9705 Modifications ANNEX B – P/OICS for ATN Baseline 1 ANNEX C – D-ATIS template 1 – INTRODUCTION 2 – GENERAL ATN REQUIREMENTS 3 – REQUIREMENTS ON ATN APPLICATIONS 4 – REQUIREMENTS ON CONTINENTAL DL SERVICES 5 – REQUIREMENTS ON OCEANIC SERVICES 6 – REQUIREMENTS FOR ED-110B/DO-280B BACKWARDS COMPATIBILITY ANNEX A- Standard Modifications ANNEX B – ASN.1 MESSAGE DEFINITION ED-110B/DO-280B ED/DO-YYY

  5. INTRODUCTION 1 – INTRODUCTION 1.1 Purpose 1.2 Scope 1.3 Relationships to Other Documents 1.4 Description of This Document 1.5 References • Continental DL services: Enhanced (DLIC, ACM, ACL, AMC), New (D-TAXI, D-OTIS), Removed (DSC, FLIPCY, D-ATIS) • Oceanic services: DLIC, CPDLC-based (CE, CT, CT, CRD, IER, PR) • ADS-C based services put on hold • New Operational baseline (environment and operating methods) defined in SC-214/WG-78 OSD and ED-122/DO306 • ATN specific

  6. INTRODUCTION 1 – INTRODUCTION 1.1 Purpose 1.2 Scope 1.3 Relationships to Other Documents 1.4 Description of This Document 1.5 References • Continental DL services: Enhanced (DLIC, ACM, ACL, AMC), New (D-TAXI, D-OTIS), Removed (DSC, FLIPCY, D-ATIS) • Oceanic services: DLIC, CPDLC-based (CE, CT, CT, CRD, IER, PR) • ADS-C based services put on hold • Operational baseline (environment and operating methods) defined in SC-214/WG-78 OSD and ED-120 • ATN specific Section complete – Ready for review No issue

  7. ATN GENERAL 2 – ATN GENERAL REQUIREMENTS 2.1 Main Components 2.2 Functions of ATN Applications and CPDLC Message Set 2.3 ATN Standards 2.4 Known Defects to Standards 2.5 General Requirements • ATN Technical baseline : ATN Internet Communication Services in Doc 9705, ATN Applications in Doc 9880 (CM, CPDLC) and RTCA/EUROCAE Doc (PM-FIS) • Definition of CPDLC Message Set • 2 versions: v1 (ED110-B implementations), v2 continental & oceanic (SC-214/WG-78 and ED-120/DO-30x SPR) • 4 combinations: used in v1 and v2, v1 only, v2 only, not used

  8. ATN GENERAL 2 – ATN GENERAL REQUIREMENTS 2.1 Main Components 2.2 Functions of ATN Applications and CPDLC Message Set 2.3 ATN Standards 2.4 Known Defects to Standards 2.5 General Requirements • ATN Technical baseline : ATN Internet Communication Services in Doc 9705, ATN Applications in Doc 9880 (CM, CPDLC) and RTCA/EUROCAE Doc (PM-FIS) • CPDLC Message Set • 2 versions: v1 (Link 2000+), v2 continental & oceanic (SC-214/WG-78 and ED-120/DO-30x SPR) • 4 message types identified: used in v1 and v2, v1 only, v2 only, not used • Section complete – Ready for review • PM-FIS specification (V1-1) developed by SG-3 • Validation of PM-FIS specification required (Jan to Mar 09) • Liaison with ICAO for inclusion of PM-FIS in Doc 9880

  9. ATN CM 3 – REQUIREMENTS FOR ATN APPLICATIONS 3.1 CM 3.2 (ADS-C) 2.3 CPDLC 2.4 FIS • CM • Version negotiation at logon (v1=Link2000+, v2=SC-214/WG-78) • CM-logon message modified and CM-update function added to support air-initiated applications (D-OTIS)

  10. ATN CM 3 – REQUIREMENTS FOR ATN APPLICATIONS 3.1 CM 3.2 (ADS-C) 2.3 CPDLC 2.4 FIS Section complete – Ready for review No Issue

  11. ATN CPDLC 3 – REQUIREMENTS FOR ATN APPLICATIONS 3.1 CM 3.2 (ADS-C) 2.3 CPDLC 2.4 FIS • CPDLC • ED110B/DO-280B Technology independent requirements moved to OSD • Time, timestamp, message display guidance, CPDLC ON/OFF management, concatenation rules, message construction rules (UM79/80 for ACL, UM73 DCL, D-TAXI), parameter construction rules (routeInformation, position) • ATN dependent requirements • Error management, usage of ATN CPDLC service primitives and parameters, protected mode management, extensibility feature • DSC related requirements are deleted

  12. ATN CPDLC 3 – REQUIREMENTS FOR ATN APPLICATIONS 3.1 CM 3.2 (ADS-C) 2.3 CPDLC 2.4 FIS • Section almost complete – Ready for review • Management of Resp (N) Messages (risk to associate an error response to a wrong UM)

  13. ATN FIS 3 – REQUIREMENTS FOR ATN APPLICATIONS 3.1 CM 3.2 (ADS-C) 2.3 CPDLC 2.4 FIS • FIS • ED110B/DO-280B Technology independent requirements moved to OSD: • Time, timestamp, message display guidance, NOTAMs filtering process, • ATN dependent requirements • Error management, usage of ATN defined reject/abort reasons, usage of ATN FIS service primitives and parameters, protected mode management, extensibility feature, definition of user defined data (FISService, User Defined Reject Reason), security & priority management

  14. ATN FIS 3 – REQUIREMENTS FOR ATN APPLICATIONS 3.1 CM 3.2 (ADS-C) 2.3 CPDLC 2.4 FIS Section complete – Ready for review

  15. DLIC services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS • DLIC • CM-logon result / Flight plan correlation decoupled • New Operating Table for CM-update

  16. DLIC services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS Section complete – Ready for review

  17. CPDLC-based Services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS • Editorial changes • All requirements on timer management in a single section • All common requirements grouped in “Elements of Procedure” (Management of open dialogues, NDA, VCI, CDA, LACK disabling, …) • No “shall” requirements in operating tables • ACM • New cases added for cover all CPDLC ON/OFF situations • New message transactions (flight crew change of frequency request, deferred instruction to change frequency, monitored frequency confirmation)

  18. CPDLC-based Services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS • ACL • Ground automated generation of messages allowed • Extended message set supported • Enhanced existing messages (timesec, BLOCK LEVEL, free text) • AMC • Definition of a new CHECK STUCK MICROPHONE message • DCL (New) • Definition of optimized Departure Clearance Request and Departure Clearance messages • D-TAXI (New) • Definition of Downlink and Uplink Messages • 4 operating methods: information/clearance request/pushed

  19. CPDLC-based Services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS • Section not complete • ACM: Monitored Frequency Confirmation scenario • Definition of messages for DCL and D-TAXI • Timer management

  20. FIS-based Services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS • D-OTIS (New) • Replace D-ATIS • 5 sub-services: ATIS, NOTAM, VOLMET, OTIS, AIB • 4 operating methods: demand/update contract for single/dual type of information

  21. FIS-based Services 4 – REQUIREMENTS FOR CONTINENTAL DATA LINK SERVICES 4.1 DLIC 4.2 to 4.7 CPDLC-based services: ACM, ACL, AMC, DCL, D-TAXI 4.8 to 4.9 FIS-based services: D-OTIS Section complete – Ready for review

  22. Oceanic Services 5 – REQUIREMENTS FOR OCEANIC DATA LINK SERVICES 5.1 DLIC 5.2 to 5.4 Connection management services: CE, CT, TC 5.5 to 4.9 Transaction management services: CRD, IER • Oceanic Services (New) • Oceanic services are “implicitly” supported by SC-214 services • ACM = CE + CT + TC • ACL = CRD + IER + PR • Oceanic message set required by ED-120 supported by SC-214 message set CE: Connection Establishment, CT: Connection Termination, TC: Transfer of Control, CRD: Clearance Request and Delivery, IER: Information Exchange and Reporting, PR: Position Reporting

  23. Oceanic Services 5 – REQUIREMENTS FOR OCEANIC DATA LINK SERVICES 5.1 DLIC 5.2 to 5.4 Connection management services: CE, CT, TC 5.5 to 4.9 Transaction management services: CRD, IER • Section complete – Ready for review • ADS-C based services will be addressed in WP2 (2009) CE: Connection Establishment, CT: Connection Termination, TC: Transfer of Control, CRD: Clearance Request and Delivery, IER: Information Exchange and Reporting, PR: Position Reporting

  24. BACKWARDS COMPATIBILITY 6 – BACKWARDS COMPATIBILITY TO ED-110B IMPLEMENTATIONS 6.1 Context 6.2 to 6.3 Approaches for CM and CPDLC 6.4 to 6.6 Uplink/Downlink Messages & Parameters Translation Rules • Assumptions • Compatibility provided to known ED-110B implementations (Reference: Specification on Data Link Services to support Data Link IR) • DSC and DCL messages not implemented • 2 backwards compatibility schema • SC-214 Aircraft (to Link Ground System) act as a Link Aircraft • SC-214 Ground System (to Link Aircraft) provide SC-214 services as much as possible • Free text used for clearances except • Loadable clearances • DL Response not supported (e.g. REPORT)

  25. BACKWARDS COMPATIBILITY 6 – BACKWARDS COMPATIBILITY TO ED-110B IMPLEMENTATIONS 6.1 Context 6.2 to 6.3 Approaches for CM and CPDLC 6.4 to 6.6 Uplink/Downlink Messages & Parameters Translation Rules • Section complete – Ready for review • Assumptions to be validated • Proposed syntax for FREE TEXT to be validated

  26. ASN.1 Definition 7 – ANNEX MESSAGE DEFINITION 7.1 CPDLC Message Set 7.2 to 7.7 DATIS, METAR, NOTAM, OTIS, VOLMET and AIB Message sets • Defined based on • Range and Resolution Tables in OSD for CPDLC services • Templates for FIS services • Reference for the new CPDLC message numbering

  27. ASN.1 Definition 7 – ANNEX MESSAGE DEFINITION 7.1 CPDLC Message Set 7.2 to 7.7 DATIS, METAR, NOTAM, OTIS, VOLMET and AIB Message sets • Section almost complete – Ready for review • Consolidation of templates required (ATIS and VOLMET/TAF ok, NOTAMs in 2009) • MET information are as per ICAO Annex 3 • Non ICAO units (e.g. Statute Miles / Visibility, Feet / RVR) are provided as alternative units

  28. Conclusion • Proposal to issue ATN INTEROP Version V0.13 End December aligned with OSD output Plenary #6 • Formal Comment Period January/February 09 • Issue Version 1.0 at Plenary #7 March 09 • Validation Period : March – September 09

More Related