Use Cases

The users and use cases of SIDLOC fall into two main high-level categories:

Spacecraft Operators

For the spacecraft operator, the main use cases for SIDLOC are spacecraft identification during Launch and Early Orbit Phase, and monitoring of the evolution of the spacecraft’s orbit during the whole duration of the mission. Although radar-based localisation is usually sufficient to determine the spacecraft’s orbit within a couple of km, positive identification is usually based on opportunistic RF transmissions which contain some form of information for deducing the ID. A common approach for identifying a spacecraft is to either directly identify by its transmission or via elimination of other object transmissions on the same launch. In addition to that, radars have limited ability to register small spacecraft (e.g. pico-satellite) or large deployments during LEOP. From the operator’s point of view, successful identification is a hard requirement for localisation and subsequent orbit determination.

Space Situational Awareness Operations

For Space Situational Awareness related operations, the targeted identification and localisation of a known spacecraft as described above, are not enough. An additional use case for SSA operations is the ability for any spacecraft, without prior knowledge of ever being launched, to be identified and localised. This group includes the Regulators and Space Traffic Management players and their use cases.

List of Use Cases

ID UC-1 - Satellite operator identifies their satellite during LEOP
Actor Satellite operator
Scenario
  1. Satellite is deployed.
  2. Satellite operator wants to identifies their satellite among other spacecraft.
  3. Satellite starts beaconing.
  4. Satellite operator acquires early orbital data.
Scope Beacon hardware
ID UC-3 - Launch provider tracks individual launch hardware
Actor Launch provider
Scenario
  1. Launch provider launches launch vehicle.
  2. Launch vehicle components are separated during launch operation.
  3. Launch provider wants to track launch hardware.
  4. A system can track individual components.
  5. This system can return tracking information to launch provider.
Scope Beacon hardware
ID UC-4 - Insurer determines insurance policy for spacecraft
Actor Insurer
Scenario
  1. Insurer wants to create insurance policy for spacecraft.
  2. The policy is affected by the presence of identification and tracking capabilities.
  3. Insurer inquires whether such capabilities are present on spacecraft.
  4. Insurer calculates risk based on the capabilities and defines policy.
Scope Beacon hardware
ID UC-5 - Insurer determines validity of insurance claim
Actor Insurer
Scenario
  1. Insurer receives an insurance claim.
  2. Insurer want to verify validity of claim.
  3. Insurer acquires spacecraft health and localization data.
  4. Insurer verifies validity of insurance claim based on the data.
Scope Beacon hardware
ID UC-6 - Launch provider verifies spacecraft separation
Actor Launch provider
Scenario
  1. Launch provider deploys spacecrafts.
  2. Spacecrafts start beaconing.
  3. Early orbital data are derived from beacon.
  4. Launch provider verifies separation from early orbit data.
Scope Beacon hardware
ID UC-7 - Regulatory authority identifies the source of a transmission
Actor Regulatory authority
Scenario
  1. Regulatory authority monitors spectrum.
  2. Regulatory authority wants to identify the source of a transmission.
  3. Spacecraft transmissions and identification data are associated.
  4. Regulatory authority accesses the data and identifies the source of the transmission.
Scope Beacon hardware
ID UC-8 - Satellite operator monitors health of spacecraft
Actor Satellite operator
Scenario
  1. Satellite operator wants to monitor spacecraft health.
  2. An unexpected loss of communication with the spacecraft takes place or the spacecraft reaches EOL.
  3. Beacon hardware is still operational.
  4. Satellite operator receives health data via beacon hardware.
Scope Beacon hardware, Communications protocol
ID UC-10 - SSA provider uniquely identifies spacecrafts during LEOP
Actor SSA provider
Scenario
  1. A spacecraft deployment commences.
  2. SSA provider wants to uniquely identify deployed spacecrafts during LEOP.
  3. Spacecraft starts beaconing.
  4. SSA provider uses beacon identification and localization data to uniquely identify spacecraft.
Scope Beacon hardware
ID UC-12 - Groundstation provider tracks spacecraft
Actor Groundstation provider
Scenario
  1. Groundstation provider wants to track spacecraft orbit and frequency.
  2. Spacecraft beacons are received.
  3. Spacecraft is identified from identification data transmitted in the beacons.
  4. Localization data can be received from the beacons or derived from them.
  5. Groundstation tracking system points the antenna to spacecraft using localization data.
  6. Groundstation receiver applies doppler frequency correction based on localization data.
Scope Beacon hardware, Communications protocol
ID UC-13 - SSA provider tracks EOL spacecrafts
Actor SSA provider
Scenario
  1. SSA provider wants to track EOL spacecrafts.
  2. Beacon hardware continues to operate on spacecrafts past EOL.
  3. SSA provider receives and identifies spacecrafts from beacon.
  4. SSA provider can pull localization data or derive orbit from beacon.
Scope Beacon hardware
ID UC-14 - Payload owner correlates spatial, temporal and scientific data
Actor Payload owner
Scenario
  1. Payload owner wants to correlate science, time and location data.
  2. Scientific data and beacons are received.
  3. Payload owner correlates science data with spatial and temporal data.
Scope Beacon hardware, Communications protocol