TE

Terminal Equipment

Other →
Introduced in R99 Also in: Services, User Equipment

TE is the end-user device, such as a computer or smartphone, that utilizes a Mobile Termination unit to connect to a mobile network and is responsible for generating, processing, and terminating the user's data stream.

Category
Other
Introduced
R99
Where
Core Network › Legacy Core
Also touches
2 segments
Specifications
17 specs
TE Description Purpose Detected Changes Specifications

Description

Terminal Equipment (TE) is a fundamental concept in 3GPP architectures, representing the endpoint that originates or terminates information flows. It is the user-side equipment that contains the functions for communication with a correspondent node. In the context of mobile networks, the TE does not contain the specific radio modem functions for accessing the cellular network; those are housed in a separate functional entity called the Mobile Termination (MT). The TE connects to the MT via a standardized interface, such as those defined by 3GPP or other bodies like ETSI or ITU-T. This separation allows for flexibility, enabling different types of TEs (e.g., laptops, IoT sensors, payment terminals) to connect to the network through a common MT device, such as a cellular dongle or a smartphone acting as a hotspot.

Architecturally, the TE is part of the Terminal Equipment - Mobile Termination (TE-MT) model. The TE is responsible for the user application layers (Layer 7 and above in the OSI model), handling tasks like web browsing, email clients, or sensor data processing. It communicates with the MT using a Terminal Adaptation (TA) function, which adapts the TE's data streams to the protocols understood by the MT for transmission over the radio interface. The MT, in turn, handles all the lower-layer protocols specific to the radio access network (RAN), including radio resource control, mobility management, and link-layer security.

The role of the TE is defined across numerous 3GPP specifications covering service aspects, architecture, and protocols. For instance, specifications detail how a TE establishes a data connection through the MT, how quality of service (QoS) parameters are negotiated, and how specific AT commands (standardized in 3GPP TS 27.007) can be used to control the MT from the TE. This clear functional separation is crucial for device certification, network interoperability, and the development of a vast ecosystem of user equipment that can leverage evolving cellular technologies without each TE needing integrated radio hardware.

Purpose & Motivation

The concept of Terminal Equipment was formalized to create a clear architectural separation between the user's application device and the network-specific radio communication hardware. This separation addresses the problem of device diversity and technological evolution. Without this model, every end-user device would need to integrate the complex and rapidly changing radio modem technology, increasing cost, size, and power consumption, and making it difficult to upgrade the radio technology independently of the application device.

Historically, this model draws from the Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) concepts in fixed-line data communications (e.g., modems). In the mobile context, it allows for modularity. A single, certified MT module (like a USB dongle or embedded chipset) can provide network access for a wide variety of TEs. This was particularly important in the early days of mobile data (GPRS, UMTS) where integrating radios into laptops was impractical. The model remains relevant for IoT, where a simple sensor (TE) can connect via a low-power cellular module (MT). It standardizes the interface, ensuring that any compliant TE can work with any compliant MT, fostering a competitive and interoperable market.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change

In Release 16, a new capability was introduced for the Terminal Equipment (TE) to be informed by the User Equipment (UE) about its attachment status for a specific service. Specifically, the TE can now receive an indication of whether the UE is EPS attached for access to RLOS. This enhancement provides the TE, a distinct functional entity within the Mobile Equipment, with greater awareness of the core network attachment state relevant to its operations.

  • Indicating to the TE whether the UE is EPS attached for access to RLOS TS 27.007CR0652
Rel-17 1 change

In Release 17, a key enhancement for Terminal Equipment involved a refinement of the IMS Credentials (IMC) specifically for terminals accessing IMS via Standalone Non-Public Networks (SNPN). This update provided a clearer and more precise definition of the IMC, which is the security data set used by terminals for IMS access in these SNPN scenarios. The correction ensured proper technical alignment for terminals that do not support traditional 3GPP access technologies when connecting via an SNPN.

  • Correction of IMC definition for terminals accessing IMS via SNPN TS 21.905CR0122

Explore further

Broader topics and technologies where TE plays a role.

Defining Specifications

3GPP specifications that define or reference TE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 22.944 vj00 UE Functionality Split Scenarios and Requirements Rel-19
TS 23.050 v1100 UMTS Network Principles and Architecture R99
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19
TS 23.101 vj00 UMTS Architecture and Functional Separation Rel-19
TS 23.107 vj00 UMTS QoS Framework Rel-19
TS 23.146 vj00 3G Facsimile Group 3 Technical Realization Rel-19
TS 23.207 vj00 End-to-End QoS Framework for GPRS Rel-19
TR 23.923 v1300 Mobile IP+ Feasibility Study for UMTS/GPRS Rel-4
TS 24.523 vj00 NGCN-NGN Interconnection Scenarios Rel-19
TS 27.007 vj40 AT Command Set for UE Rel-19
TS 27.060 vj00 TE-MT Interworking for Packet Domain Rel-19
TS 29.007 vj00 PLMN-PSTN/ISDN Interworking Requirements Rel-19
TS 29.061 vj00 Packet Domain Interworking for PLMN Rel-19
TS 31.121 vi50 UICC-terminal interface test specification Rel-18
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19
TR 38.825 vg00 Study on NR Industrial IoT Rel-16