IP Library Granted Patent US 11,405,845
Granted Patent B2
US 11,405,845 · App. 16/918,738 · Granted Aug 2, 2022

Deep packet inspection in a fronthaul network of a cloud radio access network

Inventors: Irfaan Ahamed Salahuddeen (Acton, MA); Raymond Zachary Lovell (Lowell, MA)
Assignee: CommScope Technologies LLC
H04W40/02H04L5/0044H04L5/0048H04L12/1845H04L69/164H04L69/22H04W4/06H04W24/10H04W72/04H04W72/0413H04W88/085H04W92/20H04L12/189
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 11,405,845
App. No.
16/918,738
Filed
Jul 1, 2020
Granted
Aug 2, 2022
Kind
B2
Art Unit
2466
USPC
370/312
Abstract

A C-RAN includes a plurality of remote units (RUs), each being configured to exchange RF signals with at least one UE. The C-RAN also includes a central unit communicatively coupled to the plurality of RUs via a fronthaul interface. The fronthaul interface includes at least one ETHERNET switch configured to perform deep packet inspection on a received packet in order to determine whether an RU identification is present in the packet. The RU identification, if present in the packet, indicates at least one RU the packet is intended for. When the RU identification is present in the packet, the at least one ETHERNET switch is also configured to communicate, for each of the at least one RU, at least a portion of the packet to the RU based on a comparison of the RU identification with at least one bit pattern for the RU.

Claims (61)

1. A cloud radio access network (C-RAN), comprising:

a plurality of remote units (RUs), each being configured to exchange radio frequency (RF) signals with at least one user equipment (UE);

a central unit communicatively coupled to the plurality of RUs via a fronthaul interface;

at least one ETHERNET switch in the fronthaul interface configured to:

perform deep packet inspection on a received packet in order to determine whether an RU identification is present in the packet,

wherein the RU identification, if present in the packet, indicates at least one RU the packet is intended for;

when the RU identification is present in the packet, communicate at least a portion of the packet to each of the at least one RU based on a comparison of the RU identification with at least one bit pattern for the respective RU; and

wherein when the RU identification is not present in the packet, the at least one ETHERNET switch is configured to communicate the at least a portion of the packet to the at least one RU without performing the comparison.

2. The C-RAN of claim 1 , wherein the central unit is a Distributed Unit (DU) or a Central Unit (CU) configured to operate in a 3GPP Fifth Generation communication system.

3. The C-RAN of claim 1 , wherein the central unit is a baseband controller (BC) configured to operate in a 3GPP Long Term Evolution (LTE) communication system.

4. The C-RAN of claim 1 , wherein the RU identification comprises a plurality of bit positions, where each bit position corresponds to a respective one of the plurality of the RUs.

5. The C-RAN of claim 1 , wherein the ETHERNET switch is further configured to receive the packet from the central unit in a stream of packets; and

wherein the ETHERNET switch is configured to perform deep packet inspection on each packet in the stream of packets.

6. The C-RAN of claim 1 , wherein the ETHERNET switch is further configured to determine the at least one bit pattern for each of the at least one RU.

7. The C-RAN of claim 6 , wherein the at least one bit pattern is selected for each of the at least one RU using a multicast IP address or a multicast MAC address depending on an ETHERNET type of the packet.

8. The C-RAN of claim 1 , wherein the at least one ETHERNET switch is configured to perform deep packet inspection by determining whether an ETHERNET type of the packet indicates:

a reserved predetermined value that indicates inclusion of the RU identification at a first predetermined offset; or

Internet Protocol (IP).

9. The C-RAN of claim 8 , wherein when the ETHERNET type of the packet does not indicate IP or the reserved predetermined value, the at least one ETHERNET switch is configured to communicate the at least a portion of the packet to the at least one RU without performing the comparison.

10. The C-RAN of claim 1 , wherein the at least one ETHERNET switch is configured to perform deep packet inspection by determining whether an IP type of an IP packet, inside the packet, indicates User Datagram Protocol (UDP).

11. The C-RAN of claim 10 , wherein when the IP type of the packet does not indicate UDP, the at least one ETHERNET switch is configured to communicate the at least a portion of the packet to the at least one RU without performing the comparison.

12. The C-RAN of claim 1 , wherein the at least one ETHERNET switch is configured to perform deep packet inspection by determining whether a destination port in a UDP datagram, inside the packet, is in a predetermined range of ports or equals a predetermined UDP port number.

13. The C-RAN of claim 12 , wherein the destination port in the UDP datagram is not in a predetermined range of ports and does not equal a predetermined UDP port number, the at least one ETHERNET switch is configured to communicate the at least a portion of the packet to the at least one RU without performing the comparison.

14. The C-RAN of claim 1 ,

wherein the packet is an ETHERNET packet; and

wherein the RU identification is in an in-phase, quadrature-phase (I/Q) packet, a Layer 1 packet, or a Layer 2 packet,

wherein the I/Q packet, Layer 1 packet, or Layer 2 packet is contained in a UDP datagram, which is contained in an IP packet, which is contained in the ETHERNET packet.

15. The C-RAN of claim 1 , wherein one or more of the RUs individually implements multiple radio unit instances, each operating on a different carrier and being assigned a radio unit identifier.

16. The C-RAN of claim 1 ,

wherein a filter rule is set up for each or multiple radio unit instances in a radio unit;

wherein each of the multiple radio unit instances informs the ETHERNET switch of a downlink multicast IP address range of interest, a UDP port number range of interest, and an RU identification of interest;

wherein the ETHERNET switch periodically polls each radio unit instance to determine if its respective filter rule still exists.

17. A method performed by a switch in a cloud radio access network (C-RAN), the method comprising:

performing deep packet inspection on a packet, received from a central unit, in order to determine whether an RU identification is present in the packet,

wherein the RU identification, if present in the packet, indicates at least one radio unit (RU) the packet is intended for; and

when the RU identification is present in the packet, communicating at least a portion of the packet to each of the at least one RU based on a comparison of the RU identification with at least one bit pattern for the respective RU; and

wherein when the RU identification is not present in the packet, the at least a portion of the packet is communicated to the at least one RU without performing the comparison.

18. The method of claim 17 , wherein the central unit is a Distributed Unit (DU) or a Central Unit (CU) configured to operate in a 3GPP Fifth Generation communication system.

19. The method of claim 17 , wherein the central unit is a baseband controller (BC) configured to operate in a 3GPP Long Term Evolution (LTE) communication system.

20. The method of claim 17 , wherein the RU identification comprises a plurality of bit positions, where each bit position corresponds to a respective one of the plurality of the RUs.

21. The method of claim 17 , wherein the packet is received from the central unit in a stream of packets; and

wherein deep packet inspection is performed on each packet in the stream of packets.

22. The method of claim 17 , further comprising determining the at least one bit pattern for each of the at least one RU.

23. The method of claim 22 , wherein the at least one bit pattern is selected for each of the at least one RU using a multicast IP address or a multicast MAC address depending on an ETHERNET type of the packet.

24. The method of claim 17 , wherein performing deep packet inspection comprises determining whether an ETHERNET type of the packet indicates:

a reserved predetermined value that indicates inclusion of the RU identification at a first predetermined offset; or

Internet Protocol (IP).

25. The method of claim 24 , wherein when the ETHERNET type of the packet does not indicate IP or the reserved predetermined value, the at least a portion of the packet is communicated to the at least one RU without performing the comparison.

26. The method of claim 17 , wherein performing deep packet inspection comprises determining whether an IP type of an IP packet, inside the packet, indicates User Datagram Protocol (UDP).

27. The method of claim 26 , wherein when the IP type of the packet does not indicate UDP, the at least a portion of the packet is communicated to the at least one RU without performing the comparison.

28. The method of claim 17 , wherein performing deep packet inspection comprises determining whether a destination port in a UDP datagram, inside the packet, is in a predetermined range of ports or equals a predetermined UDP port number.

29. The method of claim 28 , wherein the destination port in the UDP datagram is not in a predetermined range of ports and does not equal a predetermined UDP port number, the at least a portion of the packet is communicated to the at least one RU without performing the comparison.

30. The method of claim 17 ,

wherein the packet is an ETHERNET packet; and

wherein the RU identification is in an in-phase, quadrature-phase (I/Q) packet, a Layer 1 packet, or a Layer 2 packet,

wherein the I/Q packet, Layer 1 packet, or Layer 2 packet is contained in a UDP datagram, which is contained in an IP packet, which is contained in the ETHERNET packet.

31. The method of claim 17 , wherein one or more of the RUs individually implements multiple radio unit instances, each operating on a different carrier and being assigned a radio unit identifier.

32. The method of claim 17 ,

wherein a filter rule is set up for each or multiple radio unit instances in a radio unit;

wherein each of the multiple radio unit instances informs the switch of a downlink multicast IP address range of interest, a UDP port number range of interest, and an RU identification of interest;

wherein the switch periodically polls each radio unit instance to determine if its respective filter rule still exists.

Assignments (11)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2025
From: COMMSCOPE TECHNOLOGIES LLC
To: OUTDOOR WIRELESS NETWORKS LLC
Reel/Frame 071712/0070 →
PARTIAL TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded May 8, 2025
From: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
To: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 071226/0923 →
PARTIAL TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 069889/FRAME 0114 Recorded May 8, 2025
From: APOLLO ADMINISTRATIVE AGENCY LLC
To: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 071234/0055 →
PARTIAL TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 60752/0001 Recorded May 6, 2025
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 071189/0001 →
PARTIAL RELEASE OF SECURITY INTEREST AT REEL/FRAME 058843/0712 Recorded May 2, 2025
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC; COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 071156/0801 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 058875/0449 Recorded Dec 19, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC (F/K/A ARRIS ENTERPRISES, INC.); COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 069743/0057 →
SECURITY INTEREST Recorded Dec 17, 2024
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE INC., OF NORTH CAROLINA; OUTDOOR WIRELESS NETWORKS LLC; RUCKUS IP HOLDINGS LLC
To: APOLLO ADMINISTRATIVE AGENCY LLC
Reel/Frame 069889/0114 →
SECURITY INTEREST Recorded Nov 19, 2021
From: ARRIS SOLUTIONS, INC.; ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA; RUCKUS WIRELESS, INC.
To: WILMINGTON TRUST
Reel/Frame 060752/0001 →
ABL SECURITY AGREEMENT Recorded Nov 15, 2021
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 058843/0712 →
TERM LOAN SECURITY AGREEMENT Recorded Nov 15, 2021
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 058875/0449 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2020
From: SALAHUDDEEN, IRFAAN AHAMED; LOVELL, RAYMOND ZACHARY
To: COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 053380/0937 →
Continuity (4)
Provisional Application 62956402 · Jan 2, 2020
Provisional Application 62895625 · Sep 4, 2019
Provisional Application 62870025 · Jul 2, 2019
Related Publication 20210007039A1 · Jan 7, 2021