Session Continuity
Definition
The application- and user-level outcome of maintaining an active call, data session, or control link without perceptible interruption as a device moves between cells, satellites, beams, or connectivity paths, evaluated by the end-user experience a mobility event produces rather than by whether the underlying mobility procedure itself technically completed.
Key Points
- Represents the end-user-visible outcome that lower-layer mobility mechanisms — handover, relay hand-off, beam transitions — are specifically designed to preserve, rather than being a mechanism itself
- A technically successful handover that nonetheless introduces a perceptible glitch, dropped packet burst, or brief application-level interruption still represents a session continuity shortfall, even though the underlying mobility procedure completed
- Particularly consequential for real-time and safety-relevant applications — a voice call, a remote equipment control link, a live video feed — where even a brief interruption has a materially different consequence than the same interruption in a bulk data transfer
- For mobile NTN use cases specifically, session continuity depends on handover mechanisms succeeding reliably across satellite passes, beam transitions, or constellation hand-offs, making handover success rate a direct proxy for achieved session continuity
- Where handover alone cannot maintain a connection — a device moving into a coverage gap no single cell or beam serves — relay mechanisms can extend effective coverage and preserve session continuity that would otherwise be lost entirely
Concept
Handover, beam transition, and relay hand-off are all engineering mechanisms operating below the application layer, each designed to move a device's active connection from one serving cell, beam, or path to another without the application or user needing to restart or notice the transition. Session continuity is the measure of how well that goal is actually achieved from the perspective sitting above those mechanisms — a technically completed handover that still produces a noticeable application-level glitch represents a partial session continuity failure, even if the underlying procedure itself would be logged as successful.
Explainer
The distinction between "the mobility mechanism worked" and "the user's session continued smoothly" matters because these two things can diverge in practice — a handover that completes within its allotted timing budget can still introduce enough latency or packet loss during the transition to be perceptible in a sensitive real-time application, even though the handover itself succeeded by its own technical definition. This is precisely why this corpus's NTN handover material treats handover success rate as a proxy for session continuity rather than treating the two as synonymous: the metric is useful specifically because it correlates with, but doesn't perfectly capture, the actual end-user experience session continuity is meant to describe. For CE verticals operating latency- or safety-sensitive mobile connectivity — remote equipment control from a moving vessel or vehicle, live monitoring feeds during transit through NTN coverage, voice communication for field personnel moving between coverage zones — session continuity, not just handover completion statistics, is the outcome that should ultimately determine whether a given connectivity architecture is fit for the specific operational use case it needs to support.
Cite this entry
Session Continuity. ConnectedEarth Knowledge Base. https://connectedearth.space/knowledge-base/session-continuity/ (updated 13 September 2026).