Information Element Identifier

Description

The Information Element Identifier (IEI) is a critical component in the encoding of 3GPP protocol layer messages. It is a field, typically one or two octets in length, placed at the beginning of an Information Element (IE) within a protocol data unit (PDU). An Information Element is a container for a specific piece of data, such as a cause code, a timer value, an identity, or a complex nested structure. The IEI acts as a unique key or tag that tells the receiving entity what type of data follows, how it should be parsed, and what its semantic meaning is within the context of the specific protocol.

In operation, when a network function (e.g., an AMF or MME) constructs a protocol message like a NAS (Non-Access Stratum) message or an RRC (Radio Resource Control) message, it assembles a series of IEs. Each IE starts with its IEI. The receiver, which has a protocol specification defining all valid IEIs and their corresponding data structures, reads the IEI and uses it as a lookup key. This tells the receiver the format (e.g., length of the IE content, value type like integer or octet string, and whether it is mandatory or optional) and the meaning of the subsequent bits. This mechanism allows for flexible and extensible protocol design; new IEs can be defined with new IEIs in later protocol releases without breaking backward compatibility, as older receivers can simply ignore IEIs they do not understand (if the IE is defined as optional).

The IEI is defined per protocol and is context-sensitive. For example, the IEI value 0x57 might represent a "5GMM Cause" IE in a 5G NAS message, but a completely different IE in a Diameter protocol message. The definitions are meticulously catalogued in 3GPP specifications. TS 24.008 (for NAS) and TS 36.331 (for RRC) are examples of specs that define IEI tables. The listed specs like 24.244 (3GPP TS 24.244 - Wireless LAN control protocol) and 31.102 (Characteristics of the USIM application) also define IEIs for their respective protocols. The IEI system is foundational to the Abstract Syntax Notation One (ASN.1) or other encoding rules used by 3GPP, enabling efficient binary communication between network nodes and the UE.

Purpose & Motivation

The IEI exists to solve the problem of how to structure complex, variable-length, and extensible protocol messages in a efficient and unambiguous way. In telecommunications, protocols must carry a wide variety of information types and must evolve over time to support new features. Without a tagging mechanism like the IEI, protocols would rely on fixed, positional fields, which are inflexible and make adding new parameters difficult without breaking existing implementations. The IEI allows for a TLV (Type-Length-Value) or similar structure, where the 'Type' is the IEI.

Historically, as 3GPP systems evolved from GSM to 5G, the number of parameters and message types grew exponentially. The IEI mechanism, established early in 3GPP standardization (Release 4 and earlier), provided a scalable solution. It addresses the limitation of rigid message formats by allowing IEs to be included or omitted as needed, to appear in any order, and for new IEs to be introduced seamlessly. This is essential for supporting optional features, vendor-specific extensions (within defined ranges), and for efficient encoding where only relevant information is transmitted. The motivation is to ensure robust interoperability between equipment from different vendors and across different generations of the network, as the protocol parser can focus on the IEs it recognizes and safely skip others.

Key Features

• Uniquely identifies the type and format of a following Information Element
• Enables TLV (Type-Length-Value) style encoding in protocol messages
• Allows for extensible protocol design through the addition of new IEIs
• Supports optional and conditional inclusion of parameters
• Context-specific definitions per protocol (e.g., NAS, RRC, Diameter)
• Facilitates backward and forward compatibility in network signaling

Evolution Across Releases

Defining Specifications