# US 2021/0243839 A1 · Data analysis and configuration of a distributed radio access network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0243839 A1
- Document ID: US20210243839A1
- Status: Published application
- Kind: A1
- Application number: 17/150,290
- Filed: 2021-01-15
- Published: 2021-08-05
- Earliest claimed: 2020-02-04
- Assignees: CommScope Technologies LLC
- Applicants: CommScope Technologies LLC
- Inventors: Vijayaraghavan Krishnaswamy; Pavan Kulkarni; Kesava Rao Vetapalem; Swami Rangaiah Damerla; Prashant D Paraddi
- Web page: https://patentgrep.com/patent/US20210243839A1

## CPC

- H04W 88/085: {Access point devices with remote components}
- H04W 24/04: Arrangements for maintaining operational condition
- H04W 24/10: Scheduling measurement reports {; Arrangements for measurement reports}
- H04W 24/02: Arrangements for optimising operational condition
- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04W 74/08: Non-scheduled access, e.g. ALOHA (hybrid access H04W74/02)
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 92/10: between terminal device and access point, i.e. wireless air interface
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A distributed radio access network (RAN) includes a plurality of remote units (RUs), each being configured to exchange RF signals with at least one UE. The distributed RAN also includes a central unit communicatively coupled to the plurality of RUs via a fronthaul and/or midhaul network comprising one or more ethernet switches. The distributed RAN also includes at least one processor configured to receive diagnostic information relating at least to processing performed for at least two layers of a network and/or air interface implemented by the distributed RAN; identify a system performance problem based on the diagnostic information; search for a cause of the system performance problem using at least a portion of the diagnostic information; and when the cause of the system performance problem is identified using the at least a portion of the diagnostic information, determine at least one action to correct, limit, or circumvent the system performance problem.

## Claims

### Claim 1

A distributed radio access network (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 network comprising one or more ethernet switches;
at least one processor located in the central unit, the RUs, or a combination thereof, wherein the at least one processor configured to:
receive diagnostic information relating at least to processing performed for at least two layers of an air interface implemented by the distributed RAN;
identify a system performance problem based on the diagnostic information using at least one policy;
search for a cause of the system performance problem using at least a portion of the diagnostic information and at least one trigger in the at least one policy; and
when the cause of the system performance problem is identified using the at least a portion of the diagnostic information, determine at least one action to correct, limit, or circumvent the system performance problem.

### Claim 2 (depends on 1)

The distributed RAN of claim 1, wherein the at least one processor is further configured to, when the cause of the system performance problem is not identified, identify and collect additional diagnostic information needed to identify the cause of the system performance problem.

### Claim 3 (depends on 1)

The distributed RAN of claim 1, wherein the central unit is a Third Generation Partnership Project Fifth Generation (5G) Central Unit or Distributed Unit, and the air interface is a 5G air interface.

### Claim 4 (depends on 1)

The distributed RAN of claim 1, wherein the central unit is a baseband controller configured and the air interface is a Third Generation Partnership Project Long Term Evolution air interface.

### Claim 5 (depends on 1)

The distributed RAN of claim 1, wherein the central unit is a head unit in a distributed antenna system.

### Claim 6 (depends on 1)

The distributed RAN of claim 1, wherein the at least one action comprises at least one of the following:
changing at least one parameter of the central unit, at least one of the RUs, at least one of the ethernet switches in the fronthaul network, or the at least one UE, or a combination thereof;
power cycling, reinitializing at least one component of at least one of the RUs, at least one of the ethernet switches in the fronthaul network, or the central unit, or a combination thereof;
changing RUs in a combining group for the at least one UE;
deactivating one or more components of at least one of the RUs, at least one of the ethernet switches in the fronthaul network, or the central unit, or a combination thereof;
changing a frequency at which the diagnostic information is collected; and
sending a notification to an operator of the distributed RAN via a management system, wherein the notification indicates a problem that needs further action or analysis.

### Claim 7 (depends on 1)

The distributed RAN of claim 1, wherein the diagnostic information is received from at least one of the RUs, at least one of the ethernet switches, the at least one UE, or a combination thereof.

### Claim 8 (depends on 1)

The distributed RAN of claim 1, wherein the diagnostic information comprises any of the following:
at least one metric used by a Layer-1 (L1) protocol;
at least one metric used by a Layer-2 (L2) protocol;
at least one metric used by a Layer-3 (L3) protocol;
at least one metric related to an interface or tunnel used in the distributed RAN; or
at least one metric related to CPU resources, memory resources, or other storage resources in any device within the distributed RAN.

### Claim 9 (depends on 8)

The distributed RAN of claim 8,
wherein the at least one L1 protocol comprises processing relating to a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH), or a Sounding Reference Signal (SRS);
wherein the at least one L2 protocol comprises radio link control (RLC) or medium access control (MAC); and
wherein the at least one L3 protocol comprises radio resource control (RRC), radio resource management (RRM), or self-organizing network (SON).

### Claim 10 (depends on 1)

The distributed RAN of claim 1, wherein the diagnostic information comprises any of the following:
at least one metric used by a control-plane protocol, comprising Stream Control Transmission Protocol (SCTP), S1 Application Protocol (S1AP) processing, and Internet Key Exchange (IKE);
at least one metric used by a data-plane protocol, comprising GPRS Tunneling Protocol (GTP) and Selective Data Adaptive Protocol (SDAP);
at least one metric used by Packet Data Convergence Protocol (PDCP) or IP security (IPSec) protocol; and
at least one metric used by timing systems, comprising Global Positioning System (GPS), Precision Time Protocol (PTP), and Network Time Protocol (NTP);
femto application platform interface (FAPI) messaging between a L2 component and a Layer-1 component in the central unit;
in-phase, quadrature-phase (IQ) messaging between at least one of the RUs and the central unit; or
debugging logs or other logs relating to communication between the central unit and the RUs.

### Claim 11 (depends on 1)

The distributed RAN of claim 1, wherein the at least one processor is configured to identify a system performance problem using at least a portion of the diagnostic information and at least one threshold in the at least one policy.

### Claim 12 (depends on 1)

The distributed RAN of claim 1, wherein the at least one processor is configured to search for the cause of the system performance problem using at least one trigger, in a set of hierarchical triggers, to identify the at least one action.

### Claim 13 (depends on 1)

The distributed RAN of claim 1, wherein the at least one processor is configured to determine the at least one action using at least one trigger to correct, limit, or circumvent the system performance problem.

### Claim 14

A method performed by a distributed radio access network (RAN), the method comprising:
receiving diagnostic information relating at least to processing performed for at least two layers of an air interface implemented by the distributed RAN;
identifying a system performance problem based on the diagnostic information using at least one policy;
searching for a cause of the system performance problem using at least a portion of the diagnostic information and at least one trigger in the at least one policy; and
when the cause of the system performance problem is identified using the at least a portion of the diagnostic information, determining at least one action to correct, limit, or circumvent the system performance problem.

### Claim 15 (depends on 14)

The method of claim 14, further comprising, when the cause of the system performance problem is not identified, identifying and collecting additional diagnostic information needed to identify the cause of the system performance problem.

### Claim 16 (depends on 14)

The method of claim 14, wherein the method is performed by a Third Generation Partnership Project Fifth Generation (5G) Central Unit or Distributed Unit, and the air interface is a 5G air interface.

### Claim 17 (depends on 14)

The method of claim 14, wherein the method is performed by a baseband controller configured and the air interface is a Third Generation Partnership Project Long Term Evolution air interface.

### Claim 18 (depends on 14)

The method of claim 14, wherein the method is performed by a head unit in a distributed antenna system.

### Claim 19 (depends on 14)

The method of claim 14, wherein the at least one action comprises at least one of the following:
changing at least one parameter of a central unit in the distributed RAN, at least one remote unit (RU) in the distributed RAN, at least one of one or more ethernet switches in a fronthaul network of the distributed RAN, or the at least one UE, or a combination thereof;
power cycling, reinitializing at least one component of at least one of the RUs, at least one of the ethernet switches in the fronthaul network, or the central unit, or a combination thereof;
changing RUs in a combining group for the at least one UE;
deactivating one or more components of at least one of the RUs, at least one of the ethernet switches in the fronthaul network, or the central unit, or a combination thereof;
changing a frequency at which the diagnostic information is collected; and
sending a notification to an operator of the distributed RAN via a management system, wherein the notification indicates a problem that needs further action or analysis.

### Claim 20 (depends on 14)

The method of claim 14, wherein the diagnostic information is received from at least one RU in the distributed RAN, at least one ethernet switch in a distributed RAN, at least one UE attached to the distributed RAN, or a combination thereof.

### Claim 21 (depends on 14)

The method of claim 14, wherein the diagnostic information comprises any of the following:
at least one metric used by a Layer-1 (L1) protocol;
at least one metric used by a Layer-2 (L2) protocol;
at least one metric used by a Layer-3 (L3) protocol;
at least one metric related to an interface or tunnel used in the distributed RAN; or
at least one metric related to CPU resources, memory resources, or other storage resources in any device within the distributed RAN.

### Claim 22 (depends on 21)

The method of claim 21, wherein the diagnostic information comprises any of the following:
wherein the at least one L1 protocol comprises processing relating to a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Random Access Channel (RACH), or a Sounding Reference Signal (SRS)
wherein the at least one L2 protocol comprises radio link control (RLC) or medium access control (MAC);
wherein the at least one L3 protocol comprises radio resource control (RRC), radio resource management (RRM), or self-organizing network (SON).

### Claim 23 (depends on 14)

The method of claim 14, wherein the diagnostic information comprises any of the following:
at least one metric used by a control-plane protocol, comprising Stream Control Transmission Protocol (SCTP), S1 Application Protocol (S1AP) processing, and Internet Key Exchange (IKE);
at least one metric used by a data-plane protocol, comprising GPRS Tunneling Protocol (GTP) and Selective Data Adaptive Protocol (SDAP);
at least one metric used by Packet Data Convergence Protocol (PDCP) or IP security (IPSec) protocol; and
at least one metric used by timing systems, comprising Global Positioning System (GPS), Precision Time Protocol (PTP), and Network Time Protocol (NTP);
femto application platform interface (FAPI) messaging between a L2 component and a Layer-1 component in the central unit;
in-phase, quadrature-phase (IQ) messaging between at least one of the RUs and the central unit; or
debugging logs or other logs relating to communication between the central unit and the RUs.

### Claim 24 (depends on 14)

The method of claim 14, wherein the identifying a system performance problem comprises using at least a portion of the diagnostic information and at least one threshold in the at least one policy.

### Claim 25 (depends on 14)

The method of claim 14, wherein the searching for the cause of the system performance problem comprises using at least one trigger, in a set of hierarchical triggers, to identify the at least one action.

### Claim 26 (depends on 14)

The method of claim 14, wherein the determining the at least one action comprises using at least one trigger to correct, limit, or circumvent the system performance problem.
