240 likes | 343 Views
Eric ALLAIX. DGAC-DSNA. WRC-12 A.I. 1.3. Summary. WRC Agenda Item 1.3 Resolution 421 What is UAS? What are we talking about? Invites 1 and 2 of Resolution 421 UAS applications LOS spectrum requirements BLOS spectrum requirements Candidate frequency bands
E N D
Eric ALLAIX DGAC-DSNA WRC-12A.I. 1.3
Summary • WRC Agenda Item 1.3 • Resolution 421 • What is UAS? • What are we talking about? • Invites 1 and 2 of Resolution 421 • UAS applications • LOS spectrum requirements • BLOS spectrum requirements • Candidate frequency bands • Current status of work in ITU-R • Possible regulatory actions • “Protected spectrum” Why? • Examples of risks using “non-safety” frequency allocations for satellite communications with UAS • ICAO position on AI 1.3
WRC-12 Agenda Item 1.3 => to consider spectrum requirements and possible regulatory actions, including allocations, in order to support the safe operation of unmanned aircraft systems (UAS), based on the results of ITU‑R studies, in accordance with Resolution 421 (WRC‑07)
Resolution 421 - Invites ITU-R • to conduct in time for WRC‑12 the necessary studies leading to technical, regulatory and operational recommendations to the Conference, enabling that Conference to decide on appropriate allocations for the operation of UAS • that the studies referred to in invites ITU‑R 1 should include sharing and compatibility studies with services already having allocations in those bands • to produce a report or a recommendation, as appropriate, on how to accommodate the radiocommunication requirements for UAS payloads
What is UAS? UAS: Unmanned Aircraft System An aircraft and its associated elements which is operated with no pilot on-board.
What are we talking about? Pilot ATC relay (satellite) Sense and Avoid relay (satellite) ATC (satellite) Command and control (satellite) Sense and Avoid ATC Command and control ATC Sense and Avoid ATC relay Remote pilot
Spectrum requirements and possible regulatory actions, including allocations, for safe operation of UAS Sharing and compatibility studies have to be completed with services already having allocations in the bands identified Invites 1 and 2 of Resolution 421 • Identification of the UAS applications • How much spectrum will be required in particular by taking into account the technical characteristics and the protection requirements? • Identification of current allocations that can accommodate UAS • Identification of additional frequency allocations if required • Ensuring compatibility with existing radiocommunication services • What possible regulatory actions will be required by the Conference?
1. Remote Pilot to UA 2. UA to Remote Pilot 2 1 ATC Control Station LOS spectrum requirements 34 MHz for links 1 and 2 below
Satellite Forward link: 1: Remote Pilot to satellite 2: Satellite to UA Return link: 3: UA to satellite 4: Satellite to Remote Control Station 3 2 4 UA 1 Control Station (mobile or fixed) or Gateway station (to which remote pilots are connected) ATC BLOS spectrum requirements 56 MHz for links 1, 2, 3 and 4 below
Candidate frequency bands (1/2) For LOS requirements : • 960 –1 164 MHz • Report ITU-R M. 2205 concludes that portion(s) of the existing AM(R)S allocation in the band 960-1 164 MHz can be used in some countries to support some UAS terrestrial spectrum requirements but cannot be used to meet the entire 34 MHz terrestrial spectrum requirement for UAS operations. • 5 000–5 150 MHz and 15.4-15.5 GHz • Studies are ongoing in WP 5B in these bands.
Candidate frequency bands (2/2) For BLOS requirements : • 5030-5091 MHz • Report ITU-R M. 2205 concludes that this band can be used to support the entire UAS satellite spectrum requirementsensuring the protection criteria for MLS. • 12/14 and 20/30 GHz • A Preliminary draft new report ITU-R M.[UAS-CNPC-CHAR]is under study in WP 5B.The purpose of this Report is to give examples of technical characteristics for the UAS CNPC links in certain frequency bands. But no technical studies have been done in these frequency bands
CURRENT STATUS OF WORK IN ITU-R (1/4) • ITU-R M.2171: • Characteristics of unmanned aircraft systems and spectrum requirements to support their safe operation in non‑segregated airspace • ITU-R M.2204: • Characteristics and spectrum considerations for sense and avoid systems use on unmanned aircraft systems • ITU-R M.2205: • Results of studies of the AM(R)S allocation in the band 960-1 164 MHz and of the AMS(R)S allocation in the band 5 030‑5 091 MHz to support control and non-payload communications links for unmanned aircraft systems
CURRENT STATUS OF WORK IN ITU-R (2/4) • Draft new Report ITU-R M.[UAS-BANDS-NEW-ALLOC-5 030-5 091 MHz] : • Frequency band study to support the line of sight Control and Non-Payload Communications (CNPC) link(s) for Unmanned Aircraft Systems (UAS) within new allocations in the band 5 030-5 091 MHz • Preliminary draft new Report ITU-R M.[UAS-BANDS-NEW-ALLOC-5 000-5 010 AND 5 010-5 030 MHz] : • Frequency band study to support the line of sight control and non-payload communications (CNPC) links for unmanned aircraft systems (UAS) within new allocations in the bands 5 000-5 010 and 5 010-5 030 MHz
CURRENT STATUS OF WORK IN ITU-R (3/4) • Preliminary draft new Report ITU-R M.[UAS-BANDS-NEW-ALLOC-5 091-5 150 MHz] : • Frequency band study to support line of sight control and non-payload communications (CNPC) links for unmanned aircraft systems (UAS) within new allocations in the band 5 091-5 150 MHz • Preliminary draft new Report ITU-R M.[UAS-BANDS-NEW-ALLOC-15.4-15.5 GHz] : • Frequency band study to support line of sight control and non-payload communications (CNPC) links for unmanned aircraft systems (UAS) within new allocations in the band 15.4-15.5 GHz
CURRENT STATUS OF WORK IN ITU-R (4/4) • Preliminary draft new Report ITU-R M.[UAS-CNPC-CHAR] : • Examples of technical characteristics for unmanned aircraft control and non-payload communications (CNPC) links • Bands for LOS • 960-1 164 MHz • 5 000-5 150 MHz • Bands for BLOS: • 1 545-1 555 MHz (space-to-Earth), 1 610-1 626.5 MHz (space-to-Earth and Earth‑to-space) and 1 646.5-1 656.5 MHz (Earth-to-space) • 5 030-5 091 MHz • 12/14 GHz • 20/30 GHz
Possible regulatory actions(1/3) CPM-11 report has been published • 7 methods are proposed to satisfy this agenda item: • 5 methods for the satellite component • 1 method for the terrestrial component • 1 method, covering both terrestrial and satellite components • All the allocations have to be used in such a way that the systems envisaged for UAS control and non-payload radiocommunications comply with ICAO SARPs • Any method or a combination of these methods described in the CPM-11 report may be used.
Possible regulatory actions (2/3) • Method B proposes new AM(R)S allocations for the terrestrial component. • Method C proposes no change to the Table of Frequency Allocations (RR Article 5) for frequency bands for which the studies have not been completed (for both terrestrial and satellite components, ).
Possible regulatory actions (3/3) • Five methods for the satellite component: • Method A1 proposes the use of the current AMS(R)S allocations for both links (unmanned aircraft to satellite and unmanned aircraft control station (mobile and fixed) to satellite); • Method A2 proposes the use of the current MSS, AMSS and AMS(R)S allocations for both links (unmanned aircraft to satellite and unmanned aircraft control station (mobile and fixed) to satellite) and FSS allocations (only for the fixed unmanned aircraft control station to satellite link) in accordance with the Radio Regulations; • Method A3 proposes the use of the current FSS allocations by adding a new footnote pointing toward a WRC Resolution/Recommendation (except frequency bands covered by Appendices 30, 30A and 30B to the Radio Regulations); • Method A4 proposes to restrict the communication link between unmanned aircraft and satellite to AMS(R)S allocations, to confirm the use of AMS(R)S allocations for the radiocommunication link between unmanned aircraft control station and the satellite and to allow the use of the FSS allocations for this link (except frequency bands covered by Appendices 30, 30A and 30B to the Radio Regulations); • Method A5 proposes new AMS(R)S allocations.
“Protected Spectrum”, why? • Introduction of UAS into non-segregated airspace must not reduce the current level of safety • ITU regulations provide special measures for the protection of safety communications • Those special measures are applicable to the AM(R)S, AMS(R)S and ARNS allocations used by all ICAO standardized C/N/S systems • Such measures are not applicable to other non-safety allocations, in particular to FSS, and consequently such allocations cannot be used for UAS without affecting the level of safety
UAS control Potential Interference Unmanned Aircraft flying over territory of State B Service regulated by State A Service regulated by State C Examples of risks using “non-safety” frequency allocations for satellite communications with UAS • Uncertain jurisdiction and responsibility for interference mitigation • Special measures in ITU Radio Regulations cannot be used for protection and interference mitigation • In a shared frequency allocation scenario, uncertain priority of access to UAS control • Majority of FSS allocations are not fully co-ordinated. In case incompatible assignments are made in two separate States, then UAS control is not afforded any protection against interference • In case of interference resolution, the UAS control service may be treated equally or lower than a television broadcast service
ICAO position To support, based on the results of studies identified in Resolution 421, any modification to existing allocations, or new allocations required to accommodate UAS operations in non-segregated airspace while maintaining the safety and regularity of flight of all types of aircraft. Accordingly, to ensure that allocations used, in particular, for UAS command and control, ATC relay and sense and avoid in non-segregated airspace are in the AM(R)S, AMS(R)S and/or ARNS and do not adversely affect existing aeronautical systems To oppose the use of this agenda item to seek new spectrum allocations to meet payload requirements.