Title: CPDLC - Invalid Message Response PDR Reference: 97100012 Originator Reference: INVMESRSP SARPs Document Reference: CPDLC SARPs, Section 2.3.7.11.8 Status: ADOPTED PDR Revision Date: 20/10/97 (SUBMITTED -> ACCEPTED -> PROPOSED) 29/10/97 PDR Submission Date: 06/10/97 Submitting State/Organization: ATNP WG3/SG2 Submitting Author Name: Kapp, V Submitting Author E-mail Address: kapp@cenatls.cena.dgac.fr Submitting Author Supplemental Contact Information: SARPs Date: IV1.1, March 1997 SARPs Language: English Summary of Defect: Section 2.3.7.3.11.8 "Invalid Message Response" specifies the actions the CPDLC-users have to perform when they receive a response to a message not compatible with the attribute of the original message. The logical condition expressed in sections 2.3.7.3.11.8.1 to 2.3.7.3.11.8.4 is not correct. The logical operator "or" used in the condition causes the CPDLC-users to abort the connection with the reason [invalid-response] whenever message received in response does not contain an error. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: Summary of change is to delete checking for weather the message contains an error since this is done in previous sections, and is redundant as well as confusing. Change in sections 2.3.7.3.11.8.1, 2.3.7.3.11.8.2, 2.3.7.3.11.8.3 and 2.3.7.3.11.8.4 from: 2.3.7.3.11.8.1 If the CPDLC-ground-user sends a message that has a W/U response attribute, and a response to this message is received by the CPDLC-ground-user that does not contain an error or any of the following message elements: WILCO, UNABLE, STANDBY, LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.2 If the CPDLC-ground-user sends a message that has an A/N response attribute, and a response to this message is received by the CPDLC-ground-user that does not contain an error or any of the following message elements: AFFIRM, NEGATIVE, STANDBY, LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.3 If the CPDLC-ground-user sends a message that has a R response attribute, and a response to this message is received by the CPDLC-ground-user that does not contain an error or any of the following message elements: ROGER, UNABLE, STANDBY, LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.4 If the CPDLC-user sends a message that has a N response attribute and requires a logical acknowledgment, and a response to this message is received by the CPDLC-user that does not contain an error or any of the following message elements: LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.5 If the CPDLC-user sends a message that has a N response attribute and does not require a logical acknowledgment, and a response to this message is received by the CPDLC-user that does not contain an error the CPDLC-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. to: 2.3.7.3.11.8.1 If the CPDLC-ground-user sends a message that has a W/U response attribute, and a response to this message is received by the CPDLC-ground-user that does not contain any of the following message elements: WILCO, UNABLE, STANDBY, LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.2 If the CPDLC-ground-user sends a message that has an A/N response attribute, and a response to this message is received by the CPDLC-ground-user that does not contain any of the following message elements: AFFIRM, NEGATIVE, STANDBY, LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.3 If the CPDLC-ground-user sends a message that has a R response attribute, and a response to this message is received by the CPDLC-ground-user that does not contain any of the following message elements: ROGER, UNABLE, STANDBY, LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.4 If the CPDLC-user sends a message that has a N response attribute and requires a logical acknowledgment, and a response to this message is received by the CPDLC-user that does not contain any of the following message elements: LOGICAL ACKNOWLEDGMENT, or ERROR[errrorInformation] the CPDLC-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 2.3.7.3.11.8.5 If the CPDLC-user sends a message that has a N response attribute and does not require a logical acknowledgment, and a response to this message is received by the CPDLC-user, the CPDLC-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. SME Recommendation to CCB: - CCB Decision: atnp_ccb_chair: ACCEPTED (20/10/97) CCB-3: RESOLVED