Description
The Terminal End-point Identifier (TEI) is a fundamental addressing element defined within the 3GPP TS 52.021 specification, which details the Terminal Adaptation Function (TAF) for 3GPP GSM/UMTS networks. The TEI operates within the context of the TAF, which is responsible for adapting data streams from terminal equipment (TE) for transmission over the mobile network, often involving protocols like V.xx series for circuit-switched data services. Architecturally, the TEI is assigned to each logical end-point or data session initiated by the Terminal Equipment. It functions as a local identifier within the data link layer (specifically within the LAP-family protocols adapted by the TAF), allowing the network to multiplex and demultiplex data streams belonging to different applications or sessions originating from the same physical terminal.
In operation, when a data call is established, the network assigns a TEI to the specific end-point. This identifier is then used in all subsequent data frames exchanged between the mobile station and the network's Interworking Function (IWF). The TEI is crucial for frame delineation and correct delivery, ensuring that data intended for one application (e.g., a fax session) is not mistakenly delivered to another (e.g., a modem session) sharing the same physical radio resource. Its role is analogous to Data Link Connection Identifiers (DLCIs) in Frame Relay or Virtual Channel Identifiers (VCIs) in ATM, providing a layer 2 addressing mechanism for virtual circuits.
The TEI's management involves assignment, verification, and release procedures coordinated between the terminal and the network. It is a key component in the reliable transfer of non-voice data over legacy circuit-switched domains, supporting services like fax, circuit-switched data, and early mobile internet access. While its prominence has diminished with the dominance of packet-switched IP networks in 4G and 5G, understanding TEI is essential for comprehending the evolution of mobile data services and the interworking between traditional telecom protocols and mobile systems.
Purpose & Motivation
The TEI was created to solve the fundamental problem of supporting multiple, simultaneous data sessions or logical channels from a single piece of terminal equipment over a single physical connection to the GSM/UMTS network. Prior to standardized mobile data adaptation, connecting data terminals (like laptops with modems) to mobile networks was proprietary and inefficient. The Terminal Adaptation Function (TAF), and by extension the TEI, provided a standardized way to adapt the data streams from various terminal equipment types (using interfaces like V.24/V.28) to the protocols used over the air interface.
The primary motivation was to enable robust circuit-switched data services, such as fax and dial-up internet, in the 2G and 3G eras. Without a unique end-point identifier like the TEI, the network would be unable to distinguish between different data streams multiplexed over the same radio channel, leading to data corruption and an inability to support multiple applications concurrently. The TEI thus addressed the limitation of having only a single, undifferentiated bearer for data, allowing for logical channel separation and proper session management within the constraints of circuit-switched technology.
Key Features
- Unique identification of logical end-points within a terminal
- Enables multiplexing of multiple data sessions over a single physical connection
- Operates within the Data Link Layer (Layer 2) of the protocol stack
- Essential for the Terminal Adaptation Function (TAF) defined in TS 52.021
- Supports circuit-switched data services like fax and modem calls
- Facilitates correct routing of data frames between terminal and network interworking function
Evolution Across Releases
Introduced as part of the consolidated specifications for GSM/UMTS. The TEI was defined within TS 52.021 as the identifier for the Terminal Adaptation Function, establishing its role in uniquely identifying terminal end-points for data session management in circuit-switched domains. Its architecture was carried forward from earlier GSM specifications to support legacy data services within the 3GPP framework.
Defining Specifications
| Specification | Title |
|---|---|
| TS 52.021 | 3GPP TR 52.021 |