IP Library Granted Patent US 12,395,885
Granted Patent B2
US 12,395,885 · App. 18/593,573 · Granted Aug 19, 2025

QOS flow management over E1

Inventors: Matteo Fiorani (Solna, SE); Martin Skarve (Enebyberg, SE); Göran Hansson (Stockholm, SE); Christer Gustafsson (Huddinge, SE)
Assignee: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
H04W28/0268H04W28/0252H04W28/06
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,395,885
App. No.
18/593,573
Granted
Aug 19, 2025
Kind
B2
Abstract

A method is provided by a central-unit-control plane (CU-CP) of a network node for exchanging information with a central-unit user plane (CU-UP) of the network node to manage Quality of Service (QoS) flows for the optimization of radio resources. The method includes transmitting, to the CU-UP, a request for flow information for at least one QoS flow and receiving, from the CU-UP of the network node, the flow information for the at least one QoS flow. Based on the flow information for the at least one QoS flow, at least one action is taken.

Claims (78)

1. A method performed by a central unit-control plane (CU-CP) of a network node for exchanging information with a central unit-user plane (CU-UP) of the network node to manage Quality of Service (QoS) flows for the optimization of radio resources, the method comprising:

prior to receiving flow information, establishing a default data radio bearer (DRB) and mapping a plurality of QoS flows to the default DRB;

receiving, from the CU-UP, flow information indicating that data traffic is detected for at least a first QoS flow;

based on the flow information for at least the first QoS flow, removing the first QoS flow from the default DRB and establishing a new DRB for the first QoS flow;

mapping the first QoS flow to the new DRB; and

transmitting, to the CU-UP, message indicating at least one of:

the new DRB has been added, and

a mapping of QoS flows to DRBs has changed.

2. The method of claim 1 , wherein the message comprises an E1 Bearer Context Setup Request message or an E1 Bearer Context Modification Request message.

3. The method of claim 1 , comprising:

transmitting, to the CU-UP, a request for the flow information, and

wherein the flow information is received from the CU-based on the request.

4. The method of claim 3 , wherein:

the request for the flow information comprises a request for the flow information when any downlink or uplink traffic is detected for a first time, and

the flow information for at least the first QoS flow indicates that the downlink or uplink traffic is detected for at least the first QoS for the first time.

5. The method of claim 3 , wherein the request for the flow information comprises at least one of:

a request for the flow information when downlink or uplink traffic is detected a predefined number of times for any one or more of a plurality of QoS flows that include at least the first QoS flow,

a request for the flow information when a given amount of traffic is reached for at least the first QoS flow,

a request for the flow information when any QoS flow within a group of a plurality of QoS flows that are mapped to a default DRB becomes active,

a request for the flow information when an uplink or downlink data rate goes above or below a threshold,

a request for the flow information when a level of QoS for at least the first QoS flow can no longer be fulfilled or when a level of QoS for at least the first QoS flow can be fulfilled again,

a request for a periodic reporting of an uplink or a downlink data rate for at least the first QoS flow, the request comprising a time interval for the periodic reporting, and

a request for a transmitted data volume for at least the first QoS flow.

6. The method of claim 1 , comprising using, by the CU-CP, the flow information to determine how many DRBs to establish.

7. The method of claim 1 , comprising:

receiving, from the CU-UP of the network node, information indicating that at least the first QoS flow has been inactive for an amount of time; and

performing at least one action comprising at least one of:

removing at least the first QoS flow;

remapping at least the first QoS flow from the new DRB to the default DRB; and

determining that there are no additional QoS flows to be mapped to the new DRB and removing the new DRB.

8. A method performed by a central unit-user plane (CU-UP) of a network node for exchanging information with a central unit-control plane (CU-CP) of the network node to manage Quality of Service (QoS) flows for the optimization of radio resources, the method comprising:

prior to detecting flow information, establishing a default Data Radio Bearer (DRB) and mapping a plurality of QoS flows to the default DRB;

detecting flow information for at least a first QoS flow;

based on the flow information for at least the first QoS flow, removing the first QoS flow from the default DRB and mapping at least the first QoS flow to a new DRB;

transmitting, to the CU-CP, flow information indicating that data traffic is detected for at least the first QoS flow; and

receiving, from the CU-CP, a message indicating at least one of:

the new DRB has been added, and

a mapping of QoS flows to DRBs has changed.

9. The method of 8 , wherein the message comprises an E1 Bearer Context Setup Request message or an E1 Bearer Context Modification Request message.

10. The method of claim 8 , comprising:

transmitting, to the CU-UP, a request for the flow information, and

wherein the flow information is received from the CU-based on the request.

11. The method of claim 10 , wherein:

the request for the flow information comprises a request for the flow information when any downlink or uplink traffic is detected for a first time, and

the flow information for the at least first QoS flow indicates that the downlink or uplink traffic is detected for the at least first QoS flow for the first time.

12. The method of claim 10 , wherein the request for the flow information comprises at least one of:

a request for the flow information when downlink or uplink traffic is detected a predefined number of times for any one or more of a plurality of QoS flows that includes at least the first QoS flow,

a request for the flow information when a given amount of traffic is reached for at least the first QoS flow,

a request for the flow information when any QoS flow within a group of a plurality of QoS flows that are mapped to a default DRB becomes active,

a request for the flow information when an uplink or downlink data rate goes above or below a threshold,

a request for the flow information when a level of QoS for at least the first QoS flow can no longer be fulfilled or when a level of QoS for at least the first QoS flow can be fulfilled again,

a request for a periodic reporting of an uplink or a downlink data rate for at least the first QoS flow, the request comprising a time interval for the periodic reporting, and

a request for a transmitted data volume for the at least one flow.

13. The method of claim 8 , comprising using, by the CU-CP, the flow information to determine how many DRBs to establish.

14. The method of claim 8 , comprising:

receiving, from the CU-UP of the network node, information indicating that at least the first QoS flow has been inactive for an amount of time; and

performing at least one action comprising at least one of:

removing at least the first QoS flow;

remapping at least the first QoS flow from the new DRB to the default DRB; and

determining that there are no additional QoS flows to be mapped to the new DRB and removing new DRB.

15. A network node for managing Quality of Service (QoS) flows for the optimization of radio resources, the network node, comprising:

processing circuitry operating as a central unit-control plane (CU-CP) of the network node, the processing circuitry configured to:

prior to receiving flow information, establishing a default data radio bearer (DRB) and mapping a plurality of QoS flows to the default DRB;

receive, from a central unit-user plane (CU-UP) of the network node, the flow information indicating that data traffic is detected for at least a first QoS flow;

based on the flow information for at least the first QoS flow, remove the first QoS flow from the default DRB and establishing a new DRB for the first QoS flow;

map the first QoS flow to the new DRB; and

transmit, to the CU-UP, a message indicating at least one of:

the new DRB has been added, and

a mapping of QoS flows to DRBs has changed.

16. A network node for managing Quality of Service (QoS) flows for the optimization of radio resources, the network node, comprising:

processing circuitry operating as a central unit-user plane (CU-UP) of the network node, the processing circuitry configured to:

prior to detecting flow information, establish a default Data Radio Bearer (DRB) and mapping a plurality of QoS flows to the default DRB;

detect flow information for at least a first QoS flow;

based on the flow information for at least the first QoS flow, remove the first QoS flow from the default DRB and mapping at least the first QoS flow to a new DRB;

transmit, to the central unit-control plane (CU-CP), flow information indicating that data traffic is detected for at least the first QoS flow; and

receive, from the CU-CP, a message indicating at least one of:

the new DRB has been added, and

a mapping of QoS flows to DRBs has changed.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2024
From: FIORANI, MATTEO; SKARVE, MARTIN; HANSSON, GORAN; GUSTAFSSON, CHRISTER
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 066630/0057 →
Continuity (3)
Continuation 17045387
Provisional Application 62653675 · Apr 6, 2018
Related Publication 20240236758A1 · Jul 11, 2024
References Cited (46)
US 8504712B2 · Lee · 2013 [cited by applicant]
US 11329926B2 · Liu · 2022 [cited by examiner]
US 11533651B2 · Liu · 2022 [cited by examiner]
US 11665577B2 · Han · 2023 [cited by examiner]
US 20180368109A1 · Kim · 2018 [cited by examiner]
US 20190069333A1 · Kim · 2019 [cited by examiner]
US 20190075552A1 · Yu · 2019 [cited by examiner]
US 20190182716A1 · Futaki · 2019 [cited by examiner]
US 20190253917A1 · Dao · 2019 [cited by examiner]
US 20190313244A1 · Wang · 2019 [cited by examiner]
US 20190356453A1 · Li · 2019 [cited by examiner]
US 20190357076A1 · Han · 2019 [cited by examiner]
US 20200053814A1 · Minokuchi · 2020 [cited by examiner]
US 20200169913A1 · Byun · 2020 [cited by examiner]
US 20200178326A1 · Sirotkin · 2020 [cited by examiner]
US 20200205050A1 · Shah · 2020 [cited by examiner]
US 20200229023A1 · Ke · 2020 [cited by examiner]
US 20200252813A1 · Li · 2020 [cited by examiner]
US 20200267559A1 · Mahoney · 2020 [cited by examiner]
US 20200275498A1 · Fiorani · 2020 [cited by examiner]
US 20200280937A1 · Yang · 2020 [cited by examiner]
US 20200344719A1 · Luo · 2020 [cited by examiner]
US 20200367109A1 · Chen · 2020 [cited by examiner]
US 20200396631A1 · Han · 2020 [cited by examiner]
US 20210014722A1 · Han · 2021 [cited by examiner]
US 20210099316A1 · Wang · 2021 [cited by examiner]
US 20210160730A1 · Fiorani · 2021 [cited by examiner]
US 20210176658A1 · Wang · 2021 [cited by examiner]
US 20210185755A1 · Kim · 2021 [cited by examiner]
US 20210227378A1 · Wang · 2021 [cited by examiner]
CN 101296493A · 2008 [cited by applicant]
EP 2645764A1 · 2013 [cited by applicant]
TW I31918A · 2009 [cited by applicant]
WO WO2013174335A2 · 2013 [cited by applicant]
3GPP TSG RAN WG3 meeting #97; Berlin, Germany; Source: Huawei; Title: Idle to connected procedure for CP-UP separation (R3-173131)—Aug. 21-25, 2017. [cited by applicant]
3GPP TSG-RAN WG3 #97; Berlin, Germany; Source: Ericsson, AT&T, Intel, Vodafone (Tdoc R3-173334)—Aug. 21-25, 2017. [cited by applicant]
3GPP TSG RAN WG3 Meeting #98; Reno, Nevada; Source: ZTE; Title: Discussion on E1 interface functions (R3-174400)—Nov. 27-Dec. 1, 2017. [cited by applicant]
3GPP TSG-RAN WG3 #99; Athens, Greece; Source: Ericsson; Title: E1 Setup procedure (Tdoc R3-181300)—Feb. 26-Mar. 2, 2018. [cited by applicant]
PCT International Search Report for International application No. PCT/IB2019/052791—Jul. 11, 2019. [cited by applicant]
PCT Written Opinion of the International Searching Authority issued for International application No. PCT/IB2019/052791—Jul. 11, 2019. [cited by applicant]
3GPP TS 23.214 v15.2.0; Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for control and user plane separation of EPC node… [cited by applicant]
Examination Report issued by Intellectual Property India for Application No. 202017042366—Dec. 22, 2021. [cited by applicant]
3GPP TR 38.806 v15.0.0 (Dec. 2017); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study of separation of NR Control Plane (CP) and User Plane (UP) for split option 2 (Release 15… [cited by applicant]
3GPP Draft; Meeting Report—3GPP TSG RAN WG3 AH-1801, Monday, Jan. 22, 2018, chairman Gino Masini (Ericsson); Sophia Antipolis, France. [cited by applicant]
3GPP TSG-RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda Item: 15.1.3; Source: Mediatek Inc. (Session Chair); Title: Report of the LTE breakout session (Nb-Iot) (R2-163133). [cited by applicant]
Extended European Search Report issued for International application No. 24190008.3-1215 / 4436247—Oct. 2, 2024. [cited by applicant]