IP Library › Granted Patent US 12,463,911
Granted Patent B2
US 12,463,911 · App. 18/586,341 · Granted Nov 4, 2025

Methods and apparatus relating to residential gateway support for low latency, low loss and scalable throughput (L4S) service in a system including an AMF

Inventors: Yildirim Sahin (Englewood, CO); Paul L. Russell, Jr. (Lawrence, NJ)
Assignee: Charter Communications Operating, LLC
H04L47/26H04L67/141H04L67/147H04W28/0236
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,911
App. No.
18/586,341
Granted
Nov 4, 2025
Kind
B2
Abstract

A residential gateway (RG), e.g., a 5G-RG, indicates its support for ECN marking for L4S in uplink and/or downlink via a PDU session request message, e.g., a PDU session establishment request message, communicated from the RG via a 3GPP radio access network (RAN) to a core network, e.g., a 5GC. The indication, in some embodiments, is provided in either: a Session Management (SM) capability field, e.g., a 5GSM capability field, or as a new indication, which is included as part of a N1 SM container. A RG may, and sometimes does, determine congestion in its buffers/queues and perform ECN marking and report if traffic congestion is being experienced within its own buffers/queues for uplink and/or downlink traffic. In some such embodiments, both an RG and a RAN can, and sometimes do, perform ECN marking for L4S simultaneously in both directions (i.e. uplink and downlink).

Claims (36)

1 . A communications method, the method comprising:

operating a residential gateway (RG) to communicate, via a 3GPP access network node, a first protocol data unit (PDU) session request message to an access and mobility management function (AMF), said first PDU session request message including RG L4S (Low Latency Low Loss and Scalable Throughput) capability information in at least one of: i) a capability field including an indication of support by the RG for L4S or ii) a N1 SM (N1 session management) container including an indication of support by the RG for L4S; and

operating the RG to receive a response message in response to the first PDU session request message.

2 . The communications method of claim 1 , wherein said response message includes an indicator indicating support for L4S.

3 . The communications method of claim 1 , wherein said first PDU session request message is one of a PDU session establishment request message or a PDU session modification request message.

4 . The communications method of claim 2 , further comprising:

storing RG subscription data indicating whether or not the RG is allowed to perform ECN (explicit congestion notification) marking.

5 . The communications method of claim 4 , further comprising:

operating a session management function (SMF), assigned to provide session management services for the PDU session corresponding to the first protocol data unit (PDU) session request message, to retrieve stored subscription information corresponding to the RG including L4S information corresponding to the RG.

6 . The communications method of claim 5 , further comprising:

operating said SMF to select, based on L4S information included in the retrieved subscription information, a policy control function (PCF) to be used to support the PDU session to which the first PDU session request message relates.

7 . The communication method of claim 6 , wherein said SMF selects a PCF which supports L4S when the retrieved L4S information indicates the RG supports ECN marking and selects a PCF which does not support L4S when the retrieved L4S information indicates the RG does not support ECN marking.

8 . The communications method of claim 7 , further comprising:

operating the RG to send a data packet including ECN marking in a header of said data packet as part of said PDU communications session to which the first PDU session request message relates.

9 . The communications method of claim 1 , wherein the RG is a 5G-RG (5G-Residential Gateway) that appears to a 5G network core including said AMF as a user equipment (UE).

10 . The communications method of claim 1 , wherein both the RG and 3GPP access network node perform ECN marking in both the uplink and downlink directions.

11 . A communications system, the system comprising:

a residential gateway (RG) including a first processor configured to:

operate the RG to communicate, via a 3GPP access network node, a first protocol data unit (PDU) session request message to an access and mobility management function (AMF), said first PDU session request message including RG L4S (Low Latency Low Loss and Scalable Throughput) capability information in at least one of: i) a capability field including an indication of support by the RG for L4S or ii) a N1 SM (N1 session management) container including an indication of support by the RG for L4S; and

operate the RG to receive a response message in response to the first PDU session request message.

12 . The communications system of claim 11 , wherein said response message includes an indicator indicating support for L4S.

13 . The communications system of claim 11 , wherein said first PDU session request message is one of a PDU session establishment request message or a PDU session modification request message.

14 . The communications system of claim 12 , further comprising:

a storage device storing RG subscription data indicating whether or not the RG is allowed to perform ECN (explicit congestion notification) marking.

15 . The communications system of claim 14 , further comprising:

a session management function (SMF) including a second processor configured to:

operate the SMF, assigned to provide session management services for the PDU session corresponding to the first protocol data unit (PDU) session request message, to retrieve stored subscription information corresponding to the RG including L4S information corresponding to the RG.

16 . The communications system of claim 15 , wherein said second processor is further configured to:

operate said SMF to select, based on L4S information included in the retrieved subscription information, a policy control function (PCF) to be used to support the PDU session to which the first PDU session request message relates.

17 . The communication system of claim 16 , wherein said SMF is configured to select a PCF which supports L4S when the retrieved L4S information indicates the RG supports ECN marking and to select a PCF which does not support L4S when the retrieved L4S information indicates the RG does not support ECN marking, as part of being configured to operate the SMF to select a PCF.

18 . The communications system of claim 17 , wherein said first processor is further configured to:

operate the RG to send a data packet including ECN marking in a header of said data packet as part of said PDU communications session to which the first PDU session request message relates.

19 . The communications system of claim 11 , wherein the RG is a 5G-RG (5G-Residential Gateway) that appears to a 5G network core including said AMF as a user equipment (UE).

20 . A non-transitory computer readable medium including machine executable instruction which when implemented by a processor of a residential gateway (RG) cause the RG to perform the steps of:

operating the residential gateway (RG) to communicate, via a 3GPP access network node, a first protocol data unit (PDU) session request message to an access and mobility management function (AMF), said first PDU session request message including RG L4S (Low Latency Low Loss and Scalable Throughput) capability information in at least one of: i) a capability field including an indication of support by the RG for L4S or ii) a N1 SM (N1 session management) container including an indication of support by the RG for L4S; and

operate the RG to receive a response message in response to the PDU session request message.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 27, 2024
From: SAHIN, YILDIRIM
To: CHARTER COMMUNICATIONS OPERATING, LLC
Reel/Frame 066580/0505 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 27, 2024
From: RUSSELL, PAUL L., JR.
To: CHARTER COMMUNICATIONS OPERATING, LLC
Reel/Frame 066580/0530 →
Continuity (2)
Provisional Application 63619154 · Jan 9, 2024
Related Publication 20250227069A1 · Jul 10, 2025
References Cited (23)
US 12132636B2 · Clancy et al. · 2024 [cited by applicant]
US 20190052580A1 · Peng et al. · 2019 [cited by applicant]
US 20220124548A1 · Srivastava et al. · 2022 [cited by applicant]
US 20230275842A1 · Ostberg et al. · 2023 [cited by applicant]
US 20240275887A1 · Guo et al. · 2024 [cited by applicant]
US 20250039736A1 · Panigrahi et al. · 2025 [cited by applicant]
US 20250106680A1 · Patil · 2025 [cited by examiner]
US 20250113250A1 · Kahn · 2025 [cited by examiner]
CN 118140461A · 2024 [cited by examiner]
EP 3442182A1 · 2019 [cited by applicant]
KR 20240063536A · 2024 [cited by examiner]
WO WO2025058351A1 · 2025 [cited by examiner]
WO WO2025131857A1 · 2025 [cited by examiner]
Briscoe et al., Request for Comments (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., Request for Comments (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 pa… [cited by applicant]
De Schepper et al., Request for Comments (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]
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.3.0, Sep. 2023, 696 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.4.0, Dec. 2023, 706 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.3.0, Sep. 2023, 899 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Wireless and wireline convergence access support for the 5G System (5GS) (Release 18), 3GPP TS 23.316 V18.3.0, Sep. 2023, 93… [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Wireless and wireline convergence access support for the 5G System (5GS) (Release 18), 3GPP TS 23.316 V18.4.0, Dec. 2023, 94… [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.6.0, Sep. 2023, 211 pages. [cited by applicant]
PCR 23.700-70: New Solution for L4S support in wireline access, SA WG2 Meeting #160, S2-2312144, Chicago, USA, Nov. 13-17, 2023, 5 pages. [cited by applicant]