flight dynamics topics - space data€¦ · 16/03/2015 · – transitioned from rackspace to...

11Approved for public release

FLIGHT DYNAMICS TOPICSErika Rossetto – Star One


FD Working Group Erika Rossetto (Star One)

Dean Hope (Inmarsat)

Joe Chan (Intelsat)

Pascal Wauthier (SES)

David Zamora (Eutelsat)

Brian Swinburne (Astrium)

Lorenzo Arona (Avanti)


Activities

Meeting last June:– Possible improvements for CA;– Status of SDA’s Third-Party Space Data Search;– Security Versus Usability: Concepts and Alternatives;– Improving communication between members;

Along 2014:– Meetings with Airbus, Boeing, ISODEX, GMV,

ComSpoc, ISON.


On orbit Summary

334 launches in 2014 X 75 in 2009

In 2009, about 13000 objectscataloged, currently more than17000!

SDA numbersCA runs executed: 3452Conjunctions detected: 4166725


FD aspects on SDA

Space Data Association– Cooperated with other satellite owners/operators orbit

ephemeris including maneuver effects– TLE to supplement drifters and non-cooperated satellites– Conjunction alerts currently based on miss-distances only– Monitoring to 7 day time span


FD aspects on SDA OD EvaluationInitially, then at least once a year


Ephemeris-TLE comparison

FD aspects on SDA

Discrepancy in ephemeris data

Time of last upload


FD aspects on SDA CDM analysis

Using operator’s ephemeris to provide a more realisticconjunction analysis


FD aspects on SDA SDC plug-in allows the operators

analyze CDM by themselves


FD aspects on SDA


Summary

FD working group has worked to help SDA provides a better service;

The FD aspects has been improved since last meeting;

SDA adds a valuable contribution for safety of satellite community.


STATUS OF SDC AND THE SDC PLUGINDAN OLTROGGE

SDA Users Meeting: SDA General Forum


SDA Objectives From 2014

SDA– Grow Membership– Develop Government and Industry Relationships– Develop Space Insurance Relationships– Secure Access to Additional Data Sources

SDC– Rehost the SDC to Amazon Cloud– Reduce Operating Costs and Improve Service– Implement Data Sharing for RFI Mitigation– Carrier ID Database Prototype for FIFA World Cup


SDA Objectives From Last Year …

SDAGrow MembershipDevelop Government and Industry RelationshipsDevelop Space Insurance RelationshipsSecure Access to Additional Data Sources

SDCRehost the SDC to Amazon CloudReduce Operating Costs and Improve Service Implement Data Sharing for RFI MitigationCarrier ID Database Prototype for FIFA World Cup


Space Data Center (SDC) The SDC is the processing system of the SDA

SDC – Three Key Mission Areas:– Collision avoidance monitoring (Conjunction Assessment)/

Maneuver Planning Validation / Flight Safety– Radio Frequency Interference mitigation / Geolocation support– Contact information (operations center) for SDA Members

SDC reliable and secure operation:– High level data security and encryption– Geographically separated redundancy– SDC services redundancy


SDC Demo: Home Page…


Year-in-Review: SDC Achievements Developed, tested & deployed Amazon SDC in 8 months

– Transitioned from Rackspace to Amazon Web Services (AWS)– Transitioned SDC DB from MS SQL Server to Oracle (AWS RDS)– Conducted shadow mode operations

New SDC self-signed certs for improved ops & reduced cost New Sophos Unified Threat Mgr (UTM) for all SDC transactions Upgraded SDC Plugin for new Conjunction Data Message (CDM) Drafted Orbit Hybrid Message under ISO/CCSDS auspices Carrier ID Database and RFI Precomputed Sol’n Set prototypes On-going SDC operations:

– Four new operators w/ new ephemeris converters etc.– CDM & TLE comparisons, ephem. quality monitoring, OD verifications– JSpOC dialogue for CDM & TLE comparisons, cross-tags & issues– Coordinating SSA Data Sharing w/USSTRATCOM & JSpOC– Space debris mitigation & research (Iridium 47,91 & DMSP, spatial dens)


SDC Rehost to Amazon December 2013

– Amazon configuration

January/February 2014 – Conversion begins– Login/Ephemeris conversion

April/May 2014 – CA conversion

June 2014 – SDC AWS testing and performance tuning

July 2014 – SDC AWS Shadow Operations– New self-signed security certificate implementation

August 2014 – SDC AWS live operations


SDC Transition to Amazon Cloud

Substantial SDC hosting cost reduction Multi-region (continent), dual-AZ topology

– Amazon AWS regions are separate geographic areas– Each region has multiple, isolated locations known as

Availability Zones, connected by low-latency links.


AWS High Availability

Window Application Servers– All SDC Windows services redundant across multiple AZs

Ephemeris Processing Conjunction Analysis Data Retrieval Message Processing

– All AZ instances process queued jobs on FIFO basis.– AWS CloudWatch monitors Windows service health.– Any Windows service outage covered by other AZs.– Can perform system maintenance w/o SDC outage !

Amazon RDS automatically replicates SDC DB and recovers from DB failure scenarios for Multi-AZ deployments w/o administrative intervention


SDC Security on AWS

SDC system security is a SDA priority The SDC incorporates by design layered

security and defense-in-depth strategies (monitoring, alerting, disaster recovery and forensic analysis) to help ensure a trusted and secure environment– Greatly reduces susceptibility to FREAK-style

attacks


SDC Plugin

SDC Plugin provides easy access to user-friendly, tailored analysis of SDA member data– Augments SDC rich repository of SOAP and REST web services

for automated machine-to-machine interface– Allows SDC users to obtain any/all SDC data they are

authorized to access SDC ephemerides and maneuvers populated by operators SDC RF parameters and RFI alerts to be populated as well. Automatically ingests JSpOC CDMs and performs 9-way

comparisons of conjunctions and two 3-way positional compares

Upgraded SDC Plugin for JSpOC CDMs July 2014– Free to SDA members; requires business-level STK-Pro license


RFI MITIGATION FUNCTIONS IN THE SDC

STEVE SMITH and DAN OLTROGGE

SDA Users Meeting, 16 March 2015


SDC/RFI – Introduction RFI background

– RF interference is the major operational problem affecting customer services on geostationary satellites

– ~85-90% of customer issues are due to RFI– RFI only affects a small amount of capacity but has a cost and

service impact if not quickly resolved– Investigating RFI is time consuming – we are always seeking

methods and processes to improve response

Geolocation – key mitigation technique– One of the main techniques used to

identify interfering signals– Requires precise satellite ephemeris data

for ‘affected’ and adjacent satellites– Needs RF payload data for ‘affected’

and adjacent satellites Referencesignal

MySatellite

Monitoringstation(s)

Adjacentsatellite

Thesignalwewanttolocate


SDC/RFI – Geolocation Support How can SDC help with geolocation?

– Investigation often needs accurate RF data on other satellites– SDC already contains the precise ephemeris data– Need to extend data sharing to include RF payload data– SDA already has a means of securely holding and exchanging

data with the users– It already has a legal framework to protect user’s data

SDC pre-computed geolocation solution sets– Analyze an RFI event submitted by an SDC user– Use knowledge of payload data for all satellites, to provide a

ranked order of geolocation scenarios, to input into the user’s geolocation system


Normalized RF Data & Approach

Gathered relevant RF input data– SDA/AGI developed standardized Excel templates– Eutelsat, Intelsat, SES submitted payload RF data

for handful of satellites

AGI developed analytical software EMISSION for geolocation pre-computation


SDC/RFI – Carrier ID Database

Prototype hosted by SDC for World Cup 2014 Operational database required in preparation for

SNG CID users in 2016 (FCC ruling)

Due Date CID Objective1 January 2015 All new DVB modulators purchased for video uplinking shall contain

DVB-CID

1 January 2015 All uplinkers of SCPC and MCPC video and data, fixed and mobile, shall include DVB-CID as a requirement in all RFPs and POs for new modulators

1 January 2015 Satellite Operators shall start the transition to use CID, that meets the DVB-CID (or at least the CID-NIT) standards

31 December 2017 All uplinkers shall use DVB-CID on their SCPC and MCPC video and data transmissions, and as of this date CID-NIT shall be completely phased out and no longer used

Due Date CID Objective1 June 2016 Transmission of DVB-CID shall be required on all OU/SNG transmissions,

which are under FCC jurisdiction


SDC/RFI – Planned Functions

Function Target

Pre‐Computed Geolocation Solution Sets‐ Analyze RFI event and recommend geolocation solution sets‐ Download selected dataset into user's geolocation system

Prototype: Q2 2015Final: Mid‐2016

Carrier ID Database‐ Centralized database for all operators to store CID codes‐ Only the unique code and name of operator stored

Early‐2016

RFI Fly‐By Analysis‐ Predict RFI for LEOP and drifting satellites Mid‐2016

RFI Contacts and Phonebook‐ Reliable contacts for Operators' RFI teams Early‐2016

RFI Alerts‐ Create and distribute alerts to selected members‐ Smart distribution dependent upon RFI event

Early‐2016

RFI Database‐ Store events, case studies, white papers, etc.‐ Assign tags, keywords for searching

Late‐2016


EMI Solution Set Identification of Optimal Neighbors (EMISSION) EMI is chief concern for SatComm operators RFI mitigation initiatives Inter-operator satellite operator Carrier ID DatabaseEquipment install training/cert programsGeolocation of interfering signals

Constructing a geolocation “Solution Set” w/normalized inputs can take days to weeks

“EMISSION” Tool constructs in minutes– Authoritative ephemerides + maneuvers + RF data +

antenna patterns + aggregate reference emitters + geolocation sites + STK & ODTK under the hood


Neighbor S/C #2

Ref EmittersCalibrator_01Calibrator_02

⁞

S/C CharsEphemerisCovarianceManeuvers

⁞

Transponder ConnectivityConn_01: U/L Channels, D/L mapping, LOs, Antenna Patterns

⁞

GeolocSitesGeoloc_01Geoloc_02

⁞

Neighbor S/C #1


⁞


⁞


⁞


⁞

EMISSION Tool

SDA is ideal trusted framework for behind-the-scenes RF analytics such as “EMISSION”

Large quantity of proprietary RF data req’d:

Interfered S/C


⁞


⁞


⁞


⁞

⁞

EM

ISS

ION

Rank-ordered solution sets by Ix region & location

Ran

kP

redi

cted

Per

fSco

reIn

terfe

red

S/C

Nei

ghbo

r S/C

Ref

Em

itter

#1

Ref

Em

itter

#2

⁞G

eolo

cS

ite


- - - - SDA Trusted Framework - - - SDA Trusted Framework - - - SDA Trusted Framework - - - - -

----

--SD

A Tr

uste

d Fr

amew

ork

----

--SD

A Tr

uste

d Fr

amew

ork

----

-

- - - - - - - - - SDA Trusted Framework - - - - - - - SDA Trusted Framework - - - - - - - SDA Trusted Framework - - - - - - - ---SD

A Tr

uste

d Fr

amew

ork

--

----

----

--SD

C T

rust

ed

Fram

ewor

k --

- - - - - - - - - - - - - - - -

EMISSION Process Flow

Satellite Operator

Neighbor S/C #2RF DataNeighbor S/C #1

RF DataInterf S/CRF Data

⁞

⑤

①

EMISSION

SDC Operator-Proprietary RF DB

②

③ ④

Neighbor S/C #2RF DataNeighbor S/C #1

RF DataInterf S/COrbit & ∆V Data

⁞

SDC Operator-Proprietary Orbit DB

⑦

⑥

Rank-Ordered Geolocation Solution Sets

Operators populate and maintain their authoritative RF data and antenna patterns

RF data and antenna patternsOperator-proprietary SDC orbit ephemeris & maneuver data

Viable candidate solution sets

• STKX/Object Model• STK Comm: C/N, C/No, EbNo etc.• STK for chain access/visibility

• Simulate TDOA/FDOA• Extended Kalman Filter• Estimates geolocation performance Incorporates S/C, ∆TAT,

meas & geoloc errors

Operator specifies Ix S/C Freq, Polarity

Assess geolocation performance


EMISSION/STK Viable Candidates

Referencesignal

MySatellite

Monitoringstation(s)

Adjacentsatellite

Viable Reference Emitter Frequency

Freq

(MH

z)

Inte

rfere

d S

/C

Nei

ghbo

r S/C

Interference Frequency

LO 1

LO 2

LO 3

LO A

LO B

LO C

To be viable neighboring geolocation satellite, need Local Oscillator commonality

EMISSION auto-ingests each S/C’s full RF

parameters and antenna patterns and instantiates

only those channels with

LO commonality


Complete Specificity of S/C RF …


Status and Next Steps

– EMISSION now able to ingest operator RF parameters and instantiate “heavy” STK Comm objects for full RF analysis

– In process of hooking up fully-functional ODTK TDOA/FDOA filter to evaluate geolocation performance at interference site.

– Operators/AGI explore suitability of candidate geolocation solution set viability metrics (C/N vs C/No vs EbNo vs …)

– Operators/AGI conduct operational tech evaluations of prototype– When validated, AGI will develop final EMISSION software

Implement web and windows services to populate required RF params

– Operators to develop methods to routinely load RF data to SDC using new SDC windows services


SDA New Product DevelopmentJohn Mackey

March 16, 2015


Today: SDA Missions Increase safety of flight – functions already operational

– Automatic Conjunction Assessment (CA), using operator’s ephemeris– Reduce false alarms, missed events– Minimize time and resources devoted to CA– Include planned maneuvers (unique capability)

Deal with the growing problem of RFI – ongoing development– RFI Alerts to focused distribution– RFI historical event search: data support– Generation of geolocation data sets from high quality ephemeris– Library of Reference Emitters– Carrier ID database

Reliable contacts for satellite operators – functions operational

Encourage and promote operational best practices

SDA Enhances its Members’ Satellite Operations


SDA – A Trusted Platform

Over the last 5 years, SDA has built a trusted platform for the secure exchange of satellite operational data– Technical infrastructure of the SDC: security, data

access, etc.– Legal structure and agreements that provide

protections and enforcement mechanisms to ensure that data is only used for intended purposes

These are UNIQUE CAPABILITIES What opportunities exist to leverage our

investments to generate new value for our current and future members?


SDA Evolution

No Decisions Taken Yet!– But consensus view of Directors is that the SDA

should evolve into new areas & applications that build on our capabilities

Some of the Ideas & Concepts:– Geolocation As A Service– Interference Event Database– Inter-operator sharing of cyber-threat data– Ground infrastructure database– Occasional Use Capacity Finder– Aggregation of space weather observations – Space Based SSA sensor data consolidation


Next Steps

Continue to collect ideas & concepts Evaluation / Prioritization

– Dialog with members (and potential members)– Identification of enabling technologies– Business case development

How can you help?– Reach out to us with your ideas & thoughts:

[email protected]

Government Activities

March 2015


Government 2014 Accomplishments Signed groundbreaking SSA data sharing

agreement with U.S. Government– USG signed 1st agreement with non-satellite operator

Attended multiple meetings with U.S. Government entities to discuss SSA data sharing, including EMI challenges– JFCC Space Operator talks – Enhance

communications with satellite operators; better collaboration. SDA has participated in all meetings.

– Meetings with senior leaders – promote better collaboration

– FAA/STPI/IDA – space traffic management


Government 2014 Accomplishments, cont. Participated on multiple panels to promote

SDA and data sharing– AMOS– Secure World Foundation/IFRI– SIA DOD Commercial SATCOM Workshop– U.S. – Japan Space Cooperation Workshop


Government 2014Data Sharing Agreement Groundbreaking Agreement

– Allows SDA close collaboration with USG to, e.g. exchange higher quality data than publicly available

Orbital Data Request (ODR) submitted– SDA / USG: Multiple technical discussions on data to

be shared– Objective: Optimal data shared – Combine aspects

of JSpOC catalog plus satellite operator and maneuver data (SDC)

– Exploring best technical means to exchange data between JSpOC and SDC for flight safety


Government 2015

Begin sharing data with JSpOC Continue discussions with U.S.

Government regarding best practices Continue to engage governments

outside of the U.S. in dialog to share relevant data and explore emerging issues such as EMI/RFI mitigation Enlist government and civil agencies

who operate satellites to join the SDA


SDA Current ParticipantsMulti-national, open to all space operators, in all orbital regimesThe Space Data Association (SDA) is a not-for-profit association formed by satellite operators to provide reliable and efficient data-sharing critical to the safety of the space environment and the RF spectrum

*Data Contributors

2014 Debris EventsDr. T.S. Kelso

SDC Operations Manager


Summary of 2014 EventsName International

DesignatorApogee (km) Perigee (km) Detected*/

DecayedCause

Cosmos 1867 1987-060A 797 778 35/0 (6) Unknown

Delta 2 R/B 1999-008D 841 635 7/7 (6) Unknown

Cosmos 2428 2007-029A 855 846 9/8 (17) Unknown

SL-12 Aux Motor 1994-076G 18,893 505 0/0* (15) Propulsion

SL-12 Aux Motor 2008-046H 18,745 900 10/0 (7) Propulsion

Cosmos 862 Debris

1976-105F 1,075 105* 2/2 (3) Aerodynamic

Titan 3CTranstage

1969-013B 37,195 35,904 0/0* (5) Unknown

Iridium 47 [+] 1997-082C 779 776 10/1 (10) Unknown

HaiYang 2A [+] 2011-043A 968 965 3/3 (4) Unknown

SL-12 Aux Motor 2010-007G 18,790 732 0/0* (16) Propulsion

SL-12 Aux Motor 2007-052F 18,792 733 0/0* (70) Propulsion

Iridium 91 [+] 2002-005A 780 776 4/0 (4) Unknown


Notable Events: Iridium 47

First public TLEs: 2014 Sep 26 Event occurred: 2014 Jun 7 @ 0330 UTC Operational satellite

– Reportedly remains operational– Recent optical SOI shows still stable


Notable Events: Iridium 91

First public TLEs: 2014 Dec 3 Event occurred: 2014 Nov 30 @ 1615 UTC Operational satellite

– Reportedly remains operational– Recent optical SOI shows still stable


Iridium 91 event per JSpOC

5 RSOs appear to have emanated from Iridium-91

Relative motion with Iridium-91 shows multiple separation directions


Spatial density of Resident Space Objects

Density quantifies space crowding– Can approximate collision probability

Only tracking 1/35th of objects > 1cm !


Debris-Generating Events Match Spatial Density Three likely Iridium collisions in last 5 years

Iridium 33/Cosmos 2251 10 Feb 2009

Iridium 91/UNKNOWN30 Nov 2014

Iridium 47/UNKNOWN7 Jun 2014


Notable Events: DMSP 5D-2 F13

First public TLEs: 2015 Feb 25 Event occurred: 2015 Feb 3 @ 1723 UTC Partially operational satellite

– Temperature spike in power subsystem followed by loss of attitude control

– Deactivated


Event Trigger

TLEs released via Space Track– Typically not added to their SATCAT for days/weeks– Only identify International Designator (launch)– No event time or cause provided

Data posted to CelesTrak within 8 hours Perform initial analysis and Tweet results

(@TSKelso)


Post-Event Analysis

Obtain TLEs for all objects Check debris for nodal drift & alignment

with pre-existing objects Refine event time by plotting range to

parent* Generate relative velocity VDF

– Provides insight into type of event


IRG Plans and the SDA…> VSAT Interference

– Root Causes, Tools– Action Plan

> BIG Data (SDA?)

– Collecting & Combining Data – Monitoring effectiveness of initiatives - meeting Targets– Use of “Big Data” to look for RFI types, prediction and

solutions?

> Carrier ID– …going Global? The Uplinker & Broadcaster!

> Training (EUI)– Getting the Best and how to Promote– more flexible Training solutions to meet Client Demands


> Those That Care About Prevent RFI– Carrier ID– Conflict Prevention Systems

> Those That Don’t Care About RFI– Financial – Will Cost Money To Prevent– Business – Does Not Affect MY Network

> Those That Want To Disrupt Others– Cancellation/Filtering Technologies– Un-refutable Evidence For ITU Support

March 17, 201558

3 Types of Satellite User

Satellite Users…


Technology Summary…Satellite…• Isolation of Coverage:

Cellular/Multi Beam Infrastructure - e.g. Inmarsat/Ka-Band SystemsTransmit uplink Spot Beams

• Backup Services slots, Satellite Transponders, Shared Coverage• Flexibility Frequency/Switching/Processing and cross-strapped Transponders• Active Arrays: Antenna Beam Shaping & Steerable Beams• On-Board Geolocation

Ground…• Better/Accurate/Available/Shared Ephemeris Data (SDA)• Use of “Big Data” to look for RFI types, prediction and solutions?• Geolocation –Standardised Process and Reporting• Predictive Methods, using the Politics/Events to govern the most likely targeted content and

put a “watch” on those services• Coordination between International Monitoring Stations, Satellite Operator and Commercial

Geolocation operations• Suppression (more to come on this ready for Geneva & Communic Asia); smart

receivers/filtering; • Better Service/Frequency Planning Strategies.

…aim for better, more accurate & reliable Evidence!


VSAT - the Stats…39% of All incidents are caused by VSAT!WE cannot retrofit installed VSAT terminals!A well designed system should always be able to stop a terminal faster than a person can. VSAT systems can be designed to prevent 99% of interference events:

Type Approved Terminals installed by well Trained People! Carrier Locking (do not transmit when not allowed)

Terminal Power Verification (when not within nominal conditions cease transmission automatically or trigger alarm)

Debug Mode

VSAT install base remains an issue if… not powered down!


Putting in to Perspective & “BIG Data”…


THANK YOU!

Contact…

IRG: Executive Director: Martin Coleman Email: [email protected]

flight dynamics topics - space data€¦ · 16/03/2015 · – transitioned from rackspace to...

Documents