Baseband P User Guidelines

User Guide

91/1553-LZA 701 6014/1 Uen D

Copyright

© Ericsson AB 2018. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

Trademark List

91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Contents

Contents

1 Concepts 1
1.1 Passive Intermodulation 1
1.2 Baseband P Overview 3
1.3 Cancellation Groups 3
1.4 CPRI Pass-through 5
1.5 Deactivation 5
1.6 CPRI Configuration for Tandem Baseband P 8
1.7 Baseband P Capacity Principles 10
1.8 Dependencies and Limitations 11

2 Features of Baseband P 13
2.1 CPRI Compression 13

3 Planning of Passive Intermodulation 14

3.1 Site Survey Requirements 14

4 Operation of Baseband P 15
4.1 Upgrade SW Load 15
4.2 Configure a 2 Carrier Intra-sector Cancellation Group 15
4.3 Configure a 2 Carrier Cross Sector Cancellation Group 17
4.4 Configure a 3 Carrier Intra-sector Cancellation Group 21
4.5 Configure a Cancellation Group with Partial Receiver
Protection 22
4.6 Re-configure Cancellation Group 24
4.7 Re-configure of Baseband P to a Tandem or a Multi
Standalone Configuration 25

5 Performance Management of Passive Intermodulation 34

5.1 Check Performance KPI 34

91/1553-LZA 701 6014/1 Uen D | 2018-08-20

Baseband P User Guidelines

91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Concepts

1 Concepts

1.1 Passive Intermodulation

Passive InterModulation (PIM) occurs when two or more signals are present in a
passive non-linear device or element. The signals mix or multiply with each other
and generate sum and difference signals. These resulting signals can cause in-
band interference and sensitivity degradation. PIM is becoming an increasingly
significant problem because of the increasingly complex frequency allocations.
There is a need to be able to reduce the impact of PIM in the network by cancel or
suppressing the resulting PIM products in the uplink.

Common PIM sources can be antenna elements, coax connectors, coax cable,
loose mechanical junctions, inconsistent metal to metal contacts between RF
connectors. It is caused by rust, corrosion, loose connections, dirt, oxidation, and
any contamination of these factors.

Example 1 3rd Order Intermodulation Calculation

— 1st Carrier

• Downlink = 1980 MHz

• Uplink = 1900 MHz

— 2nd Carrier

• Downlink = 1940 MHz

• Uplink = 1860 MHz

The operator has noticed Key Performance Indicator (KPI) issues during traffic
busy hours and suspects a PIM problem at one of the cell sites. A test indicated
that the 1st receiver frequency (at 1900 MHz) has a 15-dB increase in traffic
loaded uplink noise compared to the low traffic uplink noise level. The 2nd
receiver frequency (at 1860 MHz) appears to suffer no increased noise level
because of the test.

The 3rd order inter-modulation formula indicates that 2 × 1940 MHz − 1980
MHz = 1900 MHz, it is the same as the 1st receiver carrier frequency, while the
other 3rd order intermodulation formula indicates that 2 × 1980 MHz − 1940
MHz = 2020 MHz (it is not near the 2nd receiver carrier frequency.

Based on the test results and the previous calculation it appears likely that the
suspected cell is being affected by 3rd order PIM generated by the two

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 1

 Baseband P User Guidelines

transmitters and falling on the 1st receiver frequency (at 1900 MHz) has a 15-dB
increase in carrier receiver frequency at 1900 MHz.

“Theoretical” PIM 3IM Spectra for B25 (1940 MHz Tx & 1980 MHz Tx) 10 Mhz Bw carriers

50

0
1840 1850 1860 1870 1880 1890 1900 1910 1920 1930 1940 1950 1960 1970 1980 1990 2000 2010 2020 2030 2040

-50
(dB) - - -

-100

-150

-200

3rd order PIM Frequency

Signals

Band 25 (F1) 1860

MHz Rx

Band 25 (F2) 1900

MHz Rx
L0001902B

Figure 1 3rd Order PIM Spectrum Impacting 1900 MHz

2 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Concepts

1.2 Baseband P Overview

The Baseband P unit is designed to mitigate uplink PIM by adding a digital PIM
correction signal to the uplink Common Public Radio Interface (CPRI) stream
after it leaves the affected radio unit. This is before the stream reaches the digital
unit, where detection and demodulation functions occur. This ensures that any
PIM components in the affected RX band have been substantially reduced before
the digital unit start demodulating the uplink signal stream.

The Baseband P performs this uplink PIM mitigation function by monitoring the
downlink signals and use their waveforms, derived from their downlink CPRI
streams, to compute the frequency components of any PIM that could fall into
(occupy) the affected RX band.

The computed estimate of the PIM frequency waveform in the affected uplink
band is then compared, by a correlation measurement, with the corresponding
uplink waveform derived from the affected RXs uplink CPRI stream.

The unit then computes coefficients to replicate the measured uplink PIM
waveform, in the affected RX band, derived from the downlink CPRI waveforms.

This replicated PIM waveform is then subtracted from the affected uplink CPRI
stream and in the process substantially reducing the PIM components from the
original uplink data.

1.3 Cancellation Groups

A cancellation group is defined as the set of sector carriers including both the
aggressor carrier sectors ,downlink PIM generators, and the affected carrier
sectors, uplink affected receivers. These carriers are selected at the granulation of
a SectorCarrier MO. For example, if a SectorCarrier MO contains 4TX and 2RX, all
4TX or no TX are selected. Both 2RX must be selected to be part of the
cancellation group or no RX at all from the SectorCarrier MO. A subset of TX or
RX cannot be selected. It is possible to select TX and not RX, or select RX and not
TX.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 3

 Baseband P User Guidelines

B25 affected RXs

B25 TX 1 / RX 1
TX 1 TX 2 / RX 2
PIM Cancellation
Group 1
B25 TX 3 / RX 3
TX 2 TX 4 / RX 4 RXs unaffected by

B25 affected RXs

B25 TX 1 / RX 1
TX 1 TX 2 / RX 2
DU or
Baseband P PIM Cancellation
Baseband B25 TX 3 / RX 3 Group 2

TX 2 TX 4 / RX 4 RXs unaffected by

B25 affected RXs

B25 TX 1 / RX 1
TX 1 TX 2 / RX 2
PIM Cancellation
TX 3 / RX 3 Group 3
B25
TX 2 TX 4 / RX 4 RXs unaffected by

B25 TX 1 = 1980 MHz (ch 8140), 10 MHz BW, RX = 1900 MHz (ch 26140)
B25 TX 2 = 1940 MHz (ch 8540), 10 MHz BW, RX = 1860 MHz (ch 26540)
L0001871B

Figure 2 Three Cancellation Groups each comprising Two Carrier Sectors

The Figure 2 shows the boundaries of three cancellation groups, one cancellation
group per cell. In each cell and cancellation group both of the two TX branches
are included. Only the first of the RXs, with two branches, is included as an
affected RX. In other words, in the example 1 the first and second TXs
corresponding to downlink frequencies of 1980 MHz and 1940 MHz are included
in each cancellation group as well as one of the RXs. The first one corresponding
to an RX frequency of 1900 MHz. The second RX is not included in the
cancellation group, based on the results of the test and the 3rd order
intermodulation calculation Example 1.

Each cancellation group in this example contains 2 TX branches × 2 carrier

frequencies = 4 TX streams and 2 RX branches × 1 carrier frequency = 2 RX
streams. As explained later in this guide, one Baseband P can support 3 such
cancellation groups, as shows in the Figure 2.

Manage Cascaded Radio Units on the same CPRI

Uplink and downlink data is transported by a common CPRI link for cascaded
radio units. A maximum number of two cascaded radio units, per CPRI link, can
be supported by the Baseband P.

One or both of the radios in a cascaded radio chain can be members of same
cancellation group.

The procedure to assign radios in a cascaded chain to a cancellation group is

identical to assigning non-cascaded radios to a cancellation group.

4 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Concepts

Differences in Configuration of the Baseband to DU

There are no differences to set up cancellation groups connected to 52xx DUs.
The Baseband P is known as a FieldReplaceableUnit in Baseband Radio
Nodes terminology, but referred to as an AuxPluginUnit with DU Radio Nodes
terminology. During the hardware commissioning process, the correct Baseband
P unit type names need to be used, depending on whether a DU Radio Node or
Baseband Radio Node DU is connected.

1.4 CPRI Pass-through

A single 9.8-Gbps CPRI link can support multiple carrier sectors and with
cascading multiple radio units. If a cancellation group includes some, but not all,
carrier sectors carried by a CPRI link, then the CPRI data associated with those
carrier sectors that are not part of a cancellation group are effectively passed
through a Baseband P. without their content being affected in any way.

If a CPRI stream carries a mix of carriers some of which need to be included in a

cancellation group and therefore must be connected to a Baseband P port,
together with other carriers destined for other cascaded radio units that do not
belong to any cancellation group, then the CPRI data to and from these other
carriers automatically passed through the Baseband P without alteration.

If a CPRI link does not include carriers that belong to any cancellation group,
then that CPRI link cannot be connected to and from any of the Baseband P
CPRI ports.

1.5 Deactivation
A cancellation group consists of a set of radios that include the aggressors (that
is transmitters) and the PIM affected (the receiver frequencies that PIM impacts).

For two carrier sector cancellation groups such as the band 17 and band 14
combination. Both the band 17 receivers and the band 14 receivers have the
potential to be affected by third order PIM products falling into their receive
bands (at about the same level). In such cases both the band 17 and band 14
transmitters and both their receivers set to activated state in the cancellation
group.

There are other two carrier sector cancellation groups such as the example
outlined in Passive Intermodulation on page 1 comprising band 25 with two
carriers at:

— 1st Carrier

• Downlink = 1980 MHz

• Uplink = 1900 MHz

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 5

 Baseband P User Guidelines

— 2nd Carrier

• Downlink = 1940 MHz

• Uplink = 1860 MHz

In this case, only the upper receiver at 1900 MHz is affected by third order PIM
while the other receiver at 1860 MHz is clear.

6 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Concepts

“Theoretical” PIM 3IM Spectra for B25 (1940 MHz Tx & 1980 MHz Tx) 10 Mhz Bw carriers

50

0
1840 1850 1860 1870 1880 1890 1900 1910 1920 1930 1940 1950 1960 1970 1980 1990 2000 2010 2020 2030 2040

-50
(dB) - - -

-100

-150

-200

3rd order PIM Frequency

Signals

Band 25 (F1) 1860

MHz Rx

Band 25 (F2) 1900

MHz Rx
L0001902B

Figure 3 Third Order PIM Spectrum Impacting 1900 MHz

For this second example, it would be appropriate to deactivate the 1860-MHz

receivers because the cancellation algorithm has nothing to cancel on that
receive frequency and by deactivating this carrier the Baseband P resources
assigned to the cancellation group can be reduced.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 7

 Baseband P User Guidelines

The corresponding downlink at 1940 MHz cannot be deactivated because it is

one of the two aggressor frequencies which together with a common PIM source
generates third order PIM in the 1900-MHz receiver.

Deactivation of receivers in cancellation groups that are unimpacted by PIM or

transmitters that do not contribute to PIM allows larger (more complex)
cancellation groups to be configured than are possible without appropriate
deactivation.

1.6 CPRI Configuration for Tandem Baseband P

Tandem configured Baseband P units are required when a shared cancellation
group is necessary to utilize the units computing resources. For example, to
support three cancellation groups that each require ⅔rds resources of a single unit
would require three Baseband P units if shared cancellation groups were not
used. However using shared cancellation groups only two Baseband P units are
needed to support the three cancellation groups.

A tandem configured Baseband P consists of two Baseband P units

interconnected with two short (maximum 3 meters) Inter P Link (IPL) cables.
Once these links exist, both units can communicate with each other and are
automatically aware of their tandem configuration.

1.6.1 Configurations Requiring a Tandem Configuration

Each Baseband P can support up to three cancellation groups (depending on the

complexity of the cancellation group). The more demanding (more complex)
cancellation groups can reduce this support to two or even a single cancellation
group. Expressed another way: some cancellation groups require ⅔rd of the
resources of a Baseband P while other cancellation groups may require ⅔rds or
even 3/3rds of a Baseband P capacity.

Suppose, for example, that a three cell site requires that three cancellation groups
be configured and the complexity of each cancellation group requires ⅔rds of the
capacity of a Baseband P. With such a setup, illustrated in the Figure 4 , one of
the cancellation groups need to be shared across two Baseband Ps in an
arrangement known as a Tandem Baseband P. For this cancellation group (unlike
the last cancellation group example), both RX carriers band 14 and band 17 are
affected of PIM products and so both are included in the cancellation group.

Each digital unit connected to a tandem Baseband P pair requires at least one
CPRI connection to each member of the tandem pair.

8 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Concepts

B17 TX 0 / RX 0
RRUS11 TX 1 / RX 1
Baseband P
PIM Cancellation
1 Half of B14 TX 0 / RX 0 Group 1
4478 TX 1 / RX 1

B17 TX 0 / RX 0
RRUS11
DU or IPL Link
TX 1 / RX 1

Baseband Half of B14 TX 0 / RX 0 PIM Cancellation

Group 2
4478 TX 1 / RX 1 Shared Cancellation
Group

B17 TX 0 / RX 0
Baseband P RRUS11 TX 1 / RX 1
2 PIM Cancellation
Half of B14 TX 0 / RX 0 Group 3
4478 TX 1 / RX 1

B14 TX = 763 MHz, 10 MHz BW, RX = 793 MHz, 10 MHz BW Full-band

B17 TX = 739 MHz, 10 MHz BW, RX = 709 MHz, 10 MHz BW Sub-banded
L0001870B

Figure 4 A Tandem Configured Baseband P with a Shared Cancellation Group

Figure 4 includes examples of two types of radios:

— Group 1 radios (supporting band 17)

— Group 6 radios (supporting band 14)

The group 1 radios (for definition of radio groups, see RBS Configurations)
require greater uplink processing resources per carrier (for PIM cancellation) than
the group 6 radios because each 5 MHz of uplink bandwidth (for the group 1
band 17 carrier) are processed as separate uplink carriers. That is, each 10-MHz
bandwidth band 17 uplink carrier is treated by the Baseband P as two adjacent
5-MHz carriers unlike the 10-MHz bandwidth band 14 carriers which are treated
as single carriers.

Summarizing the numbers of TX and RX streams for these cancellation groups:

— TX streams = 2 carriers × 2 branches = 4 streams.

— Band 17, RX streams = 1 carrier × 2 branches × 2 Sub-bands = 4 streams.

— Band 14, RX streams = 1 carrier × 2 branches × 1 Sub-band = 2 streams.

Total Rx streams = 4 + 2 = 6 per cancellation group.

The two members of the tandem Baseband P configuration are connected by two
IPL links (shows in the Figure 4 ). These two IPL connections are essential to the

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 9

 Baseband P User Guidelines

operation of the tandem Baseband P and are electrical (not fiber) links with a
capacity equivalent to a 9.8-Gbps CPRI link and are used to transfer TX and RX
data for the shared cancellation group (that is PIM Cancellation Group 2 in the
Figure 4) between tandem Baseband Ps.

1.7 Baseband P Capacity Principles

Each Baseband P has a finite processing capacity and there are maximum limits
on the numbers of TX and RX streams that can be supported within each
cancellation group.

The processing capacity required to run a cancellation group depends on the

complexity of the configuration which is non-linearly proportional the number of
TX carriers (that is. the aggressor carriers), the number of TX aggressor antenna
ports, the number of affected carriers and the number of affected antenna ports.

For the 2 carriers band 25 cancellation group shows in Figure 2 each cancellation
group requires less than ⅔ of the computing resources of a single Baseband P so
up to 3 such cancellation groups can be supported by each Baseband P unit as
shown.

This relatively simple cancellation group contains 4 (aggressor) TX streams + 2

(affected) RX streams (which is well within the maximum cancellation group
limits of 8 TX streams and 8 RX streams).

For more complex cancellation groups such as the 2 carrier cancellation group
described in Figure 4 2/3 of a Baseband Ps capacity because in this case the
cancellation group contains 4 (aggressor) TX streams + 6 (affected) RX streams.

The number of RX streams requiring PIM suppression for the second cancellation
group is larger (this is 6 RX streams compared to 2 RX streams for the earlier
cancellation group) which increases the relative computation required so the 2nd
cancellation group requires ⅔ of the resources available in a single Baseband P
unit. For a site consisting of 3 such cancellation groups the resources of a tandem
Baseband P is required (as shown in the Figure 4).

It is possible to attempt to configure a sufficiently large or complex cancellation

group that is that exceeds one or more of the capacity limits for a single
cancellation group and such a configuration is rejected by the Baseband P.

The following Figure 5 provides some examples of 2 carrier cancellation group

parameters (intra sector and cross sector types) and the last column indicates the
proportion of a Baseband Ps resources used by each configuration rounded to the
nearest ⅔.

10 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Concepts

Figure 5 2 Carrier Cancellation Group Parameters Example

The current maximum number of TX streams per cancellation group = 8 and the
maximum configurable RX streams for a single cancellation group is also 8.

There are some exceptions to this maximum (8 + 8) streams rule where up to 10

TX streams can be configured, but the trade off is that only 4 RX streams can be
protected from PIM with the 10 downlink streams configured.

1.8 Dependencies and Limitations

Baseband P requires following:
— Access type LTE FDD

— Digital unit or baseband unit with software version L18.Q1 or newer

Baseband P can only mitigate PIM that originates from the TX of an LTE FDD
carriers passing through the Baseband P. If the PIM results from a carrier not
CPRI cabled through the Baseband P, it will not be mitigated.

A cancellation group can include two or more sector carriers supported by one or
more radio units. Typically, the different carriers will be supported on different
radio units, but for some of the larger bandwidth bands (such as band 25) two
carrier sectors could exist on the same radio unit and produce PIM degrading
sensitivity of one of the uplink carriers.

A cancellation group can contain a maximum of 8 TX streams and 8 RX streams

A TX stream represents one carrier frequency transmitted by one TX port for all
LTE carrier bandwidths (up to a maximum of 20 MHz).

An RX stream represents one carrier frequency received by one RX port. For

newer radios a carrier stream is independent of the carrier bandwidth, while

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 11

 Baseband P User Guidelines

group 1 radios (for definition of radio groups, see RBS Configurations) and earlier
generation radios each 5 MHz part of the RX band represents an RX stream.

A different (computing resources) limitation relates to the complexity of the

cancellation group.

For example, a cancellation group composed of one B29 (2 TX and 0 RX) plus
one B17 (2 TX and 2 RX) requires approximately ⅔rd of the computing resources
of one Baseband P unit. This means that three such cancellation groups can be
supported by a single Baseband P unit.

Similarly, a cancellation group composed of one B14 (2 TX and 2 RX) plus one
B17 (2 TX and 2 RX) requires approximately ⅔rd of the computing resources of
one Baseband P unit. This means that three such cancellation groups can be
supported by a tandem pair of Baseband P units (because ⅔ + ⅔ + ⅔ = 2). In order
to utilize the tandem configured Baseband P units one of these (example)
cancellation groups must be shared across two of the Ps – this type of
cancellation group is known as a shared cancellation group. The Tandem
baseband P software seamlessly handles communication and data transfer
between the shared components of the shared cancellation group via the two
connecting IPL cables. To configure a shared cancellation group the operator can
assign the required sector carriers to both Baseband P units identifying the
carriers as members of the same cancellation group.

12 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Features of Baseband P

2 Features of Baseband P

Baseband P mitigates PIM on uplink carriers.

2.1 CPRI Compression

This feature increases the capacity of the LTE air BW for one Baseband CPRI link,
with up to 50%. The feature is available for LTE FDD/TDD in configurations with
Baseband and for radio types that support CPRI compression. For more
information, see feature description CPRI Compression.

CPRI Compression Limitation on Baseband P

The CPRI Compression feature is not supported on CPRI paths that go through
the Baseband P.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 13

 Baseband P User Guidelines

3 Planning of Passive Intermodulation

Preparation work recommended before configuring cancellation groups.

3.1 Site Survey Requirements

A PIM site survey is necessary to establish the need for PIM mitigation at a cell
site. The degradation of certain KPIs during busy hours could be (although not
necessarily) a result of PIM. Examples of KPIs that are sensitive to PIM effects
include accessibility, retain ability, HO success rate, uplink throughput and in
some cases downlink throughput. To establish whether PIM is a contributor to a
busy hour degradation of uplink throughput for a specific cell it is necessary to
run a site stress test at the cells site.

An RF stress test may be run during the maintenance window to avoid impacts to
traffic. The essential purpose of a stress test is to artificially load the downlinks of
all TXs at a site to full power (for example, by using an AILG traffic generator).
The site’s TXs are loaded with traffic initially one carrier at a time, and then
combined with other carriers up to and including the condition when all carriers
are loaded with traffic at full power. It is also necessary for a stress to run TX
combinations from more than one cell simultaneously in order to identify cross
sector generated PIM at the candidate sites (in case it occurs).

During each traffic loaded TX condition (1 TX, 2 TXs, ... “n” TXs) uplink
interference KPIs are collected and compared with the uplink noise power levels
(per PRB) collected from the all the sites receivers during low traffic conditions.

If the downlink traffic loaded uplink noise power is significantly higher than the
quiet uplink noise power (for one or more of the loaded carrier combinations) it is
evidence that site level PIM is the probable cause of the noise increase and that
the specific loaded carrier frequencies are the main generators of the PIM. The
greater the power ratio in loaded uplink noise power to unloaded uplink noise
power the greater the severity of the PIM at the site.

The outputs of a stress test can identify the carriers involved in the PIM (both
aggressor carriers and affected carriers) and the potential severity (for example,.
SINR degradation) of the issue expected during traffic busy hours.

14 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

4 Operation of Baseband P

4.1 Upgrade SW Load

The Baseband P614 hardware is modelled and managed as a AuxPluginUnit in
a DU, and FieldReplaceableUnit in a BB similar to a radio. Following this
model, the software upgrade process is also replicated, such that the Baseband
P614 software levels are controlled by the DU and BB in the same manner as a
radio.

4.2 Configure a 2 Carrier Intra-sector Cancellation Group

B17 TX 0 / RX 0
BB RRUS11 TX 1 / RX 1
DU 1 P614
1 B29 TX 0
RRUS E2 Two sector
(2Tx only) TX 1 carriers CG

L0001966A

Figure 6 Example of a 2 carriers intra-sector cancellation group.

To set up a 2 carrier intra-sector cancellation group. That is both carriers coming

from sector alpha or sector beta. The only difference here from Configure a 2
Carrier Cross Sector Cancellation Group on page 17 being that we create our
cancellation function using cancellation configurations from sector alpha+sector
alpha or sector beta+sector beta.

Steps

Create a cancellation group.

1. Create the cancellation function.

Example

cr ManagedElement=1,PimCancellationFunction=1

2. Create the cancellation configurations.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 15

 Baseband P User Guidelines

Example

cr ENodeBFunction=1,SectorCarrier=3,PimCancellationConfig=1
cr ENodeBFunction=1,SectorCarrier=4,PimCancellationConfig=1

Both sector carrier 3 and sector carrier 4 are from Sector Alpha

3. Set all downlink carriers to be part of the cancellation group by setting

dlPimCandidate True.

Example

set <config_pid_B17> <config_pid_B29> dlPimCandidate true

Activate cancellation.
4. Set ulPimCancellationMode to 2 (ACTIVATED).

Example

set <config_pid_B17> ulPimCancellationMode 2

16 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

4.3 Configure a 2 Carrier Cross Sector Cancellation Group

RRUS11 B17
Baseband
40W
R503 4
3 5 Data1 RF A Atn
6 Sector Alpha
7 Data2 RF B Atn

9 RRUS11 B29
2 10 40W
11
12 Data1 RF A Atn
Baseband P614
Data2 RF B Atn
13
BB-A
Ru-A Radio-A
Ru-A 1 14
15
Two carrier cross
16 sector cancellation
group
BB-B Radio-B RRUS11 B17-1
40W
BB-C Radio-C Data1 RF A Atn
Data2 RF B Atn

BB-D Radio-D
RRUS11 B29-1
40W
BB-E Radio-E
Data1 RF A Atn Sector Beta

Data2 RF B Atn
BB-F Radio-F

IPL1 IPL2

SYNC RRUS31 B25

RiA 40W
TNA
RiB Data1 RF A Atn

RiC Data2 RF B Atn

RiD
RRUS31 B25 Sector Gamma
RiE 40W
RiF Data1 RF A Atn
OTENB5314 Data2 RF B Atn

L0001901C

Figure 7 OTENB5314 Cell Site Diagram

In this example the radio sectors coming from Baseband R503 are marked as
alpha sector while the sectors coming from radios attached to Baseband P614
are marked as beta sector.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 17

 Baseband P User Guidelines

To set up a 2 carrier cross sector cancellation group, one carrier coming from B29
(sector carrier 4) radio connected through the Baseband R503 and the other
carrier coming from the B17-1 (sector carrier 6) radio connected directly through
the Baseband P614.

Steps

Create a cancellation group.

1. Create the Cancellation Function.

Example

OTENB5314> cr ManagedElement=1,PimCancellationFunction=1

System Output

170831-16:37:56 10.122.107.34 17.0h ERBS_NODE_MODEL_J_1_145_COMPLETE stopfile=/tmp/26890

>>> [Proxy ID = 2320] MO name :ManagedElement=1,PimCancellationFunction=1

2. Create a cancellation configuration.

Example

OTENB5314> cr ENodeBFunction=1,SectorCarrier=1-B17,PimCancellationConfig=1

System Output

170831-16:39:13 10.122.107.34 17.0h ERBS_NODE_MODEL_J_1_145_COMPLETE stopfile=/tmp/26890

Here you are prompted for the Cancellation Function’s MO LDN

Attribute 1 of 1, pimCancellationFunctionRef (moRef:PimCancellationFunction):
Enter mo LDN: ManagedElement=1,PimCancellationFunction=1

>>> [Proxy ID = 2321] MO name :ManagedElement=1,ENodeBFunction=1,SectorCarrier=1-B17,Pi →

mCancellationConfig=1
OTENB5314OTENB5314>

3. Create another cancellation configuration.

Example

cr ENodeBFunction=1,SectorCarrier=1-B29,PimCancellationConfig=1

System Output

18 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

170831-16:39:55 10.122.107.34 17.0h ERBS_NODE_MODEL_J_1_145_COMPLETE stopfile=/tmp/26890

You are again prompted for the Cancellation Function’s MO LDN

Attribute 1 of 1, pimCancellationFunctionRef (moRef:PimCancellationFunction):
Enter mo LDN: ManagedElement=1,PimCancellationFunction=1

>>> [Proxy ID = 2322] MO name :ManagedElement=1,ENodeBFunction=1,SectorCarrier=1-B29,Pi →

mCancellationConfig=1

Activate the cancellation group

4. List cancellation group related MOs to find proxy Ids (pids).

Example

OTENB5314> get cancellation

System Output

170831-16:36:48 10.122.107.34 17.0h ERBS_NODE_MODEL_J_1_145_COMPLETE stopfile=/tmp/26890

===================================================================================
2148 PimCancellationFunction=2
===================================================================================
PimCancellationFunctionId 2
availabilityStatus 8 (NO_STATUS)
operationalState 0 (ENABLED)
reservedBy [0] =
sharedFunctionIdentifier -1
userLabel
===================================================================================
2150 PimCancellationFunction=1
===================================================================================
PimCancellationFunctionId 1
availabilityStatus 8 (NO_STATUS)
operationalState 0 (ENABLED)
reservedBy [2] =
>>> reservedBy = ENodeBFunction=1,SectorCarrier=4,PimCancellationConfig=1
>>> reservedBy = ENodeBFunction=1,SectorCarrier=6,PimCancellationConfig=1
sharedFunctionIdentifier -1
userLabel
===================================================================================
2151 ENodeBFunction=1,SectorCarrier=4,PimCancellationCon →
fig=1
===================================================================================
PimCancellationConfigId 1
dlPimCandidate false
pimCancellationFunctionRef PimCancellationFunction=1
ulPimCancellationMode 0 (EXCLUDED)
===================================================================================
2152 ENodeBFunction=1,SectorCarrier=6,PimCancellationCon →

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 19

 Baseband P User Guidelines

fig=1
===================================================================================
PimCancellationConfigId 1
dlPimCandidate false
pimCancellationFunctionRef PimCancellationFunction=1
ulPimCancellationMode 0 (EXCLUDED)
===================================================================================
Total: 4 MOs

5. Set cancellation configurations downlinks to true.

Example

OTENB5314> set 2151 2152 dlPimCandidate true

System Output

170831-17:03:07 10.122.107.34 17.0h ERBS_NODE_MODEL_J_1_145_COMPLETE stopfile=/tmp/26890

Set 2152 on following 4 MOs ?
===================================================================================
2151 ENodeBFunction=1,SectorCarrier=4,PimCancellationConfig=1
2152 ENodeBFunction=1,SectorCarrier=6,PimCancellationConfig=1
===================================================================================
Set 2152 on 2 MOs. Are you Sure [y/n] ?

a. Confirm with yes.

Example

Set 2152 on 2 MOs. Are you Sure [y/n] ? y

System Output

===================================================================================
Id MO dlPimCandidate Result
===================================================================================
2151 SectorCarrier=4,PimCancellationConfig=1 true >>> Set.
2152 SectorCarrier=6,PimCancellationConfig=1 true >>> Set.
===================================================================================
Total: 2 MOs attempted, 2 MOs set

6. Set a cancellation configurations ulPimCancellatioMode to 2 (ACTIVATED)

Example

OTENB5314> set 2152 ulPimCancellationMode 2

System Output

20 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

170831-17:03:30 10.122.107.34 17.0h ERBS_NODE_MODEL_J_1_145_COMPLETE stopfile=/tmp/26890

Set ulPimCancellationMode on following 1 MOs ?
===================================================================================
2152 ENodeBFunction=1,SectorCarrier=6,PimCancellationConfig=1
===================================================================================
Set ulPimCancellationMode on 1 MOs. Are you Sure [y/n] ?

a. Confirm with yes.

Example

Set ulPimCancellationMode on 1 MOs. Are you Sure [y/n] ? y

System Output

===================================================================================
Id MO ulPimCancellationMode Result
===================================================================================
2152 SectorCarrier=6,PimCancellationConfig=1 2 >>> Set.
===================================================================================
Total: 1 MOs attempted, 1 MOs set

4.4 Configure a 3 Carrier Intra-sector Cancellation Group

B17 TX 0 / RX 0
BB RRUS11 TX 1 / RX 1
DU 1 P614
1 Half of B14 TX 0 / RX 0
4478 Three sector
TX 1 / RX 1 carriers CG 1

B29 TX 0
RRUS E2 TX 1

L0001872B

Figure 8 Example of a 3 carriers intra-sector cancellation group.

The configuration sequence in this example is analogous to Configure a 2 Carrier

Cross Sector Cancellation Group on page 17 and Configure a 2 Carrier Intra-
sector Cancellation Group on page 15, however it will be based on the Figure 8
since it contains a three carrier sector.

— B17 corresponds to cell 1

— B14 corresponds to cell 2

— B29 corresponds to cell 3

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 21

 Baseband P User Guidelines

Steps

Create a cancellation group.

1. Create the cancellation function.

Example

cr ManagedElement=1,PimCancellationFunction=1

2. Create the cancellation configurations.

Example

cr ENodeBFunction=1,SectorCarrier=2,PimCancellationConfig=1
cr ENodeBFunction=1,SectorCarrier=3,PimCancellationConfig=1
cr ENodeBFunction=1,SectorCarrier=4,PimCancellationConfig=1

Enter the MO LDN of the cancellation function when prompted for each
cancellation configuration creation.
Activate the cancellation group.
3. Set all downlinks to true.

Example

set <config_pid_B17> <config_pid_B14> <config_pid_B29> dlPimCandidate true

4. Set ulPimCancellationMode to 2 (ACTIVATED).

Example

set <config_pid_B14> ulPimCancellationMode 2

Setting this attribute to True enables PIM mitigation for all uplink carriers in
this sector carrier.

4.5 Configure a Cancellation Group with Partial Receiver

Protection
This refers to large cross sector cancellation group configurations with up to 10
TX streams and 4 RX streams – the specific RX streams to be protected are
selectable, at the granularity level of 1 SectorCarrier. For example, all RX streams
or none are protected per SectorCarrier.

22 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

B17 TX 0 / RX 0
RRUS11 TX 1 / RX 1 Sector 1

Baseband P TX 0 / RX 0
B14 TX 1 / RX 1
1 RRUS11 TX 2 / RX 2
TX 3 / RX 3

Three sector
B17 TX 0 / RX 0 carriers CG 2
RRUS11 TX 1 / RX 1
DU or IPL Link TX 0 / RX 0
Baseband B14 TX 1 / RX 1
TX 2 / RX 2
Sector 2
RRUS11
TX 3 / RX 3

B17 TX 0 / RX 0
Baseband P RRUS11 TX 1 / RX 1
2 TX 0 / RX 0 Sector 3
B14 TX 1 / RX 1
RRUS11 TX 2 / RX 2
TX 3 / RX 3

B14 TX = 763 MHz, 10 MHz BW, RX = 793 MHz, 10 MHz BW Full-band

B17 TX = 739 MHz, 10 MHz BW, RX = 709 MHz, 10 MHz BW Sub-banded
L0001958B

Figure 9 A three carrier “shared” cross sector cancellation group

The example cross sector cancellation group shown in Figure 9 includes three
radios consisting of two band 14 4TX/4RX radios plus one band 17 2TX/2RX
radio.

The total number of transmitter branches for this cancellation group is 10 which
exceeds the normal maximum allowed limit of 8 TX streams per cancellation
group, however, a limited (partial) uplink protection of up to 4 RX branches is still
possible in this case.

In this case, the operator can choose to configure the cancellation group to
protect all 4 receiver branches in either of the band 14 radios or alternatively to
protect the band 17 receiver branches from passive intermodulation effects.

Protecting the 4 receiver branches is done as you would expect. The steps below
shows the procedure to create cancellation group 2 shown in Figure 9, choosing
to protect the 2nd band 14 radios receiver branches.

— The 1st B14 RU corresponds to sector 1

— The 2nd B14 RU corresponds to sector 2

— The B17 RU corresponds to sector 2

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 23

 Baseband P User Guidelines

Steps

Create a cancellation group.

1. Create the cancellation function.

Example

cr ManagedElement=1,PimCancellationFunction=1

2. Create the cancellation configurations.

Example

cr ENodeBFunction=1,SectorCarrier=2,PimCancellationConfig=1
cr ENodeBFunction=1,SectorCarrier=3,PimCancellationConfig=1
cr ENodeBFunction=1,SectorCarrier=4,PimCancellationConfig=1

Enter the MO LDN of the cancellation function when prompted for each
cancellation configuration creation.

3. Set all downlink to true.

Example

set <config_pid_B14> <config_pid_B17> <config_pid_B14> dlPimCandidate true

Activate cancellation.
4. Set ulPimCancellationMode to 2 (ACTIVATED).

Example
set <config_pid_B14#2> ulPimCancellationMode 2

Setting this attribute to True enables PIM mitigation for all uplink carriers in
this SectorCarrier.

4.6 Re-configure Cancellation Group

Cancellation groups are managed by changing the attributes of the
PimCancellationConfig MO. This MO is a child of the SectorCarrier MO, the
uplink and downlink carriers in context are implicitly defined.

4.6.1 Effect of Starting and Stopping a Cancellation Group on other System

Functions

In the context of the sectorCarriers in a cancellation group:

24 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

— The downlink traffic of the SectorCarriers in a cancellation group

(dlPimCandidate=true) is never impacted by the status of a cancellation
group.

— The uplink traffic should have its signal strength improved only when the
cancellation group is activated ( ulPimCancellationMode= ACTIVATED) for
a given uplink carrier. The passive intermodulation mitigation on the uplink
ramps up over time, achieving maximum passive intermodulation mitigation
over many minutes.

— Any KPIs related to the uplink carriers mitigated in the above steps should be
positively impacted by the passive intermodulation mitigation.

SectorCarriers that are CPRI cabled through the Baseband P614, but are not part
of a cancellation group
(PimCancellationConfig.pimCancellationFunctionRef children to the
sectorCarrier MO is not defined) will not have any impact from cancellation
group management changes.

4.6.2 Effect of Adding or Removing a Carrier to a Cancellation Group on other

System Functions

— For downlink, a carrier only has an impact on the cancellation group when
the dlPimCandidate is changed (true/false).

— For uplink, the ulPimCancellationMode attribute is changed for uplink

carriers to control passive intermodulation mitigation for that specific uplink
carrier.

In each case above, if uplink carriers were actively being mitigated, the Baseband
P614 must pause for the cancellation group in context, and consider the new
cancellation group settings. The Baseband P614 will automatically begin to
search and mitigate passive intermodulation with the new cancellation group
settings. As in any other configuration change, the passive intermodulation
mitigation ramps up over time.

A cancellation group can be reset by setting ulPimCancellationMode=

EXCLUDED for all SectorCarriers in a given cancellation group that are currently
set to ACTIVATED.

For the same cancellation group, set each to ulPimCancellationMode=

ACTIVATED to have the Baseband P614 restart the ramp of passive
intermodulation mitigation for the given cancellation group.

4.7 Re-configure of Baseband P to a Tandem or a Multi

Standalone Configuration

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 25

 Baseband P User Guidelines

4.7.1 Transition of Baseband P from Standalone or MultiStandalone to Tandem

— Pre-state: Two standalone Baseband Ps connected to DU. If starting with

one Baseband P, add a second Baseband P unit.

— Post-state: Tandem Baseband Ps connected to DU.

Steps

1. Connect the IPL cables. Make sure that both IPL cables are of the same
length.

a. Connect the cable from Baseband P 1 – port IPL A to Baseband P 2

– port IPL A.
b. Connect the cable from Baseband P 1 – port IPL B to Baseband P 2
– port IPL B.

Baseband P
1

A B

IPL Link

A B

Baseband P
2

L0001983A

Figure 10 Physically Connect of IPL Cables

2. Configure the Iplport MOs (A to A) and (B to B).

Example

set Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1,IplPort=A remoteIplPortRef R →

bsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2,IplPort=A
set Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1,IplPort=B remoteIplPortRef R →
bsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2,IplPort=B
set Equipment=1,RbsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2,IplPort=A remoteIplPortRef R →
bsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1,IplPort=A

26 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

set Equipment=1,RbsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2,IplPort=B remoteIplPortRef R →

bsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1,IplPort=B

3. Restart both Baseband Ps.

Note:
During the restart of the Baseband P, all contact between the DU and the
connected radios is interrupted. As a consequence all the traffic carried by
these radios are interrupted.

Example
The interval between restart each of Baseband P is less than one minute.

acc Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1 restartunit

acc Equipment=1,RbsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2 restartunit

An alternative Baseband P restart method to reduce the time delay between resta →
rting of the units.
acc <PIMCU1 proxyid> <PIMCU2 proxyid> restartunit

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 27

 Baseband P User Guidelines

Baseband P614
PIM Cancellation
1
Group 1
BB-A
Ru-A Radio-A
Ru-A

B17
BB-B Radio-B Data 1
RRUS11

BB-C Radio-C

B14
Data 1
BB-D Radio-D 4478

BB-E Radio-E
DU or
Baseband
Ri-A BB-F Radio-F

Ri-B
IPL A IPL B
Ri-C

Ri-D

Ri-E IPL A IPL B

PIM Cancellation
Group 2
Ri-F BB-A
Ru-A Radio-A
Ru-A

B14
BB-B Radio-B Data 1
4478

BB-C Radio-C

B17
Data 1
BB-D Radio-D RRUS11

BB-E Radio-E

BB-F Radio-F

Baseband P614
2

L0002033A

Figure 11 A Tandem Configured Baseband P with a Non-Shared Cancellation Group

Follow 4 to 6 if the cancellation group that need to be converted to a shared

cancellation group only. If there is no need to be converted to a shared
cancellation group, stop the procedure.

The Figure 11 shows an example of a non-shared cancellation group before

when it is converted to a shared cancellation group.

28 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

4. Remove cancellation group from Baseband P 1.

a. Remove all downlink carriers by setting dlPimCandidate to false

in the PimCancellationConfig for all carriers in that cancellation
group.

Example

set SectorCarrier=x, PimCancallationConfig=y dlPimCandidate false

b. Deactivate all cancellation and uplink carriers by setting

ulPimCancellationMode in the PimCancellationConfig to 0
(EXCLUDED) for all carriers in that cancellation group.

Example

set SectorCarrier=x, PimCancallationConfig=y ulPimCancellationMode 0

5. Migrate the affected CPRI connections and provisioning to another

Baseband P.
This is an example procedure for moving the B14 radio of cancellation group
1 to Baseband P 2.

a. Lock the B14 cell.

b. Lock the B14 radio unit.
c. Delete the RiLink MO between DU/BB – port Ri-B and Baseband P
1 – port BB-B.
d. Move the CPRI cable (and SFPs) to connect from DU/BB – port Ri-C
to Baseband P 2 – port BB-C.
e. Delete the RiLink MO between Baseband P 1 – port Radio-B to the
B14 radio – port Data 1.
f. Move the CPRI cable (and SFPs) to connect from Baseband P 2 –
port Radio-C to B14 radio – port Data 1.
g. Create the RiLink MO between DU/BB – port Ri-C and Baseband P
2 – port BB-C.
h. Create the RiLink MO between Baseband P 2 – port Radio-C and
B14 radio port – Data 1.
i. Unlock the B14 radio unit.
j. Unlock the B14 cell.

6. Activate the cancellation group.

a. Set cancellation configurations downlinks to true.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 29

 Baseband P User Guidelines

Example

set SectorCarrier=x, PimCancallationConfig=y dlPimCandidate true

b. Set ulPimCancellationMode to 2 (ACTIVATED).

Example

set SectorCarrier=x, PimCancallationConfig=y ulPimCancellationMode 2

The Figure 12 shows an example of a shared cancellation group when it is

configured and activated.

30 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

Baseband P614
Shared PIM Cancellation
1
Group 1
BB-A
Ru-A Radio-A
Ru-A

B17
BB-B Radio-B Data 1
RRUS11

BB-C Radio-C

B14
Data 1
BB-D Radio-D 4478

BB-E Radio-E
DU or
Baseband
Ri-A BB-F Radio-F

Ri-B
IPL A IPL B
Ri-C

Ri-D

Ri-E IPL A IPL B

PIM Cancellation
Group 2
Ri-F BB-A
Ru-A Radio-A
Ru-A

B14
BB-B Radio-B Data 1
4478

BB-C Radio-C

B17
Data 1
BB-D Radio-D RRUS11

BB-E Radio-E

BB-F Radio-F

Baseband P614
2

L0002042A

Figure 12 A Tandem Configured Baseband P with a Shared Cancellation Group

4.7.2 Transition of Baseband P from Tandem to MultiStandalone

— Pre-state: Tandem Baseband Ps connected to DU

— Post-state: Two standalone Baseband Ps connected to DU

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 31

 Baseband P User Guidelines

Steps

1. Check if a shared cancellation group is provisioned.

Remove shared cancellation group before transition. Follow these steps to
remove the shared cancellation group only. If there is no shared cancellation
group, proceed to Step 3.

a. Deactivate all cancellation and uplink carriers by setting

ulPimCancellationMode in the PimCancellationConfig to 0 for
all carriers in that cancellation group.

Example

set SectorCarrier=x, PimCancallationConfig=y ulPimCancellationMode 0

b. Remove all remaining downlink carriers by setting dlPimCandidate

to false in the PimCancellationConfig for all carriers in that
cancellation group.

Example

set SectorCarrier=x, PimCancallationConfig=y dlPimCandidate false

c. Delete the PimCancellationConfig for all carriers in that

cancellation group.

Example

Delete SectorCarrier=x, PimCancallationConfig=y

d. Delete the PimCancellationFunction.

Example

Delete PimCancellationFunction=z

Result: The shared cancellation group is now removed.

2. Clear the Iplport MOs so that the attribute remoteIplPortRef is not

referring to any IPL ports from other Baseband P.

Example

set Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1,IplPort=A remoteIplPortRef

set Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1,IplPort=B remoteIplPortRef
set Equipment=1,RbsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2,IplPort=A remoteIplPortRef
set Equipment=1,RbsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2,IplPort=B remoteIplPortRef

3. Disconnect the IPL cables from port A to port A and from port B to port B
between the two Baseband Ps.

32 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Operation of Baseband P

It is possible that alarms associated with the IPL ports occur. The alarms are
cleared by the following steps as the Baseband Ps are restarted.

4. Restart both Baseband Ps.

Note:
During the restart of both Baseband Ps, all contact between the DU and the
connected radios is interrupted. As a consequence all the traffic carried by
these radios are interrupted.

Example
The interval between restart each of Baseband P614 is less than one minute.

acc Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=PIMCU1 restartunit

acc Equipment=1,RbsSubrack=1,RbsSlot=8,AuxPlugInUnit=PIMCU2 restartunit

An alternative Baseband P restart method to reduce the time delay between resta →
rting of the units.
acc <PIMCU1 proxyid> <PIMCU2 proxyid> restartunit

5. Verify that the IPL state is OFF_LINE and DISABLED in both Baseband Ps.

Example

get iplport

System Output

IplPortId A
availabilityStatus 8 (OFF_LINE)
operationalState 0 (DISABLED)
remoteIplPortRef
reservedBy [0] =

The two Baseband P are now considered to be standalone and independent of one another. Only
non-shared cancellation groups can now be supported.

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 33

 Baseband P User Guidelines

5 Performance Management of Passive

Intermodulation

5.1 Check Performance KPI

The new KPIs associated with the cancellation group and their meaning.

These pm counters are not collected by default. The configuration of a scanner

for the PimCancellationFunction MO is necessary to activate the collection of
measurement data into pm counters.

For further information about pm counters, see the document Performance

Management (DU-based node) or Manage Performance (Baseband-based node).

Table 1 The Available Baseband P614 Counters

Counter
pmPimcCancellationGroupStatus
pmPimcCoefficientsDivergence
pmPimcCancellationDepth
pmPimcPowerSignalInjected
Description
This counter indicates how much time a
cancellation group spent in each of the 4
possible operational states over the 15-minutes
ROP period. For description of the transition
between different states and functions, see the
Figure 13.
This counter indicates how much time a
cancellation group spent in each of the 4
possible coefficients states over the 15-minutes
ROP period.
The 32 bins displayed correspond to (0–32 dB)
indicate the number of events recorded at each
cancellation depth bin (in dB) over the 15-
minutes ROP period.
The 32 bins correspond to (0–32 dBc relative to
the uplink signal power) indicates the number
of events recorded at each signal (uplink
correction) injection level (in dB) over the 15-
minutes ROP period.
Power Signal Injected indicates how far the
detected PIM is below the total uplink carrier,
before PIM cancellation.
When Power Signal Injected is 0, it means that
all the uplink signal is PIM. In such a case, it is

34 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

 Performance Management of Passive Intermodulation

Counter Description
not the PIM that is missing, the uplink LTE
carrier is low compared to the PIM or missing
altogether.
When the Power Signal Injected is 0.5, it means
that PIM is half a dB below the total signal (the
uplink signal is mostly PIM) and therefore the
uplink signal that is not PIM (UL LTE carrier
and noise) is about 10 dB below the total
signal.

Figure 13 Cancellation Group State Diagram

Example 2
The following command return counters summary.

pget PimCancellationFunktion

System Output

======================================================================================= →
==========================

MO Attribute V →
alue

======================================================================================= →
==========================

PimCancellationFunction=1 pmPimcCancellationDepth i[31] = 0 0 258 24 2 0 →

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 35

 Baseband P User Guidelines

0 1 2 13 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

PimCancellationFunction=1 pmPimcCancellationGroupStatus i[4] = 0 0 150 0

PimCancellationFunction=1 pmPimcCoefficientsDivergence i[4] = 0 300 0 0

PimCancellationFunction=1 pmPimcPowerSignalInjected i[31] = 0 14 2 2 2 2 →

80 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The Interpretation of these counters arrays is as follows:

pmPimcCancellationDepth i[31] = 0 0 258 24 2 0 0 1 2 13 0 0 0 0 0 0 0 0 0 0 0 0

0 0 0 0 0 0 0 0 0
The cancellation depth example:
—-1 dBc to -2 dBc, 258/300= 86% of the time

—-2 dBc to -3 dBc, 24/300= 8% of the time

—↓

—-9 dBc to -10 dBc, 13/300= 4.3% of the time

The cancellation depth was always between -1 dBc and -10 dBc.

pmPimcCancellationGroupStatus i[4] = 0 0 150 0

Therefore during this period, the cancellation group was in PimcAction state continuously.

pmPimcCoefficientsDivergence
Therefore during this period, the PIM tracking for both uplink carriers was in the
coefficientsConverging state continuously. i[4] = 0 300 0 0

pmPimcPowerSignalInjected i[31] = 0 14 2 2 2 280 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

0 0 0 0 0
The PIM signal depth example:
—0 dBc to -1 dBc, 14/300= 4.7% of the time

—↓

—-4 dBc and -5 dBc 280/300= 93% of the time

The PIM signal depth was always between 0 dBc and -5 dBc.

36 91/1553-LZA 701 6014/1 Uen D | 2018-08-20

91/1553-LZA 701 6014/1 Uen D | 2018-08-20 37