IP Library Granted Patent US 12,279,156
Granted Patent B2
US 12,279,156 · App. 17/335,655 · Granted Apr 15, 2025

Traffic timing control for an open radio access network in a cloud radio access network system

Inventors: Wessam Afifi Ahmed (Plano, TX); Young-Han Nam (Plano, TX); Sridhar Rajagopal (Plano, TX); Rasiklal Kachhla (Plano, TX)
Assignee: Mavenir Systems, Inc.
H04W28/06H04L47/27H04W8/24H04W56/0045H04W72/04
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,279,156
App. No.
17/335,655
Granted
Apr 15, 2025
Kind
B2
Abstract

There is provided a method of operating an Open Radio Access Network (O-RAN) having an O-RAN radio unit (O-RU) and an O-RU controller. The method includes sending, from the O-RU to the O-RU controller, (i) a message informing that the O-RU supports a feature such as (a) a plurality of delay management profiles, and/or (b) a plurality of transmission window sizes, and (ii) a report of capabilities of the O-RU, where the report includes a parameter such as (a) a quantity of supported delay management profiles, (b) supported window sizes for each of the plurality of delay management profiles, and/or (c) a supported window offset for each of the plurality of delay management profiles. The O-RU controller configures the O-RU based on the feature and the parameter.

Claims (52)

1. A method of operating an Open Radio Access Network (O-RAN) having an O-RAN radio unit (O-RU) and an O-RU controller, comprising:

sending, from said O-RU to said O-RU controller, a message informing that said O-RU supports features including (a) a plurality of delay management profiles, and (b) a plurality of transmission window sizes; and

sending, from said O-RU to said O-RU controller, a report of capabilities of said O-RU, wherein said report comprises parameters including (a) a quantity of supported delay management profiles, (b) supported window sizes for each of said plurality of delay management profiles, and (c) a supported window offset for each of said plurality of delay management profiles;

wherein said O-RU controller configures said O-RU based on said features and said parameters;

wherein each of said plurality of delay management profiles is defined in terms of a subcarrier spacing (SCS) and a bandwidth (BW).

2. The method of claim 1 , wherein each of said plurality of delay management profiles is given a delay management profile identification.

3. The method of claim 1 , wherein said O-RAN also includes an O-RAN distributed unit (O-DU), and said method further comprises:

sending, from said O-DU to said O-RU, in a control-plane message, a section extension that includes a delay management profile identification (ID) that identifies a delay management profile to be used for a user-plane resource.

4. The method of claim 3 , wherein said delay management profile ID refers to delay parameters of a control-plane message.

5. The method of claim 1 , wherein said O-RAN also includes an O-RAN distributed unit (O-DU), and said method further comprises:

sending, from said O-DU to said O-RU, in a control-plane message, a section extension that indicates a transmit window and a delay offset to be used for a time/frequency resource.

6. The method of claim 1 , wherein said O-RU controller statically links, via a management-plane interface, a delay management profile in said plurality of delay management profiles, to traffic selected from the group consisting of user-plane traffic and control-plane traffic.

7. The method of claim 1 , wherein said O-RU controller configures said O-RU, via a management-plane interface, with a window size from said supported set of window sizes, and a window offset from said supported window offsets, for traffic selected from the group consisting of user-plane traffic and control-plane traffic.

8. The method of claim 1 , wherein said O-RU controller configures said O-RU via a management-plane interface by marking control-plane traffic as non-delay managed traffic.

9. The method of claim 1 ,

wherein said O-RU controller resides in a service management and orchestration system (SMO), and

wherein said O-RU controller configures said O-RU in communications conducted between said O-RU controller and said O-RU via a management-plane interface.

10. An Open Radio Access Network Radio Unit (O-RU) comprising electronic circuity adapted to perform operations of:

sending to an O-RU controller in an Open Radio Access Network (O-RAN), a message informing that said O-RU supports features including (a) a plurality of delay management profiles, and (b) a plurality of transmission window sizes;

sending to said O-RU controller, a report of capabilities of said O-RU, wherein said report comprises parameters including (a) a quantity of supported delay management profiles, (b) supported window sizes for each of said plurality of delay management profiles, and (c) a supported window offset for each of said plurality of delay management profiles;

receiving from said O-RU controller, configuration data based on said features and said parameters; and

operating said O-RU in accordance with said configuration data,

wherein each of said plurality of delay management profiles is defined in terms of a subcarrier spacing (SCS) and a bandwidth (BW).

11. The O-RU of claim 10 , wherein each of said plurality of delay management profiles is given a delay management profile identification.

12. The O-RU of claim 10 , wherein said electronic circuitry is further adapted to perform an operation of:

receiving, from an Open Radio Access Network Distributed Unit (O-DU) in said O-RAN, in a control-plane message, a section extension that includes a delay management profile identification (ID) that identifies a delay management profile to be used for a user-plane resource.

13. The O-RU of claim 12 , wherein said delay management profile ID refers to delay parameters of a control-plane message.

14. The O-RU of claim 10 , wherein said electronic circuitry is further adapted to perform an operation of:

receiving from an Open Radio Access Network Distributed Unit (O-DU) in said O-RAN, in a control-plane message, a section extension that indicates a transmit window and a delay offset to be used for a time/frequency resource.

15. The O-RU of claim 10 , wherein said O-RU controller statically links, via a management-plane interface, a delay management profile in said plurality of delay management profiles, to traffic selected from the group consisting of user-plane traffic and control-plane traffic.

16. The O-RU of claim 10 , wherein said O-RU controller configures said O-RU, via a management-plane interface, with a window size from said supported set of window sizes, and a window offset from said supported window offsets, for traffic selected from the group consisting of user-plane traffic and control-plane traffic.

17. The O-RU of claim 10 , wherein said O-RU controller configures said O-RU via a management-plane interface by marking control-plane traffic as non-delay managed traffic.

18. The O-RU of claim 10 ,

wherein said O-RU controller resides in a service management and orchestration system (SMO), and

wherein said O-RU controller configures said O-RU in communications conducted between said O-RU controller and said O-RU via a management-plane interface.

19. An Open Radio Access Network Radio Unit controller (O-RU controller) comprising electronic circuity adapted to perform operations of:

receiving, from an Open Radio Access Network Radio Unit (O-RU) in an Open Radio Access Network (O-RAN), a message informing that said O-RU supports features including (a) a plurality of delay management profiles, and (b) a plurality of transmission window sizes;

receiving, from said O-RU to said O-RU controller, a report of capabilities of said O-RU, wherein said report comprises parameters including (a) a quantity of supported delay management profiles, (b) supported window sizes for each of said plurality of delay management profiles, and (c) a supported window offset for each of said plurality of delay management profiles; and

configuring said O-RU based on said features and said parameters;

wherein each of said plurality of delay management profiles is defined in terms of a subcarrier spacing (SCS) and a bandwidth (BW).

20. The O-RU controller of claim 19 , wherein each of said plurality of delay management profiles is given a delay management profile identification.

21. The O-RU controller of claim 19 , wherein said O-RAN also includes an O-RAN distributed unit (O-DU), and wherein said O-DU sends to said O-RU, in a control-plane message, a section extension that includes a delay management profile identification (ID) that identifies a delay management profile to be used for a user-plane resource.

22. The O-RU controller of claim 21 , wherein said delay management profile ID refers to delay parameters of a control-plane message.

23. The O-RU controller of claim 19 ,

wherein said O-RAN also includes an O-RAN distributed unit (O-DU), and

wherein said O-DU sends to said O-RU, in a control-plane message, a section extension that indicates a transmit window and a delay offset to be used for a time/frequency resource.

24. The O-RU controller of claim 19 , wherein said electronic circuitry is further adapted to perform an operation of statically linking, via a management-plane interface, a delay management profile in said plurality of delay management profiles, to traffic selected from the group consisting of user-plane traffic and control-plane traffic.

25. The O-RU controller of claim 19 , wherein said electronic circuitry is further adapted to perform an operation of configuring said O-RU, via a management-plane interface, with a window size from said supported set of window sizes, and a window offset from said supported window offsets, for traffic selected from the group consisting of user-plane traffic and control-plane traffic.

26. The O-RU controller of claim 19 , wherein said electronic circuitry is further adapted to perform an operation of configuring said O-RU via a management-plane interface by marking control-plane traffic as non-delay managed traffic.

27. The O-RU controller of claim 19 ,

wherein said O-RU controller resides in a service management and orchestration system (SMO), and

wherein said O-RU controller configures said O-RU in communications conducted between said O-RU controller and said O-RU via a management-plane interface.

Assignments (13)
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 069113 AND FRAME 0558 Recorded Jul 31, 2025
From: GLAS USA LLC
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072308/0172 →
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 067565 AND FRAME 0678 Recorded Jul 29, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0421 →
GRANT OF SECURITY INTEREST - PATENTS Recorded Jul 29, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: GLAS USA LLC
Reel/Frame 072245/0764 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0041 →
RELEASE OF SECURITY INTERESTS (SYNDICATED) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0121 →
SECURITY INTEREST Recorded Jul 28, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: BLUE TORCH FINANCE LLC
Reel/Frame 072268/0439 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 4, 2024
From: MAVENIR SYSTEMS, INC.
To: GLAS USA LLC
Reel/Frame 069113/0558 →
RELEASE OF SECURITY INTEREST Recorded Oct 4, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 069113/0596 →
SECURITY INTEREST Recorded Aug 30, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 068822/0966 →
SECURITY INTEREST Recorded May 29, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 067565/0678 →
SECURITY AGREEMENT Recorded Jul 13, 2022
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 060641/0242 →
SECURITY AGREEMENT Recorded Aug 18, 2021
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 057221/0801 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 1, 2021
From: AHMED, WESSAM AFIFI; NAM, YOUNG-HAN; RAJAGOPAL, SRIDHAR; KACHHLA, RASIKLAL
To: MAVENIR SYSTEMS, INC.
Reel/Frame 056403/0295 →
Continuity (2)
Provisional Application 63034067 · Jun 3, 2020
Related Publication 20210385686A1 · Dec 9, 2021
References Cited (29)
US 5905715A · Azarmi · 1999 [cited by examiner]
US 20100309281A1 · Lim · 2010 [cited by examiner]
US 20120230310A1 · Roy · 2012 [cited by examiner]
US 20130102312A1 · Nilsson · 2013 [cited by examiner]
US 20150257024A1 · Baid · 2015 [cited by examiner]
US 20190053120A1 · Park · 2019 [cited by examiner]
US 20190313288A1 · Li · 2019 [cited by examiner]
US 20200053777A1 · Babaei · 2020 [cited by examiner]
US 20200305159A1 · Raghothaman · 2020 [cited by examiner]
US 20200314826A1 · Sharma · 2020 [cited by examiner]
US 20210195635A1 · Wänstedt · 2021 [cited by examiner]
US 20210204148A1 · Chou · 2021 [cited by examiner]
US 20210258866A1 · Chou · 2021 [cited by examiner]
US 20210314211A1 · Grayson · 2021 [cited by examiner]
US 20210385169A1 · Urman · 2021 [cited by examiner]
US 20220158897A1 · Chou · 2022 [cited by examiner]
US 20220159525A1 · Chou · 2022 [cited by examiner]
US 20220201796A1 · Nakata · 2022 [cited by examiner]
US 20220295309A1 · Akhtar · 2022 [cited by examiner]
WO WO2018035489A1 · 2018 [cited by examiner]
WO WO2021090444A1 · 2021 [cited by examiner]
WO WO2021117245A1 · 2021 [cited by examiner]
WO WO2021144976A1 · 2021 [cited by examiner]
WO WO2021166044A1 · 2021 [cited by examiner]
ORAN-WG1.OAM Architecture v01.00 “O-RAN Operations and Maintenance Architecture”, O-RAN Alliance, Working Group 1, Jul. 2019. [cited by applicant]
ORAN-WG4.CUS.0-v02.00: “O-RAN Fronthaul Working Group Control, User and Synchronization Plane Specification” Release 02.00, Jul. 2019. [cited by applicant]
Extended European Search Report for corresponding European application EP21177553 9 pages, dated Oct. 11, 2021. [cited by applicant]
ORAN-WG4.CUS.0-v03 “Control, User and Synchronization Plane Specification”, O-RAN Alliance, Working Group 4, 2020. [cited by applicant]
ORAN-WG4.MP.0-v02.00: “O-RAN Fronthaul Working Group Management Plane Specification” Release 02.00, Aug. 2019. [cited by applicant]