Title: CPDLC - Reception of a D-START Calling ID with a wrong type PDR Reference: 98120010 Originator Reference: acicpdlc04 SARPs Document Reference: CPDLC SARPs, Sections 2.3.4.2.1, 2.3.5.3.2.1, 2.3.5.5.2.1, 2.3.5.4, and 2.3.5.6 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: 03/12/98 Submitting State/Organization: AIRSYS ATM (ACI) Submitting Author Name: Ilkiewicz, M / Stokes, S Submitting Author E-mail Address: michel.ilkiewicz@cdv.vly.sextant. thomson-csf.com, Shawn.Stokes@atnsi.com Submitting Author Supplemental Contact Information: SARPs Date: IV2.2, IV2.3 (Doc 9705 Ed1) SARPs Language: English Summary of Defect: The CPDLC ASE should abort with a reason indicating Invalid Calling Peer ID (not yet defined as a abstract syntax value for the CPDLCProviderAbortReason in section 2.3.4.2.1) when a D-START indication is received with a Calling Peer ID which is not valid for the expected peer originator end system type of the D-Start message. Consider the following cases, which should result in an Abort by the CPDLC ASE: a) CPDLC-air-ASE receives a D-START indication with a Calling Peer ID which is not a valid four to eight character facility designator. Note: Requirement 2.3.5.3.2.1 should also indicate as a precondition to this requirement that the Calling Peer ID is a valid facility designator. b) CPDLC-ground-ASE receives a D-START indication containing a AircraftPDUs [StartDownMessage] APDU with a Calling Peer ID which is not a valid 24 bit Aircraft Address. Note: Requirements 2.3.5.5.2.1 and 2.3.5.5.2.2 should also indicate as a precondition to this requirement that the Calling Peer ID is a valid aircraft address. c) CPDLC-ground-ASE receives a D-START indication containing a GroundPDUs [ATCForwardMessage] APDU with a Calling Peer ID which is not a valid four to eight character facility designator. Note: Requirements 2.3.5.5.2.3 and 2.3.5.5.2.4 should also indicate as a precondition to this requirement that the Calling Peer ID is a valid facility designator. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: Solution A/ 1/ The Abstract syntax for the CPDLCProviderAbortReason in section 2.3.4.2.1 should add one addition value as follows: invalid-calling-peer-id (8), 2/ The requirement text for section 2.3.5.3.2.1 should be changed from: Upon receipt of a D-START indication, if the CPDLC-air-ASE is in the state and the D-START parameter contains a GroundPDUs [UplinkMessage] APDU, and the D-START parameter has the abstract value "high priority flight safety message" and the D-START parameter has the abstract value "low", and the D-START parameter has one of the abstract values specified in Table 2.3.6-1, the CPDLC-air-ASE shall: To: Upon receipt of a D-START indication, if the CPDLC-air-ASE is in the state and the D-START parameter contains a GroundPDUs [UplinkMessage] APDU, and the D-START parameter has the abstract value "high priority flight safety message" and the D-START parameter has the abstract value "low", the D-START parameter has one of the abstract values specified in Table 2.3.6-1, and the D-START parameter is a valid four to eight character facility designation, the CPDLC-air-ASE shall: 3/ Add a new section 2.1.5.4.8 and subsections for the following textual requirements as follows: 2.1.5.4.8 D-START Indication Calling Peer ID Parameter Not as Expected 2.15.4.8.1 Upon receipt by the CPDLC-air-ASE of a D-START indication with a Calling Peer ID which is not a valid four to eight character facility designator, the CPDLC-air-ASE shall: a) stop all timers b) create a AircraftPDUs APDU with a CPDLCProviderAbortReason [invalid-calling-peer-id] APDU message element c) invoke D-ABORT request with 1) the abstract value "provider" as the D-ABORT Originator parameter value, and 2) the APDU as the D-ABORT User Data parameter value d) if DSC has the abstract value "true", set DSC to the abstract value "false", and e) enter the IDLE state 4/ Add a new section 2.1.5.6.8 and subsections for the following textual requirements as follows: 2.1.5.6.8 D-START Indication Calling Peer ID Parameter Not as Expected 2.15.6.8.1 Upon receipt by the CPDLC-air-ASE of a D-START indication with a Calling Peer ID which is not a valid four to eight character facility designator, the CPDLC-air-ASE shall: a) stop all timers b) create a GroundPDUs APDU with a CPDLCProviderAbortReason [invalid-calling-peer-id] APDU message element c) invoke D-ABORT request with 3) the abstract value "provider" as the D-ABORT Originator parameter value, and 4) the APDU as the D-ABORT User Data parameter value d) if DSC has the abstract value "true", set DSC to the abstract value "false", and e) enter the IDLE state Solution B/ In order to be able to map the value received in the D-START ind parameter to the CPDLC-start/forward parameter or to the DSC-start parameter, a check ON THE TYPE of the must first be performed by the ASE. This is not done in section 2.3.5.3.2.1. This is done is section 2.3.5.5.2.1, 2.3.5.5.2.2, 2.3.5.5.2.3 and 2.3.5.5.2.4. There is an exception handling procedure (section 2.3.5.4.4.4 for the air-ASE and section 2.3.5.6.4.4 for the ground ASE introduced by PDR 98110002) defined for the case an unexpected primitive or parameter primitive is received. If the peer ASE has used the wrong type for the Calling Peer Id, the dialogue is aborted on the ground that the protocol has not been respected by the peer (reason "protocol error"). Therefore, change 2 in solution A/ above is proposed to be accepted. The changes 1, 3 and 4 above are proposed to be rejected. SME Recommendation to CCB: CCB Decision: atnp_ccb_chair: SUBMITTED (03/12/98) CCB-8 (Honolulu) : ACCEPTED (18/01/99) CCB_8a (Honolulu) : RESOLVED (21/01/99) With solution B/