Non-terrestrial networks use airborne or spaceborne platforms within a communications path. Payload function placement, the gateway-facing feeder link, the user-facing service link, and supplemental coverage are related but distinct planning subjects.
Why it matters: Architecture, service, spectrum, and regulatory conclusions depend on which part of the non-terrestrial path is being discussed. Keeping these concepts distinct improves requirements, evidence requests, and comparisons without prescribing a design.
A non-terrestrial network extends a communications path through an airborne or spaceborne platform. The payload may relay signals or perform selected onboard processing; the feeder link connects the platform to gateway infrastructure; the service link connects it to user equipment. Supplemental Coverage from Space adds a distinct United States regulatory context for complementary terrestrial mobile coverage. These concepts interact, but each answers a different architecture, service, or regulatory question.
A transparent payload relays the radio path between a user-side service link and a gateway-side feeder link without placing the principal base-station processing functions on the airborne or spaceborne platform. Ground-side network functions therefore remain central to the path, although the exact implementation is architecture-specific.
transparentpayload.comA regenerative payload places selected processing functions on the airborne or spaceborne platform in addition to radio-frequency relay functions. Depending on the architecture, those functions may include base-station-related processing, switching, or routing, but the term alone does not specify a complete onboard design.
regenerativepayload.comThe feeder link is the wireless connection between an NTN gateway on the ground and the NTN payload on an airborne or spaceborne platform. It is the gateway-facing side of the non-terrestrial access path and is distinct from the service link used by user equipment.
ntnfeederlink.comThe service link is the wireless connection between user equipment and the NTN payload on an airborne or spaceborne platform. It is the user-facing side of the non-terrestrial path and remains distinct from the feeder link between the payload and gateway infrastructure.
ntnservicelink.comIn the United States, Supplemental Coverage from Space is an FCC framework for authorized satellite operations that supplement terrestrial mobile coverage using terrestrial spectrum, subject to licensing, leasing, interference, service, and public-safety requirements.
supplementalcoveragefromspace.comTransparent and regenerative payloads distinguish relay-oriented from onboard-processing contexts. Feeder and service links distinguish the gateway-facing and user-facing sides of the path. Supplemental Coverage from Space addresses a regulated complementary-coverage context rather than a payload or link type.
3GPP describes NTN terminology and architecture, while the FCC defines the United States Supplemental Coverage from Space framework. LJP uses those sources to explain public terminology; the package structure itself is an LJP editorial construct.
3rd Generation Partnership Project (3GPP) · Official 3GPP technology overview
Explains NTN platform, payload, feeder-link, service-link, gateway, and release context used across the capability family.
Official overview; updated by 3GPP
The source explains 3GPP terminology and does not define or endorse the LJP package.
Federal Communications Commission · FCC 24-28; GN Docket No. 23-65
Adopts the United States regulatory framework for Supplemental Coverage from Space and defines its regulated scope.
Report and Order and Further Notice of Proposed Rulemaking; adopted March 14, 2024
The order governs SCS in the United States; it does not validate the LJP portfolio organization.
Non-terrestrial network evaluations often combine payload roles, gateway and user-side links, coverage outcomes, and adjacent platform context without clearly separating the decisions. Inconsistent language can obscure responsibilities, evidence needs, and the boundaries between public orientation and implementation-specific analysis.
Review the public definitions, relationships, buyer questions, and credibility boundaries.
Map the five capability questions to the buyer's architecture, portfolio, and decision context.
Define a scoped evaluation and identify the evidence required for a decision.
Conduct qualified diligence and decide whether controlled follow-on work is appropriate.
The package provides one active Canonical Package Namespace, five active peer Capability Namespaces, three contextual Supporting Namespaces, machine-readable identities, public boundaries, and a controlled path into qualified evaluation.
unifiedntn.com is the active organizing identity for the package. Unified NTN is LJP organizational terminology that coordinates the five capability questions without prescribing a network design.
This publication presents category structure, public definitions, relationships, and evaluation context. Buyers retain authority over architecture, implementation, vendor choice, standards interpretation, regulatory analysis, procurement, deployment, and transaction decisions.
The package organization is an LJP editorial construct. External sources explain their own terminology and do not endorse LJP, its namespaces, or a commercial evaluation.
Use the published package map to define a controlled, buyer-specific evaluation and the evidence needed for a decision.
Email LJP Asset Group