eRAN3.

1 LTE TDD
Interference Detection Guide

Issue 3.1

Date 2012-11-227

INTERNAL

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei
and the customer. All or part of the products, services and features described in this document may
not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all
statements, information, and recommendations in this document are provided "AS IS" without
warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in
the preparation of this document to ensure accuracy of the contents, but all statements, information,
and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

Issue 3.1 (2012-11-2222) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co.,
Ltd.
LTE TDD Fault Diagnosis Guide-Interference Detection About This Document

About This Document

Author
Prepared By Wang Hua (employee ID: Date 2013-02-27
0065235)
Reviewed By Date
Reviewed By Date
Approved By Date

Change History
Date Issue Description Author

2010-11-30 1.0 Completed the draft. Yang Lu (employee

ID: 00142241)
2010-12-15 1.1 Added some operation procedures. Yang Lu (employee
ID: 00142241)
2011-07-11 1.2  Added descriptions of time division Yang Lu (employee
duplex (TDD)-related interference ID: 00142241), Ye
detection and the baseband prototype Guojun (employee ID:
tool usage based on lab test 00047562)
verification involved in eRAN2.1 and
eRAN2.2.
 Added TDD Global Positioning System
(GPS) clock loss cases.
2011-09-15 1.3  Added operation procedures and Yang Lu (employee
analysis methods for uplink (UL) ID: 00142241)
frequency spectrum scanning for a
remote radio unit (RRU) and the usage
of the UL frequency spectrum analysis
tool based on the content involved in
eRAN2.1 and eRAN2.2.
 Revised the document based on issue
LTE TDD Fault Diagnosis Guide-Interference Detection About This Document

Date Issue Description Author

1.2.
 Added intermodulation interference
cases of Germany D2.
2012-02-06 2.0 Revised the description of interference Wang Hua (employee
maintenance and measurement added to ID: 00065235)
eRAN3.0.
2012-11-22 2.1 Revised the description of interference Wen Yu (employee
maintenance and measurement added to ID: 00145024)
eRAN3.1.
2013-2-27 3.0  Clarified the interference detection Wang Hua (employee
process. ID: 65235)
 Updated inter-system interference
detection process.
 Added descriptions of how to use tools
to detect interference.
 Added typical cases of interference
detection.

Abstract
Long Term Evolution (LTE), radio network planning, radio network optimization, intra-
system interference, inter-RAT interference, intermodulation interference, spurious emission
interference

Key Words
This document describes interference classification, location, and solution in LTE networks,
and provides experience and solutions during network plan optimization and hardware fault
rectification. It serves as a guideline for frontline engineers to locate interference in LTE
networks.
LTE TDD Interference Detection Guide Contents

Contents

About This Document....................................................................................................................ii

1 Disclaimer Statement....................................................................................................................1
2 Overview.........................................................................................................................................2
3 Interference Causes.......................................................................................................................3
3.1 Intra-System Interference..................................................................................................................................3
3.1.1 Interference Caused by Out of Frame or GPS Clock Loss.......................................................................3
3.1.2 Interference Caused by TDD Long Distance...........................................................................................5
3.1.3 Interference Caused by Incorrect Data Configuration..............................................................................6
3.1.4 Interference Caused by Coverage Overlap...............................................................................................6
3.2 Inter-RAT Interference.......................................................................................................................................7
3.2.1 Spurious Emission Interference................................................................................................................7
3.2.2 Blocking Interference...............................................................................................................................8
3.2.3 Intermodulation Interference....................................................................................................................9
3.2.4 In-Band Interference.................................................................................................................................9

4 Interference Handling................................................................................................................11
4.1 Interference Monitoring...................................................................................................................................11
4.1.1 Traffic Measurement Counters...............................................................................................................11
4.1.2 CHR........................................................................................................................................................12
4.1.3 Cell Performance Monitoring.................................................................................................................12
4.1.4 Cell Performance Monitoring on the LMT.............................................................................................20
4.2 Interference Identification................................................................................................................................22
4.2.1 Interference Type Identification.............................................................................................................22
4.2.2 Intra-System Interference.......................................................................................................................22
4.2.3 Inter-RAT Interference............................................................................................................................39
4.3 Interference Location and Handling................................................................................................................42
4.3.1 Intra-System Interference Location—Interference Map........................................................................42
4.3.2 Inter-System Interference Handling.......................................................................................................45
4.4 Interference Handling......................................................................................................................................49
4.4.1 Intra-System Interference Handling.......................................................................................................49
4.4.2 Inter-System Interference Handling.......................................................................................................50
LTE TDD Interference Detection Guide Contents

5 Typical Cases................................................................................................................................52
5.1 Cases for Intra-System Interference................................................................................................................52
5.1.1 Network Entry Failures Due to out of Frame During a Test Conducted by MIIT in Huairou...............52
5.1.2 GPS Synchronization Loss Interference at Site S in Country S.............................................................53
5.2 Cases for Inter-System Interference Handling.................................................................................................57
5.2.1 Inter-System Interference on Frequency Band F at City S in Country C...............................................57

6 Others.............................................................................................................................................60
6.1 Frequency Clearance Before Network Planning..............................................................................................60
6.2 Silence Frame Collection (Not Available at Present)......................................................................................60

A Acronyms and Abbreviations..................................................................................................61

eRAN3.1 LTE TDD Interference Detection Guide 2 Overview

1 Disclaimer Statement

This document can be used to quickly locate and resolve problems. Normally there is no way
to avoid that some user data such as Internet Protocol (IP) addresses will be used during the
troubleshooting. You are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the
personal data of users is fully protected.
 2 Overview

Interference is a key factor that affects network quality, and it affects the call quality, call
drop, handover, and throughput. How to reduce or eliminate interference is the focus during
network planning and optimization. This document describes a general process of interference
detection and detailed procedures involved in this process.
 3 Interference Causes

Interference in an LTE network can be classified as intra-system interference, inter-system

interference, and hardware fault interference.
 Intra-system interference refers to intra-frequency interference caused by the following
items:
− LTE TDD out of frame or GPS clock loss
− Long distance in TDD networks
− Incorrect data configuration
− Coverage overlap
 Inter-system interference refers to the following types of interference from another
system to the live system:
− Unauthorized usage of an LTE frequency band
− Spurious emission interference
− Blocking interference
− Intermodulation interference

3.1 Intra-System Interference

3.1.1 Interference Caused by Out of Frame or GPS Clock Loss
The LTE TDD has a demanding requirement on clock synchronization. If the clock of E-
UTRAN NodeB (eNodeB) A is not synchronous with that of a neighboring cell within a
network, and downlink (DL) signals from eNodeB A are received by a neighboring cell,
interference occurs during UL signal receiving of a neighboring cell. Assume that eNodeB A
and eNodeB B have asynchronous clocks. Figure 3.1.1.1.I.1.1.1 shows how transmitting
signals from eNodeB A interfere with UL signal receiving of eNodeB B. Generally, an
antenna is installed at a high position of an eNodeB, for example, 30 m in an urban area and
40 m in a suburban area. If an antenna is installed at such a typical position, ling-of-sight
transmission is implemented between antennas of two eNodeBs. In this case, the transmitting
signals from one eNodeB are easy to be received by another eNodeB. Therefore, interference
is severe.
 Figure 3.1.1.1.I.1.1.1 Interference caused by out of frame

DL UL DL UL

DL UL DL UL

With the guard period (GP) in the LTE TDD special subframe, uplink-downlink switching can
be ensured. The value of GP ranges from 100 μs to 700 μs. If the duration of GPS clock loss
exceeds the GP range, interference occurs between eNodeBs.

Figure 3.1.1.1.I.1.1.2 LTE TDD subframe structure

One slot,
Tslot=15360Ts 30720Ts

Subframe #0 Subframe #2 Subframe #3 Subframe #4

One subframe,
30720Ts

DwPTS GP UpPTS

Interference also occurs when the GPS clock is lost. However, interference caused by GPS
clock loss has a great impact on network performance and involves impact on more eNodeBs
than that caused by out of frame. If the GPS clock of an eNodeB is lost, multiple neighboring
eNodeBs may be affected and user equipment (UE) served by the eNodeBs cannot have
services. What's worse, the UEs cannot enter the network even when the reference signal
received power (RSRP) is within the normal range. The result of tracing the UL received
signal strength indicator (RSSI) for the eNodeBs shows that the RSSI for the eNodeBs is at
least 10 dB to 20 dB higher than the normal value.
The possible causes for GPS clock loss are as follows:
 The GPS is incorrectly installed and cannot receive enough number of satellites.
 The GPS is with interference.
 The satellite card is faulty.
For Huawei eNodeBs, you can run the DSP GPSSNR:; command to query the number of
satellites and the value of SINR received by the GPS antenna. In addition, an alarm is
reported when the GPS clock is unlocked. However, if there is equipment from another
vendor in the network, interference to Huawei eNodeBs may be generated when their GPS
clock is unlocked.
3.1.2 Interference Caused by TDD Long Distance
The following describes application scenarios and causes for TDD long-distance interference.
The radio transmission environment is good between an eNodeB with interference and
eNodeBs that are interfered with. This environment can be regarded as a free space. When
signals from a remote eNodeB are transmitted to an eNodeB that is interfered with, signal
attenuation is weak due to a good transmission environment. In addition, due to the
transmission delay, the downlink pilot timeslot (DwPTS) for the eNodeB with interference
overlaps the uplink pilot timeslot (UpPTS) for the eNodeB that is interfered with. In some
cases, the DwPTS is transmitted simultaneously with the UL subframe of the eNodeB that is
interfered with. In this case, signal transmitting of the eNodeB with interference has an impact
on signal receiving of the eNodeB that is interfered with. Figure 3.1.2.1.I.1.1.1 shows the
TDD long-distance interference.

Figure 3.1.2.1.I.1.1.1 TDD long-distance interference

The DwPTS represents the DL pilot timeslots, and UpPTS represents the UL pilot timeslots.
GP is a guard period in a special subframe, which ensures downlink-to-uplink switching.
The DwPTS must be reliably received during cell searching to prevent interference to the UL.
The UpPTS must be transmitted in advance during random access to prevent interference to
the DL.
The GP in a special subframe specifies the minimum distance beyond which DL signals do
not interfered with UL signals. The following table shows different GPs in a special subframe,
ranging from 21.4 km to 214.3 km. If the radio transmission environment between eNodeBs
is good and a special subframe has a short GP, TDD long-distance interference may occur.

Table 3.1.2.1.I.1.1.1.1 Subframe configuration and DwPTS/UpPTS

Special Subframe DwPTS GP UpPTS GP (km)
Configuration

0 3 10 1 214.3
1 9 4 1 85.7
2 10 3 1 64.3
 Special Subframe DwPTS GP UpPTS GP (km)
Configuration

3 11 2 1 42.9
4 12 1 1 21.4
5 3 9 2 192.9
6 9 3 2 64.3
7 10 2 2 42.9
8 11 1 2 21.4

The following problems occur due to TDD long-distance interference:

 UEs at the edge of the cell that is interfered with cannot randomly access the network.
 UEs from a neighboring cell cannot be handed over to a cell that is interfered with.
 The rates for DL and UL services decrease a lot.

3.1.3 Interference Caused by Incorrect Data Configuration

Intra-system interference increases due to incorrect data configurations about the following
items:
 System frequency
 Physical cell identifier (PCI)
 Uplink-downlink subframe configuration
 TDD time offset
If the interference increases, the RSRP or SINR is less than the expected value.
In a WiMAX-LTE or TDS-LTE dual-mode network, or a hybrid-mode network, inter-RAT
TDD interference may be generated if the clock offset is incorrectly set. Therefore, you must
perform data configurations strictly based on the policy of frame synchronization over the air
interface in a network that has dual-mode scenarios. After the data configurations are
complete, you are advised to restart the eNodeB.
Intra-system interference caused by incorrect data configurations can be verified by checking
data configurations. After the data configuration check, configurations of all eNodeBs must be
the same as the specified configurations.

3.1.4 Interference Caused by Coverage Overlap

A coverage overlap refers to a situation with the following phenomenon:
The actual serving range of a cell is far larger than the planned serving range.
The cell can provide strong signals for UEs when its coverage range overlaps the coverage
range of another eNodeB.
 In this case, UEs can still have services in this cell or other UEs can be handed over to the
cell. This brings severe interference to other remote cells. A coverage overlap occurs due to
inconsistency between the actual serving range and the planned serving range, and the
consistency is caused by incorrect configurations of the antenna azimuth and downtilt. A
coverage overlap has the following impact on a network: interference, call drops, congestion,
and handover failures.
Interference caused by a coverage overlap belongs to DL interference. Currently, this type of
interference is verified by comparing DL RSRP and SINR reported by UEs.

3.2 Inter-RAT Interference

The frequency used by an LTE network is not unique, and therefore the LTE network is easy
to be interfered with. Interference during microwave communication or from an inter-
frequency system can be verified by operator feedback or using a spectrum analyzer or
scanner.
Interference also occurs due to other communication devices, such as military communication
devices, large-power electrical devices, and illegal transmitters.
Inter-system interference refers to interference from TD-SCDMA, WiMAX, or UMTS
networks. LTE TDD networks and the preceding networks may interfere with each other.
Under ideal conditions, the following formula takes effect:
DL SINR = DL RSRP – Noise floor (ambient noise)
For example, if DL RSRP is –100 dBm and the noise floor is –110 dBm, DL SINR is about 10
dB. If the actual DL SINR is 0 dB, DL interference exists, which may come from DL signals
of nearby cells.
TD-SCDMA is short for Time Division-Synchronous Code Division Multiple Access.
WiMAX is short for Worldwide Interoperability for Microwave Access. UMTS is short for
Universal Mobile Telecommunications System.

3.2.1 Spurious Emission Interference

Spurious emission interference refers to the additive interference generated by the interference
source on the working frequency band of the receiver that is interfered with. Spurious
emission interference includes the following types:
 Out-of-band power leakage of the interference source
 Amplified noise floor
 Harmonic emissions
All the interference reduces the signal noise ratio (SNR) of the receiver that is interfered with.
Spurious emission interference is generated by a transmitter and includes the thermal noise
generated and amplified by the power amplifier (PA), harmonic emission generated during the
PA operation, and spurious signals generated by the frequency mixer.
 Figure 3.2.1.1.I.1.1.1 Spurious emission interference

3.2.2 Blocking Interference

A receiver usually works at a linear area. When a receiver receives strong signals, it works in
non-linear mode or in a saturation state in some cases. This is called blocking interference.
Generally, blocking interference is caused by a strong interfering signal out of the receive
band. As a result, the receiver works in saturation state and then gains are reduced. In
addition, the interfering signal may mix with the local oscillator signal and then cause the
interference in the intermediate frequency (IF). Moreover, the out-of-band suppression ratio
of the receiver may be limited, so that the interference is generated directly.
Blocking interference can reduce the receiver gains and increase the noise.

Figure 3.2.2.1.I.1.1.1 Blocking interference

3.2.3 Intermodulation Interference
Intermodulation interference consists of transmitting intermodulation and receiving
intermodulation.
 Transmitting intermodulation: When multiple signals are transmitted simultaneously to a
transmitter, the intermodulation product is generated on the back end non-linear circuit
of the transmitter. Then, the frequency of the intermodulation product falls on the useful
frequency band of the receiver and causes the intermodulation interference.
 Receiving intermodulation: When a receiver simultaneously receives multiple signals,
the intermodulation product is generated on the front end non-linear circuit of the
receiver. Then, the frequency of the intermodulation product falls on the useful
frequency band of the receiver and causes the intermodulation interference.
In most cases, intermodulation interference is common on the live network because passive
device performance deteriorates after long-time operating, or because intermodulation
suppression is unsatisfactory. Interference detection indicates that antenna performance is
poor, and antenna connectors have engineering quality problems. This is the major cause of
intermodulation interference.

Figure 3.2.3.1.I.1.1.1 Intermodulation interference

Intermodulation products are classified into order-specific signals, such as third-order, fifth-
order, or seventh-order signals.
Figure 3.2.3.1.I.1.1.1 shows third-order signals. The frequency combination such as 2f1-f2
and 2f2-f1 of two strong interfering signals may fall on the band of the receiver and then
generates interference.
The strength of fifth- and seventh-order signals is at least 20 dB lower than that of the third-
order signals. Only when isolation between two systems does not meet the requirement, fifth-
and seventh-order signals have interference on the interfered system.
Intermodulation suppression is achieved by changing passive devices or improving the
engineering quality of antenna feeders. In most cases, the suppression requires the
intermodulation KPI of –140 dBc or –97 dBc.

3.2.4 In-Band Interference

Other systems illegally use the LTE TDD frequency band, causing interference to the TDD
system. This is called in-band inter-system interference. For example, the following types of
frequency bands are used:
 PHS whose 1.9 GHz frequency band has not been cleared
 Broadcast wireless system working on 2.6 GHz frequency band
 Military communication system working on 2.4 GHz frequency band
Interference can only be eliminated when thorough frequency clearance is performed. With
interference source determined, operators push the Radio Spectrum Committee to clear the
frequency.
LTE TDD Interference Detection Guide 4 Interference Handling

4 Interference Handling

Interference detection is the necessity for interference handling and call quality improvement.
After interference detection, proper measures are used to locate the interference for
eliminating it or reducing it. In LTE networks, the following methods or tool can be used for
interference detection: traffic statistic query, LMT- or OMC-based data analysis, RSSI query,
UL subcarrier IN, drive tests, and frequency spectrum scanning.
During interference detection, the service application quality, RSSI, RSRP, SINR, and block
error rate (BLER) traced on UEs or the eNodeB are used to check whether there is
interference on the UL or DL. Then, further detection is performed. This chapter describes the
procedure and operation methods for interference detection.

4.1 Interference Monitoring

For details about how to collect interference data, see LTE Maintenance and Operation
Description and Data Collection Guide.

4.1.1 Traffic Measurement Counters

Table 4.1.1.1.I.1.1.1.1 Traffic measurement counters
Counter Traffic Measurement Description
ID Counter

1526728297 L.UL.Interference.Max Specifies the maximum subcarrier interference

noise detected by each UL physical resource
block (PRB).
1526728298 L.UL.Interference.Avg Specifies the average subcarrier interference
noise detected by each UL PRB.
LTE TDD Interference Detection Guide 4 Interference Handling

4.1.2 CHR
In eRAN3.0, fields related to interference detection are added to the call history record
(CHR).
1. The UpPTS network indicator (NI) is used to detect interference in UpPTS areas. If the
NI value exceeds the specified threshold, interference exists.
2. The NIs for the first and last UL subframes are used to detect the interference to each UL
subframe.
3. The tunnel-level received total wideband power (RTWP) is used to detect the RTWP
between different tunnels. This helps check whether interference exists.
4. The power receiving strength for the first UL subframes 0 and 6 is used to differentiate
TDD long-distance interference.
5. The power receiving strength for the last UL subframes 0 and 12 is used to differentiate
interference caused by GPS clock loss.
The OMStar is used to analyze the CHR, and detailed information about it is not described in
this chapter.

4.1.3 Cell Performance Monitoring

In cell performance monitoring, the following three methods are used to monitor uplink
interference:
 RSSI statistics monitoring
 Interference detection monitoring
 TDD interference detection monitoring
TDD interference detection monitoring is recommended.

4.1.3.1 UL RSSI Statistics Monitoring

RSSI statistics monitoring allows you to detect the receive power on each RB allocated for
demodulation reference signals (DMRSs) in the current bandwidth, and the average receive
power of each antenna, that is, the total receive power on the uplink in the frequency domain.
When there is no load in a cell, RSSI statistics monitoring can be used to analyze the UL
interference. However, TDD interference cannot be observed if the interfering signal timeslot
is not contained in the symbol where a DMRS is located. Table 4.1.3.1.I.1.1.1.1 describes the
RSSI statistics monitoring result.
LTE TDD Interference Detection Guide 4 Interference Handling

Table 4.1.3.1.I.1.1.1.1 RSSI statistics monitoring result

When a cell carries no load, observe the interference as follows:

LTE TDD Interference Detection Guide 4 Interference Handling

On the OMC, choose Monitor > Signaling Trace > Signaling Trace Management and start
Interference RSSI Statistic Detect Monitoring.
The following figure shows the RSSI statistics monitoring result.

Figure 4.1.3.1.I.1.1.2 RSSI statistics monitoring result

Observe the interference distribution on the frequency domain as follows:

1. Export the data in CSV format.
2. Measure the average value of each RB in all measurement periods.
3. Draw a curve displaying the RSSI of RBs in all measurement periods or draw a curve
displaying the RSSI of all RBs in a measurement period

Figure 4.1.3.1.I.1.3.1 RSSI of RBs

LTE TDD Interference Detection Guide 4 Interference Handling

If there is no service, the RSSI of RBs is about –119 dBm. If there is service in the UL, the
RSSI of UL RBs increases, which is not suitable for interference observation.
The RSSI value can be used to determine whether the UE has interference. In addition, the
difference between RSSI values of different antenna ports can be used to determine whether
the engineering quality is poor or the device has faults.

NOTE
The RSSI value cannot be used for interference observation in the following scenarios:
 There is service in the UL.
If there is no service, the RSSI of RBs is about –119 dBm. If there is service, the RSSI of RBs
increases.
 A sector serves UEs.
In this scenario, the sector receives a high RSSI value of UE signals. In addition, the values of the main
and diversity RSSIs have a difference of 5 dB, which is normal.

In theory, the RSSI is calculated as follows:

RSSI = –174 dBm + 10 x log10(BW) + NF + AD quantitative error
Table 4.1.3.1.I.1.3.1.1 shows the typical RSSI values when there is no UE on each frequency
bandwidth. Note that the a difference of ±2 dB is acceptable.

Table 4.1.3.1.I.1.3.1.1 Mappings between bandwidths and RSSI values

Bandwidth (MHz) RSSI (dBm)

1.4 –109
3 –105
5 –103
10 –100
15 –98
20 –97

Interference exists if the RSSI value is 8 dB larger than that listed in Table 4.1.3.1.I.1.3.1.1.

4.1.3.2 UL Interference Detection Monitoring

Interference detection monitoring allows you to detect the interference and noise power on
each RB, and view the interference on the uplink. You can accurately check interference in the
frequency domain regardless of whether a cell has load. Table 4.1.3.1.I.1.3.1.1 describes the
interference detection monitoring result.
LTE TDD Interference Detection Guide 4 Interference Handling

Table 4.1.3.2.I.1.1.1.1 Interference detection monitoring result

This method can be used to observe interference regardless of whether there is load or not.
The monitoring method is similar to that described above. On the OMC, choose Monitor >
Signaling Trace > Signaling Trace Management and start Interference Detect Monitoring.
Figure 4.1.3.2.I.1.1.2 shows the UL interference detection monitoring result.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.1.3.2.I.1.1.2 UL interference detection monitoring result

The interference detection monitoring measures the subcarrier-level interference signal

strength. Therefore, in a scenario where there is no interference, the noise floor for monitoring
measurement is between –130 dBm and –128 dBm.
Interference exists if the IN value is 8 dB larger than the noise floor. Note that the NI value is
measured when there is no UE.

4.1.3.3 TDD Interference Detection Monitoring

TDD interference detection monitoring allows you to check whether TDD interference exists
based on the receive power of different symbols in the first and last UL subframe. You can
observe interference in the time domain to quickly locate TDD interference. Table
4.1.3.2.I.1.1.1.1 describes the interference detection monitoring result.
LTE TDD Interference Detection Guide 4 Interference Handling

Table 4.1.3.3.I.1.1.1.1 TDD interference detection monitoring result

LTE TDD Interference Detection Guide 4 Interference Handling

After interference is detected using the previous methods, check whether the interference
comes from the TDD system as follows:
On the OMC, choose Monitor > Signaling Trace > Signaling Trace Management and start
TDD interference detection monitoring.
The following figure shows the TDD interference detection monitoring result.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.1.3.3.I.1.1.2 TDD interference detection monitoring result

The TDD interference detection monitoring result shows that the PUSCH bandwidth is
classified into four frequency bands. The number of RBs allocated to each frequency band is
calculated as follows:
1. Use the number of RBs for the full bandwidth to minus the maximum number of RBs
that are occupied by the PUCCH.
2. Divide the result from step 1 by the number of frequency bands.
3. Round down the value from step 2.
Measure the average IN value of the subcarrier working on each frequency band, which are
RB Group1 IN Power, RB Group2 IN Power, RB Group3 IN Power, and RB Group4 IN
Power. The four groups of results show the general interference in the frequency domain.
The following fields are used in the TDD interference detection monitoring process to
determine the UL interference in the time domain:
 UpPTS IN Power
 Receive Power of Symbol 0 in First UL Subframe
 Receive Power of the 6th (or 4th) Symbol 0 in First UL Subframe
 Receive Power of Symbol 0 in Last UL Subframe
 Receive Power of the Last but Two Symbols on the Last UL Subframe
If any of the four fields indicates that there is interference, inter-system interference exists.

4.1.4 Cell Performance Monitoring on the LMT

Before the OMC is deployed, log in to the LMT to perform UL interference monitoring.
After the OMC is deployed, use the UL interference detection monitoring method.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.1.4.1.I.1.1.1 Cell performance monitoring on the LMT

Figure 4.1.4.1.I.1.1.2 shows the cell performance monitoring result on the LMT.

Figure 4.1.4.1.I.1.1.2 Cell performance monitoring result

LTE TDD Interference Detection Guide 4 Interference Handling

4.2 Interference Identification

4.2.1 Interference Type Identification
Interference types can be identified using the following procedure:
Step 1 Check whether the eNodeB serving the cell works properly. Check whether there are alarms
related to the antenna feeder system, TRX, eNodeB clock, or channel exceptions.
Step 2 Query the historical operation logs about the related cells. Check whether some eNodeB
hardware is added or modified, or data is changed. Check whether the interference occurs due
to operations in Step 2.
Step 3 Configure a normalized check. This avoids intra-frequency interference or unsynchronized
interference due to data configuration faults.
 Normalized check
− Use an inverse frequency spectrum analyzer to identify the interference type based on
the interference characteristics.
− Use an OMStar tool to analyze the CHR and identify the interference caused by GPS
unlocked faults or remote TDD interference.
− Use cell performance monitoring to determine interference types based on the
interference characteristics.
 Inter-system interference
Communicate with customers about the wireless system distribution that possibly has
suffered from interference. Eliminate the interference based on the analysis results. If the
interference persists, check whether unknown inter-system interference exists.
 External interference
Use the frequency scanner to search for the external interference source. Push the
customer to clear the frequency.
----End

4.2.2 Intra-System Interference

Intra-system interference includes interference caused by the following items:
 LTE TDD out of frame (UL)
 Long distance in TDD networks (UL)
 Incorrect data configuration (UL and DL)
 Coverage overlap (DL)
The faults such as GPS unsynchronization, faulty frequency configuration, missing neighbor
relationship configuration, and faulty PCI configuration can be detected on the eNodeB using
the configuration check or alarm query. The interference check methods are required in the
following scenarios:
 Common configuration check or alarm query may not identify the faults. For example, if
the GPS clock is abnormal, an alarm is reported and the alarm can be queried. If the GPS
synchronization loss occurs, no alarm is generated.
 A new site is enabled but the GPS is not connected.
LTE TDD Interference Detection Guide 4 Interference Handling

If coverage overlap occurs, the cell that is interfered with has a good RSRP but a poor SINR.
In addition, the UE handover ratio increases in the cell. The possible cause is that the system
design is not reasonable. For example, the pilot transmit power is set to a large value, the
eNodeB position or the antenna tilt is not proper, or inappropriate design for places with
complex geographical features, such as sea, lake, or mountain.
The OMC UL interference monitoring uses UL data collection function or tool to detect UL
interference.

4.2.2.1 UE Frequency Scan

This function requires test UEs.
There is interference on the DL if the following conditions are met:
 The DL RSRP measured by a UE at a test point is normal.
 The DL SINR is less than the specified value.
 DL data transmission stops.
 The BLER is greater than the specified value.
If the DL RSSI measured by a UE at a test point is abnormal, the live network is interfered
with another system. In this case, you can scan DL frequency spectrum to learn about
frequency-domain resource status.
The following figure shows the frequency spectrum for received signals of the UE under the
test. The horizontal axis represents the frequency, and the vertical axis represents the signal
strength.
In this test, a 15 kHz bandwidth is used as the signal measurement unit. Therefore, the noise
floor is –125 dBm, as shown in the following figure.

Operations:
After a UE enters the network, choose Configuration > Test Plan Control on the probe.
LTE TDD Interference Detection Guide 4 Interference Handling

Choose frequency scanning items and enter the frequency band to be scanned. The following
figure shows the frequency scanning procedure of LTE band 38.

Start the test.

Observe the frequency spectrum.

You are advised to learn about the principle for UE frequency spectrum scanning before
observing the frequency spectrum. This helps you better understand it. The following section
briefly describes the principle for UE frequency spectrum scanning.
LTE TDD Interference Detection Guide 4 Interference Handling

Probe-based UE frequency spectrum scanning currently supports a bandwidth of 20 MHz, 10

MHz, and 5 MHz. The 5 MHz is the minimum bandwidth. After the frequency band is
specified, the UE calculates the bandwidth for frequency spectrum scanning based on the
specified frequency band (each ARFCN represents 0.1 MHz). If a bandwidth of 20 MHz can
be scanned, the probe scans a bandwidth of 20 MHz. If the bandwidth is less than 20 MHz,
the probe scans a bandwidth of 10 MHz. If the bandwidth is less than 10 MHz, the probe
scans a bandwidth of 5 MHz.
Frequency spectrum scanning involves signals when the UE is in the offline state. Therefore,
the UE does not know where valuable signals start. For a bandwidth of 20 MHz, a 1 MHz
guard band is reserved on both sides of the bandwidth during intermediate frequency
processing. Therefore, the whole bandwidth of 20 MHz is scanned, but there is a 1 MHz dent
on one side of each bandwidth of 20 MHz. In this case, the strength of detected signals is
similar to the noise floor, and is about –130 dBm. The UE does not know where valuable
signals start, and the scanned frequency is not a multiplier of the configured 20 MHz.
Therefore, there are dents between signals. The following figure shows an example of
frequency spectrum scanning with an overall bandwidth of 50 MHz. In this figure, The 50
MHz bandwidth is divided into three parts for testing: 20 MHz, 20 MHz, and 10 MHz. The
bandwidth of useful signals is within the range of the first and second 20 MHz. Therefore, a
dent occurs between the useful signals, as shown in the red circle in the following figure.

Pay attention to this point during operations. To avoid this problem, you are advised to
configure different frequencies for starting scanning and observe multiple scanning results.

4.2.2.2 UL Interference Detected by Cell Performance Monitoring

1. Determine the interference type by the RSSI statistics monitoring or interference
detection monitoring.
Intra-system interference: Remote TDD interference and GPS synchronization loss
interference is symbol-level interference in the time domain and is evenly distributed in
the frequency domain. However, the RSSI statistics monitoring and interference
detection monitoring use the RB as the measurement unit in the frequency domain and
second in the time domain. Therefore, these methods cannot be used to analyze the intra-
system interference characteristics.
2. Check whether intra-system interference exists by the TDD interference detection
monitoring.
LTE TDD Interference Detection Guide 4 Interference Handling

The following fields are used in the TDD interference detection monitoring process to
determine the UL interference in the time domain:
− UpPTS IN Power
− Receive Power of Symbol 0 in First UL Subframe
− Receive Power of the 6th (or 4th) Symbol 0 in First UL Subframe
− Receive Power of Symbol 0 in Last UL Subframe
− Receive Power of the Last but Two Symbols on the Last UL Subframe
If any of the four fields indicates that there is interference, intra-system interference
exists.
a. If the UpPTS IN Power value of a cell is 6 dB larger than other field values,
interference exists in the UpPTS of the local cell but interference does not exist in
the UL.
a) If the Receive Power of the Last but Two Symbols on the Last UL Subframe
value of neighboring cells is 6 dB larger than that of the local cell, GPS clock
loss interference exists and the local cell is the interference source.
b) If the Receive Power of the Last but Two Symbols on the Last UL Subframe
value of a neighboring cell such as cell A is 6 dB larger than that of the local cell
and other cells have the same value as the local cell, GPS clock loss interference
exists and cell A is the interference source.
c) If neighboring cells and the local cell have the same field value, remote TDD
interference exists.
b. If the UpPTS IN Power value is similar to the Receive Power of Symbol 0 in First
UL Subframe value of the same cell, and they are 6 dB larger than other field
values, interference exists in the local cell UpPTS and UL.
a) If the Receive Power of the Last but Two Symbols on the Last UL Subframe
value of neighboring cells is 6 dB larger than that of the local cell, GPS clock
loss interference exists and the local cell is the interference source.
b) If the Receive Power of the Last but Two Symbols on the Last UL Subframe
value of a neighboring cell such as cell A is 6 dB larger than that of the local cell
and other cells have the same value as the local cell, GPS clock loss interference
exists and cell A is the interference source.
c) If neighboring cells and the local cell have the same field value, remote TDD
interference exists.
If there is interference in the frequency domain but no interference is detected using
TDD interference detection monitoring, intra-system interference may exist. In
certain subframe configurations on a no-load network, intra-system interfering
signals may not completely fall in the previously referred symbols. Therefore, you
must use reverse spectrum analysis to further locate intra-system interference.

4.2.2.3 Reverse Spectrum Analysis

Time domain power and frequency domain power
Time domain power for all symbols include power of two symbols in the UpPTS, and 14
symbols in the first UL subframe. Time domain power is used to check whether there is DL
symbol characteristics.
Frequency domain power of symbol x in subframe y of radio frame z indicates the power
condition of 2048 subcarriers on each symbol. Frequency domain power is used to check
whether there is pilot location characteristics.
LTE TDD Interference Detection Guide 4 Interference Handling

Reverse Spectral Data Collection

In eRAN3.0, the baseband data collected on the reverse link are automatically saved in a CHR
file. This is different from earlier versions. eRAN3.1 inherits this function and provides the
following new functions:
 Collecting data in the silent period. That is, scheduling is paused when a data collection
frame is transmitted in a cell with heavy traffic. This avoids impacts of UL signals on
interfering signals.
 Collecting data for each RRU in an SFN cells
 Collecting data of five consecutive frames using MML commands
 Collecting data of complete frames
On the OMC or Web LMT, run the GET CELLRICDATA command with Main eNodeB
Local cell ID, Main eNodeB Local cell ID, Cabinet No. of RRU, Subrack No. of RRU,
Slot No. of RRU, RX Channel No. of RRU, and Silence Flag(ON or OFF) specified to
collect reverse baseband data. This command is used to collect data about long-distance
interference to the local cell. Based on the collected dedicated signals (DSs) or cell reference
signals (CRSs), PCIs can be obtained to help identify the cells that cause long-distance
interference. It is recommended that CRSs be collected. Run the ULD LOG command or use
INC to collect CHR data ten minutes after the GET CELLRICDATA command is executed.
Note that SilenceFlag must be set to ON if you want to collect data in the silent period. Set
SilenceFlag to OFF in other cases.
If DSs are collected, run the SND CELLRICPCISEQ command before running the ULD
LOG command. This command is used to transmit data about cell long-distance interference.
DSs are generated based on the equivalent PCI of a cell. The equivalent PCI equals the sum of
the cell PCI and the PCI offset specified in this command. DSs are used to distinguish cells
with the same PCI and help identify the cells that cause long-distance interference. After the
command is successfully executed, run the ULD LOG command or use INC to collect CHR
data.
Note that Call Log Collection must be selected, as shown in Figure 4.2.2.3.I.1.1.1.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.1.1.1 Collecting CHR data using INC

Reverse Spectrum Analysis Using Spectrum Analyzer

To apply for a license of Spectrum Analyzer, contact Rong Chaohong (employee ID:
00129272).
After the data collection is complete, use Spectrum Analyzer to analyze UL data. The
following describes how to use this tool.
For details about how to install it, see Guide to LTE TDD Reverse Frequency Spectrum
Analyzer.
In versions later than eRAN3.1, the collected spectrum contains data of five frames (ten 5 ms
half-frames), which may be saved in multiple files. Therefore, the first step is to combine
CHR files.
Step 1 Combine CHR files.
Before combination, you must confirm the CHR files to be combined, because not all CHR
files collected using INC contain reverse spectral data. At first, open the last generated CHR
file and check the data of which frames are contained in it. Based on the import result, the
data of four frames are contained.
For example, select Flow_3 and click Start.
The analysis result is incompletely displayed in the right pane, which indicates that this CHR
file does not contain complete reverse spectral data. The result is the same for Flow_6.
If you select Flow_4 or Flow_5, the reverse spectral data are complete.
LTE TDD Interference Detection Guide 4 Interference Handling

Therefore, you must combine this CHR file with the preceding CHR file and the following
CHR file.

Figure 4.2.2.3.I.1.1.2 Analyzing a CHR file

In the main window, choose Tool > CHR Files Merger.

Figure 4.2.2.3.I.1.1.3 Choosing CHR Files Merger

Click Merger.

Figure 4.2.2.3.I.1.1.4 CHR Files Merger

Select the CHR files to be combined in the file generation order. As shown in Figure
4.2.2.3.I.1.1.5, the three files 184732B0.CHR, 1847576C.CHR, and
LTE TDD Interference Detection Guide 4 Interference Handling

20121127_105617+0800_0050.CHR are generated in descending order, and therefore you

must select them in this order. Otherwise, an error may occur during the file combination.

Figure 4.2.2.3.I.1.1.5 Selecting CHR files

Click Open.
A dialog box is displayed, indicating that the combination is successful. A file started with
Merger_ can be found in the directory where Spectrum Analyzer is installed.

Figure 4.2.2.3.I.1.1.6 Dialog box indicating a successful combination

Step 2 Import data.

Click Import Data and select the CHR file previously combined or an original CHR file to
import data. Then, you can view the data of five consecutive frames if you select the CHR file
previously combined.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.2.1.1 Time domain power for all symbols

Step 3 Analyze and view data.

Select frames to be analyzed, set Bandwidth and ULCP Type, and click Start.
Click the drop-down list box under View.
You can view charts about the average power in the time and frequency domains, and charts
about the power of each symbol in one UL subframe in the frequency domain.
You can determine the interference type based on analysis of the interference waveform in the
frequency domain and interference level of 14 symbols in each subframe.

Typical GPS Synchronization Loss Interference

The following figure shows the time domain power for all symbols.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.3.1.1 Time domain power for all symbols

3 symbols 2 symbols 3 symbols 2 symbols

The following rules can be observed from Figure 4.2.2.3.I.3.1.1.

 Interference is distributed in one symbol in the time domain.
 A symbol where interference exists is two or three symbols away from the next symbol
where interference exists.
 Frequency domain power of a single symbol
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.3.1.2 Frequency domain power of symbol 1 in subframe 2 radio frame 0

Subframe 2 is the first subframe in the UL.Choose Matlab Figure ( )

to query each subframe in the red frame of Figure 4.2.2.3.I.3.1.2.
Starting from subcarrier 425, interference power with a difference of 5 regularly occurs.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.3.1.3 Frequency domain in details

Figure 4.2.2.3.I.3.1.4 shows the PCI detection result.

Figure 4.2.2.3.I.3.1.4 PCI detection result

The PCI Detect function can be used to find out the PCI of the interference source eNodeB.
The reverse frequency spectrum analyzer is used to detect multiple cells. The result indicates
that the cell with a PCI of 90 has time frequency synchronization loss.
UL and DL subframes are aligned by extending the time in the previous figure. The result
indicates that UL interference is closely related to the DL pilot distribution.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.3.1.5 DL symbol mappings

LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.3.I.3.1.6 Viewing the power in the time and frequency domains

----End

4.2.2.4 Uplink Interference Using OMStar

Currently, OMStar supports CHR interference data analysis instead of reverse spectrum
analysis. The data traced is similar to those traced in TDD interference detection monitoring.
For details, see section 4.1.2"CHR."
The following describes how to use OMStar to analyze UL interference.
Step 1 Collect CHR data.
Create a task using INC. Note that eNodeB configurations must be collected at the same time.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.4.I.1.1.1 Collecting CHR data

Step 2 Import CHR data using Transdata.

For details, see "Importing the Configuration Data" and "Importing the CHR Data" in the
section "Data Management" of Transdata User Manual.
Step 3 Use OMStar to analyze CHR data.
After the data are imported, open OMStar and select the created project.
Click Scene Application and expand Other Scenes.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.2.4.I.3.1.1 MAINEX OMStar

Double-click LTE_InterferenceCheck.
Select the eNodeB to be analyzed, select items to be analyzed, and click OK.
The analysis report is automatically exported.

Figure 4.2.2.4.I.3.1.2 Starting CHR data analysis

LTE TDD Interference Detection Guide 4 Interference Handling

As shown in Figure 4.2.2.4.I.3.1.3, the desired UL interference data are contained in the
report.

Figure 4.2.2.4.I.3.1.3 CHR data analysis report

For details about the intra-system interference detection rules based on the OMStar, see
section 4.2.2.2"UL Interference Detected by Cell Performance Monitoring."
----End

4.2.3 Inter-RAT Interference

The following devices may have interference to a network:
 Television station
 Large-power broadcasting station
 Microwave
 Radar
 High-voltage power cable
 Simulated eNodeB
 Inter-RAT network
 Confidential equipment used for a meeting
 Interference unit used at a gas station
The impact of inter-RAT interference is similar to that of intra-system interference. When
interference occurs, signals are interfered with. The impact of different external interference
sources differs from each other. For example, interference caused by some external
communications equipment may have an impact only on a frequency band. When the
LTE TDD Interference Detection Guide 4 Interference Handling

frequency band is separated, interference can be avoided. In addition, interference caused by a

radar has an impact on a network at different periods.
All external interference can be located in a similar way. For DL external interference, you
must use a spectrum analyzer and a directional antenna to locate the interference source. For
UL external interference, you can use cell performance monitoring, reverse spectrum analysis,
and CHR log analysis to locate the interference source.

4.2.3.1 Determine the interference type by the RSSI statistics monitoring or

interference detection monitoring.
Typical spurious interference
Spurious interference occurs in the TDD system, and the NI intensity slowly decreases. The
signal strength is about –80 dBm at RB 0, but it decreases to –110 dBm at RB53. The signal
strength is weak when the RB is away from RB 0.

Figure 4.2.3.1.I.1.1.1 NI distribution of UL interference

NI Distribution of East Garden FE3

-50
-60 1 5 9 13 17 21 25 29 33 37 41 45 49 53 57 61 65 69 73 77 81 85 89 93 97
NI Intensity (dBm/RE)

-70
-80
-90
-100
-110
-120
-130
RB Number

Typical intermodulation interference

The frequency band that is interfered with has abnormal waveform such as third- or fifth-
order bandwidth. Figure 4.2.3.1.I.1.1.2 shows that the interference from the GSM
intermodulation signals.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.2.3.1.I.1.1.2 NI distribution of UL interference

NI Distribution of GeXin FE1

-80
NI Intensity (dBm/RE) -85 1 5 9 13 17 21 25 29 33 37 41 45 49 53 57 61 65 69 73 77 81 85 89 93 97
-90
-95
-100
-105
-110
-115
-120
-125
RB Number

Typical blocking interference

Blocking interference is not obvious in the frequency band, and therefore a blocking filter is
required to detect interference. Figure 4.2.3.1.I.1.1.3 shows the NI comparison between
interference detected with and without a block filter.
Note that the waveform is for reference only, and other blocking interference waveform may
not be the same.

Figure 4.2.3.1.I.1.1.3 NI comparison between block interference and no block interference

NI Comparison between Block Interference and no Block

interference
-50
No Block Interference
NI intensity (dBm/RE)

-60
1
5
9
13
17
21
25
29
33
37
41
45
49
53
57
61
65
69
73
77
81
85
89
93
97
-70 Block Interference
-80
-90
-100
-110
-120
-130
RB Number

4.2.3.2 Determine the Interference Type by Frequency Scanning

In the actual network, interference is more complex and multiple types of interference is
overlapped in the frequency band, and no obvious interference characteristics can be found. In
this case, interference cannot be classified by RSSI statistics monitoring or UL interference
detection monitoring. Meanwhile, in the commercial network, specific interference check
LTE TDD Interference Detection Guide 4 Interference Handling

methods are required because signals cannot be completely closed in the TDD frequency
band.
Frequency scanning can be used to find out the interference source, and therefore this section
is incorporated into section 4.3.2"Inter-System Interference Handling."

4.3 Interference Location and Handling

For each type of interference, the period during which interference occurs can be detected.
If interference occurs from 10:00 to 18:30 during a day and disappears at night or weekends,
you can conclude that interference mainly occurs during work hours at a day.
If intra-system interference occurs, it may be caused by UEs from some enterprises.
If inter-RAT interference occurs, it may be caused by interference sources from some
factories.

4.3.1 Intra-System Interference Location—Interference Map

Intra-system interference of cells can be displayed on the map using the engineering
parameters. Interference distribution is closely related to interference intensity, and therefore
interference source can be detected using the distribution characteristics.
GPS synchronization loss interference
As shown in Figure 4.3.1.1.I.1.1.1, eNodeBs marked in blue are deployed by other suppliers
and eNodeBs marked in other colors are deployed by Huawei. Interference intensity is shown
using colors from red to green in descending order, and cells in red are most severely
interfered with.
Interference intensity gradually weakens from cells in red to their neighboring cells,
indicating that the interference source is within the cells in the red frame. Detection results
indicate that eNodeBs deployed by other suppliers has GPS unlocked faults and thereby
interference occurs, affecting other cells nearby.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.3.1.1.I.1.1.1 Interference map

Remote TDD interference

The interfering eNodeB and the interfered eNodeB are far from each other, the distance
between which is from 21.4 km to 214.3 km based on the GAP protection distance. Therefore,
interference is displayed in a large area.
As shown in Figure 4.3.1.1.I.1.1.2, UL interference exists in two sectors facing each other.
The distance calculated based on the number of interference symbols is consistent with the
actual distance.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.3.1.1.I.1.1.2 Interference map—sea

Figure 4.3.1.1.I.1.1.3 Interference map—distance

LTE TDD Interference Detection Guide 4 Interference Handling

The distance between two eNodeBs may be long because of the heights. In this case,
interference differs from that of the sea case and only cells located in a high place can
interfere cells located in a low place, as shown in Figure 4.3.1.1.I.1.1.4.

Figure 4.3.1.1.I.1.1.4 Interference map—height distance

4.3.2 Inter-System Interference Handling

If inter-system interference occurs, a spectrum analyzer is recommended to locate the
interference source.

4.3.2.1 UL Interference Location for TDD Networks

If the data analysis result shows that the UL is interfered with an external system, the
interference source must be located. The following describes the procedure for interference
location during a UL test at specified places.
Step 1 Learn about frequency spectrum allocation and communications system in use in the local
area from an operator or based on the Internet. Then, identify the interference sources based
on collected data.
Step 2 Connect the test equipment according to the following figure. Use a directional antenna with a
minimum gain of 10 dB (a Yagi antenna is recommended). In the coverage range of the
eNodeB, test the strength of interference signals every 45° and identify the direction where
the interference signals are strongest. Ensure that the parameter setting on the spectrum
analyzer is consistent with that for the electromagnetic background interference test.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.3.2.1.I.2.1.1 Connection of equipment for UL interference location

Yagi antenna

Spectrum analyzer
UL band-pass filterLow-noise amplifier

Step 3 Change the SPAN setting and center frequency based on the characteristics of detected
interference signals. Then, analyze the frequency spectrum width, distribution, changes, and
strength of the interference signals.
Step 4 If the interference is caused by another system whose antenna and feeder system is installed in
the same place with the live system, locate the interference source. Determine the interference
type. Otherwise, go to the next step.
Step 5 Determine the direction where the interference signals are strongest and narrow the
interference range based on the three-point positioning method and drive tests. Then, locate
the interference sources. At each point, set the parameters on the spectrum analyzer based on
the SPAN and central frequency obtained in Step 3. Then, use the spectrum analyzer to scan
the strength of interference signals in each direction and identify the direction with strongest
interference signals. Figure 4.3.2.1.I.5.1.1 shows the three-point positioning method used on
the UL.

Figure 4.3.2.1.I.5.1.1 Three-point positioning method used on the UL

The procedure for interference location during a UL drive test is the same as that for DL. For
details, see section 4.2.2.1 "UE Frequency Scan."
----End
LTE TDD Interference Detection Guide 4 Interference Handling

4.3.2.2 DL Interference Location for TDD Networks

Based on the geographical distribution diagram and frequency analysis of the drive test,
determine the areas with interference. In each area, use the three-point positioning method to
narrow the interference range and locate the interference sources. The initial parameters are
set to the same values as the parameters in the electromagnetic background DL interference
test.
During the test, multiple interference sources may exist. You can change the frequency or
power to locate the interference source based on the interference property. You can set the
parameters such as frequency, reverse-band working (RBW), and reference level based on the
actual requirements.

Figure 4.3.2.2.I.1.1.1 Three-point positioning method used on the DL

Figure 4.3.2.2.I.1.1.2 shows the connection of test equipment.

Figure 4.3.2.2.I.1.1.2 Connection of equipment for DL interference location

Yagi antenna

Spectrum analyzer
DL band-pass filterLow-noise amplifier
LTE TDD Interference Detection Guide 4 Interference Handling

The following problem occurs during an electromagnetic background DL interference test:

Within the whole DL frequency band defined in a protocol, the Global System for Mobile
Communications (GSM), Code Division Multiple Access (CDMA), UMTS, or WiMAX
system is carried on neighboring channels. For these systems, data is transmitted on the DL. If
the test points during drive tests are near the site of these systems, interference is severe in the
target frequency band of the electromagnetic background interference test. You are advised to
choose several typical points for locating this type of interference. In this way, you can obtain
the frequency spectrum of the neighboring frequency band and the target frequency band.
Then, you can approve that inter-frequency interference exists.
A frequency clearance test for an operator is used as an example here. During the test, an
Agilent scanner is used for drive tests and the target frequency band to be tested is from 880
MHz to 885 MHz. The scanner RBW is set to 30 kHz, and the noise floor of the scanner is
about –110 dBm. The following figure shows that the strength of many signals is greater than
–110 dBm. Therefore, interference occurs in many areas.

Figure 4.3.2.2.I.1.1.3 Example of interference distribution during a DL interference test

After interference location, all interference is caused by the CDMA system deployed by
another operator and working on a frequency band from 887 MHz to 880 MHz.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.3.2.2.I.1.1.4 Example of DL interference sources

4.4 Interference Handling

4.4.1 Intra-System Interference Handling
1. GPS synchronization loss interference
If GPS synchronization loss interference exists, check GPS synchronization faults in the
specified area and rectify the GPS faults. Meanwhile, check the GPS on the entire
network regularly and ensure that no similar fault occurs.
2. Remote TDD interference
Perform the following operations:
− If additional frequencies are available, use different frequencies for interfering
eNodeBs and interfered eNodeBs.
− If no additional frequencies are available, adjust the azimuth to avert interference and
adjust tilts to reduce interference power.
3. Cross-cell coverage
Check whether interference is within the normal range. If the interference is out of the
normal range, optimize the network in terms of the network structure, antenna
installation height, azimuth, tilt, and power. Perform the following steps to check intra-
frequency sectors that are interfered with.
− If additional frequencies are available, use different frequencies for interfering
eNodeBs and interfered eNodeBs.
− If no additional frequencies are available, replan the PCI to avoid mod3 interference
and reduce pilot interference.
− If no additional frequencies are available and PCI mod3 interference is eliminated,
adjust the azimuth to differ the interference directions and adjust tilts to reduce
interference power.
LTE TDD Interference Detection Guide 4 Interference Handling

4.4.2 Inter-System Interference Handling

i. Inter-System Co-site Interference Handling
Handle interference as follows:
1. Add space isolation between two systems.
Table 4.4.2.1.I.1.1.1.1 lists the requirements for isolation between two systems.

Table 4.4.2.1.I.1.1.1.1 Space isolation requirements

　 Isolation Distance (m)

Horizontal distance >= 3 m

Vertical distance >= 0.5 m
Horizontal and vertical distances >= 0.5 m
>= 0.5 m

In the actual network, the space isolation between two systems must be set based on main
equipment RF performance, frequency isolation between systems, and antenna performance.
For example, if frequency band F (1880 MHz to 1900 MHz) receives interference from DCS
(1850 MHz to 1872.6 MHz), the space isolation requirements are shown in Figure
4.4.2.1.I.1.1.2.
LTE TDD Interference Detection Guide 4 Interference Handling

Figure 4.4.2.1.I.1.1.2 Space isolation requirements

2. If the physical space for the antenna installation is insufficient, eliminate the interference
based on the interference type.
− If it is the blocking interference, improve the anti-blocking capability in the TDD
system by adding a filter on the RRU top.
− If it is the spurious interference, improve the out-of-band interference suppression
capability by adding a narrow-band filter on the interference equipment top.
− If it is the intermodulation interference, improve the device or antenna feeder
performance. If the interference is caused by the jumper connector, replace the
jumper connector. If the interference is caused by the antenna and feeder system,
replace an antenna with better intermodulation suppression KPIs
ii. Inter-System Non-Co-Site Interference Handling
Handle interference using the following steps:
Step 1 If the interference comes from systems deployed by other vendors, negotiate with the
operators and increase the space isolation distance by adjusting azimuth or tilts, add frequency
isolation by replanning frequencies, and so on.
Step 2 If the interference comes from illegal systems, negotiate with the Radio Spectrum Committee
and clear the frequency.
----End
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

2 Typical Cases

For details about more cases, see TDD LTE Interference Cases.

2.1 Cases for Intra-System Interference

2.1.1 Network Entry Failures Due to out of Frame During a Test
Conducted by MIIT in Huairou
Description
A UE can occasionally enter a network at some places. When the RSRP is normal, for
example, –70 dBm, the UE cannot enter the network.
Analysis
The following describes the possible reasons for network failures:
 Internal hardware fault of an eNodeB or UE
 External interference
Solution
1. On the LMT, enable multiple eNodeBs one by one to verify network entries.
All UEs can enter the network.
Then, enable the eNodeBs simultaneously.
Network entry fails.
This proves that all hardware of the eNodeBs and UE is in good conditions.
2. Query the RSSI.
The UL RSSI on the LMT is about –80 dBm, and the value is different from the normal
value –100 dBm when there is no UL network entry.
Then, synchronize the GPS clocks of all eNodeBs.
3. Enable multiple eNodeBs one by one to verify network entries again.
All UEs can enter the network.

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 52

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

2.1.2 GPS Synchronization Loss Interference at Site S in Country

S
Description
When UEs perform UL services in the northern part of a city, service rates are low. Then, the
UL interference detection is monitored and the result shows that the UL IN value of this cell is
excessively high and neighboring cells have excessively high IN values.

Figure 2.1.2.1.I.1.1.1 Interference map

Analysis
Use a reverse spectrum analyzer to restore the spectrum in the receive channel using the data
collected by frontline engineers.

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 53

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

Figure 2.1.2.1.I.1.1.2 Time domain power for all symbols

3 symbols 2 symbols 3 symbols 2 symbols

The following rules can be observed from Figure 2.1.2.1.I.1.1.2.

 Interference is distributed in one symbol in the time domain.
 A symbol where interference exists is two or three symbols away from the next symbol
where interference exists.
 Frequency domain power of a single symbol

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 54

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

Figure 2.1.2.1.I.1.1.3 Frequency domain power of symbol 1 in subframe 2 radio frame 0

Figure 2.1.2.1.I.1.1.4 Frequency domain in details

Subframe 2 is the first subframe in the UL. Choose Matlab Figure ( )

to query the each subframe in the red frame of Figure 4.2.2.3.I.3.1.2
Starting from subcarrier 425, interference power with a difference of 5 regularly occurs.

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 55

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

 Figure 2.1.2.1.I.1.1.5 shows the PCI detection result.

Figure 2.1.2.1.I.1.1.5 PCI detection result

The PCI Detect function can be used to find out the PCI of the interference source eNodeB.
The reverse frequency spectrum analyzer is used to detect multiple cells. The result indicates
that the cell with a PCI of 90 has time frequency synchronization loss.
UL and DL subframes are aligned by extending the time in the previous figure. The result
indicates that UL interference is closely related to the DL pilot distribution.

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 56

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

Figure 2.1.2.1.I.1.1.6 DL symbol mappings

Solution
Interference exists because GPS clock is unlocked. After the GPS clock fault is rectified,
interference is eliminated.

2.2 Cases for Inter-System Interference Handling

2.2.1 Inter-System Interference on Frequency Band F at City S in
Country C
Description
During a single eNodeB verification process at city S, multiple eNodeBs have unsatisfactory
UL throughputs. UL interference monitoring results indicate that UL RSSIs of the traced
eNodeBs are abnormal when there is no UE, and the RSSI values are higher than those when
there is no load.
Traffic statistics on the live network indicates that the number of cells that are severely
interfered with accounts for 8.9% of the total cells, and the noise floor increases by more than
28 dB.

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 57

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

Analysis
Locate the interference.
Use a frequency scanner to scan frequencies on some eNodeBs and many eNodeBs have the
same time domain and frequency domain phenomenon, as shown in the following figures.
Frequency domain frequency scanning

Time domain frequency scanning

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 58

Copyright © Huawei Technologies Co.,
Ltd.
eRAN3.1 LTE TDD
Interference Detection Guide 6 Others

The frequency domain scanning result indicates that the TDD system working on 1850 MHz
to 1872.6 MHz is affected by DCS 1800 signals, which is a temporary frequency band used in
city S. During frequency scanning, when the Yagi antenna is installed facing the DCS 1800
antenna, interference is the most severe. The time domain frequency scanning shows that time
domain length is 0.577 ms, which is the same as the DCS timeslot length. Therefore, the
interference comes from DCS 1800 frequency band.
Use the co-site interference detection method to detect specified eNodeBs and find out that
most of the cells are affected by intermodulation interference from DCS 1800 frequency band.
Solution
Detect intermodulation interference for cells that are interfered with and check whether the
interference comes from the antenna or jumper.
 Replace the antenna or jumper where intermodulation exists.
 Clear the high-band frequency (about 7.6 MHz) of the DCS 1800 temporary frequency
band.

Issue 3.1 (2012-11-22) Huawei Proprietary and Confidential 59

Copyright © Huawei Technologies Co.,
Ltd.
 3 Others

3.1 Frequency Clearance Before Network Planning

If an LTE frequency is used without authorization, the frequencies of the whole network must
be scanned before network planning. By doing this, places with in-band and out-of-band
interference can be located. Then, operators can clear the frequencies at the places or take
preventive measures at places with out-of-band interference.

3.2 Silence Frame Collection (Not Available at Present)

There are online UEs in a network if number allocation is commercialized at some sites. If UL
interference exists, and the strength of interference signals is less than or similar to that of UE
signals, differentiating UL signals and external interference is difficult. Therefore, external
interference cannot be accurately located. In addition, online UEs cannot be forced to exit the
network. To solve this problem, silence frames can be collected for analysis in other systems.
When silence frames are being collected, resource scheduling is performed at the MAC layer
to prohibit UL services of some frames. Then, UL data about the frames are collected for
frequency spectrum analysis. After the analysis, the frequency spectrum of interference
signals can be generated for interference location.
eRAN3.1 LTE TDD
Interference Detection Guide A Acronyms and Abbreviations

A Acronyms and Abbreviations

B
BLER block error rate

C
CDMA Code Division Multiple Access
CHR call history record

D
DL downlink
DwPTS downlink pilot timeslot

E
eNodeB E-UTRAN NodeB

F
FPGA field programmable gate array

G
GP guard period
GPS Global Positioning System
GSM Global System for Mobile Communications

I
eRAN3.1 LTE TDD
Interference Detection Guide A Acronyms and Abbreviations

IF intermediate frequency
IP Internet Protocol

L
LOS line of sight
LTE Long Term Evolution

M
MAC media access control
MML man-machine language

N
Nf noise factor
NI network indicator

P
PA power amplifier
PCI physical cell identifier
PRACH physical random access channel
PRB physical resource block

R
RB resource block
RBW reverse-band working
RRU remote radio unit
RSRP reference signal received power
RSSI received signal strength indicator
RTWP received total wideband power

S
SINR signal to interference plus noise ratio
SNR signal noise ratio
SRS sounding reference signal
eRAN3.1 LTE TDD
Interference Detection Guide A Acronyms and Abbreviations

T
TDD time division duplex
TD-SCDMA Time Division-Synchronous Code Division Multiple Access

U
UE user equipment
UL uplink
UMTS Universal Mobile Telecommunications System
UpPTS uplink pilot timeslot

W
WiMAX Worldwide Interoperability for Microwave Access