Store and Forward Data Retention Period

Description

The S&F (Store and Forward) data retention period is a key parameter defined for 5G systems with satellite access that support store-and-forward operation. In such systems, a serving satellite may not always have a simultaneous connection to the ground network via a feeder link or inter-satellite link (ISL). During these disconnected periods, the satellite stores user data on-board and forwards it once connectivity to the ground network is re-established. The data retention period defines how long this stored data remains valid and is retained before being discarded.

Architecturally, the S&F data retention period operates at the intersection of the 5G core network, the satellite access network, and the UE. When a UE transmits uplink data or receives downlink data while the satellite lacks a feeder link, the data is buffered on-board. The retention period acts as a timer or validity window: if the data cannot be delivered to its destination (the ground network for UL, or the UE for DL) within this period, it is deleted. This prevents stale data from accumulating and consuming limited on-board storage resources.

The parameter is particularly important for non-terrestrial network (NTN) deployments where satellite visibility and feeder link availability are intermittent. It must be carefully dimensioned to balance delivery success probability against storage capacity constraints. A retention period that is too short may cause legitimate data to be discarded before a forwarding opportunity arises; one that is too long may exhaust on-board memory and delay the delivery of newer, more time-critical data.

From a protocol perspective, the retention period influences scheduling, buffer management, and QoS handling in the satellite payload. It interacts with 3GPP QoS mechanisms such as the 5QI (5G QoS Identifier) and may be configured per QoS flow or per UE. The period is specified in 3GPP TS 22.261 (Service requirements for the 5G system) and TS 22.865 (Study on satellite access Phase 3), which define the service-level requirements for store-and-forward operation.

In Rel-19, the definition was introduced as "the data storage validity period for the 5G system with satellite access supporting store and forward operation (e.g. after which undelivered data stored is being discarded)." In Rel-20, the wording was refined to "the data storage validity period for a 5G system with satellite access supporting store and forward operation (e.g. after which undelivered data stored is being discarded)," changing the article from "the" to "a" to generalize the definition. This subtle editorial change reflects the maturation of the concept from a specific system reference to a generic system property.

Purpose & Motivation

The S&F data retention period exists to address a fundamental challenge in satellite-based 5G networks: intermittent connectivity between the satellite and the ground network. Unlike terrestrial base stations that maintain continuous backhaul connectivity, satellites in low Earth orbit (LEO) or medium Earth orbit (MEO) may experience periods where no feeder link or inter-satellite link is available. Without a defined retention period, data stored on-board during these gaps could either be discarded too early (causing service failures) or retained indefinitely (exhausting storage and causing buffer overflow).

Prior to the introduction of store-and-forward operation in 3GPP Release 19, satellite access in 5G assumed continuous or near-continuous feeder link availability, which limited coverage to areas with ground station infrastructure. The store-and-forward paradigm removes this limitation by allowing the satellite to autonomously buffer data and deliver it later, but it introduces the need for a validity period to manage on-board storage. The retention period solves this by providing a deterministic rule for when undelivered data must be discarded.

This parameter is essential for enabling global IoT coverage, emergency communications, and maritime or aeronautical services where ground infrastructure is sparse. It allows network operators to trade off storage capacity, delivery latency, and service reliability in a controlled manner, and it supports regulatory requirements for data handling in disconnected scenarios.