SESAR2020 RPAS C2 Activity #2 6.11.2014
A#2 C2 Contents Initial Work split Participants RPAS C2 Objectives Work plan Meetings Deliverables A#2 DOW view RPS Next steps RPA <-> RPS C2 Transaction RPIL ATC <-> RPIL RPA ATC <-> RPA ATC A/C ATC Transaction Terminology note: C2 datalink (C3 stands for application level)- as defined in ICAO RPAS manual 2
Initial work split i1 i2 i3 i4 i5 i6 i7 i8 Petr Kanovsky-Honeywell PK Francesco Fusco-CIRA FF Rita Rinaldo-ESA RR Patrick de Prevaux - ASD PP Dominique Colin-ECTL DC Laurence Duquerroy -ESA LD Aurora Sanchez -ENAIRE AS Juan Ponce-Cassidian JP Francois Rivet-ASD FR Erwan Le-Ho-TASF EL i1 C2 requirements RCP i2 RCP to RPAS segmentation/categorization i3 GNSS services impact on C2 i4 SDR role i5 C2 for formation flight i6 Safety & Security i7 - Modeling, prototyping and demonstration i8 - Spectrum issues, including RF interference This allocation was done around the 1 st meeting, all items are covered, even there are more contributors to one item Items taken from the RPAS Activities_Project work plan v1.0 document 3
C2 Objectives, dependences and deliverables Assumed is tight cooperation with other activities (A#1-6) and RPAS actors (EUROCAE, JARUS, ) in order to not start again from beginning, but do the work effectively. Legend: Objective Deliverable Dependency A#1 D&A A#3 Airspc O1: Environment definition Operational Services and Environment Description (OSED) Note: Deliverable is not complete standard (e.g. SPR), but significant and leading contribution to the EUROCAE work. A#5 HF A#4 Conting. O3: Safety impact O2: RCP O6: Simulation & Testing Models and prototypes O4: Feasibility &Spectrum & RFI O5: Avionics & Architecture Spectrum requirements, including spectrum management issues. Interoperability requirements (INTEROP) Safety and Performance Requirements (SPR) A#6 Secur. System/performance specifications (SPS) 4
RPAS C2 objectives O1: RPAS Environment & operations definition common work across all Activities- includes airspaces, D&A, GNSS, formation flight, formulation of stepwise approach O2: Operational RCP figures identification parameters (latency ) for defined environment & operations O3: Safety RCP figures formulation safety parameters O4: Existing Technology status analyses-feasibility to fulfill RCP figures by state-of-the-art systems including RF Interferences and Business cases O5: Requirements for Avionics architectures and avionics&architectures proposal O6: Simulation and demonstration of all above defined work
A2/C2 work plan A2/C2 meeting (T0)- 25.9.2014 start of items identifications and definitioninitial allocation Meeting (T1=T0+1week) initial contribution Meeting (T2=13.10.2014) contribution discussion format still TBC Internal Milestone #1 date (T3=16.10.2014) Initial release for external comments (before that email exchange of drafts)-in proper format External Milestone #2 date (T4=23.10.2014) handover to ML 2 nd Working Session and A#2 presentation T5 = 27.11.2014 Meeting T6=5.11.2014 comments integration RPAS Definition Phase Workshop 02 T7=6.11.2014 T1 T2 T3 6 T0 T5 T6 T7 T4
Meetings attendance log Petr Francesc o Rita Patrick Dominique Laurence Aurora Juan Francois -Yoann 25.9. 2.10. 13.10. 5.11. Erwan Derek 7
Assumed standardization contributions & dependences 8 Standard Relation Assumed release Date OSED Input 2015 SPR & INTEROP RPAS C2 MASPS stage One RPAS C2 MASPS stage Two RPAS C2 RLOS MOPS RPAS C2 BRLOS MOPS SARPS Major contribution Major contribution Major contribution Major contribution Major contribution Partial contribution 2016 2016 2017 2018 2018 2018 Important note: Based on latest realistic, but not yet approved EUROCAE WG73 Terms of references Description Operational Services and Environment Definitions (OSED) shall be available prior the SESAR2020 RPAS activities start The Operational and Safety Performance Requirements (SPR) and Interoperability (INTEROP) analyses will deliver requirements directly relevant to the subjects of Command and Control Minimum Aviation System Performance Standards C2 system oriented - Content definition and initial figures draft version This version shall be final MASPS for official release Minimum Operational Performance Specification C2 equipment oriented, focusing on RLOS operations Minimum Operational Performance Specification C2 equipment oriented, focusing on BRLOS operations C2 related Standards and Recommended Practices (SARPS - ICAO)
A#2 DOW view Description of work Nature and description of work Define the RPAS C2 exchanges at application level (messages type and size, associated traffic model ), integrating especially the level of automation, the flight phase and the area of operation. Evaluate STANAG 4586 suitability for this activity. Reference architecture identification ( components of the C2 chain, external and internal interfaces). Determine RPAS C2 requirements for RLOS and BRLOS starting from JARUS-RPAS C2 link RCP concept (Ed 1.0) and DeSIRE and CERES projects outcomes related to RCP definition and allocation (DeSIRE and CERES Final Report): Refinement of stepwise methodology for allocating RCP figures based on operation types (e.g. airspace class, population density, RPA types). This includes the assessment of the severity level associated to C2 related hazards in cooperation with Activities #1, #3 and #4; Definition of C2 Data link Operational and Safety Performances Requirements, i.e. assignment of RCP figures (availability, continuity, communication transaction time, integrity) per operation types, down to an apportionment to data link systems (RLOS and BRLOS), ensuring both safe operations as well as technical feasibility; Definition of the approach to verify and demonstrate compliancy with the performances requirements in accordance with Activity #5 (e.g. need of unambiguous measurable metrics); Exploring the effect and efficiency on Comms C2 data link of multiple collaborative RPAS flight. Swarming and distributed tasks; Cross check and liaison with GNSS services (related to gap 2.2). and identification of GNSS augmentation services impact on C2 operational and functional requirements during all RPAS flight phases; Strategic vision that addresses potential impacts to C2 link due to increasing demand, rapidly evolving technologies, and new uses; Formulate requirements for RPAS C2 Avionics Definition of needed assurance level (DAL) for C2 system; Security SW development assurance level definition (Activity #6 cooperation), attending to operational scenario; Mapping of all required RPAS radio systems from the points of safety, simultaneous operation and RF parameters in order to analyze SDR approach benefits for RPAS; Safety analysis for point-to-multipoint (aircraft formation and swarm) C2 architecture, e.g. common point of failure if ground C2 data link (RLOS or BLOS) is shared by several RPAs; Identification of parameters for link quality monitoring and identification of corresponding threshold values triggering contingency procedures; C2 Security aspects addressing requirements from Activity #6:: Resilience to attacks to data link systems (e.g. jamming and hijacking by Radio and SW means); Identification of requirements for domains segregation in avionics architecture for CNS functions; Use of multi-lateration for surveillance based on C2 data link signals in RLOS 9
A#2 DOW view Modelling, prototyping and demonstration. All the above should be demonstrated by stepped approach from modelling and simulation to in- flight demonstration of selected cases; Assessment of existing/planned RPAS performances (via analysis and simulation) and their impact on required C2 performance; Proposal of COM avionics architecture that reflects Activity #6 results and fulfils required domains segregation; Test bed simulating/emulating the complete C2 system of systems, i.e. integrating the application layer, the backup ground network, the emulation of radio data links. Such a test bed would make it possible to emulate C2 exchanges and test contingency procedures, handover procedures, multilink procedures etc. Trade-off for C2 data link (multilink) architectures and link requirements for RPAS operations including, but not primarily, formation and swarm flight. Reference designs, adaptable to different aircraft environments (small, medium, large, dominant carrier, no dominant carrier, and other tenant mix), including basic security requirements for all stakeholders; Spectrum issues, including RF interference. Quantification of the extent and magnitude of the interference problems for the purpose of RPAS Command and control ;; Techniques for identifying and resolving interference issues outside reference designs; Band planning issues, including sharing between RLOS and BRLOS SESAR This activity has impact on SESAR through: Communications requirements on aviation Spectrum requirements; RCP Latency definition and requirements; C2 architecture and integration with ATC communications and data link. Operational navigation capabilities depending on the Command and control design and data link performance, in particular for separation and during the landing phase (DA/DH) Surveillance through the use of multi-lateration using C2 datalink in RLOS 10
Common work Next steps Define Operational Improvements As defined in roadmap? =VLL (VLOS, E-VLOS, B-VLOS) + VFR/IFR (RLOS/BRLOS)? = 5 items? Identify and propose list of C2 related enablers TBD- RLOS C2 datalink, BRLOS C2 datalink, RPAS C2 avionics, Analyze required outputs (alignment with EUROCAE WG73) what must be done in order to realize C2 enablers and achieve OI s (MOPS, MASPS ) and formulate Deliverables Address dependences with other activities & Identify required inputs Formulate waves and solutions in order to follow Detailed Description of Work template (=WBS leading to deliverables) Running SESAR RPAS projects outputs incorporation. Data available? 11
Backup - Other RPAS activities - Activity 1 IFR/VFR & BVLOS D&A Activity 2 IFR/VFR & BVLOS Comms C2 Data Link Activity 3 IFR/VFR & BVLOS Airspace Access and Airport Operations Activity 4 IFR/VFR & (B)VLOS - Contingency Activity 5 IFR/VFR & BVLOS Human Factors Activity 6 - Security Activity 7 Demonstrations of best practices 12
13 Thanks for your attention