Engineering Papers⌕ Search

Engineering topics

Shadi Zogheib

Publications and source records attributed to Shadi Zogheib.

Cognitive Engine One: A Cross-Layer Framework for Autonomy in Multi-Provider Space Communications Environments

Spacecraft information needs, along with the communications environments in which data transfers occur, are becoming increasingly dynamic. Earth orbit is served by dozens of ground station and relay satellite providers – each with unique protocols and service capabilities. In this context, we present a system to automate end-to-end space communications across the protocol stack for each of several providers. The proposed system schedules contacts with providers, configures point-to-point RF links, and ensures data is transferred to its destination. Data monitoring and rescheduling provide an automated failover capability in the event of unsuccessful contacts. We verify system performance in a high-fidelity emulation testbed. Results from several scenarios demonstrate favorable system performance across a variety of mission use cases.

space communications↗

Automated End-to-End Spacecraft Connectivity Across Diverse Links

An increasing variety of communications services are available to space missions. Yet varying standards between providers hinder adoption due to the complexity of managing many configurations. We present a software framework to automatically establish end-to-end communications during contacts with a provider by configuring spacecraft protocols at the physical, link, and network layers. Underlying protocols and routes are abstracted, allowing the user to simply send data to a destination with the framework ensuring its delivery. We evaluate a full implementation of the framework in laboratory experiments conducted on an emulated communications testbed. These tests demonstrate data delivery across three different services with rapid (<20s) reconfiguration as the spacecraft transitions between providers.

satellite communication↗

Service Provider Agnostic Adaptive Coding and Modulation System Design

Commercial service providers (CSPs) are increasingly used to provide communications services to near-Earth science and exploration missions. CSPs commonly utilize modems that are designed to implement adaptive coding and modulation (ACM) in unique ways with modems from the same vendor. However, some missions cannot fly a matching vendor modem, either because the vendor only designs modems for terrestrial use, or the mission needs to fly a software defined radio. We present an ACM system design that allows missions to implement ACM on DVB-S2 compliant CSP links without needing to fly a modem from the same vendor the CSP uses. We implement and test our design in an emulated communications testbed. These tests demonstrate that our ACM system design can successfully adapt to link quality changes up to 6.12 dB/second.

Adaptive coding and modulation↗

Service Provider Agnostic Adaptive Coding and Modulation System Design

Commercial service providers (CSPs) are increasingly used to provide communications services to near-Earth science and exploration missions. CSPs commonly utilize modems that are designed to implement adaptive coding and modulation (ACM) in unique ways with modems from the same vendor. However, some missions cannot fly a matching vendor modem, either because the vendor only designs modems for terrestrial use, or the mission needs to fly a software defined radio. We present an ACM system design that allows missions to implement ACM on DVB-S2 compliant CSP links without needing to fly a modem from the same vendor the CSP uses. We implement and test our design in an emulated communications testbed. These tests demonstrate that our ACM system design can successfully adapt to link quality changes up to 6.12 dB/second.

Adaptive coding and modulation↗

SERENE: Saturn Enceladus Return Explorer with Nuclear Electric Propulsion

A ‘quick’ Enceladus sample return mission concept was developed based on the scientist recommendations at the recent ‘Accelerating Space Science with Nuclear Technology Workshop’. The Nuclear Electric Propulsion spacecraft assumed a follow-on 40 kWe nuclear reactor using the demonstrated 40 kWe Fission Surface Power system, expected in the early 2030s. The NEP vehicle also utilized a set of NEXT-C ion thrusters as well as planned Artemis commercial launchers. By launching the 40 kW NEP vehicle on a Starship and adding the propellants of 15 tankers, the 27t probe could be sent on a direct trajectory to Saturn (no Earth or Jupiter flybys) where NEP was used for Saturn capture, spiral down, spiral up and return to the Earth. A small lander obtained the surface Enceladus sample. Using the 40 kW NEP provided a round-trip time of only 16.5 years. A second option was more attractive from a science perspective whereby the NEP vehicle would deliver a large, 6t chemical lander to low Enceladus orbit where it would grab and return a sample to Earth (similar to the recent Orbilander design but in reverse). After deploying the lander, the NEP vehicle would stay in Saturn space performing a moon tour by orbiting four more moons and mapping the large moon of Titan. This option took slightly longer (18.5 yrs) due to the chemical return leg limitations. Both options demonstrated the agility, payload capability, and sample return goals the workshop recommended. An all-chemical option with two stages was roughly analyzed but took 21.5 yrs and required a Jupiter gravity assist.

Nuclear Electric Propulsion↗