Fragmentation Data Message Alexandru Mancas CCSDS Fall Meetings 2019, Darmstadt, Germany ESA UNCLASSIFIED - For Official Use
Agenda 1. Short overview of the concept paper 2. Developments since the concept paper was distributed 3. How it ties up with the Navigation Hybrid Message concept 4. Way forward ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 2
Fragmentation Data Message INTRODUCTION ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 3
Introduction o original concept developed together with RDM in mid-2015 o concept paper drafted at the same time as the RDM concept paper (found on my computer thanks to Spotlight; not sure if shared with WG) o contents were based on the output of the prototype ESA SST Fragmentation Analysis System (FAS) o re-drafted in mid-/late-2019 and distributed to the working group o since 2015: o different perspective on fragmentation events from ESA Space Debris Office activities o NDM progress, including RDM, OCM, and OCM (in development) o RDM development and contents led to some doubts about the original FDM content o thoughts developed on how the FDM ties in with the hybrid message concept ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 4
Fragmentation Data Message CONCEPT PAPER ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 5
Basic ideas o written mainly for a stand-alone message, same as the CDM and RDM o KVN and XML versions, KVN mock example in the paper o did not want to tie in to a hybrid message in the proposal, as that idea was not proposed in a concept paper yet o possibility left in the proposal for other possible approaches to take with the message, such as creating an XML-only message re-using structures from existing XML NDMs o justification for the need for such a message (large number of fragments in orbit generated in the last two decades) ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 6
��� ������������ � ���������� �� ��� ������ (a) Absolute number of resulting fragments per event cause. Absolute number of fragments generated per event cause Large number of deliberate fragments in the 2005-2010 bin ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 7 (b) Relative number of resulting fragments per event cause. Figure 5.4: Historical trend of numbers of fragments produced by fragmentation events. Page 54/77 ESA’s Annual Space Environment Report Issue Date 24 April 2019 Ref GEN-DB-LOG-00271-OPS-SD
Proposed content o contents proposed for a stand-alone message o header, metadata, and data sections o metadata: fragmentation id, event status (detected/simulated), event type, epoch, number of fragment clouds detected + optional keywords o data section: 2 blocks, one per fragmentation cloud o KVN with general information: progenitor and physical properties, granular control over number of fragments in the cloud (catalogued, in-orbit, tracked, etc), distribution in orbital elements, epoch for the above’ o (optional) data lines with information about each fragment in the cloud: IDs, epoch of detection and assignment to the cloud, etc ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 8
Fragmentation Data Message RECENT DEVELOPMENTS ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 9
Recent developments on only on one since th the pa pape per wa was distr tribu bute ted: : som ome inte terest t in pr prototy ototypi ping expr pressed by by 1. ESA (obviously) generate+process FDMs 2. DLR/GSOC read/process FDMs 3. AGI (tentative), hoping for generate+process FDMs ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 10
Fragmentation Data Message HYBRID MESSAGE CONNECTION ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 11
Hybrid message o the concept paper follows the same approach with the CDM/RDM: some overlap with existing messages (OPM mainly) and enough information to get some analysis done o especially for fragmentation events, more information could be exchanged, such as: o state vectors or ephemerides + estimated physical properties for each fragment (to re- use OCM/OEM/OPM stuff?) o covariance information for each fragment o tracking data for each fragment o given the above, would it make sense to me to think of the FDM (not as proposed in the concept paper) but as a first instantiation of the hybrid message? ie we could start defining blocks (orbit, physical properties, tracking, etc), and the FDM ‘standard’ would just specify how to assemble them ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 12
Fragmentation Data Message WAY FORWARD ESA UNCLASSIFIED - For Official Use ESA | 01/01/2016 | Slide 13
Recommend
More recommend
