IP Library › Granted Patent US 12,689,965
Granted Patent B2
US 12,689,965 · App. 18/199,907 · Granted Jul 21, 2026

Methods and apparatus for supporting low latency, low loss and scalable throughput L4S through the use of UE route selection policy (URSP) rules

Inventors: Yildirim Sahin (Englewood, CO); Paul L. Russell, Jr. (Lawrence, NJ); Maulik Vaidya (Escondido, CA)
Assignee: Charter Communications Operating, LLC
H04W40/02H04L45/30
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,689,965
App. No.
18/199,907
Granted
Jul 21, 2026
Kind
B2
Abstract

A UE is supplied with one or more UE Route Selection Policy (URSP) rules which include an indicator indicating support for a “L4S” Connection Capability. The use of an L4S connection capability indicator allows a UE to obtain L4S support for application traffic data requiring L4S support. The connection capabilities option in the URSP rule or rules allows a UE to select an appropriate route selection for matching L4S connection capability. By allowing a UE to indicate that a packet or packet flow is to be matched to a PDU session which has an L4S connection capability, the UE can trigger establishment of a new PDU session to support a flow of application data packets requiring L4S support or can cause the packet flow to be assigned to an existing PDU session or trigger a modification of an existing PDU Session which supports L4S.

Claims (42)

1 . A method of operating User Equipment (UE), the method comprising:

storing in the UE a set of UE Route Selection Policy (URSP) rules, said set of URSP rules including at least a first rule including a L4S traffic descriptor;

detecting, in the UE, a need to support a L4S traffic flow by detecting i) an application request from an application running on the UE requesting L4S treatment for application traffic corresponding to the requesting application or ii) an L4S indicator in incoming application traffic, said incoming application traffic being from an application running on the UE; and

determining, in the UE, the URSP rule stored in the UE to use in response to detecting the need to support the L4S traffic flow, said determining including identifying a stored URSP rule that includes an L4S traffic descriptor.

2 . The method of claim 1 , wherein detecting a need to support a LAS traffic flow includes detecting an application request from an application running on the UE requesting L4S treatment for application traffic corresponding to the requesting application.

3 . The method of claim 1 , wherein detecting a need to support a LAS traffic flow includes detecting an L4S indicator in incoming application traffic, said incoming application traffic being from an application running on the UE.

4 . The method of claim 1 , wherein said set of URSP rules also include rules for non LAS flows, rules for non-L4S flows not including said L4S traffic type descriptor.

5 . The method of claim 4 , further comprising:

determining if a PDU session corresponding to the determined URSP rule is already ongoing.

6 . The method of claim 5 , further comprising:

in response to determining that a PDU session corresponding to the determined URSP rule is already ongoing, assigning a first application packet flow to an on-going PDU session that supports L4S.

7 . The method of claim 6 , wherein assigning the first application packet flow to an on-going PDU session that supports L4S includes:

sending a PDU session modification request to an AMF.

8 . The method of claim 6 , further comprising:

in response to determining that a PDU session corresponding to the determined URSP policy is not already ongoing, establishing a new PDU session supporting an L4S packet flow and assigning the first application packet flow to the new PDU session.

9 . The method of claim 8 , wherein establishing a new PDU session supporting an LAS packet flow includes:

sending a PDU session establishment request to an AMF to establish the new PDU session supporting the L4S packet flow.

10 . The method of claim 1 , further comprising:

receiving the first rule at the UE, prior to storing the first rule at the UE, said first rule being from a PCF and being communicated to the UE via an AMF as part of a UE policy update.

11 . The method of claim 10 , wherein said set of URSP rules includes a plurality of URSP rules including a L4S traffic descriptor and a plurality of rules which do not include a L4S traffic descriptor.

12 . A User Equipment (UE), comprising:

memory storing a set of UE Route Selection Policy (URSP) rules, said set of URSP rules including at least a first rule including a LAS traffic descriptor; and

a processor configured to:

operate the UE to detect a need to support a LAS traffic flow by detecting i) an application request from an application running on the UE requesting L4S treatment for application traffic corresponding to the requesting application or ii) an LAS indicator in incoming application traffic, said incoming application traffic being from an application running on the UE; and

determine the URSP rule stored in the UE to use in response to detecting the need to support the L4S traffic flow, said determining including identifying a stored URSP rule that includes an L4S traffic descriptor.

13 . The UE of claim 12 , wherein said processor is configured, as part of being configured operate the UE to detect a need to support a L4S traffic flow, to:

detect an application request from an application running on the UE requesting LAS treatment for application traffic corresponding to the requesting application.

14 . The UE of claim 12 , wherein said processor is further configured, as part of being configured operate the UE to detect a need to support a L4S traffic flow, to:

detect an L4S indicator in incoming application traffic, said incoming application traffic being from an application running on the UE.

15 . The UE of claim 14 , wherein said processor is further configured to:

operate the UE to assign a first application packet flow to an on-going PDU session that supports L4S, in response to determining that a PDU session corresponding to the determined URSP rule is already ongoing.

16 . The UE of claim 15 , said processor is configured to:

operate the UE to send a PDU session modification request to an AMF, as part of being configured to operate the UE to assign the first application packet flow to an on-going PDU session that supports L4S.

17 . The UE of claim 15 , wherein said processor is further configured to:

operate the UE to establish a new PDU session supporting an LAS packet flow and assigning the first application packet flow to the new PDU session, in response to determining that a PDU session corresponding to the determined URSP policy is not already ongoing.

18 . The UE of claim 17 , wherein said processor is configured to:

operate the UE to send a PDU session establishment request to an AMF to establish the new PDU session supporting the L4S packet flow, as part of being configured to operate the UE to establish a new PDU session supporting an LAS packet flow.

19 . A method of operating a policy control function (PCF) apparatus, the method comprising:

generating a UE Route Selection Policy (URSP) rule which includes a connection capability identifier indicating a LAS connections capability; and

communicating the URSP rule indicating a LAS connections capability to a user equipment (UE).

20 . The method of claim 19 , wherein communicating the URSP rule indicating the L4S connections capability to a UE includes:

sending the URSP rule to the UE via an Access and Mobility Management Function (AMF) as part of a URSP update, said URSP rule including a traffic descriptor which includes the connection capability identifier indicating the L4S connections capability.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2023
From: VAIDYA, MAULIK
To: CHARTER COMMUNICATIONS OPERATING, LLC
Reel/Frame 063912/0199 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 8, 2023
From: SAHIN, YILDIRIM
To: CHARTER COMMUNICATIONS OPERATING, LLC
Reel/Frame 063901/0658 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 8, 2023
From: RUSSELL, PAUL L., JR.
To: CHARTER COMMUNICATIONS OPERATING, LLC
Reel/Frame 063901/0665 →
Continuity (1)
Related Publication 20240388989A1 · Nov 21, 2024
References Cited (38)
US 12413653B1 · Yi · 2025 [cited by applicant]
US 20020150060A1 · Montpetit · 2002 [cited by applicant]
US 20240056401A1 · Nádas · 2024 [cited by examiner]
US 20240236765A1 · Xu et al. · 2024 [cited by applicant]
US 20240334243A1 · Taneja · 2024 [cited by applicant]
US 20240373448A1 · Fang · 2024 [cited by examiner]
US 20250016883A1 · Yang et al. · 2025 [cited by applicant]
US 20250126064A1 · Ke · 2025 [cited by applicant]
US 20250168072A1 · Karampatsis · 2025 [cited by examiner]
EP 4391639A1 · 2024 [cited by applicant]
WO 2023046118A1 · 2023 [cited by applicant]
WO 2024013545A1 · 2024 [cited by applicant]
Change Request, Resolution of EN for L4S, SA WG2 Meeting #156e, S2-2306189, E-meeting, Apr. 17, 2023-Apr. 21, 2023, 4 pages. [cited by applicant]
Change Request, Standardized traffic categories in URSP, 3GPP TSG-CT WG1 Meeting #141e, C1-232295, Online Apr. 17-21, 2023, 15 pages. [cited by applicant]
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, International Search Report and Written Opinion of the International Searching Authority f… [cited by applicant]
Iyengar et al., RFC 9000, QUIC: A UDP-Based Multiplexed and Secure Transport, Internet Engineering Task Force (IETF), May 2021, 151 pages. [cited by applicant]
Briscoe et al., RFC 9330, Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture, Internet Engineering Task Force (IETF), Jan. 2023, 36 pages. [cited by applicant]
De Schepper et al., RFC 9331, The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S), Internet Engineering Task Force (IETF), Jan. 2023, 52 pages. [cited by applicant]
De Schepper et al., RFC 9332, Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S), Internet Engineering Task Force (IETF), Jan. 2023, 52 pages. [cited by applicant]
Ramakrishnan et al., Request for Comments: 3168, The Addition of Explicit Congestion Notification (ECN) to IP, Network Working Group, Sep. 2001, 63 pages. [cited by applicant]
Kohler et al., Request for Comments: 4340, Datagram Congestion Control Protocol (DCCP), Network Working Group, Mar. 2006, 129 pages. [cited by applicant]
Randall R. Stewart, Request for Comments: 4960, Stream Control Transmission Protocol, Network Working Group, Sep. 2007, 96 pages, downloaded from https://www.rfc-editor.org/rfc/rfc4960.txt. [cited by applicant]
Sarker et al., Request for Comments: 8888, RTP Control Protocol (RTCP) Feedback for Congestion Control, Internet Engineering Task Force (IETF), Jan. 2021, 9 pages, downloaded from https://www.rfc-editor.org/rfc/rfc8888.… [cited by applicant]
Briscoe et al., More Accurate ECN Feedback in TCP, Workgroup: TCP Maintenance & Minor Extensions (tcpm), Internet-Draft: draft-ietf-tcpm-accurate-ecn-22, Updates: 3168 (if approved), Intended Status: Standards Track dat… [cited by applicant]
Change Request, Connection capabilities defined in GSMA PRD NG. 135, 3GPP TSG-CT WG1 Meeting #140, C1-230083, Athens, Greece, Feb. 27-Mar. 3, 2023, 13 pages. [cited by applicant]
Change Request, Standardized traffic categories in URSP, 3GPP TSG-CT WG1 Meeting #140, C1-230314, Athens, Greece, Feb. 27-Mar. 3, 2023, 15 pages. [cited by applicant]
LS reply on Traffic Categories, ENSWI#20 Doc 004, 3GPP TSG-CT WG1 Meeting #140, C1-230713, Athens, Greece, Feb. 27-Mar. 3, 2023, 4 pages. [cited by applicant]
Third Generation Partnership Project (3GPPTM), Draft Meeting Report for TSG CT WGT meeting: 140, Athens, Geneva, Feb. 27, 2023 to Mar. 3, 2023, 365 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 18), 3GPP TS 23.003 V18.1.0, Mar. 2023, 152 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18), 3GPP TS 23.501 V18.1.0, Mar. 2023, 667 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18), 3GPP TS 23.502 V18.1.1 Apr. 2023, 829 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 18), 3GPP TS 23.503 V18.1.0, Mar. 2023, 165 … [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18), 3GPP TS 24.501 V18.2.1, Mar. 2023, 1057 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User Equipment (UE) policies for 5G System (5GS); Stage 3 (Release 18), 3GPP TS 24.526 V18.0.0, Sep. 2022, 59 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User Equipment (UE) policies for 5G System (5GS); Stage 3, (Release 18), 3GPP TS 24.526 V18.2.0, Mar. 2023, 64 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 17), 3GPP TS 38.300 V17.4.0, Mar. 2023, 210 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; PDU Session User Plane Protocol (Release 17), 3GPP TS 38.415 V17.0.0, Apr. 2022, 18 pages. [cited by applicant]
LTE; 5G; Interface between the Control Plane and the User Plane nodes (3GPP TS 29.244 version 16.5.0 Release 16) ETSI TS 129 244, V16.5.0, Nov. 2020, 317 pages. [cited by applicant]