Title: ARF - QOS in D-START Primitives PDR Reference: 99030003 Originator Reference: SARPs Document Reference: ADS SARPs, Sections 2.2.2.5.3.5.3.1, 2.2.2.5.3.5.3.2 and 2.2.2.5.4.7.1 Status: ADOPTED Impact: C (Clarification) PDR Revision Date: 17/05/99 (PROPOSED -> RESOLVED) 18/03/99 (ACCEPTED -> PROPOSED) 01/03/99 (SUBMITTED -> ACCEPTED) PDR Submission Date: 01/03/99 (SG2 meeting) Submitting State/Organization: Submitting Author Name: Picard, F Submitting Author E-mail Address: picard_frederic@stna.dgac.fr Submitting Author Supplemental Contact Information: SARPs Date: IV2.3 - Doc 9705 Ed.1 SARPs Language: English Summary of Defect: Section 2.2.2.5.4.7.1 covers the ARF ASE exception handling requirement for the case where one of the QOS parameters is invalid within a D-START indication. Section 2.2.2.5.4.7.1 should also cover the case where the QOS Routing Class is not valid. The ARF ASE requirement associated with receiving a valid D-START indication needs to include a valid QOS Routing class as a precondition (2.2.2.5.3.5.3.1). Assigned SME: Sub-Volume II SME Proposed SARPs amendment: A check on the received Traffic Type value is needed to check the requested category (ATSC/AOC/other). If the AOC category is used instead of ATSC, if for some reason there is no AOC route available, the messages could not be transmitted. No check can be done on the ATSC route class since all values are authorised. 1/ Change 2.2.2.5.3.5.3.1 from: If in the RF-R-IDLE state, and if the D-START parameter is not compatible with the version number of the responding ADS-RF-ASE, and the parameter value is "high priority flight safety messages", and the parameter is the abstract value "low", and the parameter is a valid four to eight character facility designation, the responding ADS-RF-ASE shall: to: If in the RF-R-IDLE state, and if the D-START parameter is not compatible with the version number of the responding ADS-RF-ASE, and the parameter value is "high priority flight safety messages", and the parameter is the abstract value "low", and the parameter identifies the traffic category "Air Traffic Service Communications (ATSC)", and the parameter is a valid four to eight character facility designation, the responding ADS-RF-ASE shall: 2/ Change 2.2.2.5.3.5.3.2 from: If in the RF-R-IDLE state, and if the D-START parameter is compatible with the version number of the responding ADS-RF-ASE, the responding ADS-RF-ASE shall: to: If in the RF-R-IDLE state, and if the D-START parameter is compatible with the version number of the responding ADS-RF-ASE, and the parameter value is "high priority flight safety messages", and the parameter is the abstract value "low", and the parameter identifies the traffic category "Air Traffic Service Communications (ATSC)", and the parameter is a valid four to eight character facility designation, the responding ADS-RF-ASE shall: 3/ Change 2.2.2.5.4.7.1 from: Upon receipt of a D-START indication with the parameter set to a value other than the abstract value "high priority flight safety messages", or the parameter set to a value other than the abstract value "low", the ADS-RF-ASE shall: to: Upon receipt of a D-START indication with the parameter set to a value other than the abstract value "high priority flight safety messages", or the parameter set to a value other than the abstract value "low", or the parameter set to a value not identifying the traffic category "Air Traffic Service Communications (ATSC)", the ADS-RF-ASE shall: SME Recommendation to CCB: - CCB Decision: atnp_ccb_chair (01/03/98): SUBMITTED CCB-9 (Naples): RESOLVED (17/05/99)