1 / 8

EUROCAE WG-78 / RTCA SC-214 WP 1 Sub-Group Maastricht, 8-12 June 2009

EUROCAE WG-78 / RTCA SC-214 WP 1 Sub-Group Maastricht, 8-12 June 2009. WP1 Progress Report. WP1 Issues. ACM Issues Ground behavior upon receipt of downlink message before ground enabling CPDLC : Multiple & Local choices : Accept the message and do one of the following :

carr
Download Presentation

EUROCAE WG-78 / RTCA SC-214 WP 1 Sub-Group Maastricht, 8-12 June 2009

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. EUROCAE WG-78 / RTCA SC-214 WP 1 Sub-Group Maastricht, 8-12 June 2009 WP1 Progress Report

  2. WP1 Issues ACM Issues • Ground behavior upon receipt of downlink message before ground enabling CPDLC : Multiple & Local choices : • Accept the message and do one of the following : • * When the message permits a response, send UM2 REQUEST DEFFERED and process the message when CPDLC is enabled; or • * When the message permits a response, send UM1 STANDBY and process the message when CPDLC is enabled; or • * Just process the message when CPDLC is enabled; • Reject the message and do one of the following : • * When the message permits a response, send UM0 UNABLE followed by message element UM183 [CPDLC TRANSFER IN PROGRESS – REPEAT REQUEST AFTER COMPLETION]; or • * send an ERROR followed by message element UM183 [CPDLC TRANSFER IN PROGRESS – REPEAT REQUEST AFTER COMPLETION]. • New : Confirmation of Monitored Frequency (in case of UM120 Monitor) => To be discussed during next Meeting => Position paper will be prepared by FAA for Langen Meeting OR

  3. WP1 Issues TIMER Issues • Cancellation of Ground TTr/Airborne TTs (when implemented) upon issuing an “Uplink” STANDBY • No timer reset • Applicable each time a STANDBY is sent by the Ground • Ground System Behavior upon a TTs Time-out • Plenary#7 Decision to only warn the ATCO is not longer valid • The dialogue is closed technically (as per ED120/ED110) DCL Issues • Resolution of Matt’s Comments on DCL Messages/Parameters • DCL Template still under discussion

  4. WP1 Issues D-TAXI Issues • D-ATXI Graphic data must not be sent in a standalone message (without D-TAXI Route Clearance) • Two solutions have to be assessed : • Graphics information could be passed as parameter in each message element of the D-TAXI Clearance : • TAXI [taxi route + graphic data] • HOLD SHORT [ground position + graphic data] • EXPECT TAXI [taxi route + graphic data] • Graphics information could be passed as a message element of the D-TAXI Clearance. • TAXI [taxi route] • HOLD SHORT [ground position] • EXPECT TAXI [taxi route] • + Graphic TAXI Route element • No more than two D-TAXI Route Clearances and 1 D-TAXI Graphic data in one message • D-TAXI Graphic ORs has been reviewed => New release for August Meeting • D-TAXI OSA/OPA will be ready for next Plenary Meeting

  5. WP1 Issues OPA Issues • Allocation of RCP Values • Proposal to use the “Exponential” Model for allocation => Need for further validation (e.g. based upon experience from MUACC) • Specifying TIMER Values • Need for a set of values per Application (not per domain, …) to cover different Operational situations • For ground TTs, 4 values have been agreed for CPDLC : 45sec, 100sec, 180sec, 300sec • It is a local choice to select the Ground TTs value according to the operational situation and the nature of the message to be sent. • Values have to be assessed during the Validation process • No need to mention Airborne TTs within ISPR. It is a local airborne choice to have such a pilot warning • Remaining issue : Need to assess value(s) Ground TTr • Specifying (Technical) LATENCY Value • The agreed value is 20s for the Ground/Airborne sides • Value has to be assessed during the Validation process

  6. What’s next ….. Work Organization • Jane for “Weather” & CPDLC Material • Thierry for ADS-C Material Remaining WP1 Issues for Next Meeting • D-TAXI Graphics OSD (Christian) / OSA / OPA Who is in charge of doing it ? • Confirmation of Monitored Frequency (in case of VCI is Monitor) (?) • Values for Ground TTr (Wim/Kathy) • DCL Template consolidation (Matt) • ATS Function definition (Tom)

  7. WP1/WP2 Work Schedule Overview August Meeting (24-28 Aug.) Toulouse Plenary #8 (21-24 Sep.) Seattle Meeting (26-30 Oct.) Albuquerque Meeting (14-18 Dec.) D-TAXI Graphics OSD Resolution WP1 Issues WP1 I SPR WP1 OPA WP2 ISPR Comments By 7th Dec. 16 Nov. D-TAXI Graphics OSA/OPA WP2 ISPR Review Consolidation of WP2 ISPR Resolution of WP2 ISPR Comments RedLine Full WP2 SPR Integration – version F Initial Integration of OSD (4DTRAD/FLIPINT/WEATHER Initial Integration of WP2 ISPR WP2 I SPR OSA for 4DTRAD/FLIPINT/WEATHER OPA for 4DTRAD/FLIPINT/WEATHER

  8. MoM for Maastricht WP1 Meeting will be sent by the end of the week …Have safe trip back. See you in Langen! 8

More Related