End-to-End

Description

In 3GPP standards, End-to-End (E2E) is a holistic architectural and service concept that defines the complete communication path between two endpoints, which could be user equipment (UE), application servers, or other network functions. This path encompasses all involved network segments: the Radio Access Network (RAN), the Core Network (CN), and potentially external networks like the Internet or other operator domains. The E2E perspective is crucial for service provisioning, as it ensures that performance, security, and functional requirements are maintained across every hop and administrative boundary. It shifts the focus from isolated network element performance to the complete user experience and service delivery.

Architecturally, E2E considerations are embedded in service definitions and requirements specifications. For instance, when defining a new service like enhanced Mobile Broadband (eMBB) or Ultra-Reliable Low-Latency Communication (URLLC), 3GPP specifies E2E key performance indicators (KPIs) such as latency, reliability, and data rate. These KPIs must be satisfied by the collective performance of the RAN, transport network, core network functions, and any application servers. This requires coordination between different network domains, often managed through policy control, network exposure, and orchestration functions like the Network Slice Selection Function (NSSF) and the Policy Control Function (PCF).

From a protocol perspective, E2E can refer to the logical connection between peer entities at the highest layer of a protocol stack, such as the application layer. However, in 3GPP's system architecture, it more commonly refers to the service layer. Mechanisms like Quality of Service (QoS) flows are established E2E, with QoS Class Identifiers (QCIs) and 5G QoS Identifiers (5QIs) ensuring that packets receive appropriate treatment from the UE, through the gNB/NG-RAN, the User Plane Function (UPF), and onto the data network. Network Slicing is a prime example of an E2E construct, where a logical network comprising specific RAN, transport, and core network resources is instantiated to provide an isolated E2E service with guaranteed characteristics.

The role of E2E in the network is foundational for service assurance and innovation. It enables operators to offer Service Level Agreements (SLAs) to enterprise customers or vertical industries, as the performance can be guaranteed across the entire network path. For management systems, E2E service monitoring and fault management are essential to quickly isolate issues that degrade the user-perceived service quality. Furthermore, E2E security models ensure protection is applied consistently from the device to the cloud application, preventing vulnerabilities at network boundaries.

Purpose & Motivation

The concept of End-to-End (E2E) was formally emphasized in 3GPP to address the challenges of providing consistent, high-quality services across increasingly complex and multi-domain network architectures. Early mobile networks (2G, 3G) primarily focused on connectivity within a single operator's radio and core network. With the advent of IP-based services, roaming, and interconnection with external packet data networks, the user experience became dependent on the performance of all traversed networks. The lack of an E2E view made it difficult to guarantee service quality, troubleshoot problems, and implement advanced features like prioritized traffic handling for specific applications.

The introduction of E2E as a core principle, particularly from Release 9 onwards, was motivated by the need to support diverse services with stringent requirements. The rise of real-time services (VoIP, video conferencing), mission-critical communications, and later, IoT and vertical industry applications, demanded predictable performance not just in the radio link, but across the entire data path. This was a limitation of previous approaches where QoS mechanisms might only be applied in the core network, leaving the RAN or external transit networks as potential bottlenecks. E2E design ensures that service requirements are translated into specific configurations and policies for each network segment, enabling true service-based architecture.

Historically, the evolution towards 5G and Network Slicing made the E2E concept indispensable. A network slice is by definition an E2E logical network. Creating a slice for a factory automation or a massive IoT deployment requires coordinated resource reservation and configuration in the RAN, transport, and core. The E2E framework defined in specifications like TS 22.261 (5G service requirements) provides the blueprint for how these isolated E2E networks are conceived, instantiated, and managed, solving the problem of network rigidity and enabling one physical infrastructure to support countless tailored virtual networks.

Key Features

• Holistic service definition covering UE, RAN, core network, and data network
• Enables definition and guarantee of End-to-End Key Performance Indicators (KPIs)
• Foundation for Network Slicing, creating logical E2E isolated networks
• Supports coordinated QoS policy enforcement across all network domains
• Essential for E2E service monitoring, assurance, and fault management
• Facilitates Service Level Agreements (SLAs) with enterprises and verticals

Evolution Across Releases

Defining Specifications