Architecture / UML
NTN resilience
When the ground network fails, a non-terrestrial path is only useful if you know what still works and what gets worse.
Accepted source 05aaa9aec168 · ACCEPTED_MAIN · simulation
Scenario outputs are simulations. They are not an on-orbit measurement or a satellite service-level agreement. measured_topology is not recorded as true.
Current is shown first. Future and legacy stay labeled. A rendered SVG is used when accepted main already committed one. Otherwise the Mermaid or Markdown source is shown and is not executed in the browser.
- current: Use case — current
- current: Sequence — terrestrial / NTN failover (current)
- future: Future — orbit-accurate visibility
- legacy: Legacy UML index — ntn-resilience-sim
Current
Use case — current
current mermaid
What this diagram shows
UC3[Compare fallback / static / adaptive]
What this diagram does NOT prove
This diagram does not prove an operational satellite network.
Source path docs/uml/current/use_case.md @ 05aaa9aec168
Sequence — terrestrial / NTN failover (current)
current mermaid
What this diagram shows
participant T as Terrestrial link (assumption)
What this diagram does NOT prove
This diagram does not prove an operational satellite network.
Source path docs/uml/current/sequence_failover.md @ 05aaa9aec168
Future
Future — orbit-accurate visibility
future mermaid
What this diagram shows
TLE[Public TLE / ephemeris] --> VIS[Pass windows]
What this diagram does NOT prove
This diagram does not prove an operational satellite network.
Source path docs/uml/future/orbit_accurate.md @ 05aaa9aec168
Legacy
Legacy UML index — ntn-resilience-sim
legacy markdown
What this diagram shows
Legacy UML index — ntn-resilience-sim
What this diagram does NOT prove
This diagram does not prove an operational satellite network.
Source path docs/uml/legacy/index.md @ 05aaa9aec168
gunnchOS