Title: DFIS - Late demand contract rejection PDR Reference: M2030002 Originator Reference: SARPs Document Reference: 2.4.1.1.5, table 2.4.5-7, table 2.4.5-6a, Figure 2.4.5-4, table 2.4.5-1, 2.4.5.3.1, 2.4.5.3.5.4.2, 2.4.5.3.6.5.2, 2.4.7.2.1.1.2, 2.4.7.3.5. Status: RESOLVED Impact: B PDR Revision Date: 13/03/02 (PROPOSED -> RESOLVED) 12/03/02 (SUBMITTED -> ACCEPTED -> PROPOSED) PDR Submission Date: 12/03/2002 Submitting State/Organization: SGA2/4 - Phuket meeting Submitting Author Name: Submitting Author E-mail Address: Submitting Author Supplemental Contact Information: SARPs Date: Edition 3 SARPs Language: English Summary of Defect: When a DFIS ground system has responded to a DFIS demand contract establishment request with a positive acknowledgement, there is no way for the ground system to respond negatively later on, if no report is available. This might be the case when the DFIS ground system thinks that the requested information will be shortly made available but the information can not be retrieved. It is proposed to allow the FIS-ground-user to invoke the FIS-demand-contract response (rejected) after the invocation of the FIS-demand-contract response (positive ack). Note. There is no problem with the FIS update contract since the FIS-ground-user is allowed to invoke the FIS-update-cancel service after the sending of a positive ack and before the sending of the first FIS report. Assigned SME: SV2 SME Proposed SARPs amendment: DC1/ At the end of section 2.4.1.1.5, Note a) 3) ii) A) add : DC2/ table 2.4.5-7, cell (DC-demand-contract rsp(rejected), DC-G-ACTIVE) replace: Not permitted by: LI-Send-Normal [FISReject]APDU DC-G-IDLE DC3/ table 2.4.5-6a, cell ([FISReject] APDU, DC-A-ACTIVE) replace: AB-abort ("sequence abort") DC-A-IDLE By: Stop t-DC-2 If last FIS contract start t-INACTIVITY DC-demand-contract cnf DC-A-IDLE DC4/ Rename Figure 2.4.5-4 to Figure 2.4.5-4a and add Figure 2.4.5-4b: <- FIS-demand-contract req FIS-demand-contract-ind <- FIS-demand-constract-rsp (positive acknowledgement)-> -> FIS-demand-contract-cnf (positive acknowledgement) FIS-demand/-contract-rsp (rejected) -> -> FIS-demand-contract-cnf (rejected) add title: Figure 2.4.5-4b Use of the FIS-demand-contract service with contract reject after a positive ack DC5/ In table 2.4.5-1 FIS Service Provider Timers, Replace in cell (t-DC-2, stop event): FIS-report-ind By: FIS-report-ind or FIS-demand-contract-cnf (rejected) after a FIS-demand-contract-cnf (positive acknowledgement) DC6/ In 2.4.5.3.1 note 4, add d) the FIS-air ASE invokes a FIS-demand-contract confirmation (rejected) following a FIS-demand-contract confirmation (positive acknowledgement), renumber "d) to i)" as "e) to j)" DC7/ In 2.4.5.3.1 note 5, add c) the FIS-ground-ASE receives receives a FIS-demand-contract-response (rejected) following a FIS-demand-contract confirmation (positive acknowledgement). Renumber "c) to i)" as "d) to j)" DC8/ add section 2.4.5.3.5.4.2 as follows: 2.4.5.3.5.3.2 If in the DC-A-ACTIVE state, the ground FIS UC module shall: a) stop timer t-DC-2, b) request the FIS HI module to invoke a FIS-demand-contract confirmation with the following parameters: 1) the parameter containing the information which has been received as the APDU-element, and 2) the parameter, containing the abstract value "rejected", and 1) the parameter containing the information which has been received as the APDU-element,and c) enter the DC-A-IDLE state. DC9/ add section 2.4.5.3.6.5.2 as follows: 2.4.5.3.6.5.2 If in DC-G-ACTIVE state, the ground FIS DC module shall: a) create a FISUplinkAPDU [FISReject] APDU with an APDU-element based on the value of the and the parameters, b) request the LI module to send the APDU to the FIS-air-ASE, and c) enter the DC-G-IDLE state. DC10/ add section 2.4.7.2.1.1.2 2.4.7.2.1.1.2 When talking to a version 1 FIS air system, the FIS-ground-user shall be prohibited from a) sending an FIS-demand-contract response with the parameter set to "rejected" after an FIS-demand-contract response with the parameter set to "positive acknowlegement" DC11/ add new section 2.4.7.3.5 and renumber subsequent sections: 2.4.7.3.5 Upon receipt of a FIS-demand-contract-indication and the invocation of a FIS-demand-response (positive acknowledgement), if the FIS-ground-user is not able anymore to send the FIS report, it shall invoke the FIS-demand-response with the parameter set to the abstract value "rejected". Impact on Interoperability: No. On the basis of application information exchanged during CM, a version 2 DFIS ground system user is supposed to not send a FIS-demand-contract response (rejected) after a FIS-demand-contract response (positive ack). If it does, the aircraft will abort the FIS abort with reson "sequence error". Proposed CAMAL amendment: tbd. PDR Validation Status: Paper Validation OKI implementation ? SME Recommendation to CCB: - CCB Decision: CCB-15 (Phuket - 13/03/02): RESOLVED