LJP Asset Group

LJP reference page · As of November 10, 2026

Satellite Direct-to-Device: Regulatory Terms, Network Architecture, and Spectrum Questions

A short public guide to the terms that appear when satellite access and cellular devices are discussed together. It separates regulatory wording, network architecture, spectrum questions, and LJP’s own descriptive reference names.

Terms and scope

Why do different organizations use different words for satellite-to-phone service?

Direct answer: the words often point to different layers of the subject. A regulatory framework can define conditions for a particular kind of authorization; a standards body can describe parts of a network architecture; and industry or plain-language terms can help a reader frame a question. Treating them as interchangeable can hide the distinction that matters.

FunctionRegulatory wordingStandards wordingIndustry wordingSource
U.S. framework for satellite service supplementing terrestrial mobile coverageSupplemental Coverage from Space (SCS)Not a substitute for an NTN architecture labelSatellite-to-phone is often used descriptively; on LJP pages it is plain-language wordingFCC 24-28
Connection between user equipment and a satellite or airborne platformAuthorization questions depend on the actual location and arrangementService linkPart of a direct-to-device path, not the whole service3GPP NTN overview
Connection between platform and ground gatewayAuthorization questions remain separateFeeder linkGround-side part of an NTN path3GPP NTN overview
Payload approachNot a regulatory finding by itselfTransparent and regenerative payloads are architectural distinctionsUse the underlying architecture source rather than a marketing label3GPP TR 38.821 (Release 16 study)

The FCC adopted an SCS framework in FCC 24-28 and separately sought comment on proposed portions. That framework is meaningful in its own regulatory setting; it is not a label for every satellite-to-device arrangement or every NTN architecture. Likewise, service and feeder links identify different communications relationships. They do not, by themselves, establish a device’s compatibility, coverage, authorization, or complete service availability.

Spectrum questions

What questions does “spectrum” leave unanswered?

Direct answer: naming a band or describing spectrum as available does not settle the rights, geography, time, intended use, technical conditions, or coordination that a proposal may require. Those questions need evidence tied to the actual arrangement.

A useful review first identifies the applicable authorization and the spectrum resource at issue. It then asks where and when the arrangement is proposed, what use is described, which equipment assumptions apply, and what coexistence or coordination evidence is relevant. A spectrum contribution or leasing description should be read against the governing FCC record and its conditions, rather than treated as a generic statement that anyone may use a resource. FCC 24-28 is the adopted SCS framework cited here.

Some questions are still proposals, not adopted rules. FCC 26-51 is an FCC proposal; final comment deadlines are not verified in this guide. It should therefore be read as proposed material, including any discussion of unlicensed-device and satellite operations, rather than as present operating authority.

Coexistence and coordination are similarly not shorthand for a result. Coexistence analysis asks whether identified uses may interact under stated assumptions. Coordination is a process among the relevant parties or authorities. Neither word, standing alone, supplies the facts needed to conclude that a particular arrangement can proceed. A review should preserve the underlying frequency, location, time, equipment, and authorization assumptions so that a reader can see what the evidence actually addresses.

For focused public vocabulary, see LJP’s NTN Spectrum Coexistence, Supplemental Spectrum, and Supplemental Coverage from Space reference pages. Those pages are reference explanations, not authorizations or operating-service claims.

Naming practice

Why distinguish a brand from a technical working name?

Direct answer: a brand, a technical label, and a domain name can each do different work. In LJP’s view, a plainly labeled domain can be a stable place to explain a term and link the primary sources that define or constrain it. That practical role does not give the domain owner ownership of the term, regulatory authority, or control over a network.

For example, RFC 9460 specifies SVCB and HTTPS DNS resource records for service binding and endpoint information. It is useful when discussing how a client can learn connection information for a network service. It is not authority for satellite terminology, domain ownership, or a naming claim. Keeping that boundary explicit helps a public glossary stay useful without borrowing authority from an unrelated technical specification.

LJP’s view: write the source name beside the working name. If a label comes from a regulator or standards body, link that source. If it is descriptive framing, say so. This makes it easier for readers to decide which wording belongs in a technical document, a regulatory filing, or a public explanation.

Practical use

What can marketing teams use from this?

Direct answer: a marketing team can use a source-linked glossary to avoid turning a broad phrase into an unsupported promise. Start by asking: which term is being used, who defines it, what scope does that definition have, and is the reader being shown a regulatory, architectural, or descriptive claim?

Keep a short definition next to its primary source. State whether a reference is adopted, proposed, or descriptive. Preserve the distinction between what an organization publishes today and what an external authority defines. Finally, assign responsibility for keeping the glossary current. These are communication practices, not certification or a substitute for legal, technical, or regulatory review.

Engineering use

What can engineering teams use from this?

Direct answer: engineers can turn vague labels into explicit interface and evidence questions. Service links and feeder links are concrete examples: one concerns the relationship to user equipment, the other the relationship to a ground gateway. Transparent and regenerative payloads are also architectural distinctions; they should be documented with the source and assumptions relevant to the system under review.

An evidence-linked glossary can name the interface or specification vocabulary used by a project, explain what each term does not establish, and point to the governing document. It should not imply that a general public page proves an end-to-end design, a radio result, permission to operate, or an available service. The 3GPP NTN overview and TR 38.821 record are the architectural starting points used here.

LJP reference names

Why consider LJP's reference names?

Direct answer: LJP owns 13 domain names that each already have a plain-language page explaining one term used in satellite-to-phone discussions, with the FCC or 3GPP source linked where one exists. A team that wants a ready, neutral starting point for its glossary, specifications or public explanations may reduce foundational naming and definition work by discussing a transfer or license with LJP, individually or together. LJP owns the domain names, not the terms.

What a team receives

  • Defined pages: each name has a published page explaining its term, with primary-source links where available.
  • A coordinated set: the names cover the service framework, link architecture, spectrum questions, resilience, and positioning and timing context in one consistent presentation.
  • Neutral and transferable: the names are held outside any single carrier, vendor or venture, and are available for discussion of transfer, assignment or license.
  • Infrastructure choice: the reference names do not require adoption of an LJP-operated communications service; a team can choose the infrastructure for its intended use.

The 13 names are presented together:

  • supplementalcoveragefromspace.com
  • unifiedntn.com
  • satellite2cell.com
  • ntnservicelink.com
  • ntnfeederlink.com
  • leoorchestration.com
  • ntnintegrity.com
  • resilientntn.com
  • ntnspectrumcoexistence.com
  • multioperatorspectrumpooling.com
  • supplementalspectrum.com
  • sovereignpnt.com
  • assuredtiming.com

Related material: see the 13-domain overview, which lists each name with its role and source.

Contact

How can I reach LJP?

Direct answer: email [email protected].

An invitation to talk, not a binding offer. Ownership verification is available on request.

Primary sources used in this guide