Internet-Draft SRv6mob-arch November 2026
Kamata, et al. Expires 20 May 2027 [Page]
Workgroup:
DMM Working Group
Internet-Draft:
draft-ietf-dmm-srv6mob-arch-05
Published:
Intended Status:
Informational
Expires:
Authors:
T. Kamata
Cisco Systems, Inc.
J. Horn
Cisco Systems, Inc.
L. Jalil
Verizon
W. Cheng
China Mobile
M. Kohno
Keio University

Architecture Discussion on SRv6 Mobile User plane

Abstract

This document describes the solution approach and its architectural benefits of transforming mobile session information into routing information, leveraging segment routing capabilities, and operating within the IP routing paradigm.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 20 May 2027.

▲

Table of Contents

1. Introduction

The existing mobile user plane is currently defined as an overlay tunnel session to a mobile anchor point (UPF: User Plane Function in 5G context).

While this approach may be suited for use cases requiring frequent mobile handover and functionality tied to session initiation/ termination, it may be challenging in some deployments to cost-effectively and scalably address the high traffic volumes of the 5G/Beyond 5G era and the increasingly distributed data and computing demands in the future.

The requirements for wireless systems are becoming more diverse, and there are cases, such as some IoT and FWA (Fixed Wireless Access) systems, where the frequent mobile handover is not necessarily mandatory.

This document describes the solution approach and its architectural benefits of transforming mobile session information into routing information, leveraging segment routing capabilities, and operating within the IP routing paradigm.

This document also clarifies the motivation for the MUP initiatives : [RFC9433][I-D.mhkk-dmm-mup-architecture]

2. Problem Definition

Depending on the deployment and service requirements, a tunnel-based mobile user plane may require additional design considerations for:

The scalability comparison in this document refers to the amount of connectivity state needed to represent optimized any-to-any communication, rather than to the computational complexity of all mobile control-plane procedures. In the existing 3GPP architecture, the mobile control plane remains responsible for establishing and maintaining PDU sessions, including the selection of the relevant user-plane functions and GTP-U tunnel endpoints. The conventional anchor-based architecture can maintain one session per endpoint, but traffic between endpoints is generally carried through the selected anchor. If optimized any-to-any connectivity among N endpoints is instead represented using a separate tunnel or forwarding state for each communicating endpoint pair, the amount of such state can grow as N(N-1), or O(N^2).

In the MUP architecture, the 3GPP session-management functions continue to manage the lifecycle and policy of mobile sessions. Relevant session information is learned by the MUP control plane and transformed into destination-based routing information. A route describing reachability to a destination can be shared by traffic from multiple sources, and transit nodes do not need to maintain GTP-U tunnel state for every communicating endpoint pair. Consequently, optimized any-to-any reachability can be represented by O(N) destination-based entries at a forwarding node, before route aggregation, rather than by O(N^2) pairwise entries.

This comparison does not imply that all per-session state is eliminated. The 3GPP session-management functions continue to maintain the session lifecycle and policy information required by the mobile service. Rather, the scalability benefit described here comes from sharing reachability information among multiple sources instead of maintaining separate GTP-U tunnel or forwarding state for every communicating endpoint pair.

Edge/distributed computing can be seen as one scenario involving any-to-any communication. Destination-based IP routing can facilitate reachability to distributed computing resources.

As for FMC/WWC, there is currently a coordinated standardization effort between 3GPP WWC [TS.23316] and BBF [BBF407]. These approaches can integrate wireline traffic with the mobile packet core. Depending on the deployment and service requirements, anchoring such traffic may introduce additional considerations for path optimization and scalability.

In addition, an anchor that terminates a large number of tunnel sessions may become a scaling consideration in some deployments.

In the scenarios described above, shared routing information can reduce the need for pairwise tunnel state. This does not preclude the use of SRv6 source routing or hybrid approaches, including uSID-based segment encoding, for path steering. Segment Routing can provide path steering, protection, policy control, multi-tenancy, and support for reliability and SLA differentiation. Segment Routing can also be used in the underlay of a GTP-U-based architecture.

3. SRv6 MUP and the 5G/Beyond 5G use cases

This section discusses the potential benefits of applying SRv6 MUP to selected 5G/Beyond 5G use cases. These benefits arise from representing relevant mobile session information as routing information and from using Segment Routing capabilities where they are applicable.

In particular, the adoption of the SRv6 uSID (NEXT-C-SID) flavor [RFC9800] can reduce encapsulation overhead and enhance packet efficiency. Since uSID allows multiple segments to be compressed into a single IPv6 Destination Address (DA), it optimizes forwarding performance and minimizes the MTU impact even when long Segment Lists are required. This efficiency is a critical enabler for the use cases described below.

3.1. Network Slicing

Network slicing enables network segmentation, isolation, and SLA differentiation such as latency and availability. End-to-end slicing will be achieved by mapping and coordinating IP network slicing, RAN and mobile packet core slicing.

In a tunnel-based mobile user plane, meeting end-to-end SLAs may require coordination with the underlying IP network. An IP routing-based approach can provide another way to address this requirement.

Segment Routing has a comprehensive set of slice engineering technologies. How to build network slicing using the Segment Routing technology is described in [I-D.ali-teas-spring-ns-building-blocks].

Moreover, the stateless slice identifier encoding [I-D.filsfils-spring-srv6-stateless-slice-id] may enable per-slice forwarding policy using the IPv6 header.

The use of uSID can make slice-specific path steering more packet-efficient. By compressing multiple service and topological SIDs into a compact header, it can reduce the risk of fragmentation and MTU-related issues associated with deep SID stacks.

3.2. Edge Computing

Edge computing, where the computing workloads and datastores are placed closer to users, is recognized as one of the key pillars to meet demanding requirements of 5G/Beyond 5G era, with regard to low latency, bandwidth efficiency, data locality and privacy.

Edge computing is more important than ever. Improvements in New Radio can reduce access-network latency. However, when traffic to a nearby application must traverse a distant user-plane anchor, the resulting path may limit the end-to-end latency benefit.

Even with existing mobile architectures, it is possible to place UPFs in a multi-tier, or to distribute UPFs, to achieve Edge Computing. [TS.23548] and [ETSI-MEC] describe how to properly select the UPF of adequate proximity. Depending on the deployment, branching traffic or using different UPFs may require additional signaling and coordination. Maintaining seamless handover with distributed UPFs may also require additional design considerations.

When it comes to the IP routing paradigm, ubiquitous computing is innately supported. uSID is particularly beneficial here, as edge computing frequently involves a high volume of small packets, such as those generated by IoT devices. Traditional SRv6 headers with long Segment Lists can impose a disproportionately high overhead on these small payloads. uSID minimizes this overhead, thereby maximizing effective throughput and ensuring efficient utilization of bandwidth-constrained links in distributed edge environments.

3.3. URLLC (Ultra-Reliable Low-Latency Communication) support

3GPP [TR.23725] investigates the key issues for meeting the URLLC requirements on latency, jitter and reliability in the 5G System. The solutions described in that document focus on improving the overlay protocol (GTP-U) and provide a few hints on how to map such tight-SLA into the transport network. These hints are based on static configuration or static mapping for steering the overlay packet into the right transport SLA. The scalability and operational impact of such approaches depend on the deployment.

Another issue that deserves special mention is the ultra-reliability issue. In order to support ultra-reliability with the tunnel session paradigm, redundant user plane paths based on dual connectivity have been proposed. The proposal has two main options.

  • Dual Connectivity based end-to-end Redundant User Plane Path

  • Support of redundant transmission on N3/N9 interfaces

In the case of the former, UE and hosts have RHF(Redundancy Handling Function). In sending, RHF is to replicate the traffic onto two GTP-U tunnels, and in receiving, RHF is to merge the traffic.

In the case of the latter, traffic are to be replicated and merged with the same sequence for specific QoS flow, which requires further enhancements.

In either case, achieving the intended reliability benefit requires ensuring that the redundant sessions use sufficiently disjoint transport paths.

An SRv6 MUP approach provides another way to address these transport-path requirements.

Segment routing has some advantages for URLLC traffic. First, traffic can be mapped to a disjoint path or low latency path as needed. Second, Segment routing provides an automated reliability protection mechanism known as TI-LFA, which is a sub-50ms FRR mechanism that provides protection regardless of the topology through the optimal backup path. It can be provisioned slice-aware.

uSID further strengthens URLLC support by reducing packet length and, consequently, serialization delay, particularly on bandwidth-constrained links. Together with appropriate path selection and protection, this can help limit latency variation in applicable deployments.

4. Co-existence and Incremental Deployability

Mobile networks are composed of radio, mobile packet core, and IP networks (access and backbone), with separate standard organizations and communities. Therefore, coexistence with existing systems and incremental deployment are important considerations when introducing a new user-plane approach.

[RFC9433] defines the user plane convergence between GTP-U and SRv6, so that it can co-exist with the existing user plane as needed.

[I-D.mhkk-dmm-mup-architecture] defines the MUP architecture for Distributed Mobility Management, which can be plugged into the existing mobile service architecture. In the architecture, mobile session information is transformed to routing information, and operated using an L3VPN-based scheme.

5. Security Considerations

The deployment of this architecture is targeted in an administrative domain, and the functionality is domain specific.

6. IANA Considerations

This memo includes no request to IANA.

7. References

7.1. Normative References

[RFC9433]
Matsushima, S., Ed., Filsfils, C., Kohno, M., Camarillo, P., Ed., and D. Voyer, "Segment Routing over IPv6 for the Mobile User Plane", RFC 9433, DOI 10.17487/RFC9433, , <https://www.rfc-editor.org/rfc/rfc9433>.
[RFC9800]
Cheng, W., Ed., Filsfils, C., Li, Z., Decraene, B., and F. Clad, Ed., "Compressed SRv6 Segment List Encoding", RFC 9800, DOI 10.17487/RFC9800, , <https://www.rfc-editor.org/rfc/rfc9800>.

7.2. Informative References

[BBF407]
BBF, "5G Wireless Wireline Convergence Architecture", BBF TR-407 Issue:1, .
[ETSI-MEC]
ETSI, "MEC in 5G Networks", ETSI White Paper No.28, .
[I-D.ali-teas-spring-ns-building-blocks]
Ali, Z., Filsfils, C., Camarillo, P., Voyer, D., Matsushima, S., Rokui, R., Dhamija, and P. Maheshwari, "Building blocks for Network Slice Realization in Segment Routing Network", Work in Progress, Internet-Draft, draft-ali-teas-spring-ns-building-blocks-03, , <https://datatracker.ietf.org/doc/html/draft-ali-teas-spring-ns-building-blocks-03>.
[I-D.filsfils-spring-srv6-stateless-slice-id]
Filsfils, C., Clad, F., Camarillo, P., Raza, S. K., Voyer, D., and R. Rokui, "Stateless and Scalable Network Slice Identification for SRv6", Work in Progress, Internet-Draft, draft-filsfils-spring-srv6-stateless-slice-id-10, , <https://datatracker.ietf.org/doc/html/draft-filsfils-spring-srv6-stateless-slice-id-10>.
[I-D.mhkk-dmm-mup-architecture]
Matsushima, S., Horiba, K., Kawakami, Y., Murakami, T., Patel, K., and J. Horn, "Mobile User Plane Architecture for Distributed Mobility Management", Work in Progress, Internet-Draft, draft-mhkk-dmm-mup-architecture-02, , <https://datatracker.ietf.org/doc/html/draft-mhkk-dmm-mup-architecture-02>.
[TR.23725]
3GPP, "Study on enhancement of Ultra-Reliable Low-Latency Communication (URLLC) support in the 5G Core network (5GC)", 3GPP TR 23.725 16.2.0, .
[TS.23316]
3GPP, "Wireless and wireline convergence access support for the 5G System (5GS)", 3GPP TS 23.316 16.7.0, .
[TS.23548]
3GPP, "5G system Enhacements for Edge Computing", 3GPP TS 23.548 17.0.0, .

Acknowledgements

Authors would like to thank Satoru Matsushima, Shunsuke Homma, Yuji Tochio and Jeffrey Zhang, for their insights and comments.

Contributors

Francois Clad
Cisco Systems, Inc.
France
Pablo Camarillo Garvia
Cisco Systems, Inc.
Spain
Zafar Ali
Cisco Systems, Inc.
United States of America

Authors' Addresses

Teppei Kamata
Cisco Systems, Inc.
Japan
Jakub Horn
Cisco Systems, Inc.
Czech Republic
Luay Jalil
Verizon
United States of America
Weiqiang Cheng
China Mobile
China
Miya Kohno
Keio University
Japan