Designated Router

Description

The Designated Router (DR) is a functional entity defined within the 5G Core Network architecture to support Edge Computing, specifically detailed in the framework for enabling edge applications. It resides in the user plane path, typically collocated with or near the User Plane Function (UPF) that serves a specific local area or data network. The primary role of the DR is to act as an intelligent routing anchor for traffic destined to or originating from applications deployed at the network edge.

Operationally, when a UE's session is established with an edge application server (EAS), the 5G core network (via the SMF) configures the UPF and the associated DR with the appropriate traffic steering rules. The DR examines the IP packets flowing from the UE. Based on the destination IP address, and potentially other packet filters, the DR determines whether the traffic is intended for a local EAS or should be routed to the central internet or cloud. For traffic destined to a local EAS, the DR performs the necessary Network Address Translation (NAT) or IP routing functions to direct the packets onto the local data network where the EAS resides, avoiding unnecessary latency from routing to a central data center.

Architecturally, the DR is a key component in realizing efficient edge traffic offload. It works in conjunction with the Session Management Function (SMF), which provides the steering policies, and the Network Exposure Function (NEF) or Edge Enabler Client/Server, which facilitate application discovery. The DR may implement features like UE IP address preservation for the EAS, traffic duplication for analytics, and integration with the Local Area Data Network (LADN) concept. Its deployment is crucial for low-latency services like industrial IoT, augmented reality, and vehicle-to-everything (V2X), as it ensures user traffic takes the most direct path to the proximate application instance, minimizing round-trip time and backhaul congestion.

Purpose & Motivation

The Designated Router was introduced to address the traffic routing challenges inherent in distributed Edge Computing architectures within 5G. As applications moved from centralized clouds to the network edge to reduce latency, a mechanism was needed to ensure UE traffic could be efficiently and dynamically steered to the correct local application instance without complex client-side configuration or inefficient tromboning (routing to a central point and back).

Previous mobile network architectures lacked a standardized, network-controlled function for granular local traffic steering at the edge. Solutions were often vendor-specific or relied on external SDN controllers. The DR, standardized starting in 3GPP Release 16, provides a native, protocol-agnostic routing function within the 3GPP user plane. It solves the problem of transparently connecting UEs to the optimal edge application server based on network policies and UE location. This enables use cases requiring ultra-reliable low-latency communication (URLLC) and high bandwidth by establishing efficient, localized data paths. Its creation was motivated by the industry's shift towards multi-access edge computing (MEC) and the need for the 5G core to natively support application context-aware routing, which is fundamental for delivering the performance promises of 5G.

Key Features

• Steers UE traffic to local Edge Application Servers (EAS)
• Performs IP routing and potentially NAT functions at the edge
• Operates under control of SMF-provided traffic steering policies
• Enables low-latency communication paths for edge applications
• Supports integration with Local Area Data Network (LADN) concepts
• Facilitates efficient edge traffic offload and backhaul savings

Evolution Across Releases

Defining Specifications