Type Length Instance Value

Description

Type Length Instance Value (TLIV) is a data encoding format that extends the common Type-Length-Value (TLV) scheme by incorporating an Instance field. It is extensively used within 3GPP protocols, most notably in the Information Elements (IEs) of the GPRS Tunneling Protocol (GTP) for both control (GTP-C) and user plane (GTP-U). Each TLIV-encoded IE consists of four consecutive fields. The Type field (1 or 2 octets) identifies the kind of information being carried (e.g., an IMSI, a QoS profile, or a TEID). The Length field (2 octets) specifies the total length in octets of the subsequent Instance and Value fields. The critical addition is the Instance field (1 octet), which acts as a discriminator. This allows multiple IEs of the same Type to be included in a single protocol message without ambiguity. For example, a GTP-C message could contain several Bearer Context IEs (same Type) for different bearers, each distinguished by a unique Instance value. Finally, the Value field contains the actual payload data, whose structure is defined by the specific IE's specification. The TLIV format provides a self-describing and flexible framework. Protocol decoders can parse messages by reading the Type, skipping forward based on the Length if the Type is unrecognized (ensuring backward compatibility), and correctly associating multiple instances of data. The encoding is byte-aligned and used for both mandatory and optional IEs. Its design is central to the extensibility of 3GPP core network signaling, allowing new IEs to be added in later releases without breaking existing implementations that can simply ignore unknown Types.

Purpose & Motivation

The TLIV format was created to address the need for a robust, extensible, and unambiguous encoding scheme for complex protocol signaling in mobile core networks. Simple TLV encoding can handle basic data, but control plane messages often require multiple instances of the same information type (e.g., multiple QoS profiles for a session). Without an Instance field, distinguishing these multiple occurrences would require complex and inefficient workarounds. The TLIV structure solves this by providing a clean, standardized way to pack and unpack nested or repeated information elements. Its introduction, particularly with GTP, provided a future-proof foundation for the Evolved Packet Core (EPC) and 5G Core (5GC) interfaces. As services evolved from basic GPRS to complex 5G network slicing and edge computing, hundreds of new IEs have been defined. The TLIV format ensures that new network functions can introduce new IE Types, and legacy nodes can safely ignore them by using the Length field to skip over the unknown data. This backward compatibility was crucial for the gradual, multi-vendor rollout of new 3GPP features across global networks.

Key Features

• Four-field structure: Type, Length, Instance, Value
• Instance field enables multiple IEs of identical Type within a single message
• Self-describing format allows for backward and forward compatibility
• Extensively used in GTP-C and GTP-U for EPC and 5GC interfaces
• Length field enables parsers to skip unknown IE types safely
• Standardized octet-aligned encoding for reliable cross-vendor interoperability

Evolution Across Releases

Defining Specifications