Description
Receive Not Ready (RNR) is a supervisory frame type defined within data link layer protocols, such as those specified in 3GPP for GSM and UMTS networks. It operates as part of the Layer 2 protocol stack, often within the Radio Link Control (RLC) or Link Access Protocol (LAP) frameworks, to manage the flow of data between peer entities. The primary function of an RNR frame is to signal from the receiver to the transmitter that the receiver is temporarily unable to accept new data frames. This condition typically arises due to internal buffer congestion, high processing load, or other temporary limitations that prevent the receiver from handling additional data without risk of overflow or loss.
When a receiver sends an RNR frame, it explicitly instructs the transmitter to halt the transmission of information frames (I-frames). The transmitter, upon receiving the RNR, enters a quiescent state where it stops sending new I-frames but may continue to send supervisory frames like Receiver Ready (RR) or other control signals to maintain the link. The RNR frame includes necessary control information, such as the receiver's sequence number, to identify the context of the communication. This mechanism is crucial in half-duplex or acknowledgment-based protocols to prevent the sender from overwhelming the receiver, thereby avoiding frame discards and retransmissions that would degrade throughput and increase latency.
The RNR condition is typically cleared when the receiver sends a Receiver Ready (RR) frame, indicating it is prepared to resume data reception. In some implementations, a timer may be associated with the RNR state to prevent deadlocks; if the receiver does not send an RR within a specified period, the transmitter might initiate recovery procedures. RNR is integral to the error recovery and flow control procedures defined in specifications like 24.022 (Mobile Station - Base Station System Interface) and 44.064 (General Packet Radio Service; Mobile Station - Serving GPRS Support Node interface). Its role ensures that data link layer protocols can adapt to dynamic network conditions, maintaining reliability and efficiency in wireless communications.
Purpose & Motivation
The Receive Not Ready (RNR) frame type was introduced to address the need for robust flow control in data link layer protocols within 3GPP systems, particularly for GSM and UMTS. Prior to its standardization, simpler protocols might lack explicit mechanisms to handle receiver congestion, leading to data loss, unnecessary retransmissions, and reduced network efficiency when a receiver became temporarily unable to process incoming frames. RNR provides a standardized way for a receiver to signal its status, enabling proactive flow management.
In wireless environments, factors like variable radio conditions, processing delays, and buffer limitations can cause temporary receiver unavailability. Without RNR, a sender might continue transmitting, causing buffer overflows and frame discards, which would trigger retransmission procedures and increase latency. By allowing the receiver to explicitly indicate its not-ready state, RNR helps prevent these issues, optimizing throughput and resource utilization. It is a key component of the acknowledgment-based protocols that ensure reliable data delivery over unreliable radio links.
The creation of RNR was motivated by the evolution toward more complex data services in mobile networks, where efficient flow control became critical for supporting applications like packet-switched data. It addresses limitations of earlier approaches that relied solely on window-based flow control or implicit signaling, which could be less responsive to sudden congestion. RNR enhances the adaptability of the data link layer, contributing to the overall quality of service in 3GPP networks.
Key Features
- Explicit flow control signaling to pause data transmission
- Prevents receiver buffer overflow and data loss
- Integrates with supervisory frame protocols like LAP and RLC
- Includes sequence number for context identification
- Cleared via Receiver Ready (RR) frame to resume communication
- Supports timer-based recovery to avoid deadlocks
Evolution Across Releases
Introduced as a frame type in data link layer protocols for GSM and UMTS, primarily within specifications like 24.022. It provided a standardized mechanism for receivers to signal temporary unavailability, enabling flow control to prevent data loss during congestion. Initial capabilities included integration with existing LAP protocols for reliable data transfer.
Defining Specifications
| Specification | Title |
|---|---|
| TS 24.022 | 3GPP TS 24.022 |
| TS 37.462 | 3GPP TR 37.462 |
| TS 44.064 | 3GPP TR 44.064 |