Title: SV2 Chapter 8 revisited PDR Reference: 99050003 Originator Reference: - SARPs Document Reference: SARPs Sub_Volume II, see text Status: ADOPTED PDR Revision Date: 30/01/02 (RESOLVED -> ADOPTED) 19/05/99 (PROPOSED -> RESOLVED) 18/05/99 (SUBMITTED -> PROPOSED) PDR Submission Date: 17/05/99 Submitting State/Organization: ATNP/WG3/SG2 Submitting Author Name: Picard, F Submitting Author E-mail Address: PICARD_Frederic@stna.dgac.fr Submitting Author Supplemental Contact Information: SARPs Date: ICAO 9705 Edition 1 (IV 2.3), 06/11/98 SARPs Language: English Summary of Defect: Issue 1/ There is a duplication of material in SARPs chapters 8 and emerging P/OICS. Tables related to the support requirements of the services and the APDU should be suppressed from SARPs chapters 8. Issue 2/ Configurations of ADS need to be revisited. Issue 3/ Configurations of CM need to be revisited. Assigned SME: Sub-Volume II SME Proposed SARPs amendment: Issue 1/ 1/ (ARF) Remove tables 2.2.2.8-4 and 2.2.2.8-5. 2/ (CPDLC) Remove tables 2.3.8-5 and 2.3.8-6. 3/ (FIS) Remove tables 2.4.8-4 and 2.4.8-5. Issue 2/ 4/ (ADS) Change ADS chapter 8 as follows: 2.2.1.8 Subsetting Rules 2.2.1.8.1 General Note. - 2.2.1.8 specifies conformance requirements which all implementations of the ADS protocol obey. 2.2.1.8.1.1 An implementation of either the ADS ground based service or the ADS air based service claiming conformance to 2.2.1 shall support the ADS protocol features as shown in the tables below. Note. - The 'status' column indicates the level of support required for conformance to the ADS-ASE protocol described in 2.2.1. The values are as follows: a) 'M' mandatory support is required; b) 'O' optional support is permitted for conformance to the ADS protocol; c) 'N/A' the item is not applicable; and d) 'C.n' the item is conditional where n is the number which identifies the condition which applicable. Table 2.2.1.8-1. ADS Protocol Versions Implemented -------------------------------------------------------------------------------- Status Associated Predicate -------------------------------------------------------------------------------- Version 1 M none -------------------------------------------------------------------------------- Table 2.2.1.8-2. ADS Operational Functional Units -------------------------------------------------------------------------------- Status Associated Predicate -------------------------------------------------------------------------------- The ADS system acts as an airborne system C.1 ADS/air The ADS system acts as a ground system C.1 ADS/ground The ADS ground system can establish demand contracts If (ADS/ground) C.2 else N/A G-DC-FU The ADS ground system can establish event contracts and process emergency reports If (ADS/ground) C.2 else N/A G-EC-FU The ADS ground system can establish periodic contracts and process emergency reports If (ADS/ground) C.2 else N/A G-PC-FU The ADS air system can process demand contracts If (ADS/air) C.3 else N/A A-DC-FU The ADS air system can process event contracts If (ADS/air) C.3 else N/A A-EC-FU The ADS air system can process periodic contracts If (ADS/air) C.3 else N/A A-PC-FU The ADS air system can send emergency reports If (A-EC-FU or A-PC-FU) O else N/A A-EM-FU -------------------------------------------------------------------------------- C.1 a conformant implementation shall support one and only one of these options. C.2 a conformant ground implementation shall support at least one of the three options. C.3 a conformant air implementation shall support at least one of the three options. Table 2.2.1.8-3. ADS-ground-ASE Conformant Configurations -------------------------------------------------------------------------------- List of Predicates Functionality Description -------------------------------------------------------------------------------- I ADS/ground + G-DC-FU Demand contract only can be established with the aircraft. II ADS/ground + G-EC-FU Event and Emergency contracts can be established with the aircraft. III ADS/ground + G-PC-FU Periodic and Emergency contracts can be established with the aircraft. IV ADS/ground + G-DC-FU + G-EC-FU Demand, Event and Emergency contracts can be established with the aircraft. V ADS/ground + G-DC-FU + G-PC-FU Demand, Periodic and Emergency contracts can be established with the aircraft. VI ADS/ground + G-EC-FU + G-PC-FU Event, Periodic and Emergency contracts can be established with the aircraft. VII ADS/ground + G-DC-FU + G-EC-FU + G-PC-FU Demand, Event, Periodic and Emergency contracts can be established with the aircraft. -------------------------------------------------------------------------------- Note. - An ADS ground system may or may not support the modify emergency capability. Table 2.2.1.8-4. ADS-air-ASE Conformant Configurations -------------------------------------------------------------------------------- List of Predicates Functionality Description -------------------------------------------------------------------------------- I ADS/air + A-DC-FU Demand contract only can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Event or Periodic contracts are requested. II ADS/air + A-EC-FU Event contract only can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Demand or Periodic contracts are requested. III ADS/air + A-PC-FU Periodic contract only can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Demand or Event contracts are requested. IV ADS/air + A-DC-FU + A-EC-FU Demand and Event contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Periodic contracts are requested. V ADS/air + A-DC-FU + A-PC-FU Demand and Periodic contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Event contracts are requested. VI ADS/air + A-EC-FU + A-PC-FU Event and Periodic contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Demand contracts are requested. VII ADS/air + A-DC-FU + A-EC-FU + A-PC-FU Demand, Event and Periodic contracts can be established with the ground system. VIII ADS/air + A-EC-FU + A-EM-FU Event and Emergency contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Demand and Periodic contracts are requested. IX ADS/air + A-PC-FU + A-EM-FU Periodic and Emergency contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Demand and Event contracts are requested. X ADS/air + A-DC-FU + A-EC-FU + A-EM-FU Demand, Event and Emergency contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Periodic contracts are requested. XI ADS/air + A-DC-FU + A-PC-FU + A-EM-FU Demand, Periodic and Emergency contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Event contracts are requested. XII ADS/air + A-EC-FU + A-PC-FU + A-EM-FU Event, Periodic and Emergency contracts can be established with the ground system. A Negative Acknowledgement with reason "ADS-service unavailable" is sent when Demand contracts are requested. XIII ADS/air + A-DC-FU + A-EC-FU + A-PC-FU + A-EM-FU Demand, Event, Periodic and Emergency contracts can be established with the ground system. -------------------------------------------------------------------------------- Issue 3/ 5/ Change CM chapter 8 as follows: 2.1.8 Subsetting Rules 2.1.8.1 General Note. - 2.1.8 specifies conformance requirements which all implementations of the CM protocol obey. 2.1.8.1.1 An implementation of either the CM ground based service or the CM air based service claiming conformance to 2.1 shall support the CM protocol features as shown in the tables below. Note 1. - The 'status' column indicates the level of support required for conformance to the CM-ASE protocol described in 2.1. The values are as follows: a) 'M' mandatory support is required; b) 'O' optional support is permitted for conformance to the CM protocol; c) 'N/A' the item is not applicable; and d) 'C.n' the item is conditional where n is the number which identifies the condition which applicable. Table 2.1.8-1. CM Protocol Versions Implemented -------------------------------------------------------------------------------- Status Associated Predicate -------------------------------------------------------------------------------- Version 1 M none -------------------------------------------------------------------------------- Table 2.1.8-2. CM Operational Functional Units -------------------------------------------------------------------------------- Status Associated Predicate -------------------------------------------------------------------------------- The CM system acts as a ground system C.1 CM/ground The CM system acts as an airborne system C.1 CM/air The ground CM system can update application information if CM/ground O else N/A G-UP-FU The ground CM system can request the aircraft to initiate a logon with a specified CM ground system if CM/ground O else N/A G-CO-FU The ground CM system can forward aircraft information to another CM ground system if CM/ground O else N/A G-FO-IN The ground CM user can process forwarded aircraft information if CM/ground O else N/A G-FO-FU The air CM user can process an update request if CM/air O else N/A A-UP-FU The air CM user can process a contact request if CM/air O else N/A A-CO-FU -------------------------------------------------------------------------------- C.1 a conformant implementation shall support one and only one of these options. Table 2.1.8-3. CM Ground Configurations -------------------------------------------------------------------------------- CM ground system List of Predicates Functionality Description -------------------------------------------------------------------------------- I CM/ground Logon exchanges are supported with an aircraft. Received forward requests are rejected with reason 'service not supported'. II CM/ground + G-FO-IN Logon exchanges are supported with an aircraft. Forward exchanges initiated by the local ground system user are supported. Received forward requests are rejected with reason 'service not supported'. III CM/ground + G-FO-FU Logon exchanges are supported with an aircraft. Received forward requests from peer CM ground systems are processed by the local CM user. IV CM/ground + G-FO-IN + G-FO-FU Logon exchanges are supported with an aircraft. Forward exchanges initiated by the local ground system user are supported. Received forward requests from peer CM ground systems are processed by the local CM user. V CM/ground + G-UP-FU Same as subset I plus the capability of a CM ground system to update application information on an aircraft. VI CM/ground + G-UP-FU + G-FO-IN Same as subset II plus the capability of a CM ground system to update application information on an aircraft. VII CM/ground + G-UP-FU + G-FO-FU Same as subset III plus the capability of a CM ground system to update application information on an aircraft. VIII CM/ground + G-UP-FU + G-FO-IN + G-FO-FU Same as subset IV plus the capability of a CM ground system to update application information on an aircraft. IX CM/ground + G-CO-FU Same as subset I plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system. X CM/ground + G-CO-FU + G-FO-IN Same as subset II plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system. XI CM/ground + G-CO-FU + G-FO-FU Same as subset III plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system. XII CM/ground + G-CO-FU + G-FO-IN + G-FO-FU Same as subset IV plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system. XIII CM/ground + G-CO-FU + G-UP-FU Same as subset I plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system and the capability of a CM ground system to update application information on an aircraft. XIV CM/ground + G-CO-FU + G-UP-FU + G-FO-IN Same as subset II plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system and the capability of a CM ground system to update application information on an aircraft. XV CM/ground + G-CO-FU + G-UP-FU + G-FO-FU Same as subset III plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system and the capability of a CM ground system to update application information on an aircraft. XVI CM/ground + G-CO-FU + G-UP-FU + G-FO-IN + G-FO-FU Same as subset IV plus the capability of a CM ground system to request an aircraft to perform a logon with a specified CM ground system and the capability of a CM ground system to update application information on an aircraft. -------------------------------------------------------------------------------- Note 2. - A CM ground system may or may not support the maintain dialogue feature. Table 2.1.8-4. CM Air Configurations -------------------------------------------------------------------------------- CM air system List of Predicates Functionality Description -------------------------------------------------------------------------------- I CM/air Logon exchanges can be initiated with ground systems. Received contact requests are rejected with reason 'contact not successful'. Received update requests are processed by the CM-ASE but ignored by the CM-user. II CM/air + A-UP-FU Logon exchanges can be initiated with ground systems. Received contact requests are rejected with reason 'contact not successful'. Received update requests are processed by the CM-ASE and the CM-user. III CM/air + A-CO-FU Logon exchanges can be initiated with ground systems. Received update requests are processed by the CM-ASE but ignored by the CM-user. Received contact requests are processed and acted upon by the CM-ASE and the CM-user. IV CM/air + A-UP-FU + A-CO-FU Logon exchanges can be initiated with ground systems. Received update requests are processed by the CM-ASE and the CM-user. Received contact requests are processed and acted upon by the CM-ASE and the CM-user. -------------------------------------------------------------------------------- Note 3. - A CM air system must support the maintain dialogue feature. SME Recommendation to CCB: RESOLVED CCB Decision: CCB-9 (Naples): SUBMITTED (17/05/99) CCB-8 (Naples): RESOLVED (19/05/99)