Description
The Application Level Container is a Rel-13 concept defined in TS 23.303 (Proximity-based Services, ProSe) and TS 33.303 (Proximity-based Services security aspects). It is defined as an application layer package that is opaque to the 3GPP networks. In other words, it is a data structure whose contents are generated and consumed by applications, while the network treats it as an uninterpreted blob that it forwards or stores without inspecting or modifying the internal structure.
The primary context for the Application Level Container is Proximity-based Services (ProSe). In ProSe, UEs discover each other and communicate directly (device-to-device) or via network paths. Applications running on the UEs may need to exchange application-specific information—such as discovery parameters, service identifiers, or security credentials—that is meaningful only to the applications. The Application Level Container provides a standardized envelope for carrying this information through ProSe procedures (for example, discovery requests and responses) without requiring the network to understand the application semantics. The network elements involved in ProSe, such as the ProSe Function, handle the container as opaque data, ensuring that application-level details remain private and that the network remains application-agnostic.
Security is a key aspect. TS 33.303 specifies the security mechanisms for ProSe, including how the Application Level Container is protected. Because the container is opaque to the network, the security of its contents is typically end-to-end between the applications, using application-layer security mechanisms. The network's role is limited to transporting the container reliably. This separation of concerns—network transports, application secures—is a fundamental design principle that allows ProSe to support a wide range of applications without requiring network upgrades for each new application.
The container is structured to be self-contained, meaning it includes all the information necessary for the receiving application to process it. The exact format of the container is application-specific and outside the scope of 3GPP standardization; 3GPP only defines the envelope and the procedures for carrying it. This flexibility is intentional, enabling innovation at the application layer while maintaining interoperability at the network layer.
Since its introduction in Rel-13, the definition of the Application Level Container has remained unchanged through Rel-19. This stability reflects the enduring utility of the opaque container concept: as long as the network does not need to interpret application data, the container can carry any application payload. The concept has proven valuable not only in ProSe but also as a general pattern for application-transparent data exchange in 3GPP networks, influencing similar constructs in later service exposure and IoT architectures.
Purpose & Motivation
The Application Level Container exists to solve the problem of transporting application-specific data through 3GPP network procedures without requiring the network to understand or process that data. In ProSe and similar services, applications need to exchange information that is meaningful only to them—such as discovery metadata, service parameters, or security material. If the network had to interpret this data, it would need to be updated for every new application, which is impractical and stifles innovation.
By defining the container as opaque to the network, 3GPP achieves a clean separation of concerns: the network provides reliable transport and procedural handling, while applications define and manage the payload. This allows new applications to be deployed without network changes, reduces the risk of network elements mishandling application data, and preserves the privacy of application-level information. It also simplifies interoperability, as the network only needs to support the container envelope, not the myriad possible payloads.
The concept was introduced in Rel-13 alongside ProSe, where device-to-device discovery and communication required a flexible way to carry application data. The Application Level Container provided the necessary abstraction, enabling ProSe to support diverse applications while keeping the network core simple and application-agnostic. Its continued presence through Rel-19 demonstrates the value of this design pattern in evolving network architectures.
What changed in its specifications
The latest release-to-release comparison of specifications that define Application Level Container. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.303: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.303 →Rel-19 brings only minor changes to TS 33.303: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 33.303 →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 Application Level Container, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.303 vj00 | Proximity Services (ProSe) Stage 2 | Rel-19 read |
| TS 33.303 vj00 | ProSe Security Specification for EPS | Rel-19 read |