top of page

An NTN with a Transparent Payload: Architecture, NTN Gateway, Control Functions and 5G NR Operation

8 minutes ago
23 min read

Introduction: Understanding the Transparent Payload NTN

Non-Terrestrial Networks (NTN) are extending cellular connectivity beyond conventional terrestrial infrastructure. Satellites and high-altitude platforms can help provide communication services in remote locations, maritime environments, aviation, disaster-affected areas and regions where terrestrial network coverage is limited.

However, integrating satellites into a cellular network requires more than placing a radio transceiver in space. Engineers must understand how radio signals travel between a user device, a satellite platform, an NTN Gateway and the ground-based network functions.

One important architecture is the NTN with a transparent payload, which forms part of the 3GPP NTN framework introduced for 5G NR in Release 17.

In this architecture, the satellite or airborne platform primarily acts as a radio relay. It forwards the received radio signal toward the appropriate destination without hosting the complete gNB protocol stack on the platform.

This distinction is important because the radio access network's higher-level processing remains associated with ground-based infrastructure.

A transparent payload NTN implementation typically involves three major infrastructure elements:

  1. NTN payload: The radio relay equipment carried by a satellite or airborne platform.

  2. NTN Gateway: The ground-based infrastructure that connects the satellite radio system with the terrestrial network.

  3. NTN control function: The functionality responsible for controlling NTN platforms and infrastructure resources and providing relevant control information.

Together, these components support the NTN serving-link provisioning system, which works alongside the non-NTN gNB functions to provide 5G NR connectivity.

The following guide explains this architecture, the role of each component, the difference between feeder and service links, beam-related provisioning information, operational challenges and the practical considerations involved in implementing a transparent payload NTN.


Apeksha Telecom NTN Connectivity
Apeksha Telecom NTN Connectivity

Table of Contents

  1. What Is an NTN with a Transparent Payload?

  2. What Is a Transparent Payload in Satellite Communication?

  3. Transparent Payload NTN Architecture

  4. Major Components of a Transparent Payload NTN

  5. How NR-Uu Signals Travel Through the NTN

  6. NTN Payload and Platform Responsibilities

  7. Role of the NTN Gateway

  8. Understanding the NTN Control Function

  9. NTN Serving-Link Provisioning System

  10. Feeder Link vs Service Link

  11. Beam Mapping and NTN Cell Configuration

  12. Time Windows, Satellite Movement and Link Switching

  13. Ephemeris Information and Beam Footprint Management

  14. What Additional Information Is Needed for NTN Operation?

  15. Transparent Payload vs Regenerative Payload

  16. Technical Challenges in Transparent Payload NTN

  17. Practical Example: Connecting a 5G UE Through a Satellite

  18. Importance of Transparent Payload NTN for 5G-Advanced and 6G

  19. Key Benefits and Limitations

  20. Conclusion

  21. Frequently Asked Questions

  22. References and Further Reading


  1. What Is an NTN with a Transparent Payload?

A Non-Terrestrial Network uses communication infrastructure located above the Earth's surface. This infrastructure can include satellites in different orbits and airborne platforms such as high-altitude platform stations (HAPS).

In a transparent payload architecture, the NTN platform forwards radio signals between the user equipment and ground infrastructure. The satellite does not need to host the complete gNB processing functions.

The term transparent refers to the payload's role in the communication path. The payload relays the radio signal rather than implementing the full cellular base-station protocol stack onboard.

This does not mean that the satellite performs no processing whatsoever. Practical radio payloads can include filtering, amplification, frequency conversion, beamforming and other radio-frequency operations. The exact implementation depends on the system design.

The important architectural distinction is that the complete gNB functionality is not hosted on the transparent payload.


Why does this architecture matter?

A conventional terrestrial 5G network has a UE communicating with a terrestrial gNB over the NR-Uu radio interface.

With transparent payload NTN, the same logical radio interface is extended through a non-terrestrial radio path.

The satellite provides the radio relay, while the associated ground infrastructure supports the remaining network functions.

This approach allows network operators to use satellite platforms to extend coverage without requiring every satellite to operate as a complete onboard gNB.

It also creates implementation considerations involving the satellite-to-ground connection, beam configuration, timing, Doppler compensation, gateway selection and service continuity.

3GPP TR 38.821 documents technical solutions studied for NR support over NTN, while the subsequent NR specifications define the applicable standardized radio and protocol behavior.


  1. What Is a Transparent Payload in Satellite Communication?

A transparent payload is a satellite or airborne communication payload that relays the received radio signal instead of implementing the complete base-station protocol stack onboard.

Consider a simplified communication path:

5G UE → Satellite → NTN Gateway → Ground-based gNB functions → 5G Core

The reverse direction carries downlink traffic toward the UE.

The satellite serves as an intermediate radio element in this path. It receives the signal through one radio link and forwards it through another.

A practical implementation may process the radio signal at the physical or radio-frequency level. However, it does not perform the complete onboard gNB processing associated with a regenerative architecture.

Example

Imagine a user in a remote mountainous region where terrestrial cellular coverage is unavailable.

The user's 5G NTN-capable device communicates with a satellite using the applicable NTN radio interface.

The satellite forwards the signal toward a ground-based NTN Gateway. The ground infrastructure then connects the radio path to the relevant gNB functionality and the wider network.

For downlink communication, the process works in the opposite direction.

The satellite therefore extends the radio coverage of the ground-based network without necessarily becoming a complete cellular base station in space.


  1. Transparent Payload NTN Architecture

A transparent payload NTN implementation includes more than the satellite itself. It requires a coordinated arrangement of radio infrastructure, gateway resources and control functions.

The main elements are:

  • NTN platform and payload.

  • NTN Gateway.

  • NTN control function.

  • NTN serving-link provisioning system.

  • Non-NTN infrastructure gNB functions.

  • User equipment and the wider mobile network.

Logical architecture

The following simplified representation illustrates the principal components.

                       NTN CONTROL FUNCTION

                                |

                   Platform and Resource Control

                                |

                                v

 

  5G UE <---- Service Link ----> NTN PAYLOAD

                                  |

                                  |

                           Feeder Link

                                  |

                                  v

                            NTN GATEWAY

                                  |

                                  |

                       Ground Network Transport

                                  |

                                  v

                         gNB FUNCTIONALITY

                                  |

                                  v

                              5G CORE

Important: This is a simplified conceptual diagram, not a complete 3GPP reference architecture. The actual placement of functions, interfaces and transport connections depends on the deployment.

The NTN serving-link provisioning system provides the functionality needed to support the NR-Uu radio path through the NTN infrastructure.

It works with the non-NTN gNB functions to implement the overall radio access network.

The architecture may include multiple NTN payloads and multiple NTN Gateways. This is important for satellite constellations, gateway diversity and deployments in which service and feeder links change over time.


Why are multiple payloads and gateways important?

A single satellite may not be able to provide continuous coverage to every geographical area. Satellites move relative to the Earth's surface, and their coverage footprints change.

Similarly, a gateway may not remain the best or available ground connection throughout a satellite's movement.

A practical deployment therefore needs mechanisms to manage available payloads, beams, gateways and switching schedules.

The architecture must coordinate these resources so that the network can maintain connectivity as conditions change.


  1. Major Components of a Transparent Payload NTN

4.1 NTN Payload

The NTN payload is the communication equipment installed on a satellite or airborne platform.

Its primary communication role is to relay radio signals between the service link and the feeder link.

Depending on the implementation, the payload may support:

  • Radio-frequency reception and transmission.

  • Signal amplification.

  • Frequency conversion.

  • Beam generation and beam steering.

  • Filtering and channelization.

  • Communication with the platform's supporting systems.

The exact set of functions depends on the radio payload design.

4.2 NTN Platform

The platform is the physical vehicle carrying the NTN payload.

Examples include:

  • Low Earth Orbit (LEO) satellites.

  • Medium Earth Orbit (MEO) satellites.

  • Geostationary Earth Orbit (GEO) satellites.

  • High-altitude platform stations.

  • Other suitable airborne platforms.

The platform supplies the infrastructure needed to operate the payload.

This can include power, physical support, commanding capabilities, telemetry, attitude control, thermal management and radiation protection where applicable.

These supporting systems are important because the payload must operate reliably in an environment that differs substantially from a terrestrial base station.

4.3 NTN Gateway

The NTN Gateway provides the ground-side connection for the satellite communication path.

It supports the necessary radio-signal forwarding and connectivity between the NTN infrastructure and the terrestrial network.

Depending on the deployment, it may connect the satellite system to the ground-based gNB functions through suitable transport infrastructure.

Gateway availability, geographic location, link quality and scheduling can influence network operation.

4.4 NTN Control Function

The NTN control function manages NTN platforms and infrastructure resources.

Its responsibilities can include controlling satellite or airborne platforms, coordinating payload and gateway resources, and supplying control information such as ephemeris data to the relevant gNB functions.

The exact implementation and division of responsibilities can vary between deployments.

The control function is therefore important for coordinating the dynamic aspects of NTN operation.

4.5 Non-NTN gNB Functions

These are the gNB functions that are not implemented as part of the transparent payload on the NTN platform.

They work with the NTN serving-link provisioning system to provide the overall radio access functionality.

They also use relevant control information to account for the satellite's position, radio propagation conditions, beam configuration and mobility-related events.

This division allows the radio relay and the cellular processing functions to remain architecturally distinct.


  1. How NR-Uu Signals Travel Through the NTN

The NR-Uu interface is the radio interface between the UE and the 5G NR access network.

In NTN, this radio path may extend through a transparent payload before reaching the ground-based infrastructure.

The following sequence provides a simplified view of uplink operation.

Step 1: UE transmits an uplink signal

The UE transmits the relevant NR signal using the NTN radio configuration.

The transmission must account for the radio conditions and applicable NTN-specific procedures.

Step 2: Satellite receives the signal

The NTN payload receives the transmission through the service link.

It performs the radio operations supported by its implementation and forwards the signal through the appropriate feeder-link path.

Step 3: Signal reaches the NTN Gateway

The NTN Gateway receives the forwarded signal and provides the necessary connection toward the ground-based radio access infrastructure.

Step 4: Ground-based gNB functionality processes the communication

The relevant gNB functions process the received radio communication according to the applicable NR procedures.

The exact processing boundary depends on the implementation of the NTN serving-link provisioning system and associated ground infrastructure.

Step 5: Communication proceeds through the network

After the relevant radio access processing, traffic can proceed through the wider network toward the destination.

Downlink communication follows the reverse direction: the ground-based network sends the required signal through the NTN Gateway and feeder link, the payload relays it through the service link, and the UE receives it.

Key engineering point

The transparent payload does not eliminate the need for 5G NR processing. Instead, it changes how the radio path is physically implemented.

This is why engineers must study both the cellular architecture and the satellite radio environment when designing or troubleshooting NTN systems.


  1. NTN Payload and Platform Responsibilities

Understanding the difference between an NTN payload and an NTN platform is essential.

The platform is the vehicle; the payload is the communication equipment it carries.

For example, a satellite may contain a communication payload along with power systems, propulsion, thermal-control equipment, antennas and attitude-control systems.

The payload relies on the platform to provide the physical and operational conditions needed for communication.

6.1 Platform support functions

The platform may provide:

  • Power supply: Electrical power for communication and supporting equipment.

  • Commanding: Mechanisms for receiving and executing authorized operational commands.

  • Telemetry: Information about platform health and operating conditions.

  • Attitude control: Maintaining or adjusting the platform's orientation.

  • Thermal management: Managing the operating temperature of onboard equipment.

  • Physical protection: Providing structural support and, where necessary, radiation protection.

These functions help keep the communication payload operational.

6.2 Why platform control matters to the radio network

A satellite's position and orientation influence the coverage area and the geometry of its communication links.

For example, the movement of a LEO satellite changes its position relative to a user and a gateway. This affects the available radio path and may require the network to update its resource assignments.

Similarly, a change in the pointing direction of a beam can alter the geographical area served by that beam.

The NTN control function and the supporting network management systems must therefore coordinate platform operation with radio-network requirements.


  1. Role of the NTN Gateway

The NTN Gateway is a key ground-based component in a transparent payload architecture.

Its role is not simply to provide a physical landing point for a satellite signal. It forms part of the communication path connecting the non-terrestrial radio infrastructure with the ground-based network.

7.1 Gateway responsibilities

Depending on the implementation, the gateway infrastructure can support:

  1. Reception and transmission of satellite radio signals.

  2. Connectivity between feeder links and terrestrial network transport.

  3. Forwarding of signals associated with the NR-Uu radio path.

  4. Coordination with available NTN payload resources.

  5. Support for gateway selection and feeder-link switching.

  6. Integration with the ground-based gNB functions.

These activities must be coordinated with the rest of the network.

7.2 Why can a deployment require multiple gateways?

A satellite constellation may need multiple gateways to provide coverage, increase operational flexibility or maintain a suitable connection as satellites move.

A satellite's visibility from a particular gateway changes over time. Weather, radio-frequency conditions, gateway availability and deployment topology can also influence the preferred connection.

Multiple gateways can provide alternative connectivity paths, but they introduce additional coordination requirements.

The network must know which gateway is serving a particular resource and when a feeder-link switchover is expected.

7.3 Gateway selection and service continuity

Consider a satellite moving away from one gateway's useful coverage region and toward another.

The network may need to transfer the feeder-link connection to a different gateway.

Depending on the implementation, the transition may require resource reconfiguration, transport-path changes and coordination with the NTN serving-link provisioning system.

A poorly coordinated transition could interrupt traffic. A well-planned transition can help maintain service continuity.

This is why gateway scheduling is an important part of practical NTN operation.


  1. Understanding the NTN Control Function

The NTN control function coordinates the operation of NTN platforms and infrastructure resources.

In the architecture described in the source material, its responsibilities include controlling spaceborne and airborne platforms, managing resources such as NTN payloads and gateways, and providing control information to the relevant non-NTN gNB functions.

8.1 Platform control

The control function may coordinate platform-related operations and receive information about platform status.

This information helps the wider system understand the resources available for communication.

8.2 Resource control

An NTN deployment may include multiple satellites, multiple beams and several gateways.

The control function must support the coordination needed to use these resources effectively.

For example, the network may need to determine which satellite or gateway can serve a particular area during a given period.

8.3 Providing control information

Some NTN operations require knowledge of satellite position, timing and service availability.

Ephemeris information, for example, can support predictions about satellite position and help the network prepare for changing radio conditions.

The non-NTN gNB functions may use relevant information to support radio configuration, timing and mobility-related operations.

8.4 A critical standards distinction

The architectural role of an NTN control function should not be confused with a single universally mandated physical network element.

The implementation may distribute control and management responsibilities across multiple systems.

Likewise, the mechanisms used to provision all the control information needed by a gNB are not necessarily defined in full by 3GPP.

This distinction matters when engineers compare a logical architecture with a commercial deployment.

A logical architecture describes functional relationships; a commercial implementation must additionally define the practical systems, interfaces, operational procedures and management arrangements needed to make those relationships work.


  1. NTN Serving-Link Provisioning System

The NTN serving-link provisioning system is a central element in the architecture described in the source material.

It provides the functionality needed to support the NR-Uu radio path through the NTN infrastructure and works with the non-NTN gNB functions.

A deployment may use one or multiple NTN payloads on different platforms and one or multiple NTN Gateways.

This means that the system must account for the relationships between radio resources, beams, gateways, platforms and the geographical areas being served.

9.1 What does provisioning involve?

Provisioning can include information needed to determine:

  • Which NTN cell identifier is associated with a beam.

  • Which geographical area a cell represents.

  • Which platform and gateway serve the cell.

  • When a particular link is expected to be available.

  • When a feeder link or service link is expected to switch.

  • How beam movement affects the geographical footprint.

The required information depends on the deployment and the applicable interface and specification requirements.

9.2 Why is provisioning important?

Without accurate provisioning, the network may have difficulty coordinating radio resources with the satellite infrastructure.

For example, a cell identifier alone does not tell an operational system where the associated beam is currently located or which gateway is serving it.

Additional information is needed to associate the logical cell with the relevant beam, geographical area and time-dependent serving resources.

Provisioning therefore connects the logical radio access network with the physical satellite infrastructure.


  1. Feeder Link vs Service Link

Two terms are particularly important when understanding transparent payload NTN: service link and feeder link.

Although both are radio links, they connect different parts of the communication system.

Parameter

Service Link

Feeder Link

Primary connection

UE and NTN payload

NTN payload and NTN Gateway

Main purpose

Carries the UE's radio communication

Connects the satellite radio system with ground infrastructure

Network role

Part of the NR-Uu radio path

Supports the satellite-to-ground connection

Main engineering considerations

Coverage, link budget, propagation delay, Doppler and beam footprint

Gateway visibility, link availability, capacity and switching

Relationship to the UE

Directly associated with the UE's satellite radio path

Normally not the UE's direct radio link

Potential changes

Beam or serving-satellite changes

Gateway or feeder-link changes

10.1 Service link

The service link connects the UE to the NTN payload.

Its performance depends on factors such as the distance between the UE and satellite, antenna characteristics, propagation conditions, radio resources and beam coverage.

For a moving satellite, the service-link geometry changes over time.

This can affect propagation delay, Doppler shift and the availability of the serving beam.

10.2 Feeder link

The feeder link connects the NTN payload to the NTN Gateway.

It provides the satellite-side connection to the ground network.

Its availability depends on the satellite-to-gateway geometry, the radio system and the gateway's operational status.

A feeder-link switchover can be necessary when a different gateway becomes more suitable or when the existing link is no longer available.

10.3 Why engineers must distinguish them

A service-link switchover and a feeder-link switchover are different operational events.

A service-link change affects the radio path between the UE and the NTN payload.

A feeder-link change affects the connection between the NTN payload and the ground gateway.

Depending on the topology, one event may occur without the other.

For example, a satellite could continue serving a user through the same beam while its ground connection changes from one gateway to another.

This distinction is useful when analyzing handovers, interruptions and link-switching behavior.


  1. Beam Mapping and NTN Cell Configuration

Beam mapping connects the logical radio-network configuration with the physical beam and geographical area served by the NTN infrastructure.

In NTN, a cell cannot always be understood solely as a fixed geographical area, as it often can be in a simplified terrestrial-network example.

Satellite movement, beam steering and platform selection can change the relationship between a beam and the Earth's surface.

The source material identifies several categories of information that may be required for beam-related provisioning.

11.1 Mapping cell identifiers to beams

The network may need to associate an NTN cell identifier with a specific beam.

The applicable mapping depends on the interface and the architecture.

For example, provisioning information may describe the relationship between the NTN cell identifier used on the NG interface and the relevant beam, or between the NTN cell identifier used on the Uu interface and the beam.

These mappings must be interpreted according to the specific deployment and interface requirements.

11.2 Cell reference location

The system may also need a reference location for the geographical area served by a cell.

This could include a cell centre and a description of its coverage range.

The reference location helps relate a logical cell to a physical geographical area.

However, a reference location alone is not sufficient to describe every aspect of a moving satellite beam. Additional information may be needed to describe the footprint's size, shape and movement.

11.3 Mapping cells to geographical areas

The network may require information linking a cell identifier on the Uu interface with the geographical area reported through the NG interface.

This relationship supports coordination between radio access procedures and the network's geographical representation of service areas.

It is especially relevant where satellite movement or beam steering changes the area associated with a logical cell.

11.4 Why accurate mapping matters

Suppose a satellite beam moves across a large geographical region.

The logical cell identity, geographical footprint and serving-platform information must remain consistent with the actual deployment configuration.

If these relationships are not updated or coordinated correctly, the network may associate a cell with an incorrect area or resource.

Such inconsistencies can complicate service-area management, mobility and troubleshooting.

Beam mapping is therefore not simply a documentation exercise. It is part of the operational information needed to coordinate the radio network with the NTN infrastructure.


  1. Time Windows, Satellite Movement and Link Switching

NTN resources are dynamic.

A satellite moves relative to the Earth's surface, a beam's footprint can change, and the availability of a feeder link may vary over time.

For this reason, practical provisioning may need to include time-dependent information.

12.1 Serving-resource time windows

A time window identifies a period during which a particular resource or configuration is expected to apply.

Depending on the architecture, provisioning may include information about:

  • The period during which a beam serves a particular cell.

  • The platform serving the area.

  • The gateway associated with a feeder link.

  • The timing of an expected service-link switchover.

  • The timing of an expected feeder-link switchover.

This information helps the network prepare for upcoming resource changes.

12.2 Successive feeder-link switchovers

A satellite may change its ground connection as its position changes or as the network selects a different gateway.

Provisioning information can describe the expected time windows for successive feeder-link changes.

The operational objective is to coordinate the change with the wider communication system.

Depending on the design, a switchover may involve preparing an alternative link, updating resource associations and managing the corresponding transport path.

12.3 Successive service-link switchovers

The service link may also change as a result of satellite movement, beam changes or serving-resource selection.

The network may need a schedule describing when a different platform or beam is expected to serve the relevant area.

The exact procedure depends on the deployment and the mobility mechanisms being used.

12.4 Why time-based coordination matters

Consider a moving LEO satellite.

At one moment, a user may be served by one satellite and beam. Later, another satellite may become the preferred serving resource.

If the network can predict the transition, it may be able to prepare the relevant configuration in advance.

However, prediction alone does not guarantee uninterrupted service. Actual performance depends on radio conditions, implementation details, available resources and the success of the transition procedure.


  1. Ephemeris Information and Beam Footprint Management

Ephemeris information describes the orbital position and motion of a satellite over time.

It is an important input for understanding the satellite's position relative to the Earth and predicting its future movement.

In NTN, ephemeris-related information can support several network operations.

13.1 Satellite position and movement

Knowing the satellite's position helps the network estimate its relationship with the UE and the gateway.

This supports the planning of service availability and radio-resource changes.

13.2 Beam footprint prediction

A beam's footprint is the geographical area illuminated or served by that beam.

The footprint depends on factors such as satellite position, antenna characteristics, beam pointing and the radio system's configuration.

As the satellite moves, the footprint may move across the Earth's surface.

Ephemeris information can contribute to predicting this movement, although additional antenna and beam-configuration information is also required.

13.3 Doppler and propagation-delay considerations

Satellite motion changes the relative velocity between the communicating endpoints.

This can produce Doppler shift, while the long propagation distance introduces delay.

These factors are particularly important in NTN because the distances and relative motion can differ significantly from conventional terrestrial radio links.

Relevant control information can help the radio access network prepare for the expected conditions and apply the required NTN procedures.

13.4 Service continuity

Predicting the movement of a satellite and its beam can help the network prepare for changes in serving resources.

For example, it may help determine when another satellite is expected to become available or when a gateway transition should be planned.

The benefit depends on the accuracy of the available information and how effectively it is incorporated into network control and radio procedures.


  1. What Additional Information Is Needed for NTN Operation?

A transparent payload NTN deployment needs more than a cell identifier and a satellite location.

The source material describes different categories of provisioning information that can be relevant to particular interface and deployment arrangements.

The following table summarizes these categories conceptually.

Information Category

What It Describes

Why It Matters

Cell-to-beam mapping

Association between a logical cell and a beam

Connects network configuration with radio resources

Cell reference location

Reference position and coverage range

Helps identify the geographical area associated with a cell

Cell and time-window mapping

The beam and cell association during a defined period

Supports time-dependent resource coordination

Feeder-link switching schedule

Expected changes in gateway connectivity

Helps prepare ground-link transitions

Service-link switching schedule

Expected changes in the UE-to-payload radio path

Supports mobility and service continuity

Serving-platform information

Which satellite or airborne platform serves an area

Helps coordinate available NTN resources

Gateway information

Which gateway is associated with the relevant resources

Supports connectivity and switching coordination

Beam footprint information

Coverage area and movement of the beam

Helps relate radio resources to geographical coverage

Satellite elevation information

Elevation angle relative to the UE or relevant location

Can help assess visibility and radio-link conditions

Ephemeris information

Satellite position and motion

Supports prediction, timing and mobility-related operations

The precise information fields, formats, interfaces and provisioning responsibilities depend on the applicable specifications and implementation.

It is important not to interpret every item in this conceptual table as a mandatory field on every 3GPP interface.

The distinction between standardized radio procedures and deployment-specific operational management is particularly important in NTN.


  1. Transparent Payload vs Regenerative Payload

Transparent and regenerative payloads represent two different approaches to implementing satellite-based radio access.

A transparent payload primarily relays the radio signal, while a regenerative payload can perform additional processing onboard the satellite.

The exact capabilities of a regenerative payload depend on the implementation and the functions placed onboard.

Parameter

Transparent Payload

Regenerative Payload

Main role

Relays the radio signal

Processes and regenerates signals using onboard functions

Complete gNB processing onboard

Not required by the transparent architecture

May be implemented in whole or in part, depending on the design

Ground infrastructure

Supports the relevant gNB processing and network connectivity

Still required for functions that remain on the ground

Onboard complexity

Generally lower than a design with extensive onboard gNB processing

Generally higher when more network functions are onboard

Ground-network dependency

Strong dependence on ground-based radio access processing

Depends on the division of functions between satellite and ground

Typical architectural consideration

Radio relay and ground-based processing

Greater onboard processing and potentially different transport arrangements

Deployment considerations

Gateway availability, feeder links, radio relay and timing

Onboard processing, power, computing resources and transport architecture

Which architecture is better?

Neither approach is universally better.

Transparent payloads can be attractive when operators want to relay radio signals while retaining the relevant gNB processing on the ground.

Regenerative payloads can support different architectural choices by moving some processing functions onboard.

The appropriate choice depends on coverage objectives, payload capabilities, latency requirements, operational complexity, cost, power constraints and the intended network architecture.

Important standards note: The table describes the general architectural distinction. Specific regenerative capabilities, including the placement of gNB functions, depend on the implementation and the applicable 3GPP specifications.


  1. Technical Challenges in Transparent Payload NTN

Although transparent payload NTN can extend cellular coverage, its deployment involves several engineering challenges.

16.1 Long propagation delay

Satellite communication paths can be substantially longer than terrestrial cellular paths.

The resulting propagation delay affects communication timing and may influence the design and operation of radio procedures.

Engineers must account for the satellite's orbit, the geometry of the service and feeder links, and the end-to-end path.

16.2 Doppler shift

Relative movement between a satellite and a UE can produce Doppler shift.

The magnitude depends on factors such as relative velocity, carrier frequency and link geometry.

NTN systems must use appropriate procedures and configuration to manage the resulting frequency effects.

16.3 Beam movement

Satellite beams may move across the Earth's surface, depending on the satellite orbit and beam-steering strategy.

This creates a need to coordinate beam configuration, geographical coverage and serving-cell information.

16.4 Gateway availability

A gateway may not remain available to a satellite throughout its movement.

The network must therefore manage gateway selection and feeder-link transitions.

16.5 Resource scheduling

A practical deployment may include multiple satellites, beams and gateways.

The system must coordinate their availability and allocate the appropriate resources over time.

16.6 Control-information accuracy

Incorrect or outdated information about satellite position, beam mapping or link schedules can undermine resource coordination.

Operational systems must therefore maintain reliable configuration data and suitable update procedures.

16.7 Service continuity

A change in serving satellite, beam or gateway can affect an active communication session.

The network needs suitable mobility, switching and recovery mechanisms to minimize disruption.

These challenges show why NTN engineering requires knowledge of both 5G radio procedures and satellite communication systems.


  1. Practical Example: Connecting a 5G UE Through a Satellite

Consider a user located in an area without terrestrial cellular coverage.

A suitable NTN deployment provides service through a satellite equipped with a transparent payload.

The communication sequence can be understood in several stages.

Stage 1: Service availability

The network determines which satellite and beam can serve the geographical area during the relevant time window.

The associated provisioning information identifies the relevant resources and their availability.

Stage 2: UE communication

The NTN-capable UE communicates over the service link using the applicable NR-NTN procedures.

The radio configuration must account for the satellite communication environment.

Stage 3: Signal relay

The transparent payload receives the radio signal and relays it through the appropriate feeder link.

The payload does not need to implement the complete gNB protocol stack.

Stage 4: Gateway connectivity

The NTN Gateway receives the forwarded signal and connects it to the relevant ground infrastructure.

Stage 5: Ground-based radio processing

The non-NTN gNB functions work with the NTN serving-link provisioning system to support the radio access operation.

Stage 6: Wider network connectivity

The communication proceeds through the wider network toward the intended destination.

Stage 7: Resource transition

As the satellite moves, the network may need to update the serving beam, select another satellite or change the gateway.

Relevant control and provisioning information can help the network coordinate these changes.

This example illustrates the key principle: transparent payload NTN extends the radio path through a satellite while retaining the relevant gNB processing outside the transparent payload.


  1. Importance of Transparent Payload NTN for 5G-Advanced and 6G

NTN is an important part of the broader effort to integrate terrestrial and non-terrestrial connectivity.

Transparent payload architectures provide one way to combine satellite radio infrastructure with cellular network functions.

This is relevant to several potential applications:

  • Extending mobile connectivity to remote regions.

  • Supporting communication over oceans and other isolated areas.

  • Providing connectivity for suitable aviation and maritime services.

  • Improving communication resilience in disaster-affected regions.

  • Supporting selected IoT deployments outside conventional terrestrial coverage.

  • Enabling integrated satellite and terrestrial network services.

The continued evolution of NTN specifications also reflects the industry's interest in more capable satellite-based communication systems.

Release 17 introduced the first normative 3GPP NTN support for NR and IoT technologies. Later releases have continued to address enhancements and additional deployment scenarios.

Engineers should consult the relevant specifications when assessing which features are standardized for a particular release.


  1. Key Benefits and Limitations

Benefits

Extended coverage: Satellites and suitable airborne platforms can provide service in locations that are difficult to cover using terrestrial infrastructure alone.

Separation of radio relay and ground processing: The transparent architecture allows the payload to relay signals without requiring the complete gNB protocol stack onboard.

Architectural flexibility: The deployment can use multiple payloads and gateways, subject to the implementation.

Integration with cellular systems: The architecture supports the extension of NR radio connectivity through non-terrestrial infrastructure.

Centralized ground-side processing: Retaining the relevant gNB functions on the ground can simplify some aspects of onboard payload design.

Limitations and trade-offs

Dependence on ground infrastructure: The architecture relies on the required gateway and ground-based network functions.

Propagation delay: Long radio paths introduce delays that must be considered in system design.

Doppler and mobility: Satellite motion creates additional radio and resource-management challenges.

Gateway scheduling: A moving satellite may need to change its ground connection.

Provisioning complexity: Cell, beam, platform, gateway and time-window information must be coordinated.

Deployment-specific constraints: Actual performance depends on satellite orbit, radio spectrum, payload capability, antenna configuration, gateway placement and network implementation.

The architecture is therefore best evaluated as part of a complete communication system rather than as a standalone satellite component.


Conclusion

An NTN with a transparent payload is an important architectural approach for extending 5G NR connectivity through satellite and airborne platforms.

Its defining feature is the separation between radio-signal relay and the complete gNB processing functionality.

The NTN payload forwards the radio signal, the NTN Gateway connects the satellite system with ground infrastructure, and the NTN control function supports the management of platforms and infrastructure resources.

The NTN serving-link provisioning system works with the non-NTN gNB functions to support the NR-Uu radio path.

Understanding this architecture also requires understanding feeder links, service links, beam mapping, cell reference locations, ephemeris information and time-dependent switching schedules.

These details become especially important in moving-satellite deployments, where the network must coordinate changing coverage footprints, serving platforms and gateway connections.

For telecom engineers, the key takeaway is that transparent payload NTN is not simply a satellite communication link; it is a coordinated radio access architecture connecting the UE, satellite infrastructure, ground gateways and cellular network functions.

A solid understanding of these relationships helps engineers analyze NTN deployment options, understand 3GPP architecture, troubleshoot connectivity challenges and prepare for the evolution of satellite-enabled 5G-Advanced and 6G networks.


Continue Learning with Telecom Gurukul

For engineers looking to strengthen their understanding of 5G NR, NTN, protocol testing, RAN architecture and future telecom technologies, explore the technical learning resources available through Telecom Gurukul.

Explore the institute's 5G/6G Non-Terrestrial Networks (NTN) Certification Program for a broader introduction to satellite-enabled cellular networks.

For training enquiries, contact Apeksha Telecom / The Telecom Gurukul


Frequently Asked Questions

  1. What is a transparent payload in NTN?

A transparent payload is a satellite or airborne communication payload that relays radio signals between the UE and ground infrastructure without implementing the complete gNB protocol stack onboard.


  1. What are the main components of transparent payload NTN architecture?

The major components include the NTN payload, NTN platform, NTN Gateway, NTN control function, NTN serving-link provisioning system and non-NTN gNB functions.


  1. Does a transparent satellite contain a complete 5G gNB?

Not as part of the transparent payload architecture. The relevant gNB processing functions remain outside the transparent payload, although the precise division of functionality depends on the implementation.


  1. What is the role of an NTN Gateway?

The NTN Gateway supports the satellite-to-ground connection and provides connectivity between the NTN infrastructure and the ground-based network.


  1. What is the difference between a feeder link and a service link?

The service link connects the UE and the NTN payload. The feeder link connects the NTN payload and the NTN Gateway.


  1. What is an NTN control function?

It is functionality responsible for coordinating NTN platforms and infrastructure resources and providing relevant control information to other network functions.


  1. Why is ephemeris information important in NTN?

Ephemeris information describes satellite position and motion. It can help the network predict satellite movement, coordinate resources and prepare for changes in radio-link geometry.


  1. What is beam mapping in NTN?

Beam mapping associates logical cell identifiers with radio beams and, where required, their geographical coverage and time-dependent serving resources.


  1. Why are time windows needed in transparent payload NTN?

Time windows can describe when a particular beam, satellite or gateway resource is expected to be available. They help coordinate resource changes and link switching.


  1. What is the difference between transparent and regenerative payloads?

A transparent payload primarily relays the radio signal. A regenerative payload can perform additional processing onboard, potentially including some gNB functions, depending on the implementation.


  1. Which 3GPP document explains NTN solutions for NR?

3GPP TR 38.821 is titled Solutions for NR to support Non-Terrestrial Networks (NTN). It is an important technical reference for understanding NTN solution studies.


  1. Is transparent payload NTN relevant to 5G-Advanced and 6G?

Yes. NTN continues to be relevant to the evolution of satellite and terrestrial network integration. The exact capabilities available depend on the applicable 3GPP release and implementation.


References and Further Reading

  1. 3GPP TR 38.821 — Solutions for NR to support Non-Terrestrial Networks (NTN): Official 3GPP specification portal

  2. GSMA — 3GPP overview of Non-Terrestrial Networks (NTN): GSMA NTN overview

  3. 3GPP NTN and satellite communication technical background: 3GPP TR 38.821 technical report PDF

  4. Telecom Gurukul — Technical training and learning resources: Telecom Gurukul official website

  5. Telecom Gurukul — NTN Certification Program: 5G/6G NTN Certification Program 2026

 

Comments


  • Facebook
  • Twitter
  • LinkedIn

©2022 by Apeksha Telecom-The Telecom Gurukul . 

bottom of page