IP Library Granted Patent US 12,463,771
Granted Patent B2
US 12,463,771 · App. 18/626,265 · Granted Nov 4, 2025

Mobile network user plane with access network user plane function

Inventors: Zhaohui Zhang (Westford, MA); Constantine Dimitrios-Polychronopoulos (Saratoga, CA); Arda Akman (San Ramon, CA)
Assignee: Juniper Networks, Inc.
H04L5/0048H04L5/0064H04W8/04H04W28/0263
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,463,771
App. No.
18/626,265
Granted
Nov 4, 2025
Kind
B2
Abstract

In an example, a method comprises executing, by an access network user plane function (ANUP) for a mobile network, an access network protocol to implement a connection with a user equipment (UE); implementing, by the ANUP, based on session data received from a control plane function of a mobile core network for the mobile network, an interface with a data network; and routing or switching, by the ANUP, packets between the connection with the UE and the interface with the data network.

Claims (47)

1 . A computing system comprising:

processing circuitry in communication with storage media, the processing circuitry configured to execute an access network user plane function (ANUP) for a mobile network, the ANUP configured to:

execute an access network protocol to implement a protocol data unit (PDU) session with a user equipment (UE);

advertise, to a data network, a host route comprising an Internet Protocol (IP) address for the UE;

route or switch packets between the data network and the PDU session with the UE based on the host route; and

implement, with a mobile core network for the mobile network, a common interface that provides a combination of an N2 interface and an N4 interface.

2 . The computing system of claim 1 , wherein the host route for the UE comprises a persistent Internet Protocol (IP) address for the UE.

3 . The computing system of claim 1 , wherein the ANUP is configured to advertise the host route for the UE based on the UE anchoring to the ANUP.

4 . The computing system of claim 1 , wherein the ANUP is further configured to advertise, to the data network and based on the UE de-anchoring from the ANUP, a withdrawal of the host route for the UE.

5 . The computing system of claim 1 , wherein the ANUP is configured to:

receive the packets, wherein the packets when received at the ANUP are not encapsulated with a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) header; and

route or switch the packets toward the UE based on the PDU session.

6 . The computing system of claim 1 , wherein the access network protocol comprises one or more of a Radio Link Control (RLC), a Packet Data Convergence Protocol (PDCP), or a Service Data Adaption Protocol (SDAP).

7 . The computing system of claim 1 ,

wherein the data network is implemented as an Internet Protocol Virtual Private Network (IP-VPN) or an Ethernet VPN,

wherein the ANUP is configured as a customer edge (CE) device connected to a provider edge (PE) device or integrated into the PE device of the IP-VPN or Ethernet VPN.

8 . The computing system of claim 1 , wherein the ANUP is configured to implement, based on session data received from a control plane function of a mobile core network for the mobile network, an interface with the data network.

9 . The computing system of claim 1 , wherein the ANUP does not implement an N3 interface.

10 . A method comprising:

executing, by an access network user plane function (ANUP) for a mobile network, the ANUP executed by processing circuitry, an access network protocol to implement a protocol data unit (PDU) session with a user equipment (UE);

advertising, by the ANUP, to a data network, a host route comprising an Internet Protocol (IP) address for the UE;

routing or switching, by the ANUP, packets between the data network and the PDU session with the UE based on the host route; and

implementing, by the ANUP and with a mobile core network for the mobile network, a common interface that provides a combination of an N2 interface and an N4 interface.

11 . The method of claim 10 , wherein the host route for the UE comprises a persistent Internet Protocol (IP) address for the UE.

12 . The method of claim 10 , wherein advertising the host route for the UE is based on the UE anchoring to the ANUP.

13 . The method of claim 10 , further comprising advertising, by the ANUP, to the data network and based on the UE de-anchoring from the ANUP, a withdrawal of the host route for the UE.

14 . The method of claim 10 , further comprising

receiving, by the ANUP, the packets, wherein the packets when received at the ANUP are not encapsulated with a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) header; and

routing or switching, by the ANUP, the packets toward the UE based on the PDU session.

15 . The method of claim 10 , wherein the access network protocol comprises one or more of a Radio Link Control (RLC), a Packet Data Convergence Protocol (PDCP), or a Service Data Adaption Protocol (SDAP).

16 . The method of claim 10 ,

wherein the data network is implemented as an Internet Protocol Virtual Private Network (IP-VPN) or an Ethernet VPN,

wherein the ANUP is configured as a customer edge (CE) device connected to a provider edge (PE) device or integrated into the PE device of the IP-VPN or Ethernet VPN.

17 . The method of claim 10 , further comprising implementing, by the ANUP and based on session data received from a control plane function of a mobile core network for the mobile network, an interface with the data network.

18 . The method of claim 10 , wherein the ANUP does not implement an N3 interface.

19 . Non-transitory, computer-readable media comprising instructions that, when executed, are configured to cause processing circuitry to:

execute an access network user plane function (ANUP) for a mobile network, the ANUP configured to:

execute an access network protocol to implement a protocol data unit (PDU) session with a user equipment (UE);

advertise, to a data network, a host route comprising an Internet Protocol (IP) address for the UE;

route or switch packets between the data network and the PDU session with the UE based on the host route; and

implement, with a mobile core network for the mobile network, a common interface that provides a combination of an N2 interface and an N4 interface.

20 . A computing system comprising:

processing circuitry in communication with storage media, the processing circuitry configured to execute an access network user plane function (ANUP) for a mobile network, the ANUP configured to:

execute an access network protocol to implement a protocol data unit (PDU) session with a user equipment (UE);

advertise, to a data network, a host route comprising an Internet Protocol (IP) address for the UE; and

receive packets from the data network, wherein the received packets are not encapsulated with a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) header; and

route or switch the received packets, using the PDU session, toward the UE based on the host route.

Assignments (1)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0034 →
Continuity (3)
Continuation 17657582 · Mar 31, 2022
Provisional Application 63264075 · Nov 15, 2021
Related Publication 20240250789A1 · Jul 25, 2024
References Cited (39)
US 10798617B1 · Ghadge et al. · 2020 [cited by applicant]
US 11303696B2 · You et al. · 2022 [cited by applicant]
US 11375527B1 · Eyuboglu et al. · 2022 [cited by applicant]
US 11418600B1 · Panem Jaya et al. · 2022 [cited by applicant]
US 11979349B2 · Zhang · 2024 [cited by examiner]
US 20170012816A1 · Park et al. · 2017 [cited by applicant]
US 20190053117A1 · Bae et al. · 2019 [cited by applicant]
US 20200107213A1 · Park et al. · 2020 [cited by applicant]
US 20200287826A1 · Wang · 2020 [cited by applicant]
US 20200367201A1 · Cai et al. · 2020 [cited by applicant]
US 20200383009A1 · Qiao et al. · 2020 [cited by applicant]
US 20210367703A1 · Chandramouli · 2021 [cited by examiner]
US 20230102552A1 · Ali et al. · 2023 [cited by applicant]
US 20230155762A1 · Zhang et al. · 2023 [cited by applicant]
CN 110198307A · 2019 [cited by applicant]
WO 2019078888A1 · 2019 [cited by applicant]
WO 2020106274A1 · 2020 [cited by applicant]
WO 2020173137A1 · 2020 [cited by applicant]
WO 2020197451A1 · 2020 [cited by applicant]
“3rd Generation Partnership Project,” Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17), 3GPP TS 23.501 V17.7.0, Dec. 2022, 573 pp. [cited by applicant]
Bryant et al., “Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture,” Network Working Group, RFC 3985, Mar. 2005, 40 pp. [cited by applicant]
Extended Search Report from counterpart European Application No. 22180545.0 dated Dec. 14, 2022, 9 pp. [cited by applicant]
Jaffry et al., “PDU Session Establishment in 5G,” medium.com, Jan. 12, 2023, 3 pp. [cited by applicant]
Matsushima et al., Segment Routing IPV6 Mobile User Plane Architecture for Distributed Mobility Management draft-mhkk-dmm-srv6mup-architecture-01, Internet Engineering Task Force, Internet-Draft, Nov. 10, 2021, 34 pp. [cited by applicant]
Matsushima et al., “Segment Routing IPv6 Mobile User Plane Architecture for Distributed Mobility Management draft-mhkk-dmm-srv6mup-architecture-04,” Internet Engineering Task Force, Internet-Draft, Oct. 24, 2022, 41 pp. [cited by applicant]
Matsushima et al., “Segment Routing IPV6 Mobile User Plane Architecture for Distributed Mobility Management,” draft-mhkk-dmm-srv6mup-architecture-02, Internet Engineering Task Force, , Mar. 7, 2022, 17 pp. [cited by applicant]
Murakami et al., “BGP Extensions for the Mobile User Plane (MUP) SAFI draft-mpmz-bess-mup-safi-00.txt,” Internet-Draft, Mar. 7, 2022, 39 pp. [cited by applicant]
Murakami et al., “BGP Extensions for the Mobile User Plane (MUP) SAFI,” Internet-Draft: draft-mpmz-bess-mup-safi-02, Mar. 13, 2023, 18 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/657,582, dated May 23, 2023 through Jan. 9, 2024, 55 pp. [cited by applicant]
Response to Extended Search Report dated Dec. 14, 2022, from counterpart European Application No. 22180545.0 filed Nov. 10, 2023, 24 pp. [cited by applicant]
Rosen et al., “BGP/MPLS IP Virtual Private Networks (VPNs),” Network Working Group, RFC 4364, Feb. 2006, 47 pp. [cited by applicant]
Sangli et al., “BGP Extended Communities Attribute,” Network Working Group, RFC 4360, Feb. 2006, 12 pp. [cited by applicant]
U.S. Appl. No. 18/343,248, filed Jun. 28, 2023, Zhang et al. [cited by applicant]
Xiao et al., “Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3),” Network Working Group, RFC 3916, Sep. 2004, 19 pp. [cited by applicant]
Zhang et al., “BGP Signaling for Mobile User Plane,” draft-zpm-dmm-mup-bgp-signaling-00, Internet-Draft, Mar. 7, 2022, 8 pp. [cited by applicant]
Zhang et al., “Mobile User Plane Evolution draft-zzhang-dmm-mup-evolution-02,” Internet-Draft, Oct. 24, 2022, 19 pp. [cited by applicant]
Zhang, “5G Edge Cloud and Multi-access Edge Computing (MEC) Security,” Juniper Networks, Retrieved from: https://blogs.juniper.net/en-us/service-provider-transformation/5g-edge-cloud-and-multi-access-edge-computing-mec-… [cited by applicant]
“5G System Enhancements for Edge Computing; Stage 2”, (3GPP TS 23.548 V17.0.0 Release 17), 3GPP A Global Initiative, Sep. 24, 2021, 52 pp. [cited by applicant]
First Office Action and Search Report, and translation thereof, from counterpart Chinese Application No. 202210711337.8 dated May 22, 2025, 36 pp. [cited by applicant]