240 likes | 254 Views
This document outlines the purpose, development, and common evaluation scenarios of the Communications Operating Concept & Requirements (COCR) for aircraft traffic. It covers the development of Version 2.0 and outlines the key requirements for communications in different phases of flight.
E N D
Communications Operating Concept & Requirements (COCR) ICAO ACP WG-T Montreal 2- 5 October 2007 Gregg Anderson - FAA Danny van Roosbroek - EUROCONTROL
Outline • Purpose of the COCR • Development of Version 2.0 • Common Evaluation Scenarios • Conclusions
Aircraft Traffic Communications A Day in 2025 • More than double today’s traffic • Advanced ATC concept • Data is Primary • … • T -Throughput • C - Continuity • I - Integrity • A - Availability
COCR development • Joint EUROCONTROL/FAA activity through common team • Based on potential operational scenarios available at the time in medium and long term • Phase 1 – to 2020 • Phase 2 – 2020+ • Paradigm shift between Phases when data communications becomes the ‘normal’ means of communication • Future radio system is aimed at supporting the Phase 2 requirements • Primarily for data communication • COCR carried out an analysis to support these requirements in various phases of flight
Overview of the COCR (1/3) • Captures the operational requirements for Phase 1 (from now to 2020) and Phase 2 (beyond 2020) • Concept in Phase 1 is drawn largely from available material at the time i.e. the EUROCONTROL ATM concept document for 2008-11 & 2020 and beyond • Concepts in Phase 2 are based on more extensive use of Phase 1 services and more advanced operations (e.g. 4D Trajectory Management) • Autonomous operations take place in some parts of the airspace • Based on postulated ATS operational concept using existing documentation and extending it into the future • Broadly in-line with SESAR and NextGen concepts of operation
Overview of the COCR (2/3) • From the operational concepts, information flows have been identified in representative test volumes of airspace i.e. ‘positions/sectors’ in Airport, TMA, En Route, & Oceanic. • Airport positions & Radar sectors in Phase 1 similar to today • Radar sectors larger in Phase 2, perhaps 2-3x. Airport positions pretty much the same as Phase 1 • Covers all ATS and AOC air-to-ground and air-to-air voice and data communication • Includes ADS-B and AOC applications • Includesmicro-jets & UAV’s (only ATC control element) • Does not include Air Marshall, UAV Command & Control, SWIM, or spacecraft communications
Overview of the COCR (3/3) • Identifies all communication requirements based on safety and security analysis • Availability, continuity, reliability and latency • Requirements are technology independent • Communication requirements are then used in a queuing model for communication loading (b/s per service volume) • Aircraft numbers are grown over time using EUROCONTROL SAAM data in ECAC – MLM in US
Final COCR Version 2.0 • Final version of the COCR completed in March 07 – • Presented at ACP/1 • Responded to comments received on COCR Version 1.0 and clarify areas of ambiguity • Ensured satisfactory agreement among stakeholders with some of the more stringent services and the surrounding concept of their use • Captured and defined missing services • Further defined services to ensure a more complete understanding of their operational use • Categorised services into similar safety/operation groups • Assessed the safety and security requirements associated with each group • Assessed the associated performance requirements impact • Used to support the technology assessment
Evaluation Scenarios • Provide a family of generic operational environments based on an extrapolation of the Phase 2 COCR requirements so each expresses the same requirement in different ways • Reinterpretation of COCR requirements expressed in a variety of ways that can be better used during the technology assessment work • This set of scenarios were used in the technology assessment so as to compare results and identify the technologies in an equitable way
Airport surface • The airport Test Volumes have been defined as: • TV1.1 Airport Zone: 10NM diameter Cylinder including Runway and Tower operations but excludes surface. • TV1.2 Airport Surface: 5NM diameter circle including Clearance/Ramp and Ground components. 5 NM was representative of a large European airport
Core Europe • Concept of Core Regional Test Volumes was introduced: • TV4.1-4.4 have been redefined as Core Regional TVs • They are representative of a global Large Area Volume (LAV) such as ECAC or NAS. • Designed to formulate a generic large area rather than a specific case • Characterise a large terrestrial coverage area, or large terrestrial area inclusive of surrounding oceanic airspace regions • Core Regional Test Volumes provide a scenario for either TMA or ENR airspace. • Core Regional Test Volume designed for assessment of space based technologies.
Aircraft Traffic • Traffic Growth Predicting tool used • Busy hour in busy day in 2025 (Phase 2 – COCR) • Peak aircraft count chosen for each Test Volume • Aircraft traffic assumed to be uniformly distributed within the test volume. Ref. Volume Type PIAC TV1.1 Airport Zone – 10NM diameter 26 TV1.2 Airport Surface – 5NM diameter 264 TV2.1 TMA Small – 49 x 49 NM 44 TV2.2 TMA Large – 75 x 75 NM 53 TV3.1 ENR Small – 55 x 55 NM 45 TV3.2 ENR Medium – 100 x 100 NM 62 TV3.3 ENR Large – 200 x 200 NM 204 TV3.4 ENR Super Large 400 x 400 NM 522 1733 TV4.1 Core Regional FL050 – FL245 [TMA] TV4.2 Core Regional FL245 – FL450 [ENR] 2908 1753 TV4.3 Core Reg + Oceanic FL050 – FL245 [TMA] TV4.4 Core Reg + Oceanic FL245 – FL450 [ENR] 3415
Conclusions • The COCR has been the basis for evaluating technologies • Evaluation Scenarios have been used to assess technologies against the requirements in an equitable way • The choice of the appropriate scenario was dependent on the technology