Continuity, degradation, and recovery
Continuity is the ability to sustain or restore an intended function under stated conditions. Degradation describes what remains when part of an arrangement is impaired; recovery describes how the arrangement returns to an intended state. These are related but separate questions.
A resilience discussion identifies the function under review, the operating assumptions, and the dependencies that must be available together. It does not turn a reference label into a coverage or uptime claim.
Redundancy and common dependencies
Redundancy supplies an alternative component or path. It does not by itself establish resilience, because alternatives can share a gateway, power source, ground network, control dependency, location, or administrative boundary.
For an NTN arrangement, the relevant dependencies can include space assets, gateways, ground networks, power, and the integration that connects them. The comparison is between stated alternatives and the dependencies they still share.
Illustrative disruption scenario
Hypothetical example: a reviewer considers an arrangement with two access paths but one gateway region and one ground-network dependency. If the shared dependency is unavailable, the presence of two access paths does not establish continuity. The reviewer then examines the stated recovery sequence and operating assumptions. This is a review example, not a deployed service or measured result.
Evaluation questions and evidence
Dependency question: What space, gateway, ground-network, power, and integration dependencies are identified? Examine architecture and dependency descriptions; they establish the stated scope, not availability.
Recovery question: What disruption, recovery objective, and operating assumptions are stated? Examine recovery plans, exercises, and relevant test results; they establish what was considered under those conditions, not a universal outcome.
Common-exposure question: Which alternatives share a location, power source, gateway, control function, or administrative boundary? Examine topology, responsibility, and dependency records; they establish a reviewable exposure question, not a resilience certification.
Related concepts and terminology
A Service Link can identify a user-facing relationship, while a Feeder Link identifies a gateway-side relationship. Both can be inputs to a continuity review without establishing resilience.
Resilient NTN is LJP descriptive framing. This reference does not provide an emergency service, recovery program, uptime commitment, coverage promise, or compliance determination.
Primary reference material.
- 3GPP — NTN architecture reference
Supports the distinction between access, platform, and gateway-side NTN components used to identify dependencies in this reference.
Public reference resources.
Namespace manifest · Reference summary · Robots policy · Sitemap