Format Identifier

Description

The Format Identifier (FI) is a crucial field within protocol headers in 3GPP specifications, primarily used in the Packet Data Convergence Protocol (PDCP) and Medium Access Control (MAC) layers to signal the format of the associated protocol data unit (PDU). It is a few bits long (e.g., 2 bits in PDCP for LTE/NR) that explicitly defines how the remaining bits of the header and payload should be parsed. For instance, in PDCP data PDUs, the FI indicates whether the PDU contains a sequence number, whether robust header compression (ROHC) context is present, and the length of any additional fields. This allows a single protocol entity to support multiple PDU formats dynamically, adapting to different service requirements like control plane signaling, user plane data, or header-compressed IP packets.

Architecturally, the FI is generated by the transmitting protocol entity (e.g., PDCP transmitter in the UE or gNB) based on the configuration received from higher layers or RRC signaling. In PDCP, specified in 3GPP TS 36.323 and TS 38.323, the FI is part of the PDCP PDU header, which also includes fields like the PDCP sequence number (SN) and data. The receiving entity examines the FI bits first to determine the header structure before attempting to decompress or decipher the payload. In MAC, as per TS 36.321 and TS 38.321, FI-like indicators (e.g., subheader formats) identify the presence and size of logical channel IDs (LCIDs), length fields, and padding, enabling the multiplexing of multiple MAC service data units (SDUs) into a single transport block.

The operation involves the transmitter setting the FI according to the PDU type: for example, '00' might indicate a PDCP data PDU with a 12-bit SN and no ROHC feedback, while '01' could indicate a PDU with a 7-bit SN and an ROHC feedback field. The receiver uses a finite-state machine or lookup table, as defined in the specification, to interpret the FI and extract the correct fields. This mechanism is key to efficient use of radio resources because it avoids transmitting fixed-length headers for all PDUs, instead using minimal overhead tailored to the specific context. It also ensures backward and forward compatibility, as new FI values can be defined in later releases to introduce new PDU formats without breaking existing implementations.

Purpose & Motivation

The Format Identifier was introduced to address the need for flexible and efficient protocol data unit formatting in evolving 3GPP systems. Early cellular protocols often used fixed PDU structures, which led to unnecessary overhead when certain fields (like large sequence numbers or compression contexts) were not needed for all types of traffic. With the advent of LTE in Release 8, which supported diverse services from voice over IP (VoIP) to high-speed internet, a more adaptive header structure became necessary to optimize radio resource usage and reduce latency.

The primary problem FI solves is the efficient multiplexing and processing of heterogeneous data flows within the same protocol layer. For example, in PDCP, some packets may require robust header compression (ROHC) to minimize IP header overhead, while others (like control signaling) do not. Without an FI, the receiver would need to blindly attempt multiple parsing methods, increasing complexity and error probability. The FI provides explicit signaling, enabling the receiver to correctly and quickly process each PDU, which is critical for low-latency services and battery-efficient device operation.

Historically, FI builds on concepts from earlier telecom and internet protocols (like the Type field in Ethernet) but is tailored for the unique constraints of wireless links. It addressed limitations in pre-LTE systems where protocol overhead was less optimized, contributing to lower spectral efficiency. In LTE and 5G NR, the FI enables advanced features like duplication (for reliability), integrity protection, and efficient support for small data packets in IoT, by allowing distinct PDU formats for each use case. Its design allows 3GPP to evolve protocols across releases while maintaining interoperability, as devices can ignore unknown FI values or handle them gracefully through predefined rules.

Key Features

• Explicitly indicates the structure and field lengths of protocol data units (PDUs)
• Enables support for multiple PDU formats within a single protocol entity (e.g., PDCP, MAC)
• Reduces header overhead by allowing variable-length fields based on context
• Facilitates correct parsing of headers for robust header compression (ROHC) and sequence numbering
• Supports dynamic adaptation to different service types (e.g., control plane, user plane, IoT data)
• Ensures forward compatibility by allowing definition of new format values in future releases

Evolution Across Releases

Defining Specifications