# Toward Integrated Satellite Operations and Network Management: A Review and Novel Framework
## 4 Architectures
### Integrated Operations  
Figure 4 presents an example of a sporadic connectivity constellation featuring a sparse LEO constellation extending the coverage of delay-tolerant IoT application. In this figure, the IoT device is connected to the IoT server using SaF mechanisms and regenerative payloads on the satellites [29]. In the diagram, the arrows indicate service data flow except for the feeder link (where both operational and service data are transmitted) and the connection between GS and ground control (only operational data). Figure 5 presents the control architecture design for sporadic connectivity cases like the example. As can be observed, the system is controlled using only SatOps, namely, platform and ground control commands. The CMS takes as inputs the operational criteria from both MNO and SNO. That information generates control commands for the satellites and ground elements using the same interfaces as traditional SatOps. However, the CMS will try to align these SatOps as best as possible these SatOps with the NetOps criteria and intent rules from the network manager. As for the satellite control, the platform commands are used to change the OM of the satellite. The platform OM is a predefined configuration of all the platform subsystems, including the payload. In this case, the payload subsystem control involves commanding and configuring the RAN, CN, and SaF proxies, enabling discontinuous communication. Regarding ground control, the CMS schedules GS passes and ground SaF proxies to coordinate the transmissions with those scheduled onboard the satellites. The CMS receives feedback from satellite telemetry and ground operations control to dynamically adapt the commands and react to system uncertainties. A use case of persistent connectivity is also presented using the integrated control architecture with the CMS. An example scenario is shown in Figure 6, featuring a multilayered constellation providing direct-to-handset 5G connectivity. The constellation is composed of a dense LEO constellation and a MEO or GEO constellation of relay satellites. All satellites use regenerative payload since the gNB is on the ground. The operational and service data are separated into different planes in this scenario. The operational plane uses the LDA of the LEO constellation to offer a low data rate yet high availability link through the network. The service data plane uses the HDA of the LEO satellites and the MEO/GEO relay satellites [91]. These allow the service data plane to transmit with high data rates but require coordination from the operational plane (pointing, booking, etc.). Figure 4: Sporadic connectivity scenario featuring a sparse LEO constellation for IoT services. Figure 7 presents the control architecture design for persistent connectivity constellations like the example. The system is again only controlled using SatOps interfaces and commands (platform and ground control). Like with the sporadic connectivity architecture, the CMS takes as inputs the operational criteria from both network and satellite operators and generates the SatOps that follow the satellite operator requirements and best align with the network operator's intents. The platform control works with platform OM as well, and the only change with respect to the sporadic connectivity architecture is that commands focus on the communications system/payload, namely the LDA and HDA antennas. With this, the CMS controls both data planes. As for the ground control, it is mainly composed of the different plane GSs. As such, the CMS coordinates GS passes and  
Figure 5: Control diagram using integrated operations for a sporadic connectivity constellation. The CMS receives operational criteria from both MNO and SNO, generating unified control commands for satellite platform subsystems and ground elements. Platform control manages satellite OM including payload configuration for gNB, CN functions, and SaF proxies. Ground control coordinates GS passes and ground-based SaF proxies.