Space ODA: Integrating SatCom into the Terrestrial 5G/6G Ecosystem

As the need for global connectivity grows, the space industry is moving away from working in isolation and is becoming part of Non-Terrestrial Networks (NTNs) that connect with terrestrial 5G and future 6G networks. In this new environment, using TM Forum’s Open Digital Architecture (ODA) has transitioned from a theoretical concept into a practical business requirement.

Operators such as Société Européenne des Satellites (SES, the pioneer of ODA certification in this industry) and the project participants, Unified Network Integration for Terrestrial and Non-terrestrial Communications (UNITe), prove that standardizing satellite services through Open APIs and ODA components reduces service activation times by 90% and accelerates operational processes fivefold.

To see how this framework is changing the space connectivity market, we need to look at both its immediate benefits and the major technical challenges that must be solved for true plug-and-play interoperability.

Shifting from proprietary hardware to Network-as-a-Service (NaaS)

In the past, equipment suppliers such as Thales and Airbus provided end-to-end management systems designed for specific satellite constellations. These closed, proprietary setups make it hard for operators to expand their services. To unify systems under the Open Digital Architecture (ODA), these large, single-purpose systems need to be split into modular, interchangeable parts.

Replacing legacy infrastructure with a modular framework allows operators to treat satellite resources as regular network assets in a Network-as-a-Service (NaaS) model. With the ODA Canvas, they can automate how hybrid services are managed. This makes it possible to switch traffic smoothly between terrestrial 5G and satellite links during international transport, so data sessions stay connected.

Rethinking inventory systems: The move to 4D, real-time resource accounting

Traditional telecom inventory systems are built for fixed assets (e.g., base stations) that remain in one place, but Low Earth Orbit (LEO) satellites are always moving. Managing these fast-moving resources changes how networks track and report usage. Instead of static records, operators now need dynamic, time-aware systems that can follow satellite paths and show real-time availability.

LEO satellites act as high-speed mobile base stations, which adds new challenges to the network’s access layer. Signal range, strength, and quality change all the time as the satellite moves in relation to users on the ground. The high speed also causes the Doppler Effect, meaning real-time frequency adjustments are needed to compensate for the shifting frequency responses. Since the network is mobile, management systems must predict when satellites will move out of range and handle handovers to new satellites as they appear.

Key issues of ODA unification in the satellite sector

Achieving a fully unified terrestrial and non-terrestrial network requires overcoming several distinct technical and structural challenges across the architecture ecosystem.

Lack of a unified data model for orbital resources

TM Forum’s Information Framework (SID) was built for fixed, ground-based infrastructure such as cables and masts; it does not cover the changing conditions of satellites in orbit. Standard service features do not meet the unique needs of LEO and MEO satellites, such as delays based on position or dynamic beam hopping. Unless the SID standard is updated to include these features, connecting satellite networks with ground Operations Support Systems (OSS) will continue to need costly custom data translators. This ongoing need for custom solutions goes against the basic “plug-and-play” idea of the Open Digital Architecture framework.

Orchestration harmonization in a multi-vendor environment

Satellite equipment suppliers have usually offered full, closed management systems. To unify these systems under the ODA framework, these proprietary setups need to be broken into interchangeable parts. Right now, setting up a service that uses one vendor’s satellite and another’s ground gateway still needs manual work. TM Forum is working on standards such as Service Inventory (TMF 638) and Service Ordering (TMF 641) to promote open interfaces, but suppliers are hesitant to open their systems because they fear losing control over profits and unique technology features.

The challenges of edge computing and limited computing power in orbit

It is difficult to run ODA components directly on satellite hardware. The problem is that the ODA framework assumes cloud-native environments, which require substantial computing power and stable data transfers for reliable management. Satellites, however, operate under stringent energy and processor limitations. Moving ODA logic to the edge in space means that the components need to be much smaller and less energy-demanding, a concept referred to as Tiny-ODA. Without unified, lightweight management standards, autonomous network functions such as orbital link self-healing will remain restricted to ground control centers, slowing system response times.

Security and data sovereignty in hybrid networks

Connecting SatCom and terrestrial networks creates new security risks, especially around device identity management. Satellite networks often support critical government and military systems that require much stricter security measures than commercial networks. Building a unified ODA framework that allows networks to share infrastructure securely while also keeping sensitive traffic fully separate remains a significant challenge. Without a global identity management standard accepted by both civilian regulators and defense groups, it is hard to roll out shared platforms for both civilian and defense use.

Synchronizing software and hardware lifecycles

There is a significant gap between the lifespans of space hardware and terrestrial software. Satellites are built to work for 5 to 15 years, but ODA software and standards change every month. This means equipment launched into orbit must remain capable of interoperating with IT systems that will use entirely different versions of Open APIs a decade later.

To solve this issue, unification must incorporate long-term backward compatibility or standardize remote software update processes via Software-Defined Radio (SDR) automated by the ODA Canvas. Without this, operators risk having "technological orphans" in orbit – modern satellites that cannot be controlled by modern management systems.

The standardization roadmap: How TM Forum and UNITe are bridging the gap

Current standardization efforts within the TM Forum and projects such as UNITe focus on eliminating these barriers:

API adaptation for unified orchestration (TMF638 and TMF641)

Current standardization efforts focus on extending the standard Service Inventory (TMF 638) and Service Ordering (TMF 641) APIs to include specific orbital parameters. This change will help operators manage services across different vendors, avoid closed management systems, and automate service setup.

Predictive orchestration and seamless handovers

To manage the constant movement of low-orbit satellites, new AI and algorithm-based tools are being created. These systems use real-time data about satellite paths to manage traffic ahead of time. By predicting when satellites will move, the network can switch user sessions smoothly, so there is no drop in quality.

Software-defined radio (SDR) in ODA Canvas

Addressing the discrepancy between satellite operational lifespans and monthly software updates involves software-defined radio technology. Standardizing remote orbital software updates to ensure long-term compatibility between space-borne hardware and evolving terrestrial IT frameworks.

Tiny-ODA optimization for edge computing

To work within the tight power and computing limits of satellite processors, teams are improving cloud-native container environments. This effort, called Tiny-ODA, makes container systems run efficiently in space, opening the door to more autonomous management on satellites.

The business case for satellite and terrestrial convergence

Bringing satellite communications into terrestrial 5G and future 6G networks is a key step toward worldwide coverage without blind spots. Despite technical barriers such as data model gaps, on-orbit computing limitations, and multi-vendor lock-in that still need to be resolved, the long-term benefits, such as cost reduction and ease of connecting various technologies, will immensely benefit the entire industry. For connectivity providers, standardization brings new opportunities, business models, and revenue streams, along with the flexibility needed to lead the next generation of global connectivity.