RTWP and External

Interference Optimization
Introduction

 Signal received by the antenna is amplified by a tower mounted amplifier (TMA) (optional)
and a remote radio unit (RRU) in a NodeB and then converted from a digital signal to an
analog one. After that, P_out signal is output. Therefore, RTWP indicates the power of a
signal received by the antenna receiving port. The formula for calculating RTWP is as follows:

RTWP = P_in = P_out – G

 When no signal is input into the receiver (namely, no inter-RAT or intra-RAT interference
exists or no users are served in the system), the RTWP measured in the NodeB equals the
NodeB PN. The formula for calculating NodeB PN is as follows:

PN = KTB + NF

Where,

K = Boltzmann constant

T = 290 K (room temperature)

B = RF carrier bandwidth (Hz)

NF: noise factor of the RF system

 Due to certain networking configuration, the NodeB PN rises in the following scenarios:

1) When a TMA or line amplifier (LA) is used without the configuration of RX channel
attenuation, the

NodeB PN rises.

Rise volume (X) = TMA gain – Antenna feeder/Jumper attenuation

2) A NodeB uses the configuration of multiple RRUs in one cell. Note that the configuration of
multiple RRUs in one cell in RAN13.0 and later versions does not result in the rise of PN. The rise
volume of PN is relevant to the number of RRUs in one cell. Assume that N RRUs are in one cell, the
rise volume N is 10log(N) dBm.

Criteria for Measuring Channel Quality

 The criterion for measuring the quality of uplink channels is RTWP:

 Normally, the RTWP noise floor (RTWP without subscribers) should be around -106
dBm. Lower and higher values indicate that channels are abnormal.

 If the alarm for the excessively low RTWP is generated (RTWP < -114 dBm), the RTWP
noise floor is too low.

 If the value of VS.MinRTWP in case of no subscribers is always greater than -102 dBm,
the RTWP noise floor is too high.

 If the alarm for RTWP/received signal strength indicator (RSSI) imbalance on RF receive
channels is generated, the main and diversity RTWP is not in balance.

 Note 1: Abnormal RTWP values may also be caused by other factors such as service-
related reasons, instead of uplink channel problems.

 Note 2: Common traffic measurement indexes for identifying high and low RTWP
include VS.MinRTWP, VS.MeanRTWP, and VS.CellDCHUEs.

 Note 3: Common information for identifying RTWP imbalance includes main and
diversity RTWP information.

 The criteria for measuring the quality of downlink channels are the standing wave ratio and
transmit power.

 The standing wave ratio and transmit power problems can be identified based on alarms
and measurement data.
Action Checklist (Details)
Step Prescribed Action Entrance Condition Objective

Analyze whether the problem occurs after

indexes change or always exists, occurs on the
entire network or on top cells, is a multi-carrier
Action 1: Identify the
or single-carrier problem, occurs on indoor cells
characteristics of an No condition.
or macro cells, occurs in cities or countryside,
RTWP problem.
and occurs in busy hours or idle hours. Specify
the impact range of the problem and determine
the general problem analysis direction.
Step Action 2: Analyze Analyze whether RTWP changes are caused by
1 RNC/NodeB indexes change. external operations such as swap, upgrade,
operation logs. reset, or expansion.

Analyze whether the RTWP changes are caused

Action 3: Check
indexes change. by sudden external events (such as traffic
sudden factors.
increase) and bad weather.

Action 4: Check
equipment faults and No condition. Check whether hardware failure occurs.
alarms.

Action 5: Subdivide
problem causes 1:
Cells need to be Analyze possible causes for the problem based
Analyze the RTWP
analyzed. on the traffic measurement data.
traffic measurement
data in detail.
Step The main and diversity
2 Action 6: Subdivide RTWP information needs
problem causes 2: to be analyzed if the
Analyze possible causes for the problem based
Analyze the main and problem is not solved
on the main and diversity RTWP symptoms.
diversity RTWP based on traffic
information in detail. measurement RTWP
analysis.

The analysis results of

Action 7: Check actions 5 and 6 indicate Check whether the parameter settings are
Steps parameter settings. that the problem may be correct.
3 and a configuration problem.
4
Action 8: Check the The analysis results of Check whether the antenna and feeder have
antenna and feeder actions 5 and 6 indicate engineering quality problems, such as
 that the problem may be
intermodulation interference, incorrect antenna
quality. caused by poor antenna
and feeder connection, or cable break.
and feeder quality.

The analysis results of

actions 5 and 6 indicate
Action 9: Check
that the problem may be Check whether external interference exists.
external interference.
caused by external
interference.

The analysis results of

actions 5 and 6 indicate
Action 10: Check
that the problem may be Check whether interference between
interference between
caused by interference neighboring cells exists.
neighboring cells.
between neighboring
cells.

The RTWP problem Check whether the problem is a capacity

Action 11: Check persists after the problem. See the capacity-related topic UMTS
capacity problems. preceding actions are Network Planning and Optimization: Processes
performed. + Principles + Tools + Deliverables.

Action Checklist (Summarized)

Possible Causes of High RTWP

1. External Interference

2. Inter-modulation Interference

3. Traffic Related

4. NodeB Configuration Related

5. Hardware Related

Checklist to Perform RTWP Analysis:

1. Observe the single site and surrounding site RTWP trending –Swap, New Site.

2. Check Alarm and operation log (if sudden occur cases)

3. Determine if the RTWP is caused by traffic.

4. Perform configuration check.

 5. Check VSWR reading.

6. Check Main and Diversity RTWP Difference.

7. NodeB LMT FFT Scanning.

8. 3G Inter-modulation Test (automatically using command or manually)

9. 2G Inter-modulation Test.

10. External Frequency Scanning.

Action Checklist 6. Check Main and Diversity RTWP Difference Using NodeB LMT

Step1 Determine the board location of carrier and sector intended to be troubleshooted

Action Checklist 6. Check Main and Diversity RTWP Difference Using

NodeB LMT
 Are the reflections on all carriers
the same?

(Y) RF channel configuration problems (attenuation

The trends of the configuration and interconnection mode)
main and diversity (N) Carrier configuration problems, 80%
RTWP are the
same, with a fixed (Y) Antenna channel amplifier or attenuator problems,
difference. 15%

1. The Engineering problems (abnormal sector

difference interconnection and cross-connection) that can
between The trends of the be identified based on neighboring cells, 40%
the main main and diversity
and RTWP are Engineering problems (intermodulation
diversity different (not interference), 45%
RTWP is related or loosely
large. related). External interference (external polarization interference
(Obtain the (only the main or diversity signals are interfered)), 10%
data of the Configuration problems (interconnection mode and a
cells with single-antenna cell is configured as a dual-antenna
the cell), 60%
The main or
problem
diversity RTWP
and co-RF
has no fluctuation Hardware failure of the RF module (channel fault alarm and
module
cells.) cable damage), 20%

Engineering problems (The main or diversity channel is not

connected and an antenna and feeder component is damaged), 20%

Below is the sample of main and diversity RTWP tracing result

 Note 1: This step applies to fault

modes that require comparison
between the main and diversity
RTWP data, for example, antenna
and feeder intermodulation
interference, incorrect antenna and
feeder connection or antenna and
feeder failure, configuration
problems, and external interference.

 Note 2: The sum of all ratios is not

100% because other causes may
exist.
Action Checklist 7. NodeB LMT FFT Scanning Using Broadband
Offline Frequency Scanning.

 The NodeB R13 and later versions support FFT frequency scanning. By scanning the frequencies
on an LMT, you can obtain the frequency information about a cell to identify interference.

Impact on
Services (This
Typical Application
Function System and Advantage Disadvantage
Scenario
Other
Systems)

This function This function does

High-
has no not interrupt This function cannot
definition Collect information
impact on the services, involves show the situation
online for checking
local-end and small data amount, when no frequency is
carrier interference.
peer-end and provides high used.
scanning
services. precision.

If problems are found

This function does
in service verification This function
not interrupt
Broadband on a site in the has no
services and can
online engineering phase, impact on the The definition is a
show the
carrier this function can be local-end and little low.
interference
scanning used to check peer-end
between
whether external services.
frequencies.
interference exists.

This function This function

This function provides a wide interrupts services
This function stops
Broadband interrupts range of spectrum and features low
services and collects
Offline both local- scanning, features definition. Generally,
interference
Frequency end and high accuracy, and this function can be
information to ensure
Scanning peer-end eliminates the used only after being
the accuracy.
services. impacts from approved by a
services. customer.
Action Checklist 7. NodeB LMT FFT Scanning Using Broadband
Offline Frequency Scanning.
Action Checklist 7. NodeB LMT FFT Scanning Using Broadband
Offline Frequency Scanning.

MAXIS SPECTRUM F4
Layer URARFCN(UL) Center Freq(UL) UARFCN(DL) Center Freq(DL) UL Center Freq Number 2714
F1 9736 1947.2 10686 2137.2
UL Center Freq (MHz) 882.8
F2 9687 1937.4 10637 2127.4
F3 9712 1942.4 10662 2132.4 Lower Freq(MHz) 880.3
F4 2714 882.8 2939 927.8 Higher Freq(MHz) 885.3

The traced FFT scanning result can be reviewed using a tool located in NodeB LMT installed folder,
typically as below path in your system.

D:\HW LMT\adaptor\clientadaptor\FreqChartReview
Action Check List 8. 3G Inter-Modulation Test(Using MML)
Use below NodeB command to test Inter modulation:
Action Check List 8. 3G Inter-Modulation Test (Manual)

Step2: Run above command in NodeB command. However, before execute step1&2, board RTWP
tracing have to executed first in order to observe RTWP behavior when the maximum downlink output
power is started to check the interference from frequency component(refer picture below). Lower
bands are more vulnerable PIM than high bands due to the gap between the uplink frequency and the
downlink frequency is narrower.
Action Check List 9. 2G Inter-Modulation on 3G Test
Access corresponding 2G BSC LMT, select Device Maintenance. Then right click on the TRX in the cell,
then select “Test idle timeslot”. This test is to transmit maximum power in those 2G idle timeslot and
observe any interference change in 3G systems.
Action Check List 9. 2G Inter-Modulation on 3G Test
If RTWP spike up in NodeB LMT, means inter-modulation interference exist. Else it might not because of
2G inter-modulation interference.

Stop the idle timeslot test after the test.