GCI Huawei 3G Network Optimization

Nubee Training Center (NTC)
3G Network Field Optimization & Tools
www.nubeesystem.com
SECTION – 2
PT. Nubee System

Mayapada Tower, 11th Floor
Jl. Jendral Sudirman Kav. 28
Jakarta 12920
http://campus.nubeesystem.com
OUTLINE 68
Huawei RNC & Node B Short Introduction
Huawei Optimization Tools
Huawei 3G KPI & Reports
Huawei RNC & Node B counters
Company Confidential
68 © PT. Nubee System
Abbreviations
WMPT WCDMA Main Processing and Transmission Unit

WBBPa WCDMA Baseband Process unit Type A
WRFU WCDMA Radio Filter Unit
UBFA Universal BBU Fan Unit Type A (2U)
UEIU Universal Environment Interface unit
UELP Universal E1/T1 Lighting Protection unit
UFLP Universal FE/GE Lighting Protection unit
UPEU Universal Power and Environment Interface Unit
UTRP Universal Transmission Processing Unit
DCDU-01 Direct Current Distribution Unit-01
CPRI Common Protocol Radio Interface
PSU The power supply unit
PMU The power and environment monitoring unit
APM Advanced Power Module
69 © PT. Nubee System Page 69
BSC6810 Cabinets
Item Specification
Outline 2200˄H˅h600
dimensioning (mm) ˄W˅h800˄D˅
Height of the
46U
available space
Weight 140~350kg
Power RSR: 4,650W

consumption RBR: 4,660 W
Front View Rear View

BSC6810 Subrack
• 12 U shielding subrack of Huawei

• 28 slots with backplane is positioned in the middle
Front View Rear View

Capacity
• It supports up to 51,000 equivalent voice

channels
• It supports up to 3,264Mbit/s PS service
processing (UL+DL) 6,000
• It supports up to 1,700 NodeBs and 5,100
Cells 15,000
• It provides Single-Subrack Solution: supports 24,000
6,000 equivalent voice channels and
384Mbit/s PS data capacity;
33,000
42,000
51,000
Page72
BTS3900 Appearance
Type Parameters
Dimensions 600(W)*900(H)*450(D)
Weight under full configuration ≤ 160Kg

3*1 and 3*2 Weight ≤ 120Kg
- 48V : Input range of voltage -38.4V DC to -57V DC
+24V: Input range of voltage +21.6 V DC to +29 V DC
220AC : Input range of voltage 220AC:Single-phase or
three-phase power cable
Working Temperature -20Ԩ̚+50Ԩ
BTS3900 Single Cabinet Full Configuration Structure
1U
9U
19U
2U
1U
1U
2U
1U
2U
- 48VDC + 24VDC 220V AC

Single Cabinet Single Cabinet Single Cabinet
BTS3900 Stacked Cabinets Full Configuration Structure
3U
DBS3900 Overview
• DBS3900 is a distributed NodeB of forth

generation NodeB.
• DBS3900 system consists of:
• BBU3900 Antenna
• RRU3804 or RRU3801E RRU TMA
• Antenna and feeder system 3804 or 3801E RF jumper
Feeder
grounding
-48V DC cable
Power cable RF jumper
power
BBU3900
-48V/ 24V
DC power Grounding
Power cable cable
Trunk cable Fiber or CPRI high-speed

signal cable
RNC
DBS3900 Capacity and Characteristics
Specification of the DBS3900

• High capacity;
• BBU3900 supports 24 cells, with 1,536 UL CEs and 1,536 DL
CEs.
• One RRU3804 supports the 4-carrier configuration.
• When the NodeB expands from 1x1 to 1x4 or from 3x1 to
3x4, no extra RRU is required.
Characteristics of the DBS3900
l Supports RRU cascading
[ When using the 1.25 G optical module, cascading levels ≤ 4

[ When using the 2.5 G optical module, cascading levels ≤ 8
DBS3900 Capacity and Characteristics
Characteristics of the DBS3900
l Supports ATM ǃIP and ATM/IP Dual stack networking;

l Supports Multiple Clock and Synchronization Modes;
ð Iub interface clockǃ
ð GPS clock and
ð Internal clock
l Supports high-speed packet access (HSPA) technology
[ HSDPA allows the traffic at up to 14.4 Mbps for a single cell
[ The peak uplink data rate of an HSUPA subscriber is up to 5.76 Mbit/s.
l Supports the Multimedia Broadcast and Multicast Service (MBMS)
BTS3900 Capacity and Characteristics
• System capacity specifications:

• BTS3900 can support up to: uplink and downlink 1536 CEs
• BTS3900 can support up to: 3*8 cells or 6*4 cells
l Characteristics
[ Transmission Type: E1/T1, FE (electrical port ), FE (optical port ),

[ Networking mode: star, chain, tree, ring and hybrid
[ Synchronization clock sources: Iub interface clock, GPS, and internal clock
[ Handover types: softer handover, soft handover and hard handover
[ Services: CS services, PS services , mixed services and position services
[ Enhanced functions˖RET , HSDPA , HSUPA
OUTLINE 80
Huawei 3G Optimization Tools
Performance/alarms
/configurations/
iManagerTM M2000
engineering para.
Capture test data
GENEX
Nastar
RAN auto Node B

configuration RNC
console
Analysis Result
sharing
Node
Nod eB
v GENEX Probe HLR/AC

GENEX Node B
v AGILENT
v QUALCOMM
Assistant RNS
v HUAWEI RNC PSTN
PLMN
MSC/SSP/VLR
MSC ISDN
Node B
RNC
GMSC/SSP
GENEX CN
Node B
Probe
Node BRNS
OUTLINE 82
RNC_A-Retainability
Some cells in the border

with RNC Meruya suffer Due to PS IRATHO
RAB Loss SRB Reset due degraded after
to Iur not yet connected SGSN rehoming
Due to PS IRATHO
degraded after
SGSN rehoming
RNC_A-Mobility
ISHO problem solved
after MSC LAC
reconfiguration
Missing LAC neighbor

relation in CN between
LAC 1047 (3G) and LAC
102 & 157 (2G) ISHO back to degraded
since 17-Nov. Still under
investigation
RNC_A-Traffic
Urban area. Traffic

relatively decreased
every week-end days
ISHO CS Degradation Since 17 Dec 09
ISHO CS End2End degraded

again since 17-Dec-09 5PM.
Previously the problem already
solved on 14-Dec-09 after
troubleshooting on LAC
configuration at Core Network
side.
OUTLINE 87
RNC & Node B Counters
Nubee Training Center (NTC)
Sample Optimization Cases & How to Analyze
www.nubeesystem.com
SECTION – 3
PT. Nubee System

Mayapada Tower, 11th Floor
Jl. Jendral Sudirman Kav. 28
Jakarta 12920
http://campus.nubeesystem.com
OUTLINE 90
Analyze by Drive Test Result
Analyze by KPI or Counters
Analyze by Signaling Tracing

Case 1. Analyzing Pilot Pollution Problem
Pilot Pollution analysis based on scanner data
Pilot pollution causes the following network problems.
• Ec/Io Deterioration: Multiple strong pilots interferes useful functional signals,
so Io increases, Ec/Io decreases, BLER increases, and network quality
declines.
• Call Drop Due to Handover: More than three strong pilots or no primary
pilot exists in multiple pilots, frequent handover occurs among these pilots.
This might cause call drop.
• Capacity Decline: The interference of the areas with pilot pollution
increases, the system capacity declines.
Scanner Pilot Pollution
KPI:
Using Assistant to analyze Pilot Pollution:
1. Customize Pilot Pollution
2. Locate Pilot Pollution area
Pilot Pollution happens near the bridge. Multiple strong
pilots include:
• signals on the thither side of the bridge
• ssignals
ignals along
along with
with the treet
the sstreet
Pilot Pollutions Area
3. Confirm the cells causing Pilot Pollution
• SC224 (available signals on the thither side of the bridge)
• SC50, SC176/SC178, SC170 (overshooting on the thither side of the bridge)
• SC26 (overshooting along with the street)
• SC1 (available signals)
4. Solutions
Antenna down tilt adjustment
• Reduce antenna down tilt to increase cell coverage
range on the thither side of the bridge. e.g. SC224.
• Increase antenna down tilt to reduce coverage range
on the thither side of the bridge. e.g. SC170 and
SC176/SC178.
• Increase antenna down tilt to reduce coverage range
along with the street, e.g. SC26.
After adjustment, pilot pollution here reduced above

90%
Case 2. Call Drop due to weak Coverage
Weak coverage
The characteristic of weak coverage is: weak RSCP

and Ec/Io, TxPower increases, even reaches the
maximum before call drop
1. Check the Ec/Io and RSCP around this call drop

point
We will find that receive signals in red box are very

weak, especially before the call drop.
So we need to observe Ec/Io and RSCP on chart in

more detail.
Weak coverage
2. Observe RSCP and Ec/Io

before call drop
On the charts, we will find that

Ec/Io and RSCP in Active Set
and Monitor Set became worse
and worse.
UE has send “Measurement

Report” many times, but there
was no right cell to provide
enough coverage.
Finally, call drop occurred.
Weak coverage
3. Analysis
The distance from call drop point to SC212 (nearest working cell in Active
Set) is 2078m, and the azimuth of SC212 is reverse to call drop area. There
is a much nearer cell SC190, but it seems not to work.
4. Solution
• Check the site in red box, and

turn it on
• Adjust RF parameters of cells

nearby
OUTLINE 97

KPI Analysis: CS RAB setup SR
Possible reasons for RAB Setup failures:

(1) poor coverage; (2) no enough resource
KPI Analysis: CS Drop Calls
Typical reasons for drop calls:
(1) poor coverage (e.g. SRB/TRB reset);
(2) Strong UL/DL interference
(3) Insufficient handover area
KPI Analysis: Inter-RAT HO SR
e.g. BSIC wrong

configured
in 3G network
Data discrepancies between 3G network and 2G
network have direct impact on inter-RAT HO SR.
Iub Congestion Counter Analysis
From RNC performance data, we find

that RRC and RAB Success Rate
is low, the main cause is IUB
congestion.
Table 1 the RRC Result of NodeB43304 and NodeB43305
Table 2 the RAB Result of NodeB43304 and NodeB43305
Sample Case for Inter RAT HO
IRAT HO Preparations Performance can

be observed from counter
“VS.IRATHO.SuccRelocPrepOutCS.Cell.R
ate”, “IRATHO.SuccRelocPrepOutCS” &
“IRATHO.AttRelocPrepOutCS”
Cause/Analysis
• 1. Non Suitable GSM Cell is defined.

• 2. Wrong GSM parameter is set.
• 3. MSC have not configured the corresponding neighbor GSM
Cells (GSM LAC, GSM CELL ID) and vice versa.
• 4. 3G Core LAC Neighbors configuration are wrong
• 5. 3G Core circuit pool setting did not match 2G BSC
Cause/Analysis
Handling Problem
• 1. GSM Neighbor Relationship: Check whether correct GSM Cell
neighbor relationshop is defined correctly where 3G and 2G sites
location should be at the same area. Since it is swap project, pre-
swap dump is the source of reference to define the GSM cell. Check
from Map info and pre-swap dump for the verification.
• 2. GSM information: Cross check every single possible parameter
that might make mistake in command ADD GSMCELL, ADD
GSMNCELL
• 3. Switches Setting: Check Switches Setting in RNC by using
command LST CORRMALGOSWITCH. There are 6 subclusters in this
RNC, only 1 out of 6 Subcluster faced InterRAT Preparation 100%
failure problem. Thus, RNC Level Switches setting should not be the
root cause of the problem.
Handling Problem
• In this case, the root cause is due to MSC that connect to GSM
BSS have not define new swapped Huawei RNC and cell on
time. Thus, the Relocation Preparation failure due to no reply
from MSC that connects to GSM BSS equipment.
OUTLINE 107

Analysis by Tracing
Analysis:
1. The Interactive Service Class was requested by User on 04:31:03
2. The SIM Card profile is 8.64 Mbps for DL and 4.032 Mbps for UL.
3. The PDP Context Accepted 04:31:04
Analysis by Tracing
Sample Case Analysis by Tracing (Inter RAT Relocation Preparation Failure )
Trace the signaling from LMT, found out that

RANAP_Relocation_Preparation Failure msg
due to ‘Unspecified failure’. This message is
sent out from CoreNetwork(CN). the root
cause is due to MSC that connect to GSM
BSS have not define new swapped Huawei
RNC and cell on time. Thus, the Relocation
Preparation failure due to no reply from MSC
that connects to GSM BSS equipment.
Sample Case Analysis by Tracing ( RRC Connection Drop )
Sample Case Analysis by Tracing ( Inter RNC HO )
Sample Case Analysis by Tracing ( Inter RNC HO )
Sample Case Analysis by Tracing ( Low Throughput)
Sample Case Analysis CS Inter RAT HO Attempt 0%
Case Description Sample Ca

Case
as Analysis CS Inter RAT HO attempt 0%
Below is Huawei RNC600 at Country I on the IRATHO attempt statistics from 1st
September 2008 to 23rd September 2008.
IRAT HO Success Rate (%)
100.00%
90.00%
80.00%
70.00%
60.00%
50.00% IRAT HO Success Rate (%)
40.00%
30.00%
20.00%
10.00%
0.00%
200 8 00 8 00 8 00 8 00 8 0 08 0 08 0 08 0 08 0 08 0 08 0 08
2 2 2 2 2 2 2 2 2 2 2
9/ 1/ /3/ /5/ /7/ /9/ 11/ 13/ 15/ 17/ 19/ 21/ 23/
9 9 9 9 9/ 9/ 9/ 9/ 9/ 9/ 9/
From the DT analysis, it shows that the compressed mode where Event 2D has triggered as shown in L3
signaling message in Figure 1 and Figure 2 when it reaches RSCP threshold which is -95dBm.
After UE has sent the MEASUREMENT REPORT to start compressed mode to the RNC600, a
MEASUREMENT CONTROL message is received from the RNC600 to report to UE the details of
INTERRAT neighbours as shown in Figure 3.
Figure 2: DT Analysis L3 Signaling Figure 3: Measurement Report showing Compressed

Company Confidential Mode has triggered.
m Page 116
From the DT analysis, it shows the 3G and 2G neighbours are configured and we have performed
the consistent check on the data GSMCELL in the RNC600 with the latest 2G data such as
BCCHARFCN, Location Area Code (LAC), GSMCELLID, NCC and BCC; and the result shows that
all necessary data as stated are matched.
After UE has sent the MEASUREMENT REPORT message (to start the compressed mode) to RNC
and received MEASUREMENT CONTROL message (to report the GSM neighbours) from RNC, the
RNC will start to send RELOCATION REQUIRED message to Core Network as shown in Figure 5.
Figure 5: Signaling Message from RNC to CN

Figure 4: RRC MEASUREMENT CONTROL
message showing
Figure details
the 2: DT Analysis neighbours
of GSM L3 Signaling Figure 3: Measurement Report showing Compressed
C f for 3G serving cell Mode has triggered.
m Page 117
%
To further investigate the root cause of this no INTERRAT handover attempt, RNC performance data on
22/9/2008 1130~1230 is extracted and analyzed using Huawei Genex Nastar WCDMA network analyzing
tools and it shows that there is RELOCATION REQUIRED message sent from RNC600 to the CN with the
counter VS.SRELOC.AttPrep.IRHOCS; showing 2753 times of RELOCATION REQUIRED messages sent
to CN as shown in Figure 6. However, the RNC600 received 2752 times of RELOCATION PREPARATION
FAILURE from the CN with the counter VS.SRELOC.FailPrep.IRATCSOut.
51&,G 51&1DPH 7LPH$VGD\ 9665(/2&)DLO3UHS,5$7&62XW 9665(/2&$WW3UHS,5+2&6
51&

Figure 6: Statistics on the RELOCATION REQUIRED and RELOCATION PREPARATION FAILURE
%
The CN signaling collection was performed on 2008-10-17 from 16:00 to 17:00.
The root cause from RNC tracing is that Semantic error which indicates that the 2G cell information,
such as CGI, BCCH, LAC, and etc may be incorrectly set in MSC.
The MSS team has checked the

MSC (MSC1) connected to 2G BSC
and MGW (MSC2) which connected
to the 3G RNC. They have found
out that there is no 2G and 3G
neighbour relationship is defined in
MSC1 and MSC2 since the 2G BSC
cutover to MSC1.
Figure 8: Relocation Preparation failure cause: Semantic error
Summary
To provide better quality of To provide a more competitive

experience for Subscribers network for Operator
UMTS Network
Optimization
Trade-off between optimized Ongoing optimization across

coverage, capacity, quality network life cycle

GCI Huawei 3G Network Optimization

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

GCI Huawei 3G Network Optimization

Transféré par

Droits d'auteur :

Formats disponibles

Nubee Training Center (NTC)

3G Network Field Optimization & Tools

PT. Nubee System

Huawei RNC & Node B Short Introduction

Huawei Optimization Tools

Huawei 3G KPI & Reports

Huawei RNC & Node B counters

WMPT WCDMA Main Processing and Transmission Unit

Power RSR: 4,650W

Front View Rear View

• 12 U shielding subrack of Huawei

Front View Rear View

• It supports up to 51,000 equivalent voice

Weight under full configuration ≤ 160Kg

- 48VDC + 24VDC 220V AC

• DBS3900 is a distributed NodeB of forth

Trunk cable Fiber or CPRI high-speed

Specification of the DBS3900

Characteristics of the DBS3900

l Supports RRU cascading

[ When using the 1.25 G optical module, cascading levels ≤ 4

Characteristics of the DBS3900

l Supports ATM ǃIP and ATM/IP Dual stack networking;

• System capacity specifications:

[ Transmission Type: E1/T1, FE (electrical port ), FE (optical port ),

Huawei RNC & Node B Short Introduction

Huawei Optimization Tools

Huawei 3G KPI & Reports

Huawei RNC & Node B counters

RAN auto Node B

v GENEX Probe HLR/AC

Huawei RNC & Node B Short Introduction

Huawei Optimization Tools

Huawei 3G KPI & Reports

Huawei RNC & Node B counters

Some cells in the border

Missing LAC neighbor

Urban area. Traffic

ISHO CS End2End degraded

Huawei RNC & Node B Short Introduction

Huawei Optimization Tools

Huawei 3G KPI & Reports

Huawei RNC & Node B counters

Sample Optimization Cases & How to Analyze

PT. Nubee System

Analyze by Drive Test Result

Analyze by KPI or Counters

Analyze by Signaling Tracing

Pilot Pollutions Area

After adjustment, pilot pollution here reduced above

The characteristic of weak coverage is: weak RSCP

1. Check the Ec/Io and RSCP around this call drop

We will find that receive signals in red box are very

So we need to observe Ec/Io and RSCP on chart in

2. Observe RSCP and Ec/Io

On the charts, we will find that

UE has send “Measurement

Finally, call drop occurred.

• Check the site in red box, and

• Adjust RF parameters of cells

Analyze by Drive Test Result

Analyze by KPI or Counters

Analyze by Signaling Tracing

Possible reasons for RAB Setup failures:

51&,G 51&1DPH 7LPH$VGD\ 9665(/2&)DLO3UHS,5$7&62XW 9665(/2&$WW3UHS,5+2&6

51&