Current Status of 3GPP Edge Computing Standardization
Edge computing has gradually become an important component in the evolution of the 5G system, and 3GPP has consolidated its direction beginning in Release 17. Current standardization work is mainly driven by SA2 and SA6.
SA2 first conducted a full technical assessment in TR 23.748, analyzing how edge capabilities can be incorporated into the 5G Core. Based on this, TS 23.548 defines the system-level enhancements needed to support edge computing, including:
-
Distributed anchor point model
-
Session breakout model
-
Multiple PDU session model
These models provide different approaches for traffic steering and reflect how networks can direct user traffic toward edge data centers in an efficient and predictable manner.
On the application side, TS 23.558 introduces the Edge Enabler Layer (EEL), which includes the Edge Enabler Client (EEC), Edge Enabler Server (EES), and Edge Configuration Server (ECS). These components support application discovery, selection, and mobility handling, ensuring that an application can move with the user without interrupting service.
Security considerations for edge deployments are analyzed in TR 33.839, which identifies additional risks that arise when applications are hosted close to the user.
Together, these Release 17 specifications form the basis of the current 3GPP framework for edge computing.
Planned Enhancements in Future Releases
Looking ahead, 3GPP will continue to refine the standards introduced in Release 17. The following areas are expected to receive particular attention:
Local Routing and Traffic Steering
Improvements will focus on how networks choose the best UPF for a specific user or service, taking into account latency, load conditions, and the availability of local applications.
Session and Service Continuity
Future releases will strengthen the mechanisms defined in TS 23.558—particularly EAS relocation, context transfer, and procedures supporting both UE and AF mobility.
User Plane Selection and Re-selection
Dynamic UPF re-selection will become more important as networks deploy multiple edge sites. Ongoing work aims to make traffic routing more responsive to real-time network conditions.
Network Capability Exposure
Building on the foundations of Release 17, additional APIs will help edge applications retrieve network conditions, optimize routing, and interact with 5G system functions more directly.
Quality of Service and Billing
Further integration of QoS control and charging—handled by PCF—will ensure that traffic processed at the edge can be measured, controlled, and billed with the same granularity as centralized traffic.
Local Data Network Enhancements
Future standards will refine the coordination between centralized cloud applications and the distributed edge application environment, including how applications are deployed, updated, and discovered across multiple sites.
Shortcomings in Current 3GPP Edge Computing Standardization
Despite the progress in Release 17, several limitations remain:
Fragmented Standards Across Different Groups
Edge-related functions are described across SA2, SA6, SA3 and partially in RAN. Although each piece is correct individually, the overall framework still lacks the level of integration operators expect.
Late Introduction of Unified Architecture
Before Release 17, 3GPP had no single end-to-end architecture dedicated to edge computing. Much of the industry relied on vendor-specific implementations, leading to compatibility issues.
Focus on Core 5G Enhancements
3GPP’s primary tasks remain the 5G system architecture, RAN evolution, and physical layer improvements. Edge computing, while important, is still a secondary topic in many work items.
Deployment Challenges
Because edge computing involves coordination between network operators, cloud providers, and application developers, real-world deployments are developing more slowly than the standards themselves.
Implications for the Industry
The direction of future 3GPP edge computing standardization suggests several practical considerations:
-
Operators will need to deploy UPFs near users to support latency-critical services.
-
Application providers should prepare to integrate with the Edge Enabler Layer defined in TS 23.558.
-
Equipment vendors must ensure their products support TS 23.548 traffic routing models.
-
Developers will increasingly rely on standardized network APIs instead of vendor-specific interfaces.
-
The industry must adopt more unified practices for edge application deployment and mobility handling.
A clear understanding of the 3GPP roadmap will help network operators and ecosystem partners plan more sustainable edge computing strategies.
Conclusione
Future 3GPP edge computing standardization builds on the Release 17 framework, where TS 23.548, TS 23.558, TR 23.748, and TR 33.839 provide the first comprehensive industry-wide architecture for edge computing. While these standards already form a solid foundation, further enhancements will continue to improve traffic steering, mobility support, capability exposure, and overall integration between 5G networks and edge applications.
As the ecosystem matures, staying aligned with 3GPP’s ongoing work will be essential for organizations aiming to deploy reliable, scalable, and future-proof edge computing solutions.