AeroMACS SARPS Validation Activities – Contributions Table

EUROCONTROL, DRAFT v0.1, 2nd May 2014

Introduction

This document provides a full table of the AeroMACS SARPs requirements and identifies the validation activity planned for each of the SARPs, as well as identifies who is planning to support the validation activities for each of the AeroMACS SARPs.

This current draft of this paper is provided for discussion in WGS aiming to confirm the involvement of the identified contributors, as well as to agree on the proposed validation activity/methodology. This draft will be updated following feedback from the WGS members.

Note: The SARPS wording for the various sections of the table in this version needs to be rechecked and updated as required. The current wording and numbering is based on the paper presented by ECTL to WGS in February 2014 (based on the then available version of the draft SARPS).

AeroMACS Validation Report and Validation Methodology

It is proposed that the AeroMACS SARPs Validation Report (VR) is structured in four parts (sections) as described below:

1)Introduction identifying the validation methods used(definition/information) as well as the contributing exercises and any other relevant material

2)A table with the following columns:

  • SARPs number and SARPs text (title at least or also detailed SARP requirement text
  • Validation method or methods proposed/agreed/applied
  • Summary of validation result with references as required to Appendices with detailed reports from the various validation exercises

3)Conclusions of the validation

4)Appendices as required with the detailed validation information for the different SARPs (as referenced in section 2)

For section1 of the VR, it is proposed to use the UAT validation manual to capture the validation methodology and approach. An extract of the UAT is provided below identifying the 10 validation methods identified/used (as well as their acronyms).

It is proposed that the same validation methods and terminology are used for the AeroMACS VR.

In terms of validation exercises, input is expected from the SESAR, FAA/NASA and HITACHI activities.

For section 2, the following template is proposed to be used:

SARPs ID / Proposed / Agreed / Applied validation method / Validation Outcome
SARPs numbering and SARPs text (title at least, or also detailed SARP requirement text if required/agreed / Summary of validation result with references as required to Appendices with detailed reports from the various validation exercises / Summary of validation result with references as required to Appendices with detailed reports from the various validation exercises
… / … / …

AeroMACS SARPS validation – Contributions Table

The following table is provided to agree among the validation contributing parties the validation approach expected to be applied as well as to agree on the sharing (overlapping and duplication of validation activities is actually encouraged if possible) of the validation work. This table can also be used in the future to build/finalise the table for the ICAO validation report as proposed in the previous section (AeroMACS Validation Report and Validation Methodology).

AeroMACS SARPS Validation: Proposed validation Method(s) and Planned Contributions Table

no / SARPs Text / Proposed / required
validation method / SESAR Expected support / FAA/NASAExpectedsupport / HitachiExpected support / Notes
SESAR Verification objective / SESAR Project / SESAR Status
2 / GENERAL REQUIREMENTS / NVR
2.1 / GENERAL / NVR
2.1.1 / AeroMACS shall conform to the requirements of this and the following chapters. / NVR
2.1.2 / AeroMACS shall only transmit when on the surface of an aerodrome.
Note.- ITU Radio Regulations No.5.4.4.4B stipulate that the AeroMACS operation is limited to surface applications. / IB / AeroMACS_VVO_INT_06 / 15.2.7 / 9.16 / Stested[1]
2.1.3 / AeroMACS shall support aeronautical mobile (route) service (AM(R) S) communications. / IB / AeroMACS_VVO_Valid_01_A / SANDRA SP6 / Stested
2.1.4 / AeroMACS shall process messages according to their associated priority. / UT? / AeroMACS_VVO_Interop_04 / 15.2.7 / 9.16 / Ttested[2]
Stested
AeroMACS_VVO_Interop_05 / 15.2.7 / 9.16 / Stested
AeroMACS_VVO_Interop_07 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_Valid_04 / SANDRA SP6 / Stested
2.1.5 / AeroMACS shall support multiple levels of message priority. / UT / AeroMACS_VVO_Interop_04 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_Interop_05 / 15.2.7 / 9.16 / Stested
AeroMACS_VVO_Interop_07 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_Valid_04 / SANDRA SP6 / Stested
2.1.6 / AeroMACS shall support point to point communication. / UT / AeroMACS_VVO_Interop_01 / 15.2.7 / 9.16 / Ttested
AeroMACS_VVO_Interop_05 / 15.2.7 / 9.16 / Stested
2.1.7 / AeroMACS shall support multicast and broadcast communication services. / None
2.1.8 / AeroMACS shall support internet protocol (IP) packet data services. / UT / AeroMACS_VVO_Ground_03 / SANDRA SP6 / Stested
2.1.9 / AeroMACS shall provide mechanisms to transport ATN/IPS and ATN/OSI (over IP) based messaging. / AeroMACS_VVO_Ground_03
(Partially) / SANDRA SP6 / Stested[3]
2.1.10 / Recommendation.—AeroMACS should support voice services. / IA and IB ??? / Non-planned objective / SANDRA SP6 / Stested[4]
2.1.11 / An AeroMACS MS shall support multiple service flows simultaneously. / UT / AeroMACS_VVO_Interop_05 / 15.2.7 / 9.16 / Stested
2.1.12 / AeroMACS shall support adaptive modulation and coding. / UT / AeroMACS_VVO_Interop_02 / 15.2.7 / 9.16 / Ttested
AeroMACS_VVO_RF_01 / 15.2.7 / 9.16 / Ttested
2.1.13 / AeroMACS shall be implemented as an aerodrome cellular communications system where continuity in communication during aircraft movement is met by MS initiated AeroMACS handover procedures. / AeroMACS_VVO_RFReal_05 / 15.2.7 / 9.16
AeroMACS_VVO_Ground_04 / SANDRA SP6
2.1.14 / AeroMACS shall keep total accumulated interference levels with limits defined by the International Telecommunication Union - Radiocommunication Sector (ITU-R) as required by national/international rules on frequency assignment planning and implementation. / S / None / TBC
3 / RADIO FREQUENCY (RF) CHARACTERISTICS / NVR
3.1 / General Radio characteristics / NVR
3.1.1 / AeroMACS shall operate in time division duplex (TDD) mode. / AeroMACS_VVO_Interop_01 / 15.2.7 / 9.16 / Ttested
Stested
3.1.2 / AeroMACS shall operate with a 5 MHz channel bandwidth. / AeroMACS_VVO_Interop_01 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_RF_06 / 15.2.7 / 9.16 / Ttested
Stested
3.1.3 / AeroMACS antenna polarization shall be vertical. / Non-planned objective
(Partially) / SANDRA SP6 / Stested[5]
3.1.4 / AeroMACS shall operate without guard bands in between adjacent AeroMACS channels. / AeroMACS_VVO_RFReal_01 / 15.2.7 / 9.16
3.1.5 / AeroMACS shall operate according to the orthogonal frequency division multiple access method. / AeroMACS_VVO_Interop_01 / 15.2.7 / 9.16 / Ttested
Stested
3.1.6 / AeroMACS shall support both segmented partial usage sub-channelisation (PUSC) and PUSC with all carriers as sub-carrier permutation methods. / AeroMACS_VVO_Interop_02 (Partially) / 15.2.7 / 9.16
3.2 / Frequency Bands / NVR
3.2.1 / The AeroMACS equipment shall be able to operate in the band from 5030 MHz to 5150 MHz in channels of 5 MHz bandwidth.
Note 1.— Some States may, on the basis of national regulations, have additional allocations to support AeroMACS. Information on the technical characteristics and operational performance of AeroMACS is contained in the European Organisation for Civil Aviation Equipment (EUROCAE) Document ED-223, AeroMACS Minimum Operational Performance Specification (MOPS) and ED-227, AeroMACS Minimum Aviation System Performance Standard (MASPS) .
Note 2. — The last center frequency of 5145 MHz is selected as the reference frequency. AeroMACS nominal center frequencies are referenced downward from the reference frequency in 5 MHz steps. / AeroMACS_VVO_Interop_01 (Partially [5091-5150]) / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_RFReal_01 (Partially [5091-5150]) / 15.2.7 / 9.16
3.2.2 / The mobile equipment shall be able to operate at center frequencies offset from the preferred frequencies, with that offset having a 250 KHz step size.
Note. — The nominal center frequencies are the preferred center frequencies for AeroMACS operations. However, the base stations should have the capability to deviate from the preferred center frequencies to satisfy potential national spectrum authority implementation issues (i.e. to allow AeroMACS operations while avoiding receiving or causing interference to other systems operating in the band such as MLS and AMT). / AeroMACS_VO_Interop_01 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_RF_06 / 15.2.7 / 9.16 / Ttested
Stested
3.3 / RADIATED POWER / NVR
3.3.1 / The total mobile station effective isotropic radiated power (EIRP) shall not exceed 30 dBm / AeroMACS_VVO_RF_08 / 15.2.7 / 9.16 / Stested / TBC
3.3.2 / The total base station EIRP in a sector shall not exceed:
a) 39.4 dBm for elevation angles from the horizon up to 1.5 degrees
b) 39.4 dBm linearly decreasing (in dB) to 24.4 dBm for elevation angles from 1.5 to 7.5 degrees
c) 24.4 dBm linearly decreasing (in dB) to 19.4 dBm for elevation angles from 7.5 to 27.5 degrees
d) 19.4 dBm linearly decreasing (in dB) to 11.4 dBm for elevation angles from 27.5 to 90 degrees
Note 1.— EIRP defined as antenna gain in a specified elevation direction plus the average AeroMACS transmitter power. While the instantaneous peak power from a given transmitter may exceed that level when all of the subcarriers randomly align in phase, when the large number of transmitters assumed,, average power is the appropriate metric.
Note 2.— If a sector contains multiple transmit antennas (e.g., multiple input multiple output (MIMO)antenna), the specified power limit is the sum of the power from each antenna. / None / TBC
3.4 / MINIMUM RECEIVER SENSITIVITY / NVR
3.4.1 / The sensitivity level is defined as the power level measured at the receiver input when the bit error rate (BER) is equal to 1*10-6. / TBC
3.4.2 / The AeroMACS reciver sensitivity shall comply with table X-1 – AeroMACS Receiver Sensitivity values.
Note 1.—The computation of the sensitivity level for the AeroMACS is described in XXX guidance material
Note 2.— AeroMACS minimum receiver sensitivity would be 2 dB lower than indicated if CTC is used.
Table X-1 – AeroMACS Receiver Sensitivity values
Modulation scheme using CC encoding scheme / Rep. Factor / MS Sensitivity / BS Sensitivity
64 qam 3/4 / 1 / -74.37 dBm / -74.50 dBm
64 qam 2/3 / 1 / -76.37 dBm / -76.50 dBm
16 qam 3/4 / 1 / -80.37 dBm / -80.50 dBm
16 qam 1/2 / 1 / -83.87 dBm / -84.00 dBm
qpsk 3/4 / 1 / -86.37 dBm / -86.50 dBm
qpsk 1/2 / 1 / -89.50 dBm / -89.50 dBm
qpsk 1/2 with repetition 2 / 2 / -92.37 dBm / -92.50 dBm
Note .— 64 QAM transmission is optional for MS. / AeroMACS_VVO_Interop_02 / 15.2.7 / 9.16 / Ttested
Stested / TBC
AeroMACS_VVO_RF_07 / 15.2.7 / 9.16 / Stested
3. 5 / Emissions / NVR
3.5.1 / The power spectral density of the emissions must be attenuated below the output power of the transmitter as follows:
a)On any frequency removed from the assigned frequency between 0–45% of the authorized bandwidth (BW): 0 dB.
b)On any frequency removed from the assigned frequency between 45–50% of the authorized bandwidth: 568 log (%of (BW)/45) dB.
c)On any frequency removed from the assigned frequency between 50–55% of the authorized bandwidth: 26 + 145 log (% of BW/50) dB.
d)On any frequency removed from the assigned frequency between 55– 100% of the authorized bandwidth: 32 + 31 log (% of (BW)/55) dB.
e)On any frequency removed from the assigned frequency between 100–150% of the authorized bandwidth: 40 +57 log (% of (BW)/100) dB.
f)On any frequency removed from the assigned frequency between above 150% of the authorized bandwidth: 50 dB or 55 + 10 log (P) dB, whichever is the lesser attenuation.
g)The zero dB reference is measured relative to the highest average power of the fundamental emission measured across the designated channel bandwidth using a resolution bandwidth of at least one percent of the occupied bandwidth of the fundamental emission and a video bandwidth of 30 kHz. The power spectral density is the power measured within the resolution bandwidth of the measurement device divided by the resolution bandwidth of the measurement device. Emission levels are also based on the use of measurement instrumentation employing a resolution bandwidth of at least one percent of the occupied bandwidth. / h) / AeroMACS_VVO_RF_08 / 15.2.7 / 9.16 / Ttested
Stested / TBC
3.5.2 / The AeroMACS radios shall implement power control.
Note.— The purpose of this requirement is to minimize harmful interference to other aeronautical systems which can result from radiated and/or conducted emissions that include harmonics, discrete spurious, inter-modulation products and noise emissions. / AeroMACS_VVO_RF_08 / 15.2.7 / 9.16 / Stested / TBC
AeroMACS_VVO_RF_09 / 15.2.7 / 9.16
3.5.3 / AeroMACS minimum rejection for adjacent (+/–5MHz) channel – measured at BER=10-6 level for a victim signal power 3 dB higher than the receiver sensitivity - shall be 10 dB for 16 QAM 3/4. / AeroMACS_VVO_RF_04 / 15.2.7 / 9.16 / TBC
3.5.4 / AeroMACS minimum rejection for adjacent (+/–5MHz) channel measured at BER=10-6 level for a victim signal power 3 dB higher than the receiver sensitivity shall be 4 dB for 64 QAM 3/4. / AeroMACS_VVO_RF_04 / 15.2.7 / 9.16 / TBC
3.5.5 / AeroMACS minimum rejection for second adjacent(+/–10MHz) channel and beyond – measured at BER=10-6 level for a victim signal power 3 dB higher than the receiver sensitivity - shall be 29 dB for 16 QAM 3/4. / None / TBC
3.5.6 / AeroMACS minimum rejection for second adjacent (+/–10MHz) channel and beyond – measured at BER=10-6 level for a victim signal power 3 dB higher than the receiver sensitivity - shall be 23 dB for 64 QAM 3/4.
Note.— for additional clarification, to the requirements stated in paragraph 3.5.3,3.5.4,3.5.5 and 3.5.6, refer toIEEE 802.16-2009 section 8.4.14.2. / None / TBC
3. 6 / Susceptibility / NVR
3.6.1 / AeroMACS equipment shall meet the performance requirements of Chapter 4 when operating in an interference environment causing a cumulative relative change in receiver noise temperature of (∆T/T) of 25 %. / None / TBC (to be done in CLE?)
4 / PERFORMANCE REQUIREMENTS / NVR
4.1 / AeroMACS COMMUNICATIONS SERVER PROVIDER REQUIREMENTS / NVR
4.1.1 / The maximum unplanned service outage duration on a per aerodrome basis shall be 6 minutes;
Note.— A partial service outage is equivalent to full outage if the partial outage means any of the other performance requirements of Chapter 4 are not met. / None / TBC
4.1.2 / The maximum accumulated unplanned service outage time on per aerodrome basis shall be 240 minutes/year. / None
4.1.3 / The maximum number of unplanned service outages per 4 month period shall not exceed 4. / None / TBC
4.1.4 / The mean time between unplanned service outages shall not be less than 876 hours per year. / None
4.2 / The Mobile Station (MS) Requirements / NVR
4.2.1 / The MS shall meet the performance requirements contained in sections 3 and 4.3, 4.5, 4.6 and 4.7 when operating with any Doppler velocity up to 50 nautical miles per hour. / AeroMACS_VVO_RFReal_08 / 15.2.7 / 9.16 / Stested
SANDRA SP7
(Partially) / Stested
AeroMACS_VVO_RF_04 / 15.2.7 / 9.16
4.3 / Delay Parameters / NVR
4.3.1 / Subnetwork entry time shall be less than 90 seconds. / AeroMACS_VVO_Interop_03 / 15.2.7 / 9.16 / Stested / TBC
Specific measurement / Specific measurement / Ttested
4.3.2 / Recommendation .— Subnetwork entry time should be less than 20 seconds . / AeroMACS_VVO_Interop_03 / 15.2.7 / 9.16 / Stested
Specific measurement / Specific measurement / Ttested
4.3.3 / The from-MS data transit delay (95th percentile), shall be less than or equal to 1.4 seconds over a window of 1 hour or 600 messages, whichever is longer for the highest priority data service. / None
To be considered / TBC
4.3.4 / The to-MS data transit delay (95th percentile), shall be less than or equal to 1.4 seconds over a window of 1 hour or 600 messages, whichever is longer for the highest priority data service. / None
To be considered / TBC
4.4 / INTEGRITY / NVR
4.4.1 / ???
Residual error rate, to/from-MS. The residual error rate in the from-MS direction shall be less than or equal to 5 x 10-8 per SNSDU. / Requirement under development / TBC
4.4.2 / ???? / TBC
4.4.4 / ???Max BER ???? / TBC
4.5 / Voice Service Performance / NVR
4.5.1 / When AeroMACS supports VOIP as packetized data, it shall meet the requirements specified in section XXX Doc 9896. / NVR, IB / None / Reference to ICAO IPS doc that is supporting EUROCAE WG67 docs????
4.6 / SECURITY SERVICE / NVR
4.6.1 / AeroMACS shall provide a capability to protect the integrity of messages in transit.
Note.— The capability includes cryptographic mechanisms to provide integrity of messages in transit. / AeroMACS_VVO_Interop_11 (¿Partially?) / 15.2.7 / 9.16 / Stested / TBC / TBC
4.6.2 / AeroMACS shall provide a capability to ensure the authenticity of messages in transit.
Note.— The capability s includes cryptographic mechanisms to provide authenticity of messages in transit. / AeroMACS_VVO_Interop_11 / 15.2.7 / 9.16 / Stested / TBC / TBC
4.6.3 / AeroMACS shall provide a capability to protect the availability of the system.
Note.— The capability s includse measures to ensure that the system and its capacity are available for authorized uses during unauthorized events. / None / TBC / TBC
4.6.4 / AeroMACS shall provide a capability to protect the confidentiality of messages in transit.
Note.— The capability includes cryptographic mechanisms to provide encryption/decryption of messages. / AeroMACS_VVO_Valid_06 / SANDRA SP6 / TBC / TBC
AeroMACS_VVO_Interop_11 / 15.2.7 / 9.16 / Stested
4.6.5 / AeroMACS shall provide an authentication capability.
Note.— The capability includes cryptographic mechanisms to provide peer entity authentication, mutual peer entity authentication, and data origin authentication. / AeroMACS_VVO_Interop_03 / 15.2.7 / 9.16 / Stested / TBC / TBC
SANDRA SP6 / Stested
AeroMACS_VVO_Interop_11 / 15.2.7 / 9.16 / Stested
4.6.6 / AeroMACS shall provide a capability to authorize the permitted actions of users of the system.
Note.— The capability s includes mechanisms to explicitly authorize the actions of authenticated users. Actions that are not explicitly authorized are denied. / AeroMACS_VVO_Interop_11 / 15.2.7 / 9.16 / Stested / TBC / TBC
4.6.7 / If AeroMACS provides interfaces to multiple information domains, AeroMACS shall provide capability to prevent intrusion from lower integrity information domain to higher integrity information domain. / None
Possibly some simulation results / TBC / TBC
4.7 / CONTINUITY OF SERVICE / NVR
4.7.1 / Connection resilience. The probability that a transaction will be completed once started shall be at least .9996 over any one-hour interval . / None / TBC
5 / SYSTEMS INTERFACES AND APPLICATION REQUIREMENTS / NVR
5.1 / SYSTEM INTERFACES / NVR
5.1.1 / AeroMACS shall provide data service interface to the system users. / None
5.1.2 / AeroMACS shall support link layer switching. / None
5.1.3 / AeroMACS shall support notification of the loss of communications. / None / Stested
5.2 / APPLICATION REQUIREMENTS / NVR
5.2.1 / AeroMACS shall support multiple classes of services to provide appropriate service levels to applications. / AeroMACS_VVO_Interop_04 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_Interop_05 / 15.2.7 / 9.16 / Stested
AeroMACS_VVO_Interop_07 / 15.2.7 / 9.16 / Ttested
Stested
AeroMACS_VVO_Valid_04 / SANDRA SP6 / Stested
5.2.2 / If there is a resource contention, AeroMACS shall pre-empt lower priority service(s) in favour of higher priority service(s). / AeroMACS_VVO_Interop_04 / 15.2.7 / 9.16 / Ttested
Stested

[1]Stested means Selex or Airbus Test in P9.16/15.2.7 or SANDRA SP6/SP7 done. One should keep in mind that this is not in any case a full verification of SARPS as prototypes development (and SESAR/SANDRA docs) were issued before or in // with SARPS to give inputs to SARPS.

[2] Ttested means Thales Lab Test in P1527 done see VR pr0003_02 on SJU Extranet. One should keep in mind that this is not in any case a full verification of SARPS as prototypes development (and SESAR docs) were issued before or in // with SARPS to give inputs to SARPS.

[3] ATN/OSI (over IP) based messaging tested

[4]VoIP Service was tested even if not initially planned

[5]Antennas with vertical polarization were used in some tests in SANDRA