Transfer Interval

Description

Transfer Interval is a term introduced in 3GPP Release 19 to describe the time difference between two consecutive transfers of application data from an application, through the service interface, to the 3GPP system. This concept is particularly relevant in the context of industrial automation, Time-Sensitive Networking (TSN), and deterministic networking, where precise timing and periodicity of data transfers are essential for correct system operation. The transfer interval defines the periodicity at which an application generates and sends data to the network, and it directly influences the network's configuration to meet the application's latency and reliability requirements.

The transfer interval is a key parameter in the characterization of industrial IoT use cases and applications. In industrial environments, various types of traffic exist, ranging from cyclic control data with very short intervals (e.g., 1 ms or even 250 μs for motion control) to less frequent monitoring data (e.g., 1 s or longer for process monitoring). The 3GPP system must be configured to handle these diverse requirements, and the transfer interval serves as a primary input for network dimensioning and resource allocation. For example, a shorter transfer interval requires more frequent scheduling opportunities, more frequent reference signals for channel estimation, and potentially more stringent synchronization requirements.

The concept of transfer interval is closely related to other timing parameters in 3GPP specifications. The communication service availability is often specified as a percentage, indicating the proportion of transfer intervals in which the application data is delivered successfully within the required latency bound. The end-to-end latency is typically defined as the time from the generation of the application data at the sender to the successful delivery at the receiver, and it must be less than the transfer interval for the system to be able to keep up with the data generation rate. The jitter, or variation in latency, is also important, especially for cyclic traffic where the receiver expects data at regular intervals.

In the context of 5G and beyond, the Ultra-Reliable Low-Latency Communication (URLLC) service category is designed to support applications with very short transfer intervals. The 5G system supports configurable numerology, with subcarrier spacings from 15 kHz to 960 kHz, enabling slot durations from 1 ms down to approximately 15.6 μs at the highest numerology. This flexibility allows the network to schedule transmissions at intervals that match the application's transfer interval. Additionally, features like configured grant (CG) and semi-persistent scheduling (SPS) are used to provide periodic transmission opportunities without the overhead of dynamic scheduling, which is particularly beneficial for applications with deterministic transfer intervals.

The introduction of the Transfer Interval definition in Release 19 reflects the ongoing evolution of 3GPP towards supporting industrial IoT and time-sensitive applications. Previous releases (Rel-15, Rel-16, Rel-17) laid the groundwork for URLLC and TSN integration, but the precise definition of transfer interval in Release 19 provides a standardized vocabulary for describing application requirements. Specifications 22.104 (Service requirements for cyber-physical control applications in vertical domains) and 22.289 (Service requirements for mobile communication systems for railway applications) provide the context for this term, illustrating its importance in industrial and transportation verticals. The transfer interval is used in conjunction with other parameters like communication service availability and end-to-end latency to fully characterize the QoS requirements of an application.

Purpose & Motivation

The Transfer Interval concept was created to provide a standardized way to describe the temporal characteristics of application data in industrial IoT and time-sensitive networking scenarios. Before this definition, various terms like 'cycle time,' 'update time,' or 'sampling period' were used in different contexts, leading to potential confusion. By standardizing the term in 3GPP specifications, it becomes possible for network operators, application developers, and equipment vendors to communicate requirements precisely and consistently.

The primary problem that the Transfer Interval addresses is the need for deterministic communication in industrial environments. Traditional mobile networks were designed for human-centric communication (voice, video, web browsing) where occasional latency variations are acceptable. However, industrial control applications, such as motion control in manufacturing robots or fault detection in power grids, require data to be transferred at precise, regular intervals. A deviation from the expected transfer interval can lead to control loop instability, production errors, or even safety hazards. By defining the transfer interval as a formal parameter, 3GPP enables the network to be configured and optimized for these deterministic requirements.

Furthermore, the Transfer Interval is essential for the integration of 5G with Time-Sensitive Networking (TSN) standards defined by IEEE 802.1. TSN uses the concept of a 'cycle time' for scheduled traffic, and the 3GPP transfer interval must be aligned with the TSN cycle time for seamless interworking. This alignment ensures that the 5G system can act as a TSN bridge, providing transparent transport for time-sensitive traffic between wired TSN segments. The definition in Release 19 thus supports the broader goal of making 5G a viable technology for Industry 4.0 and other vertical domains where deterministic networking is a prerequisite.