Description
A Trusted Execution Environment (TEE) is a secure, isolated area of a processor — typically on a device or within a network function — in which sensitive code and data can be executed and stored with strong guarantees of confidentiality and integrity, even if the main operating system or applications are compromised. The TEE runs alongside the Rich Execution Environment (REE), which hosts the normal operating system and applications, but is separated from it by hardware-enforced isolation. This isolation ensures that secrets such as cryptographic keys, credentials, and biometric data never appear in the REE's memory space and cannot be read or modified by REE software, including malware.
In 3GPP Rel-19, the TEE concept is introduced into media-related specifications, notably TS 26.804 and TS 26.813, which deal with media handling, codec security, and related trust frameworks. The motivation is that modern media services — real-time video, immersive media, and content protection — increasingly require that decryption keys, watermarking logic, and identity credentials be processed in an environment that the content owner and the user can both trust. A TEE provides this anchor of trust: media decryption and rendering of protected content can occur inside the TEE so that keys are never exposed to the general-purpose OS, and attestation mechanisms can prove to a remote party that the TEE is genuine and running approved code.
Architecturally, a TEE is built on hardware security features such as ARM TrustZone, dedicated secure processors, or similar isolation technologies. It exposes a limited, well-defined interface to the REE through which applications can request specific trusted services without gaining access to the TEE's internal state. The TEE typically hosts a small trusted OS and a set of trusted applications (TAs), each providing a specific security service. Remote attestation allows a relying party — for example, a media server or an identity provider — to verify the integrity of the TEE and the trusted application before releasing keys or sensitive data.
Within 3GPP's media and security work, the TEE complements other security mechanisms such as the UICC/eSIM for identity and key storage, and the secure element for payment and authentication. Whereas the UICC is optimized for network access credentials, the TEE is a general-purpose secure compute environment capable of running richer logic, such as media decryption pipelines, digital rights management agents, and privacy-preserving processing. The Rel-19 specifications examine how TEE capabilities can be leveraged for media security, including the interfaces and trust assumptions needed for interoperability across devices and vendors.
The introduction of TEE into 3GPP specifications reflects a broader industry trend toward hardware-rooted security for services that run over mobile networks. As 5G and future networks carry more sensitive media and data, and as regulatory requirements for privacy and content protection tighten, the TEE provides a standardized, auditable foundation for protecting those assets on devices that are otherwise open, general-purpose computing platforms.
Purpose & Motivation
The TEE concept exists because general-purpose operating systems on devices and servers cannot be trusted to protect high-value secrets. Mobile devices run large, complex software stacks with broad attack surfaces; if decryption keys, identity credentials, or media content are handled in the normal OS, a single vulnerability can expose them. The TEE solves this by providing a hardware-isolated environment where sensitive operations occur, with strong assurance that even a fully compromised REE cannot access the protected data.
In the 3GPP context, the motivation for introducing TEE in Rel-19 is the growing security demands of media services. Protected content distribution, real-time media encryption, watermarking, and privacy-sensitive processing all require a trust anchor on the device that content owners, service providers, and users can rely on. Previous approaches relied on secure elements such as the UICC, which are excellent for network credentials but limited in compute capability and flexibility for rich media processing. The TEE fills this gap by offering a programmable secure environment.
Standardizing TEE usage in 3GPP specifications (TS 26.804, TS 26.813) ensures that different vendors and operators share common assumptions about trust, attestation, and interfaces, enabling interoperable media security solutions across the 5G ecosystem. It also aligns 3GPP work with broader industry frameworks for confidential computing and hardware-rooted security.
What changed in its specifications
The latest release-to-release comparison of specifications that define TEE. Each summary describes the whole specification, not only this term.
Rel-19 adds CMCD reporting, multi-source media delivery, content steering, QoS enhancements, and QUIC-based streaming.
Full comparison in TS 26.804 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference TEE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 26.813 vk00 | Avatar Representation and Communication | Rel-20 read |