Title: FIS - Update Contract cancelled during contract establishment PDR Reference: 97110003 Originator Reference: cancelfrompending SARPs Document Reference: FIS SARPs, Sections 2.4.5.3.7.1, 2.4.5.3.7.2, 2.4.5.3.7.3.1, 2.4.5.3.7.4.1, 2.4.5.3.7.5.1, 2.4.5.3.7.6.2, 2.4.5.3.7.7.2, and Tables 2.4.5-8/a and 2.4.5-9/b Status: ADOPTED PDR Revision Date: 16/12/97 (ACCEPTED -> PROPOSED -> RESOLVED) 08/12/97 (SUBMITTED -> ACCEPTED) PDR Submission Date: 27/11/97 Submitting State/Organisation: Aerospatiale Submitting Author Name: Chapirot, L Submitting Author E-mail Address: lucie.chapirot@avions.aerospatiale.fr Submitting Author Supplemental Contact Information: SARPs Date: IV2.1, October 97 SARPs Language: English Summary of Defect: Assumption: the underlying dialogue is already established. The FIS-air-user invokes subsequently the FIS-update-contract request and the FIS-cancel-update request. The two following scenarios are not supported by the current FIS protocol (it is specified that the FIS-air-ASE shall abort the contracts). First scenario: Air Ground FIS-update-contract Request -----------> -----------> FIS-update-contract Indication FIS-cancel-update-contract FIS-update-contract Request -----------> <---------- Response (Accept) ----------> FIS-cancel-update-contract Indication FIS-cancel-update-contract Confirm <----------- Second scenario: Air Ground FIS-update-contract Request -----------> -----------> FIS-update-contract Indication FIS-cancel-update-contract FIS-update-contract Request -----------> <----------- Response (Reject) FIS-cancel-update-contract Confirm <----------- SME Comment: Air ASE ------- a) The SARPs state that if an air UC module being in the UC-A-CANCEL state receives an [FISAccept]APDU or an [FISReject]APDU, it shall abort the FIS contracts with the reason "sequence error". It is correct when the UC module went to the UC-A-CANCEL state from the UC-A-ACTIVE state. It is correct not when the UC module went to the UC-A-CANCEL state from the UC-A-PENDING state. In that case, the incoming APDU shall be accepted but not provided to the user and the UC module shall stay in the same state waiting the completion of the cancel procedure. b) The SARPs state that if a UC module being in the UC-A-CANCEL state receives an [FISReport]APDU, it shall invoke the UC-report indication primitive. It is correct when the UC module went to the UC-A-CANCEL state from the UC-A-ACTIVE state. It is not correct when the UC module went to the UC-A-CANCEL state from the the UC-A-PENDING state. In that case, the FIS contracts shall be aborted with the reason "sequence error". c) In addition, once the FIS-air-user has invoked the FIS-cancel-update-contract request, he should not received anything but the FIS-cancel-update-contract confirmation (with the exception of the abort primitives). Ground ASE ---------- d) There is an inconsistency between the textual and the tabular specification. Requirement 2.4.5.3.8.8.2 is not correctly reflected in state table 2.4.5-9/b. e) There are several typos in Table 2.4.5-9/b. The third column should have the title UC-G-ACTIVE instead of UC-G-CANCEL. The three occurrences of UC-A-IDLE should read UC-G-IDLE. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: It is proposed to track the previous state from which the FIS-air-ASE came to the UC-A-PENDING. 1[a,b]/ Add the following note after 2.4.5.3.7.1 in italics: Note. The air FIS UC Module has a boolean variable named CANCELFROMPENDING. 2[a,b]/ Add a new requirement 2.4.5.3.7.2 and change the number of the following requirements: 2.4.5.3.7.2 On initiation, CANCELFROMPENDING shall be set to FALSE. 3[a,b]/ Change 2.4.5.3.7.7.2 d) and e) from: d) start the t-UC-3 timer, and e) enter the UC-A-CANCEL state. To: d) start the t-UC-3 timer, e) set CANCELFROMPENDING to be TRUE, and f) enter the UC-A-CANCEL state. 4[a,b]/ Change in table 2.4.5-8/a in the cell (UC-cancel-update-contract req, UC-A-PENDING) start t-UC-3 to: start t-UC-3 CANCELFROMPENDING = TRUE 5[a]/ Add a new requirement after 2.4.5.3.7.3.1 (reception of a [FISAccept-accept]APDU): 2.4.5.3.7.3.2 If in the UC-A-CANCEL state and the CANCELFROMPENDING is set to TRUE, the air FIS UC module shall: a) stop timers t-UC-1 and t-UC-2, b) set CANCELFROMPENDING to be FALSE, and c) remain in the UC-A-CANCEL state. 6[a]/ Add a new requirement after 2.4.5.3.7.4.1 (reception of a [FISAccept-positiveack]APDU: 2.4.5.3.7.4.2 If in the UC-A-CANCEL state and the CANCELFROMPENDING is set to TRUE, the air FIS UC module shall: a) stop timers t-UC-1 and t-UC-2, b) set CANCELFROMPENDING to be FALSE, and c) remain in the UC-A-CANCEL state. 7[a]/ Change in table 2.4.5-8/a the cells ([FISAccept-accept]APDU,UC-A-CANCEL) and ([FISAccept-positive acknowledgment]APDU,UC-A-CANCEL) from: AB-abort ("sequence error") -> UC-A-IDLE to: If CANCELFROMPENDING = TRUE stop t-UC-1, t-UC-2 CANCELFROMPENDING = FALSE -> UC-A-CANCEL 8[a]/ Add a new requirement after 2.4.5.3.7.5.1 (reception of a [FISReject] APDU] APDU: 2.4.5.3.7.5.2 If in the UC-A-CANCEL state and the CANCELFROMPENDING is set to TRUE, the air FIS UC module shall: a) stop timers t-UC-1 and t-UC-2, b) set CANCELFROMPENDING to be FALSE, c) request the FIS HI module to invoke a FIS-cancel-update-contract confirmation with the <> parameter containing the information which has been received as the <> APDU-element, and d) enter the UC-A-IDLE state. 9[a]/ Change in table 2.4.5-8/b the cell([FISReject]APDU,UC-A-CANCEL) from: AB-abort ("sequence error") -> UC-A-IDLE to: If CANCELFROMPENDING = TRUE stop t-UC-1, t-UC-2 CANCELFROMPENDING = FALSE UC-cancel-update-contract cnf -> UC-A-IDLE else AB-abort ("sequence error") -> UC-A-IDLE 10[b,c]/ Change 2.4.5.3.7.6.2 (reception of a [FISReport]APDU from: 2.4.5.3.7.6.2 If in the UC-A-CANCEL state, the air FIS UC module shall: a) request the FIS HI module to invoke a FIS-report indication with the following parameters: 1) the FISContractNumner parameter containing the information which has been received as the ContractNumber APDU-element, 2) the FISInformation parameter, containing the information which has been received as the FISReportData APDU-element, and b) remain in the UC-A-CANCEL state to: 2.4.5.3.7.6.2 If in the UC-A-CANCEL state and the CANCELFROMPENDING is set to FALSE, the air FIS UC module shall remain in the UC-A-CANCEL state. 11[b,c]/ Change in table 2.4.5-8/a the cell ([FISReport]APDU,UC-A-CANCEL) from: UC-report ind -> UC-A-CANCEL to: if CANCELFROMPENDING = FALSE -> UC-A-CANCEL else AB-abort ("sequence errror") ->UC-A-IDLE 12[d]/ change in table 2.4.5-9/b the cell ([FISCancelUpdateContract] APDU, UC-G-PENDING from: AB-abort ("protocol error") * UC-A-IDLE To: UC-cancel-update-contract ind LI-Send-Normal [FISCancelUpdateAccept] APDU -> UC-G-IDLE 13[e]/ In Table 2.4.5-9/b, change the title of the third column from: UC-G-CANCEL To: UC-G-ACTIVE 14[e]/ In table 2.4.5-9, change the three occurrences of UC-A-IDLE to UC-G-IDLE. SME Recommendation to CCB: CCB Decision: atnp_ccb_chair: SUBMITTED (27/11/97) Atnp_ccb_chair: ACCEPTED (08/12/97) CCB-4 (Montreal): RESOLVED (16/12/97)