Huawei 2G/3G Network Optimization: Sharing Session Bandung, January 21-23, 2015

Security Level:
Huawei 2G/3G Network Optimization

sharing session
Bandung , January 21-23, 2015
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.

Prepared by : Edward Sulung E00751213
Contents
1 3G WCDMA
2G/3G Introduction
Network Structure and Principle
2 3G WCDMA
2G/3G Introduction
Radio Network Optimization Tools
3 2G/3G Huawei Parameters
4 2G/3G Optimization Cases
5 2G/3G Hedex Documentation
PT. HUAWEI SERVICES Huawei Confidential Page 2

2G/3G Network Structure and Principle Advantage
Increasing number of
customer and
Sites triggered optimization
action
To keep the performance
stable and better customer
satisfaction

2G/3G Network Structure and Principle methodology
Data Input and Find
Problems
Verify Parameter Problems

N
Classify Parameter Problems Other Process
Determine Parameter Values to be

Modified and List MML Commands
Evaluate Changing Effects
N
Determine whether Changing N
Y
End
Prepare Test Plan and Implement
Changing
Test , Get Data again and Compare
Problems Eliminate Or Need not Change more
Proper optimization procedure becomes

End
number 1st rule to
Investigate RF issues
Availability
Routine and New
Inconsistency
Site
Check on the Physical
network Update in
Tuning,
Fast Customer the network
redirection
Complain
antenna Low
Handling
Traffic to
congested
area
Out of The Box
Optimization
Sales Team
Process
Cooperation
Temporary
related to
antenna
customer redirection
complain on neighbor
Replaced stollen
(Signal Loc
ICM Band Proposed
Information) New Overlay feeder issue
GSM900 to upgrade fo
DCS1800 on congested
3Band cell only
Antenna

Routine Daily Alarm

Inconsistency &
Check on the Performance
network Monitoring
Event
Preparation for Global
Recommendati parameter
on and Action standarization
Proactive
Optimization
Communicate
Process
to Planning Defining
team related to Strategic
upgrade Optimization
plan/activity in
the network
Communica Engineering
te to FOP Antenna Engineering
Antenna
related to Physical
configuration Physical
HW & configuration
Transmissio Update
Update
n Issue

2G/3G Network Structure and Principle 2G to 3G evolution
3G
2Mbps
2.5G 384kbps IMT-2000
115 kbps EDGE

2G 57.6 kbps GPRS
9.6 kbps HSCSD
GSM

Page 7
2G/3G Network Structure and Principle Global System
2G Global Network Structure
MSC
BSS
TC/SM GPRS Backbone
BSC PCU SGSN
BTS
Page 8
2G/3G Network Structure and Principle Global System
3G Global Network Structure
MGW
BSS
GPRS Backbone
RNC RNC SGSN
NodeB NodeB
Page 9
Frequency Time Spread Code

Division Division Spectrum Division
Multiple Multiple Multiple Multiple
Access Access Access Access
Multiple
Transmitters
and
Multiple Data
User N
User 2
User 3
User 1
User 2
User 3
User 1
Channels
Frequency Time Frequency

Each User has a unique Each Transmitter has a unique
Each User has a unique
frequency spreading code
time slot
(1 voice channel per user) Each Data Channel has a unique

Each Data Channel has a unique
orthogonal code
position within the time slot
All users transmit at the Many users share the same

Several users share the
same time frequency and time
same frequency
IS-95, cdma2000, WCDMA
IS-136, GSM, PDC
AMPS, NMT, TACS

Page 10

Page 11
Frequency Frequency Point

Range (MHz) Uplink Frequency Downlink Frequency
Spectrum Available
450.4~457.6
GSM 450 Fu(n)=450.6+0.2(n-259) 259<=n<=293 Fd(n)=Fu(n)+10
460.4~467.6
478.8~486
GSM 480 Fu(n)=479+0.2(n-306) 306<=n<=340 Fd(n)=Fu(n)+10
488.8~496
824~849
GSM 850 Fu(n)=824.2+0.2(n-128) 128<=n<=251 Fd(n)=Fu(n)+45
869~894
Fu(n)=890+0.2n 0<=n<=124
E-GSM 900 880~915 925~960 Fd(n)=Fu(n)+45
Fu(n)=890+0.2(n-1024) 975<=n<=1023
876~915 Fu(n)=890+0.2n 0<=n<=124
R-GSM 900 Fd(n)=Fu(n)+45
921~960 Fu(n)=890+0.2(n-1024) 955<=n<=1023
1850~1910
PCS 1900 Fu(n)=1850.2+0.2(n-512) 512<=n<=810 Fd(n)=Fu(n)+80
1930~1990

Page 12
Frequency Frequency Hopping
f0
f1
f2
f3
f4
Frame
Time

Page 13
Physical Channel and Logical Channel
The physical channel is the medium over which the information is carried: 200KHz and
0.577ms
The logical channel consists of the information carried over the physical channels
0 1 2 3 4 5 6 7 0 1 2 3
Timeslot The information carried in one time
slot is called a “burst”
TDMA FRAME TDMA FRAME

Page 14
Uplink Logical channel
CCH
RACH CCCH
SDCCH
SACCH DCCH DCH
FACCH
TCH/F
TCH
TCH/H
Page 15
Downlink Logical channel
FCCH
BCCH SCH
CCH BCCH
PCH
CCCH
AGCH
SDCCH
DCCH SACCH
DCH FACCH
TCH/F
TCH
TCH/H
Page 16
- User information bits are spread over a wide bandwidth by multiplying user information with the quasi-random bits
(called Chips) user data x spreading code
-The rate at which the data spreads is called the chip rate.
-The ratio of the chip rate to the symbol rate is called the spreading Factor (SF).
- Spreading code in mobile phone is as same as that in transmission point as to do the correlation detection (explained
on Rake Receiver for multipath reception)
-Each user is identified by a unique spreading code
-The chip rate of 3.84 Mcps (megachips per second) is used in Spreading and De-Spreading
-The long codes with 25 degree generator polynomials are truncated to the 10 ms frame
length, resulting in 38 400 chips with 3.84 Mcps

Page 17
Consists of 2 operations:
1. Channelization
• Transforms each symbol (data bit) to the number of chips (increases bandwidth)
• Number of chips per symbol = Spreading Factor (SF)
2. Scrambling
• Scrambling code is applied

Page 18
Spreading Codes is also known as Channelization Codes as :

- In Uplink : separate user and control data (one user)
- In Downlink : to separate common and dedicated channels within a cell
(multiple users)
The length of the spreading code varies according to the symbol Rate as seen below :
The OSVF uses length 256 per bit would be represented by 256 chips
The OSVF uses length 4 per bit would be represented by 4 chips. Better using a long OSVF as for adding redundancy to the
transmitted information (seen in spreading gain)

Page 19
1. The signal energy (pertaining, for example,

to a single chip of a CDMA waveform) may
arrive at the receiver across clearly
distinguishable time instants
 the WCDMA receiver can separate those
multipath components and combine
them coherently to obtain multipath diversity
2. Also, for a certain time delay position there
are usually many paths nearly equal in length
along which the radio signal travels
 signal cancellation is necessary

Page 20
Logical Channels
content is organised in separate channels, e.g.
System information, paging, user data, link management
Transport Channels
logical channel information is organised on transport channel
resources before being physically transmitted
Physical Channels Frames

(UARFCN, spreading code) Iub interface

Page 21
MAPPING CHANNEL (DL)
Logical Transport Physical

Channels Channels Channels
P-SCH
S-SCH
CPICH
BCCH BCH P-CCPCH
PCCH PCH S-CCPCH
PICH
CCCH AICH
FACH
CTCH CSICH
DCCH CD/CA-ICH
DSCH PDSCH
DTCH DCH DPDCH
DPCCH

Page 22
MAPPING CHANNEL (UL)
Logical Transport Physical

Channels Channels Channels
CCCH RACH PRACH
DCCH CPCH PCPCH
DTCH DCH DPDCH

DPCCH

Page 23
LOGICAL CHANNEL
There are two types of logical channels (FDD mode):
Control Channels (CCH):
•Broadcast Control Channel (BCCH)
System information is made available on this channel. The system information informs the UE about the serving PLMN, the serving cell, neighbourhood lists,
measurement parameters, etc.
This information permanently broadcasted in the downlink.
•Paging Control Channel (PCCH)
Given the BCCH information the UE can determine, at what times it may be paged. Paging is required, when the RNC has no dedicated connection to the UE.
PCCH is a downlink channel.
•Common Control Channel (CCCH)
Control information is transmitted on this channel. It is in use, when no RRC connection exists between the UE and the network. It is a bi-directional channel,
i.e. it exists both uplink and downlink.
•Dedicated Control Channel (DCCH)
Dedicated resources were allocated to a UE. These resources require radio link management, and the control information is transmitted both uplink and
downlink on DCCHs.
Traffic Channels (TCH):
•Dedicated Traffic Channel (DTCH)
User data has to be transferred between the UE and the network. Therefore dedicated resources can be allocated to the UE for the uplink and downlink user
data transmission.
•Common Traffic Channel (CTCH)
Dedicated user data can be transmitted point-to-multipoint to a group of UEs.

Page 24
TRANSPORT CHANNEL
Logical Channels are mapped onto Transport Channels. There are two types of Transport Channels (FDD mode):
Common Transport Channels:

•Broadcast Channel (BCH)
It carries the BCCH information.
•Paging Channel (PCH)
It is in use to page a UE in the cell, thus it carries the PCCH information. It is also used to notify UEs about cell system information changes.
•Forward Access Channel (FACH)
The FACH is a downlink channel. Control information, but also small amounts of user data can be transmitted on this channel.
•Downlink Shared Channel (DSCH)
This channel is used downlink. Dedicated user data and control information for several mobile phones can be transmitted with one DSCH.
•Random Access Channel (RACH)
This uplink channel is used by the UE, when it wants to transmit small amounts of data, and when the UE has no RRC connection. It is often used to
allocated dedicated signalling resources to the UE to establish a connection or to perform higher layer signalling. It is a contention based channel, i.e.
several UE may attempt to access UTRAN simultaneously.
•Common Packet Channel (CPCH)
Similar to the RACH, it is a contention based uplink channel. In contrast to the RACH, it can be used to transmit larger amounts of (bursty) traffic.
Dedicated Transport Channels:

•Dedicated Channel (DCH)
Dedicated resources can be allocated both uplink and downlink to a UE. Dedicated resources are exclusively in use for the subscriber.
On the following figures. you can see the mapping of logical channels onto transport channels, as well as the mapping of transport channels onto physical
channels.
Page 25
2G/3G RNO tools Nastar
Export the
results.
Displays the RSCP_DL, Display the summary of all

Ec/No_DL, and TP of the counters corresponding to
AMR, VP, BE, AMR+BE, and services involved in all 2-D
Test cells other services in a 2-D chart. charts in a summary table.
Poor ECNO Good

Both are poor. Poor TP
Combination counters of
RSCP_DL, Ec/No_DL,
and TP for CS services
and PS services.
Both are poor. Poor RSCP Poor ECNO Good

Cases of UMTS/GSM Neighboring Cell Analysis
3. Shiqiaoqianfeng D-2 cell is not configured

as a neighboring cell of W Shawanhuiting 3.
According to the GIS, they are a little far
away from each other. Check whether cross
coverage occurs.
2. W Shiqiaodesheng 2, which is near to w

Shawanhuiing 3, is not found during the
1. It is obviously that Shiqiaonanti 1 and 2 are neighboring cell measurement of w
not configured as neighboring cells of w Shawanhuiting. Need checking.
Shawan huiting 3.
1. Neighboring cells are obviously miss-configured.

2. Antennas are blocked or base stations do not work normally.
3. The direction angle of the antenna is improper and the cross
coverage occurs.
Page 27
GSM Neighboring Cell Analysis — Redundant and Missing Neighbors
Export the results
Missing neighbors
Defined Neighbors
Page 28
GSM Frequency Analysis — Result Query (Frequency Optimization) (I)
Frequency separation rule
Export the frequency Interference compare analysis Provide BCCH and TCH
optimization result frequency optimization
results respectively
Frequency usage ratio
Problem Description
The current BCCH (1020) of G541_Donkels Bohey EPT Tower_2 has
strong interference.
Better frequencies for the

test cells.
Page 29
2G/3G RNO tools U2000
Double Clicked on
Performance to view
RNC/BSC or Cell level
STS
Double Clicked on
Topo View to check
alarm RNC/BSC or Site
Level




NodeB MML Command RNC MML Command


Checking NODEB LICENSE

DSP LICENSE;

Checking NODEB CE Board Capacity

DSP BRD;
DSP BBPTC;
CE BOARD TYPE :
HBBI ==> UL/DL = 128/256
EBBI ==> UL/DL = 384/384
WBBPa ==> UL/DL = 128/256
WBBPb1 ==> UL/DL = 64/64
WBBPb2 ==> UL/DL = 128/128
WBBPb3 ==> UL/DL = 256/256
This command only exist in BTS3900 WBBPb4 ==> UL/DL = 384/384

Checking NODEB WRFU Power Max
DSP BRD;
DSP BRDMFRINFO;

Checking NODEB TX Power Max NodeB
LST LOCELL;
LST LOCELL:MODE=LOCALCELL,LOCELL=1;

Checking NODEB CELLS/SECTORS
LST LOCCELL;
DSP LOCCELL;
LST SEC;
In Pico, better not

connect 2 feeders to
RX_a
and RX_b. But not in
Macro sites.

Checking NODEB VSWR board and Alarm Active
DSP VSWR;
DSP ALMAF;

Checking NODEB R99 Algorithm & Congestion Control parameter

LST R99ALGPARA;
LST CONGCTRLPARA;

Checking NODEB E1 IP capacity & status

DSP E1T1
DSP DEVIP

Checking BASIC Configuration of NodeB
LST UNODEB;
This command to see the cellname, sectors, configured E1 in RNC.
Check
PT. the
HUAWEI consistency
SERVICES between nb of E1 in NodeB
Huawei Confidential Page 44
Checking RESELECTION CELL
LST UCELLSELRESEL;

Checking NEIGHBOR RELATION 3G-3G & 3G-2G
LST UINTRAFREQNCELL;  to see 3G adj cell and its adjacency parameters
LST U2GNCELL;  to see 2G adj cell and its adjacency parameters

Checking IRAT2G & SHO parameters

LST UCELLINTERRATHOCOV; cell LST UINTERRATHOCOV;  RNC

Checking IRAT2G & SHO parameters

LST UCELLINTERRATHOCOV; cell LST UINTERRATHOCOV;  RNC

CELL HEALTY CHECK
CELL HEALTHY CHECK of a cell is necessary during real time monitoring
DSP UCELLCHK:CHECKSCOPE=CELLID,CELLID=38219; RTWP measure result[dBm] = -97.9

RNMDN06 Current background noise = 68
+++ RNMDN06 2013-12-06 09:07:16 Latest TxPwr measure result[%] = 42
O&M #1135545 Cell Uu uplink congested state = Not congested
%%/*3025439*/DSP UCELLCHK:CHECKSCOPE=CELLID,CELLID=38219;%% Cell Uu downlink congested state = Not congested
RETCODE = 0 Execution succeeded. DC HSDPA carrier group of cell Uu downlink congested state = Not congested
Cell uplink load[%] = 71
Cell health information Cell downlink load[%] = 40
----------------------- DC HSDPA carrier group of cell downlink load[%] = 0
Cell ID = 38219 Current cell DCH user number = 36
Cell is activated or not = Yes Current cell FACH user number = 0
Cell is unblocked or not = Yes Current cell HSDPA user number = 21
Cell is setup or not = Yes Current cell HSUPA user number = 21
Cell barred indicator in idle mode = Access allowed Count of cell current 64QAM users = 10
Cell barred indicator in connected mode = Access allowed Count of cell current MIMO users = 0
Cell is available or not = Yes Count of cell current EFACH users = 0
cell reported by NodeB is unavailable = No
Cell is blocked by NodeB = No
Exist available RACH flag = Yes
Exist available FACH flag = Yes
Exist available PCH flag = Yes
Exist available NCP flag = Yes
Exist available CCP flag = Yes
RTWP measure state = Normal
TxPwr measure state = Normal

CELL HEALTY CHECK
Cell Credit uplink congested state = NodeB not congested&LCG not congested&LC not
Count of cell current DtxDrx users = 0 congested
Count of cell current HsScchLessOperation users = 0 Cell Credit downlink congested state = NodeB not congested&LCG not
Count of cell current 64QAM+MIMO users = 0 congested&LC not congested
Count of cell current UL16QAM users = 0 Cell fairness state = Fair
Count of cell current Uplink Enhanced L2 users = 0 Cell of MBSC max power[dBm] = 460
Count of cell main carrier in local cell current DC-HSDPA users = 0 Cell of NodeB max power[dBm] = 460
Count of cell current E-DPCCH Boosting users = 0 Whether HSDPA is configured and active = Yes
Count of cell current DC-HSDPA+MIMO users = 0 Whether HSDPA is supported by NodeB = Yes
Count of cell current EPCH users allocated dedicated H-RNTI = 0 Whether HSDPA is setup successfully = Yes
Count of cell current ERACH users = 0 Whether HSUPA is configured and active = Yes
Count of cell current EDRX users = 0 Whether HSUPA is supported by NodeB = Yes
Count of cell main carrier in local cell current DC-HSUPA users = 0 Whether HSUPA is setup successfully = Yes
Current cell uplink equivalent user number[*100] = 7199 Whether function of EFACH is configured and active = No
Current cell downlink equivalent user number[*100] = 5442 EFACH function of local cell = Yes
Downlink Equal User Number of DC Cell Carry Group[*100] = 0 Whether EFACH is setup successfully = No
Current user uplink switch algorithm = Not used Whether function of MIMO is configured and active = No
Current user downlink switch algorithm = ALGORITHM_FIRST MIMO function of local cell = No
Cell code used rate[%, SF256 used] = 85 Whether MIMO is setup successfully = No
Cell code congested state = Not congested 64QAM function of local cell = Yes
Cell credit used rate[%,Max(ulUsed/ulMax, dlUsed/dlMax)] = 7 64QAM function of cell = Yes
Cell Iub uplink congested state = Not congested 64QAM+MIMO function of local cell = No
Cell Iub downlink congested state = Not congested 64QAM+MIMO function of cell = No

CELL HEALTY CHECK
E-DPCCH Boosting function of local cell = No
Downlink Enhanced L2 function of local cell = Yes E-DPCCH Boosting function of cell = No
Downlink Enhanced L2 function of cell = Yes DC-HSDPA+MIMO function of local cell = No
Uplink Enhanced L2 function of local cell = No DC-HSDPA+MIMO function of cell = No
Uplink Enhanced L2 function of cell = No Whether function of EPCH is configured and active = No
DTXDRX function of local cell = Yes EPCH function of local cell = Yes
DTXDRX function of cell = No Whether EPCH is setup successfully = No
HsScchLessOp function of local cell = Yes Whether function of ERACH is configured and active = No
HsScchLessOp function of cell = No ERACH commom EDCH function of cell = No
Uplink 16QAM function of local cell = No ERACH E-AI function of cell = No
Uplink 16QAM function of cell = No ERACH commom EDCH HSDPCCH function of cell = HS-DPCCH non-Capable
DC-HSDPA function of local cell = No Whether ERACH is setup successfully = No
DC-HSDPA function of cell = No EDrx function of local cell = Yes
Local Cell ID of DC Assisted Cell = <NULL> EDrx function of cell = No
DC-HSUPA function of local cell = No Cell DSP No. = 20
DC-HSUPA function of cell = No Cell DSP subrack No. = 2
Cell DSP slot No. = 11
Cell CLB state = Not CLB
(Number of results = 1)
--- END

Counter Categories
 Counter
 Performance measurement counter is a basic unit for the performance measurement. It defines
what to measure.
 Counter categories
 system counters, defined by NEs, include:
 default counters
 extended counters.
 user-defined counters, are defined on the M2000 client.
Page52
Counter Categories (Cont.)
 Default Counter,Extended Counter and User-Defined Counter
Page53
Adding a User-Defined Counter
 According to the existing measurement counters, to define a user-required

measurement counter by using the arithmetic.
Page54
Adding a User-Defined Counter (Cont.)
Page55
Adding a User-Defined Counter (Cont.)
Page56
Selection of the Object and Period
Page57
Selection of the Object and Period (Cont.)
Period
Counter
Object

Set Measurement Counters
 After the object and period are appointed, counters can then be chosen
Counters

Measurement States Management

Measurement States Management (Cont.)

Measurement States Management (Cont.)

Querying by Template

Querying by New Conditions
Page64
Querying by New Conditions (Cont.)
Page65
Managing Result Query Templates
Page66
Displaying Query Results
 Measurement results can be displayed in a table or a line or bar chart.
Page67
Subscribe to Measurement Results
Page68
Synchronizing Measurement Results
 the missing measurement results can be obtained by synchronizing measurement

results.
Page69
Synchronizing Measurement Results (Cont.)
Page70
Querying Missing Results
 You can also directly synchronize the queried missing data in the “Measurement
Status” window.
Page71
Querying Missing Results (Cont.)
Page72
Monitoring the Integrity of Current Results
Page73
Monitoring the Integrity of Current Results (Cont.)
 Monitoring output
Page74
Querying the Integrity of Historical Results
Page75
Querying the Integrity of Historical Results (Cont.)
 Querying output
Page76
Simple Counter Threshold
Page77
Simple Counter Threshold (Cont.)
Page78
Page79
Page80
Combined Counter Threshold
Page81
Activate/Deactivate Counter Threshold
Page82
2G/3G Huawei Parameters basic
For UL Power Congestion :
1st Solution Step:
1. Check MAXTXPOWER per Cell in LST UCELL
2. Upgrade from 430 to 460 (RNC and NodeB must be set the same)
2nd Solution Step:

1. Check LST UCELLCAC
2. Check UL total equivalent user number (ULTOTALEQUSERNUM)  max setting is 200
3. If it’s still default, then upgrade it to 150 or 200
4. Then Check LST UCELLALGOSWITCH
5. Set NBMUlCacAlgoSelSwitch (Uplink CAC algorithm switch ) = ALGORITHM_SECOND
6. Set NBMDlCacAlgoSelSwitch (Downlink CAC algorithm switch) = ALGORITHM_FIRST
3rd Solution Step:

1. Check LST UCELLALGOSWITCH
2. In NBMLdcAlgoSwitch, Set UL_UU_LDR (Uplink UU LDR Algorithm: )=1 (ON)
3. Then check UCELLLDR,
4. Set UlLdrFirstAction (UL LDR first action) = BERateRed(BE traff rate reduction), UlLdrBERateReductionRabNum=1,
GoldUserLoadControlSwitch=ON

For DL Power Congestion :
1st Solution Step:

1. Check LST UCELLCAC
2. Check DL total equivalent user number (ULTOTALEQUSERNUM)  max setting is 200
3. If it’s still default, then upgrade it to 150 or 200
4. Check DL total power threshold (default is 90%), Set to 95%
5. Then Check LST UCELLALGOSWITCH
6. Set NBMDlCacAlgoSelSwitch (Downlink CAC algorithm switch ) = ALGORITHM_SECOND
2nd Solution Step:

1. Check LST UCELLALGOSWITCH
2. Set DL_UU_LDR (Downlink UU LDR Algorithm: )=1 (ON)
3. Then check UCELLLDR,
4. Set DlLdrFirstAction (DL LDR first action) = BERateRed(BE traff rate reduction), DlLdrBERateReductionRabNum=1,
GoldUserLoadControlSwitch=ON
To see the effect of LDR

VS.LCC.LDR.InterFreq
VS.LCC.LDR.BERateDL
VS.LCC.LDR.BERateUL
To create FTI :
Iub congestion :
1. Add E1/IP migration 1. Add TRMFACTOR (to set the reduced PS in Iub)
2. FTI solution temporary 2. Check ADJNODE (Check ANI of the nodeB)
3. Set ADJMAP for FTI
ADD TRMFACTOR: FTI=4, REMARK="IUB_SULUNG_OPTIM";

MOD TRMFACTOR: FTI=4, PSSTRMDL=10, PSSTRMUL=10, PSINTERDL=10, PSINTERUL=10, PSBKGDL=10, PSBKGUL=10,
HDSTRMDL=10, HDINTERDL=10, HDBKGDL=10, HUSTRMUL=10, HUINTERUL=10, HUBKGUL=10;
MOD ADJMAP: ANI=100, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=50, TMISLV=50, TMIBRZ=50, FTI=4;

Increase maximum number of HSDPA in a cells
MOD UCELLCAC: CellId=16148, MaxHsDpaUserNum=96;

Activate code LDR Algorithm and set the LDR on 1st action with Code Adjust
MOD UNODEBALGOPARA: IDTYPE=BYNAME, NodeBName="X3253388G_3G_BAWAN_AGAM",

NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;

3G Neighbors Updating
ADD UEXT2GCELL: GSMCellIndex=45315, GSMCellName="PB13533", NBscIndex=0, LdPrdRprtSwitch=OFF, MCC="510", MNC="11", CnOpGrpIndex=0, LAC=22372,
CfgRacInd=NOT_REQUIRE, CID=13533, NCC=3, BCC=1, BcchArfcn=682, RatCellType=GPRS, UseOfHcs=NOT_USED;
RMV UEXT2GCELL: GSMCellIndex=1;
MOD UEXT2GCELL: GSMCellIndex=18409, BcchArfcn=114;
MOD UEXT2GCELL: GSMCellIndex=18409, LAC=114;
ADD U2GNCELL: RNCId=812, CellId=43352, GSMCellIndex=43464, BlindHoFlag=FALSE, NPrioFlag=FALSE;
RMV U2GNCELL: RNCId=812, CellId=43352, GSMCellIndex=43464;
ADD UEXT3GCELL: NRncId=812, CellId=43076, CellHostType=SINGLE_HOST, CellName="PB3G2_43076", CnOpGrpIndex=0, PScrambCode=76, BandInd=Band1,
UARFCNUplinkInd=TRUE, UARFCNUplink=9838, UARFCNDownlink=10788, TxDiversityInd=FALSE, LAC=32331, CfgRacInd=REQUIRE, RAC=214, QqualminInd=TRUE, Qqualmin=-18,
QrxlevminInd=TRUE, Qrxlevmin=-58, QrxlevminExtSup=FALSE, MaxAllowedUlTxPowerInd=FALSE, UseOfHcs=NOT_USED, CellCapContainerFdd=DELAY_ACTIVATION_SUPPORT-
0&HSDSCH_SUPPORT-0&FDPCH_SUPPORT-0&EDCH_SUPPORT-0&EDCH_2MS_TTI_SUPPORT-0&EDCH_2SF2_AND_2SF4_SUPPORT-0&EDCH_2SF2_SUPPORT-0&EDCH_2SF4_SUPPORT-
0&EDCH_SF4_SUPPORT-0&EDCH_SF8_SUPPORT-0&EDCH_HARQ_IR_COMBIN_SUPPORT-0&EDCH_HARQ_CHASE_COMBIN_SUPPORT-0&CPC_DTX_DRX_SUPPORT-
0&CPC_HS_SCCH_LESS_OPER_SUPPORT-0&HSPAPLUS_MIMO_SUPPORT-0&FLEX_MACD_PDU_SIZE_SUPPORT-0&FDPCH_SLOT_FORMAT_SUPPORT-
0&HSPAPLUS_DL_64QAM_SUPPORT-0, EFachSupInd=FALSE;
RMV UEXT3GCELL: NRncId=812, CellId=12345;
ADD UINTRAFREQNCELL: RNCId=810, CellId=16043, NCellRncId=812, NCellId=44802;
RMV UINTRAFREQNCELL: RNCId=810, CellId=16043, NCellRncId=812, NCellId=44802;

2G Neighbors Updating
ADD GEXT2GCELL: EXT2GCELLID=2399, EXT2GCELLNAME="PB2G14284", MCC="510", MNC="11", LAC=22321, CI=14284,

BCCH=109, NCC=1, BCC=6, COMSC=NO, LAYER=3, PRIOR=PRIOR-1;
RMV GEXT2GCELL: IDTYPE=BYID, EXT2GCELLID=1;
MOD GEXT2GCELL: IDTYPE=BYID, EXT2GCELLID=2071, NCC=3, BCC=4;
MOD GEXT2GCELL: IDTYPE=BYID, EXT2GCELLID=2071, LAC=22321;
MOD GEXT2GCELL: IDTYPE=BYID, EXT2GCELLID=2071, LAYER=22321;
MOD GEXT2GCELL: IDTYPE=BYID, EXT2GCELLID=2071, BcchArfcn=22321;
ADD G2GNCELL: IDTYPE=BYNAME, SRC2GNCELLNAME="4372_PadangBulan-6", NBR2GNCELLNAME="PB14201";
RMV G2GNCELL: IDTYPE=BYNAME, SRC2GNCELLNAME="4372_PadangBulan-6", NBR2GNCELLNAME="PB14201";
ADD GEXT3GCELL: EXT3GCELLID=5322, EXT3GCELLNAME="PB3G2_44424", MCC="510", MNC="11", LAC=32325, CI=44424,
RNCID=811, DF=10788, SCRAMBLE=4, DIVERSITY=NO, UTRANCELLTYPE=FDD;
RMV GEXT3GCELL: IDTYPE=BYID, EXT3GCELLID=1;
MOD GEXT3GCELL: IDTYPE=BYID, EXT3GCELLID=2071, LAC=22321;
MOD GEXT3GCELL: IDTYPE=BYID, EXT3GCELLID=1, SCRAMBLE=1;
MOD GEXT3GCELL: IDTYPE=BYID, EXT3GCELLID=1, CELLLAYER=1;
ADD G3GNCELL: IDTYPE=BYNAME, SRC3GNCELLNAME="4442L1_BaganSiapiApi2-4", NBR3GNCELLNAME="PB3G2_44424";
RMV G3GNCELL: IDTYPE=BYNAME, SRC3GNCELLNAME="4442L1_BaganSiapiApi2-4", NBR3GNCELLNAME="PB3G2_44424";

2G/3G Optimization Cases Congestion
2G 3G Case in XL network Riau and SUmbar
no case name system point category area status

1 bad SQI on all cell in a RNC 3G transmission system quality problem Riau cleared
2 bad SQI on all BSC A over IP 2G routers quality problem Sumatera Barat cleared
3 cell down flicker 3G transmission system availability problem Riau mostly cleared
4 excessive relation 2G 3G neigbors updating mobillity problem Riau and Sumatra Barat cleared
5 external interference 2G frequency plan quality problem Riau cleared
6 internal interference on tch freq hopping 2G frequency plan quality problem Riau cleared
7 lack relation 2G 3G neigbors updating mobillity problem Riau and Sumatra Barat cleared
8 MPU XPU unbalance 3G RNC Processor system quality problem Riau cleared
9 cross feeder 2G 3G RBS antenna system missmatch configuration Riau and Sumatra Barat monitoring
10 overshooting 2G 3G RBS antenna system missmatch configuration Riau and Sumatra Barat monitoring
11 wrong azimuth 2G 3G RBS antenna system missmatch configuration Riau and Sumatra Barat monitoring
12 E1 T1 excessive bite error rate 2G transmission system Access problem Riau and Sumatra Barat not cleared
13 high dropped cal due to Abis Failures 2G transmission system Retainability problem Riau mostly not cleared
14 high dropped cal due to Equipment Failures 2G RBS equipment system Retainability problem Riau mostly not cleared
15 low cell availability rate 2G 3G RBS power system availability problem Riau mostly not cleared
16 low speed internet 3G transmission system Access problem Riau mostly not cleared
17 low traffic OL2<< OL1 semirigid 2G RBS antenna system Access problem Riau and Sumatra Barat not cleared
18 rabfailediub.cong 3G transmission system Access problem Riau mostly not cleared
19 sctp link congestion alarm 3G transmission system Access problem Riau and Sumatra Barat not cleared
20 transport rx level degrade 3G transmission system Access problem Riau mostly not cleared

2G/3G Optimization Cases 3G PAGING/SPLIT LAC
RTWP MEASUREMENT
Case : LOCALIZED RTWP ISSUE
Suspected
interference
location
Logically, if the suffered cells are localized in a

specific cluster, the cause is due to external
interference.
If only 1 cell, there should be internal interference

2G/3G Optimization Cases 3G PAGING/SPLIT LAC
-Identify RANAP Paging issues/Utran paging

issues
-Issue paging is also related to paging discard
issue which is experienced by nodeB/cells
(VS.RRC.FC.Disc.Num)
-Temporary solution before adding Paging from
Paging from
CPU/SPU/MPU balancing is by increasing RNC/UTRAN
SMPAGECTHD value under SET FCCPUTHD CN to RNC
to Cells
•Paging Congestion = VS.RRC.Paging1.Loss.PCHCong.Cell/ VS.UTRAN.AttPaging1

2G/3G Optimization Cases CS Drop suddenly
PS Traffic increased 400% in Pekanbaru in 4 month that triggered bad KPI performance 3G include low cell
availability ,bad SQI ( -10), degraded speech drop rate, low speech access rate significantly because there
congested in iub interface. For Temporary solution, Optim trial to tuned FTI capability for redefined
bandwidth each services especially interactivePS as mention . KPI performance back to normal after
execution and speed rate maintained in user experience.

2G/3G OPTIMIZATION CASES idle reselection
2G-3G AGRESIVITY
Below is the sample of calculation reselection between 2G & 3G :
NE Name 2G CELL CI 2G 3G CELLNAME 3G Qqualmin SsearchRAT QsearchI FDDQmin (GUI) FDDQoffset Qqualmin + SSearchRat FDDQmin Value FDDQmin > Qqualmin + SSearchRat ?
BMDN24 2222500_PasarVMartubung-1 25001 MD3G25003 3222500G_3G_PASAR_V_MARTUBUNG-3 -16 0 7 2 0 -16 -18 NOT OK/PING PONG
BMDN24 2222500_PasarVMartubung-1 25001 MD3G25002 3222500G_3G_PASAR_V_MARTUBUNG-2 -20 0 7 2 0 -20 -18 OK
BMDN24 2222503_PelabuhanBelawanTengah-1 25031 MD3G25031 3222503G_3G_PELABUHAN_BELAWAN_TENGAH-1 -20 0 7 0 0 -20 -20 NOT OK/PING PONG
BMDN24 2222503_PelabuhanBelawanTengah-2 25032 MD3G25032 3222503G_3G_PELABUHAN_BELAWAN_TENGAH-2 -20 1 7 7 0 -18 -12 OK
BMDN20 3058_GrahaXLMedan[HUT]-1 30581 MD3G57214 E721G_3G_GRAHA_XL_MEDAN-4 -16 0 7 5 0 -16 -10 OK

2G/3G Optimization Cases Bad SQI bad and MPU XPU Load
Check UCELLSETUP :

2G/3G Optimization Cases Bad SQI and Path Fault
User covered under BSC BPRM1 Padang always have bad quality SQI in busy hours ( SQI > 0). Optim found by DT and fund alarm Path Fault that related to BSC – MSC
interconnection. After rectified router setting, SQI problem cleared.

2G/3G Optimization Cases Uplink Congestion case
Below is a case, whenever UlTotalEqUserNum is increased or its algoswitch is OFF

 UL power is restricted by UlTotalEqUserNum (total equivalent user numbers corresponding to the
100% uplink load) under UCELLCAC, with NBMUlCacAlgoSelSwitch – ALGORITHM_SECOND
 Increase the UlTotalEqUserNum to reduce UL Power congestion
 Change the NBMUlCacAlgoSelSwitch to ALGORITHM_OFF (no restriction towards UE to access)
 Note : those action means that cell will allow more user to access, which impact to UL Interference
(User interference). The more user can access a cell, the higher UL interference will be
Seems that RTWP increased since action was conducted.

2G/3G Optimization Cases EDGE Reconfiguration
SET BTSIDLETS: IDTYPE=BYID, BTSID=216, CGN=0, TSCOUNT=12;

RRC and RAB must be impacted by REJECTION due to Congestion that related to :
1. CE Capacity
2. Code Capacity
3. Power Capacity
4. Iub Capacity
5. RTWP level
XL Marketing Pekanbaru as costumer request Optim that possibility to optimum speed EDGE. Optim done Audit 2E1 and defined idletimeslot as much better to improved
speed downlink throughput from 40 kbps to 70 kbps for 96 Sites in Pekanbaru city

2G/3G Optimization Cases HSUPA Capacity
Costumer complaint Padang informed that they got slow internet uploading 3G. Optim increased maxuserhsupa from 20 to 40 user and user
happy get hsupa speed and traffic increase to 30 users. We implemeted to whole area .

2G/3G OPTIMIZATION CASES costumer complaint
Below are samples of common customer complain and steps to analyze :
1. 2G too dominant than 3G signal although there is 3G cell candidate active in the spot
2. Ping pong reselection between 2G-3G
3. 3G signal cell serving too early to move to 2G system
4. Can’t make a call voice/data
5. Low coverage 3G
6. Slow Throughput

2G too dominant than 3G signal although there is 3G cell candidate active in the spot &
Ping pong reselection between 2G-3G
Complain Issue
1. MAP View Spot Location

2. Healthy Check Alarm
3. Check Adjacency between 2G & 3G of
possible cell serving Page 62, 121-123
4. Check parameter reselection 2G-3G
5. Check capacity & availability of possible cell
serving
Optimization Action related to neighboring

No
All normal and
Load capacity improvement
Yes
Drive test in the spot location & Site Audit

3G signal cell serving too early to move to 2G system
Complain Issue

3. Check Adjacency between 3G & 2G of
possible cell serving
4. Check parameter adjacency 3G-2G Page 48, 49, 121-123
(CIOOffset,Qoffset1sn,Qoffset2sn)
5. Check IratHO Parameter in 3G (2D-2F,
TARGETRATTHD)
Optimization Action related to neighboring

No
All normal and
Load capacity improvement
Yes

Can’t make a call voice/data
Complain Issue

3. Check RR-RAB rejection due to capacity
(Power, CE, Iub, Code) & Check RTWP
4. If "very high RRC.NoReply" occur (even TP Page 62, 108 – 110, 132 - 135
is normal), RESET WRFU
5. If NoReply still high, Swap/Replace WRFU
6. Check TP related to complain location, if
7. Customer in far TP distribution, increase
power or RLpower
Optimization Action
No
All normal related to Load capacity
improvement
Yes

Low coverage 3G
Complain Issue

3. Check TP related to complain location
4. Check power setting
5. Check customer surrounding area (blocking,
obstacle)
Optimization Action, Propose physical

No
All normal tuning
Yes
Drive test in the spot location & Site
Audit/Propose New Site

Slow Throughput
Complain Issue

3. Check RR-RAB rejection due to capacity
(Power, CE, Iub, Code) & Utilization
4. Check HSDPA User Number
5. Check Code Allocation
6. Check Iub Transport Type
7. Throughput Optimization Action

2G/3G Optimization Cases Accessability

ACCESSIBILITY
RRC SETUP FAIL

ACCESSIBILITY
RRC SETUP FAIL
Measurement points Description
C VS.RRC.Rej.Redir.Service
VS.RRC.Rej.Redir.InterRat,VS.RRC.Rej.Redir.IntraRat,VS.RRC.Rej.ULCE
E .Cong,VS.RRC.Rej.DLCE.Cong
G VS.RRC.Rej.RL.Fail,VS.RRC.Rej.DLCE.Cong,VS.RRC.Rej.ULCE.Cong
H VS.RRC.Rej.TNL.Fail
K VS.RRC.FailConnEstab.NoReply
L VS.RRC.Rej.Sum,VS.RRC.FailConnEstab.Cong
VS.RRC.FC.Disc.Num
Number of Discarded RRC Connection Requests Due to Various Flow Control Functions for Cell
Time/Number of Cell Update Requests Discarded Due to Flow

Control for CPUS Subsystem
Time/Number of Paging Discarded Due to Flow Control for CPUS

Subsystem Check MPU/XPU Load
Number of Discarded RRC Connection Requests Due to MPU

Overload/CPU High load for CPUS Subsystem

ACCESSIBILITY
VS.RRC.RL.Fail
Number of RRC Connection Rejects Due to Radio Link Setup Failure for Cell
There are some conditions to analize this issue :

1. Check if it happens suddently  Reset the NodeB/WRFU
2. If the number is very high and other parameters can’t solve it  Swap/Replace WRFU, probably HW faulty
without alarm triggered
3. If no HW faulty, check the SHO Overhead (TP), CE Board capability  Related to NBAP signalling capacity

ACCESSIBILITY
NBAP Signalling
NBAP capacity is provided in CE board
Counters are resided under Iub
Measurement
How to calculate this load?
Why Iub?
Because Iub is the transport channel where may signaling is passing through

ACCESSIBILITY
IUB CAPACITY
Iub capacity is critical for accessibility and throughput of cell serving. In order to utilize Iub capacity properly,
a setting in Iub is necssary.
Below are parameters to identify Iub and it’s connection of each nodeB
1. TRMFACTOR
 contains information about Iub service indicator value
2. ADJNODE
 shows node mapping of nodeB in relation with Iub
3. ADJMAP
 contains Iub connection type of a nodeB (FTI=Format Table Index)
Setting value of each service means user will utilize the Iub service as high as the percentage of the value.
Note : Either configuration of ATM or IP can be seen through MITBrowser

ACCESSIBILITY
IUB CAPACITY
Iub TYPE – ATM (Crosschek Nb of E1 under RNC)
LST UNODEB:LSTTYPE=ByNodeBName,NODEBNAME="3214223G_3G_KUALASIMPANG";
After execute :
RNBRU01 DSP E1T1:SRN=1,SN=17,BT=AOUc,PN=213;
E1/T1 port state

List NodeB ----------------
---------- Port No. = 213
Port running state = Port available
Subrack No. = 1 State Changed Time = 2013-11-30 22:46:46
Subrack name = EPS_Subrack_1 State Changed Cause = Ingress Tributary Unit Alarm Indication Signal cleared
Executing port test or not = No
Slot No. = 17 Port type = E1
IMA group No. = 132 Transmitting frame format = E1 CRC4 multi frame
Expected receiving frame format = E1 CRC4 multi frame
Board Type = AOUc Loopback type = No loopback
Min Number of Links Activated = 1 Loopback Remaining Time(Minute) = 0
Check SSN & IMALink No Code Violation Count = 0
IMA ID = 49 Framing Error Count = 29840
TX frame length = D128 Number of CRC errors = 54317
Number of E-Bit errors = 6156
Max diff delay[ms] = 200 Number of Sa6 errors = 6932
IMA protocol version = V1.1 Number of multiframe periods received in the asynchronous state = <NULL>
Number of frame or multiframe alignment COFA changes = <NULL>
Flow control switch = ON Property of interfere code = TC Scramble Enabled
Flow control parameter index = 1 Is this E1/T1 occupied = YES
Connected node information NODEB(CELL) and N7DPC = 3214223G_3G_KUALASIMPANG:42231 (
Expected diff delay guard-band[cells] = 10 (Number of results = 1)
TRM load threshold index = 0
Operator Separated Flag = OFF --- END
Operator Separated Index = <NULL>
Block Status = UNBLOCKED
IMA Link No. in IMA Group = 213(17),214(17),215(17),216(17)
Fractional Link No. in IMA Group = NO
Fractional Link Bearing Port No. in IMA Group = NO

ACCESSIBILITY
IUB CAPACITY
Iub TYPE – ATM (Crosschek Nb of E1 under NodeB)
DSP E1T1:;
3214223G_3G_KUALASIMPANG
+++ 3214223G_3G_KUALASIMPANG 2013-12-10 18:22:04
O&M #94600
%%/*20273703*/DSP E1T1:;%%
RETCODE = 0 Operation succeeded.
DSP E1T1 Result

---------------
Cabinet No. Subrack No. Slot No. Subboard Type Port No. Link Running Status Actual Work Mode Actual Frame Format Actual Line Code Clock Mode Link Test Execution Status Used Flag Loop Left Time(min)
0 0 7 Base Board 0 Available E1 Unbalance E1 CRC4 Multiple Frames E1 HDB3 Code Slave Mode No Test Yes 0
--- END
Nb of E1 ATM under NodeB = Under RNC  4 E1

ACCESSIBILITY
IUB CAPACITY
IuB TYPE – IP
In order to know the IP Bandwidth of RXTX in IP Iub transmission,
LST ADJNODE:LSTTYPE=BYNAME,NAME="X3234477G_3G_SIMPANG_BARU",LSTFORMAT=VERTICAL;
ADJNODE:LSTTYPE=BYNAME,NAME="X3234477G_3G_SIMPANG_BARU",LSTFORMAT=VERTICAL;%%
List Adjacent Node LST IPPATH:ANI=227,LSTFORMAT=VERTICAL;

------------------ RNPKB02
Adjacent Node ID = 227 +++ RNPKB02 2013-12-11 10:23:18
Adjacent Node Name = X3234477G_3G_SIMPANG_BARU O&M #3740186
Adjacent Node Type = Iub Interface %%/*3113584*/LST IPPATH:ANI=227,LSTFORMAT=VERTICAL;%%
NodeB ID = 44771 RETCODE = 0 Execution succeeded.
Transport Type = IP
Is Root Node = <NULL> List IP Path
Route Mode = <NULL> ------------
Upper Ani = <NULL> Adjacent Node ID = 227
Subrack No. = <NULL> IP path ID = 1
Slot No. = <NULL> Interface Type = Iub Interface
Subsystem No. = <NULL> Transport Type = IP
SAAL link No. = <NULL> IP path type = EF
Qaal2 Protocol Version = <NULL> Local IP address = 10.164.19.4
Is IP Pool = No Peer IP address = 10.164.146.45
Ping Check Period = <NULL> Peer subnet mask = 255.255.255.255
Ping Check Timeout Counts = <NULL> Forward Bandwidth = 100000
Ping packet Length = <NULL> Backward Bandwidth = 100000
Differentiated Service Codepoint = <NULL> Carry Flag = NULL
End
End

ACCESSIBILITY
SHO Overhead
SHO Overhead condition describes the overhead condition due to soft/softer handover which impacts to cell dimensioning
High SHOOverhead shows that the network quality around the cell is poor, or many pilot pollution resides.
This condition is triggered by some improper network dimensioning as below :
1. Overshoot cell coverage (many neighbors with strong level of RSCP)  Pilot pollution
2. High mobility in softer handover (although TP is still acceptable)
By reducing SHO Overhead, capacity and network quality will improve.
SHO overhead condition can be detected by analyzing Drive test result.
SHO Overhead = (VS.SHO.AS.1RL)+(2*VS.SHO.AS.2RL)+(3*VS.SHO.AS.3RL) -1 X 100%

(VS.SHO.AS.1RL+ VS.SHO.AS.2RL+ VS.SHO.AS.3RL)

ACCESSIBILITY
SHO Overhead
Overshoot cell coverage (SHOOverhead 118.16% -- 3223745G_3G_PETERNAKAN_SUNGGAL_2)
2.1 km
In this case, pilot pollution is possibly high, and need to

audit site (physical tuning)

ACCESSIBILITY
CE CAPACITY & CONFIGURATION

Under MML Command NodeB, CE capacity & other Board capability information can be collected
DSP BRD:;
3223121G_3G_BROMO_MEDAN DSP BBPTC:CN=0,SRN=0,SN=2; LST LOCELL:MODE=LOCALCELL,LOCELL=1;
+++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:54:56 3223121G_3G_BROMO_MEDAN 3223121G_3G_BROMO_MEDAN
O&M #12692 +++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:55:08 +++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:55:35
%%/*7395401*/DSP BRD:;%% O&M #12693
RETCODE = 0 Operation succeeded. %%/*7395413*/DSP BBPTC:CN=0,SRN=0,SN=2;%% List Local Cell
RETCODE = 0 Operation succeeded. ---------------
Display Board Local Cell ID = 1
------------- Base Band Process Unit Traffic Capability Cell ID = 31211
Cabinet No. Subrack No. Slot No. Config Type SubBoard Type Administrative state StandBy Status Operational State Alarm Status Availability Status ----------------------------------------- Site No. = 31211
Cabinet No. = 0 Sector No. = 0
0 0 2 WBBP NULL Unblocked NULL Enabled Normal Normal Subrack No. = 0 Reserved Cell = FALSE
0 0 3 WBBP NULL Unblocked NULL Enabled Normal Normal Slot No. = 2 UL BB Resource Group No. = 0
0 0 6 UNKNOWN NULL NULL NULL Disabled Normal Unconfigured, Communication lost Cell = 6 DL BB Resource Group No. = 0
0 0 7 WMPT NULL NULL Active Enabled Normal Normal Uplink CE R99 and HSUPA = 384 UL 16QAM = FALSE
0 0 16 FAN NULL NULL NULL Enabled Normal Normal Downlink R99 CE = 384 UL L2 Enhanced = FALSE
0 0 19 UPEU NULL NULL NULL Enabled Normal Normal HSDPA Capacity = 90 ERACH = FALSE
1 4 0 WRFU NULL Unblocked NULL Enabled Normal Normal (Number of results = 1) DL 64QAM+MIMO = FALSE
1 4 2 WRFU NULL Unblocked NULL Enabled Normal Normal DC+MIMO = FALSE
1 4 4 WRFU NULL Unblocked NULL Enabled Normal Normal GU Power Share Flag = TRUE
(Number of results = 9) --- END BOOST = FALSE
FDE = FALSE
IC = FALSE
--- END Local Cell Radius(m) = 29000
LST LOCELL:MODE=ALLLOCALCELL; Local Cell Inner Handover Radius(m) = 0
3223121G_3G_BROMO_MEDAN Two Tx Way = FALSE
DSP BRDMFRINFO:CN=1,SRN=4,SN=0;
+++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:55:15 Cabinet No. of Power Amplifier1 = 1
3223121G_3G_BROMO_MEDAN
O&M #12694 Subrack No. of Power Amplifier1 = 4
+++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:55:56
%%/*7395415*/LST LOCELL:MODE=ALLLOCALCELL;%% Slot No. of Power Amplifier1 = 0
O&M #12698
RETCODE = 0 Operation succeeded. Antenna No. of Power Amplifier1 = ANT0A
%%/*7395449*/DSP BRDMFRINFO:CN=1,SRN=4,SN=0;%%
RETCODE = 0 Operation succeeded. UL Frequency Channel Number = 9813
List Local Cell DL Frequency Channel Number = 10763
--------------- Max Output Power(0.1dBm) = 460
Display Board Manufacturing Information
Local Cell ID Cell ID Site No. Sector No. UL BB Resource Group No. DL BB Resource Group No. Local Cell Radius(m) Local Cell Inner Handover Radius(m) Two Tx Dl BB Resource Allocation Mode = From the WBBPa and other new boards
---------------------------------------
Way Reserved Cell Desensitization Intensity(dB) = 0
Type = WD2MWRFU81
Serial Number = 210231580410A1001403 High Speed Movement Mode = FALSE
1 31211 31211 0 0 0 29000 0 FALSE FALSE Remote Cell Mode = FALSE
Description = HERT RFU,WD2MWRFU81,Multi-Carrier Transceiver
2 31212 31211 1 0 0 29000 0 FALSE FALSE Support VAM = FALSE
Unit(DHT 80W,Band1,RX1920-1980/TX2110-2170MHz)
3 31213 31211 2 0 0 29000 0 FALSE FALSE Tx and Rx Separate Flag = FALSE
Date of Manufacture = 2010-01-05
4 37217 31211 0 0 0 29000 0 FALSE FALSE (Number of results = 1)
Vendor = Huawei
5 37218 31211 1 0 0 29000 0 FALSE FALSE
Issue Number = 00
6 37219 31211 2 0 0 29000 0 FALSE FALSE
(Number of results = 6) --- END
--- END
--- END
ACCESSIBILITY
CE CAPACITY & CONFIGURATION

Each WBBP Board can be set to different UL/DL Group
DSP BRD:;
3223121G_3G_BROMO_MEDAN LST LOCELL:MODE=LOCALCELL,LOCELL=1;
+++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:54:56 3223121G_3G_BROMO_MEDAN
O&M #12692 +++ 3223121G_3G_BROMO_MEDAN 2013-12-05 15:55:35
%%/*7395401*/DSP BRD:;%%
RETCODE = 0 Operation succeeded. List Local Cell
---------------
Display Board Local Cell ID = 1
------------- Cell ID = 31211
Cabinet No. Subrack No. Slot No. Config Type SubBoard Type Administrative state StandBy Status Operational State Alarm Status Availability Status Site No. = 31211
Sector No. = 0
0 0 2 WBBP NULL Unblocked NULL Enabled Normal Normal Reserved Cell = FALSE
0 0 3 WBBP NULL Unblocked NULL Enabled Normal Normal UL BB Resource Group No. = 0
0 0 6 UNKNOWN NULL NULL NULL Disabled Normal Unconfigured, Communication lost DL BB Resource Group No. = 0
0 0 7 WMPT NULL NULL Active Enabled Normal Normal UL 16QAM = FALSE
0 0 16 FAN NULL NULL NULL Enabled Normal Normal UL L2 Enhanced = FALSE
0 0 19 UPEU NULL NULL NULL Enabled Normal Normal ERACH = FALSE
1 4 0 WRFU NULL Unblocked NULL Enabled Normal Normal DL 64QAM+MIMO = FALSE
1 4 2 WRFU NULL Unblocked NULL Enabled Normal Normal DC+MIMO = FALSE
1 4 4 WRFU NULL Unblocked NULL Enabled Normal Normal GU Power Share Flag = TRUE
(Number of results = 9) BOOST = FALSE
--- END FDE = FALSE
IC = FALSE
LST ULGROUP:; Local Cell Radius(m) = 29000
3223121G_3G_BROMO_MEDAN Local Cell Inner Handover Radius(m) = 0
+++ 3223121G_3G_BROMO_MEDAN 2013-12-05 21:37:53 Two Tx Way = FALSE
Cabinet No. of Power Amplifier1 = 1
List ULGROUP Subrack No. of Power Amplifier1 = 4
------------ Slot No. of Power Amplifier1 = 0
UL BB Resource Group No. Demodulation Work Mode Antenna No. of Power Amplifier1 = ANT0A
UL Frequency Channel Number = 9813
0 2-Channels Demodulation Mode DL Frequency Channel Number = 10763
(Number of results = 1) Max Output Power(0.1dBm) = 460
List ULGROUP Dl BB Resource Allocation Mode = From the WBBPa and other new boards
------------ Desensitization Intensity(dB) = 0
UL BB Resource Group No. Cabinet No. of UL Process Unit Subrack No. of UL Process Unit Slot No. of UL Process Unit High Speed Movement Mode = FALSE
Remote Cell Mode = FALSE
0 0 0 2 Support VAM = FALSE
0 0 0 3 Tx and Rx Separate Flag = FALSE
(Number of results = 2) (Number of results = 1)
--- END --- END

ACCESSIBILITY
POWER CAPACITY
There are 2 issues related to power congestion, UL and DL
RRC/CS/PS-ULPowerCongestion : means that UL power capacity for UE under the serving cell is insufficient
RRC/CS/PS-DLPowerCongestion : means that DL power capacity for UE under the serving cell is insufficient
To see realtime health check of the cell : DSP UCELLCHK
How to solve it?

UL Power Congestion : If uplink power is restricted, check whether any interference exists
 UL power is restricted by UlTotalEqUserNum (total equivalent user numbers corresponding to the
 Note : those action means that cell will allow more user to access, which impact to UL Interference
(User interference). The more user can access a cell, the higher UL interference will be

ACCESSIBILITY
POWER CAPACITY
DL Power Congestion : insufficient DL power
To analyze this issue : 1. Attempt RRC/RAB, probably neighbor site was down, impacting load traffic.
2. High TP (Overshoot)
3. If No issue in availability & not overshoot, parameter optimization is needed
PARAMETER ADJUSMENT
1. Set DlCellTotalThd in CAC to 95% (Default 90%), means the number of user to enter the admission before rejection is higher
2. Set GOLD User ON (gold user (384 kbps) will be involved in load control algorithm (RateReduction/HO)
3. Apply LDB action in Algoswitch and set theLDB threshold in UCELLLDB
4. Apply LDR/OLC action
5. Upgrade MaxTxPower (Note : Cell level setting must be < RNC level setting)
In order to improve accessibility due to load issue, load control system is a primary point to understand

ACCESSIBILITY
POWER CAPACITY
Other solution to improve power capacity (DL power issue) is by reducing power margin of the related cell
HSDPA Power Resource (HSDPA Principle)
Power resource management determines the transmit power of the HS-PDSCH, HS-SCCH, and HS-DPCCH.
DL Power Resource Allocation :
1. The downlink power resources are first reserved for common physical channels (CCH) and allocated to the
DPCH (the broadcast channel, pilot channel, and paging channel).
2. Power for DPCH : This portion of power is allocated to real-time services (voice and video calls) and PS R99
services, and varies with the number and locations of users.
3. The HSDPA power resources are first allocated to the downlink control channel HS-SCCH. For
details. The remaining power resources are allocated to the traffic channel HS-PDSCH; The HSPA power
resources is also allocated to the HSUPA downlink control channels, including the
E-AGCH, E-RGCH, and E-HICH
Every TTI,the NodeB detects the power usage of R99 channels to determine the power available for HSPA
 HSDPA user power = Maximum cell transmit power – (Power for CCH + Power margin + Power for DPCH)
4. Power Margin : The power margin is reserved to ensure that the system can remain stable even if the UE
position or environment changes (reserved for R99 power control)

ACCESSIBILITY
POWER CAPACITY
100%
39.81 dBm
95%, 37.8 dBm

ACCESSIBILITY
POWER CAPACITY
TFRC methods
By reducing the power margin, there would be an increment of power resource for R99.
Note : HSDPA Feature & Principles

ACCESSIBILITY
LOAD CONTROL
 The load control algorithms are applied to the different UE access phases as follows:
PUC: Potential User Control CAC: Call Admission Control

IAC: Intelligent Access Control LDB : Intra-frequency Load Balancing
LDR: Load Reshuffling OLC: Overload Control
Resources
Load Control Algorithm
Power Code NodeB Credits Iub Bandwidth
PUC √ - - - Resource considered by each load
IAC √ √ √ √ control algorithm
CAC √ √ √ √ To see all performance counter for algorithm,

LDB √ - - -
LDR √ √ √ √
OLC √ - - √
–: not considered; √: considered

ACCESSIBILITY
LOAD CONTROL : PUC
Threshold
Heavy? Cell TCP SIB3, 11
Light?
Normal? System
cell
information
reselection
RNC parameters NodeB UE
SCRIPT ACTIVATION : MOD UCELLALGOSWITCH: CellId=xxxx, PUC-1;

SCRIPT : MOD UCELLPUC:CELLID=xxx, SPUCLIGHT=35,SPUCHEAVY=50,OFFSINTERHEAVY=8,OFFQOFFSET1HEAVY=12,OFFQOFFSET2HEAVY=12;
Default : SPUCLIGHT : 35, SPUCHeavy : 70, OffQoffSET1Heavy=4, OffQoffset1Light=-4

SPUCLIGHT & SPUCHHeavy : to decide whether the cell load is in havey/light condition
OffQoffSET1Heavy (RSCP) : if neighbor cell is in heavy load, Qoffset1sn will be offset 4 dB  hold user in source cell
OffQoffset1Light (RSCP) : if neighhbor cell is inlight load, Qoffset1sn will be offset -4 dB  faster reselection to neighbor cell

ACCESSIBILITY
LOAD CONTROL : LDB
Intra-frequency Load Balancing (LDB) is performed to adjust the coverage areas of cells by modifying PCPICH power, means will affect UE in all states
This counter informs the cell breathing

Condition, how long its condition is over
threshold, Nb of CPICH Pilot adjustment
SCRIPT ACTIVATION : MOD UCELLALGOSWITCH: CellId=xxx, NBMLdcAlgoSwitch=INTRA_FREQUENCY_LDB-1;

SCRIPT : MOD UCELLLDB: CellId=xxx, PCPICHPowerPace=2, CellOverrunThd=12, CellUnderrunThd=12;
Default : PCPICHPowerPace: Pilot Power adjustment step (increased/decreased) too high value will cause drop call
CellOverrunThd-UnderrunThd : threshold to decide the cell is overload

ACCESSIBILITY
LOAD CONTROL : CAC
CAC is used to determine whether the system resources are sufficient to accept a new user's access request or not
Admission request
Code-based No
admission successful?
Yes
No
Power-based
As CAC is a decision threshold whether a user is admitted/
“permitted” to access a service, and if CAC admission control is set to
Yes
OFF/no threshold, means there will be no limitation threshold for user
NodeB credit-based
No CAC Decision Threshold to access a service (all users will be permitted to access  high user 
UL interference)
Yes
No
Iub resource-based
Yes
Admission based on No
the number of HSPA users
successful?
Yes
Resource-based admission Resource-based admission

successful unsuccessful

ACCESSIBILITY
LOAD CONTROL : CAC
CAC SWITCH :
 Code CAC
 DlHoCeCodeResvSf (Code&Creditreserved for HO)
 Power CAC
 Uplink CAC algorithm switch: ALGORITHM_SECOND
 Downlink CAC algorithm switch: ALGORITHM_FIRST
 NodeB credit CAC
 CAC algorithm switch: ON
 Cell CAC algorithm switch-CRD_ADCTRL: ON
 HSDPA user number CAC
 Cell CAC algorithm switch-HSDPA_UU_ADCTRL: OFF
 HSUPA user number CAC
 Cell CAC algorithm switch-HSUPA_UU_ADCTRL: OFF

ACCESSIBILITY
LOAD CONTROL : POWER CAC
UL power congestion : UL Power Congestion : If uplink power is restricted, check whether any interference exists
Request initiation  UL power is restricted by UlTotalEqUserNum (total equivalent user numbers corresponding to the
Uplink call  Note : those action means that cell will allow more user to access, which impact to UL Interference.
admission decision (User interference). The more user can access a cell, the higher UL interference will be
DL power congestion :
1. Set DlCellTotalThd in CAC to 95% (Default 90%), means the number of user to enter the admission before rejection is higher.
No 2. Set GOLD User ON (gold user (384 kbps) will be involved in load control algorithm (RateReduction/HO)
Admitted?
3. Apply LDB action in Algoswitch and set theLDB threshold in UCELLLDB
4. Apply LDR/OLC action
Yes 5. Upgrade MaxTxPower (Note : Cell level setting must be < RNC level setting)
Downlink call
admission desicion
No
Admitted?
Yes
Request accepted Request rejected

ACCESSIBILITY
UCELLALGOSWITCH : NBMUlCacAlgoSelSwitch  UL CAC Algorithm Switch
NBMDLCacAlgoSelSwitch  DL CAC Algorithm Switch
Algorithm OFF : UL/DL admission control algorithm is disabled

Algorithm 1: based on UL/DL load measurement and load prediction (RTWP and TCP)/Power-based increment prediction
Algorithm 2: based on Equivalent Number of User (ENU)
Algorithm 3: loose call admission control algorithm
Algorithm 1 : Obtain ULRTWP, TCH from Cell/UE

RNC Cell
calculate the current LST UCELLCAC:CELLID=38219,LSTFORMAT=VERTICAL;
uplink load factor ηUL of RNMDN06
+++ RNMDN06 2013-12-06 15:19:30
the requested service O&M #1136876
(&its increment), and %%/*3030048*/LST UCELLCAC:CELLID=38219,LSTFORMAT=VERTICAL;%%
predict the UL Load Factor RETCODE = 0 Execution succeeded.
ηUL(UlCCHLoadFactor)
List Cell Oriented CAC Algorithm Parameters
-------------------------------------------
Cell ID = 38219
Cell Name = MD3G2_38219
Cell environment type = TU
UL threshold of Conv AMR service = 75
UL threshold of Conv non_AMR service = 75
UL threshold of other services = 60
DL threshold of Conv AMR service = 85
DL threshold of Conv non_AMR service = 85

ACCESSIBILITY
Algorithm 2 : the admission of uplink/downlink power resources uses the algorithm depending on the Equivalent Number of Users (ENU)
The 12.2 kbit/s AMR traffic is defined as one ENU. Thus, the 12.2 kbit/s AMR traffic can be used to calculate the ENU of all other services
Obtain total ENU from CELL

RNC Cell
Obtain New incoming LST UCELLCAC:CELLID=38219,LSTFORMAT=VERTICAL;
ENU, and forecast the RNMDN06
+++ RNMDN06 2013-12-06 15:19:30
Total ENU O&M #1136876
%%/*3030048*/LST UCELLCAC:CELLID=38219,LSTFORMAT=VERTICAL;%%
RETCODE = 0 Execution succeeded.
List Cell Oriented CAC Algorithm Parameters

-------------------------------------------
Cell ID = 38219
Cell Name = MD3G2_38219
Cell environment type = TU
UL threshold of Conv AMR service = 75
UL threshold of Conv non_AMR service = 75
UL threshold of other services = 60
DL threshold of Conv AMR service = 85
DL threshold of Conv non_AMR service = 85
DL threshold of other services = 83
UL handover access threshold = 80
DL handover access threshold = 87
UL total power threshold = 95
DL total power threshold = 95
UL common channel load reserved coefficient = 0
DL common channel load reserved coefficient = 0
DL neighbour interference factor = 60
UL total equivalent user number = 200
DL total equivalent user number = 200

ACCESSIBILITY
Algorithm 3 : Algorithm 3 is similar to algorithm 1. The difference is that the estimated load increment in algorithm 3 is always set to 0
X No calculation of its increment

ACCESSIBILITY
LOAD CONTROL : CREDIT CAC
• CE is used to measure the channel demodulation capability of the NodeBs. On the RNC side, it is referred to the NodeB credit. On the
NodeB side, it is the channel element
• The resource of one equivalent 12.2 kbit/s AMR voice service, including 3.4 kbit/s signaling, is defined as one CE
• There are two kinds of CE, that is, uplink CE supporting uplink services and downlink CE supporting downlink services. Therefore, one
12.2 kbit/s AMR voice service consumes one uplink CE and one downlink CE

ACCESSIBILITY
LOAD CONTROL : CREDIT CAC
UlHoCeResvSf
Parameter name: UL handover credit reserved SF
Recommended value: SF16
DlHoCeCodeResvSf
Parameter name: DL handover credit and code reserved SF
HsupaCeConsumeSelection
Parameter name: HSUPA Credit Consume Type
Recommended value: MBR

ACCESSIBILITY
LOAD CONTROL : HSDPA/HSUPA CAC
HSPA user number CAC is involved in:
Cell level  Maximum number of HSPA users in a cell
NodeB level  Maximum number of HSPA users in all the cells configured in one NodeB
HSDPA user number CAC:

When HSDPA_UU_ADCTRL is set to on, the HSDPA services have to undergo admission decision based on the number of HSDPA users.
When a new HSDPA service attempts to access the network, the algorithm admits the service if the following conditions are met:
The number of HSDPA users in the cell does not exceed the maximum value specified by MaxHsdpaUserNum.
The number of HSDPA users in the NodeB does not exceed the maximum value specified by NodeBHsdpaMaxUserNum (UNODEBALGOPARA 
3840/6144  high number).
Otherwise, the algorithm rejects the service request.
HSUPA user number CAC:
When HSUPA_UU_ADCTRL is set to on, the HSUPA services have to undergo admission decision based on the number of HSUPA users.
When a new HSUPA service attempts to access the network, the algorithm admits the service if the following conditions are met:
The number of the HSUPA users in the cell does not exceed the maximum value specified by MaxHsupaUserNum.
The number of the HSUPA users in the NodeB does not exceed the maximum value specified by NodeBHsupaMaxUserNum (UNODEBALGOPARA).
Otherwise, the algorithm rejects the service request.

ACCESSIBILITY
LOAD CONTROL : HSDPA/HSUPA CAC
HSDPA_UU_ADCTRL/ HSUPA_UU_ADCTRL Active:
CAC PBRThd
HsdpaStrmPBRThd : Average throughput admission threshold of the HSDPA streaming service

If the sum of PBR of all the accessed streaming users is lower than the average throughput admission threshold of the HSDPA streaming service multiplied by the sum of GBR of all
the accessed streaming users, it indicates that the QoS of the accessed users cannot be satisfied and new HSDPA streaming services are not allowed. Otherwise, the QoS can be
satisfied and new HSDPA streaming services are allowed
HsdpaBePBRThd : Average throughput admission threshold of the HSDPA best effort traffic
If the sum of PBR of all the accessed HSDPA BE users is lower than the average throughput admission threshold of the HSDPA BE service multiplied by the sum of GBR of all the
accessed HSDPA BE users, it indicates that the QoS of the accessed users cannot be satisfied and new HSDPA BE services are not allowed
If the value is too high, admission requirement of the HSDPA streaming/BE service is strict, which improves the service quality of the HSDPA streaming/BE
service but also may lead to HSDPA capacity waste. If the value is too low, admission requirement of the HSDPA streaming/BE service is loose, which allows
more HSDPA streaming/BE services but QoS of the HSDPA streaming/BE service cannot be guaranteed.
Higher value  more strict  capacity waste  Guaranted Bit Rate (UEnum is small)
Lower value  more services allowed  Bit rate is nor guaranted

ACCESSIBILITY
LOAD CONTROL : IAC (Intelegence Access Control)
The disadvantages of CAC:
For PS NRT (Non-Real Time) services, CAC is not flexible
No consideration about the priority of different users
No consideration about Directed Retry after CAC rejection
“Intelligent” means the algorithm can increase admission successful rate
This load control is mainly related to DRD parameter (DirectRetryDecision)

DrSwitch-DR_ RRC_DRD_SWITCH
Parameter name: DRD switch for RRC connection The RNC implements service steering between inter-frequency (Interfreq DRD)
Recommended value: ON or inter-RAT (DRD) cells according to the cause of RRC connection setup. In
RedirSwitch addition, the RNC considers the load of the cell for access and the redirection
factors to control the degree of load balancing
Parameter name: Redirection Switch • Algorithm switch: DrSwitch-DR_ RRC_DRD_SWITCH
Recommended value: OFF • Triggering factor: RedirFactorOfNorm or RedirFactorOfLDR
RedirFactorOfNorm/RedirFactorOfLDR • Target cell: RedirSwitch
Current Condition : to HHOInterfreq
Parameter name: Redirection Factor Of Normal/LDR
Recommended value: 0, 100
DRDEcN0Threshhold
Parameter name: Drd Ec/N0 threshold
Recommended value: -18, namely -18dB
ACCESSIBILITY
LOAD CONTROL : LDR (Load Resuffling)
To see the counter performance of LCC (Load Congestion Control): Check counter under Algorithm Cell

ACCESSIBILITY
LOAD CONTROL : LDR (Load Resuffling)
NBMLdcAlgoSwitch-UL_UU_LDR/DL_UU_LDR CellLdrSfResThd
Parameter name: Cell LDC algorithm switch for LDR Parameter name: Cell LDR SF reserved threshold
Recommended value: OFF, OFF Recommended value: SF8
UlLdrTrigThd/DlLdrTrigThd  UCELLLDM MaxUserNumCodeAdj
Parameter name: UL/DL LDR trigger threshold Parameter name: Max user number of code adjust
Recommended value: 55%, 70% Recommended value: 1
UlLdrRelThd/DlLdrRelThd LdrCodePriUseInd
Parameter name: UL/DL LDR release threshold Parameter name: LDR code priority indicator
Recommended value: 45%, 60% Recommended value: FALSE
NBMLdcAlgoSwitch-CELL_CODE_LDR
Parameter name: Cell LDC algorithm switch for LDR
Recommended value: OFF
CellLdrSfResThd
Parameter name: Cell LDR SF reserved threshold
NodeBLdcAlgoSwitch-IUB_LDR
Parameter name: NodeB LDC algorithm switch for LDR
Recommended value: OFF

ACCESSIBILITY
LOAD CONTROL : OLC
After the UE access is allowed, the power consumed by a single link is adjusted by the single link power control function. The power varies with all kinds of
factors such as the mobility of the UE and the changes in the environment. In some situations, the total power load of the cell can be higher than the target
load. To ensure the system stability, Overload Control (OLC) must be performed.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC subparameters of the NBMLdcAlgoSwitch parameter.
UL/DL load The above figure shows the triggering and release of cell power overload:
If the current UL/DL load of an R99 cell is higher than or equal to
Overload released the UlOlcTrigThd or DlOlcTrigThd for 1,000 ms, the cell is in the
Cell in overload
overload state and the related overload handling action is taken. If
the current UL/DL load of the R99 cell is lower than the
OLC trigger UlOlcRelThd or DlOlcRelThd for 1,000 ms, the cell comes back to
threshold the normal state.
OLC release
The overload triggering and release mechanisms for UL HSPA cells
threshold are the same as those for R99 cells.
Whether a DL HSPA cell is overloaded is estimated according to the

sum of the non-HSPA power and the GBP.
time
RNC periodic check
State transition hysteresis threshold

ACCESSIBILITY
LOAD CONTROL : OLC
NBMLdcAlgoSwitch-UL_UU_OLC/DL_UU_OLC
Parameter name: Cell LDC algorithm switch for OLC
Recommended value: OFF, OFF
UlOlcTrigThd/DlOlcTrigThd
Parameter name: UL/DL OLC trigger threshold
Recommended value: 95%, 95%
UlOlcRelThd/DlOlcRelThd
Parameter name: UL/DL OLC release threshold
Recommended value: 85%, 85%
OlcPeriodTimerLen
Parameter name: OLC period timer length
Recommended value: 3000, namely 3000ms

RETAINABILITY – RL Re-Establishment
RADIO LINK RE-ESTABLISHMENT
Radio Link Re-Establishment is optional feature.

Mostly RABAbnormal release is due to SRB.Reset where this loss is triggered when RNC receives an update from
cell that error happens in RLC then RNC will send “IU Release Request” to CN due to RL RF failure and the call is
dropped

RLC UE BEHAVIOUR
RLC unrecoverable error
If the maximum number of tranmissions of a RESET PDU is equal to MaxRST-1, then RLC unrecoverable error shall be indicated to upper layers.
The concept of RLC unrecoverable error is valid only for RLC-AM entities (Signalling radio bearer
for all messages sent on the DCCH)
Cell Update Procedure

The UE will initiate a RRC Cell update procedure, when a RLC unrecoverable error
is detected. The cell update cause will be set to "RLC unrecoverable error".
Network behaviour on receiving cell update message with cause RLC unrecoverable error
There are two options available for the network
a) It can support call re-establishment (Accessibility-RRC Connection Setup)
b) It cant support call re-establishment. (Accessibility-RRC Connection Setup)
This is governed by the timer values T314(CS) and T315(PS) signalled in SIB 1. if they are set to 0,
then network doesnt support call re-establishment i.e RRC connection signalling release message will be
sent to UE and if these timers have a value other than 0, then the network will do the re-establishment via
the cell update confirm message.

RLC UE BEHAVIOUR
 User equipment (UE) can detect a Radio Link Control (RLC) unrecoverable error and a Radio Link (RL) failure. The two errors are handled
differently while the UE is in a dedicated channel (DCH) state. The RL failure leads to execution of Radio Access Bearer (RAB) release steps,
characterized by utilizing respective timer values to determine if associated RABs should be released. The RLC unrecoverable error is not permitted
to execute the RAB release steps. This prevents unnecessary dropping of services. The UTRAN can optionally include and set the indicators to
command the UE to perform the indicated RLC re-establishment procedure.
 SRB is on Control Plane part and RB is on User Plane Part
 When the maximum number of attempts to send a RESET PDU is reached (MAXRST), the sender RLC entity 76 shall terminate the on-going RLC
RESET procedure and indicate an unrecoverable error to the upper layer (RRC layer 80).When the RRC layer 80, receives the indicated
unrecoverable error from the AM RLC entity 76 the UE shall perform a Cell Update procedure using the cause "RLC unrecoverable error"
All RNC, MAXRST is already D32

RL Failure Message Procedure
UE NodeB RNC CN
Measurement Report
(cell update :RLC error/RL
Failure) Measurement Result
RL Failure INDICATION
RL RESTORE INDICATION
message IU RELEASE REQUEST (RL Failure)
(during timer T314/T315)
UE will update to RNC related to the RF condition

RL Failure Message Procedure
When RL Re-establishment is activated :
Activation of RL Reestablishment:
RsvdPara1: RSVDBIT1_BIT22,
RSVDBIT1_BIT23, RSVDBIT1_BIT24,
At this point, RNC RSVDBIT1_BIT25, RSVDBIT1_BIT26,
will do Link re-
(cell update :RLC error/RL establishment RSVDBIT1_BIT28
Failure) when :
1.RNC receives
RLFailure
Indication and
2. Doesn’t receive
an RL Restore
RL RESTORE INDICATION Indication msg
message from nodeB after
(during timer T314/T315) timer expires
Radio Link Re-establishment

UTILIZATION
Related to capacity monitoring, a utilization of 3G capability is necessary to check.
Below are formula to calculate a utilization in WCDMA :
KPI Name Formula
UL Max CE Utilization Rate (%) 100* (VSLCULMaxLicenseGroupShared(A)/VSLCULCreditAvailableShared(B))
DL Max CE Utilization Rate (%) 100* (VSLCDLMaxLicenseGroupShared(A)/VSLCDLCreditAvailableShared(B))
UL Average CE Utilization Rate (%) 100*(VSLCULMeanLicenseGroupShared(A)/VSLCULCreditAvailableShared(B))
DL Average CE Utilization Rate (%) 100*(VSLCDLMeanLicenseGroupShared(A)/VSLCULCreditAvailableShared(B))
IuB DL Max Utilization (%) 100*(VSATMDlMaxUsed1(A)/VSATMDlTotal1(B))
IuB DL Avg Utilization (%) 100*(VSATMDlAvgUsed1(A)/VSATMDlTotal1(B))
Average Code Utilization Rate (%):
100*(((([VSMultRABSF4]+[VSSingleRABSF4])*64)+(([VSMultRABSF8]+[VSSingleRABSF8])*32)+(([
Average Code Utilization Rate (%) VSMultRABSF16]+[VSSingleRABSF16])*16)+(([VSMultRABSF32]+[VSSingleRABSF32])*8)+(([VSM
ultRABSF64]+[VSSingleRABSF64])*4)+(([VSMultRABSF128]+[VSSingleRABSF128])*2)+([VSMultR
ABSF256]+[VSSingleRABSF256]))/256)
Power Avg Uttilization(%) (10^(([VSMeanTCP]-MaxTA(dBm)/10))*100
Iu-CS Utilization (%) CS traffic (VS.AMR.RB.DL.12.2) / Iu-CS Interface cap
Iu-PS Utilization (%) (VS.IuPS.BytesPayldIntact.Rx + VS.IuPS.BytesPayldBgrd.Rx) / IU-PS bandwidth

UTILIZATION
CE Utilization – M2000 Iub Utilization – M2000

UTILIZATION
Power Utilization – M2000 Code Utilization – M2000

THROUGHPUT
Throughput Analysis
Analysis flow Action Needs
Resource check
Parameter audit
TOP Cell analysis
Action of Parameter opt

THROUGHPUT
Resource Uu Interface
Resource Allocate
Method
MPO not
Limitation proper
Schedule
Power CQI
Schedule Algorithm L2L swap
E1 num not No Adjust by
enough Coverage Dynamic BLER
Code
Iub Transmission Limitation
Low HSDPA
Transmission A lot small-packet
Throughput
service in HSDPA
tariff policy
Transmission limitation Service
adjust UE access even
Type
in cell center
tariff Large packet service even TP of Access
Some Server unstable
policy
Server CAT More UE access in
the border of Cell
not enough data in Buffer More high-cat UE
Operator Out of RAN UE

THROUGHPUT
Cause Action Analysis Optimization
1, parameter tuning whole network
Resource Allocate Parameter check It is difficulty to divide the cell to ‘power limit’ or ‘code
2, raise a RM to R&D to set the default
Method Top cell check limit’, the ‘power and code balance’ method is better.
value in R14
1, parameter tuning whole network
No Adjust by BE (non-conversation) can get better throughput based on
Parameter check 2, raise a RM to R&D to set the default
Dynamic BLER the real channel quality.
value in R14
Optimize the status transfer timer to put the small-packet user
A lot small-packet Top cell check 1, parameter tuning in top cells
to FACH
service in HSDPA Customer complain 2, UUESTATETRANSTIMER
The UE measures the Ec/No of the Common Pilot Channel

(CPICH) and adds a Measurement Power Offset (MPO) as the
MPO not proper Parameter check parameter tuning in top cells
Ec/No estimation value of the HS-PDSCH, to modify the SNR
of channel evaluation.
Resource check E1 expansion or change to IP(can not
E1 num not enough The Iub limit the throughput in some hotspots.
Top cell check control)
not enough data in Top cell check
This is the limitation of server. None
Buffer Customer complain
More UE access in Top cell check Need U900 activation to optimize the
The coverage have extension after the 3rd carrier activation.
the border of Cell Customer complain coverage of top cell.

THROUGHPUT
OPT 1 . HSDPA radio resource allocation strategies, whole network

SET MACHSPARA: LOCELL=0, RSCALLOCM=POWERCODE_BAL
This feature can balance the consumption of currently available code resources and power resources, to avoid code or power
unilaterally congestion in order to improve resource utilization, enhance cell capacity. Relative to the code priority, the power code
balance can enhance the cell downlink load, while reducing the resource utilization of code.
CODE_PRI: Code resource priority allocation strategy is mainly used in the power-limit scenario, this strategy led to a low ratio of power
resource utilization in the power not limit scenario, thereby reducing the system throughput.
POWER_PRI: power resources for priority allocation, mainly used in the code resource constrained scenario, this strategy led to a low
ratio of code resource utilization in the code not limit scenario, thereby reducing the system throughput.

THROUGHPUT
OPT 2. Configuring CQI Adjustment Based on Dynamic BLER Target

SET MACHSPARA: LOCELL=0, CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER;
With this feature, the NodeB can dynamically select the optimum BLER target value based on the channel quality fluctuation of HSDPA
users. The NodeB then adjusts the Channel Quality Indicator (CQI) accordingly, improving user throughput and cell throughput.
NO_CQI_ADJ: The UE measures the Ec/No of the Common Pilot Channel (CPICH) and adds a Measurement Power Offset (MPO) as the
Ec/No estimation value of the HS-PDSCH. That is, the UE assumes that the NodeB transmits the HS-PDSCH according to CPICH Power +
MPO. Then, add the SF gain 10 * log16 to obtain the SNR of the HS-PDSCH. Obtain the CQI according to the relationship between the
SNR and CQI of the simulated HS-PDSCH.
CQI_ADJ_BY_IBLER: 1st SBLER indicates the BLER of initial data transmission, also called IBLER. With this feature ,NodeB can adjust CQI
to a proper value according IBLER . But in some scenario ,If the SBLER is always around 10% no matter how you move the position, it
may results from enabling the function of channel adjustment.

THROUGHPUT
OPT 3. status transfer parameter optimization
MML Parameter Default value Opt value

BeF2DTvmTimeToTrig D0 D640
BeF2HTvmTimeToTrig D0 D640
D0
SET UUESTATETRANS BeF2ETvmTimeToTrig D640
BeH2FTvmTimeToTrig D5000 D2560
D2FTvmTimeToTrig D5000 D2560
SET BeD2FStateTransTimer 5 2
UUESTATETRANSTIMER BeH2FStateTransTimer 5 2

THROUGHPUT
OPT 4. Modify Cell HSDPA Parameters (Recommended value of Power Compensate is set to 1~1.5)
MOD UCELLHSDPA : CellId=0, HsPdschMPOConstEnum = 0;
This parameter named Measure Power Offset Constant is used to compute measurement power offset. Measurement power offset is
used by UE to obtain total received HS-PDSCH power. The calculation for Measure Power Offset is as shown below:
CQI = CPICH Ec/No + MPO + 10 * log16 + 4.5

= SNRcpich + MPO + 4.5
= SNRhs-pdsch (based on assumed power) + 4.5 (with a round process, depending on the UE implementation)
MPO = min(13, Pcell-Pcpich - MPO constant) dB , The MPO constant is 2.5 by default
(For details of the IE "Measure Power Offset", refer to 3GPP TS 25.214)

THROUGHPUT
HSDPA Throughput
Chip Rate(Kcps) SF No. of Bits per modulation scheme Modulation Scheme Encoding Rate No. of SF 16 codes Throughput(kbps) Throughput(Mbps)
3840 16 2 QPSK 3/4 5 1800 1.8

3840 16 4 16 QAM 3/4 5 3600 3.6
3840 16 4 16 QAM 3/4 10 7200 7.2
3840 16 4 16 QAM 4/4 15 14400 14.4
3840 16 6 64 QAM 4/4 15 21600 21.6
HSUPA Throughput
Chip No. of Bits per modulation Modulation Encoding Throughput(kbp Throughput(Mbp
SF No. of SF codes
Rate(Kcps) scheme Scheme Rate s) s)
3840 4 2 QPSK - 1 1920 1.92
3840 2 2 QPSK 1 3840 3.84
3840 4 6 64 QAM 1 5760 5.76
3840 2 4 16 QAM 1 7680 7.68

2nd CARRIER IMPLEMENTATION
2ND CARRIER STRATEGY XL
Intra-freq. SHO bi-directional
Inter-RAT handover (3G to 2G)
F2 R99+HSPA R99+HSPA
R99+HSPA
Inter-Freq Handover (Blind
handover)
F1 R99+HSPA R99+HSPA R99+HSPA
GSM 2G 2G 2G 2G
 Allow intra-frequency handover based on coverage both for F1 & F2;

 Configure blind handover neighboring relationships between F1 and F2 cells within the same
coverage range, allow Inter-freq handover (bi-directional blind handover) between F1 and F2
in the area both F1 and F2 covered.
 Configure GSM as neighboring cell both for F1 and F2, only configure F1 as neighboring cell
for GSM.

F2 to F2 Intra-Frequency Neighbor Relation
The same strategy with F1 cell, the adjacency F2 cell should be configured as neighbor
F2 to GSM Neighbor Relation

The same strategy with F1 cell, the adjacency GSM cell should be configured as neighbor
GSM to F2 Neighbor Relation

No need to configure, just make sure GSM to F1 neighbor relation is configured
Active RNC Level DRD (Directed Retry Decision) function

Use below script to active RNC Level DRD function
Set UDRD: LdbDRDSwitchHSDPA=ON;
Active Cell Level DRD (Directed Retry Decision) function

Use below script to active Cell Level DRD function
ADD UCELLDRD: CellId=12344, LdbDRDSwitchHSDPA=ON;

Configure F1 to F2 inter-frequency neighbor (and vice versa), the same sector F1 cell to F2 cell inter-frequency neighbor relation
Script Sample
ADD UINTERFREQNCELL: RNCId=310, CellId=15461, NCellRncId=310, NCellId=15464,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, HOCovPrio=0, BlindHoFlag=TRUE,
NPrioFlag=FALSE, DRDEcN0Threshhold=-14;
Parameter Description
Source Cell fill in F1 Cell ID, should be the same sector with F2 cell
Target Cell fill in F2 Cell ID, should be the same sector with F1 cell
set "HOCovPrio=0" to disable coverage-based inter-freq handover (F1&F2 cell
HOCovPrio
with same coverage, so if F1 coverage poor, F2 coverage will poor too)
BlindHoFlag set "BlindHoFlag=TRUE" to enable F1 to F2 DRD (directly retry decision)

DRDEcN0Threshh set "DRDEcN0Threshhold = -14 " to avoid the DRD happened in poor coverage
old area (the Ec/No lower than -14)

LMT NodeB MONITORING
2G-3G AGRESIVITY
In this part, the main point is how to make 3G network more aggressive than 2G in order to build up good customer perception
Principle of reselection from 2G to 3G in idle mode
 qSearchI
Start  7 (always search): UE will always search 3G cells. This setting are configured for all
2G cell
 15 (never search): UE never search 3G cells.
No Does the signal level of serving cell
meet the requirement of threshold  fddQOffset  point 1 (This describes the signal level offset for 3G cell reselection.
of searching for 3G cell?
A 3G cell can be reselected when the average signal level of the target 3G cell is
higher than that of the current serving cell )
Yes
1  Range [-32dB; 0 dB]: 2 kinds of thresholds are used for different cells.
Is RSCP>RLA_C + Qoffset?
No And does this condition last RLA= the  Recommended value : 0 (-32)
for more than 5 seconds? received signal
level average  fddQMin  point 2 (This describes the signal level threshold for 3G cell
Yes [dBm] for the reselection. Only when the signal level in the target 3G cell is higher than the
serving GSM cell
No Is CPICH Ec/No> FDD_Qmin?
And does this condition last
2 and its strongest
serving cell. the target 3G cell may become a candidate cell for reselection)
for more than 5 seconds? GSM neighbors  Range[-10 dB;-12dB; -20dB]: 3 kinds of thresholds are used for different cells.
Yes
The cell reselection is complete.  To avoid ping pong reselection between 2G-3G is by fulfilling a criteria : FDDQmin >
Qqualmin + SsearchRat
End
MAIN MONITORING REALTIME
Below are some of primary real time monitoring/checking :
1. RTWP Measurement
2. RX SCANNING
3. Throughput, User Number, RTWP
4. Iub IP Ping Transmission

RTWP MEASUREMENT
Main point for RTWP measurement :
1. RTWP measurement is for UL side of the cell
2. RTWP measurement is inline with SIB7 distribution (Message related to UL interference)
3. RTWP alarm is triggered when the delta(difference) level between Primary RTWP and Secondary RTWP is reaching 6 dB
4. RTWP is considered to be the impact of low accessibility/high drop when the value is higher than -95 dBm
5. RTWP is raising as the traffic is increasing
6. UL interference can be triggered either by Internal or External Interference
7. RXScanning is necessary as to identify RTWP cause, how wide the interference is, etc
8. Using LMT (Local Maintenance Terminal), RTWP checking (other actions), can be conducted remotely to the nodeB
9. RTWP statistic can be gathered from M2000 in subset “CELL TS & RX Power” with counter [VS.MaxRTWP (dBm), VS.MeanRTWP (dBm), and VS.MinRTWP
(dBm)]
10. Mapping the RTWP issue to know whether the issue is localize issue or not
11. Check whether the RTWP occur only in busy hour or always high during the whole day

RTWP MEASUREMENT
Case : 322C015G_3G_KISARAN_II
MD3G30157
4 km
MD3G2_32734
Cell covers end coverage and far distance around 3.5 km. It is possible the cause is either due to external interference or internal issue.

RTWP MEASUREMENT
RXModBranch=
6 dB
RXModBranch=
6 dB
After set RXmodBranch 6 dB, RTWP improved, and traffic CS & Data are still stable. Currently, setting has been fall
back to default (0 dB)

RTWP MEASUREMENT
Block board
sector 2 & 3
No improvement when board sector 2 & 3 were blocked  not impacted from internal hardware issue of other WRFU board.
Plan : 1. Swap WRFU of sector-1 to 2/3 due to no external interference/any UL interference found in RXScanning
2. Physical tuning antenna (downtilt), but will sacrifice loss traffic

RTWP MEASUREMENT
Case : 322C015G_3G_KISARAN_II (AFTER SWAP WRFU Sec-1 to Sec-2)
Suspect
WRFU
HW issue

RTWP MEASUREMENT
Case : 322C015G_3G_KISARAN_II (AFTER REPLACE WRFU)

CELL-NODEB MONITORING VIA RNC
There are many real time

Monitoring of cell and can be used to
Identify issue

RX SCANNING
RX Scanning is necessary to know the level of “interference” in measured frequency range.
In order to conduct a frequency RX Scanning, board WRFU must be blocked first
+++ 3G_GARUMARENDAL
O&M #44130
%%DSP BRD:;%%
RETCODE = 0 Operation succeeded.
Display Board
-------------
Cabinet No. Subrack No. Slot No. Config Type SubBoard Type Administrative state StandBy Status Operational
State Alarm Status Availability Status
0 0 1 WBBP NULL Unblocked NULL Enabled Normal Normal

0 0 3 WBBP NULL Unblocked NULL Enabled Normal Normal
0 0 7 WMPT NULL NULL Active Enabled Normal Normal
0 0 16 FAN NULL NULL NULL Enabled Normal Normal
0 0 18 UEIU NULL NULL NULL Disabled Normal Unconfigured
0 0 19 UPEU NULL NULL NULL Enabled Normal Normal
1 4 0 WRFU NULL Unblocked NULL Enabled Normal Normal
1 4 2 WRFU NULL Unblocked NULL Enabled Major Normal
1 4 4 WRFU NULL Unblocked NULL Enabled Normal Normal
--- END

Below are user number, throughput & RTWP real time monitoring :

Below is CPU usage real time monitoring, related to CPU load measurement

Iub PING TEST
LST DEVIP:; LST VLANMAP:;
3234477G_3G_SIMPANG_BARU 3234477G_3G_SIMPANG_BARU
+++ 3234477G_3G_SIMPANG_BARU 2013-12-11 18:03:39 +++ 3234477G_3G_SIMPANG_BARU 2013-12-11 18:03:50
O&M #44095 O&M #44096
%%/*24306053*/LST DEVIP:;%% %%/*24306093*/LST VLANMAP:;%%
RETCODE = 0 Operation succeeded. RETCODE = 0 Operation succeeded.
List Device IP Configuration Data List Next Hop VLAN Mapping Configuration
--------------------------------- ----------------------------------------
Cabinet No. Subrack No. Slot No. Subboard Type Port Type Port No. IP Address Mask Next Hop IP VLAN Mode Insert VLAN Tag VLAN ID Set VLAN Priority VLAN Priority VLAN Group No.
0 0 7 Base Board Ethernet Port 0 10.164.62.77 255.255.255.0 10.164.62.1 Single VLAN Enable 2202 Enable 0 NULL
0 0 7 Base Board Ethernet Port 0 10.164.146.45 255.255.255.224 10.164.146.33 VLAN Group NULL NULL NULL NULL 0
(Number of results = 2) (Number of results = 2)
--- END --- END
PING:SN=7,SRCIP="10.164.146.45",DSTIP="10.164.146.33",CONTPING=DISABLE,APPTIF=YES,SBT=BASE_BOARD,PT=ETH,PN=0;
3234477G_3G_SIMPANG_BARU
PING 10.164.146.33: 32 data bytes

Reply from 10.164.146.33: bytes=32 Sequence=1 ttl=64 time=10 ms
Reply from 10.164.146.33: bytes=32 Sequence=2 ttl=64 time=10 ms Note : 10.164.62.77  IP OM (monitoring)
Reply from 10.164.146.33: bytes=32 Sequence=3 ttl=64 time=1 ms 10.164.146.45  IP Service
Reply from 10.164.146.33: bytes=32 Sequence=4 ttl=64 time=1 ms
--- 10.164.146.33 ping statistics ---
10.164.62.1  IP Gateway Monitoring
4 packet(s) transmitted 10.164.146.33  IP MPLS (Connected to RNC)
4 packet(s) received
Percent 0.00 packet lost
round-trip min/avg/max = 1/5/10 ms
13 reports in total
--- END
Total: 13 packet(s) received.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 174

Huawei 2G/3G Network Optimization: Sharing Session Bandung, January 21-23, 2015

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei 2G/3G Network Optimization: Sharing Session Bandung, January 21-23, 2015

Uploaded by

Copyright:

Available Formats

Security Level:

Huawei 2G/3G Network Optimization

HUAWEI TECHNOLOGIES CO., LTD.

3 2G/3G Huawei Parameters

4 2G/3G Optimization Cases

5 2G/3G Hedex Documentation

PT. HUAWEI SERVICES Huawei Confidential Page 2

PT. HUAWEI SERVICES Huawei Confidential Page 3

Verify Parameter Problems

Classify Parameter Problems Other Process

Determine Parameter Values to be

Evaluate Changing Effects

Test , Get Data again and Compare

Problems Eliminate Or Need not Change more

Proper optimization procedure becomes

PT. HUAWEI SERVICES Huawei Confidential Page 5

Routine Daily Alarm

PT. HUAWEI SERVICES Huawei Confidential Page 6

115 kbps EDGE

PT. HUAWEI SERVICES Huawei Confidential Page 7

2G Global Network Structure

BSC PCU SGSN

3G Global Network Structure

RNC RNC SGSN

Frequency Time Spread Code

Frequency Time Frequency

(1 voice channel per user) Each Data Channel has a unique

All users transmit at the Many users share the same

PT. HUAWEI SERVICES Huawei Confidential Page 10

PT. HUAWEI SERVICES Huawei Confidential Page 11

Frequency Frequency Point

PT. HUAWEI SERVICES Huawei Confidential Page 12

Frequency Frequency Hopping

PT. HUAWEI SERVICES Huawei Confidential Page 13

Physical Channel and Logical Channel

TDMA FRAME TDMA FRAME

PT. HUAWEI SERVICES Huawei Confidential Page 14

Uplink Logical channel

Downlink Logical channel

PT. HUAWEI SERVICES Huawei Confidential Page 17

PT. HUAWEI SERVICES Huawei Confidential Page 18

Spreading Codes is also known as Channelization Codes as :

PT. HUAWEI SERVICES Huawei Confidential Page 19

1. The signal energy (pertaining, for example,

PT. HUAWEI SERVICES Huawei Confidential Page 20

Physical Channels Frames

PT. HUAWEI SERVICES Huawei Confidential Page 21

MAPPING CHANNEL (DL)

Logical Transport Physical

PT. HUAWEI SERVICES Huawei Confidential Page 22

MAPPING CHANNEL (UL)

Logical Transport Physical

CCCH RACH PRACH

DCCH CPCH PCPCH

DTCH DCH DPDCH

PT. HUAWEI SERVICES Huawei Confidential Page 23

PT. HUAWEI SERVICES Huawei Confidential Page 24

Common Transport Channels:

Dedicated Transport Channels:

Displays the RSCP_DL, Display the summary of all

Poor ECNO Good

Both are poor. Poor RSCP Poor ECNO Good

PT. HUAWEI SERVICES Huawei Confidential Page 26