| Deliverable | Requirement |
|---|---|
| Uplink/Downlink needs | Define the maximum data rate and latency requirements for both uplink (command) and downlink (payload/telemetry) data. |
| Defining which ground station will receive data | Define the Ground Station Network (GSN) and specific contact schedules or handoff criteria for reliable data downlink. |
| Defining what will be downlinked | Specify the complete Data Product List, including priority levels for payload data, telemetry, and health packets. |
| On board processing | The onboard computer shall be capable of processing payload data according to the defined algorithm (e.g., compression, feature extraction). |
| Toss out unreasonable data before it's processed / basic filtering on data | Implement a Data Quality Filter (DQF) to identify and discard or flag out-of-range, non-physical, or corrupted sensor readings prior to storage or transmission. |
| data informs other parts of satellite (controls) | Define the cross-subsystem data interface for using sensor/telemetry data (e.g., temperature) to trigger or inform actions in other systems (e.g., activating cooling/spinning). |
| Appropriate Sensor Suite / Data must be correctly relayed from sensors | Data acquisition system shall implement measures (e.g., Cyclic Redundancy Check CRC) to ensure the integrity and correctness of data relayed from the sensors to the onboard processor. |
| Encryption method / data must be encrypted | All downlink data (payload and critical telemetry) shall be secured using a defined encryption standard (e.g., AES-256) with approved key management protocols. |
| Anti-spoofing/general security measures | The Command & Data Handling (C&DH) system shall implement authentication protocols (e.g., authenticated header) to verify the source of all uplink commands (anti-spoofing). |
| Send out NaN type data when compromise is detected | Upon detection of a security breach or data integrity failure, the system shall autonomously transition to a defined secure mode and flag all outgoing data packets with a security alert status code (e.g., an error flag or 'NaN' equivalent). |
| Shall send at least one health packet per orbit / Sends health packets after every orbit | The data management system shall generate and downlink a System Health Packet (SHP) containing critical subsystem telemetry at least once per orbit. |
| Relay data collection mode if it changed | The SHP shall include the current Payload Operational Mode (e.g., Priority Collection, Low-Power Standby, Baseline Scan). |
| data storage? | Define the minimum onboard data storage capacity (e.g., $X$ GB) and the maximum data retention time before automated deletion. |
Overview
Content Tools
Activity