Radio Link Protocol

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Radio Link Protocol" – news · newspapers · books · scholar · JSTOR (June 2025) (Learn how and when to remove this message)

Radio Link Protocol (RLP) is an automatic repeat request (ARQ) fragmentation protocol used over a wireless (typically cellular) air interface.^[1] RLP occurs on the data link layer (Layer 2) of the OSI networking model.^[2]

Most wireless air interfaces are tuned to provide 1% packet loss, and most vocoders are mutually tuned to sacrifice very little voice quality at 1% packet loss. However, 1% packet loss is intolerable to all variants of TCP, and so something must be done to improve reliability for voice networks carrying TCP/IP data. A RLP detects packet losses and performs retransmissions to bring packet loss down to approximately .01%, or even .0001%, which is suitable for TCP/IP applications. When the receiver detects a missed packet, it sends a NAK (not acknowledged) frame to the sender, which triggers a retransmission of the missing packet. At the same time, the receiver sets a timer for receipt of the missing packet. Each time the timer expires without receipt of the packet, the receiver resets the timer and sends NAK a number of times equal to 1 + the number of times the timer has already expired, up to a limit.^[3]

RLP also implements stream fragmentation and reassembly, and sometimes, in-order delivery. Some forms of RLP rely upon a higher-layer PPP protocol to provide these functions,^[4] while newer forms of RLP also provide framing and compression.^{[citation needed]}

Because a CDMA IS-95 network's smallest voice packet size (and thus an RLP packet length) can be as little as 88 bits (11 bytes),^[5] RLP headers must be very small, to minimize overhead. This is typically achieved by allowing both ends to negotiate a variable 'sequence number space', which is used to number each byte in the transmission stream.^[4] In some variants of RLP, this sequence counter can be as small as 6 bits

A RLP transport cannot ask the air interface to provide a certain payload size. Instead, the air interface scheduler determines the packet size, based upon constantly changing channel conditions, and upcalls RLP with the chosen packet payload size, right before transmission. Most other fragmentation protocols, such as those of 802.11b and IP, used payload sizes determined by the upper layers, and call upon the MAC to create a payload of a certain size. These other protocols are not as flexible as RLP and can sometimes fail to transmit during a deep fade in a wireless environment.^{[citation needed]}

A RLP protocol can be ACK-based or NAK-based.^{[citation needed]} Most RLPs are NAK-based, meaning that forward-link sender assumes that each transmission got through, and the receiver only NAKs when an out-of-order segment is received. This greatly reduces reverse-link transmissions, which are spectrally inefficient and have a longer latency on most cellular networks. When the transmit pipeline goes idle, a NAK-based RLP must eventually retransmit the last segment a second time, in case the last fragment was lost, to reach a .01% packet loss rate. This duplicate transmission is typically controlled by a "flush timer" set to expire 200-500 milliseconds after the channel goes idle.^{[citation needed]}

The concept of a RLP protocol was invented by Phil Karn with Qualcomm in 1993^[4] for CDMA (IS-95) networks. The January 2006 IEEE 802.20 specification uses a form of RLP.^{[citation needed]}

Cellular networks such as GSM and CDMA use different variations of RLP. In UMTS and in LTE, the protocol is called RLC (Radio Link Control).^[6]

This computer networking article is a stub. You can help Wikipedia by expanding it.

• v
• t
• e

This article about wireless technology is a stub. You can help Wikipedia by expanding it.

• v
• t
• e