Title: CPDLC - Closure Messages PDR Reference: 99010003 Originator Reference: logack SARPs Document Reference: CPDLC SARPs, Sections 2.3.7 Status: RESOLVED Impact: C (Clarification) PDR Revision Date: 21/01/99 (PROPOSED -> RESOLVED) 19/01/99 (ACCEPTED -> PROPOSED) 18/01/99 (SUBMITTED -> ACCEPTED) PDR Submission Date: 14/01/98 Submitting State/Organization: WG3/SG2 Submitting Author Name: Hamelink, J Submitting Author E-mail Address: Submitting Author Supplemental Contact Information: SARPs Date: IV2.3 (Doc 9705 Ed1) SARPs Language: English Summary of Defect: Some of the CPDLC messages, both air and ground PDUs are system generated, rather than human generated. These messages are contained in tables 2.3.7-15 (uplink) and 2.3.7-26(downlink). Operational requirements from ADSP require that a LOGICAL ACKNOWLEDGMENT be transmitted just prior to the display of a message to the pilot or controller. Thus, when the system generated messages are sent they will be sent instead of a LOGICAL ACKNOWLEDGEMENT, if a logical acknowledgment is required. They will also serve as a closure message. Chapter 7 of the CPDLC SARPs must be updated to reflect this operational requirement. Some other problems to 2.3.7 have been found and are noted here at the end. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: 1. Modify Table 2.3.7-3 the "Valid Responses Description" column as follows: a. the "W/U" row: From: "Response required: WILCO, UNABLE, STANDBY permitted, LOGICAL ACKNOWLEDGMENT (only if required), ERROR (if necessary)" To: "Response required: WILCO, UNABLE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, ERROR, LOGICAL ACKNOWLEDGMENT (only if required)" b. the "A/N" row: From: "Response required: AFFIRM, NEGATIVE, STANDBY permitted, LOGICAL ACKNOWLEDGMENT (only if required), ERROR (if necessary)" To: "Response required: AFFIRM, NEGATIVE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, ERROR, LOGICAL ACKNOWLEDGMENT (only if required)" c. the "R" row: From: "Response required: ROGER, UNABLE, STANDBY permitted, LOGICAL ACKNOWLEDGMENT (only if required), ERROR,(if necessary)" To: "Response required: ROGER, UNABLE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, ERROR, LOGICAL ACKNOWLEDGMENT (only if required)" d. the "N" row: From: "LOGICAL ACKNOWLEDGMENT (only if required), ERROR,(if necessary, only when logical acknowledgment is required)" To: "LOGICAL ACKNOWLEDGMENT (only if required), ERROR, NOT CURRENT DATA AUTHORITY, or NOT AUTHORIZED NEXT DATA AUTHORITY" Note that it is no change to the "Y" row. 2. Modify Table 2.3.7-4 the cell in the "N" row and "Valid Responses Description" column as follows: From: "LOGICAL ACKNOWLEDGMENT (only if required), ERROR,(if necessary, only when logical acknowledgment is required)" To: "LOGICAL ACKNOWLEDGMENT (only if required), ERROR, SERVICE UNAVAILABLE, or FLIGHT PLAN NOT HELD" Note that it is no change to the "Y" row. 3. Modify section 2.3.7.3.9.8 as follows: From: When a message is received by the CPDLC-user requiring a logical acknowledgment response, the CPDLC-user shall respond with either a CPDLC message containing a LOGICAL ACKNOWLEDGMENT message element, or a message containing an ERROR message element. To: When a message is received by the CPDLC-user requiring a logical acknowledgment response, a) when the CPDLC-user is a CPDLC-air-user, the CPDLC-air-user shall respond with either a CPDLC message containing a LOGICAL ACKNOWLEDGMENT message element, or with a message containing an ERROR, NOT CURRENT DATA AUTHORITY, or NOT AUTHORIZED NEXT DATA AUTHORITY message element as appropriate, or b) when the CPDLC-user is a CPDLC-ground-user, the CPDLC-ground-user shall respond with a CPDLC message containing a LOGICAL ACKNOWLEDGMENT message element, or with a message containing an ERROR, SERVICE UNAVAILABLE, or FLIGHT PLAN NOT HELD message element as appropriate. 4. Modify section 2.3.7.3.9.9 as follows: From: A logical acknowledgment response message, if required, shall be sent prior to sending any other related response message(s), except a response containing an ERROR message element. To: A logical acknowledgment response message, if required, shall be sent prior to sending any other related response message(s), except: a) when the response is an uplink message, a response message containing an ERROR, SERVICE UNAVAILABLE, or FLIGHT PLAN NOT HELD message element as appropriate, or b) when the response is a downlink message, a response message containing an ERROR, NOT CURRENT DATA AUTHORITY, or NOT AUTHORIZED NEXT DATA AUTHORITY message element as appropriate. Note.- When case a) or b) occurs, the LOGICAL ACKNOWLEDGMENT message element is not sent. 5. Modify section 2.3.7.3.9.10 as follows: From: When the CPDLC-air-user receives a message with a W/U RESP attribute, the only permitted responses shall be messages that contain a LOGICAL ACKNOWLEDGMENT (if required), STANDBY, WILCO, UNABLE or ERROR message element. To: When the CPDLC-air-user receives a message with a W/U RESP attribute, the only permitted responses shall be messages that contain a LOGICAL ACKNOWLEDGMENT (if required), STANDBY, WILCO, UNABLE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. 6. Modify section 2.3.7.3.9.11 as follows: From: When the CPDLC-air-user receives a message with a W/U RESP attribute, the closure response message shall contain at least a WILCO, UNABLE or ERROR message element. To: When the CPDLC-air-user receives a message with a W/U RESP attribute, the closure response message shall contain at least a WILCO, UNABLE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. 7. Modify section 2.3.7.3.9.12 as follows: From: When the CPDLC-air-user receives a message with a A/N RESP attribute, the only permitted responses shall be messages that contain a LOGICAL ACKNOWLEDGMENT (if required), STANDBY, AFFIRM, NEGATIVE or ERROR message element. To: When the CPDLC-air-user receives a message with a A/N RESP attribute, the only permitted responses shall be messages that contain a LOGICAL ACKNOWLEDGMENT (if required), STANDBY, AFFIRM, NEGATIVE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. 8. Modify section 2.3.7.3.9.13 as follows: From: When the CPDLC-air-user receives a message with a A/N RESP attribute, the closure response message shall contain at least a AFFIRM, NEGATIVE, or ERROR message element. To: When the CPDLC-air-user receives a message with a A/N RESP attribute, the closure response message shall contain at least a AFFIRM, NEGATIVE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. 9. Modify section 2.3.7.3.9.14 as follows: From: When the CPDLC-air-user receives a message with a R RESP attribute, the only permitted responses shall be messages that contain a LOGICAL ACKNOWLEDGMENT (if required), STANDBY, ROGER, UNABLE or ERROR message element. To: When the CPDLC-air-user receives a message with a R RESP attribute, the only permitted responses shall be messages that contain a LOGICAL ACKNOWLEDGMENT (if required), STANDBT, ROGER, UNABLE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. 10. Modify section 2.3.7.3.9.15 as follows: From: When the CPDLC-air-user receives a message with a R RESP attribute, the closure response message shall contain at least a ROGER, UNABLE or ERROR message element. To: When the CPDLC-air-user receives a message with a R RESP attribute, the closure response message shall contain at least a ROGER, UNABLE, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. 11. Modify section 2.3.7.3.9.20 as follows: From: When the CPDLC-air-user receives a message with a N RESP attribute, but requiring a logical acknowledgment, the only permitted response shall be a message that contains a LOGICAL ACKNOWLEDGMENT, or ERROR message element. This response message is the closure message. To: When the CPDLC-air-user receives a message with a N RESP attribute, but requiring a logical acknowledgment, the only permitted response shall be a message that contains a LOGICAL ACKNOWLEDGMENT, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element. This response message is the closure message. 12. Modify section 2.3.7.3.9.21 as follows: From: When the CPDLC-ground-user receives an air/ground message with a N RESP attribute, but requiring a logical acknowledgment the only permitted response shall be a message that contains a LOGICAL ACKNOWLEDGMENT or ERROR message element. This response message is the closure message. To: When the CPDLC-ground-user receives an air/ground message with a N RESP attribute, but requiring a logical acknowledgment the only permitted response shall be a message that contains a LOGICAL ACKNOWLEDGMENT, SERVICE UNAVAILABLE, FLIGHT PLAN NOT HELD or ERROR, message element. This response message is the closure message. 13. Modify section 2.3.7.11.7 as follows: From: ERROR Message Response To: System Management Responses 14. Modify section 2.3.7.11.7.1 as follows: From: If the CPDLC-user sends a message containing the ERROR message element instead of the expected response message, the ERROR message shall contain the received message identification number as the message reference number. To: If the CPDLC-air-user sends a message containing the NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element instead of the expected response message, the NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message shall contain the received message identification number as the message reference number. and add new section 2.3.7.3.11.7.2 as follows: If the CPDLC-ground-user sends a message containing the SERVICE UNAVAILABLE, FLIGHT PLAN NOT HELD or ERROR message element instead of the expected response message, the SERVICE UNAVAILABLE, FLIGHT PLAN NOT HELD or ERROR message shall contain the received message identification number as the message reference number. 15. Modify section 2.3.7.3.11.7.2 (re-numbered as section 2.3.7.3.11.7.3) as follows: From: If an ERROR message is sent in response to a CPDLC message the received CCPDLC message shall be disregarded. To: If the CPDLC-air-user sends a NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR message element in response to a CPDLC message, the received CPDLC message shall be disregarded. and add new section 2.3.7.3.11.7.4 as follows: If the CPDLC-ground-user sends a SERVICE UNAVAILABLE, FLIGHT PLAN NOT HELD or ERROR message element in response to a CPDLC message, the received CPDLC message shall be disregarded. 16. Modify section 2.3.7.3.11.8.1 as follows: From: 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[errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. To: 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, NOT CURRENT DDATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR[errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 17. Modify section 2.3.7.3.11.8.2 as follows: From: 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[errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. To: 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, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR[errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 18. Modify section 2.3.7.3.11.8.3 as follows: From: 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 [errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. To: 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, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR [errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 19. Modify section 2.3.7.3.11.8.4 as follows: From: 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[errorInformation] the CPDLC-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalild-response]. To: If the CPDLC-ground-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-ground-user that does not contain any of the following message elements: LOGICAL ACKNOWLEDGMENT, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY or ERROR[errorInformation] the CPDLC-ground-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. Note editorial correction of "invalild" to "invalid" in last line of this section. and add new section 2.3.7.3.11.8.5 as follows: If the CPDLC-air-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-air-user that does not contain any of the following message elements: LOGICAL ACKNOWLEDGMENT, SERVICE UNAVAILABLE, FLIGHT PLAN NOT HELD or ERROR[errorInformation] the CPDLC-air-user shall invoke CPDLC-user-abort request with a CPDLC message containing the CPDLCUserAbortReason with the value [invalid-response]. 20. In section 2.3.7.4.4.2.8.2, the CPDLC-air-user is requested to send a CPDLC-end response with the Result parameter set to "accepted". Since the CPDLC-air-user has downlink open message, the choice between accepting or rejecting the end request should be given to him. Thus, Section 2.3.7.4.4.2.8.2 c) should be modified as follows: From: "accepted". To: "accepted" or "rejected". 21. In 2.3.7.5.1.2.3, uplink message FLIGHT PLAN NOT HELD should be an allowed Reject Reason. Modify section 2.3.7.5.1.2.3 as follows: From: If the CPDLC-ground-user sets the CPDLC-start response parameter to the abstract value "rejected" then the shall be an uplink message containing only the SERVICE UNAVAILABLE message element. To: If the CPDLC-ground-user sets the CPDLC-start response parameter to the abstract value "rejected" then the parameter shall be an uplink message containing either the SERVICE UNAVAILABLE or FLIGHT PLAN NOT HELD message element as appropriate. 22. In 2.3.7.5.2.1.3, uplink message FLIGHT PLAN NOT HELD should be an allowed Reject Reason. Modify section 2.3.7.5.2.1.3 as follows: From: If the CPDLC-ground-user sets the DSC-start response parameter to the abstract value "rejected" then the shall be an uplink message containing only the SERVICE UNAVAILABLE message element. To: If the CPDLC-ground-user sets the DSC-start response parameter to the abstract value "rejected" then the parameter shall be an uplink message containing either the SERVICE UNAVAILABLE or FLIGHT PLAN NOT HELD message element as appropriate. 23. In 2.3.7.5.2.2.2 b), uplink message FLIGHT PLAN NOT HELD should be an allowed Reject Reason. From: if, and only if, the Result parameter is set to the abstract value "rejected", then set the Reject Reason parameter to a CPDLC message with the message element SERVICE UNAVAILABLE. To: From: if, and only if, the Result parameter is set to the abstract value "rejected", then set the Reject Reason parameter to a CPDLC message with the message element SERVICE UNAVAILABLE or FLIGHT PLAN NOT HELD as appropriate. SME Recommendation to CCB: CCB Decision: atnp_ccb_chair: SUBMITTED (14/01/99) CCB-8 (Honolulu): ACCEPTED (18/01/99) CCB-8a (Honolulu): RESOLVED (21/01/99)