IP Library Granted Patent US 12,477,600
Granted Patent B2
US 12,477,600 · App. 18/768,094 · Granted Nov 18, 2025

Tunnel failure signaling procedures

Inventors: Weihua Qiao (Herndon, VA); Esmael Hejazi Dinan (McLean, VA); Kyungmin Park (Vienna, VA); Jinsook Ryu (Oakton, VA); Peyman Talebi Fard (Vienna, VA); Taehun Kim (Fairfax, VA)
Assignee: Ofinno, LLC
H04W76/12H04L12/4633
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,477,600
App. No.
18/768,094
Granted
Nov 18, 2025
Kind
B2
Abstract

A user plane function (UPF) receives, from a control plane function (CPF), a request to establish a layer 2 tunneling protocol (L2TP) tunnel for a first protocol data unit (PDU) session of a wireless device. The UPF sends, to the CPF, a message comprising a tunnel failure cause for the establishment of the L2TP tunnel for the first PDU session. The message indicating at least one of a L2TP tunnel failure of the L2TP tunnel, or a L2TP session failure associated with the L2TP tunnel.

Claims (62)

1 . A method comprising:

receiving, by a user plane function (UPF) from a control plane function (CPF), a request to establish a layer 2 tunneling protocol (L2TP) tunnel between the UPF and an L2TP network server (LNS) for a first protocol data unit (PDU) session of a wireless device, wherein the UPF supports an L2TP service;

determining, by the UPF, a failure of the L2TP tunnel establishment; and

sending, by the UPF to the CPF and based on the determining, a message comprising a tunnel failure cause for the L2TP tunnel indicating:

an L2TP tunnel failure of the L2TP tunnel; and

that an L2TP access concentrator (LAC) and LNS pair connection between the UPF and the LNS does not exist;

wherein the UPF comprises the LAC.

2 . The method of claim 1 , wherein the CPF comprises a session management function (SMF).

3 . The method of claim 1 , wherein the L2TP tunnel is between the UPF and an L2TP server for the wireless device.

4 . The method of claim 1 , wherein the message further comprises a tunnel failure indication indicating a failed tunnel.

5 . The method of claim 1 , wherein the message further comprises an address of a tunnel server endpoint for a failed tunnel.

6 . The method of claim 1 , wherein the tunnel failure cause comprises an information element indicating at least one of:

a physical link failure of the tunnel;

a permanent failure of the tunnel;

a temporary failure of the tunnel; or

a tunnel session failure.

7 . The method of claim 1 , wherein the message further comprises a tunnel type comprising at least one of:

an L2TP tunnel version 2;

an L2TP tunnel version 3;

a generic routing encapsulation (GRE) tunnel;

an IP-in-IP tunnel; or

a GPRS tunnelling protocol (GTP) tunnel.

8 . A user plane function comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the user plane function (UPF) to:

receive, from a control plane function (CPF), a request to establish a layer 2 tunneling protocol (L2TP) tunnel between the UPF and an L2TP network server (LNS) for a first protocol data unit (PDU) session of a wireless device, wherein the UPF supports an L2TP service;

determine a failure of the L2TP tunnel establishment; and

send, to the CPF, a message comprising a tunnel failure cause for the L2TP tunnel indicating:

an L2TP tunnel failure of the L2TP tunnel; and

that an L2TP access concentrator (LAC) and LNS pair connection between the UPF and the LNS does not exist;

wherein the UPF comprises the LAC.

9 . The user plane function of claim 8 , wherein the CPF comprises a session management function (SMF).

10 . The user plane function of claim 8 , wherein the L2TP tunnel is between the UPF and an L2TP server for the wireless device.

11 . The user plane function of claim 8 , wherein the message further comprises a tunnel failure indication indicating a failed tunnel.

12 . The user plane function of claim 8 , wherein the message further comprises an address of a tunnel server endpoint for a failed tunnel.

13 . The user plane function of claim 8 , wherein the tunnel failure cause comprises an information element indicating at least one of:

a physical link failure of the tunnel;

a permanent failure of the tunnel;

a temporary failure of the tunnel; or

a tunnel session failure.

14 . The user plane function of claim 8 , wherein the message further comprises a tunnel type comprising at least one of:

an L2TP tunnel version 2;

an L2TP tunnel version 3;

a generic routing encapsulation (GRE) tunnel;

an IP-in-IP tunnel; or

a GPRS tunnelling protocol (GTP) tunnel.

15 . A non-transitory computer-readable medium storing instructions that, when executed by the one or more processors of a user plane function (UPF), cause the UPF to:

receive, from a control plane function (CPF), a request to establish a layer 2 tunneling protocol (L2TP) tunnel between the UPF and an L2TP network server (LNS) for a first protocol data unit (PDU) session of a wireless device, wherein the UPF supports an L2TP service;

determine a failure of the L2TP tunnel establishment; and

send, to the CPF, a message comprising a tunnel failure cause for the L2TP tunnel indicating:

an L2TP tunnel failure of the L2TP tunnel; and

that an L2TP access concentrator (LAC) and LNS pair connection between the UPF and the LNS does not exist;

wherein the UPF comprises the LAC.

16 . The non-transitory computer-readable medium of claim 15 , wherein the CPF comprises a session management function (SMF).

17 . The non-transitory computer-readable medium of claim 15 , wherein the L2TP tunnel is between the UPF and an L2TP server for the wireless device.

18 . The non-transitory computer-readable medium of claim 15 , wherein the message further comprises a tunnel failure indication indicating a failed tunnel.

19 . The non-transitory computer-readable medium of claim 15 , wherein the message further comprises an address of a tunnel server endpoint for a failed tunnel.

20 . The non-transitory computer-readable medium of claim 15 , wherein the tunnel failure cause comprises an information element indicating at least one of:

a physical link failure of the tunnel;

a permanent failure of the tunnel;

a temporary failure of the tunnel; or

a tunnel session failure.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2024
From: QIAO, WEIHUA; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; RYU, JINSOOK; TALEBI FARD, PEYMAN; KIM, TAEHUN
To: OFINNO, LLC
Reel/Frame 068326/0537 →
Continuity (4)
Continuation 17962032 · Oct 7, 2022
Continuation PCTUS2022012074 · Jan 12, 2022
Provisional Application 63136522 · Jan 12, 2021
Related Publication 20240365410A1 · Oct 31, 2024
References Cited (53)
US 9167610B2 · Henry et al. · 2015 [cited by applicant]
US 10555252B2 · Liu et al. · 2020 [cited by applicant]
US 10993112B2 · John et al. · 2021 [cited by applicant]
US 11240719B2 · Park et al. · 2022 [cited by applicant]
US 20060126584A1 · Zhang et al. · 2006 [cited by applicant]
US 20190098537A1 · Qiao · 2019 [cited by examiner]
US 20190109819A1 · Link, II · 2019 [cited by applicant]
US 20200053828A1 · Bharatia et al. · 2020 [cited by applicant]
US 20200267784A1 · Bharatia et al. · 2020 [cited by applicant]
US 20210014780A1 · Qiao et al. · 2021 [cited by applicant]
US 20210144790A1 · Faccin · 2021 [cited by examiner]
US 20220095154A1 · Qiao et al. · 2022 [cited by applicant]
EP 4118925A1 · 2023 [cited by applicant]
EP 4118926A1 · 2023 [cited by applicant]
WO WO2020073752A1 · 2020 [cited by examiner]
WO WO2020093790A1 · 2020 [cited by examiner]
WO WO2020096594A1 · 2020 [cited by examiner]
WO WO2022068219A1 · 2022 [cited by examiner]
WO 2022147048A1 · 2022 [cited by applicant]
WO 2022155169A1 · 2022 [cited by applicant]
3GPP TR 29.820 V0.3.0 (Nov. 2020); Technical Report; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals Study on Best Practice of PFCP; (Release 17). [cited by applicant]
Partial European Search Report, mailed Sep. 9, 2024, in EP Patent Application No. 24166319.4. [cited by applicant]
Extended European Search Report mailed Dec. 18, 2024 in EP Patent Application No. 24166319.4. [cited by applicant]
3GPP TS 23.007 V17.0.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Restoration procedures; (Release 17). [cited by applicant]
3GPP TS 23.501 V16.7.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2; (Release … [cited by applicant]
3GPP TS 23.502 V16.7.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2; (Release 16). [cited by applicant]
3GPP TS 23.503 V16.7.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); … [cited by applicant]
3GPP TS 24.501 V17.1.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; … [cited by applicant]
C1-196779; (was C1-196130); 3GPP TSG-CT WG1 Meeting #120; Portoroz (Slovenia), Oct. 7-11, 2019; CR-Form-v12.0; Change Request; 24.501 CR 1404; rev 3; Current version: 16.2.0. [cited by applicant]
3GPP TS 29.061 V14.3.0 (Mar. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interworking between the Public Land Mobile Network (PLMN) suppo… [cited by applicant]
3GPP TS 29.244 V16.6.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; St… [cited by applicant]
3GPP TS 29.274 V17.0.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio S… [cited by applicant]
3GPP TS 29.510 V17.0.0 (Dec. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3; (Relea… [cited by applicant]
C4-192470; was C4-192360; 3GPP TSG-CT WG4 Meeting #91; Reno, US; May 13-17, 2019; CR-Form-v12.0; Change Request; 29.510 CR 0154; rev 5; Current version: 15.3.0. [cited by applicant]
C4-205789; was C4-205692; 3GPP TSG-CT WG4 Meeting #101e; E-Meeting, Nov. 3-13, 2020; CR-Form-v12.0; Change Request; 29.510 CR 0407; rev 3; Current version: 16.5.0. [cited by applicant]
3GPP TS 29.561 V16.3.0 (Mar. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Interworking between 5G Network and external Data Net… [cited by applicant]
C4-205478; 3GPP TSG-CT WG4 Meeting #101e; E-meeting, Nov. 3, 2020-Nov. 13, 2020; Title: LS on Support of L2TP on SGi/N6 with Control and User Plane Separation; Release: Rel-17; Work Item: BEst Practice of PFCP (BEPoP). [cited by applicant]
C4-205509; 3GPP TSG-CT WG4 Meeting #101e; E-meeting, Nov. 3, 2020-Nov. 13, 2020; Source: Ericsson, ZTE; Title: KI on UPF Support for L2TP; Spec: 3GPP TR 29.820; Agenda item: 6.1.3; Document for: Agreement. [cited by applicant]
C4-205791; was C4-205607; 3GPP TSG-CT WG4 Meeting #101e; E-Meeting, Nov. 3-13, 2020; Source: ZTE; Title: Solution for L2TP tunnel setup; Spec: 3GPP TR29.820; Agenda item: 6.1.3; Document for: Approval. [cited by applicant]
CP-201357; (revision of CP-201076); 3GPP TSG-CT Meeting #88e; E-Meeting, Jun. 29-Jul. 1, 2020; Source: 3GPP TSG CT WG4; Title: New WID on BEst Practice of PFCP; Document for: Approval; Agenda Item: 17.2. [cited by applicant]
S2-160841; (revision of S2-154454, 255, 768); SA WG2 Meeting #113; Jan. 25-29, 2016, Saint Kitts, KN; CR-Form-v11.1; Change Request; 23.401 CR 2934; rev 6; Current version: 13.5.0. [cited by applicant]
S2-1911270; (revision of S2-1910599); 3GPP TSG-WG SA2 Meeting #136; Reno, NV, USA, Nov. 18-22, 2019 CR-Form-v12.0; Change Request; 23.501 CR 1710; rev 4; Current version: 16.2.0. [cited by applicant]
S2-2009331; 3GPP TSG-SA WG2 Meeting #142E; Nov. 16-20, 2020, Electronic, Elbonia; Title: LS Response on Support of L2TP in PFCP; Response to: S2-2008496 / C4-205478; Release: Release-17; Work Item: BEPoP. [cited by applicant]
L2TP Access Concentrator; P-GW Administration Guide, StarOS Release 21.20; Oct. 8, 2021. [cited by applicant]
Layer 2 Tunneling Protocol—Wikipedia; Retrieved Dec. 9, 2020; https://en.wikipedia.org/wiki/Layer_2_Tunneling_Protocol. [cited by applicant]
Townsley et al.; Layer Two Tunneling Protocol “L2TP”; Network Working Group; Request for Comments: 2661; Category: Standards Track; Aug. 1999. [cited by applicant]
Zorn et al.; RADIUS Attributes for Tunnel Protocol Support; Network Working Group; Request for Comments: 2868; Updates: RFC 2865; Category: Informational; Jun. 2000. [cited by applicant]
Lau et al.; Layer Two Tunneling Protocol—Version 3 (L2TPv3); Network Working Group; Request for Comments: 3931; Category: Standards Track; Mar. 2005. [cited by applicant]
TR-456 AGF Functional Requirements; Issue: 01; Technical Report; Jul. 2020; The Broadband Forum. [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority mailed on Jun. 22, 2022 in International Application No. PCT/US2022/012074. [cited by applicant]
C4-213396 was C4-213258; 3GPP TSG-CT WG4 Meeting #103-e; E-Meeting, Apr. 14-Apr. 23, 2021; Change Request; 29.244; CR 0554; rev 1; Current version: 17.0.0. [cited by applicant]
C4-205234; 3GPP TSG-CT WG4 Meeting #101e; E-meeting, Nov. 3, 2020-Nov. 13, 2020; Source: Ericsson; Title: KI on UPF Support for L2TP; Spec: 3GPP TR 29.820; Agenda item: 6.1.3; Document for: Agreement. [cited by applicant]
C4-205607; was C4-205195; 3GPP TSG-CT WG4 Meeting #101e; E-Meeting, Nov. 3-13, 2020; Source: ZTE; Title: Solution for L2TP tunnel setup; Spec: 3GPP TR29.820; Agenda item: 6.1.3; Document for: Approval. [cited by applicant]