ACP WG-F/26 WP-09

INTERNATIONAL CIVIL AVIATION ORGANIZATION

26THMeetingof the Aeronautical Communication Panel Working Group F

(ACP WG-F/26)

(Montreal, 21 – 30March 2012)

Agenda Item 2.Outcome of WRC-12–General

Agenda Item 6.Development of material for ITU-R meetings

Final Report of the Correspondence Group

Dealing with WRC-12 Agenda Item 1.7

(Presented by SUZUKI,Yoshio, Coordinator CG 1.7)

SUMMARY
WRC-12 provided a new annex to Resolution 222 to ensure long-term spectrum access for the AMS(R)Sand to provide a new Resolution [COM4/1] for the development of methodology to calculate AMS(R)S spectrum requirements.
It is expected that AMS(R)S spectrum requirements could be satisfied in the frequency coordination process under modified Resolution 222, but it requires further efforts by the aviation community to develop appropriate ITU-R Recommendation and to implement appropriate process to accommodate AMS(R)S spectrum requirements in practice.
According to modified Resolution 222, ICAO isinvited to evaluate and comment on the AMS(R)S traffic requirements received from individual administrations, on the basis of the known global and regional aviation traffic requirements, including the time-scale of regional and global communication requirements,
Therefore ICAO may participate in the process of determining AMS(R)S spectrum requirements by validating communications traffic data brought to ICAO by AMS(R)S operators.
Resolution [COM4/1] invited ICAO and IATA to participate in the studies identified in to conduct studies on, and develop in one or more ITUR Recommendations, a methodology, including clear definitions of input parameters and assumptions to be used, to calculate spectrum requirements
ICAO would be asked to consider and recommend appropriate input parameters mainly for information relating to estimate aviation communication traffics and conditions to ensure required operational and safety level for AMS(R)S communications.
Based on the above discussions, the correspondence group provided a draft final report as attached for the consideration at the WG-F/26 meeting.
ACTION
The meeting is asked to consider the attachment of this paper and to confirm the role of ICAO in the process of frequency coordination responding to“invite ICAO” in the Resolution 222(Rev. WRC-123) and participation in the ITU-R WP 4C activities.
If possible, it is also encouraged to develop elements for the WP 4C contribution to develop the ITU-R Recommendation of the procedures to determine AMS(R)S spectrum requirements responding to Resolution [COM4/1](WRC-12).

1. Background

The 25th meeting of the Working Group F considered the interim report of the Correspondence Group dealing with WRC-12 Agenda Item 1.7 including discussions on three major issues identified as well as outcomes of the CPM, ITU-R WP 4C and regional preparatory meetings relating to Agenda Item 1.7.

The Working Group provided guidelines for member states towards WRC-12 Agenda Item 1.7 to explain interest of aviation group in the Conference.

WRC-12 considered measures to satisfy Agenda Item 1.7 and agreed to provide a new annex to Resolution 222indicating procedures to implement No.5.357A and Resolution222 to ensure long-term spectrum access for the AMS(R)S and to provide a new Resolution [COM4/1] (WRC12) for the development of methodology to calculate AMS(R)S spectrum requirements.

2. Discussion

WRC-12 provided a new annex to Resolution 222 to ensure long-term spectrum access for the AMS(R)Sand to provide a new Resolution [COM4/1] for the development of methodology to calculate AMS(R)S spectrum requirements.

It is expected that AMS(R)S spectrum requirements could be satisfied in the frequency coordination process under modified Resolution 222, but it requires further efforts by the aviation community to develop appropriate ITU-R Recommendation and to implement appropriate process to accommodate AMS(R)S spectrum requirements in practice.

According to Radio Regulation, frequency coordination is a subject to the notifying administrations concerned and therefore results, details of discussions and conditions agreed are to be kept as confidential.

However, under the new procedures provided by Annex to Res. 222, sufficient transparency of process to accommodate spectrum requirements are considered to satisfy interest of aviation community as far as possible.

In addition, as for the estimation of aviation traffics, it is considered that information and suggestions provided by aviation experts such as ICAO would be useful and important.

According to modified Resolution 222, ICAO isinvited to evaluate and comment on the AMS(R)S traffic requirements received from individual administrations, on the basis of the known global and regional aviation traffic requirements, including the time-scale of regional and global communication requirements,

Therefore ICAO may participate in the process of determining AMS(R)S spectrum requirements by validating communications traffic data brought to ICAO by AMS(R)S operators.

Resolution [COM4/1] invited ICAO and IATA to participate in the studies identified in to conduct studies on, and develop in one or more ITUR Recommendations, a methodology, including clear definitions of input parameters and assumptions to be used, to calculate spectrum requirements

According to a method under consideration in the ITU-R WP 4C, various input information/parameters are used for the calculation of the AMS(R)S spectrum requirements.

ICAO would be asked to consider and recommend appropriate input parameters mainly for information relating to estimate aviation communication traffics and conditions to ensure required operational and safety level for AMS(R)S communications.

Based on the above discussions, the correspondence group provided a draft final report as attached for the consideration at the WG-F/26 meeting.

3. Proposed Action

The meeting is asked to consider the attachment of this paper and to confirm the role of ICAO in the process of frequency coordination responding to“invite ICAO” in the Resolution 222(Rev. WRC-123) and participation in the ITU-R WP 4C activities.

If possible, it is also encouraged to develop elementsfor the WP 4C contribution to develop the ITU-R Recommendation of the procedures to determine AMS(R)S spectrum requirements responding to Resolution [COM4/1](WRC-12).

Attachment

Draft

Final Report of the Correspondence Group

Dealing with WRC-12 Agenda Item 1.7

1. Introduction

The 25th meeting of the Working Group F considered the interim report of the Correspondence Group dealing with WRC-12 Agenda Item 1.7 including discussions on three major issues identified (WP12) as well as outcomes of the CPM, ITU-R WP 4C and regional preparatory meetings relating to Agenda Item 1.7 (IP3 to 6).

The Working Group provided guidelines for member states towards WRC-12 Agenda Item 1.7 to explain interest of aviation group in the Conference. (Reference 1)

WRC-12 considered measures to satisfy Agenda Item 1.7 and agreed to provide a new annex to Resolution 222indicating procedures to implement No.5.357A and Resolution222 (Rev.WRC12) to ensure long-term spectrum access for the AMS(R)S (Reference 2) and to provide a new Resolution [COM4/1] (WRC12) for the development of methodology to calculate AMS(R)S spectrum requirements. (Reference 3)

This document provides a final report of the correspondence group to be submitted to the 26th WG-F meeting.

2. Objectives of the Correspondence Group and its Terms of Reference

Objectives of the Correspondence Group agreed at the WG-F/25 is to consider the role of ICAO proposed within Method B and to consider improvement of methodology for determining AMS(R)S spectrum requirements easing some of the concerns of Method B.

Terms of Reference for the group are;

(1) To consider a strategy to improve procedures to satisfy Agenda Item 1.7 based on Method B

(2) To consider methodology to determine AMS(R)S spectrum requirements especially for providing input information such as AMS(R)S traffics requirements

(3) To consider ICAO role in the above process

(4) To report progress of the Correspondence Group to WG-F meetings

3. Discussions

(Issue 1) Strategy to improve procedures to satisfy Agenda Item 1.7 based on Method B

Four different methods were shown in the CPM Report and Method B including following procedures seemed to be an appropriate method to improve current MSS frequency coordination process supported by Asia-Pacific and South American Administrations.

(a) To determine AMS(R)S spectrum requirements under agreed methodology preferably through global expert group (such as consultation meeting)

(b) To satisfy AMS(R)S spectrum requirements at the MSS frequency coordination meeting by assigning AMS(R)S spectrum prior to other MSS networks

(c) To confirm compatibility of assigned AMS(R)S spectrum with other MSS assignments of other geographic areas.

The method D proposed by North American Administrations and supported by African Administrations also seems to be acceptable since it indicates responsibility of the notifying Administrations to accommodate AMS(R)S spectrum requirements and proposing to develop agreed methodology for the calculation of AMS(R)S spectrum requirements in the form of ITU-R Recommendation.

CEPT has been considering a compromized method with Methods A and B such as organizing reassessment meeting in the case that AMS(R)S spectrum requirement is not satisfied at the coordination meeting instead of consultation meeting.

APT has also proposing integrated ideas of Methods A, B and D to modify current Res. 222 by enhancing indicating to determine AMS(R)S spectrum requirements through expert group and to satisfy priority of AMS(R)S spectrum access without any annex.

Brazil, Egypt and Japan proposed a new annex to enhance current Res. 222 but to ease objections and concerns on the Method B raised by MSS operators.

After lengthy discussionson all issues proposed above, WRC-12 finally agreed to develop a new Annex to Res. 222 including procedures to improve current practices;

(i) To determine AMS(R)S spectrum requirements under agreed methodology in the form of ITU-R Recommendation,

(ii) To accommodate validated spectrum requirements in the frequency coordination process,

(iii) To report total AMS(R)S spectrum assignments to BR, and in the case of spectrum requirements was not satisfied, notifying AMS(R)S Administration may request BR to hold reassessment meeting to confirm its fact,

(iv) To hold additional coordination meeting to satisfy AMS(R)S spectrum requirements if required.

(Issue 2) Input information and conditions to be used for the calculation of AMS(R)S spectrum requirements

Resolution [COM4/1] invited ICAO and IATA to participate in the studies identified in to conduct studies on, and develop in one or more ITUR Recommendations, a methodology, including clear definitions of input parameters and assumptions to be used, to calculate spectrum requirements

In the process to calculate AMS(R)S spectrum requirements, input parameters and conditions are important and they are to be presented based on reliable sources which ITU-R members would recognize.

According to a method under consideration in the ITU-R WP 4C, various input information/parameters are used for the calculation of the AMS(R)S spectrum requirements.

They are divided into two categories, (1) information relating to estimate aviation communication traffics, and (2) information relating to convert communication traffics to required spectrum.

ICAO would be asked to consider and recommend appropriate input parameters mainly for category (1) and conditions to ensure required operational and safety level for AMS(R)S communications.

Annex 1shows descriptions of basic input parameters and assumptions relating to estimate aviation traffics for the calculation of the AMS(R)S spectrum requirements and related information and Annex 2 shows glossaries to be considered at the next WP 4C meeting

.

(Issue 3) ICAO role in the process of AMS(R)S frequency coordination

It is noted that, according to Radio Regulation, frequency coordination is a subject to the notifying administrations concerned and therefore results, details of discussions and conditions agreed are to be kept as confidential.

However, under the new procedures provided by Annex to Res. 222, sufficient transparency of process to accommodate spectrum requirements are considered to satisfy interest of aviation community as far as possible.

In addition, as for the estimation of aviation traffics, it is considered that information and suggestions provided by aviation experts such as ICAO would be useful and important.

To achieve such principle, in the process of determining AMS(R)S spectrum requirements, input parameters and their conditions are important and critical, therefore they are to be presented based on reliable sources which ITU-R members would recognize.

Therefore, modified Resolution 222 invited,

1administrations, if they so desire, to have their AMS(R)S traffic requirements submitted to ICAO before the frequency coordination meeting;

2ICAO to evaluate and, as appropriate, comment on the AMS(R)S traffic requirements received from individual administrations, on the basis of the known global and regional aviation traffic requirements, including the time-scale of regional and global communication requirements,

ICAO may participate in the process of determining AMS(R)S spectrum requirements by validating communications traffic data brought to ICAO by AMS(R)S operators.

These AMS(R)S communications traffics data may be defined by a special group organized by ICAO.

ICAO is encouraged to participate in the work of developing ITU-R Recommendation to calculate/validate AMS(R)S spectrum requirements mainly in the area of estimating aviation communication traffics

4. Conclusion and proposal

WRC-12 considered measures to satisfy Agenda Item 1.7 and provided a new annex to Resolution 222 to ensure long-term spectrum access for the AMS(R)Sand to provide a new Resolution [COM4/1] for the development of methodology to calculate AMS(R)S spectrum requirements.

It is expected that AMS(R)S spectrum requirements could be satisfied in the frequency coordination process under modified Resolution 222, but it requires further efforts by the aviation community to develop appropriate ITU-R Recommendation and to implement appropriate process to accommodate AMS(R)S spectrum requirements in practice.

WG-F is asked to consider the Attachment, especially on the role of ICAO in the process of frequency coordination as invite ICAO in the Resolution 222 and participation in the ITU-R WP 4C activities.

References

(1) Attachment F to WG-F/25 Report: Guidelines for member states towards WRC-12 Agenda Item 1.7

(2) Resolution 222 (Rev. WRC-12): Use of the frequency bands 1525-1559MHz and 1626.5-1660.5MHzby the mobile-satellite service, and procedures to ensure long-term
spectrum access for the aeronautical mobile-satellite (R) service

(3) Resolution [COM4/1]: Development of methodology to calculate aeronautical mobile-satellite (R) service spectrum requirements within the frequency bands 1545-1555MHz (space-to-Earth) and 1646.5-1656.5MHz (Earth-to-space)

(4) Annex 6 to Doc.4C/660: Working documents towards a preliminary draft new Report ITU-R M.[AMS(R)S.METHODOLOGY], General principles, guidelines and example methodology(ies) to calculate spectrum requirements to satisfy AMS(R)S access within the bands 15451555MHz (space-to-Earth) and 1646.5-1656.5MHz (Earth-to-space)

ANNEX 1

Descriptions of Basic Input Parameters and Assumptions relating to estimate Aviation Traffics for the Calculation of the AMS(R)S Spectrum Requirements and other Information

Attachment 6 to Doc. 660 provides working documents towards a preliminary draft new Report ITU-R M.[AMS(R)S.METHODOLOGY] including some considerations and examples of methodologies to determine spectrum requirements to satisfy AMS(R)S access within the bands 1545-1555MHz (space-to-Earth) and 1646.5-1656.5MHz (Earth-to-space) and it is expected that appropriate Recommendation(s) are to be developed during the next ITUR study period based on this ITUR Report.

There are a number of procedural observations, questions, and suggestions related to the methodologies proposed within. In some instances while the proposed methodologies may include suggestions for addressing certain issues, their scope may reach beyond the intent of this document affecting regulations, recommended practices or deployment plans. As such, these issues are provided here in the form of observations and/or questions simply to provide focus for future discussions.

Synergies are of particular importance when dealing with the complex challenges faced when developing AMS(R)S spectrum requirements. Any implementation techniques that can be identified to simplify, reduce cost and hasten the execution of the proposed methodologies will be of great value and sharing of these is to be encouraged going forward. In this light the suggestions below are included. They are not intended to be prescriptive in any way but rather considered as an aid that may be included in the development of a final recommendation.

1Input Parameters

Input parameters to be used for the calculation of AMS(R)S spectrum requirements may be based on known facts, measurements, historic or similarity inference, simulations, forecasts, and estimates. However, each input should be based on the most valid source available at the time of the coordination process. The list provided below gives examples of inputs that may be required to implement the methodologies to be developed.

It should be noted that all of the information contained in this section may not be needed as an input.

a)Detailed information concerning the air traffic characteristics (airliner, cargo, and general aviation) such as latitude/longitude boundaries of the air space and any crossing of these boundaries; flight routes and schedule, additional unscheduled flights that would typically be added by airliners; aircraft equipage, number of aircraft equipped with AES terminals and model of AES terminal registered with the satellite operator, to the extent available.

b)AMS(R)S terminal characteristics: This should be provided by the AMS(R)S satellite operator for all carrier types supported by its satellite system. Characteristics should include information such as:

–bit rate as a function of C/N0;

–service types supported: data, i.e.voice, broadcast, addressed, party-line;

–reference information bit rate: pilot signals, channel feedback information;

–signalling bits employed: data link signalling, acknowledgements, other;

–error correction bits employed: coding, parity;

–guard time bits; for TDMA carriers;

–preamble bits;

–range of message size, frame size, packet size, segment size, and window size;

–other protocol information, e.g.header bits and , queuing algorithms used.

This information might also be provided more generically, e.g.on a message basis with typical and maximum information and overhead bits provided.

c)Voice traffic characteristics: For example, the average Erlang load by aircraft is needed and might be provided via measured data or from statistical references. Table6-24 of the “Communications Operating Concept and Requirements for the Future Radio System”, Version 2 (COCRv2) report provides the ATS related party-line voice transmission characteristics based on a survey of studies.

d)Detailed information on AMS(R)S Data traffic characteristics: To support queuing model analyses, traffic characteristics for each priority service and any network management services are needed. These characteristics may include: service instance rate, message quantity and message sizes. However what is needed for the queuing model is the message arrival rate, and the message size.

e)QoS performance requirements: Performance thresholds required include: transit delay (latency), integrity (bit error rate), availability of provision, and call establishment delay. Thresholds should be provided for each service class and airspace domain associated with priority communications, levels 1 to 6 specified in ITUR Article44 plus any network management service required. Reference [2] provides a cross-classification between ITU priority levels and COCR defined ATS and AOC communications[1]. This cross-classification is summarized in Table1 of AppendixA. The COCR provides QoS threshold in compliance with RCTA defined parameters as well as safety and operational review results conducted as part of the COCR study. However the QoS requirements were based on air to air and air/ground/air communications so the QoS thresholds may need to be adjusted to account for the operational limits of satellite communication links.