Title: CM - QOS in D-START Primitives PDR Reference: 98120006 Originator Reference: acicm04 SARPs Document Reference: CM SARPs, Sections 2.1.5.3.2.2, 2.1.5.3.2.3, 2.1.5.3.3.2, 2.1.5.3.3.3, and 2.1.5.4.7 Status: RESOLVED Impact: C (Clarification) PDR Revision Date: 17/05/99 (PROPOSED -> RESOLVED) 01/03/99 (ACCEPTED -> PROPOSED) 18/01/99 (SUBMITTED -> ACCEPTED) PDR Submission Date: 12/03/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: Problem 1/ Sections 2.1.5.4.7 covers the exception handling requirement for the case where one of the QOS parameters is invalid within a D-START indication. However, the CM ASE should also abort if the QOS parameters received in the D-START confirm is not valid for the CM ASE. The requirements related to the receipt of valid D-START confirmation primitives (see 2.1.5.3.2.3 and 2.1.5.3.3.3) need to include conditions for valid QOS parameters similar to the D-START Indication requirements. Problem 2/ Section 2.1.5.4.7.1 should cover the case where the QOS Routing Class is not valid. The requirements associated with the receipt of valid D-START indication primitives (See 2.1.5.3.2.2 and 2.1.5.3.3.2) need to include conditions for valid routing class. Problem 3/ The assumption is made in the application SARPs that when the Routing Class abstract value "ATSC - No Traffic Type Policy Preference" is requested by the DS-user, then the DSP (actually the TSP) indicates in the D-START indication (actually the T-CONNECT indication) the actual Traffic Type ("A" to "H"). This assumption is not correct, the traffic type value supplied in the indication is always identical the one provided in the request. This means that the value "ATSC - No Traffic Type Policy Preference" may be received by the called ASE. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: 1/ Change section 2.1.5.3.2.2.1 from: Upon receipt of a D-START indication, if the CM-air-ASE is in the IDLE state and the D-START indication Priority Quality-of-Service parameter has the abstract value "flight regularity communications" and the RER Quality-of-Service parameter has the abstract value of "low" then: To: Upon receipt of a D-START indication, if the CM-air-ASE is in the IDLE state and the D-START indication Priority Quality-of-Service parameter has the abstract value "flight regularity communications" and the RER Quality-of-Service parameter has the abstract value of "low" and the D-START QOS Routing Class parameter has one of the abstract values specified in Table 2.1.6-1 then: 2/ Change section 2.1.5.3.2.3.1 from: Upon receipt of a D-START confirmation, if the CM-air-ASE is in the LOGON state and if the APDU contained in the D-START User Data parameter is a [CMLogonResponse]APDU or if the D-START User Data parameter is not present but the D-START DS User Version Number parameter is present, the CM-air-ASE shall: To: Upon receipt of a D-START confirmation, if the CM-air-ASE is in the LOGON state and the D-START QOS Priority parameter has the abstract value "high priority flight safety message" and the D-START QOS Residual Error Rate parameter has the abstract value "low" and the D-START QOS Routing Class parameter has one of the abstract values specified in Table 2.1.6-1 and if the APDU contained in the D-START User Data parameter is a [CMLogonResponse]APDU or if the D-START User Data parameter is not present but the D-START DS User Version Number parameter is present, the CM-air-ASE shall: 3/ Change section 2.1.5.3.3.2.1 from: Upon receipt of a D-START indication, if the CM-ground-ASE is in the IDLE state and the APDU contained in the D-START User Data parameter is a [CMLogonRequest] APDU and the abstract value of the D-START Calling Peer ID parameter is a 24 bit Aircraft Address and the D-START indication Priority Quality-of-Service parameter has the abstract value "flight regularity communications" and the RER Quality-of-Service parameter has the abstract value of "low" then: To: Upon receipt of a D-START indication, if the CM-ground-ASE is in the IDLE state and the APDU contained in the D-START User Data parameter is a [CMLogonRequest] APDU and the abstract value of the D-START Calling Peer ID parameter is a 24 bit Aircraft Address and the D-START indication Priority Quality-of-Service parameter has the abstract value "flight regularity communications" and the RER Quality-of-Service parameter has the abstract value of "low" and the D-START QOS Routing Class parameter has one of the abstract values specified in Table 2.1.6-1 then: 4/ Change section 2.1.5.3.3.2.2 from: Upon receipt of a D-START indication, if the CM-ground-ASE is in the IDLE state and the APDU contained in the D-START User Data parameter is a [CMForwardRequest] APDU and the abstract value of the D-START Calling Peer ID parameter is a 4 to 8 character Facility Designation and the D-START indication Priority Quality-of-Service parameter has the abstract value "flight regularity communications" and the RER Quality-of-Service parameter has the abstract value of "low" then: To: Upon receipt of a D-START indication, if the CM-ground-ASE is in the IDLE state and the APDU contained in the D-START User Data parameter is a [CMForwardRequest] APDU and the abstract value of the D-START Calling Peer ID parameter is a 4 to 8 character Facility Designation and the D-START indication Priority Quality-of-Service parameter has the abstract value "flight regularity communications" and the RER Quality-of-Service parameter has the abstract value of "low" and the D-START QOS Routing Class parameter has one of the abstract values specified in Table 2.1.6-1 then: 5/ Change section 2.1.5.3.3.3.1 from: Upon receipt of a D-START Confirmation: To: Upon receipt of a D-START Confirmation and the D-START QOS Priority parameter has the abstract value "high priority flight safety message" and the D-START QOS Residual Error Rate parameter has the abstract value "low" and the D-START QOS Routing Class parameter has one of the abstract values specified in Table 2.1.6-1: 6/ Change section 2.1.5.4.7 from: D-START Indication Quality of Service Not As Expected To: D-START Quality of Service Not As Expected 7/ Add new section 2.3.5.4.7.2 as follows: 2.3.5.4.7.2 If a D-START confirmation QOS Priority parameter does not have the abstract value of "high priority flight safety messages" or if the QOS Residual Error Rate parameter does not have the abstract value of "low" or if the QOS Routing Class parameter does not have one of the abstract values specified in Table 2.1.6-1, and the Result parameter has the abstract value "accepted", the CM-ASE shall: a) Stop any timer, b) If the CM-ASE is a CM-air-ASE, create a CMAircraftMessage APDU with a CMAbortReason [invalid-QOS-parameter] APDU message element, c) If the CM-ASE is a CM-ground-ASE, create a CMGroundMessage APDU with a CMAbortReason [invalid-QOS-parameter] APDU message element, d) 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, and e) invoke a CM-provider-abort service indication with the abstract value "invalid-QOS-parameter ", and f) Enter the IDLE state. 8/ Change section 2.1.5.4.7.1 from: If the abstract value of the Priority Quality-Of-Service parameter is not "flight safety communications" or if the RER Quality-Of-Service parameter is not "low", the CM-ASE shall: To: If a D-START indication QOS Priority parameter does not have the abstract value of "high priority flight safety messages" or if the QOS Residual Error Rate parameter does not have the abstract value of "low", or if the QOS Routing Class parameter does not have one of the abstract values specified in Table 2.1.6-1, the CM-ASE shall: SME Recommendation to CCB: - Problem 1/ There is no need at all to check the QOS parameter of a D-START confirmation. The Priority and the Routing Class provided by the initiator ASE can not be changed by the DSP or the peer ASE (see SARPs SV4 section 4.2.3.2.1, note 7). The RER may be changed only if the requested RER is "high" (seen note 10). For ADS, the requested RER is low, therefore the peer ASE cannot change the value. Therefore, if the dialogue is established, it is established with the QOS requested by the initiator ASE. Note. Anyway, when the peer ASE invokes the D-START response, the Transport connection is already set up and its QOS parameters can not be changed. Therefore changes 2, 5, 6 and 7 are proposed to be rejected. Problem 2/ 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. Change 1, 3 and 4 proposed above are modified as follows: 1/ Change section 2.1.5.3.2.2.1 from: Upon receipt of a D-START indication, if the CM-air-ASE is in the state and the D-START indication Quality-of-Service parameter has the abstract value "flight regularity communications", the Quality-of-Service parameter has the abstract value of "low" and the parameter is a valid four to eight character facility designation then: To: Upon receipt of a D-START indication, if the CM-air-ASE is in the state and the D-START QOS parameter has the abstract value "flight regularity communications", the D-START QOS parameter has the abstract value of "low", the D-START QOS parameter identifies the traffic category "Air Traffic Service Communications (ATSC)" and the parameter is a valid four to eight character facility designation then: 3/ Change section 2.1.5.3.3.2.1 from: Upon receipt of a D-START indication, if the CM-ground-ASE is in the state and the APDU contained in the D-START parameter is a [CMLogonRequest] APDU and the abstract value of the D-START parameter is a 24 bit Aircraft Address and the D-START indication Quality-of-Service parameter has the abstract value "flight regularity communications" and the Quality-of-Service parameter has the abstract value of "low" then: To: Upon receipt of a D-START indication, if the CM-ground-ASE is in the state and the APDU contained in the D-START parameter is a [CMLogonRequest] APDU and the abstract value of the D-START parameter is a 24 bit Aircraft Address and the D-START QOS parameter has the abstract value "flight regularity communications" and the D-START QOS parameter has the abstract value of "low" and the D-START QOS parameter identifies the traffic category "Air Traffic Service Communications (ATSC)" then: 4/ Change section 2.1.5.3.3.2.2 from: Upon receipt of a D-START indication, if the receiving CM-ground-ASE is in the state and the APDU contained in the D-START parameter is a [CMForwardRequest] APDU and the abstract value of the D-START parameter is a 4 to 8 character Facility Designation and the D-START indication Quality-of-Service parameter has the abstract value "flight regularity communications" and the Quality-of-Service parameter has the abstract value of "low" then: To: Upon receipt of a D-START indication, if the receiving CM-ground-ASE is in the state and the APDU contained in the D-START parameter is a [CMForwardRequest] APDU and the abstract value of the D-START parameter is a 4 to 8 character Facility Designation and the D-START QOS parameter has the abstract value "flight regularity communications" and the D-START QOS parameter has the abstract value of "low" and the D-START QOS parameter identifies the traffic category "Air Traffic Service Communications (ATSC)" then: 8/ Change section 2.1.5.4.7.1 from: If the abstract value of the Quality-Of-Service parameter is not "flight regularity communications" or the abstract value of the Quality-Of-Service parameter is not "low", the CM-ASE shall: To: If the abstract value of the D-START QOS parameter is not "flight regularity communications" or the abstract value of the D-START QOS parameter is not "low" or the abstract value of the D-START QOS parameter does not identify the traffic category "Air Traffic Service Communications (ATSC)", the CM-ASE shall: Problem 3/ There is no change to the CM SARPs since the received Routing Class value is not provided to the CM-user. The mapping Table (2.2.1.6-1) is only application for the D-START request (not the indication) and does not need to be changed. CCB Decision: atnp_ccb_chair (02/12/98): SUBMITTED CCB-8 (Honolulu): ACCEPTED (18/01/99) CCB-9 (Naples): RESOLVED (17/05/99)