AL

Application Layer

Services
Introduced in Rel-8
AL refers to the Application Layer in the 3GPP service architecture, which hosts end-user services and applications. It is a conceptual layer above the core network where value-added services like multimedia streaming, messaging, and IoT applications reside and interact with the underlying transport capabilities. Its definition ensures standardized service enablers and interfaces for consistent application behavior across networks.

Description

The Application Layer (AL) in 3GPP is a logical architectural stratum that encompasses the applications and service capabilities utilized by end-users and enterprises. It sits atop the core network and leverages the connectivity, session management, and quality of service (QoS) functions provided by lower layers, such as the IP Multimedia Subsystem (IMS) or 5G Core Network. The AL is not a single physical entity but a collection of application servers, service platforms, and client software that implement services like Voice over LTE (VoLTE), video calling, rich communication services (RCS), multimedia broadcast/multicast services (MBMS), and various IoT applications. These applications use standardized Application Programming Interfaces (APIs) and reference points, such as those defined in 3GPP TS 23.247 for service exposure, to interact with network functions for authentication, policy control, and media delivery.

Architecturally, the AL interfaces with core network functions through well-defined service-based interfaces (SBIs) in 5G or traditional reference points in earlier releases. For instance, an application server in the AL may communicate with the Policy Control Function (PCF) to request specific QoS for a video stream or with the Unified Data Management (UDM) for user authentication. Key components within the AL include the Application Function (AF), which is a formal 3GPP network function that influences traffic routing and policy decisions, and various service enablers like the Multimedia Telephony Service for IMS (MTSI). The AL also encompasses client-side application logic on user equipment (UE), which implements protocols like the Real-time Transport Protocol (RTP) for media or HTTP/2 for web services.

The role of the AL is to provide a standardized environment for service development and deployment, ensuring interoperability across different operators and device types. It abstracts the complexities of the underlying radio and core networks, allowing application developers to focus on service logic while relying on network capabilities for security, mobility, and session management. In specifications like 3GPP TS 26.110 for codec characteristics or TS 38.857 for vehicle-to-everything (V2X) application layer support, the AL defines protocols, data formats, and behaviors specific to services, such as adaptive bitrate streaming for video or collective perception messages for autonomous driving. This layer is crucial for enabling advanced use cases in 5G and beyond, including augmented reality, industrial automation, and network slicing-aware applications, by providing a framework for service exposure and network integration.

Purpose & Motivation

The Application Layer exists to decouple service innovation from network infrastructure evolution, allowing operators and third-party developers to create and deploy applications independently of the underlying transport technology. Prior to its formalization in 3GPP, services were often tightly integrated with specific network implementations, leading to vendor lock-in, interoperability issues, and slow time-to-market for new features. By defining a standardized AL with clear interfaces, 3GPP enables a vibrant ecosystem of applications that can work consistently across diverse networks, from 4G LTE to 5G and future systems. This approach addresses limitations of monolithic network architectures where service logic was embedded within core network elements, making updates cumbersome and hindering scalability.

Historically, the AL concept gained prominence with the introduction of IMS in 3GPP Release 5, which provided a service delivery platform for multimedia applications. However, it was further refined in later releases to support a broader range of services, including those for IoT and V2X communications. The motivation for its continuous evolution stems from the need to support emerging use cases that require low latency, high reliability, or massive connectivity, such as in 5G. By specifying application-layer protocols and enablers, 3GPP ensures that these services can leverage network capabilities like network slicing, edge computing, and QoS differentiation effectively, solving problems related to service performance, security, and management in complex multi-vendor environments.

Key Features

  • Standardized service enablers and APIs for application development
  • Integration with core network functions via defined reference points (e.g., AF interacting with PCF)
  • Support for multimedia services through codecs and streaming protocols
  • Enables IoT and V2X applications with specific message formats and procedures
  • Facilitates service exposure for third-party developers via Network Exposure Function (NEF)
  • Provides framework for application-aware network slicing and QoS management

Evolution Across Releases

Rel-8 Initial

Introduced the Application Layer concept within the Evolved Packet System (EPS) architecture, focusing on service delivery over LTE. It defined initial application enablers for IMS-based services like Voice over LTE (VoLTE) and Multimedia Telephony Service for IMS (MTSI), with specifications covering codec requirements and basic service exposure mechanisms to support interoperable multimedia applications.

Defining Specifications

SpecificationTitle
TS 23.247 3GPP TS 23.247
TS 26.110 3GPP TS 26.110
TS 38.305 3GPP TR 38.305
TS 38.833 3GPP TR 38.833
TS 38.857 3GPP TR 38.857
TS 38.878 3GPP TR 38.878