00-Huawei RAN16.0 Solution Overview Draft (Beta 20140421) V2.9

www.huawei.
com
RAN16.0 Solutions Overview

HUAWEI TECHNOLOGIES CO., LTD.
Content
1
Summary of RAN16.0
RAN16 Solutions in Details
Page 2
Summary of RAN16.0
NodeB Capability Improvement
UMTS HD Voice
New BBU: BBU3910

New baseband board: UPPB d1~d6;
UL Resource POOL of 12 Cells
CE Efficiency Improvement for HSUPA
TTI 2ms
Inter-Dependence of BBU Uplink
Resource
160/192 HSPA Users per Cell
CS
Voice
Turbo
ICPrecise Power Control
Garbled Voice Detection and Correction for
TDM
AMR Services
DPCH
PO
Fast
Radio Bearer Setup
CPICH
KQI Voice
WB-AMR Enhancement
UMTS Small-Packet Storm Solution
UMTS Highly Efficient O&M Solution
Control Channel Parallel Interference
Swap Efficiency Improvement for Intra-RNC

Swap Efficiency Improvement for Inter-RNC
Automatic NodeB and Cell Allocation in the
RNC
Feature State Query and Bulk Commission
Cancellation (Phase 3)
Flexible Power Control for Uplink Low
Data Rate Transmission
Turbo IC Phase2
Load-based Intelligent State Transition
FACH POOL
Page 3
Summary of RAN16.0
UMTS RNC in Pool Solution
UMTS Big Event Solution
RNC in Pool User-Plane Load Sharing
Camping
Turbo ICStrategy Switch for Mass Event
RB
parking
TDM
DPCH P
UMTS U900&U850 Solution
UMTS SON Solution
Adaptive RACH
UMTS Uplink narrowband Interference

Detection
Interference Rejection Combining
UMTS Network Sharing Solution
UMTS HetNet Micro BTS Solution
MOCN Cell Resource Demarcation

MOCN Independent Iub Transmission
Resource Allocation
Uplink CoMP (Joint Reception)

Marco & Micro RRUs in One Cell
Macro-Micro DC-HSDPA
Service Steering and Load Sharing in
CELL_FACH State
UMTS MBB Visualization Solution
UMTS CS+PS Combined Services KPI Solution
KPI-PS
KQI APP
PS initial rate of Multi-RAB is configured

dynamically according to traffic
CS+PS MultiRAB Call Re-Establishment
Enhancement
Page 4
Summary of RAN16.0
UMTS Network KPI Improvement Solution
UMTS Service Experience Management Solution

Turbo IC
TDM
Video
Service Rate Adaption
VoIPApplication
DPCH P Management
2D Event Type Switch Triggering IFHHO and

IRAT HO
PS IRATHO Penalty Due To CS IRATHO
Preparation Failure
1X Event Optimization
SRB Rate Selection Based On Congestion and
Coverage
Call Drop Rate improve during State transition
Improve IUR Call Drop Rate by Handling CELL
UPDATE from Unknown DRNC CELL
KPI system for user in PCH_State
Paging Counter System and improving Paging
Success rate
Latency Improvement
Radio Bearer Setup message omission
Differentiated Service Based on Application

Resource Reservation
UMTS Uplink Throughput Improvement Solution

HSUPA Power Control -- Power Control Enhancement
EDPCCH Boosting
HSUPA Coverage Enhancement at UE Power Limitation
Initial HBD(Happy Bit Delay) Selection Based on Load
RSCP- and RTWP-based Adjustment of HSUPA Small Target
Retransmissions
HSUPA forcible scheduling despite of NACK messages on the
serving link
UMTS User Experience Management Solution
UMTS Downlink Throughput Improvement Solution
Terminal Black List

Differentiated Service Based on Terminal
Page 5
HSPA Serving Cell Change Optimization

HSDPA Mobility Management -- Fast HSDPA Serving
Cell Change
HSDPA Inter-Cell Power Sharing
Enhanced HSDPA Code Utilization
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Page 6
New BBU: BBU3910

CE Efficiency Improvement for HSUPA TTI 2ms
Inter-Dependence of BBU Uplink Resource
Huawei Confidential
BBU3910, Well-prepared for Future Evolution

Performance Improved
CPRI interface number tripled:
provide more CPRI interface for 4-mode co-BBU
Power Supply capacity increases 55%:

support board configuration of heavy site in the future
CPRI Interface
Number
+200%
3
6
1
2
BBU3900
Backplane switch capacity

doubled(2*5Gbps) and Full Meshed.
Power Supply
+55%
1000
W
650
W
Configuration
Simplified
Use any BBP slot for CPRI connections.

No need to adjust the BBP position in BBU
when supporting new feature(e.g. CA).
BBU3910
BBU3900
BBU3910
Huawei Confidential
Page 8
BBU 3910 Full Mesh, No More slot limitation

BBU3900
Switching Path on backplane
BBU3910
Switching Path on backplane
Slot 0
Slot 0
Slot 4
Slot 1
Slot 2
Slot 4
Slot 1
Slot 2
Slot 5
Slot 5
Slot 3
Slot 3
The same physical size as BBU3900.
Full meshed backplane. The limitation that only slot 2/3 can provide CPRI for
other slots doesnt exist any more.
Huawei Confidential
Page 9
BBU 3910 Limitations
Only U-serial Boards can be used in BBU 3910. e.g.
UBBPd1~d6.
UMPT
UCIU
Huawei Confidential
Page 10
New BBU: BBU3910

Huawei Confidential
Page 11
UBBPd, Supporting Multi-mode Concurrency in One

Board
6 kinds of UBBPd boards
Satisfy different scenario
requirements
Series
Multi-Mode
Software configurable for a

specific RAT, among GULT 4
RATs
Up to GUL 3 RATs concurrency
UBBPd
Industrys 1st GUL 3RAT concurrent BBP
Max. capacity: 1024CE(U) /
6*20M 4T4R (L) / 48TRx(G)
Powerful
Capacity
High
Integration
Huawei Confidential
Board number can be saved by

50% in typical configuration
BBU Power consumption can be
saved by 40% 50%
Page 12
Serial Universal Baseband Board

UBB
P
Single Mode
LTE FDD
LTE
TDD
Multi Mode
UMTS
GSM
GU
GL
d1
DL/UL:512CE/384CE
288 Users; 6 cells
24TRx
12TRx+
192CE
d2
DL/UL:768CE/512CE
384 User; 6cells
24TRx
12TRx+
256CE
DL/UL:512CE/384CE
288 Users; 6 cells
24TRx
12TRx+
192CE
12TRx+3*
10M 2T2R
d3
3*20M 2T2R
TH DL/UL:450/225
d4
3*20M 4T4R
TH DL/UL:600/300
3*20M
4T4R
DL/UL:768CE/512CE
384 User; 6cells
24TRx
12TRx+
256CE
12TRx+3*
10M 2T2R
d5
6*20M 2T2R
TH DL/UL:600/300
6*20M
2T2R
DL/UL:768CE/768CE
512 User; 6cells
36TRx
18TRx+
384CE
18TRx+3*
20M 4T4R
d6
6*20M 4T4R
TH DL/UL:900/450
6*20M
4T4R
DL/UL:1024CE/1024CE
768 User; 12cells
48TR
X
24TRx+
512CE
24TRx+3*
20M 4T4R
UL
GUL
512CE+3*
20M 4T4R
12TRx+256CE
+3*20M 4T4R
UBBP is the only baseband board which can work in the new BBU( BBU3910)
Huawei Confidential
Page 13
Appearance of UBBP
Identifier
Connector
CPRI0 to CPRI5
SFP female
(9.8Gbps)
HEI
QSFP
(2*6.25G)
Quantity Description
6
Data transmission ports that interconnect the

BBU and the RF modules. These ports support
electrical and optical signal input and output.
Provides a port for interconnection with another

baseband board (via UCIU in Cloud BB
solution)to share the baseband resources.
Huawei Confidential
Page 14
New BBU: BBU3910

UL Resource POOL of 12 Cells IntFD-160007
Huawei Confidential
Page 15
Background
In the typical scenarios of 3 or 4 carriers plus 3 sectors, 9 or 12 cells will be configured in
one NodeB
Before R16.0
The baseboard of UMTS NodeB before R16.0 only support UL resource Pool of 6 cells so
the cells of NodeB will be partitioned into many resource groups, and the CE resources can
not be shared between these groups( Inter-Dependence of BBU Uplink Resource WRFD151210 can only come to the limited share between groups, not full share )
From R16.0
UBBPd board can handle demodulation and decode of 12 cells with 2 Rx antennas .
If all the boards of a UL resource group are UBBPd boards ,this group support UL resource of
12 cells , so CE resources can be fully shared between these 12 cells.
If the UL resource group is composed of UBBPd board and other boards ,since other boards
only support UL resource Pool of 6 cells, so this group only support UL resource Pool of 6
cells
Huawei Confidential
Page 16
Impact and Dependency
Benefit
Dependency on features
If the UBBPd and WBBP board are mixed in one UL resource group, the feature Inter-Dependence of BBU Uplink
Resource WRFD-151210 is recommended be activated to improve the resource share capability.
Dependency on Hardware
None
Impacted on Features
None
Mutually Exclusive Features
The utilization efficiency of UL CE will be improved .

The admission rejection due to UL CE resource congestion will be reduced, and the access successful rate will be
improved(Such as RRC & RAB setup successful rate) .
Depends on UBBPd board
License
None
Huawei Confidential
Page 17
New BBU: BBU3910

CE Efficiency Improvement for HSUPA TTI 2ms WRFD-160205
Huawei Confidential
Page 18
Background
Before R10
R10
Dynamic CE
management
R14 CE
overbooking
R16 CE
efficiency
improvement
for 2ms
Admission CE
calculation
for 2ms TTI
Based on MBR
Based on
max{GBR,
OneRlcPdu}
Based on actual
rate
Based on rate for

single HARQ
OneRlcPdu
Admission CE
consumption
for 2ms TTI
>=8
>=8
>=2
Version and
feature
CE
consumpti
on with
feature
Inactive
HARQ processes
OneRlcPdu
(320bit)
CE
consumpti
on without
feature
Harq average
rate: 20kbps
CE
CE admission
admission control
control
rejected
rejected
RAN12
RAN14
RAN16
Each 2 ms HSUPA only consumes 1 CE based on the Single HARQ

Huawei Confidential
Improvement
Improvement
on
on HW
HW and
and SW
SW
admitted
admitted
Total
Total 88 CE
CE is
is configured
configured
Page 19
Average CE
Average CE
consumption:
consumption:
1.875 2
1.875 2
Average CE
Average CE
consumption: 1
consumption: 1
Impact Analysis
Benefits
CE congestion is reduced
The CE efficiency is improved and leads to less CE
congestion.
More HSUPA UEs stay on 2ms
More 2ms UEs can be admitted, and the probability
of admission-CE-based dynamic TTI adjustment
from 2 ms to 10 ms HSUPA is reduced. More HSUPA
UEs can stay on the 2ms state
Benefit on KPI
The probability of admission-CE-based dynamic
TTI adjustment from 2 ms to 10 ms HSUPA is
reduced , so the RB Reconfiguration is less ,which
has benefit on KPI .
2ms HSUPA
turns to 10ms
Admission CE
consumption
HUSPA user
number
Without
Overbooking
Before R14
With
Overbooking
R14
With CE efficiency
improvement
R16
Negative Impact
When lots of UE are admitted, average CE allocated for each user is decreased and HSUPA 2ms TTI users
may be configured to single HARQ state, peak rate and QoS could decrease .
Huawei Confidential
Page 20
Dependency
Dependency on other Features
Depended on UBBPd or WBBPf

RAN11.0 WRFD-010638 Dynamic CE Resource Management
RAN14.0 WRFD-140212 CE Overbooking
WRFD-160213 Turbo IC Phase 2

No impact : The causes to trigger single HARQ are different between this feature (based on CE ) and
WRFD-160213 (based on RTWP) ,and they have no impact on each other.
Dependency on NE
None
License
An optional feature with new license on NodeB to control
Huawei Confidential
Page 21
Verification
Availability Observation
VS.HSUPA.AlltoSingleHARQNum.CECong will be pegged after feature activation.
Gain Observation
VS.HSUPA.RAB.FailEstab.ULCE.Cong
Credit resource congestion may decrease.
VS.HSUPA.UE.Mean.TTI2ms
The number of 2ms TTI HSUPA UEs may increase.
VS.NodeB.ULCreditUsed.Mean
Admission UL credit consumption may decrease.
VS.LC.ULMean.LicenseGroup
Actual used UL CE consumption may decreased.
Huawei Confidential
Page 22
New BBU: BBU3910

Inter-Dependence of BBU Uplink Resource WRFD-151210
Huawei Confidential
Page 23
Introduction
Original Configuration
F1
WBBP0
F3
Optimized Configuration
WBBP0
F2
F4
F
2
WBBP1
F4
Uplink resource group can support less
than 6 cells.
Resource unbalance between different
Uplink resource groups.
WBBP1
WBBP2
WBBP3
F4
F
1
WBBP0
F1
WBBP1
F2
WBBP2
F
3
F3
Uplink resource group can support more than 6 cells.

Improve uplink CE usage.
The Inter-Dependence of BBU Uplink Resource feature groups the intra-frequency
cells and deploys the cell groups as a chain on the baseband equipment. In this way,
any two cell groups on the chain can share some CEs.
Huawei Confidential
Page 24
Impact
Benefits
The Inter-Dependence of BBU Uplink Resource feature increases the uplink CE utilization and radio
access success rate. How much this feature affects system capacity depends on the number of
baseband boards in a resource group, number of carriers, and number of uplink CEs required by
carriers, and therefore cannot be quantified.
Network Impact
System capacity
The Inter-Dependence of BBU Uplink Resource feature allows cells to share CEs to increase
uplink CE utilization.
Network performance
The Inter-Dependence of BBU Uplink Resource feature increases the radio access success rate
when the system rejects UE access attempts due to uplink CE congestion.
Huawei Confidential
Page 25
Dependency
Dependency Features
None
WRFD-021308 Extended Cell Coverage up to 200km
The Inter-Dependence of BBU Uplink Resource feature is mutually exclusive with the Extended Cell Coverage up to 200km feature.
If remote cells are configured by adding remote cell groups or changing the cell radius to more than 30 km, Inter-Dependence of
BBU Uplink Resource will fail to take effect.
WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell

WRFD-151208 Static Desensitization Based Multi RRUs in One Cell
Impacted Features
WRFD-010209 4-Antenna Receive Diversity
WRFD-020103 Inter Frequency Load Balance
If the 4-Antenna Receive Diversity feature is activated, Inter-Dependence of BBU Uplink Resource will not improve CE utilization.
This is because only three cells can be set up on a baseband board if 4-Antenna Receive Diversity is activated and the cells cannot
be deployed in chain mode.
After Inter-Dependence of BBU Uplink Resource is activated, the cell group-level credit reshuffling algorithm in the Inter Frequency
Load Balance feature will fail.
Dependencies on Hardware
The WBBPa board does not support Inter-Dependence of BBU Uplink Resource.
Dependencies on NEs
None
License
A license control item has been added in NodeB for this feature.
Huawei Confidential
Page 26
New BBU: BBU3910

160/192 HSPA Users per Cell WRFD-160208 WRFD-160209
Huawei Confidential
Page 27

Background
With the increasing penetration rate of smartphones, more and more services are expected. This
increases the number of online connections. In addition, online users expect to use the HSPA
technology to obtain better experience. For telecom operators, they expect more users to use the
HSPA technology as the service bearer instead of R99 (DCH), thereby improving the system
capacity and efficiency.
Introduction
140
This feature is implemented on NodeBs and RNCs.A maximum 120
100
60
HSPA
connection
number
users can only use R99 (DCH) as the bearer due to the HSPA
40
R99(DCH)
connection limitation although service requirements are met.
20
of 128 HSPA users are allowed in the existing single cell.

When the number of HSPA users in the cell exceeds 128, extra
80
0
0
Huawei Confidential
50 connection
100
150
200
RL
number
Page 28
250
Impact
Feature Benefits
This feature allows more users to use HSPA as the bear and improves user experience .
Network Impacts
Impacts on System Capacity
More users are allowed to use HSPA, the HSPA service volume is increased, and the R99(DCH)
service volume is decreased.
Impacts on Network Performance
The number of online HSUPA users is increased, thereby increasing the uplink CE consumption.
The load overhead of online users' control channels is increased .
Huawei Confidential
Page 29
Dependency
Dependency Feature
UBBPd
NE Dependency
Be advised to use this feature with WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA and
WRFD 010686 CPC-DTX/DRX. When CEs are insufficient, you are advised to use this feature with WRFD-140212 CE
Overbooking.
Hardware Dependency
None
Impacted Features
WRFD-160208 160 HSPA Users per Cell
WRFD-010670 128 HSUPA Users per Cell
WRFD-010654 128 HSDPA Users per Cell
WRFD-010652 SRB over HSDPA
Mutually-exclusive Features
Only 3900 series base stations (except for BTS3902E) support this feature.
License Planning
This feature has introduced new license items on RNCs for cell-level function control.
Huawei Confidential
Page 30
Performance Monitoring
No traffic statistics counters are added.
WRFD-160208 160 HSPA Users per Cell / WRFD-160209 192 HSPA Users per Cell
Monitor the number of HSPA users in the cell.
Enable the "cell user number" detection item in "cell performance detection" on the RNC LMT.
View the maximum HSDPA user number through the performance statistics counter VS.HSDPA.UE.Max.Cell and view the
maximum HSUPA user number through the performance statistics counter VS.HSUPA.UE.Max.Cell on the U2000.
Monitor the impacts on capacity.
VS.MeanRTWP(dBm). When the value of VS.HSUPA.UE.Mean.Cell is increased, the capacity will be decreased and the value of
VS.MeanRTWP will be increased. If WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA is activated, the
uplink capacity of HSUPA cells can be improved with the load being limited.
Monitor CE consumption.
VS.LC.ULCreditUsed.Mean. When the value of VS.HSUPA.UE.Mean.Cell is increased, the CE consumption will be increased. If WRFD140212 CE Overbooking is activated, the admitted CE congestion can be relieved with insufficient CEs.
Monitor network KPIs related to call drop and access.
With the increase of the VS.MeanRTWP value, call drop-related and access-related KPIs gradually deteriorate. If the RTWP can be
decreased by activating the recommended feature, network KPIs can be improved.
Huawei Confidential
Page 31
Content
1
Summary of RAN16.0

UMTS HD Voice


UMTS SON Solution

Huawei Confidential
Page 32
UMTS HD Voice
CS Voice Precise Power Control WRFD-160204
Garbled Voice Detection and Correction for AMR Services
Fast Radio Bearer Setup
KQI Voice Counters
AMR/WB-AMR Speech Rates Control Enhancement
Huawei Confidential
Page 33
Background
Traditional Power Control before R16:

BLER based outer loop power control allow
the target SIR to rise sharply once the CRC
CS Voice Precise Power Control is introduced

in R16:
BLER-BER based outer loop power control can react more quickly
check of AMR frame is incorrect, and slowly
as the channel condition changed and SIR-target will be
decline if the CRC check is correct .
adjusted in time before speech frame loss , then the MOS of AMR
can be increased.
MOS (mean
Huawei Confidential
opinion score)Page
of 34
AMR is improved 0.05~0.1.
Introduction
The feature gets more accurate power control with the following ways:
Outer Loop optimization (More Precise control)
BLER->BER->SIRtarget
DTX Power Control
Inner Loop optimization (Higher receive capability)
Searching optimization (Depends on UBBP in NodeB )
SIR estimator optimization (Depends on WBBPf in NodeB)
This feature can works on all kinds of AMR/WB-AMR rate, and it also works on AMR+PS R99/HSPA
Huawei Confidential
Page 35
Impact & Dependency
Benefit
MOS (mean opinion score) of AMR voice is improved 0.05~0.1 in normal scenario , or increase voice
capacity 5%~10% in the capacity limited scenario .
In lab test , MOS is increased as below single user :
Case
Performance
Gain
AMR 12.2k
MOS
0.05~0.1
AMR+R99 8k
MOS
0.1~0.15
In lab test, with same BLER, UE transmit power decrease about 0.5dB single user , so voice capacity may
increase 5%~10%
Impacts on other Features or KPI
None
Dependency
For Inner Loop optimization, Searching optimization depends on UBBP board, and SIR estimator optimization depends on WBBPf
board. If there is no UBBP or WBBPF broad, only Outer Loop optimization is available ,and only 50% feature gain will be get.
License
A new
license is introduced
in RNC level.
HUAWEI
TECHNOLOGIES
CO., LTD.
Huawei Confidential
Page 36
Verification
Availability observation
If these counters are not 0, then this feature takes effect for the corresponding service.
Name
Description
VS.SingleRAB.CSVoicePPC.CSVoiceFram Total voice frame number where CS Voice Precise Power Control takes effect for
single CS service
es
Gain
Total voice frame number where CS Voice Precise Power Control takes effect for
VS.MultiRAB.CSVoicePPC.CSVoiceFrame
observation
multi-RAB service
s RNC counters
Counters
Description
VS.EVQI.AMRNB.UL.TotalValue VS.EVQI.AMRWB.UL.TotalValu
e
VS.EVQI.AMRNB.UL.Excellent.Num VS.EVQI.AMRWB.UL.Exce
llent.Num
VS.EVQI.AMRNB.UL.Good.Num VS.EVQI.AMRWB.UL.Good.Nu
m
VS.EVQI.AMRNB.UL.Accept.Num VS.EVQI.AMRWB.UL.Accept
.Num
VS.EVQI.AMRNB.UL.Poor.Num VS.EVQI.AMRWB.UL.Poor.Num
VS.EVQI.AMRNB.UL.Bad.Num VS.EVQI.AMRWB.UL.Bad.Num
Expected gain
Uplink average EVQI for AMR-NB or AMR-WB

Number of
AMR-WB
Number of
WB
Number of
WB
Number of
WB
Number of
WB
uplink excellent EVQI for AMR-NB or
Average EQI improve

0.05~0.1
Improve 5%~10%
uplink good EVQI for AMR-NB or AMR-
Improve 5%~10%
uplink accept EVQI for AMR-NB or AMR- Decrease 5%~10%

uplink bad EVQI for AMR-NB or AMR-
Decrease 5%~10%
uplink poor EVQI for AMR-NB or AMR-
Decrease 5%~10%
Huawei Confidential
Page 37
UMTS HD Voice
CS Voice Precise Power Control
Garbled Voice Detection and Correction for AMR

Services WRFD-160102
KQI Voice Counters
Huawei Confidential
Page 38
Background
Garbled Voices in 22% of Voice Quality
Complaints
This feature has the following functions:

Garbled voice detection and correction for uplink AMR-NB services
Garbled voice detection and correction for uplink AMR-WB services
Garbled voice detection for downlink AMR-NB services
Garbled voice detection for downlink AMR-WB services
User Complaint distribution
If the encryption & decryption parameters are different

between RNC and UE during the procedures which involves
UL AMR
Frame
encryption process ,such as AMR Setup Cell Update and

Hard handover , the voice frame will be deciphered in error.
DL Garble
Noise
Detection
UL Garble
Noise
Detection and
Correction
RNC
1
CN
UE1
the experience of users.

Huawei Confidential
RNC2
UE2
This issue will introduce the garbled voice and deteriorate
DL AMR
Frame
Page 39
Impact
Benefits
This feature can improve the efficiency to fix the garbled voice problems ,and improve the operation
and maintenance capability on Voice problems.
System Capacity Impact:

Garbled voice detection will increase CPU usage on user-plane board in RNC
Uplink garbled voice detection : the impact on CPU usage can be ignored.
Downlink garbled voice detection: the CPU usage may increase 10% at most .
Two ways are provided to alleviate CPU usage:
~ Operator can configure less ratio of the downlink garbled voice detection
~ Operator can configure less threshold to trigger the CPU usage alarm of user-plane board . If this alarm is
triggered , new AMR service will not be detected.
License:
This is an basic feature without License control
Huawei Confidential
Page 40
Verification
Availability and Benefit observation
Counter
Description
VS.AMRNB.ULGarbledVoice.Num
Number of garbled voices in uplink AMR-NB services in a cell
VS.AMRNB.DLGarbledVoice.Num
Number of garbled voices in downlink AMR-NB services in a cell
VS.AMRNB.ULGarbledVoiceCorrect.Num
Number of successful garbled voices corrections in uplink AMR-NB

services in a cell
VS.AMRWB.ULGarbledVoice.Num
Number of garbled voices in uplink AMR-WB services in a cell
VS.AMRWB.DLGarbledVoice.Num
Number of garbled voices in downlink AMR-WB services in a cell
VS.AMRWB.ULGarbledVoiceCorrect.Num
Number of successful garbled voices corrections in uplink AMR-WB

services in a cell
Huawei Confidential
Page 41
UMTS HD Voice
Fast Radio Bearer Setup WRFD-160106
KQI Voice Counters
Huawei Confidential
Page 42
Background
Traditional RB setup use the

synchronized way ,which let the RNC
NodeB and UE activate the new channel
configuration at the same time .Normally ,
the activation latency need about 400ms
to ensure the RNC NodeB and UE to
finish the new configuration preparation
Setup Time saving:

300ms
Double resources are

reversed for both old
and new channels
Unsynchronized RB setup procedure let

UE activate the new channel configuration
once receives the Radio Bear Setupfrom
RNC . NodeB will also remove the old
configuration after it detect the UE on the
new configuration.
RB Setup latency will be saved about 300ms

Huawei Confidential
Page 43
Impact
Benefit
RB Setup latency will be saved about 300ms
Impact Analysis
Double resource consumption:
The system resource consumption Such as CE /Code User

CNBAP rise because both old and new channels need these resource
during unsynchronized setup period
The following way is provided to alleviate congestion:
When cell is in the LDR state , unsynchronized setup will not be applied automatically and
be in place of traditional synchronized RB setup.
Huawei Confidential
Page 44
Dependency
Mutually Exclusive & Impacted Features
None
1. BTS3812E\BTS3812A\BTS3812AE\DBS3800 dont support
2. BTS3900\BTS3900A\BTS3900C\BTS3900L\BTS3900A\DBS3900 with WBBPa dont support
Dependencies on UEs
Some UEs may have the compatibility risk ,and this feature can be set with black list to avoid
this risk.
License
This is an basic feature in R16 and is not license controlled.
Huawei Confidential
Page 45
Verification
Availability observation
Counter Name
Description
VS.RAB.AttEstabCS.FastSetup
Counts the number of single CS RAB establish with fast setup feature
VS.RAB.SuccEstabCS.FastSetup
Counts the number of successful single CS RAB establish with fast setup feature
VS.RAB.AttEstabPS.FastSetup
Counts the number of single PS RAB establish with fast setup feature
VS.RAB.SuccEstabPS.FastSetup
Counts the number of successful single PS RAB establish with fast setup feature
VS.MultiRAB.AttEstabCS.FastSetup
Counts the number of Multi-CS RAB establish with fast setup feature based on
PS traffic exists
VS.MultiRAB.SuccEstabCS.FastSetup
Counts the number of successful Multi-CS RAB establish with fast setup feature
based on PS traffic exists
Huawei Confidential
Page 46
UMTS HD Voice
KQI Voice Counters IntFD-160004
Huawei Confidential
Page 47
Background
Before R16
Conventional key performance indicators (KPIs) cannot truly reflect user experience.
Drive test results can truly reflect user experience, but only on test route and time period. In
addition, drive testing is costly.
Third-party assessment requires a large investment.
From R16
The Key Quality Indicator (KQI) Voice counters can assess the experience of users performing
voice services with low cost and easy operation.
KQI Voice uses traffic measurement counters to from the following aspects: Accessibility,
Integrity, and Retainability.
Accessibility : indicates whether the call can be put through
Integrity : indicates whether the user's voices can be clearly heard during the call
Retainability : indicates whether the RRC connection is abnormally released
Huawei Confidential
Page 48
Accessibility
The voice call setup successful rate

Counter
Description
VS.Orig.CS.AttEstab.Idle.AMR
The attempt numbers of Original voice calls from idle state in a cell
VS.Orig.CS.AttEstab.DCH.AMR
The attempt numbers of Original voice calls from DCH state in a cell
VS.Orig.CS.AttEstab.FACH.AMR
The attempt numbers of Original voice calls from FACH state in a cell
VS.Orig.CS.AttEstab.PCH.AMR
The attempt numbers of Original voice calls from PCH state in a cell
VS.Orig.CS.AttEstab.CSFB.AMR
The attempt numbers of Original voice calls caused by CSFB in a cell
VS.Orig.CS.SuccEstab.Idle.AMR
The numbers of Original voice calls with successful Alerting from idle state
in a cell
VS.Orig.CS.SuccEstab.FACH.AMR
The numbers of Original voice calls with successful Alerting from FACH state
in a cell
VS.Orig.CS.SuccEstab.DCH.AMR
The numbers of Original voice calls with successful Alerting from DCH state
in a cell
VS.Orig.CS.SuccEstab.PCH.AMR
The numbers of Original voice calls with successful Alerting from PCH state
in a cell

VS.Orig.CS.SuccEstab.CSFB.AMR
Huawei
Confidential
Page 49
The numbers
of Original
voice calls with successful
Alerting caused by
Accessibility
The voice call setup successful rate (Cont.)

Counter
Description
VS.Term.CS.AttEstab.Idle.AMR
The attempt numbers of Terminal voice calls from idle state in a cell
VS.Term.CS.AttEstab.DCH.AMR
The attempt numbers of Terminal voice calls from DCH state in a cell
VS.Term.CS.AttEstab.FACH.AMR
The attempt numbers of Terminal voice calls from FACH state in a cell
VS.Term.CS.AttEstab.PCH.AMR
The attempt numbers of Terminal voice calls from PCH state in a cell
VS.Term.CS.AttEstab.CSFB.AMR
The attempt numbers of Terminal voice calls caused by CSFB in a cell
VS.Term.CS.SuccEstab.Idle.AMR
The numbers of Terminal voice calls with successful Alerting from idle
state in a cell
VS.Term.CS.SuccEstab.FACH.AMR
The numbers of Terminalvoice calls with successful Alerting from FACH

state in a cell
VS.Term.CS.SuccEstab.DCH.AMR
The numbers of Terminalvoice calls with successful Alerting from DCH

state in a cell
VS.Term.CS.SuccEstab.PCH.AMR
The numbers of Terminal voice calls with successful Alerting from PCH
state in a cell
VS.Term.CS.SuccEstab.CSFB.AMR
HUAWEI
TECHNOLOGIES CO., LTD.
The numbers
Terminal voice calls with successful
Alerting caused by
Huawei of
Confidential
Page 50
CSFB in a cell
Accessibility
The voice call access latency

Counter
Description
VS.Orig.CS.Estab.Idle.MeanTime.AMRNB
The mean latency of successful Original voice calls (AMR-NB) access from
idle state in a cell
VS.Orig.CS.Estab.DCH.MeanTime.AMRNB The mean latency of successful Original voice calls
(AMR-NB) access from
VS.Orig.CS.Estab.FACH.MeanTime.AMRNB The mean latency of successful Original voice calls
(AMR-NB) access from
DCH state in a cell
FACH state in a cell
VS.Orig.CS.Estab.PCH.MeanTime.AMRNB
The mean latency of successful Original voice calls (AMR-NB) access from
PCH state in a cell
VS.Orig.CS.Estab.CSFB.MeanTime.AMRNB The mean latency of successful Original voice calls
(AMR-NB) access
caused by CSFB in a cell

VS.Orig.CS.Estab.MeanTime.AMRNB
The mean latency of successful Original voice calls (AMR-NB) access
VS.Orig.CS.Estab.Idle.MeanTime.AMRWB
The mean latency of successful Original voice calls (AMR-WB) access from
idle state in a cell
VS.Orig.CS.Estab.DCH.MeanTime.AMRWB The mean latency of successful Original voice calls
DCH state in a cell
(AMR-WB) access from
VS.Orig.CS.Estab.FACH.MeanTime.AMRW
B
The mean latency of successful Original voice calls (AMR-WB) access from
FACH state in a cell
HUAWEI
TECHNOLOGIES CO., LTD.
VS.Orig.CS.Estab.PCH.MeanTime.AMRWB
Huawei
Confidential
Page
51
The mean
latency
of successful Original voice
calls
(AMR-WB) access from
Accessibility
The voice call access latency (Cont.)

Counter
VS.Orig.CS.Estab.Delay.Good.Num.AMRNB
Description
The numbers of Good of successful Original voice calls (AMR-NB)
access in a cell
VS.Orig.CS.Estab.Delay.Accept.Num.AMRN The numbers of Accept of successful Original voice calls

B
access in a cell
(AMR-NB)
VS.Orig.CS.Estab.Delay.Bad.Num.AMRNB
The numbers of Bad of successful Original voice calls (AMR-NB) access

in a cell
VS.Orig.CS.Estab.Delay.Good.Num.AMRWB
The numbers of Good of successful Original voice calls (AMR-WB)

access in a cell
VS.Orig.CS.Estab.Delay.Accept.Num.AMRW The numbers of Accept of successful Original voice calls

B
access in a cell
VS.Orig.CS.Estab.Delay.Bad.Num.AMRWB
(AMR-WB)
The numbers of Bad of successful Original voice calls (AMR-WB) access

in a cell
Huawei Confidential
Page 52
Integrity
EVQI (Enhanced VQI):
Base on ITU-T P.863, and be suitable for both of AMR-NB and AMR-WB
The traditional VQI ( Base on ITU-T P.862 ,and be out of date) is suitable for AMR-NB, but not suitable
for AMR-WB
To be suitable for AMR-WB, EVQI introduces different estimation standard and the data result is
different with VQI . For the same AMR-NB rate ,the EVQI result is less than VQI. Please refer to the
below chart.
The EVQI class range is also [0,5], as the same range of MOS [0,5].
CLASS
RANGE
USER
EXPERIENCE
Excellen
t
EVQI > 4.0
Good
4.0 EVQI >

3.0
Users satisfied
Accept
3.0 EVQI >

2.0
Some users dissatisfied
Poor
2.0 EVQI >

1.0
Many users dissatisfied
Bad
Huawei Confidential
1.0 EVQI
Users very satisfied
Nearly all users

Page 53
dissatisfied
Integrity
AMR NB
Counter (UL)
Description
Counter(DL)
VS.EVQI.AMRNB.UL.Tot
alValue
Total summary of UL EVQI

for AMR-NB services
VS.EVQI.AMRNB.DL.TotalValue
Total summary of DL EVQI for

AMR-NB services
VS.EVQI.AMRNB.UL.Ex
cellent.Num
Number of UL EVQI is
Excellent for AMR-NB
services
VS.EVQI.AMRNB.DL.Excellent.
Num
Number of DL EVQI is Excellent

for AMR-NB services
VS.EVQI.AMRNB.UL.Go
od.Num
Good for AMR-NB services
VS.EVQI.AMRNB.DL.Good.Nu
m
Number of DL EVQI is Good for

AMR-NB services
VS.EVQI.AMRNB.UL.Ac
cept.Num
Accept for AMR-NB
services
VS.EVQI.AMRNB.DL.Accept.Nu
m
Number of DL EVQI is Accept

for AMR-NB services
VS.EVQI.AMRNB.UL.Po
or.Num
Number of UL EVQI is Poor

for AMR-NB services
VS.EVQI.AMRNB.DL.Poor.Num
Number of DL EVQI is Poor for

AMR-NB services
VS.EVQI.AMRNB.UL.Ba
d.Num
Number of UL EVQI is Bad

for AMR-NB services
VS.EVQI.AMRNB.DL.Bad.Num
Number of DL EVQI is Bad for

AMR-NB services
Huawei Confidential
Description
Page 54
Integrity
AMR WB
Counter (UL)
Description
Counter(DL)
Description
VS.EVQI.AMRWB.UL.TotalValue
Total summary of UL
EVQI for AMR-WB
services
VS.EVQI.AMRWB.DL.TotalValu
e
Total summary of DL
EVQI for AMR-WB
services
VS.EVQI.AMRWB.UL.Excellent.
Num
Excellent for AMR-WB
services
VS.EVQI.AMRWB.DL.Excellent.
Num
Number of DL EVQI is
Excellent for AMR-WB
services
VS.EVQI.AMRWB.UL.Good.Num
Good for AMR-WB
services
VS.EVQI.AMRWB.DL.Good.Nu
m
Good for AMR-WB
services
VS.EVQI.AMRWB.UL.Accept.Nu
m
Accept for AMR-WB
services
VS.EVQI.AMRWB.DL.Accept.N
um
Accept for AMR-WB
services
VS.EVQI.AMRWB.UL.Poor.Num
Poor for AMR-WB
services
VS.EVQI.AMRWB.DL.Poor.Num
Poor for AMR-WB
services
VS.EVQI.AMRWB.DL.Bad.Num Number of DL EVQI is

Bad for AMR-WB
Bad for AMR-WB
Huawei Confidential
Page
55
services
services
VS.EVQI.AMRWB.UL.Bad.Num
Integrity
AMR NB and WB silence statistics
Counter
Description
VS.AMRNB.ULSilent.Num
The numbers of silence of uplink voice call (AMR-NB)
VS.AMRNB.DLSilent.Num
The numbers of silence of downlink voice call (AMR-NB)
VS.AMRWB.ULSilent.Num
VS.AMRWB.DLSilent.Num
The numbers of silence of uplink voice call (AMR-WB)

The numbers of silence of downlink voice call (AMR-WB)
Huawei Confidential
Page 56
Retainability
Counter
Description
VS.RAB.Rel.AMRNB.CN
The numbers of abnormal voice call (AMR-NB) release from CN
VS.RAB.Rel.AMRNB.BadQuality
The numbers of normal voice call(AMR-NB) release but with bad voice
quality before the release
VS.RAB.Rel.AMRWB.CN
The numbers of abnormal voice call (AMR-WB) release from CN
VS.RAB.Rel.AMRWB.BadQuality
The numbers of normal voice call(AMR-WB) release but with bad voice
quality before the release
Huawei Confidential
Page 57
Benefit
Real-time accurate and low-cost evaluation for voice quality.

Truly reflect the voice user experience to guide the network optimization
Negative impact
In the integrity part ,the DL EVQI is based on DL BLER of Measurement Report(MR), which will
increase CPU usage of the SPU board.
Mutually Exclusive or Impacted Features
None
To reduce the impact of CPU usage , operator can decrease the DL EVQI measurements . For example
,if only the DL BLER is reported and the report period is set to 2s ,the impact on CPU usage can be
downgrade to 1%. Moreover ,if the report period is set to 6s, this impact on CPU could be ignored.
None
License
Basic function without License control.
Huawei Confidential
Page 58
UMTS HD Voice
KQI Voice Counters
AMR/WB-AMR Speech Rates Control Enhancement WRFD020701
Huawei Confidential
Page 59
Background
AMR-WB can improve the voice experience ,but will cost more resource to bring negative impact on
coverage and capacity .
This feature enhancement will optimize AMR-WB performance and resolve the coverage and capacity
problems of AMR-WB.
Sub Function
Benefit
The max downlink transmission power of

AMR-WB 23.85kbps will be increased 3dB .
Improve the downlink coverage of AMR-WB 23.85kbps to be as

same as AMR 12.2Kbps.
The AMR-WB can be downgraded by RB

reconfiguration to larger SF code in the scene
of SF congestion
Resolve the problem of too much consumption of SF code introduced

by AMR-WB ,such as 23.85k bps and this issue may have
negative impact on HSDPA throughput before .
The AMR-WB in the combined service can

be downgraded in the scene of downlink
power congestion
Resolve the problem of downlink capacity decrease introduced from

AMR-WB in the combined service
The AMR-WB in the combined service can

be downgraded based on the stability of uplink
link.
Improve the uplink coverage of AMR-WB ,and decrease the call drop
caused by limitation of uplink power of AMR-WB.
Forbid the static relocation between AMR-WB

and AMR-NB and keep the soft handover state
Avoid the call drop caused by relocation failure .
Huawei Confidential
60
Impact
Benefit
Improve the downlink coverage of AMR-WB
Decrease the possibility of SF code or downlink power congestion or caused

by AMR-WB
Decrease the call drop caused by limitation of uplink power of AMR-WB
Negative impact
The RB reconfiguration will be more than before since the SF change in the scene of code
congestion , which may increase the risk of call drop
Huawei Confidential
61
Dependency
Mutually Exclusive & Impacted Features
None
Dependencies on other NEs
None
WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band)
The CN should support AMR-WB
License
This is an enhancement of WRFD-020701 AMR/WB-AMR Speech Rates Control, and no

new license control is introduced in R16.
Huawei Confidential
62
Verification
Availability
observation
Counter
Description
VS.RAB.SuccEstabCS.AMRWBXX The times for successful AMR-WB RAB establishment with the rate
XX
of XXXX kbps in a cell.
VS.RB.AMRWB.DL.XXXX
The average user number of the AMR-WB with the downlink rate of
XXXXbps in a cell.
VS.RB.AMRWB.UL.XXXX
VS.AMRWB.DLRateUp
VS.AMRWB.DLRateDown
VS.AMRWB.ULRateUp
VS.AMRWB.ULRateDown
The average user number of the AMR-WB with the uplink rate of
XXXXbps in a cell.
The upgrade times of downlink rate of AMR-WB in a cell.
The downgrade times of downlink rate of AMR-WB in a cell.
The upgrade times of uplink rate of AMR-WB in a cell.
The downgrade times of uplink rate of AMR-WB in a cell.
Huawei Confidential
63
Content
1
Summary of RAN16.0

UMTS HD Voice


UMTS SON Solution

Huawei Confidential
Page 64
Control Channel Parallel Interference Cancellation (Phase 3)

WRFD-160201
Flexible Power Control for Uplink Low Data Rate Transmission
Turbo IC Phase2
FACH POOL
RTWP Control Optimization
Huawei Confidential
Page 65
Background
WCDMA Uplink Capacity: Uplink signals from different UEs are not orthogonal.
UMTS uplink capacity is limited by the multi-access interference (MAI) of UEs inside and interference
from outside system.
Interference cancellation (IC) reduces or eliminates

interference between UEs to effectively improve UE
receive performance, which is an effective method to
improve uplink capacity.
CCPIC
Target:
DPCCH
CCPIC
HSUPA UL
IC
Target: EDPDCH
CCPIC
HSUPA UL IC
CCPIC
PHASE2
Target:
DPCCH
CCPIC
HSUPA UL IC
CCPIC
PHASE2
Turbo IC
Target: EDPDCH
CCPIC
HSUPA UL IC
CCPIC PHASE2
Turbo IC
CCPIC PHASE3
Target:
E-DPCCH
HS-DPCCH
A large of User results in

higher interference to other
UEs.
RAN10
RAN12
Huawei Confidential
RAN14
RAN15
Page 66
RAN16
(Control Channel Parallel Interference Cancellation)
Interference
cancelled by
CCPIC Phase 2
Interference
cancelled by
CCPIC Phase
3
AMR Traffic Load
9%
40%
29%
18%
4%
HS-DPCCH Load
PS R99 Traffic Load
E-DPCCH&EDPDCH Load
UL DPCCH Load
Connection No. gain
Background-CCPIC
Phase 1
DPCCH IC
in 1 baseband board
Phase 2
Phase 3
DPCCH IC
in the
whole cell
HS-DPCCH & EDPCCH IC in the

whole cell
+15%
+20%
18%
Phase 1
Phase 2
Phase 3
E-DPCCH
Cancelled by
CCPIC phase3
Huawei Confidential
Page 67
Impact
Benefit
CCPIC PHASE3 can increase the uplink capacity for a cell when the EDPCCH and HSDPCCH load is high, and bring the increase of uplink throughput or connected user
numbers
2ms Burst Traffic Model Simulation Result
2ms Full Buffer Traffic Model Simulation Result
30%
25%
CQI feedback= 8ms

CQI feedback= 2ms
18.7%
14.5%
15%
10.5%
Connected Num Gain
25%
20%
20%
15%
AWGN
11.0%
PB3
Gain
10%
10%
5%
Scenario: single cell 2ANtennas UBBPd CQI

feedback =2ms 1s ping1500 HARQ PO=0dB
Scenario: single cell,2 Antennas, UBBPd, ROT=6,

AWGN
Throughput Gain
29.5%
5.0%
5%
0%
4
-5%
User Number
12
0%
50%
Huawei Confidential
55%
60%
Page 68
65%
Load
70%
75%
80%
Dependency
Only 3900 series NodeBs (except 3902E) support CCPIC PHASE3;

Only UBBPd board support CCPIC PHASE3;
Depended on WRFD-140202 CCPIC PHASE2
License
Introduce a new license on NodeB
Huawei Confidential
Page 69
Dependency
None
Impacted Features
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period
This feature will decrease the HS-DPCCH power ,which make the interference margin from
HSDPCCH is reduced ,and the gain of CCPIC Phase3 will be less.
WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA
This feature will decrease the E-DPCCH power ,which make the interference margin from EDPCCH
is reduced ,and the gain of CCPIC Phase3 will be less.
WRFD-010641 HSUPA Adaptive Transmission
This feature will decrease the HSDPCCH and E-DPCCH power ,which make the interference margin
is reduced ,and the gain of CCPIC Phase3 will be less.
WRFD-160202 Flexible Power Control for Uplink Low Data Rate Transmission
This feature will decrease the HSDPCCH power ,which make the interference margin from
HSDPCCH is reduced ,and the gain of CCPIC Phase3 will be less.
Huawei Confidential
Page 70
Verification
Availability
If the values of VS.CCPICPhase3.CodNum.Mean is not 0, this feature is enabled.
Gains
IC Efficiency
VS.FirstStageIcEff.Mean and VS.FirstStageIcEff.Max
CCPIC PHASE2 has not been activated before CCPIC PHASE3

These two counters will be shown as not Zero after feature activation
CCPIC PHASE2 has been activated before CCPIC PHASE3
These two counters will be increased after feature activation
Huawei Confidential
Page 71
Verification
Gains
Uplink System Capacity

VS.HSUPA.Thruput.ROTMorX
VS.HSUPA.Thruput.ROTMorX / VS.HSUPA.DataTtiNum.ROTMorX
VS.CellDCHUE
are expected to increase after feature activation
Uplink RTWP
VS.HSUPA.LoadOutput.X 0~25
are expected to increase in the low load section and decrease in the high load section after feature
activation
Huawei Confidential
Page 72

WRFD-160202
Turbo IC Phase2
FACH POOL
Huawei Confidential
Page 73
Background
With high penetration of smart-phone, on-line users in live work become

more and more.
Uplink control channels (eg. DPCCH/HSDPCCH) waste much uplink load,

and leads to high RTWP.
The average data rate is very small.
DPCCH SIRtarget can be more decreased when data rate is low, this can
reduce power waste of control channel
Adaptive Configuration of
Traffic Channel Power offset for
HSUPA(10ms TTI)
Target: E-DPDCH HARQ offset
RAN13
Adaptive Adjustment of HSUPA

Small Target Retransmissions
Dynamic Configuration of HSDPA
CQI Feedback Period
Load-based Uplink Target BLER
Configuration
Outer Loop Power Control
Enhancement
Target: Target Retransmission
Number CQI Period Target
BLER Initial Target SIR
RAN14
Power Control for Uplink Capacity solutions
Adaptive Configuration of Traffic

Channel Power offset for
HSUPA(2ms)
Target: E-DPDCH HARQ offset
RAN15
Huawei Confidential
Flexible Power Control for

Uplink Low Data Rate
Transmission
Target: Target
Retransmission Number
E-DPDCH HARQ offset Max
SIRtarget
RAN16
Page 74
Introduction
High Data Rate State and Low Data Rate State has been
introduced in feature WRFD-010712 Adaptive Configuration
of Traffic Channel Power offset for HSUPA
This Feature newly introduces Extreme Low Data Rate State
Different State is configured with different power control parameters,
such as Target Retransmission Number E-DPDCH HARQ offset
and SIRtarget.
High Data Rate State:NHR=1% or 10%, HARQ offset=0dB,
SIRtarget is about 8dB
Low Data Rate State: NHR=1% or 10%, HARQ
offset=4dB,SIRtarget is about 4dB
Extreme Low Data Rate State:NHR=10%,HARQ
Red Introduced by this feature

Black Old function
offset=6dB,SIRtarget is about 2dB

Note: NHR=Number of HARQ Retransmission
Huawei Confidential
Page 75
Impact
Benefit
When more than 20 HSUPA users take effect, this feature improves the HSUPA capacity of the cell by
5%~20% which is indicated by the increase in average cell throughput, or the decrease in Received Total Wideband
PowerTest
(RTWP).
Scenario:
Test Scenario:
CCPIC Phase 2 ON
2ms TTI
Average Data Rate=10kbps
CCPIC Phase 2 ON
10ms TTI
Average Data Rate=10kbps
-98
-100
-98.5
-100.5
-99
-99.5
-101
-100
-101.5
-100.5
-102
-101
-102.5
-101.5
-102
-103
-102.5
-103.5
-103
-104
-103.5
-104
-104.5
-104.5
-105
5
10
15
20
25
30
RTWPOFF
35
40
45
10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44
MeanRTWPOFF
RTWPON
Huawei Confidential
Page 76
MeanRTWPON

Negative Impact
More RB Reconfiguration will be introduced to reconfigure the power control parameters to the Extreme Low Data Rate State ,
which increase the possibility of PS call drop.
BTS3812E BTS3812A and BTS3812AE do not support this feature.
BTS3800 series do not support this feature
BTS3900 series (include BTS3902E and BTS3803E) support this feature except configured with WBBPa board or RRU3801C(20w).
Note this feature depends on the actual service load reported by NodeB, so it has hardware dependency.
Dependency and Mutually Exclusive Features

Depends on WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA.
Do not take effect with DC-HSUPA user.
Do not take effect when WRFD-01061208 HSUPA DCCC is activated
Do not take effect when WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell or WRFD -151208
Macro-Micro multi RRUs in one cell is activated
License
This feature performs Cell level control by introducing a new license on RNC
Huawei Confidential
Page 77
Verification
Availability
observation
If the following new counters are not 0, then this feature takes effect for the corresponding service.
Counter
VS.HSUPA.FlexPCLowRate.UE.Mean.TTI2ms
Description
Average HSUPA 2ms TTI user number in serving cell which WRFD-160202 Flexible Power Control for
Uplink Low Data Rate Transmission tack effect.
VS.HSUPA.FlexPCLowRate.UE.Mean.TTI10ms Average HSUPA 10ms TTI user number in serving cell which WRFD-160202 Flexible Power Control for
Uplink Low Data Rate Transmission tack effect.
Gain observation
VS.MultiRAB.FlexPCLowRate.UE.Mean.TTI2ms Average HSUPA 2ms TTI combine service user number in serving cell which WRFD-160202 Flexible
Power Control for Uplink Low Data Rate Transmission tack effect
Average
HSUPA 10ms
combine service
user number in serving cell which WRFD-160202 Flexible
VS.MultiRAB.FlexPCLowRate.UE.Mean.TTI10
Activate the feature in heavy uplink load cells,
and collect
theseTTI
counters
Power Control for Uplink Low Data Rate Transmission tack effect
ms
RNC counters each counter counting period is 15min.
VS.MeanRTWP VS.MeanULActualPowerLoad : are expected to decrease

VS.HSUPA.UE.Mean.Cell VS.HSDPA.UE.Mean.Cell VS.CellDCHUEs VS.PS.Int.UL.*** 8~384 .Traffic
VS.PS.Bkg.UL.*** 8~384 .Traffic : are expected to increase
NodeB counters
VS.HSUPA.LoadOutput.0~ VS.HSUPA.LoadOutput.25
are expected to increase in the low load section and decrease in the high load section after feature activation
Huawei Confidential
Page 78
Turbo IC Phase2 WRFD-160213
FACH POOL
Huawei Confidential
Page 79
Background
UMTS uplink capacity is limited by the multi-access interference
Turbo IC
(MAI) from UE inside and outside the system.

Turbo IC was introduced in RAN15.0 as an enhancement of IC on EDPDCH, by carrying out SIC (Successive IC) in decoding procedures.
In RAN16.0, phase II of Turbo IC is designed to further improve
uplink capacity in terms of 2ms HSUPA numbers as well as cell
throughput in uplink .
Higher UE data rate and more
UE numbers results in higher
interference to other users
ingle HARQ
When UL Uu interface is overloaded (RTWP becomes high), low-
data-rate 2ms HSUPA will be selected to be scheduled with single

HARQ process ( still over 2ms TTI, without need to be switched to
10ms TTI ) and these users can still be brought to Turbo IC and
get the benefit from Turbo IC .
Allow only 1 TTI to transmit data in Single HARQ
With one RLC PDU, HARQs rate = 320bit/(2ms*8) = 20kbps
When UL Uu interface congestion is released and CE resource is
sufficient, single-HARQ user can switch to be scheduled with All

HARQ processes.
Huawei Confidential
Page 80
Impact
Benefit
Significant increment on 2ms TTI user number compared with Turbo IC

(RAN15.0)
Less RB Reconfiguration between 2ms TTI and 10ms TTI decrease the
risk of call drop
Risk
2ms single HARQ user has lower data rate in single HARQ state .
The latency of user plane of single HARQ 2ms is longer than that of
full HARQ 2ms (Based on the test )
Huawei Confidential
Page 81
Dependency
None
Impacted Features
TTI switch: 2ms to 10ms based on RTWP
NodeB determines the candidates on WBBPf or UBBP for single-HARQ 2ms HSUPA and reports to RNC, and
these candidates will not be switched to 10ms based on RTWP.
TTI switch: 2ms to 10ms based on CE
No impact : Full-HARQ and Single-HARQ 2ms HSUPA can still be switched to 10ms based on CE.
WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms
No impact : The causes to trigger single HARQ are different between this feature (based on CE ) and Turbo IC
Phase2 (based on RTWP) ,and they have no impact on each other.
WRFD-010690 TTI Switch for BE Services Based on Coverage
No impact : Full-HARQ and Single-HARQ 2ms HSUPA can still be switched to 10ms based on coverage
This feature has not improvement on coverage.
Huawei Confidential
Page 82
Dependency and Verification
Dependency on Features
Depended on WRFD-150206 Turbo IC
License Control
WBBPf or UBBPd board
Introduce a new license on NodeB
VS.HSUPA.AlltoSingleHARQNum.RTWPCong
VS.HSUPA.SingletoAllHARQNum
will be counted after feature activation
Benefit On UL capacity
will increase
Benefit with TTI switching based on RTWP
VS.HSUPA.TTI2to10.ResRTWP.Succ will decrease
Huawei Confidential
Page 83
Turbo IC Phase2
Load-based Intelligent State Transition WRFD-160214
FACH POOL
Huawei Confidential
Page 84
Background
Huawei Confidential
Page 85
Introduction
RNC collects traffic pattern(IP duration and traffic data volume), calculate the high load D2F
state transition timer; this timer will be shorter than current timer, the target of this timer is to
save largest UU power when using the timer.
RNC will auto estimate the Cell Load; In high load cell, using high load state transition para to
reduce Cell load, in low load cell, using current state transition para to guarantee the user
experience.
Huawei Confidential
Page 86
Impact
Benefit
In high load cells, after data transfer in CELL_DCH, RNC will transit UE to
CELL_FACH more quickly, this will reduce the load in CELL_DCH, improve DL/UL
UU Capacity 5%~20%.
Negative Impacts
In high load cells, RNC will use high load D2F state trans parameter, after data
transfer in CELL_DCH, RNC will transit UE to CELL_FACH more quickly, this will
increase number of state trans and impact the user experience in high load
cells
Huawei Confidential
Page 87
Dependency
Dependency on Hardware/NEs/ Transimission
NA
License
NA
An optional feature by introducing a new license on the RNC
Impacted Features
It's suggested to use with WRFD-020500 Enhanced Fast Dormancy, to make

more UEs involve quick state transition for high capacity gain.
Huawei Confidential
Page 88
Verification
Query SON logs

After this feature is activated, operating information about this feature will be recorded into selforganizing network
(SON) logs.
To check whether this feature has been enabled, perform the following steps to query SON logs:
Step 1: On the M2000 client, choose SON > SON Log.
Step 2: On the displayed SON Log tab page, click Query SON Log. Set Log Category to Loadbased Intelligent State Transition log and Event Name to Not Limited. In addition, specify Event
Source Object and Time Period as required.
Step 3: Click Synchronize in the bottom right corner of the SON Log tab page.
Step 4: Click Query.
If there is a record of Cell level parameter adjustmentin the specified time period, this feature has
taken effect.
If there is no record ofCell level parameter adjustmentin the specified time period, this feature has
not taken effect.
No New counters introduced
Huawei Confidential
Page 89
Verification
Benefit Observation
Counter
Description
VS.CellDCHUEs
Number of UEs in CELL_DCH State for Cell
VS.HSDPA.MeanChThroughput
Mean Downlink Throughput of single HSDPA MAC-d Flows for Cell
VS.HSUPA.MeanChThroughput
Mean Uplink Throughput of single HSUPA MAC-d Flow for Cell
VS.MeanRTWP
Mean Power of Totally Received Bandwidth for Cell
VS.MeanTCP
Mean Transmitted Power of Carrier for Cell
VS.MeanTCP.NonHS
Mean Non-HSDPA Transmitted Carrier Power for Cell
After feature activation, In Highload Cells, VS.CellDCHUEs/VS.MeanRTWP/VS.MeanTCP.NonHS will

decrease, VS.HSDPA.MeanChThroughput/ VS.HSUPA.MeanChThroughput will increase.
Huawei Confidential
Page 90
Turbo IC Phase2
FACH POOL WRFD-151202
Huawei Confidential
Page 91
Background
RRC Access
RRC REJ
RRC REL
F2D/F2H
F2P
P2F
User Data
Status PDU
ACK
f3
CCCH
DCCH
FACH not in
Congestion
DTCH
f2
f1
FACH
When Smartphone penetration grows high, more and

more users are in FACH state and a lot of messages
and data are transmitted by FACH channel.
FACH channel is easily got congestion.
FACH not in
Congestion
FACH in
Congestion
In multi carries scenario, redirect the users from the

cell in FACH congestion to the cell with FACH in free.
FACH Pool can balance the FACH resource between
same coverage carriers within the same NodeB.
Huawei Confidential
Page 92
Typical Scenario
A UE in the CELL_PCH or URA_PCH state camps on its preferentially camped cell (cell F1), as shown in the following
figure. UE will be redirect to F2 once service activation. This strategy will improve AMR experience since the F2 with
high load from HSPA . The UE camps on F1 cell with better coverage , which brings high access successful rate and
better call drop rate .
On networks that adopt the preferentially camping policy, the number of FACH UEs across multiple co-coverage cells is
imbalanced. Among these cells, preferentially camped cells have more FACH UEs than the other cells. FACH congestion
easily occurs in cells with a large number of FACH UEs and user experience in these cells is poor. The FACH bandwidth
utilization in cells with a small number of FACH UEs is low.
This feature is not suitable for networks with macro

and micro cells. This is because this feature
F2
requires blind-handover-supporting neighboring
F1
cells. However, the blind handover flag in the areas
FACH UE
where macro and micro cells overlap may be

FALSE.
This feature is not suitable for the networks that
adopt the randomly camping policy. This is
because on these networks, the number of FACH
UEs across cells is balanced.
Huawei Confidential
Page 93
Impact
Benefit
The FACH Pool feature increases the FACH bandwidth utilization, reduces the DCH consumption, and expands system
capacity for the hot spots that adopt the preferentially camping policy. After this feature is activated, some of these UEs are
redirected to cell F2. After this, the FACH bandwidth utilization of cell F1 increases by 10% to 90%
Impact on Networks
In terms of system capacity: This feature increases the FACH bandwidth utilization, reduces the possibility of DCH
congestion, shortens the FACH delay, and improves user experience. Since more data is carried over the FACH, DCHs are
saved and the capacity of cell F2 increases by 1% to 5%.
The following description takes a hot spot in site T of country S as an example to evaluate feature gains. Before feature activation,
55 FACH UEs camp on cell F1, the FACH bandwidth utilization in cells F1 and F2 is 50%, and the DCH congestion duration in cell F1
is 3600s per hour. After feature activation, 30 FACH UEs camp on cell F1 while 25 on cell F2, and the FACH bandwidth utilization in
cell F1 is 98% while 94 in cell F2. In addition, the DCH congestion duration in cell F1 is 2700m per hour.
In terms of impact on networks: The P2F-triggered redirection algorithm prolongs the delay by 1s. This algorithm also
increases the number of cell updates.
In theory, the FACH takes half of power to transmit 256 bytes than an HSDPA channel, including the power used for a P2F state
transition. The max load of FACH is 12% or so ,if the FACH utilization of F2 reach 94%, the saved power is 12%94%50%=5.64%
compared with data transmission in HSDPA
Huawei Confidential
Page 94
Dependency
Smart P2D, described in State Transition Feature Parameter Description

TAC-based P2D in Enhanced Fast Dormancy , described in Enhanced Fast Dormancy Feature Parameter Description
TVM-based P2D, described in Flow Control Feature Parameter Description
PS P2D in case of DTCH congestion, described in Flow Control Feature Parameter Description
None
Dependency on Other NEs
1.
2.
3.
4.
None
Impacted Features
None
None
License
An RNC-level license controls the FACH Pool feature, which takes effect on a cell basis.
Huawei Confidential
Page 95
Verification
After the network has run for a period of time, query the values of the following
counters:
VS.P2F.Redir.Out
VS.P2F.Redir.Out
VS.P2F.Redir.In.DirectCmp
This feature has taken effect if the value of the first counter is not 0 and the
value of the second or third counter is not 0.
Huawei Confidential
Page 96
Feature Application Cases
Numbers of FACH UEs among different frequencies are becoming balanced.

Huawei Confidential
Page 97
Turbo IC Phase2
FACH POOL
RTWP Control Optimization IntFD-160008
Huawei Confidential
Page 98
Background
Uplink coverage will shrink due to RTWP rise, and more call drops will happen.
Based on the live network KPI
CS call drop is linearly deteriorating with RTWP rise
CS call drop rate vs RTWP

30.00%
20.00%
10.00%
0.00%
-105
-95
-85
-75
-65
-55
-10.00%
RTWP
RTWP Control Optimization will restrain RTWP rise and avoid the Uplink coverage and Call drop
performance deterioration.
Huawei Confidential
Page 99
Introduction
This algorithm module is realized in RNC, and is an enhancement of ENU(Equivalent Number of Users)
Algorithm(ALGORITHM_SECOND) . The total equivalent number users can be adjusted dynamically.
If cell RoT is bigger than RoTControlTarget uplink total ENU is decreased.
If cell RoT is smaller than RoTControlTarget*.0.9 uplink total ENU is increased .
else the uplink total ENU is kept as unchanged.
Not only the uplink total ENU adjustment, the uplink admission threshold and uplink LDR threshold are
also changed, then RoT will be restrained by less user admission and LDR actions.
Uplink Total ENU Adjustment
Cell RoT
Cell RoT>RoTControlTarget
Decrease
Cell RoT<RoTControlTarget*0.9
Increase
Other
Be kept
Uplink Call Admission Control
algorithm:
Impact on:
- Call Admission Control
- Uplink LDR
Huawei Confidential
- ALGORITHM_SECOND
- Call Admission Control
- Uplink LDR Trigger
Page 100
Impact
The algorithm is recommended to be activated when cell RTWP is too high to bring deteriorated uplink
coverage and call drop performance , and customers have expect to control the RTWP rise.
Benefit
Improve uplink coverage and call drop performance when the RTWP is too high.
Negative Impact
If RTWP in live cell is higher than RoTControlTarget, ,the total UL ENU Max will be adjusted to less value
which cause tougher admission ,and RRC success rate/RAB success rate/F2D/P2D success rate deteriorate and
CS Erlang will decrease.
More admission rejections may bring storm of retries, so it is recommended to active RRC loose admission
and WRFD-160206 RB Parking.
It is recommended to activate this algorithm on massive and continuous cells. If only single cell is activated ,the
uplink load of neighbor cells will raise the thermal of this single cell ,which deteriorates the cell capacity much.
If RTWP rise is caused by interference, this algorithm will deteriorate cell capacity much. So, auto-adaptive
background noise update algorithm is recommended to activate to adjust the background noise .
Huawei Confidential
Page 101
Dependency
Dependency on Hardware/NEs/ Transmission
None
License
None
An basic function without License Control.
Impacted Features
None
Huawei Confidential
Page 102
Verification
Counter Name
Counter Description
VS.RAC.AdjUlTotalEqUserNum.Mean
Mean adjusted uplink total equivalent user numbers for cell
VS.RAC.AdjUlTotalEqUserNum.Max
Maximum adjusted uplink total equivalent user numbers for cell
VS.RAC.AdjUlTotalEqUserNum.Min
Minimum adjusted uplink total equivalent user numbers for cell
Benefit Observation
VS.MeanRTWP will be close to VS.BackGroundNoise.Mean+ RoTControlTarget
CS and PS Call Drop rate will decrease.
Huawei Confidential
Page 103
Content
1
Summary of RAN16.0

UMTS HD Voice


UMTS SON Solution

Huawei Confidential
Page 104
Swap Efficiency Improvement for Intra-RNC WRFD-160107
Automatic NodeB and Cell Allocation in the RNC
EBC Enhancement
Huawei Confidential
Page 105

Improve the efficiency of moving NodeB in RNC
MML
Optimization
MOV UNCP
New Added MML
MOV UCCP
New Added MML

MoveType=
OnlyThisNodeBObj
MoveType=ObjsOfThis
ADD
NBOnNBSSN
Parameter:
MoveType
MoveType=AllObjsOf
ThisNodeB
MOV UNODEB
Effect
Effect
NO Need to delete, then add, Done by one command

Only move the NodeB (not include its cell, NCP or CCP)
Done by one command,

easy to use.
Same as previous version
Move the other part of NodeB on the same CPUS with

NodeB now to specified CPUS.
Whole NodeB moving:
Move all part of NodeB(include NodeB,its cells,its NCP
and its CCP) to specified CPUS, not matter where they are
now.
Done by one command,

easy to use.
Move one NodeB with 12 cells, cost time: 2min ->30s.

Dependency : This is a basic feature introduced from R16.0 ,and no license control .
Huawei Confidential
Page 106
Swap Efficiency Improvement for Inter-RNC IntFD-160012
EBC Enhancement
Huawei Confidential
Page 107

Improve the efficiency of moving NodeB across RNCs
Why the moving cost time in previous version?
- too many configure to setup a cell;
- too many neighboring cell relationship
- the MML command is done one by one
How to solve it?

- Pack the MML command to 2 virtual MML command(one for cell setup, one for
neighboring cell relationship)
Effect
- The cost time to move 180 NodeB across RNCS:
3 days 2 days.0
Dependency
- This is a basic function ,and no rely on License or other features ,but rely on CME
Huawei Confidential
Page 108
Automatic NodeB and Cell Allocation in the RNC WRFD141103
EBC Enhancement
Huawei Confidential
Page 109
Background
Scenario 1: Unplanned Big Event
Scenario 2: long-term traffic are unbalanced
Characters:
Characters:
NodeB covers hot palace such as stadium
NodeB covers hot palace such as stadium
Low traffic on working day
Low traffic on working day
Bursting traffic on holidays
Bursting traffic on holidys
One NodeB can cause on CP subsystem overload
One NodeB can cause on CP subsystem overload
Huawei Confidential
Page 110
Introduction
Immediate Homing
(Performed during busy
hours, and services are
slightly affected.)
Scenario 1:
Unplanned Big Event
Fast and without

service impact
Call drops do not occur, but new services cannot
access the network for 10s.
Automatic allocation
Scenario 2:
Scheduled Homing
(Performed during idle
hours, and services are
slightly affected.)
long-term traffic are

unbalanced
Slow and impact

online service
The reallocated object is reestablished and is

unavailable. Call drops occur, and the network
will be out-of-service. The out-of-service time is
less than or equal to 30s.
Huawei Confidential
Manual allocation
Page 111
Reviewed and
executed by
customers
Introduction - Immediate Homing

Item
Application
Scenario
Moving
Time
Move Object
Impact
on Services
10m
in
Description
Scenario 1: Unplanned big event
Immediate
Cell
The moving (not more than 10s) has the following impact
on services:
New subscribers cannot access the network.
Online subscribers will not experience call drops or
service drops, but no new signaling procedure will be
allowed.
Move cell out of this

high CPU load CPUS
Note:
Key Point
Keep high CPU load for 10min;
Only move cell (RNC automatically move cell to target CPUS by
Trigger
Condition
using MOV UCELL)
Move cell to target CPUS by using backup(first backup data of

cell and its UEs, than swap)
Huawei Confidential
During immediate allocation, service objects will be

removed and then reestablished. Therefore, the values of
the performance counters for monitoring the service
objects may be incredible and are for your reference only.
If the average CPU load of a certain subsystem is greater
than ImmdAssignOutCpuThd for 10 consecutive minutes,
service objects may be allocated from this subsystem to
another.
If the average CPU load of a certain subsystem is less
than ImmdAssignInCpuThd for 10 consecutive minutes,
service objects may be allocated to this subsystem from
another.
ImmdAssignOutCpuThd and ImmdAssignInCpuThd can be
set in the SET
UCELLAUTOHOMING
command.
Page
112
Introduction Scheduled Homing

Key Point
CPU load in is high for 30 consecutive

minutes during the past day;
Move cell/NodeB/NCP/CCP (RNC
Item
Scheduled Allocation (Automatic)
Application
Scenario
Used to balance the load generated due to radio resource management. The radio resources include
NodeBs, cells, NCPs, and CCPs.
Move Time
It is recommended that the allocation be

performed in the early morning when traffic is
the lightest. The allocation time is set in the
SET URSCADJTIME command.
Move Object
NodeB, cell, NCP, and CCP
Impact
Services
The moving has the following impact on services:

The allocated service objects will be removed and then reestablished.
Online circuit switched (CS) subscribers will experience call drops.
Online packet switched (PS) subscribers will experience service drops, but services will be
automatically reconnected.
The network will be out-of-service. For a NodeB with 12 cells, the out-of-service time is less than or
equal to 20s.
Note:
During scheduled allocation, service objects will be removed and then reestablished. Therefore, the
values of the performance counters for monitoring the service objects may be incredible and are for
your reference only.
automatically move them by using

MOV UCELL,MOV UNODEB,MOV
UNCP,MOV UCCP)
Move object by delete and rebuild,

so the on going service will be
impacted.
Trigger
Condition
Scheduled Allocation (Manual)
on
The customer can decide the allocation time as

required. It is recommended that the allocation be
performed in the early morning when traffic is the
lightest.
If the average CPU load of a certain subsystem is greater than SchedAssignOutCpuThd for 30
consecutive minutes, service objects may be allocated from this subsystem to another.
If the average CPU load of a certain subsystem is less than SchedAssignInCpuThd for 30 consecutive
minutes, service objects may be allocated to this subsystem from another.
SchedAssignOutCpuThd and SchedAssignInCpuThd can be set in the SET UCELLAUTOHOMING
command.
Huawei Confidential
Page 113
Impact
Impact
Benefit
Negative
Impacts
Immediate Homing
Avoid CPU flow control when encounter unplanned big
event, improve KPI
The moving (not more than 10s) has the following

impact on services:
New subscribers cannot access the network.
Online subscribers will not experience call drops or
service drops, but no new signaling procedure will
be allowed.
Note:
During immediate allocation, service objects will be
removed and then reestablished. Therefore, the
values of the performance counters for monitoring
the service objects may be incredible and are for
your reference only.
Scheduled Homing
Balance the CPU load of CPUSs, avoid CPU flow control,
improver KPI
The moving has the following impact on services:

The allocated service objects will be removed and then
reestablished.
Online circuit switched (CS) subscribers will experience call
drops.
Online packet switched (PS) subscribers will experience
service drops, but services will be automatically reconnected.
The network will be out-of-service. For a NodeB with 12 cells,
the out-of-service time is less than or equal to 20s.
Huawei Confidential
Note:
During scheduled allocation, service objects will be removed
and then reestablished. Therefore, the values of the
performance counters for monitoring the service objects may
be incredible and are for your reference only.
Page 114
Dependency
None
None
License
This is a basic feature Enhancement in R16 and no License Control. This feature is
supported in BSC 6910 before R16, and is supported in BSC6900 from R16.
Huawei Confidential
Page 115
Verification
Operatio
n
Immediate Homing
Scheduled Homing
Character
s when
take
effect
ALM-22240 Automatic NodeB and
Cell Allocation in the RNC

raised.
ALM-22240
Inappropriate
Deployment is raised.
You can find moving advise under Ftp\OptMml

directory
on
the
OMU
,
named:
OptMmlYearMonthDate.txt.
MANUAL Mode
is
You can find moving history under

Ftp\OptMml directory on the OMU ,
named
as:ImmMovHist_20120711_11_58_00.tx
t
the following 2 counters slide also

indicate the numbers of cells that are
moved.
VS.AutoHoming.AttCell
VS.AutoHoming.SuccCell
NodeB
the following 6 counters slide also indicate the

numbers of cells that are moved.
VS.AutoHoming.AttCell/NodeB/Iubcp
VS.AutoHoming. AttCell/NodeB/Iubcp
You can find moving history under

Ftp\OptMml directory on the OMU , named
as: SchMovHist_20120711_11_58_00.txt
The history is recorded as(cell/NCP/CCP is
similar):
MOV UNCP: IDTYPE=BYID, NodeBId=2218,

SSN=2046; //src_SSN:0-1-2070; dest_SSN:011-2046; NESSF= 80;
Please check the advise runs the RUN
BATCHFILE command to execute it.
ALM-22240 Automatic NodeB and Cell

Allocation in the RNC is raised.
The history is recorded as(cell/NodeB/CCP is

similar):
The history is recorded as:

MOV UCELL: IDTYPE=ByCellId,
CellId=4402, SSN=2194; //src_SSN:02-2196; dest_SSN:0-2-2194; NESSF =
240;
AUTO Mode
MOV UNODEB: IDTYPE=BYID,

NodeBId=2197, SSN=2074; //src_SSN:010-2080; dest_SSN:0-1-2074; NESSF=
120;
the following 6 counters slide also indicate

the numbers of cells that are moved.
VS.AutoHoming.AttCell/NodeB/Iubcp
VS.AutoHoming. AttCell/NodeB/Iubcp
NESSF: the number of equivalent standard signaling flow

Huawei Confidential
Page 116
Verification
When Immediate Homing or Scheduled Homing is turned on, RNC will output a .csv file every day to indicate the NESSF
of each CPUS under Ftp\OptMml directory on the OMU.
The .csv file like as:
NOTES
Subrack
0
Slot
1
SSN
2000
2002
NESSF On Lasted Day

1900 the busiest 30min
Predict NESSF Next Day

1800
NOTE: the Predict NESSF Next Day = Current move out volume / + move in volume
Using of above .csv file:
Help to evaluate the effect of Immediate Homing and Scheduled Homing.
Help to judge whether the move advice output by Scheduled Homing is proper.
Huawei Confidential
Page 117
Feature State Query and Bulk Commission IntFD-160009
EBC Enhancement
Huawei Confidential
Page 118
Background -
Feature State Query
Problem :
There are more than 500 features for U&L system, and each feature has many Configuration Parameters to
configure, such as RNC Connection Object parameter UCORRMALGOSWITCH, Cell level parameter
UCELLALGOSWITCH, NodeB level parameter ALGOPARA, and Channel type parameter UFRCCHLTYPEPARA, etc.
Its impossible to query the Configuration State of all Network all Features, and the relation between the License State
and Configuration State , which are necessary and basic for customers to learn about.
Requirement:
VDF JV EE and O2 all required an application to statistically analyze the NE licenses. Problem today: they
dont want to query each NE separately to get the information but they want an report including whole 2G, 3G 4G,
Radio and packet core. Also search and filtering as well as exporting is required.
Huawei Confidential
Page 119
Background -
Feature Bulk Commission
Problem:
DC-HSDPA Feature Commission includes more than 20
commands. If field engineers forget some commands, for example
missing Cell level parameter UCELLALGOSWITCH, which results in
DC-HSDPA commission
the modification of DC cell load balance policy and HSDAP throughput

drop for 400kbps, of course this feature fail to active.
It spend one week for field engineers to fix this problem.
Bulk and automatic Commission is necessary for fields engineers to
RNC Commands Related

Optional Commands
SET/MOD Commands
Commands Num
Call Times
17
8
32
19
11/13
ADD Commands
1/6
gain more efficient man-day and more customer satisfaction.

NodeB Commands Related
Optional Commands
SET/MOD Commands
Requirement:.
VDF UK complains the feature commission for many times, such
ADD Commands
as complex operation, low efficiency and satisfaction.
Huawei Confidential
Page 120
6
4
12
7
2/7
3/0
Introduction
Feature Status Query
Feature List:
UMTS & LTE Optional Features 500+
support, GSM not support except Inter-RAT
Interoperability GSM related ones
Status Query:
Configuration Status only for configuration
parameter related, License status for License
usage, and Feature Rely not support.
Query Step:
1) Feature Select (include Feature Package)
2) Network Object Select
3) Query Performance and Report Export
Huawei Confidential
Page 121
Introduction
Bulk Commission
Feature List: Some Features are complex to active, including UMTS Data Service
HSPA 12 features, Inter-RAT
Interoperability 38 features related GULT

Bulk Commission: Commission only for Configuration parameter based on feature Granularity, Hardware
Configuration not support. XLS model for Commission parameter setting, and each MO each Sheet for parameter list of
this MO. Default parameters come for live network, and suggestion values are also supported for replacement.
Commission Step:
1. Feature Select (include Feature Package)
2. Network Object Select
3. Configuration Model (.XLS) export for setting based on individual scenario
4.
Import the modified Configuration Model for Commission and Activation
Huawei Confidential
Page 122
Dependency
None
Dependency on NE
None
U2000(CME)
License
An optional feature with new license on OSS to control:
LWM1HSSOMWR---HSPA Service Operation Management -WRAN
Huawei Confidential
Page 123
EBC Enhancement IntFD-160006
Huawei Confidential
Page 124
Background
EBC in RAN16.0 has the similar technical principle and architecture to that in RAN15.0. To be specific, operators customize
required counters on the GUI, and the U2000 sends related commands to the RNC. The CHR switches used to measure
these counters are turned on and the counters are sent to the SAU. Then, the SAU preprocesses the CHRs based on the
rules delivered by the U2000, generates a MCounter file, and then reports the file to the U2000. The U2000 triggers a
secondary summary on the file again as a periodic result file. At last, the periodic result file is converted into the required
format for display on the PRS or NMS.
Huawei Confidential
Page 125
Application Scenarios
Typical Scenarios
Check the RRC setup success rate in each scenario based on EBC counters.
Check missing intra-frequency neighboring cells based on EBC counters.
Check counters related to PCH state transition and cell update.
Check the RRC setup success rate, RAB setup success rate, and RAB call drop rate based on
the transmit propagation delay (TP).
Check based on the data volume and throughput of users (gold, silver, or copper users) at
different priority from different operators, which is used for charging in the MOCN network.
Use EBC counters when RNC in Pool is supported.
Huawei Confidential
Page 126
Benefits and Network Impact
Feature benefits
Network scenarios: RNC in Pool is supported.

Usability: Significantly improved compared with RAN15.0. The operation efficiency is enhanced.
Support the Excel import or export.

Define new counters based on existing counters .
Semi-manually generate counter names based on preset conditions.
Add basic information for counters.
Screen required counters by condition.
Reliability: The secondary summary function on the U2000 maximally reduces the possibility of data
inaccuracy.
Specifications: Changed from 0.6 million (number of cells x number of counters) in RAN15.0 to 1 million in
RAN16.0. When counters are activated, check whether the system specifications reach the upper limit.
Network impact: none
Huawei Confidential
Page 127
Dependency
Dependency Features
SAU
Dependency on other NEs
None
Hardware Dependency
None
Impacted Features
None
RNC, U2000, and PRS
License
This feature is an enhancement, and there is no new license.
Huawei Confidential
Page 128
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Huawei Confidential
Page 129
RNC in Pool User-Plane Load Sharing WRFD-150211
Huawei Confidential
Page 130
Background
In RAN15.0, RNC in Pool supports load sharing of one BSC6910 pooled with three
BSC6900s or two BSC6910s pooled with each other. In RAN16.0, the enhancement of
user-plane load sharing is introduced.
Supports user-plane load sharing and increases the user-plane processing capabilities of a
logical RNC
With UP load sharing, the overflow RNC can share the UP load with the master RNC. This avoid RNC
splitting in the case of RNC UP processing capability limitations.
Reduce signaling traffic over the Iur-p interface and further improve the control plane (CP)
capacity.
With UP load sharing bound with the control plane (CP), UE's UP and CP load can be shared to the
overflow RNC, which greatly reduces the forwarding consumption over Iur-p as less messages are
forwarded. This further improves the CP capacity of a single logical RNC.
Reduce call setup delays, thereby improve user experience
With the UP load sharing bound with the CP, less signaling messages are interacted between physical
RNCs, which reduces call setup delays.
Huawei Confidential
Page 131
Introduction
UP load sharing must be performed together with CP load sharing.

Iu, Iub, and Iur user-plane transmissions must be configured on the overflow RNC. With userplane load sharing, Iu user-plane data is processed by the overflow RNC , and Iub or Iur userplane data can be processed by the master or overflow RNC.
CN
CN
IU
L_RNC1
L_RNC: Logical RNC

P_RNC: Physical
RNC
L_RNC1
IUR-P
P_RNC1
Master
L_RNC: Logical RNC

P_RNC: Physical RNC
IU
IUR-P
P_RNC2
Overflow
P_RNC1
Master
RNC in POOL
P_RNC2
Overflow
RNC in POOL
IUB
IUB
NodeB
CP
UP
NodeB
Case 1: With user-plane load sharing, transmission data

is processed by the overflow RNC.
(Priority scenario)
CP
UP
Case 2: With user-plane load sharing, transmission data needs to

travel through the Iur-p interface and be processed by the master
RNC.
(Common channel and handovers)
Huawei Confidential
Page 132
Impact
Benefit
Signaling traffic over Iur-p is reduced significantly

The signaling traffic over the Iur-p interface is reduced significantly. The following test result is based on the smartphone
model:
Messages traffic over Iur-P decreases from 61.84% (with control-plane load sharing only) to 59.29% (control-plane Plus
user-plane load sharing).
Packets over Iur-P decreases from 73.93% (with control-plane load sharing only) to 60.09% (control-plane Plus userplane load sharing).
Increases the busy hour call attempts (BHCA) and UP throughput of the logical RNC.
If only control-plane load sharing is performed, the system BHCA is 1.6 times the one without load sharing . With
control-plane plus user-plane load sharing , the system BHCA and user-plane throughput can be improved to 1.9 times .
Reduce the signaling delay introduced by only control-plane load sharing

If only control-plane load sharing is performed, signaling setup delay increases. For example, delay of the signaling
setup for a CS service is increased about 400 ms. With control-plane plus user-plane load sharing , the signaling setup
delay is greatly reduced to be the same as none-sharing scenarios.
Huawei Confidential
Page 133
Dependency
None
WRFD-010660 MBMS Phase 2

This feature is mutually exclusive with the MBMS Phase 2 because MBMS Phase 2 supports data inconsistency in inter-RNC sharing for
MBMS services, which decreases the broadcast service performance in inter-RNC handovers.
Impacted Features
WRFD-020134 Push to Talk

When this feature is used together with WRFD-020134 Push to Talk, the push to talk (PTT) access delay of UEs whose signaling is shared
between RNCs will increase. As a result, the key performance indicators (KPIs) of the Push to Talk feature cannot meet requirements.
WRFD-070004
WRFD-070005
WRFD-070006
WRFD-070007
Load Based GSM and UMTS Handover Enhancement Based on Iur-g

NACC Procedure Optimization Based on Iur-g
GSM and UMTS Load Balancing Based on Iur-g
GSM and UMTS Traffic Steering Based on Iur-g
The overflow RNC does not support the Iur-g interface. The following features do not apply to UEs whose signaling is taken over by the
overflow RNC. UEs whose signaling is processed by the master RNC can use the preceding features.
Huawei Confidential
Page 134
Dependency
Impacted Features (Continued)
WRFD-02060501 SRNS Relocation (UE Not Involved)

WRFD-021400 Direct Signaling Connection Re-establishment (DSCR)
If either of the preceding two features is used, Serving Radio Network System (SRNS) relocation and directed signaling connection
re-establishment (DSCR) due to Iur transmission resource congestion cannot be performed on UEs whose signaling is taken over by the
overflow RNC. This happens.
If the feature WOFD-192300 Event-based Counter - WRAN is used on the M2000, the event-based counters (EBCs) cannot be
applied or reported for the UEs whose signaling is taken over by the overflow RNC.
WRFD-021304 RAN Sharing Introduction Package
The WRFD-021304 RAN Sharing Introduction Package feature allows two neighboring RNCs to be configured with different OPCs
and the same NI and DSP. In this case, when user-plane load sharing is enabled, the overflow RNC cannot distinguish between the two
neighboring RNCs. Therefore, do not configure two neighboring RNCs with the same NI and DPC over the Iur interface for the overflow
RNC.
None
The base station must support IP transmission , and the CN supports configuring Iu, Iub, and Iur user-plane transmissions
on the overflow RNC.
License
This is an feature enhancement of RNC in Pool Load Sharing(WRFD-150211) without new License in R16.0
Huawei Confidential
Page 135
Verification
Counter Description
Description
VS.R99PSLoad.DLThruput.NodeShare
Average Equivalent Erlangs Consumed by CS Load Sharing Users Between Physical RNC Nodes for an
RNC
DL R99 Average Traffic of Load Sharing Users Between Physical RNC Nodes for an RNC in the PS Domain
VS.R99PSLoad.ULThruput.NodeShare
UL R99 Average Traffic of Load Sharing Users Between Physical RNC Nodes in the PS Domain
VS.HSDPAPSLoad.DLThruput.NodeShare
HSDPA Average Traffic of Load Sharing Users Between Physical RNC Nodes for an RNC in the PS Domain
VS.CSLoad.Erlang.Equiv.NodeShare
HSUPA Average Traffic of Load Sharing Users Between

Physical RNC Nodes for an RNC in the PS Domain
DL Iub DCH Traffic Passing Through the Iur-p Interface of
Load Sharing Users Between Physical RNC Nodes for an
RNC
Iub HSDPA Traffic Passing Through the Iur-p Interface of
RNC
UL Iub DCH Traffic Passing Through the Iur-p Interface of
RNC
VS.Iurp.IubBytesHSUPA.Rx.NodeShare
VS.Iurp.IurBytesDCH.Tx.NodeShare
VS.Iurp.IurBytesHSDPA.Tx.NodeShare
VS.Iurp.IurBytesDCH.Rx.NodeShare
VS.Iurp.IurBytesHSUPA.Rx.NodeShare
HSUPA Average Traffic of Load Sharing Users Between Physical RNC Nodes for an RNC in the PS Domain
DL Iub DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC
Nodes for an RNC
Iub HSDPA Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC Nodes
for an RNC
UL Iub DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC
Nodes for an RNC
Iub HSUPA Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC Nodes
for an RNC
DL Iur DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC
Nodes for an RNC
Iur HSDPA Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC Nodes
for an RNC
Iur DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC Nodes
for an RNC
Iur HSUPA Traffic Passing Through the Iur-p Interface of Load Sharing Users Between Physical RNC Nodes
for an RNC
Huawei Confidential
Page 136
Verification
Performance Evaluation
Check the user-plane load sharing effect by querying the following traffic counters:
VS.CSLoad.Erlang.Equiv.NodeShare
VS.R99PSLoad.DLThruput.NodeShare
VS.R99PSLoad.ULThruput.NodeShare
VS.HSDPAPSLoad.DLThruput.NodeShare
VS.HSUPAPSLoad.ULThruput.NodeShare
Check the traffic over the Iub links that travels through the Iur-p interface by querying the following counters:
VS.Iurp.IubBytesDCH.Tx.NodeShare
VS.Iurp.IubBytesHSDPA.Tx.NodeShare
VS.Iurp.IubBytesDCH.Rx.NodeShare
VS.Iurp.IubBytesHSUPA.Rx.NodeShare
Check the traffic over the Iur links that travels through the Iur-p interface by querying the following counters:
VS.Iurp.IurBytesDCH.Tx.NodeShare
VS.Iurp.IurBytesHSDPA.Tx.NodeShare
VS.Iurp.IurBytesDCH.Rx.NodeShare
VS.Iurp.IurBytesHSUPA.Rx.NodeShare
Huawei Confidential
Page 137
Content
1
Summary of RAN16.0

UMTS HD Voice




UMTS SON Solution

Huawei Confidential
Page 138
Camping Strategy Switch for Mass Event WRFD-151203
RB parking
Automatic Congestion Handler
Huawei Confidential
Page 139
Background
Special events, such as large gatherings, concerts, and sporting events, often result in sudden and
dramatic increases in traffic. On multi-carrier networks with preferred camping, such increases in
traffic usually lead to access congestion in preferentially camped cells and cause key performance
indicators (KPIs) to deteriorate. As a result, the system capacity is undermined.
120.00%
RRC_Att_Est_20061(F1)
RRC_Setup_SuccRate_20061(F1)
RRC_Setup_Succrate_20064(F3)
100.00%
2500
2000
80.00%
1500
60.00%
1000
40.00%
500
20.00%
12
:0
0
12
:3
0
13
:0
0
13
:3
0
14
:0
0
14
:3
0
15
:0
0
15
:3
0
16
:0
0
16
:3
0
17
:0
0
17
:3
0
18
:0
0
18
:3
0
19
:0
0
0.00%
Time(2010.6.11)
For example, in a site F1/F2/F3 is set for the UE to randomly camp on and F4 is set to IdleCellBarred.
Meanwhile, the priority of HSPA services for F4 is set higher than for F1/F2/F3. This networking strategy can
improve the AMR user experience but decreases the RRC connection setup success rate and increases the
call drop rate for CS services.
Huawei Confidential
Page 140
Feature Description-Application Scenarios
Typical Scenarios
The Camping Strategy Switch for Mass Event feature is used in places where preferred
camping is used and events such as large gathering and sporting events occur.
This feature cannot be used on networks where macro and micro cells coexist because
micro cells cannot be configured as blind-handover-supporting-cells of macro cells.
This feature can also be enabled on networks where preferred camping is used for high
and low frequencies because this feature does not change the network into random
camping until the network traffic meets a specific threshold.
Huawei Confidential
Page 141
Benefits and Network Impacts
System Capacity
During special events, this feature increases the following items:
Number of equivalent Erlangs of all the services in the CS domain

Number of HSPA bytes transmitted from the RLC layer
Network Performance
If there is a sharp increase in a network's traffic mainly due to downlink power resource congestion, this feature
increases the RRC connection setup success rate by 3% to 15% and the radio access bearer (RAB) setup success rate
for preferentially camped cells. The reason is as follows:
After the congestion occurs, UEs continuously attempt to access the network and as a result power consumption
increases. After the network camping strategy changes to random camping, the number of continuous access
attempts decreases and therefore power consumption is reduced.
If the sharp increase is mainly caused by SF code or (equivalent number of users) ENU resource insufficiency, this
feature cannot greatly increase the RRC connection setup success rate. This is because the number of SF codes and
the ENU do not increase after the network camping strategy changes to random camping.
Huawei Confidential
Page 142
Benefits and Network Impacts
Network Performance (Continued)
This feature cannot provide noticeable gains if the capability of a preferentially camped cell is different from
that of the corresponding non-preferentially camped cell, for example, a preferentially camped cell supports only
R99 services but the corresponding non-preferentially camped cell supports HSPA services. The reason is as
follows:
The two cells support different types of services. In this case, UE and service allocation between the two cells
cannot be balanced
120.00%
2500
100.00%
2000
80.00%
1500
60.00%
1000
40.00%
500
20.00%
12
:0
0
12
:3
0
13
:0
0
13
:3
0
14
:0
0
14
:3
0
15
:0
0
15
:3
0
16
:0
0
16
:3
0
17
:0
0
17
:3
0
18
:0
0
18
:3
0
19
:0
0
0.00%
Time(2010.6.11)
RRC connection setup rate in prefer camping

RRC connection setup rate in random camping

Huawei Confidential
Page 143
Dependency
Dependency or Mutually exclusive features

None.
Impacted features
The Camping Strategy Switch for Mass Event feature has higher priority than WRFD-020105 Potential User Control. When
the Camping Strategy Switch for Mass Event feature is taking effect, the WRFD-020105 Potential User Control feature stops
taking effect. When the Camping Strategy Switch for Mass Event feature stops taking effect, the Potential User Control
feature resumes.
When this feature is taking effect in a cell, the function of inter-frequency directed retry decision (DRD) for service steering
and the function of redirection during the RRC connection release phase fails.
Dependencies on hardware /other NEs

None.
License
The license control item has been added to the RNC to control this feature at the cell level.
Activation Prerequisites
The Camping Strategy Switch for Mass Event feature can be used on multi-carrier networks that use preferred camping
Huawei Confidential
Page 144
The Camping Strategy Switch for Mass Event feature does not change network parameters or affect network
performance until the network traffic meets a specific threshold.
When the network traffic meets the specific threshold, this feature is triggered to change the network camping
strategy from preferred camping to random camping. As a result, the RRC connection setup success rate is
increased by 3% to 15%.
IF this feature is triggered on a network, the parameters configured for random camping are resumed to the
original preferred camping at 4:40 every day. Therefore, the call drop rate for CS services may increase when the
traffic is not heavy but the parameters configured for this feature have not yet been resumed.
Huawei Confidential
Page 145
Application Cases
Beta test at the site of GAF067 in Koweit
The network traffic is low, so change the threshold of RrcConnSumThd and

RrcRejByCongRatioThd to make the feature triggered more easily. The basic KPI is stable.
When the feature is active, the number of RRC connection setup requests ,the DCH UEs
,the FACH UEs will be balanced between different cells.
Huawei Confidential
Page 146
Camping Strategy Switch for Mass Event
RB parking WRFD-160206
Automatic Congestion Handler
Huawei Confidential
Page 147
Background
Access Performance deterioration
The Troubles in Big Event

Scenarios
RNC rejects new users after congestion ,which
leads to too many RRC retries
Too much Uu resources are wasted on RRC

processes , which leads to very high RTWP ,
too bad access performance and too low
capacity .
The potential CS users are forbidden to retry

a new call for a period (normally ,15s) due to
the RRC access failure, which deteriorates the
RB
will keep(CS
theusers
stability
of
CSParking
users experience.
are more
sensitive than and
PS users
)
cell performance
improve
CS traffic in
Capacity deterioration
Big Event Scenarios

Huawei Confidential
Page 148
Introduction
RB Parking
RB Parking for PS sing BE service after RAB CAC failed,

which is in stead of rejection and RRC release before.
These admitted users are set in Cell_FACH Parking state.
These Parking users are not allowed to send PS data ,and

RNC will stop downlink PS data transmission also ,but CS
service is not impacted.
The PS service will resume if 4A event triggers F2D.
If the users stay in Parking more than ParkingRelTimer

(Normally,300s) the RNC will release this user to idle
directly.
Huawei Confidential
Page 149
Impact
Benefit
The PS RRC request Retries and the corresponding resource consumption will decrease, and the cell
performance stability and CS traffic will be improved in the Big Event scenarios. The experience of CS
users will be improved
The PS RAB Setup successful rate will increase since the rejection due to congestion decreases
The PS call drop rate will decrease since the preempted PS users will come to Parking instead of be
released directly.
Negative Impact
The Parking usersPS service is suspended for a period of time ,and their experience will be
deteriorated in some degree.
The battery consumption of UE is more in Cell_FACH state than Idle.
RB Parking will increase the load of FACH DCCH , so if the FACH DCCH of Cell has been congested
seriously before ,its not recommended to activate RB Parking .
Huawei Confidential
Page 150
Dependency
Dependency on features
Its recommended to cooperate with loose admission control of RRC request and strict
admission control of RAB request. If the RRC admission is strictly controlled, many service
request will be rejected in RRC phase and could not come into RB Parking procedure.
Depends on WRFD-021101 Dynamic Channel Configuration Control
Impacted Features
None
If RB Parking is activated ,the PS RAB setup on DCH 0kbit/s will be invalid.
License
An optional feature with new License of RNC level in R16
Huawei Confidential
Page 151
Verification
Counter
Description
Number of Successful Parking Triggered by F2D AccessFail for Cell

VS.F2DAccessFail.Parking
VS.RAB.SuccEstabPS.Parking.0kb Number of PS Parking RABs Established Successfully at 0 kbit/s in the
Best Cell
ps
Number of PS Parking User Normal Release for Cell
VS.RAB.NormRelPS.Parking
VS.RAB.AbnormRelPS.Parking
Number of PS Parking User Abnormal Release for Cell
VS.CellFACHUEs.Parking.Mean
Number of Parking UEs in CELL_FACH State for Cell
VS.PSPreempted.D2F.Att.Parking Number of PS BEs try to enter Parking due to be preempted

VS.PSPreempted.D2F.Succ.Parkin Number of PS BEs successfully enter Parking due to be preempted
g
Huawei Confidential
Page 152
Verification
Benefit Observation
In Big Event scenarios
PS RAB Setup Successful Rate :
PS RAB Setup Failure Rate due to congestion: Decrease
PS Call Drop Rate : Decrease
CS Users and Traffic : Increase
Increase
Huawei Confidential
Page 153
Camping Strategy Switch for Mass Event
RB parking
Automatic Congestion Handler WRFD-160253
Huawei Confidential
Page 154
Background
Unplanned Event(congregation, parade, carnival) is indeterminism and can not be
made deployment and optimization in advance.

WRFD-160253 Automatic Congestion Control(ACH) supplies an automatic mechanism
to optimize the network configuration when unplanned event is happened.

The solution goals of this feature
Simplify deployment and maintenance
Coordinate congestion-release action and improve the resource efficiency in
Unplanned or Planned event.
ACH is a feature located in the RNC with cell level switch.

Huawei Confidential
Page 155
Introduction 1/4
ACH monitors load-related measurement quantities of the cell and performs
corresponding actions when the measurement quantities meet certain
requirements.
CS RAB CAC Optimization

PS RAB unconditionally preempted
FACH max user No. increased to 60
DL NonH power status

UL actual load
DCH User No.
R99 Initial Rate limitation
N300/T300 parameter Optimization

RRC release wait time parameter
optimization
Notes:
1st and 2nd congestion actions are ACTION_WITH_LOAD : triggered when congestion and fall back when recovery.
Normal status actions are ALWAYS_ON : default recommended, no fall back once activation
Huawei Confidential
Page 156
Introduction 2/4
There are several rules for one action.
The actions can be activated/deactivated separately by enable/disable related
rules.
Action: N300/T300 optimization
No.
Rule
Rule When the downlink power load of a
1
cell enters the second-level
congestion state or the uplink power
Rule load of a cell enters the congestion
state, N300 is set to 1 and T300 is
2
set to D2000.
Rule When the downlink power load of a
cell exits the second-level congestion
3
state and the uplink power load of a
cell exits the congestion state, N300
Rule
and T300 are reset to their original
4
values.
Conditions
If [DL Non-H power
status]>=DL_HEAVY_STATE during a
time to trigger
If [Actual Load] >= 7dB and [DCH User
No.] >= 35 during a time to trigger
If [DL Non-H power status] <=
DL_LOADED_STATE and [Actual Load]
<= 4dB during a time to trigger
If [DL Non-H power status] <=
DL_LOADED_STATE and [DCH User
No.] <= 25 during a time to trigger
Executive Actions
Action="MOD UCELLIDLEMODETIMER:
CellId=$CELLID$, T300=D2000,
N300=1"
Action="MOD UCELLIDLEMODETIMER:
CellId=$CELLID$, T300=D2000,
N300=1"
T300/N300 is recovery to its original
value.
ActionType=RESUME_CFG_DATA
T300/N300 is recovery to its original
value.
ActionType=RESUME_CFG_DATA
Note: Here, the thresholds are configurable ,such as DL_HEAVY_STATE,7dB ,35 ,etc.
Huawei Confidential
Page 157
Introduction
3/4
Solution
Action
High
Optimization of N300/T300
traffic Adjustment of wait time to
events 15s
Initial Rate limitation
Trigger
Type
Category
DL nonH power / UL actual load and DCH Number Parameter ACTION_WITH_LOAD
HSUPA User No. limitation

CS redirected to GSM
UL actual load and DCH Number

Parameter ACTION_WITH_LOAD
CS
CS RAB CAC Optimization
absolute PS RAB unconditionally
first
preempted
Switch on preemption
function
CS RRC Preemption
Preemption when SPU CPU
high load
P2D CS preemption
DL nonH power / UL actual load and DCH Number Function

ALWAYS_ON
ALWAYS_ON
ALWAYS_ON

ALWAYS_ON
ALWAYS_ON
ALWAYS_ON
Huawei Confidential
Page 158
Introduction
4/4
Solution
Function
FACH FACH max user No. increased to 60
congesti P2D when FACH user No. reaches max
on
P2D based on traffic volume measurement
solution
DL Data Transmission Suspension When F2D
UL Data Transmission Suspension When F2D
F2P signaling slimming
Trigger
FACH User Number
FACH User Number
FACH User Number
FACH DTCH congestion status Function

FACH DTCH congestion status Function
FACH User Number
Function
ACTION_WITH_LOAD
ACTION_WITH_LOAD
ALWAYS_ON
OpCo RxLevMin reduction rule

optimiza Uncap the HSDPA user number limit
tion
suggesti Protect Node B and RNC from excessive RRC
on
management: CAPS.
WRFD-150230 DPCH pilot power adjustment
UL ROT and DCH Number

DCH Number
Parameter
Parameter
ACTION_WITH_LOAD
ALWAYS_ON
DCH Number
Function
ALWAYS_ON
DCH Number
Feature
ACTION_WITH_LOAD
Huawei Confidential
Type
Parameter
Function
Function
Page 159
Category
ALWAYS_ON
ALWAYS_ON
ALWAYS_ON
Benefit and Impact
Benefit:
Automatically relieve the congestion in scenarios where unplanned events occur, thereby reducing the
operation and maintenance workload. And improve system stability and optimize system performance.
Network Impact:
The network impact of this feature depends on how many functions and which functions under this
feature are enabled. The expected benefits and network impact when all functions are enabled are as
follows:
System capacity
In cell congestion scenarios, congestion relief actions help reduce cell load and improve the efficiency of
resource utilization. This feature also helps improve the cell capacity when there are sufficient services.
Functions under CS Preference improve the CS Erlangs but reduce the PS traffic volume in congestion
scenarios.
Improve the utilization of FACH resources and therefore the system capacity.
Network performance
If CS admission fails before this feature is enabled, the CS access success rate significantly increases after
this feature is enabled. However, the PS call drop rate also increases when PS or CS preemption occurs.
Huawei Confidential
Page 160
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Huawei Confidential
Page 161
UMTS Uplink narrowband Interference Detection IntFD-160033
Interference Rejection Combining (IRC)
Huawei Confidential
Page 162
Interference Detection Efficiency is Improved by 20 Times
Interference
Detection
Procedure
Data collection
Interference
Locating
Report Output
Analysis
Data collection
Frequency point, bandwidth,
Interference of each cell
Report output
strength of interference in each cell
interference
Manual
Method
0.25 Day
Chart output
displayed on map
Locating with geographic
Time interval of
Interference
Detection
Step 4
Step 2
Frequency Domain Analysis
Cells with strong inference
Automatic
Step 3
Step 1
Time Domain
0.4 Day
info.
0.2 Day
0.15 Day
This feature belongs to service solution depending on NASTAR server. All the procedures are automatic except for some
confirmation operations.
5 Days
8 Days
4 Days
1 Days
20X
20X
3 Days
20 Days
This method involves lots of manual operations with basic tools, such as Excel, Mapinfo.
Note: the days above are manual intervention
time
Huawei Confidential
Page 163
Dependency
Nastar
U2000
Check
Check the
the Time
Time
Domain
Domain Result
Result
Analysis
Start
Start
Frequency
Frequency
Domain
Domain
Analysis
Analysis
NE
details is described on product manuals .
NE
U 2000
NE
Analysis
Start
Start Time
Time
Domain
Domain
Analysis
Analysis
Frequency Domain
Nastar
Operator
Time Domain
Dependency on NEs
Depends on some type of RRUs , and the
RNC
None
NodeB
License
Check
Check the
the
Frequency
Frequency
Domain
Domain
Result
Result
This is a OSS feature and with License control on Nastar .
Huawei Confidential
Page 164
Output
Output
the
the
Interferen
Interferen
ce
ce Report
Report
UMTS Uplink narrowband Interference Detection
Interference Rejection Combining (IRC) WRFD-160250
Huawei Confidential
Page 165
Background
UMTS is an interference-limited system, so interference of various types affects the capacity of a UMTS system.
The following table describes problems related to interference.
Interference Type
Cause
Inter-path interference
Interference occurs during despreading for UEs using multipath

radio channels.
Example
Solution
Inter-path interference occurs as long as services are transmitted
on multipath radio channels and can be neglected if the service
FDE
rates are low.
Intra-cell interference (also called inter-user UEs in a cell cause interference to a UE in the same cell for which
interference)
despreading is performed.
Interference from neighboring cells (also
called inter-cell interference)
External
interference
When despreading is performed for a UE in a cell, UEs in cells

adjacent to the cell cause interference to the UE.
Interference from foreign

Other systems cause interference.
systems
Interference from
Interference sources in environments cause interference.
external sources
IC, IRC (not recommended)
Common interference from neighboring cells; strong interference Anti-interference scheduling, UL

of macro cells to micro cells in HetNet scenarios
CoMP, IRC
Interference from GSM/CDMA 2000 systems or repeaters
Interference from car engines or TV amplifiers
Anti-interference scheduling, NBIS,

IRC
Anti-interference scheduling, NBIS,
IRC
On macro networks, IRC primarily suppresses external interference; on macro and micro combined networks, IRC
can be enabled for micro cells to suppress interference from neighboring cells.
Narrowband
Statistics about
Broadband
types of
interference
occurred in an area
(number of trouble
tickets is provided) Inter modulation
37
3
4
2
5
External interference
GSM
About 1M
Interference from CDMA systems
Overall spectrum
Huawei Confidential
Interference occurred in a
cell (the number of UEs in
the cell is less than 1, and
RoT is greater than 7 dB).
Page 166
Introduction
IRC is implemented on baseband boards of NodeBs.
Each of UBBPd1 to UBBPd4 boards can provide IRC for 128 UEs, and either of UBBPd5 and UBBPd6 boards
can provide IRC for 256 UEs. IRC cannot be used in dual-mode concurrence scenarios.
IRC can be considered as a type of receiver.
Similar to RAKE/FDE receivers, IRC receivers fully use information contained in interfering signals.
If interfering signals are not correlated, IRC receives degenerate to RAKE or FDE receivers. IRC receivers are
generally considered as an improved version of RAKE/FDE receivers.
Based on the maximum SINR principle, IRC receivers consider the space and time correlation between
interfering signals (especially the space correlation) and achieve optimal performance.
Receiver Type
Applicable Scenario
RAKE
Low service rates + interference not

considered
FDE
High service rates + interference not

considered
RAKE+IRC
IRC
FDE+IRC
Low service rates + interference

considered
High service rates + interference
considered
Huawei Confidential
Page 167
Typical Scenarios
IRC applies to the following scenarios:
GU refarming scenarios
Scenarios with poor-quality repeaters
Scenarios with strong interference from foreign systems or external resources
Micro cells in HetNet scenarios
IRC is not applicable to the following scenarios:
Single-antenna scenarios
Scenarios with three or more interference sources that generate interference almost at the same
strength
Huawei Confidential
Page 168
Benefits and Impacts
Feature Benefits
When the ratio of interference to the background noise (I/N) is equal to or greater than 3 dB, the number of
connections increases by 5% to 15%.
The following illustrations assume that a network servers only burst users who use 7 kbit/s HTTP services and that
there is only one type of interference. If the I/N ratio is about 1 dB and the interfering users use the same channel as
the burst users, the throughput increases by about 7% after IRC is enabled.
Impacts on Network
Impact on the System Capacity
When the I/N ratio is equal to or greater than 3 dB, the number of connections increases by 5% to 15%.
Impact on the Network Performance
None
Huawei Confidential
Page 169
Dependency
Dependency Features
NodeBs must be configured with UBBPd boards.
Requirements for Other NEs
If the Independent Demodulation of Signals from Multiple RRUs feature is enabled, IRC does not take effect.
If the Cell Digital Combination and Split feature is enabled, IRC can be enabled but its algorithm does not take effect.
If both IRC and WRFD-150206 Turbo IC are enabled, Turbo IC can perform only one interference cancellation. As a result, IRC may be mistakenly enabled, and the gains of
Turbo IC decrease.
If both IRC and WRFD-140225 Narrowband Interference Suppression are enabled, the gains of IRC decrease because both features can suppress narrowband interference.
WFRD-151205 Uplink CoMP (Joint Reception), WFRD-151206 HetNet Uplink CoMP (Joint Reception), and WFRD-151207 Uplink CoMP (Joint Reception) Based on
Coordinated BBU. Because UL CoMP considers interfering signals from neighboring cells as the signals sent to the serving cell, the gains of IRC decrease. However, the
gains of IRC in suppressing external interference do not decrease. (Note: IRC is used to suppress external interference and interference from neighboring cells.)
WRFD-150238 AAS. An AAS used in this feature servers neighboring cells with small coverage. Therefore, this also reduces the opportunity for IRC to take effect. However,
the gains of IRC in suppressing external interference do not decrease. (Note: IRC is used to suppress external interference and interference from neighboring cells.)
Requirements for Hardware
None
Impacted Features
None
None
Requirements for licenses
This is a trial feature in R16.0 without License control.
Huawei Confidential
Page 170
Verification
Counter Name
Description
VS.IRC.ColouredInf.Num
Number of occurrences of interference in a cell (internal counter, not presented to customers)
VS.IRC.StrongColouredInf.Nu
m
Number of occurrences of strong interference in a cell (internal counter, not presented to

customers)
VS.IRC.UserNum
Average number of UEs using IRC in a cell
Benefit Observation
Obtain the counters one week before and after IRC is enabled and compare the data. This feature meets
expectations if one of the following conditions is met:
This condition applies when the occurrence of the actual RTWP exceeding the target RTWP is less than 30% in
terms of time.
When the target RoT is greater than or equal to 6 dB and smaller than or equal to 7 Db, the value of
VS.HSUPA.Thrput.ROTMor7 divided by VS.HSUPA.DataTtiNum.ROTMor7 increases by 5% to 15%.
When the target RoT is greater than 7 dB, the value of VS.HSUPA.Thrput.ROTMor9 divided by
VS.HSUPA.DataTtiNum.ROTMor9 increases by 5% to 15%.
This condition applies when the occurrence of the actual RTWP exceeding the target RTWP is greater than 30% in
terms of time.
When the RTWP remains the same after IRC is enabled, VS.HSUPA.UE.Mean increases by 5% to 15%.
Huawei Confidential
Page 171
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Huawei Confidential
Page 172
UMTS SON Solution
Adaptive RACH WRFD-151201
Huawei Confidential
Page 173
Background
Adaptive RACH enables the RNC to dynamically adjust the settings of random access parameters for a cell
based on the uplink power load and number of acknowledged random accesses in each second. This feature
can reduce the received total wideband power (RTWP) of a cell and increase its capacity.
When a large number of UEs simultaneously initiate a random access procedure in a cell, the RTWP of this cell
becomes extremely high and the high RTWP affects the uplink capacity and uplink throughput. To reduce the
RTWP in this case, the settings of random access parameters are adjusted manually before Adaptive RACH is
introduced. However, when the traffic load of the cell becomes light, using the optimized settings of random
access parameters prolongs the delay during random access and affects the network performance. Therefore,
settings of random access parameters need to be dynamically adjusted based on the cell load.
Reduced RTWP after Adaptive RACH is enabled
Huawei Confidential
Page 174
Introduction
The RNC dynamically adjust the settings of random access parameters for a cell in the following ways:
When the cell uplink load is greater than the value of the OptiStartLoadState parameter and the
number of acknowledged random accesses in a cell is greater than the value of the
RandomAccessCongestThd parameter, the RNC broadcasts the optimized settings of random access
parameters (OptiConstantvalue, OptiPowerRampStep, and OptiPreambleRetransMax) to UEs.
This reduces the interference to uplink channels brought by random accesses and therefore reduces the
RTWP.
When the number of acknowledged random accesses is less than or equal to the value of the
RandomAccessClearThd parameter, the RNC broadcasts the original settings of random access
parameters (Constantvalue, PowerRampStep, and PreambleRetransMax) to UEs to reduce the
delay during random access.
Huawei Confidential
Page 175
Benefits and Network Impact
Benefits
When the RTWP of a cell is high due to a large number of random accesses, Adaptive
RACH helps reduce the RTWP by 0.3 dB to 0.5 dB.
Network Impact
Impact on the system capacity

When the RTWP of a cell is high due to a large number of random accesses, Adaptive
RACH helps reduce the RTWP or increase the uplink throughput.

Impact on the network performance
This feature lowers the ramping step for random access preambles and therefore
prolongs the delay during random access. However, the delay is increased only by
tens of milliseconds, which does not significantly affect user experience.
Huawei Confidential
Page 176
Dependency
The BTS3812E, BTS3812A, and BTS3812AE do not support this feature.

The DBS3800 does not support this feature.
3900 series base stations configured with a WBBPa board do not support this feature.
Dependencies on Other NEs
None
None
Impacted Features
None
None
License
The cell-level license Adaptive RACH on the RNC side.
Huawei Confidential
Page 177
Activation Verification
Method 1: Query SON logs
After this feature is activated, operating information about this feature will be recorded into selforganizing network (SON) logs.
To check whether this feature has been enabled, perform the following steps to query SON logs:
Step 1: On the M2000 client, choose SON > SON Log.
Step 2: On the displayed SON Log tab page, click Query SON Log. Set Log Category to Adaptive RACH
log and Event Name to Not Limited. In addition, specify Event Source Object and Time Period as
required.
Step 3: Click Synchronize in the bottom right corner of the SON Log tab page.
Step 4: Click Query.
If there is a record in the specified time period, this feature has taken effect. If there is no
record in the specified time period, this feature has not taken effect. In this case, check
whether the cell meets the requirements for this feature.
Huawei Confidential
Page 178
Method 2: Run the MML command DSP UCELLCHK
To check whether this feature has been enabled, run the MML command DSP UCELLCHK. The
meanings of the command outputs are as follows:
Optimized: Adaptive RACH has been triggered in the cell and the optimized settings of random access
parameters are used.
Not started: Adaptive RACH has not been triggered in the cell and the original settings of random access
parameters are used.
To be stopped: The cell meets the requirement for stopping the Adaptive RACH feature and is in the hysteresis
duration for stopping the adaptive RACH feature.
Triggering conditions met
Optimized
Not started
Triggering conditions met

Tstop timer expired
Triggering conditions not met

To be stopped
Huawei Confidential
Page 179
Counters
The VS.Random.Access.ACKNum.Mean counter is added to provide the average number of

acknowledged random accesses in a cell.
Counter
Measurement
Object
Unit
Description
Measurement Point
When receiving from the NodeB a COMMON MEASUREMENT REPORT
message about the acknowledged PRACH preambles, the RNC obtains
Average
VS.Random.
Access.ACK
the number of acknowledged random accesses in the cell. The
number of
CELL
None
Num.Mean
acknowledged
random
accesses
measurement includes the acknowledged random accesses on the

RACH and ERACH. At the end of the measurement period, the RNC
divides the accumulated value in the period by the number of received
measurement reports to obtain the average number of acknowledged
random accesses.
Huawei Confidential
Page 180
To evaluate the performance of this feature, check whether the RTWP of each cell decreases.
The RTWP of a cell changes with the cell load. Therefore, the changes in RTWP in a short period
of time after this feature is activated cannot reflect the performance of this feature. You are
advised to check the RTWPs in N days (N=3 to 5) before and after this feature is activated.
The RTWP of each cell can be checked in the following ways:
Counters VS.MaxRTWP and VS.MeanRTWP on the RNC side

Counters VS.HSUPA.LoadOutput.0 to VS.HSUPA.LoadOutput.25 on the NodeB side
Huawei Confidential
Page 181
Application Cases
Test result of live network in Kuwait
After activating Adaptive RACH, the RTWP of all cells decrease, and the RTWP of high-load
cells significantly decreases by 0.3~0.5dB. Other KPIs such as Call Drop Rate are not
impacted
Huawei Confidential
Page 182
Content
1
Summary of RAN16.0

UMTS HD Voice




UMTS SON Solution

Huawei Confidential
Page 183
MOCN Cell Resource Demarcation WRFD-140223
MOCN Independent Iub Transmission Resource Allocation
Huawei Confidential
Page 184
Background
Before RAN14.0,MOCN cell total downlink power is fully
Operator A's CN
Operator B's CN
MSC
SGSN
MSC
SGSN
shared between operators.

RAN14.0 introduce the HSDPA power demarcation
between operators.
RAN16.0 introduce the cell total downlink power
(including HSDPA and DCH ) demarcation between
RNC
operators.
NodeB
Operator B
Operator C
Operator A
Operator D
Operator A
Operator C
Operator D
Operator B
Cell downlink power fully shared
Cell downlink power dynamic demarcation
Ensure fair sharing of the cell downlink power between operators..

Huawei Confidential
Page 185
Introduction
The MOCN Cell Resource Demarcation feature provides the following functions to ensure equal sharing of
cell resources among operators :
Resource Percentage Configuration for each operator;
Access control & preemption : prevent one operator access more users.
Congestion control: choose the user of the operator who occupied excess resource to do the LDR
firstly
Nodeb scheduling: adjust the scheduling priorities between the operators according to the predefined
percentage and actually usage.
Operator A's
CN
Cell Resource
Release
R99 SF code
WRFD-140223 MOCN cell

resource demarcation
HSDPA power
Total DL power
(R99&HSDPA)
Processing on the
NodeB:
scheduling
Processing on the
RNC:
1. Access
2. Preemption
3. Congestion control
Operator B's
CN
Huawei Confidential
WRFD-140223 MOCN cell

resource demarcation
enhance (RAN16)
Total DL power contain the power which can

be consumed by R99 DCH and HSDPA , except
CCH.
Page 186
Impact
Benefit
When each operators users have power resource requirement and cell DL power is insufficient ,
the MOCN Cell Resource Demarcation feature ensures that the resource usage of every operator
close to the predefined percentage,which avoids unequal resource sharing among operators.
Check the counter VS. DLDCHPwrRatio.SharedOperator0+ VS.HSDPAPwrRatio.SharedOperator0 :

VS.DLDCHPwrRatio.SharedOperator1+ VS.HSDPAPwrRatio.SharedOperator1 close to predefined DL
power ratio.
Negative Impacts
RNC is more likely to trigger preemption and the call drop rate may increase in heavy load cell if
any operator uses more DL power resources than its predefined resource percentage.
Huawei Confidential
Page 187
Dependency
The NodeB must be equipped with UBBPd board for the DL total power demarcation function.
Depends on WRFD-021311 MOCN Introduction Package feature .
License
An optional feature enhancement in RAN16.0

Feature ID
Feature Name
License Control NE
Item
WRFD-140223 MOCN Cell Resource
Demarcation
MOCN Cell
Resource
Demarcation(per
cell)
RNC
Huawei Confidential
Sales Unit
Cell
Page 188
Verification
Availability & Effect Observation
Counter ID
VS.DLDCHPwrRatio.SharedOperator0
Description
counter the DL DCH power ratio of shared operator 0
VS.DLDCHPwrRatio.SharedOperator1 counter the DL DCH power ratio of shared operator 1

VS.MeanTCPRatio.NonHS
counter the non HSDPA transmitted carrier power ratio
Huawei Confidential
Page 189
MOCN Cell Resource Demarcation
MOCN Independent Iub Transmission Resource Allocation WRFD150213
Huawei Confidential
Page 190
Background
Before RAN16.0
If the sum of each logical port bandwidth exceed the physical port bandwidth, the fairness
between operator cannot be guaranteed;
From RAN16.0
The feature enhancement in RAN16.0 will resolve this issue.
If one Operators private leaf logic port comes
Physical linkHub logical
to congestion, only this operators user plane rate

will be limited.
If NodeBs convergence logic port comes to
congestion, then all the operators user plane rate
will be limited to the ratios of configuration
Huawei Confidential
port Leaf logical

port
Paths or Adj nodes for

OPA
Paths or Adj nodes for
OPB
OPA Private Bandwidth
OPB Private Bandwidth
NodeB
Bandwidth
Page 191
Impact
Benefits
This feature allocates Iub transmission resources to operators in MOCN scenarios, preventing
one operator from occupying excess Iub transmission resources and ensuring that each
operator retains independent Iub transmission resources.
Negative Impact
This feature slightly decreases Iub resource utilization. If the Iub resources are not properly
allocated (for example, insufficient Iub bandwidth is allocated to an operator), this feature
brings some negative effects, such as access performance deterioration (for example, a
decrease in the RRC setup success rate and RAB setup success rate) and HSUPA throughput
decrease.
Huawei Confidential
Page 192
Dependency
None

This feature cannot be used together with the feature WRFD-140208 Iub Transmission
Resource Pool in RNC or WRFD-02130501 Dedicated Iub Transmission Control.
Depends on WRFD-021311 MOCN Introduction Package
License
An optional feature enhancement in RAN16.0
Feature ID
Feature Name
License Control
Item
NE
Sales Unit
WRFD-150213
MOCN Independent
Iub Transmission
Resource Allocation
MOCN Independent
Iub Transmission
Resource Allocation
(per NodeB)
RNC
NodeB
Huawei Confidential
Page 193
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Huawei Confidential
Page 194
Uplink CoMP (Joint Reception) WRFD-151205 WRFD-151206 WRFD151207
Service Steering and Load Sharing in CELL_FACH State
Huawei Confidential
Page 195
UMTS Uplink CoMP (Joint Reception)

Coordinated Links, only Uplink
RNC
The Radio links of the

UEs between RNC and NodeB
R
X
R
X
R
X
R
X
Links of Cells in active set

both Uplink and downlink
BB : Only one BBU

Or
Cloud BB: Multi BBU with
USU
NodeB 2
NodeB 1
R
X
Application
Scenarios
in Inter NodeB scenario ,
Links of Cell in active set in Intra NodeB scenario ,

R
X
R
X
R
X
R
X
R
X
Macro Cell
Macro Cell
Or
Cell 1
Cell 2
Cell 3
Intra NodeB UL CoMP
Cell
4
Cell 5
Micro cell
Or
Inter NodeB UL CoMP
Improve the reception performance to improve the system UL

capacity.
Improve the user throughput at the cell edge.
Micro cell
Macro Cell
Micro cell
Macro Cell: With the Normal RRU, and Normal Power

Configuration
Micro Cell: With the micro Power Configuration of Normal RRU
Page 196 micro power configuration )
(V3 type RRU can support
Technology Theory
Key Inforamtion
1 UL CoMP will consume more uplink resources , and it use the hardware resource to gain the
performance of air;
2 We can take the UL COMP as the technology between the Soft and Softer handover. The best
performance is that 4RX with neighbor cells ,and the neighbor cells can control the interference of
this signal.
3 UL COMP can be used with other receiving technology of multi antenna .
The Difference of ULCOMP with soft/softer handover
1 Only uplink link in the coordinated Cell , without downlink link.

2.
The addition and remove of coordinated link does not use the standard signaling ,and RNC &
UE do not feel.
-
The key solution
1 How to trigger the establishment and remove of coordinated links. The Searching and
measurement of uplink .
2 How to transfer the coordinated combined signaling Combined signaling of Intra Chip /Inter
Chip /Inter-BBU
Page 197
Technology Theory
Links of Cells in active set in Intra NodeB scenario ,
Coordinated Links, only Uplink

The Radio links of the
UEs between RNC and NodeB
RNC
R
X
R
X
Cell 1
R
X
R
X
Cell 2
Softer HO
R
X
R
X
R
X
Cell 3
Cell 4
Soft HO
R
X
R
X
R
X
Cell 5
R
X
NodeB #2
NodeB #1
NodeB #2
NodeB #1
RNC
Links of Cells in active set in Inter NodeB scenario ,

R
X
R
X
Cell 6
4Rx
R
X
R
X
Cell 1
R
X
R
X
R
X
Cell 2
Intra site UL COMP
R
X
R
X
Cell 3
R
X
R
X
Cell 4
R
X
R
X
Cell 5
R
X
R
X
R
X
Cell 6
Inter site UL COMP
Current: new Receiving technology of Multi Ant

fore Receiving technology of Multi Antenna
UL COMP Inter Site and Intra Site
Rx, Softer HO, Soft HO
Page 198
WRFD-151205 Uplink CoMP (Joint Reception)

WRFD-151206 HetNet Uplink CoMP (Joint Reception)
WRFD-151207 Uplink CoMP (Joint Reception) Based on Coordinated BBU
1. Change soft
handovers to
softer handovers
in inter-site cells
2. Extend uplink
soft handover
area from (3 dB,
6 dB) to (6 dB, 9
dB)
Scenario 1-1: Balanced

uplink load in neighboring
cells
Scenario 1: Single
macro sites
Scenario 1-2: Imbalanced
cells
Scenario 2-1: Balanced
cells
Scenario 2: Macromacro/Micro-micro sites Scenario 2-2: Imbalanced
cells
Scenario 3: Macro-micro
Y (major benefit)
softer handover
Scenario 4: Combination
of scenarios 1, 2, and 3
General Scenario
Specific Scenario
sites
3. Prompt uplink soft

handovers (in advance of
downlink soft handovers)
and suppress
interferences from
neighboring cells
Y
4. Alleviate interference
on uplink coordinating
links by neighboring
cells (Interference
cancellation and HSUPA
scheduling)
Y
Y (major gain point)
Y (major gain
point)
Y (major gain point for

R99 services)

HSUPA services)

R99 services)
Y

HSUPA services)
Y
Huawei Confidential
Page 199
Impact
Benefits
In macro-macro cells, UL CoMP increases the average uplink capacity by 3% to 7.8% and
uplink cell edge user (CEU) throughput by 10% to 15%. when both WRFD-151205 and WRFD151207 are enabled, UL CoMP increases the average uplink capacity by 6% to 10% and uplink
cell edge user (CEU) throughput by 10% to 20%.
In macro-micro cells where the number of macro cells is equal to that of micro cells, UL CoMP
increases the average uplink capacity by around 3% to 5% and uplink CEU throughput by
around 16% to 45%.
The cell edge user throughput increased when the UE transmit power limited.
Page 200
Dependency
Dependency On Features

-- None

-- None

This feature depends on WRFD-151205 Uplink CoMP (Joint Reception) and WRFD-151206 HetNet Uplink CoMP (Joint
Reception).
-- Only when this feature works along with WRFD-151205 Uplink CoMP (Joint Reception), macro-macro or micro-micro cells
connected with each other by BBUs can obtain UL CoMP gains.
-- Only when this feature works along with WRFD-151206 HetNet Uplink CoMP (Joint Reception), macro-micro cells
connected with each other by BBUs can obtain UL CoMP gains.

WRFD-151205 Uplink CoMP (Joint Reception), WRFD-151206 HetNet Uplink CoMP (Joint Reception), and WRFD-151207
Uplink CoMP (Joint Reception) Based on Coordinated BBU are mutually exclusive to the following features:
WRFD-021308 Extended Cell Coverage up to 200km
MRFD-210309 DBS Topology Maintenance
Huawei Confidential
Page 201
Dependency
Impacted Features
WRFD-151205 Uplink CoMP (Joint Reception) None
WRFD-151206 HetNet Uplink CoMP (Joint Reception) None

In macro-micro scenario, the WRFD-151206 HetNet Uplink CoMP (Joint Reception) and WRFD-150201 Macro & Micro
Co-carrier Uplink Interference Control have contradictory effects. These two features are not advised to be enabled at
the same time. In addition, gains of WRFD-151206 HetNet Uplink CoMP (Joint Reception) are higher than that of WRFD150201 Macro & Micro Co-carrier Uplink Interference Control, so preferentially enable WRFD-151206 HetNet Uplink
CoMP (Joint Reception).
Dependency on NEs
None
Huawei Confidential
Page 202
Dependency
Dependency On Hardware
To support this feature, the base station must be configured with the UBBPd board. If a cell is set up on the baseband board and serves only
as a coordinating cell, the cell will be counted as a cell as the regular cell.
Only BTS 3900 Series support
To support this feature, the base station must be configured with the UBBPd board. If a cell is set up on the baseband board and serves only
as a coordinating cell, the cell will be counted as a cell as the regular cell.
To support this feature, the base station must be configured with the UBBPd board and the UMPT board.
This feature depends on the used service unit (USU).
The Primary Cell and Coordinating cells must be configured as double or four antennas at the same time.
License
A NodeB-level license has been added for this feature to provide cell-level or NodeB-level management.
FeatureID
Feature Name
License Control Item
NE
Sales Unit
WRFD-151205

HetNet Uplink CoMP (Joint
Reception)
Based on Coordinated BBU
Node B
per Cell
HetNet Uplink CoMP (Joint Reception)
Node B
per Cell
Uplink CoMP (Joint Reception) Based on

Coordinated BBU
Node B
per NodeB
WRFD-151206
WRFD-151207
Huawei Confidential
Page 203
UMTS HetNet Micro BTS SolutionSolution
Marco & Micro RRUs in One Cell WRFD-151208
Huawei Confidential
Page 204

Multi RRUs in one cell
BBU
Macro
RRU1
Micro
RRU2
Micro
RRU3
Macro
RRU4
Independent de-modulation
Less interference for each other
Benefits
Make it possible to deploy soft cell by macro and micro cells.

Reduce the number of handover
Reduce the deployment time of micro cells in dependence, about 2
hours.
Huawei Confidential
Page 205
The Backgroud of Marco & Micro RRUs in One Cell

The example scenarios
Multi RRUs in one

Cell
Cell #1
RRU 1
RRU2
Cell #3
RRU3
Site Coverage
Some mini blind spots appear among the
Cell #2
BBU
Siteblind
Coverage
spot
normal coverages
Cell #3
Site Coverage blind
spotSite Coverage
RRU4 with micro power

configuration
Leak coverage due to the lack of site ,such as the
Linked one more RRU

for the blind spot to
enrich the coverage
site can not be implemented in some spot.
The 2 RRUs (RRU3 and RRU4) in one cell does not generate new carrier
The blind spot is mini coverage .
and scramble code ,and it can be used to blind spot coverage in the
High cost of new site close to the blind spot .
dense urban or urban .
Huawei Confidential
Page 206
The key technology of feature
The problem need to be solved
Digital attenuation Reduces the RTWP of
High RTWP due to too little MCL

The Max scale of UE power control is -50~24dBm,
low-power RRUs to unify the ground noises of RRUs in a cell.
according to 3GPP, so when the MCL is too little , the

uplink background noise will rise remarkably since the
UEs power can not decrease any more than -50dBm by
the inner loop power control.
High initial power of UE in

Micro RRU cause high RTWP
Digital attenuation and desensitization eliminate the

uplink interference due to the different power of macro
The CPICH power information of SIB5 is the one from

the highest power RRU in cell.
and micro RRU , and improve the performance .
Digital desensitization Increases the
The PRACH and DPCH are with open loop power control,
when the actual CPICH power of Micro RRU is xdB lower
than SIB5, the initial PRACH and DPCH power of UE in Micro
RRU will be xdB higher than the Marco RRU coverage ,
which will come to interference to uplink .
background noises and therefore decreases the uplink signal-to-noise

ratio (SNR) of low-power RRUs to reduce interference from high-power
RRUs in neighboring cells.
Huawei Confidential
Page 207
Dependency
Dependency On Features
WRFD-010203 Transmit Diversity

WRFD-010209 4-Antenna Receive Diversity
WRFD-010684 2x2 MIMO
WRFD-021308 Extended Cell Coverage up to
WRFD-010692 HSUPA FDE
WRFD-010701 Uplink Enhanced CELL_FACH
WRFD-010205 Cell Digital Combination and Split
0.5/0.5 Configuration
Impacted Features
None
Huawei Confidential
Page 208
Dependency
Dependencies on UEs
Only the DBS3900 with WBBPb, WBBPd, or WBBPf boards installed supports this feature.
RRU3824, RRU3826, RRU3828, RRU3829, RRU3926, RRU3928, and RRU3929 can be configured as either high-power or low-power
RRUs in a cell because they support digital attenuation and desensitization.
Other RRU models do not support digital attenuation or desensitization and therefore can be configured as high-power RRUs only. If
such an RRU is configured as a low-power RRU, the RNC reports ALM-28206 Local Cell Capability Decline.
RRU3821Es, RFUs, and AASs do not support this feature.
None
License
An RRU- and cell-level license control item has been introduced on the NodeB side for
this feature.
Huawei Confidential
Page 209
Macro-Micro DC-HSDPA WRFD-151209
Huawei Confidential
Page 210
Double the Peak Rate to 42 Mbps
Macro and Micro cells must
setup within the same base
band board.
42M
28M
21M
SC+64QAM
CPRI
DC+16QAM
DC+64QAM
CPRI
Improve the Cell Throughput 5% ~ 10%

Secondary Carrier
Primary Carrier
f1
f2
Huawei Confidential
Page 211
Background
In a network with macro and micro cells, DC-HSDPA UEs cannot use the DC-HSDPA feature even
when this feature is enabled in the network, which affects user experience.
F1
F1
DC
F1
DC
F2
F2
In a network where macro and micro cells

operate at different frequencies, UEs in the micro
cell cannot use the DC-HSDPA feature.
In a network where macro and micro cells operate

at the same frequency, UEs in the micro cell
cannot use the DC-HSDPA feature.
The Macro-Micro DC-HSDPA feature enables UEs to use the DC-HSDPA feature in network with macro and micro cells by
choosing the proper primary and secondary cells. The macro and micro cells operate at different frequencies in the same
frequency band.
Huawei Confidential
Page 212
Application Scenario
Macro-Micro DC-HSDPA requires:
Networks where macro and micro cells operate at different frequencies in the same frequency band.
In the area covered by both the macro and micro cells, the DC-HSDPA UE can use the DC-HSDPA
feature.
The coverage of the macro cell includes that of the micro cell.
Macro-Micro DC-HSDPA can be used together with Flexible Double Carrier HSDPA.
After a micro cell is enabled with Macro-Micro DC-HSDPA, this cell cannot use DB-HSDPA or 4C-HSDPA.
Huawei Confidential
Page 213
Impact
Single-user throughput
The downlink peak throughput of UEs at the center or edge of the macro or micro cell increases. The amount of the increase depends on the
channel quality of the cell.
When Macro-Micro DC-HSDPA is enabled, the downlink peak throughput of UEs increases. If the channel quality indicator (CQI) of the macro cell
is better than that of the micro cell, the increase is more than 100%; if the CQI of the macro cell is worse than that of the micro cell, the increase
is less than 100%.
After Macro-Micro DC-HSDPA is enabled, if 64QAM is used, the downlink peak throughput of a UE in the center of a micro cell increases by 21
Mbit/s theoretically. As a result, the transmission delay is reduced and user experience is improved.
Cell throughput
Macro-Micro DC-HSDPA does not reduce the total throughput of two inter-frequency cells, one of which is within the coverage of
the other.
Network Impact
A DC-HSDPA UE has the HS-DPCCH only in its primary cell. Therefore, the uplink load of a cell serving as a DC-HSDPA UEs primary cell is higher
than that of a cell serving as the SC-HSDPA cell. A DC-HSDPA UE needs to demodulate signals from primary and secondary cells, causing a 2 dB
increase in the HS-DPCCHs transmit power. As a result, the uplink load of the primary cell increases.
The ACK/NACK messages of both the anchor and supplementary carriers are sent in the primary cell in the uplink. Therefore, a DC-HSDPA UE
consumes one more channel element (CE) than an SC-HSDPA UE.
Huawei Confidential
Page 214
Dependency
Only 3900 series base stations (except the BTS3902E) support this feature. To support this
feature, the base station must be configured with the WBBPb, WBBPd, or WBBPf board.
The downlink baseband resources of macro and micro cells are provided by the same baseband
board.
Dependencies on UEs
Extended Cell Coverage up to 200 km
WRFD-010696 DC-HSDPA Introduction Package
None
License
A cell-level license control item (Macro-Micro DC-HSDPA) has been added to the NodeB for this
feature.
Huawei Confidential
Page 215
Dependency
Impacted Features
Macro-Micro DC-HSDPA is affected by the following features:
VoIP over HSPA/HSPA+
Macro-Micro DC-HSDPA cannot be used for a single voice over IP (VoIP) service.
Macro-Micro DC-HSDPA can be used for VoIP+PS BE or VoIP+streaming combined services.
CS voice over HSPA/HSPA+
Macro-Micro DC-HSDPA cannot be used for a single CS service.
Macro-Micro DC-HSDPA can be used for CS+PS BE or CS+streaming combined services.
WRFD-020134 Push to Talk
Macro-Micro DC-HSDPA cannot be used for a single push to talk (PTT) service.
Macro-Micro DC-HSDPA can be used for PTT+PS BE or PTT+streaming combined services.

Macro-Micro DC-HSDPA affects the following feature:
WRFD-150208 Flexible Double Carrier HSDPA

When Macro-Micro DC-HSDPA and Flexible Double Carrier/DB-HSDPA are used together, a micro cell only serves as a
candidate cell for flexible DC-HSDPA.
Huawei Confidential
Page 216
Service Steering and Load Sharing in CELL_FACH State WRFD150246
Huawei Confidential
Page 217
Background
In a multicarrier network configured with the preferential camping and service steering policy, UEs in idle mode or in the
CELL_PCH or URA_PCH state preferentially camp on a specific carrier. Adaptive multirate (AMR) services are established on this
carrier while packet switched (PS) services are redirected to other carriers. This ensures the voice quality of AMR services and
mitigates the impact of High Speed Packet Access (HSPA) services on AMR-related KPIs.
In versions earlier than RAN15.0, service steering is implemented through RAB DRD or FACH-to-HSDPA (F2H) DRD. However,
after micro cell deployment in a macro network, macro cells that previously had the same coverage now have the different
coverage, resulting in the decrease of DRD success rate. In this case, RRC redirection is used to implement service steering and
load sharing. With the introduction of smart phones and the solution to signaling storm, the number of UEs in the CELL_PCH
state increases but service steering cannot be performed for UEs in the CELL_PCH or URA_PCH state
To resolve the above issue, the Service Steering and Load Sharing in CELL_FACH State feature is used to implement service
steering and load sharing for UEs in the CELL_PCH or URA_PCH state through P2F-triggered redirection.
DRD
F3
F3
After the micro cell
deployment
micro cell
F2
F2
F1
F1
Huawei Confidential
RRC redirection
macro cell
P2F-triggered
Redirection for NRT
Services
Page 218
P2F-triggered
Redirection for RT
Services
Basic Concepts
Homogeneous interfrequency neighboring
cell
Heterogeneous attribute:
FALSE
Heterogeneous
inter-frequency
neighboring cell
Heterogeneous
attribute: TRUE
Homogeneous frequency
Heterogeneous
frequency
F3 macro cell
F2 micro cell
F2 macro cell
F1 macro cell
UE
P2F-triggered redirection
Coverage
area
Heterogeneous network is a network consisting of macro cells, micro cells, or inter-band cells.
Term
Definition
Example
Heterogeneous
inter-frequency
neighboring cell
Heterogeneous
frequency
Homogeneous
inter-frequency
neighboring cell
Homogeneous
frequency
An inter-frequency cell whose coverage differs from but

overlaps with the current cell
The F2 macro cell B and F2 micro cell b are heterogeneous interfrequency neighboring cells of the F1 macro cell A.
Frequency of a heterogeneous inter-frequency

neighboring cell
F2 is a heterogeneous frequency for the F1 macro cell.
Conventional neighboring cell for inter-frequency blind

handover
The F3 macro cell C is a homogeneous inter-frequency neighboring

cells for the F1 macro cell A.
Frequency of a homogeneous inter-frequency neighboring

F3 is a homogeneous frequency for the F1 macro cell.
cell
The macro cell A, B, and C of F1, F2, and F3 and F2 micro cell b
Coverage area
A group of cells within a certain coverage scope.
belong to one coverage area.
As shown in the figure, the F2 macro cell B is set to a
If there is a heterogeneous network in the coverage area,
heterogeneous cell, whereas the F3 macro cell C is not. P2Fcells
in
the
coverage
area
can
be
set
to
heterogeneous
Cell attribute
Huawei Confidential
Page 219selects F2 as the target
triggered redirection preferentially
(heterogeneous)
cells, which is identified as target cells for P2F-triggered
frequency so that the F2 micro cell b can absorb traffic from other
Benefits
Benefits
In a multicarrier network configured with service steering policy, the success rate of the PS RAB establishment and of F2H DRD decrease significantly
after the introduction of infra-frequency macro and micro combined network. Besides, UEs cannot be distributed to micro cells through the DRD.
P2F-triggered Redirection for NRT Services: redirects NRT services from a preferential camp frequency to a frequency at which micro cells operate. The
UE then selects a cell with good signal quality when the access success rate is relatively high in the infra-frequency macro and micro combined network.
P2F-triggered Redirection for RT Services After P2D Failures: redirects RT services from the preferential camping frequency to the frequency at which
micro cells operate in the case of resource congestion, improving the access rate of RT services.
P2F-triggered Redirection for RT Services: redirects AMR services from non-preferential camping frequencies to the preferential camping frequencies,
ensuring the user experience of AMR services and the effect of service steering.
Network Impact
Network Performance
Alleviate FACH congestion in the preferential camping cell.
Distribute UEs to micro cells.
Increase the service setup success rate.
Improve the user experience of AMR services.
This feature implements service steering through P2F-triggered redirection. Compared with P2F-triggered state transition, P2F-triggered redirection causes a 1s access delay
for UEs processing NRT services. P2F-triggered redirection increases the number of cell update attempts and therefore causes more signaling exchanges.
Huawei Confidential
Page 220
Dependency
None
None
Impacted Features
1. Smart P2D Transition. For details, see State Transition Feature Parameter Description.
2. TAC-based P2D Transition. For details, see Enhanced Fast Dormancy Feature Parameter Description.
3. TVM-based P2D Transition. For details, see Flow Control Feature Parameter Description
4. P2D procedure for UEs processing PS services in case of DTCH congestion. For details, see Flow Control Feature Parameter
Description.
The P2F-triggered Redirection for NRT Services feature is preferentially triggered compared with the above features.
None
None
License
This feature is under cell-level license control.
Feature ID
WRFD-150246
Feature Name
Service Steering and Load Sharing
in CELL_FACH State
License Control Item

(Per cell)
Huawei Confidential
NE
Sales Unit
RNC
Per cell
Page 221
Verification
Counter Name
Description
VS.P2F.Redir.Out
Number of Outgoing P2F-triggered Redirections for Cell
VS.P2F.Redir.In.UseNewCU
Number of Incoming P2F-triggered Redirections for Cell (Cell Update)
VS.P2F.Redir.FailOut.NonTargetFCN
Number of P2F-triggered Redirection Failures Caused by UE Not Accessing the

Target Frequency for Cell
VS.P2F.Redir.FailOut.NoReply
Number of P2F-triggered Redirection Failures Caused by UE No Response for

Cell
VS.P2F.Redir.Out.RT.P2DFail
Number of Outgoing P2F-triggered Redirections for RT Services After P2D

Failures
VS.P2F.Redir.Out.RT
Number of Outgoing P2F-triggered Redirections for RT Services for Cell
Huawei Confidential
Page 222
Content
1
Summary of RAN16.0

UMTS HD Voice



UMTS SON Solution


Huawei Confidential
Page 223
KPI-PS IntFD-160112
KQI APP
Cell-Level Coverage Quality Evaluation
Huawei Confidential
Page 224
Background
One PS Data Transfer Process
User click on
Legacy KPI
KPI-PS
RAB SETUP
First data packet
Only Signal
Plane(RRC/RAB)Can
be evaluated
Offer the whole flow evaluate

method(RRC/RAB/
Authentication/ encryption)
Low Throughput Period

RTT
High Throughput Period

Throughput
This phase of ps service quality

cant be evaluated using legacy
KPI.
to evaluate low
throughput ps service
quality using DL/UL RTT
Delay
To evaluate high throughput ps service

quality using throughput satisfied ratio
KPI-PS offers PS Service Quality Evaluation closer to user experience

Huawei Confidential
Page 225
KPI PS
Domain
Accessibility KPI
Service Integrity
KPI (Low
Throughput
Period)
Service Integrity
KPI(High
Throughput
Period)
KPI-PS
PS Service Access Success Rate
PS Service Access Delay
Round trip time over IU
Round trip time under IU
requested DL throughput of high throughput user
throughput satisfied ratio of high throughput user
average throughput of high throughput user
Huawei Confidential
Page 226
Impact
Benefit
KPI-PS is a solution for PS service quality evaluation, which is real-time, accurate

and low-cost.
This feature improves the capability to detect PS service quality problems in
terms of operation and maintenance (O&M) .
It is recommended that KPI-PS be used in all scenarios by default .
Network Impact
NA
Huawei Confidential
Page 227
Dependency
Dependency on other NEs
NA
NA
License
Basic function, No License Needed
Huawei Confidential
Page 228
KPI-PS Counter
Counter
Description
Counter
Description
VS.ULPSServ.AttEstab.Idle
UL PS Service Access Attempt

number from IDLE
VS.DLPSServ.EstabMeanTime.Id
le
DL PS Service Access
Mean Delay from idle
VS.ULPSServ.EstabMeanTime.Idle
UL PS Service Access Mean Delay

from idle
VS.DLPSServ.EstabDelay.Good.
Num.Idle
VS.ULPSServ.EstabDelay.Good.Num
.Idle
Number of UL PS Service Access

delay good from idle
VS.DLPSServ.EstabDelay.Bad.N
um.Idle
VS.ULPSServ.EstabDelay.Medium.N
um.Idle

delay Medium from idle
VS.ULPSServ.AttEstab.PCH
VS.ULPSServ.EstabDelay.Bad.Num.I
dle

delay bad from idle
VS.ULPSServ.EstabMeanTime.P
CH
Number of DL PS Service
Access delay good from
idle
Access delay bad from
idle
UL PS Service Access
Attempt number from
PCH
Mean Delay from PCH
VS.DLPSServ.AttEstab.Idle
DL PS Service Access Attempt

number from IDLE
VS.ULPSServ.EstabDelay.Good.
Num.PCH
Huawei Confidential
Number of UL PS Service
PCH
Page 229
KPI-PS Counter
Counter
Description
Counter
Description
VS.ULPSServ.EstabDelay.Medium.N
um.PCH

delay Medium from PCH
VS.DLPSServ.EstabDelay.Bad.N
um.PCH
VS.ULPSServ.EstabDelay.Bad.Num.
PCH

delay bad from PCH
VS.ULPSServ.AttEstab.MultiRAB
VS.DLPSServ.AttEstab.PCH

number from PCH
VS.ULPSServ.EstabMeanTime.M
ultiRAB
VS.DLPSServ.EstabMeanTime.PCH
DL PS Service Access Mean Delay

from PCH
VS.ULPSServ.EstabDelay.Good.
Num.MultiRAB
VS.DLPSServ.EstabDelay.Good.Num
.PCH
Number of DL PS Service Access

delay good from PCH
VS.ULPSServ.EstabDelay.Mediu
m.Num.MultiRAB
PCH
Attempt number from
MultiRAB
Mean Delay from
MultiRAB
MultiRAB
Access delay Medium
from MultiRAB
VS.DLPSServ.EstabDelay.Medium.N
um.PCH

delay Medium from PCH
VS.ULPSServ.EstabDelay.Bad.N
um.MultiRAB
Huawei Confidential
MultiRAB
Page 230
KPI-PS Counter
Counter
Description
Counter
Description
VS.DLPSServ.AttEstab.MultiRAB

number from MultiRAB
VS.PS.ULFirstPacket.RttDelay.M
edium.Num
Number of UL RTT Delay

medium
VS.DLPSServ.EstabMeanTime.Multi
RAB
DL PS Service Access Mean Delay

from MultiRAB
VS.PS.ULFirstPacket.RttDelay.Ba
d.Num

bad
VS.DLPSServ.EstabDelay.Good.Num
.MultiRAB

delay good from MultiRAB
VS.PS.DLfirstPacket.RttDelay.Me
an
DL RTT Mean Delay of

UL First Packet
VS.DLPSServ.EstabDelay.Medium.N
um.MultiRAB

delay Medium from MultiRAB
VS.PS.DLFirstPacket.RttDelay.Go
od.Num

good
VS.DLPSServ.EstabDelay.Bad.Num.
MultiRAB

delay bad from MultiRAB
VS.PS.DLFirstPacket.RttDelay.M
edium.Num

medium
VS.PS.ULfirstPacket.RttDelay.Mean
UL RTT Mean Delay of UL First

Packet
VS.PS.DLFirstPacket.RttDelay.Ba
d.Num

bad
Huawei Confidential
Page 231
KPI-PS
KQI APP IntFD-160005
Cell-Level Coverage Quality Evaluation
Huawei Confidential
Page 232
Background
Lots of PS application ,such as Web and Video , has become the major application in the wireless
network in place of the traditional Voice service.
In the MBB times, the users are more sensitive to the experience of PS service. Poor service
performance ,such as the long latency of Web and the temporary break of video , will bring bad
experience to users . However ,these experiences are difficult to evaluate by the traditional network
KPI in control plane.
RAN 16.0 introduce the experience evaluation based on the service type awareness, and provide KQI
for Web Browsing and Video service experience. The KQI with the traditional KPI can guide the
network optimization and expansion.
Huawei Confidential
Page 233
Introduction
This feature application depends on RNC and PRS.
RNC provides Web and Video service awareness ,and KQI measurement based on NIU
RNC stores the KQI measurements on SAU and report to PRS.
PRS provides the KQI Visualization
KQI performance report

KQI monitor ,and alarms for abnormal values over the threshold
General analysis for KQI problems
Visualization of the related KPI of the KQI
NodeB
RNC
SAU
(1)Service Awireness&Measurement
NIU
(2)Counters Report
SGSN
Internet
Internet
(3)KQI Visualization
Huawei Confidential
PRS(Performance Surveillance)
Page 234
Impact
Benefit
Be easy to evaluate the service experience of Web Browsing and Video
Negative Impact
The DSP load of DPU board will increase 5%

Some NIU boards are needed . In BSC 6900, the recommended number ratio of
NIUa board with DPUe board is 1:2.5.
Huawei Confidential
Page 235
Dependency
The BSC 6900 must be configured with NIUa board and SAUa board(or SAUc board)
The BSC 6910 must be configured with ENIUa board and ESAUa board.
None
None
Impacted Features
None
PRS(Performance Surveillance)
License
This feature is with License control in PRS

Operator must apply enough License for smart throughput of network , and each NIUa/ENIUa defaultly
include 50Mbps throughput License. If more throughput is needed , the extra License must be applied .
Huawei Confidential
Page 236
Verification
Web Browsing KQI
Video KQI
KQI
Description
The successful
response ratio of the
Web Page
The ratio of the procedure that

user launch Web browsing ,then
setup Web Page successfully .
The latency of the procedure that
user launch Web browsing ,then
setup Web Page connection
successfully .
The response latency

of Web Page
KQI
The successful ratio of
Video initially play
The latency of initial

cache of Video
The ratio of the

successful page show
The ratio that user can successfully

download all content of a page.
The show latency of

page
The latency which stars from the

first packet with response code
from server , and ends at the point
that all the content of page are
downloaded successfully .
The download rate of

page
The download rate of content of

page .
Description
The average numbers for

break of Video
The average period for
break of Video
The download rate of
Video
Huawei Confidential
The ratio of the procedure that

user launch Video service and
successfully play .
The latency from user
launching Video Service , to
the time of cache finish and
the video can played
successfully.
The average numbers of break
in the duration of Video play
The average period of break
in the duration of Video play
The download rate in the total
duration of Video play.
Page 237
KPI-PS
KQI APP
Cell-Level Coverage Quality Evaluation IntFD-160066
Huawei Confidential
Page 238
Background
About 40% of the current network problems are related to coverage, which is the top 1 problem. Among coverage problems,
more than 60% complaints come from residential areas, and about 70% services are performed indoors. Therefore, among
coverage problems, indoor coverage problems are the top 1 problem. Currently, coverage problems are identified and handled
by performing drive tests (DTs), which requires high costs and long periods, affecting efficiency in solving problems.
Nastar counters are obtained through postprocessing and are not systematic. In addition, cell-level geographic display is
unavailable currently.
This theme is not based on DTs. Instead, cell overage quality is evaluated by counter dotting, helping quickly and costeffectively detect cells with coverage problems on the network. Then, users can optimize cells based on top N cells with
coverage problems and the related optimization guide.
Service distribution
Distribution of user complaints

Huawei Confidential
Page 239
This theme is used to locate the following scenarios: weak coverage, interference, and indoor UE distribution. The following
scenarios are customized based on user requirements. Users can define related thresholds based on analysis requirements to
quickly locate problematic cells.
Weak
RSCP coverage
Interference
Indoor coverage
EcNo
UE TxPower
TCP
TP
RTWP
RSCP vs. TP
EcNo vs. TP
Cell configuration (Cell Max Power, CPICH power, CCH power)
Coverage KPIs:
Weak coverage: downlink RSCP, uplink UE TxPower,
and propagation delay (TP) from the UE to the base station
Interference: downlink EcNo and TCP, and uplink RTWP
Indoor weak coverage: RSCP vs. TP and EcNo vs. TP
Huawei Confidential
This theme currently does not support the

following scenarios: coverage hole, pilot pollution,
uplink and downlink balance, no dominant cell,
indoor signal pill-over/intrusion.
Page 240
Introduction 1/3
Cell-Level Coverage Quality Evaluation is implemented by recording counter values at certain

time. The recorded counter values are submitted to the PRS. The PRS displays the final results
in reports and sorts top cells in the reports .
Technical principle of cell-Level

Coverage Quality Evaluation
Huawei Confidential
Page 241
Introduction 2/3
The PRS provides an independent menu for Cell-Level Coverage Quality Evaluation. The reports
display counter measurement results on multiple pages.
PRS coverage evaluation report
Note:
The PRS supports switch to the GIS

window.
The PRS collects the proportion of a poor
counter for cells. It collects proportions of
this counter within different ranges and
determines the poor counter proportion
based on the preset poor counter threshold.
Cell1
Cell2
Poor UE TxPower proportion for a cell

Huawei Confidential
Page 242
Cell3
Introduction 3/3
Counter contents include counters related to RSCP, Ec/No, TP, and cell load, and cell power
parameters. (For example )
Counter Name
VS.RRC.Access.RSCP.x
VS.SHO.RSCP.x
Description
Remarks
Number of times the best cell's RSCP indicated in an RRC CONNECTION REQUEST message falls into
range x (x ranges from 0 to 9)
Number of times the best cell's RSCP indicated in a 1A/1B/1C measurement report falls into range x (x
ranges from 0 to 9)
New
New
VS.Periodic.MrRpt.RSCP.x
Number of times the best cell's RSCP indicated in a periodic intra-frequency measurement report falls into
New
VS.RRC.Access.EcNo.x
Number of times the best cell's Ec/No indicated in an RRC CONNECTION REQUEST message falls into
New
VS.Cell.Updt.EcNo.x
Number of times the Ec/No in RACH measurement results indicated in a CELL UPDATE message falls into
New
VS.SHO.EcNo.x
VS.Periodic.MrRpt.EcNo.x
Number of times the best cell's Ec/No indicated in a 1A/1B/1C measurement report falls into range x (x
ranges from 0 to 8)
Number of times the best cell's Ec/No indicated in a periodic intra-frequency measurement report falls into
New
New
VS.Periodic.MrRpt.UETxPower.x
Number of times the best cell's UE Tx Power indicated in a UE Tx Power measurement report falls into range
x (x ranges from 0 to 13)
New
VS.RSCP.Mean.TPx
Average RSCP for UEs with a propagation delay (TP) of x indicated in an RRC CONNECTION REQUEST
message for cell (x is an integer greater than or equal to 0)
New
VS.EcNo.Mean.TPx
Average Ec/No for UEs with a propagation delay (TP) of x indicated in an RRC CONNECTION REQUEST
message for cell (x is an integer greater than or equal to 0)
Existing
Huawei Confidential
Page 243
Impacts
Network Impacts
System Capacity
N/A
Network Performance
This theme will increase CPU usage when MR reporting is enabled.

When all MR measurements are enabled, the RNC CPU usage will increase by about 8%. The counter
overhead impact is less than 5%.
It is recommended that the MR reporting period be set to 12s. Within this period, MR measurements
do not affect network KPIs. Note that some UEs may be released or restarted unexpectedly after some
measurements are enabled. This problem has been solved using a CR and users have to turn on the
switches of related UEs when MR measurements are enabled.
Huawei Confidential
Page 244
Dependency
Dependency Features
None
NE Dependency
None
Hardware Dependency
None
Impacted Features
None
This theme is implemented by recording counter values at certain time. This version implements only some
basic counters. Counter values are recorded at certain time on RNCs and the measurement results are
reported to the PRS and displayed on quality evaluation GUIs.
License
All counters involved in this theme are external counters. Therefore, no license is required .
Huawei Confidential
Page 245
Content
1
Summary of RAN16.0

UMTS HD Voice


UMTS SON Solution

Huawei Confidential
Page 246
PS initial rate of Multi-RAB is configured dynamically according to traffic

WRFD-140104 Enhanced Combined Services
CS+PS MultiRAB Call Re-Establishment Enhancement
Huawei Confidential
Page 247
Introduction
CS
PS
PS
Traffic
During CS call, PS speed will fall sharply, then rises
CS
PS
PS Traffic
During CS call, PS speed is smooth
CS
Traffic
PS
PS
During CS call, PS speed is smooth
PS initial rate of Multi-RAB is fixed by configuration, which affects PS experience if the traffic throughput is
higher than the initial rate. Particularly evident in the non full-buffer test.
It is not applied when the downlink of PS service carried on DCH channel
Huawei Confidential
Page 248
Benefit Dependency and Performance

Evaluation
Benefit
Avoid the PS traffic falls sharply when CS service is coming(Typically :2~3s) ,and improve
the user experience.
Reduce the RB reconfiguration times due to the PS speed rises, and improve the CS Drop
Rate .
Dependency
Basic feature enhancement WRFD-140104 Enhanced Combined Services
No rely on hardware, or other feature, or license.
Average PS throughput in the Combined Service scenario

Call Drop Rate in the Combined Service scenario
Huawei Confidential
Page 249
CS+PS MultiRAB Call Re-Establishment Enhancement IntFD151030
Huawei Confidential
Page 250
Solution Introduction
CS+PS MultiRAB Call Re-Establishment Enhancement
Considering weak coverage, CS+PS call Re-Establishment can be configured to CS+0K

accompanied with 0K rising strategy.
Procedures such as fall back, preemption, and configured little rate can be performed to
ensure the successful access of Re-establishment to the network. It is applicable to single
PS service too.
Huawei Confidential
Page 251
Benefit :
Call Re-establishment successful rate will improve, and Call drop rate will improve if the network is
under heavy load. The gain is depended on the numbers of pre-emption trigger.
Negative Impacts
If pre-emption function is activated , PS call drop will increase. And the PS RAB access successful
rate will deteriorate if the pre-emption triggers a lot since PS service will re-connect network
repeatedly.
MultiRAB Call Re-establish is configured to CS +0K will impact PS experience after call re-establish
complete.
Dependency
Basic Function . No rely on hardware or license.

CO., LTD. pre-emption function
Huawei Confidential
CallTECHNOLOGIES
Re-establishment
depends on WRFD-010505
Queuing
and Pre-Emption
Page
252
HUAWEI
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Huawei Confidential
Page 253
UMTS Network KPI
Mobility KPI Improvement
SRB Rate Selection Based On Congestion and Coverage

Improve IUR Call Drop Rate by Handling CELL UPDATE from Unknown DRNC CELL
Avoid Call drop from Useless UE Capability Enquiry
RSCP-based E2D and HSUPA TTI Selection
Solution for High Call Drop due to SRB Reset or G2U
KPI system Improvement
2D Event Type Switch Triggering IFHHO and IRAT HO IntFD-160071

PS IRATHO Penalty Due To CS IRATHO Preparation Failure
Send Inter-freq Measurement Control Sequentially
Call Drop KPI Improvement
Improvement Solution

Paging Counter System and improving Paging Success rate
Latency Improvement
Huawei Confidential
Page 254
2D Event Type Switch Triggering IFHHO and IRAT

HO
Issue Scene
Some operators want to use only 2D RSCP event to trigger IFHHO and IRATHO and decrease IFHHO and
IRATHO ,but Huawei have no such switches to control only 2D RSCP event(or 2D EcNo event) trigger IFHHO
and/or IRATHO before.
Solution
Three switches like InterFreqHO2DEventType,InterRATHO2DEventType,U2LTEHO2DEventType can be setting

as ONLYRSCP or ONLYECNO or ECNOANDRSCP which can trigger IFHHO and IRATHO flexible.
Benefit
Number of IFHHO and IRAT HHO decreases.
Huawei Confidential
Page 255
Feature Deployment
Dependency
Verification
Basic function . No rely on hardware, or other feature, or license.
Check if number of VS.HSDPA.SHO.ServCellChg.SuccOut,VS.HSDPA.SHO.ServCellChg.AttOut decreases.
Check if number of following counter decreases.
VS.HHO.AttInterFreqOut
VS.HHO.SuccInterFreqOut
IRATHO.AttOutCS
IRATHO.SuccOutCS
IRATHO.AttOutPSUTRAN
IRATHO.SuccOutPSUTRAN
Huawei Confidential
Page 256
UMTS Network KPI

Solution

2D Event Type Switch Triggering IFHHO and IRAT HO

PS IRATHO Penalty Due To CS IRATHO Preparation Failure IntFD-160039
Improvement

Latency Improvement
Huawei Confidential
Page 257
Issue Scene
If many CS IRATHO preparation failures due to resource congestion, then PS IRATHO to same GSM cell will fail
with high probability.
Solution
Benefit
If a CS IRAT handover of any type (quality, coverage, and so on) to the GSM system is started and the target GSM cell
is selected based on measurements, but the relocation to the GSM system is unsuccessful and the 'RANAP: Relocation
Preparation Failure' IE is received from the core network(Failure cause is same with predefined CS IRATHO preparation
failure cause value), then PS IRAT handover to this target cell are not performed during a certain period.
PS IRAT HHO successful rate increases.
Network impact
PS drop rate will increases due to penalty .

Huawei Confidential
Page 258
Feature Deployment
Dependency
Verification
Check if number of VS.HSPA.ServCellChg.1A1COptTrig, VS.HSPA.ServCellChg.1DOptTrig is

higher than zero.
Check KPI as following

Check if number of IRATHO.AttOutPSUTRAN,IRATHO.SuccOutPSUTRAN decrease .
IRAT HO Success Ratio = (,IRATHO.SuccOutPSUTRAN/ IRATHO.AttOutPSUTRAN t) x 100%
Huawei Confidential
Page 259
UMTS Network KPI

Solution


Send Inter-freq Measurement Control Sequentially IntFD-151051
Improvement

Latency Improvement
Huawei Confidential
Page 260
Send Inter-freq Measurement Control
Sequentially
Background
MBB service grows very quickly, and lots of network introduce the 4 th even 5th carrier. Different carrier
may not share the same site, and have different coverage.
However, UE can only measure 2 additional FDD carriers according to 3GPP 25.331.
8.1.2.1
UE Measurement Capability
In CELL_DCH state the UE shall be able to monitor up to

- 32 intra frequency FDD cells (including active set), and
- 32 inter frequency cells, including
- FDD cells distributed on up to 2 additional FDD carriers and
- Depending on UE Capability, TDD cells, distributed on up to 3 TDD carriers and
- Depending on UE capability, 32 GSM cells distributed on up to 32 GSM carriers.
- Depending on UE capability, the UE shall be able to monitor up to 16 intra frequency cells during IPDL gaps.
Therefore, UE may not measure some carrier, and has to handover to GSM/GPRS, or drop due to weak
coverage.
Huawei Confidential
Page 261

Sequentially
Solution
New solution active or not controlled by Interfreqmcmode switch. If switch Interfreqmcmode is

activated, the measurement control of two carrier indicated by the first two high priority inter-frequency
neighboring cells is sent after compress mode started.
If there is no suitable neighboring cell can be hand over to after InterFreqMeasTime timer expired,
the measurement control message will be modified, and the measurement on the two frequency already
sent in measurement control message will be stopped, and new frequency will be sent in the
measurement control message. If no new frequency left, the compress mode will be stopped.
If there are inter-RAT measurement IE in the message, and it will not be affected.
which indicated by neighboring cell configuration
Only suggest to be activated in the network with more than 3 carriers.
Huawei Confidential
Page 262
Sequentially
Benefit
It is suitable for the network with more than 3 carriers.
IRAT handovers to GSM/GPRS will be decreased ,and more users will be stayed on UMTS , and enjoy better experience.
Call drops due to weak coverage may be less.
Network impact
Dependency
Basic Function , and No rely on hardware, or license.
Verification
One more measurement control message is sent during compress mode, which may affect little call drop. However, more frequency can be measured and
can be hand over to, so call drop rate will be saved. Therefore, the call drop rate may be not deteriorated.
From RNC trace from LMT or UE trace from drive test ,and check if one more measurement control message was sent to UE when 2 more inter-frequent
carrier exist and no suitable cell measured at the first time.
CS Service Drop Ratio (Cell)=

[VS.RAB.AbnormRel.CS/(VS.RAB.AbnormRel.CS+ VS.RAB.NormRel.CS)] x 100%
PS Call Drop Ratio with PCH (Cell)=
[(VS.RAB.AbnormRel.PS- VS.RAB.AbnormRel.PS.PCH-VS.RAB.AbnormRel.PS.D2P- VS.RAB.AbnormRel.PS.F2P) /(VS.RAB.AbnormRel.PS+ VS.RAB.NormRel.PS-
VS.RAB.AbnormRel.PS.PCH-VS.RAB.NormRel.PS.PCH +VS.DCCC.D2P.Succ+VS.DCCC.Succ.F2P+VS.DCCC.Succ.F2U+VS.DCCC.Succ.D2U)]*100%
Inter-frequency Hard Handover number: VS.HHO.AttInterFreq.RNC
Huawei Confidential
Page 263
UMTS Network KPI

Solution
SRB Rate Selection Based On Congestion and Coverage IntFD-160035 IntFD-160092


Improvement

Latency Improvement
Huawei Confidential
Page 264
Issue Scene
When 13.6 or 27.2Kbps SRB rate is used, RAB setup success rate under weak coverage is
lower than 3.4kbps SRB.
When 13.6K or 3.4K bps SRB rate is used, Call setup latency is longer than 27.2Kbps SRB.
Solution Description
At the initial of RRC Connection Setup or P2D , signal channel rate will be selected according to congestion
state and coverage .
If Cell is in Normal State :
When EcIo>=Strong Coverage Threshold , 27.2Kbps SRB is selected;
When EcIo< Weak Coverage Threshold, 3.4Kbps SRB is selected;
Otherwise, 13.6 Kbps SRB is selected.
If Cell is in Congestion State :
When EcIo>= Weak Coverage Threshold, 13.6 Kbps SRB is selected;
When EcIo< Weak Coverage Threshold, 3.4Kbps SRB is selected;
Huawei Confidential
Page 265
Feature Deployment
Dependency
Benefit
Improve RAB setup success under weak coverage by using 3.4kbps SRB.
Improve Call setup latency under good coverage by using 27.2Kbps or 13.6 Kbps SRB.
Setup Latency Counter :

VS.AMR.Estab.MeanTime VS.CS64.Estab.MeanTime VS.PSR99.Estab.MeanTime VS.HSDPA.Estab.
MeanTime VS.HSUPA.Estab.MeanTime
RAB Successful Rate Counter :
VS.RAB.SuccEstabCS.AMR VS.RAB.AttEstab.AMR VS.RAB.AttEstabPS.Bkg VS.RAB.SuccEstabPS.Bkg

VS.RAB.AttEstabPS.Conv VS.RAB.SuccEstabPS.Conv VS.RAB.AttEstabPS.Int VS.RAB.SuccEstabPS.Int
VS.RAB.AttEstabPS.Str VS.RAB.SuccEstabPS.Str
Huawei Confidential
Page 266
UMTS Network KPI

Solution

Call Drop Rate improve during State transition IntFD-151028

Improvement

Latency Improvement
Huawei Confidential
Page 267
Call Drop Rate improve during State Transition -- D2F
Issue Scene
When D2F procedure is time out, RNC will initiate release procedure before RAN16.0
When timer RbRecfgRspTmr expires, RNC judges the state of UE as follows:
AM mode (RB RECFG)
If RNC receives the ACK of RB RECFG from UE, it considers that UE has received RB RECFG and
entered into CELL_FACH state. So RNC deal with this scene as normal procedure instead of RNC initiate
release procedure before.
Otherwise, it rolls back to CELL_DCH state at network side.
UM mode (RB RECFG)
If RNC receives RL fail from all RLs, it considers that UE has received RB RECFG and entered into
CELL_FACH state, and RNC deal with this scene as normal procedure instead of RNC initiate release
procedure before.
Otherwise, it rolls back to CELL_DCH state at network side.
Huawei Confidential
Page 268
Call Drop Rate improve during State Transition -- D2F
Benefit
Dependency
It is applied to improve PS drop rate in the scene of

high drop rate caused by D2F (including H2F)
procedure failure. On some typical sites, PS call drop
rate can be improved about 5%.
Basic function . No rely on hardware, or other feature,

or license.
Impact Analysis
No negative impact
Huawei Confidential
Page 269
Call Drop Rate improve during State Transition -- F2D
Issue Scene
When F2D procedure is time out, RNC will initiate release procedure before RAN16.0
When timer RbRecfgRspTmr expires, RNC judges the state of UE as follows:

AM mode (RB RECFG)
If RNC received the RL Restore from all RLs, it considers that UE has received RB RECFG and
entered into CELL_DCH state. So RNC deal with this scene as normal procedure while RNC initiate
roll back to CELL_FACH state procedure before.
Otherwise, it rolls back to CELL_FACH state at network side.
UM mode (RB RECFG)
Same as AM mode
Huawei Confidential
Page 270
Call Drop Rate improve during State Transition -- F2D
Benefit
Dependency
It is applied to improve PS drop rate in the scene of

high drop rate caused by F2D (including F2H)
procedure failure. On some typical sites, PS call drop
rate can be improved about 0.7 %.
Basic function . No rely on hardware, or other feature,

or license.
Impact Analysis
No negative impact
Huawei Confidential
Page 271
UMTS Network KPI

Solution

Improve IUR Call Drop Rate by Handling CELL UPDATE from Unknown DRNC CELL IntFD-160096

Improvement

Latency Improvement
Huawei Confidential
Page 272
Handling CELL UPDATE from Unknown DRNC CELL

EX:
CN
RNC1
1.
IU
RNC2
R
CELL21,CELL22,CELL23 are all
configured as RNC1s Neighboring

RNC Cell, but CELL24 not.
CELL11
CELL12
CELL13
CELL21
CELL22
CELL23
When UE access from cell13, and moved to

CELL 23.
2. Downlink RL failure happened, and UE
reselect to CELL24 to send CELL UPDATE
message.
3. RNC1 will release the connection immediately
for CELL24 not configured as its Neighboring
RNC Cell, and it can not obtain the cell
CELL24
capability to handle the re-establishment.
CELL UPDATE
Issue Scene
If CELL UPDATE message is sent from DRNC cell who is not configured as SRNCs Neighboring RNC Cell,
the CELL UPDATE message will not be handled and the connection will be released immediately. For SRNC
can not obtain the capability of the DRNC cell, and can not decide which kind of configuration can be
configured for this UE.
Huawei Confidential
Page 273
Solution
Solution for CS service, or PS RT service ,or MultiRAB including them
SRNC re-establish the service in the cell which indicate in the UPLINK SIGNALLING TRANSFER
INDICATION(CELL UDPATE) message (Detail see the note )
Then if RL SETUP RESPONSE message from DRNC RNC including PSC and Freq IE
Including Primary Scrambling Code and frequency, then continue the re-establishment procedure.
Including Primary Scrambling Code, but frequency not included, then select the frequent of the first cell in the
neighbouring-UMTS-CellInformationItem as its frequency, and then continue the re-establishment.
Not including Primary Scrambling Code and frequency, the re-establishment will be failed.
Solution for only PS BE service
DSCR immediately.
Huawei Confidential
Page 274
Benefit and Network impact
The Benefit is related to the implement of DRNC. If RL SETUP RESPONSE message

from DRNC
Include Primary Scrambling Code and frequency IE, then CELL UPDTE message from unknown DRNC cell
which has not configured as Neighboring RNC Cell can be handled, and the call will be continued after reestablished.
Only include Primary Scrambling Code IE, but frequency IE is not include, the CELL UPDTE message from
unknown DRNC cell which has not configured as Neighboring RNC Cell can be handled, but the frequency of
the cell might be wrong if the first cell is not intra-frequent neighboring cell, and handover can not be
performed when the user moved.
Not include Primary Scrambling Code and frequency IE, there is no benefit.
No other network impact.
Huawei Confidential
Page 275
Feature Deployment
Dependency
Basic Function. No rely on hardware, or other feature, or license.
Verification
If there is AMR or AMRWB or PS BE service drop on IUR caused by the problem mentioned above, check whether will
VS.RAB.AbnormRel.AMR.Iur or VS.RAB.AbnormRel.PS.BE.Iur or VS.RAB.AbnormRel.AMRWB.Iur be decrease.
NOTE: It there is other service drop on IUR, for example, VP, or HSDPA, or HSUPA, and then check those counter in the same
IUR.CELL.
AMR Call Drop Ratio(RNC) = [(Sum{VS.RAB.AbnormRel.AMR}+Sum{VS.RAB.AbnormRel.AMR.Iur})/

(Sum{VS.RAB.AbnormRel.AMR}+ Sum{VS.RAB.NormRel.AMR}+ Sum{VS.RAB.AbnormRel.AMR.Iur}+
Sum{VS.RAB.NormRel.AMR.Iur} )]*100%
PS BE Call Drop Ratio (RNC)=

[(Sum{VS.RAB.AbnormRel.PS.BE}+Sum{VS.RAB.AbnormRel.PS.BE.Iur})/ (Sum{VS.RAB.AbnormRel.PS.BE}
+Sum{VS.RAB.NormRel.PS.BE}+Sum{VS.RAB.AbnormRel.PS.BE.Iur}+Sum{VS.RAB.NormRel.PS.BE.Iur} )]* 100%
Huawei Confidential
Page 276
UMTS Network KPI

Solution

Avoid Call drop from Useless UE Capability Enquiry IntFD-160048

Improvement

Latency Improvement
Huawei Confidential
Page 277

Issue Scene
It is found that 0.5%~1% drops due to UE capability enquiry during weak coverage after UE
relocation from other RNCs. However, the UE capability is already in the Relocation Request message
while SRNC and TRNC are the same release version. Therefore, the UE capability enquiry procedure is
no use at all.
UE in CELL_FACH state relocate from other RNC can be omitted in legacy version.
Solution
When UE in CELL_DCH state relocation from other RNC, UE capability enquiry procedure can be
omitted.
Call drop by UE capability enquiry procedure will be avoid.
No other negative impact.
Huawei Confidential
Page 278
UMTS Network KPI

Solution

RSCP-based E2D and HSUPA TTI Selection IntFD-151060

Improvement

Latency Improvement
Huawei Confidential
Page 279

Background
Coverage-based E2D and HSUPA TTI Selection for BE Service, the uplink coverage for UEs are measured in
ECN0 and UE transmission power, has the following shortcomings:
Access mode :
E2D and HSUPA TTI Selection algorithm may coexist, however, RSCP can reflect the uplink coverage
better compared with ECN0, when the KPI in a cell remains unchanged, the RSCP method can increase
the number of HSUPA 2ms TTI users
Connected mode :
E2D and HSUPA TTI Selection algorithm cannot coexist(if E2D and HSUPA TTI Selection algorithm are
both enabled, the HSUPA TTI Selection algorithm automatic expiration), UE with weak coverage
performance cannot achieve best performance of KPI and throughput.
RSCP-based E2D and HSUPA TTI Selection is needed.
Huawei Confidential
Page 280
Benefits
This feature is recommended in networks enabled with HSUPA 2ms TTI or SRB over HSUPA
Benefits
If ECN0/ UE transmit powerbased HSUPA TTI Selection algorithm has been enabled, then enable the
RSCP-based E2D and HSUPA TTI Selection feature will bring following impact:
PS Radio Access Success Ratio and PS Call Drop Ratio will be improved
If all resource(ADMCE, RTWP, IUB, used CE, DSP) are not limited, the number of HSUPA 2ms TTI
users increase by 0~10%
Huawei Confidential
Page 281
Verification
Activation Observation
Impact on KPI
VS.RABEstabE2D.COVER.Succ
VS.HSUPA.RABEstabTTI10ms.Cover.Succ
VS.HSUPA.E2D.Succ
VS.HSUPA.TTI2to10.COVER.Succ
PS RAB Setup Success Ratio
HSDPA RAB Setup Success Ratio
HSUPA RAB Setup Success Ratio
PS Call Drop Ratio
HSDPA Call Drop Ratio
HSUPA Call Drop Ratio
Impact on HSUPA 2ms and 10ms TTI users
Huawei Confidential
Page 282
UMTS Network KPI

Solution

Solution for High Call Drop due to SRB Reset or G2U IntFD-160081

Improvement

Latency Improvement
Huawei Confidential
Page 283
Background
Scenario 1
According to the statistics from some sites, SRB Reset
may be one of the main reasons for Call Drop when UEs
are under the condition of bad coverage extreme
congestion or other scenes.
Scenario 2
3G Operator
2G Operator
BSC
RNC
Node B
BTS
When the UE move from 2G to 3G,it would take a

long time usually to transmit the signaling message
because of the small default value for
NoDiscardMaxDAT(15)
Huawei Confidential
Page 284
ntroduction Impact and Dependency

Introduction
Before R16 the RLC Parameters ( NoDiscardMaxDAT TimerPoll and so on) are coincidence for the side of RNC the
UE. When the RNC have set the RLC parameters (by MML:ADD UTYPSRBRLC), then UE get it from the RB Setup or RRC
Connect Setup which take the ones of RNC.
From R16, these RLC Parameters can be set independently on RNC and UE side ,and NoDiscardMaxDAT can be greater
than before.
Benefit
The feature depend on the radio bearer type of signalling(including the SRB Over HSPA and SRB Over DCH)
Case
SRB Over HSPA
Performance
CS DCR
Gain
0~1%
SRB Over DCH
CS DCR
10%~50%
Impacts on other Features or KPI

In the case of opening SRB RL reestablish, it is not suggested to use the feature ,because when the NoDiscardMaxDAT is set
largely(such as 40 ,or more larger) ,the SHO SUCC RATE may be impacted.
Dependency
None
License
This is an basic function in R16 and is not license controlled.
Huawei Confidential
Page 285
Verification
Gain
Observation
Counter
Description
VS.RAB.AbnormRel.CS
VS.RAB.AbnormRel.CS.RF.SRBReset
The number of abnormal rab release in CS domain

The number of abnormal rab release in CS domain due to SRB Reset
VS.RAB.AbnormRel.PS.RF. SRBReset
The number of abnormal rab release in PS domain due to SRB Reset
VS.RAB.AbnormRel.PS
The number of abnormal rab release in PS domain
VS.IRATHO.SuccInCS
The number of successing IRATHO
After the feature activation, the above five counters will reduce, while
VS.RAB.AbnormRel.CS.RF.UuNoReply and VS.RAB.AbnormRel.PS.RF.UuNoReply
may increase.
Huawei Confidential
Page 286
UMTS Network KPI

Solution


Improvement
KPI system for user in PCH_State IntFD-151016

Latency Improvement
Huawei Confidential
Page 287
KPI system for user in PCH_State state
Huawei Confidential
Page 288
KPI
system for user in PCH_State state
Issue Scene
Lack evaluation for user access form URA_PCH or CELL_PCH state
When URA_PCH or CELL_PCH state was introduced, most of users initiate call in URA_PCH or
CELL_PCH state by cell update procedure. But the counter in CELLUPDATE.Cell before
R15/R16 cant perfectly evaluate this mode as user in Idle state.
A KPI system for user in URA_PCH or CELL_PCH state has been introduced in R15/16.
KPI system for user in PCH state can evaluate access success rate for user in PCH state.
Dependency
Huawei Confidential
Page 289
UMTS Network KPI

Solution


Improvement

Paging Counter System and improving Paging Success rate IntFD-160049
Latency Improvement
Huawei Confidential
Page 290
Background and Solution
Issue Scene
Lack of paging success ratio counter in connected mode when deploying PCH before.
CS paging success ratio decreased when deploying PCH
Solution
Introducing a paging success ratio system to evaluate paging success ratio counter in
connected mode when deploying PCH
Make the UTRAN PAGING triggered by PS data to preempted by CS to improve CS
paging success ratio
Huawei Confidential
Page 291
Paging counter system

Domain
KPI Counter
CS Paging success ratio
VS.RANAP.ConvPaging.Succ.IdleUE/VS.
RANAP.ConvPaging.Att.IdleUE
PS Paging success ratio
(VS.RANAP.Paging.Att.IdleUEVS.RANAP.ConvPaging.Succ.IdleUE)/
(VS.RANAP.Paging.Succ.IdleUE-VS.
RANAP.ConvPaging.Att.IdleUE)
CS Paging success ratio
(VS.RANAP.Paging1.Succ.PCHUE+VS.UTRAN.SuccPa
ging2)/
(VS.RANAP.Paging1.Att.PCHUE+VS.UTRAN.Paging2.
Att)
PS Paging success ratio
VS.UTRAN.SuccPage1/VS.UTRAN.Paging1.Att.PCHU
E.First
Paging In Idle
Paging in Connected
Mode
Formula
Huawei Confidential
Page 292
Benefit
Improve CS paging success ratio 0.1%~0.5%

Solution for paging success ratio evaluation, which is real-time, accurate and lowcost.
Network impact
No negative impact.
Huawei Confidential
Page 293
Feature Deployment
Dependency
Verification
Basic function. No rely on hardware, or other feature, or license.
Check if number of VS.RRC.Paging1.PCHCong.CSPreemptAtt increases when

VS.RRC.Paging1.Loss.PCHCong.Cell exist.
Performance Value Estimation
Check KPI CS Paging success ratio, when the function is enabled, CS Paging success ratio
will improves 0.1%~0.5%.
Huawei Confidential
Page 294
UMTS Network KPI

Solution


Improvement

Latency Improvement
Radio Bearer Setup message omission IntFD-151018
Huawei Confidential
Page 295
Issue Scene
RB setup request message size is shorter and shorten service access delay and
improve success rate . Typically ,20~30ms of UE access latency can be saved .
Dependency
Some elements of RB setup message can be short for same as or omission

according to 3GPP protocol if they are not changed from RRC phase to RB phase
Benefit
There are some unnecessary IEs in RB setup message
Impact Analysis
No negative impact and is recommended to use in all scenarios
Huawei Confidential
Page 296
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution


Huawei Confidential
Page 297
UMTS Service Experience Management

Solution
Video Service Rate Adaption WRFD-150252
VoIP Application Management
Differentiated Service Based on Application Resource Reservation
Huawei Confidential
Page 298
Background
Users expect smooth video playback and minimum bandwidth waste. However, in mobile networks,
radio resource allocation cannot match well with the bandwidth requirements of video services. The
reasons are as follows:
When the radio signal quality is good, downloading too much data at a high rate wastes bandwidth.
When the radio signal quality is poor, the download data rates fluctuate and video playback is not
smooth.
To address these problems, the WRFD-150252 Video Service Rate Adaption feature provides flexible
rate adjustment based on the data rate requirements of video playback, thereby improving user
experience.
High rate download resulted in waste of bandwidth

Huawei Confidential
Rate fluctuation causes the video Stalls
Page 299
Introduction
The feature provides the following functions:
Video rate management: Based on the video bit rate in the network, this feature sets a guaranteed
bit rate (GBR) or happy bit rate (HBR) for video services to minimize the impact of resource
congestion on video data rates.
Initial acceleration: To enable the video to start playing as soon as possible, this feature sets a high
GBR or HBR for video services in the initial acceleration period.
Automatic code rate detection: With the service type awareness of RAN , this feature can automatically
detect the code rate of MP4 FLV and 3GP, and match the SGBR/SHBR (Service
GBR/HBR)automatically based on the code rate
Throughput
faster initial rate to

reduce waiting time
Video rate
Download speed
Add service-based S-GBR/S-HBR to
guarantee video experience
Initial Acceleration Time

Huawei Confidential
Page 300
Time
Impact
Benefits
When radio or Iub resources are insufficient, this feature increases the data rates of video
services using service-specific QoS policies, which will improve user experience of video
services.
Negative Impact
If service rate management is performed on video users configured with SHBR/SGBR in a cell,
the cell throughput may be different, which depends on UE distribution, SHBR/SGBR setting of
video users, distribution of video users and the SPI weight . The Video users with poor radio
quality and lower data rate than SHBR/SGBR are more likely to be scheduled, which will reduce
the cell throughput.
A simulation test was made in a lab: A cell has three category 8 UEs. UE 1 with good channel quality
has an average channel quality indicator (CQI) of about 30, UE 2 with moderate channel quality has
an average CQI of about 25, and UE 3 with poor channel quality has an average CQI of about 9.When
all the UEs were performing full buffer services. After UE 3 was configured with an SHBR of 1024
kbit/s, the cell throughput decreased by about 30%.
Huawei Confidential
Page 301
Dependency
RNC hardware
If the RAN performs service type awareness, the BSC6900 UMTS must be configured with the NIUa board.
If the RAN performs service type awareness, the BSC6910 UMTS must be configured with the ENIUa board.
NodeB hardware
The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EBBI, EBOI, EDLP, EULP, or EULPd
board. The HBBI and HDLP boards do not support this feature.
The DBS3800 must be configured with the EBBC, EBBM, or EBBCd board. The HBBU board does not support
this feature.
The 3900 series base stations, DBS3900, BTS3900C, and BTS3902E must be configured with the WBBPb,
WBBPd, or WBBPf board. The WBBPa board does not support this feature.
This feature does not have any special requirements for the CN if the RAN performs service type awareness.
When the CN performs service type awareness operations, this feature requires the CN to contain DSCPs for
video services in the UE IP packet headers.
Huawei Confidential
Page 302
Dependency
Dependency on other feature

None

None
WRFD-020806 Differentiated Service Based on SPI Weight:
If these two feature are activated simultaneously, the final SPI Weight value ( Based on the original SPI weight value and
DLSpiWeightAdjCoef from this feature must be from 1 to 100 , or some differentiation benefit may disappear.
WRFD-020132 Web Browsing Acceleration:
For the heavily congested network, these two features can not get the maximum benefit simultaneously , and the final benefit
is up to the Qos parameters of Web and Video service.
WRFD-150254 Differentiated Service Based on Application Resource Reservation
The final benefit of WRFD-150252 is up to the HSDPA power occupation and HSDPA maximum power proportion of Video
service group . If the former is higher than the latter, the final benefit of WRFD-150252 is up to WRFD-150254.
WRFD-140221 HSDPA Scheduling Based on UE Location
Its not recommended to activate these two features simultaneously, The target of WRFD-140221 is to get the maximum cell
HSDPA throughput , while the one of WRFD-150252 is to get the best Video experience , which are different and both can not
reach the expected gain if simultaneously activated.
License
An optional feature with new license control in RNC
Huawei Confidential
Page 303
Verification
Availability and Benefits Observation
Counter
Description
VS.Video.Total.DLTraffic
The total downlink traffic volume of Video in a Cell
VS.Video.Total.DLTransTime
The total downlink transmission duration of Video in a Cell
After feature activation ,the VS.Video.Total.DLTraffic will be other than 0.

According to the different parameters setting , the Video rate (= VS.Video.Total.DLTraffic*8/
VS.Video.Total.DLTransTime) will be different in the condition of radio or Iub resources are
insufficient.
Huawei Confidential
Page 304

Solution
Video Service Rate Adaption
VoIP Application Management WRFD-150253
Huawei Confidential
Page 305
Background
The conventional mobile communications network cannot identify VoIP services and therefore cannot
provide differentiated user experience for VoIP services by means of radio resource allocation and
scheduling. The main issues are as follows:
VoIP services are treated as best-effort (BE) services. There are no GBR, buffer delay protection, or valid VoIP QoS
improvement measures.
A large amount of VoIP data transmission may affect the data transmission of other services, such as web page
browsing. There are no effective flow control measures.
The WRFD-150253 VoIP Application Management feature identifies VoIP services among PS BE services and
sets QoS parameters for the VoIP services flexibly so that operators can provide differentiated user
experience for VoIP services.
TC: Interactive, Background, No GBR or delay control
internet
UTRAN/CN
UTRAN/CN
TC: Conversation, Streaming, GBR and delay guaranteed
Huawei Confidential
Page 306
Introduction
The feature provides the following functions:
VoIP service rate management: Based on the VoIP bit rate requirement in the network, this feature sets the guaranteed bit rate for VoIP
services to minimize the impact of resource congestion on VoIP service rates.
VoIP buffer delay management: During HSDPA scheduling, the RNC controls the maximum buffer delay of VoIP service data. VoIP
service data is sent on the Uu interface before its buffer delay exceeds the maximum buffer delay. The DlMaxDelay parameter specifies
the maximum buffer delay. The RAN can blindly send signals to the UEs in weak coverage areas. This reduces the downlink buffer delay.
VoIP service rate control: You can limit the data rates of VoIP services by setting the downlink SPI weight adjustment coefficient
(specified by the DLSpiWeightAdjCoef parameter) for VoIP services to an appropriate value. This prevents a large number of VoIP
services from affecting other services.
VoIP Buffering delay management in
RAN
VoIP Rate Management in RAN
UE Throughput
UE Throughput
Priority
S-GBR
VoIP Rate Restriction in

RAN
time
time
Huawei Confidential
S-MaxDelay Buffer time
Page 307
Impact
Benefits
When radio resources or Iub resources are insufficient, this feature increases the data rates of
VoIP services and decreases the service delay using service-specific QoS policies. This improves
user experience for VoIP services. Alternatively, this feature can also limits the data rates of
VoIP services and thereby improves user experience of other services.
Negative Impact
If service rate management is performed on VoIP users configured with SGBR in a cell, the cell
throughput may be different , which depends on UE distribution, SGBR setting of VoIP users ,
distribution of VoIP users, and SPI weight.
The VoIP users with good radio quality and lower data rate than SGBR are more likely to
be scheduled, which will increase the cell throughput.
The VoIP users with poor channel quality and lower data rate than SGBR are more likely
to be scheduled, which will decrease the cell throughput.
Huawei Confidential
Page 308
Dependency
RNC hardware
NodeB hardware
The 3900 series base stations, DBS3900, BTS3900C, and BTS3902E must be configured with the WBBPb,
WBBPd, or WBBPf board. The WBBPa board does not support this feature.
This feature does not have any special requirements for the CN if the RAN performs service type
awareness. When the CN performs service type awareness, this feature requires the CN to contain DSCPs
for VoIP services in the UE IP packet headers.
License
An optional feature with new license control on RNC.
Huawei Confidential
Page 309
Dependency
Dependency on other feature

None

None
WRFD-020806 Differentiated Service Based on SPI Weight:
If these two feature are activated simultaneously, the final SPI Weight value ( Based on the original SPI weight value
and DLSpiWeightAdjCoef from this feature must be from 1 to 100 , or some differentiation benefit may
disappear.
WRFD-020132 Web Browsing Acceleration:
For the heavily congested network, these two features can not get the maximum benefit simultaneously , and the
final benefit is up to the Qos parameters of Web and VoIP service.
WRFD-150254 Differentiated Service Based on Application Resource Reservation
The final benefit of WRFD-150253 is up to the HSDPA power occupation and HSDPA maximum power proportion of
VoIP service group . If the former is higher than the latter, the final benefit of WRFD-150253 is up to WRFD150254.
WRFD-140221 HSDPA Scheduling Based on UE Location
Its not recommended to activate these two features simultaneously, The target of WRFD-140221 is to get the
maximum cell HSDPA throughput , while the one of WRFD-150252 is to get the best VoIP experience , which are
different and both can not reach the expected gain if simultaneously activated.
Huawei Confidential
Page 310
Verification
Availability and Benefits Observation
Counter
Description
VS.VoIP.Total.DLTraffic
VS.VoIP.Total.DLTransTime
The total downlink traffic volume of VoIP in a Cell

The total downlink transmission duration of VoIP in a Cell
The total scheduled times of the delay-sensitive BE service for HSDPA
users
The total blindly scheduled times of delay-sensitive BE service for
HSDPA users
The total traffic volume of delay-sensitive BE service for HSDPA users
VS.HSDPA.ScheduleNum.DelaySensitive
VS.HSDPA.ScheduleNum.DelaySensitive.Bli
nd
VS.HSDPA.DelaySensitive.DataOutput
VS.HSDPA.DelaySensitive.DataOutput.Urge
ncy
The total traffic volume of delay-sensitive BE service for HSDPA users
After feature activation ,the VS.HSDPA.ScheduleNum.DelaySensitive will be other than 0.
According to the different parameters setting , the VoIP rate (= VoIP.Total.DLTraffic*8/ VS.
VoIP.Total.DLTransTime) will be different in the condition of radio or Iub resources are insufficient.
Huawei Confidential
Page 311

Solution
Video Service Rate Adaption
VoIP Application Management

WRFD-150254
Huawei Confidential
Page 312
Background
In the traditional UMTS network, only 4 traffic classes are defined in RAN (conversational, streaming,
interactive and background). The granularity is too wide to distinguish the actual service in the RAN, such
as web VoIP and so on. So in congestion scenario some low-value service may occupy too much radio
resource to guarantee the high-value service QoS.
WRFD-150254 Differentiated Service Based on Application Resource Reservation feature limits the
HSDPA power resources allocated to low-value services and reserves the resources for high-value services
by performing the following functions:
Identifies service types
Maps service types to resource groups
Limits the proportion of the maximum HSDPA power for the resource group
low-value service
Resource
reservation
high-value service
Huawei Confidential
Page 313
Power
resource
Resource group 1~3
Maximum proportion
Resource group 0
Introduction
Identifies service types: The RAN service awareness features to identify service types, or the CN identifies the service types and
then transfers the identification result to the RAN through DSCP values in the Iu data packets for further identification.
Maps service types to resource groups: The RNC maps the service types to the four resource groups in a cell to perform
differentiated control.
Limits the proportion of the maximum HSDPA power for the resource group: During HSDPA Uu resource scheduling, the RNC
periodically calculates the total power consumption of all users on the HS-SCCH and HS-PDSCH in each resource group of a cell.
In a lightly loaded cell, HSDPA users can use remaining downlink power resources even if the power consumption of a resource
group exceeds the configured threshold. This prevents the waste of downlink power resources. If downlink power congestion
occurs in a cell and the power consumption of all users on the HS-SCCH and HS-PDSCH in a resource group exceeds the
configured proportion of the maximum HSDPA transmit power, the SPI weight of all users in the resource group
decreases then users in other resource groups or not in any resource group take priority to use power resources.
Maps service types to

resource groups for
power limitation
WEB
100%
HSDPA Power
Limitation for Cell
60%
VOIP
40%
10%
VIDEO
P2P
Huawei Confidential
Resourc
e Group
0
Resourc
e Group
1
Page 314
Resourc
e Group
2
Resource
Group 3
Impact
Benefit
This feature brings the differentiation of service experience during the
HSDPA Power congestion of cell .
The high-value service can get more power proportion and better experience ,while low-value can only get
minimum power proportion and less experience.
Negative Impact
In the scenarios of insufficient downlink power resources, the data rates of users in a resource group may be
lower than the guaranteed bit rate (GBR) if the resource group has excessive users or the configured
maximum HSDPA power ratio is too low. In extremely severe conditions, low-priority users in the resource
group may encounter call drops because they are not scheduled for a long period of time.
Huawei Confidential
Page 315
Dependency
WRFD-010611 HSDPA Enhanced Package

None
Impacted Features
WRFD-140223 MOCN Cell Resource Demarcation

This feature does not apply on cells where the WRFD-140223 MOCN Cell Resource Demarcation feature has been
activated.
WRFD-020806 Differentiated HSPA Service Based on SPI Weight
WRFD-150255 Differentiated Service Based on Terminal
The above two features adjusts SPI weights based on user priorities to provide differentiated services. If the WRFD150254 and the anyone of the above two are used together, service differentiation may be affected by the WRFD-150254 .
For example, when downlink power congestion occurs in a cell, the data of high-priority users is unlikely to be scheduled
because the HSDPA transmit power of the resource group is limited. In this case, the data of high-priority users is not
preferentially scheduled.
WRFD-150204 Platinum User Prioritizing
The power used by platinum users is not limited by the configured proportion of the maximum HSDPA transmit power.
That is, the power consumption of a resource group to which platinum users' services map may exceed the configured
proportion of the maximum HSDPA transmit power.
Huawei Confidential
Page 316
Dependency
Dependency on hardware
Dependency on RNC hardware

Dependency on NodeB hardware

To support this feature, the BTS3812E, BTS3812A, and BTS3812AE must be configured with the EBBI, EBOI, EDLP, EULP,
or EULPd board. The HBBI and HDLP boards do not support this feature.
To support this feature, the DBS3800 must be configured with the EBBC, EBBM, or EBBCd board. The HBBU board does
not support this feature.
To support this feature, the 3900 series base stations, DBS3900, BTS3900C, and BTS3902E must be configured with the
WBBPb, WBBPd, or WBBPf board. The WBBPa board does not support this feature.
Huawei Confidential
Page 317
Verification
The real time proportion of HSDPA power for the cell resource group can be observed by the below
counters:
VS.HSDPAPwrRatio.Mean.ResG0
Benefit Observation
The real time total throughput for the service in the cell can be monitored by the below counters:
VS.Web.Total.DLTraffic
VS.P2P.Total.DLTraffic
VS.Video.Total.DLTraffic
VS.VoIP.Total.DLTraffic
The real time total time for the service occurred in the cell can be monitored by the below counters:
VS.Web.Total.DLTransTime
VS.P2P.Total.DLTransTime
VS.Video.Total.DLTransTime
VS.VoIP.Total.DLTransTime
Huawei Confidential
Page 318
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution

Huawei Confidential
Page 319
Terminal Black List WRFD-160103
Differentiated Service Based on Terminal
Huawei Confidential
Page 320
Background
New feature and new kind of terminal introduce

much more terminal incompatible issue.
This feature is to solve the terminal incompatible
issue with new feature.
Huawei Confidential
Page 321
Solutions Introduction
Terminal Black List
Stored in IMEITAC Table
Feature A switched on.

Terminal X incompatible with Feature
A.
PreRAN16.0
but
RNC
Feature A can
be switched off .
incompatible
with Feature A
Black list of feature A

added in new version.
Several
Months
Update to new
version.
Feature A has a black list, and will not take

effect on the terminals whose TAC is in the
black list.
TAC of Terminal X added

in the black list of Feature A.
Feature A can be kept actively.
Huawei Confidential
Page 322
RAN16.0
Introduction
Features with black list
RNC
Terminal Black List

Stored in IMEITAC Table
Already encounter with incompatible issue
3. If in some black list, then those

features not take effect on this UE
2. Send IDENTITY REQUEST

to get the IMEI.
WRFD-010202
CELL_PCH / URA_PCH State Function
WRFD-150246 & WRFD-151202
P2F Redirect Function
WRFD-020701
AMR/WB-AMR Speech Rates Control

New feature potential with incompatible
issue
1. UE initial some service
WRFD-160102
Garble Noise detection and correction
WRFD-160212
Radio Bearer Fast Setup
Huawei Confidential
Potential issue?
introduce new on UU interface
new kind of signaling
new IE in the signaling
Page 323
Appendix: Features or related functions with black list
Feature
Special process
Feature
WRFD-150207 4C-HSDPA
Prohibit special UE bear on 4C-HSDPA
WRFD-150250 3C-HSDPA
Prohibit special UE bear on 3C-HSDPA
WRFD-010696 DC-HSDPA
Special process
WRFD-10701 Uplink
Enhanced CELL_FACH
Prohibit special UE bear on E-RACH

Prohibit special UE amr rate adjustment
Prohibit special UE bear on DC-HSDPA
WRFD-020701 WBAMR/WBAMR Speech Rates Control
WRFD-150209 DB-HSDPA
Prohibit special UE bear on DB-HSDPA
WRFD-020106 Load
Reshuffling
Prohibit special UE using SF reconfigure
WRFD-140204 DC-HSUPA
Prohibit special UE bear on DC-HSUPA
WRFD-010686 CPC - DTX /

DRX
Prohibit special UE bear on CPC - DTX / DRX
Prohibit special UE to do the garbled voice

detection and correction
WRFD-010688 Downlink
Enhanced CELL_FACH
Prohibit special UE bear on E-FACH
WRFD-160102 Garbled Voice

Detection and Correction for
AMR Services
WRFD-01061006 HSDPA
Mobility Management
Prohibit special UE using compress mode on

HSPA+
Prohibit special UE using D2P instead of D2F

Prohibit special UE using PCH to EFACH
instead of PCH to FACH

HSDPA
WRFD-01061204 HSUPA
Mobility Management
Huawei Confidential

HSUPA
HSPA+
Page 324
Appendix: Features or related functions with black list
Feature
WRFD-150220 Coverage Based PS
Handover from UMTS to LTE
WRFD-140218 Service-Based PS Handover
from UMTS to LTE
WRFD-150217 Load Based PS Handover
from UMTS to LTE
Special process
Prohibit special UE measure
GUL simultaneously in
compress mode instead of
measure GU and LTE
respectively
WRFD-010202 UE State in Connected Mode Prohibit special UE state transit

(CELL-DCH, CELL-PCH, URA-PCH, CELLto PCH state
FACH)
WRFD-020500 Enhanced Fast Dormancy
WRFD-010202 UE State in Connected Mode Prohibit special UE using D2P
(CELL-DCH, CELL-PCH, URA-PCH, CELLFACH)
WRFD-010652 SRB over HSDPA
Prohibit special UE bear on
SRBoH
WRFD-160212 Radio Bearer Fast Setup
WRFD-150246 Service Steering and Load
Sharing in CELL_FACH State
Prohibit special UE using RB

fast setup
Prohibit special UE using P2F
redirecition
WRFD-151202 FACH Pool

Feature
Special process
WRFD-140103 Call Reestablishment
Prohibit special UE reestablished on

CELL_FACH instead of CELL_DCH
WRFD-020801 Cell ID + RTT

Function Based LCS
WRFD-020803 A-GPS Based LCS
Prohibit special UE CELLID+RTT function
Downlink BLER periodical

measurement
Prohibit special UE downlink BLER

periodical measurement
UE transmit power periodical

measurement
Prohibit special UE transmit power

periodical measurement
Fast Recfg in HHO
Prohibit special UE Fast Recfg in HHO
RB SETUP message shorten
Prohibit special UE RB SETUP message

shorten
HSPA service change message

shorten
Prohibit special UE HSPA service change

message shorten
WRFD-140104 Enhanced Combined

Services
Prohibit special UE in combined services

DL DCH rate over 8kbps
WRFD-02060501 SRNS Relocation

(UE Not Involved)
Prohibit special UE SRNS Relocation (UE

Not Involved)
Huawei Confidential
Prohibit special UE A-GPS based LCS
Page 325
Impact Analysis
Positive Impact
If there are terminals incompatible with new feature, TAC of these terminals can be
configured in black list, while other terminal can still using the new feature.
No need to waiting for months to update to new version that add black list function of the
feature
Negative Impacts
None.
Huawei Confidential
Page 326
Dependency
No dependency.
License
No dependency.
This is a basic feature and No License control .
Default not used. It is recommended to use when certain terminal incompatible with
certain feature.
Huawei Confidential
Page 327
Verification
Observation after Activation
Feature will not take effect on terminals in the black list.
Observe the Counters that indicate feature activation. If reduced number is near to the incompatible issues that
analyzed before. It turns out the black list function of this feature has been active.
Another way to observe
UE Trace according to IMEI.

For example,
Black list of Radio Bearer Fast Setup
1. Counter VS.RAB.AttEstabCS.FastSetup
or VS.RAB.AttEstabPS.FastSetup
or VS.MultiRAB.AttEstabCS.FastSetup
will be reduced.
2. UE trace of certain IMEI indicate the fast setup function
not taken effect on.
Huawei Confidential
Page 328
Terminal Black List
Differentiated Service Based on Terminal WRFD-150255
Huawei Confidential
Page 329
Background
In heavy load network, resource congestion will lead to worse user experience , but there are high-value
and Low-value terminal UEs in network and Operator desires to guarantee the high-value terminal
UEs experience.
This feature allocates the IMEI_TACs of terminals on different terminal groups and specify the SPI weight
for each terminal group to provide different service quality for respective terminal groups in congested
cells.
Cell Resource
High-Value Terminal UEs (SPIWeight=100)
Cell Resource
Middle-Value Terminal UEs SPIweight=50
Cell Resource
Low-Value Terminal UEs SPIweight=1
Cell Resource
In Congested Cells The proportion of Cell Resource

Occupancy
High-Value Terminal Ues Middle-Value Terminal Ues LowValue Terminal Ues is 100:50:1
Huawei Confidential
Page 330
Introduction and Impact
Introduction
This feature obtains the terminal types of UE(IMEI_TAC) through PS IMEI inquiry procedure
This feature allocates IMEI_TACs of terminals to different terminal groups(The specification of group numbers
of is 64 ) and specifies the SPI weight for each terminal group. SPI weight affects the service quality
enjoyed by each UE Services with greater SPI weights take precedence over services with smaller SPI weights
and obtain satisfactory quality(higher rate and less latency) .
This feature only take effect when the cell resource is congested, such as HSDPA Power CE Iub etc.
Benefit
This feature brings the differentiation of
experience for different terminals during cell resource
congestion . The high-value terminals can get higher priority and better experience over the low-value
terminals .
Negative Impact
This feature may have negative impact in the following scenarios:
Supposed the UEs in weak coverage have higher priority , which will improve the scheduled opportunities
of these UEs , but the cell resource efficiency and cell throughput will be decreased
Huawei Confidential
Page 331
Dependency
When applied in the downlink on the Uu interface, this feature depends on the feature WRFD-01061103
Scheduling based on EPF and GBR.
When applied in the uplink on the Uu interface, this feature depends on the feature WRFD-01061402 Enhanced
Fast UL Scheduling or WRFD-010638 Dynamic CE Resource Management. When this feature is enabled together
with the feature WRFD-01061402 Enhanced Fast UL Scheduling, only the uplink Uu interface resources can be
differentially scheduled. When this feature is enabled together with the feature WRFD-010638 Dynamic CE
Resource Management, both the uplink Uu interface resources and CE resources can be differentially scheduled.
When applied in the downlink on the Iub interface, this feature depends on the features WRFD-010610 HSDPA
Introduction Package and WRFD-050405 Overbooking on ATM Transmission, or depends on the features WRFD010610 HSDPA Introduction Package and WRFD-050408 Overbooking on IP Transmission.
When applied in the uplink on the Iub interface, this feature depends on the feature WRFD-01061212 HSUPA Iub
Flow Control in Case of Iub Congestion.
None
Huawei Confidential
Page 332
Dependency
Impacted Features
HSUPA Scheduling Based on UE Location, which is an R15.0 enhancement of WRFD-01061209 HSUPA HARQ and Fast UL
Scheduling in NodeB, will reduce the SPI weight for UEs in soft handovers.
WRFD-150204 Platinum User Prioritizing: The SPI weight for platinum users is always 100.
WRFD-150233 Differentiated Service Based on Resource Reservation :
Introduce the function of identifying service types so that the SPI weight adjustment factor can be calculated for a
specific service type. The actual SPI weight equals the original SPI weight multiplied by the SPI weight
adjustment factor. That is, the actual SPI weight depends on the original SPI weight and the service type.
Introduce the function of bandwidth management. For a user queue where the attribute of user data rate is service
GBR (SGBR) or service HBR (SHBR), if the user data rate is less than SGBR or SHBR, the scheduling weight of the user
queue will be multiplied by an adjustment factor that is greater than 1 to raise the scheduling probability and
thereby to increase the user data rate for the queue; if the user data rate is greater than SHBR, the scheduling weight
of the user queue will be multiplied by an adjustment factor that is less than 1 to reduce the scheduling probability and
thereby to decrease the user data rate for the queue
License
An optional feature with new license control on RNC level.
Huawei Confidential
Page 333
Verification
Availability and Benefit Observation
Counter Name
VS.HSDPA.BeChThroughput.DevGrpx (0~7)
VS.HSUPA.BeChThroughput.DevGrpx(0~7)
Description
The HSDPA MAC-d flow average downlink throughput for BE traffic
queue of users in DevGrpx (0~7)
The HSUPA MAC-d flow average uplink throughput for BE traffic
queue of users in DevGrpx (0~7)
After feature activation , one VS.HSDPA.BeChThroughput.DevGrpx or VS.HSUPA.BeChThroughput.DevGrpx

will be other than 0 ,if the corresponding group is configured .
For a HSPA cell, The users from the terminal group with higher priority will have higher throughput
than the ones from lower priority group in heavy traffic hours.
Huawei Confidential
Page 334
Content
1
Summary of RAN16.0

UMTS HD Voice
UMTS SON Solution

Huawei Confidential
Page 335
HSUPA Power Control WRFD-01061203 -- Power Control Enhancement
E-DPCCH Boosting
RSCP- and RTWP-based Adjustment of HSUPA Small Target Retransmissions
HSUPA forcible scheduling despite of NACK messages on the serving link
Rollback of the Process for Switching SRBs During the DRD
Huawei Confidential
Page 336
Introduction (Scenario 1)
UMTS network is a self-interference system, so the interference among multiple UEs

leads to alternative RTWP increase.
HSUPA Traffic
c
raffi
PA T
U
S
H
c
HSDPC
C
H Loa
d
P
Tra
ffi
99
Vo
I
HSDPA
In heavy load cell, there are large numbers of

UEs with the majority is HSUPA UEs . Once
there is abnormal RTWP increasing because of
mutual interference, all UEs in this cell is
unhappy.
PS
R
c
d
HSUPA Traffic
affic
A Tr
P
U
HS
HSUPA Power Control Enhancement
HSDPA
HSDPC
C
H Loa
Vo
IP
Tra
ffi
99
Tra
ffi
affi
Tr
PS
R
R
AM
HS
UP
A
affi
Tr
Tra
ffi
ffi
Tra
A
UP
HS
ffi
Tra
A
UP
HS
R
AM
HS
UP
A
Decrease the interference of HSUPA UEs by joint

optimization for inner loop and outer loop power
control.
As a result, cell throughput may increases
2%~10%, and system stability is improved in this
high load cell.
Huawei Confidential
Page 337
Introduction (Scenario 2)
When a small quantity of HSUPA UEs are performing high-rate data transmission
(such as higher than 2 Mbit/s) in the scenario multipath effect, transient RTWP
peaks frequently occur.
Tra
ffic
H Loa
d
HSDPC
C
HSDPA
In a heavy load cell, there may have a small

quantity of HSUPA high rate UEs and other
low rate UEs. Once there is transient RTWP
peak from high-rate uploading(such as
higher than 2 Mbit/s), all other UEs in this
cell are unhappy.
PS
R9
9
Tra
ffic
H Loa
d
HSUPA Power Control Enhancement
HSDPA
PS
R9
9
R
AM
ffi
Tra
s
h a ve
uc abo
c (s
ffi e is
Tra at
A gr
UP in
HS load s)
up bit/
2M
s
h a ve
uc abo
c (s
ffi e is
Tra at
A gr
U P in
HS load s)
up bit/
2M
R
AM
ffi
Tra
HSDPC
C
Decrease the interference of HSUPA

high rate UEs by optimizing the inner
loop power control and cell
throughput increases 5%~10%.
Huawei Confidential
Page 338
Solution Introduction
The algorithm of HSUPA power control

enhancement takes effect independently for the
three categories of UEs:
high-rate non-DTX HSUPA UE

low-rate non-DTX HSUPA UE
DTX HSUPA UE.
Notes:
Note 1: The feature of HSUPA power control enhancement includes
two switches: ULINNERPCABNRISECTRLSW induced in RAN16.0
and RTWPSIRTGTADJSW induced in RAN 14.0.
Note 2: The UE identification algorithm is induced in RAN 14.0.
Note 3: RTWP congestion threshold is calculated by real time
dynamical target load. if real time measurement RTWP exceeds RTWP
congestion threshold, its regarded as abnormal RTWP rise .
Note4: The function that NodeB reports UEscongestion indication to
RNC is introduced in RAN14. If RNC receives some UEs congestion
indication , RNC sets that UEs maximum SIR target value equals to
min{current SIR target, initial SIR target}, and RNC starts a 50ms
timer to maintain maximum SIR target unchanged during this time.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 339
Dependency
3900 series base stations, uplink of a cell must be carried on the WBBPd, WBBPf, or UBBP
boards, and downlink of a cell must be carried on the WBBPb, WBBPd, WBBPf, or UBBP
boards.
None
License
This Feature is an Enhancement of WRFD-01061203 HSUPA Power Control , and no more

License Control introduced from R16.0.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 340
Verification
Scenario with multipath effect in which uplink services are carried on WBBPd boards
Step1 On the RNC LMT main page, click Monitor. In the Monitor Navigation Tree pane, choose
Monitor > UMTS Monitoring > Connection Performance Monitoring. The Connection
Performance Monitoring dialog box is displayed. In this dialog box, set Monitor Item to OLPC.
Use an HSUPA UE to perform continuous FTP data transmission.
Check whether the target SIR decreases by 1 to 3 dB. If the target SIR has decreased by 1 to 3 dB,
this feature has been activated.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 341
Verification
Scenario in which uplink services are carried on the WBBPf or UBBP boards Check whether
this feature is activated by tracing messages.
Step 1 Trace DSP-level CDT: ASIC Chip GlobalPara
Step 2 Check whether this function takes effect by observing the following IEs:
ucUlPcAbnCtrlSwitch and aucCell0RwpAbnSirReviseSwitch.
If the value of any of the preceding IEs is 1 for a cell, this function has been activated.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 342
Verification
Benefit Observation
VS.CellDCHUEs
It is expected to increase after feature activation
VS.HSUPA.MeanChThroughput
It is expected to increase after feature activation
VS.MeanRTWP
It is expected to decrease after feature activation
VS.MaxRTWP
It is expected to decrease after feature activation
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 343
E-DPCCH Boosting WRFD-010697
Huawei Confidential
Page 344
Background
E-DPCCH Boosting is used for HSUPA
only.
If the used E-TFCI > E-TFCIec, boost:
The maximum power allowed on EDPDCH is enlarged to support higher

UL throughput.
Tx power on E-DPCCH is increased.
E-DPCCH is the reference channel

for E-DPDCH instead of DPCCH.
w/o boosting
with boosting
E-DPDCH
E-DPCCH
DPCCH
E-DPDCH
E-DPCCH
DPCCH
E-DPCCH
Boosting
Reference channel for EDPDCH estimation
E-DPCCH Boosting is introduced in 3GPP Release 7 to support UL high throughput over HSUPA.
Huawei Confidential
Page 345
Introduction
E-DPCCH Boosting
configuration based
on:
SG_Grant allocation to support

E-DPCCH Boosting is based
on:
Msg: E-DPCCH
Boosting capability
UE and Cell capability

Switches
Traffic characters
Msg: E-DPCCH
Boosting config info
RNC
NodeB
Bo Ms
os g:
tin Eg DP
Bo Ms
ca CC
os g:
pa H
tin E
bi
g -DP
lit
co C
y
nfi CH
g
in
fo
SG_Grant
UE
Real UL rate
Traffic in UL buffer
CE resource is enough to support high
bit rate.
E-DPCCH Boosting usage

based on:
SG_Grant
E-TFCI to tx >E-TFCIec,boost
Available tx Power
Whether E-DPCCH Boosting is used or not is decided by UE

dynamically every TTI.
Huawei Confidential
Page 346
Introduction
Cells in same carrier
Boosting
E-DCH with
E-DPCCH
Boosting
E-DCH with
E-DPCCH
Boosting
Boosting
E-DCH without EDPCCH Boosting
Non Boosting
Boosting
E-DCH without EDPCCH Boosting
E-DPCCH Boosting is activated only if all the cells in active set support it.
Huawei Confidential
Page 347
retry
E-DCH with
E-DPCCH
Boosting
Impact
Gain=43%
E-DPCCH Boosting improves the user UL throughput by:
Increasing the power of E-DPDCH;

Taking E-DPCCH as the reference estimation channel which have enhanced quality over
DPCCH.
Huawei Confidential
Page 348
Dependency
Boosting Feature: WRFD-010697

Licenses of HSUPA introduction packet and E-DPCCH boosting
are available;
UE is R7 or later version and supports E-DPCCH boosting.
Switch of E-DPCCH boosting is ON.
Hardware dependency of NodeB:
EULPd board is required for BTS3812E/BTS3812AE

EBBCd board is required for DBS3800
WBBPd boards are required by 3900 series NodeB.
Huawei Confidential
Page 349
Verification
Counter Name
Measured object
VS.HSUPA.Boosting.UE.Mean.Cell
CELL
Mean Number of HSUPA Boosting UE in the cell
VS.HSUPA.RAB.Boosting.AttEstab
CELL
HSUPA Boosting RAB Establish Attempted times
VS.HSUPA.RAB.Boosting.SuccEstab
CELL
HSUPA Boosting RAB Establish Successful times
VS.HSUPA.RAB.AbnormRel.Boosting
CELL
HSUPA Boosting RAB abnormal releasing times
VS.HSUPA.RAB.NormRel.Boosting
CELL
HSUPA Boosting RAB normal releasing times
VS.HSUPA.Boosting.UtilizeTimeRatio
NodeBLocalCell
Counter Description
Utilized time ratio of HSUPA Boosting
Huawei Confidential
E-DPCCH Boosting
HSUPA Coverage Enhancement at UE Power Limitation WRFD-020138
Huawei Confidential
Page 351
Introduction
By 3GPP R6 definition, UE is forced to decrease EDPDCH power offset to a fixed minimum value 8/15
when UE TX power limitation.
For HSUPA service, coverage of ed 8/15 (Point A) is worse than ed,best (Point B) .
By 3GPP R8 definition, RNC can configure the EDPDCH power offset value when UE power limitation.
The configured value can be the best power offset, and keep the call from drop.
Point
A
ed/ c 8/15
NodeB
Point
A
NodeB
ed/ c 8/15
Point
B
ed,best
UE may keep the best power offset, and by

adding BLER, the coverage can be extended
to Point B.
RNC can configure the best power offset at UE power limitation, and send it to UE with
Radio Bear Reconfiguration message.
The best power offset value has better coverage than the value 8/15 and call drop is
avoided.
Page 352
Huawei Confidential
Impact
WRFD-010612 HSUPA Introduction Package
Coverage of HSUPA will be improved when the feature takes effect
None
None
Huawei Confidential
Page 353
Verification
Gain Observation
VS.HSUPA.RAB.AbnormRel.SRBoE.AboveR8
VS.HSUPA.RAB.NormRel.SRBoE.AboveR8.All
Calldrop Target of UE Supported the Feature

=(VS.HSUPA.RAB.AbnormRel.SRBoE.AboveR8)/
(VS.HSUPA.RAB.NormRel.SRBoE.AboveR8.All)
Huawei Confidential
Page 354
E-DPCCH Boosting
Initial HBD(Happy Bit Delay) Selection Based on Load IntFD160093

Retransmissions

serving link
Initial Target Value Optimization of UL Error Bits
Huawei Confidential
Background and Introduction
Background
Happy bit delay(HBD) time

Delay time of decision for HSUPA happy bit, which is introduced in 3GPP 25.321. If all the buffered user data
can be transmitted at the current rate during the time specified by this parameter, the HSUPA happy bit is set
to happy; otherwise, the HSUPA happy bit is set to unhappy.
If shorter happy bit delay time is used , the HSUPA happy bit is more easily set to Unhappy. Then, the data can
be transmitted faster, and the customer feeling will be improved.
Introduction
Principles
The function can short happy bit delay time to increase HSUPA UEs unhappy state proportion in the low uplink
load network. In this way, the HSUPA UEs can get bigger Scheduled Grant(SG) . Then, these UEs can transmit
bigger TBS as long as their data buffers are not empty and no power limitation. As a result, the HSUPA
throughput will be improved.
Typical Scenario
This function can be used in the network whose RTWP rise is smaller than 3.5dB and there is at least one
HSUPA user in the cell.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 356
Benefit and Verification
Benefits
Negative Impact
The RTWP may rise because of larger throughput in the low uplink load cell.
The value of NodeB counter VS.HSUPA.UnHappyUserNumRatio may become much larger
Dependency
If enabled, the HSUPA single user throughput will be improved 5%~10% in the low uplink load cell.
Basic Function without new License
Do a HSUPA FTP upload test and trace the UU interface CDT in the RNC LMT. Then, query the RB Setup information, if the value of
HappyBit-DelayCondition is ms2, it means the function is activated.
Gain Verification
HSUPA single user throughput will increase
(VS.HSUPA.2msTTI.Traffic+VS.HSUPA.10msTTI.Traffic)/(VS.HSUPA.2msPDU.TTI.Num*0.002+VS.HSUPA.10msPDU.TTI.Num*0.01)
RTWP will increase
Unhappy user number will increase
The RTWP may rise because of larger throughput, which can be monitored by RNC Counter VS.MeanRTWP.
The HSUPA Unhappy users may be larger, which can be monitored by NodeB counter VS.HSUPA.UnHappyUserNum and
VS.HSUPA.UnHappyUserNumRatio.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 357
E-DPCCH Boosting

Retransmissions
IntFD-160090

serving link
Huawei Confidential
Introduction
This function belongs to Adaptive Adjustment of HSUPA Small Target Retransmissions WRFD140222
Key Change
Before R16, Adaptive Adjustment of HSUPA Small Target Retransmissions only supports adjustment based on RTWP.
From R16, Adaptive Adjustment of HSUPA Small Target Retransmissions supports adjustment based on RTWP and RSCP
Typical Scenario
It is recommended that the function be enabled in a cell that meets the following conditions:
Benefits
The uplink load of the cell is not restricted.

Many HSUPA UEs have a low throughput.
When the uplink load of the cell is not restricted and a large number of UEs are processing low-speed HSUPA services, the
function increases the uplink throughput of the cell by up to about 5% compared with the RTWP-based Adjustment of
HSUPA Small Target Retransmissions function, if some UEs are continuously performing upload services.
Gain Verification
When the uplink load is unlimited and a large number of UEs are processing low-speed HSUPA services, this feature
improves the cell throughput. To verify the effect of this feature, check the value of the counter
VS.HSUPA.MeanChThroughput.TotalBytes, With the traffic pattern unchanged, this feature is supposed to increase the
value of VS.HSUPA.MeanChThroughput.TotalBytes
Huawei Confidential
E-DPCCH Boosting

Retransmissions

serving link
IntFD-160042
Huawei Confidential
Background
On live networks, an inappropriate downtilt or pilot power may cause unbalanced UL and DL coverage for HSUPA UEs
during soft handovers.
In this situation, the DL serving link quality is optimum and the UL serving link quality is worse than the UL non-serving
link quality. A cell change, which is determined by the DL pilot signal quality, cannot be triggered for HSUPA UEs.
The UL serving link of an HSUPA UE experiences frequent errors (NACK messages received). Therefore, the the NodeB
cannot adjust the scheduling grant for the HSUPA UE, and the HSUPA service rate cannot be promptly adjusted based
on the UL air interface load and demodulation performance after UL link combination. As a result, UL air interface
resource utilization and UL cell throughput are adversely affected.
This function does not take effect in softer handovers.
CELL 1 is the serving cell. CELL 2 is a non-serving cell. The

UE moves from CELL 1 to CELL 2.
Point A is a proper handover point. Before Point A, the UL
signal quality of the serving cell is better than that of the nonserving cell.
Point B is the actual handover point. At Point B, the UL
demodulation performance of the serving link is worse than that
of the non-serving link.
Unbalanced UL and DL
coverage
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 361
Introduction
Introduction
Recognition of unbalanced UL and DL coverage: For an HSUPA UE during a soft handover (excluding a softer handover), if
the serving link continuously receives NACK messages but no retransmissions occur, the HSUPA UE is experiencing
unbalanced UL and DL coverage.
When an HSUPA UE is experiencing unbalanced UL and DL coverage, the serving cell ignores the NACK messages received
on the serving link and forces the HSUPA UE to go through a scheduling process.
This function does not take effect for HSUPA UEs in softer handovers.
Benefit
If the air interface resources are sufficient, enabling this function increases the data rate of HSUPA users that have data to
transmit during soft handovers. In this way, this function raises UL air interface resource utilization and UL throughput.
In lab tests, when a single UE performs FTP uploads and the air interface resources are sufficient, this function increases
HSUPA throughput in a soft handover area by up to 90%; when the UL air interface resources are insufficient for the
serving cell, this function enables the RTWP values to better converge on the target load.
HUAWEI TECHNOLOGIES
CO., LTD.
HISILICON
SEMICONDUCTOR
Page 362
E-DPCCH Boosting

Retransmissions

serving link

IntFD-160088
Huawei Confidential
Background
Current SRBoE DRD policy
When the SRBoE feature is applied, it is recommended that SRBoE not take effect in the RRC connection setup phase. Therefore, SRBoD
in the RRC connection setup phase is changed to SRBoE in the RAB setup phase. If a directed retry decision (DRD) is triggered during
RAB setup, the SRB is switched (D2E). If the DRD fails, the process cannot be rolled back due to the product architecture, affecting the
RAB setup success rate.
To solve the preceding problem, a two-step policy is provided for the current process for switching SRBs during the DRD:
Step 1: Complete the DRD to the destination cell using SRBoD to ensure that the process can be rolled back after a DRD failure.
Step 2: Reconfigure SRBoD to SRBoE using the HSPA retry after the DRD to the destination cell.
Problem
After the two-step SRBoE DRD policy is implemented, if the reconfiguration from SRBoD to SRBoE is triggered after the transmission of
first data, data transmission before the reconfiguration will be restricted to the maximum capability (as indicated by the green circle in the
following figure) during SRBoD. As shown in the following figure, the data transmission is restricted to TBS 5748 for a period.
Huawei Confidential
Technical Principles and Application Scenarios

Technical Principles
To avoid the throughput loss problem caused by the two-step DRD policy, its need to solve the rollback problem of the
process for switching SRBs during the DRD.

The Fast Radio Bearer Setup (Asynchronous Reconfiguration) can be implemented in the process for switching SRBs
during the DRD and solve the process rollback problem.
Optimized Asynchronous Reconfiguration: The RNC does not carry the activation time in the RADIO BEARER SETUP
message. If the UE returns a RADIO BEARER SETUP FAILURE message to the RNC, the process can be rolled back.
Note: Current Synchronous Reconfiguration: The RNC carries the activation time in the RADIO BEARER SETUP message.
After the activation time expires, the RNC, NodeB, and UE switch to new link parameters. If SRB changes are accompanied by
the DRD and the DRD fails, the process cannot be rolled back due to the product architecture.
Networking scenarios where the SRBoE or SRBoH is enabled and the DRD is performed during RAB setup.
Networks with high requirements on user experience, including throughput and access delay.
Huawei Confidential
Benefit and Dependency

Benefits
Compared with the Synchronous Reconfiguration method, the Asynchronous Reconfiguration method used in the scenario of
switching SRBs during the DRD solves the process rollback problem, increases the RAB setup success rate, and reduces user
access delay.
Compared with the two-step SRBoE DRD policy, the technical solution improves users' throughput experience in the initial
access phase. The SRBoE has high requirements on coverage. Therefore, if the coverage is weak, the DRD success rate
decreases and the user access delay caused by DRD failure may deteriorate.
Dependency
Dependency
Hardware dependency: none. License: none.
Feature dependency: WRFD-010636 SRB over HSUPA, WRFD-010652 SRB over HSDPA, and WRFD020400 DRD Introduction Package
License
Basic function without License
Huawei Confidential
Verification
None. Needs to refer to the signaling process.
Compared with the two-step SRBoE DRD policy, evaluate the feature performance:
Check the user access delay and throughput in the initial access phase using the single-user test and add the
signaling observation points and quantification method.
Check the DRD success rate based on VS.DRD.RBSetup.SuccOut or VS.DRD.RBSetup.AttOut. The DRD success
rate decreases slightly.
Huawei Confidential
Content
1
Summary of RAN16.0

UMTS HD Voice

UMTS SON Solution


Huawei Confidential
Page 368
UMTS Downlink Throughput Improvement

Solution
HSPA Serving Cell Change Optimization IntFD-160074 IntFD160089
HSDPA Mobility Management -- Fast HSDPA Serving Cell Change
HSDPA Inter-cell Power Sharing
Code Channel Usage Optimization During the HSSCCH Allocation
CQI Adjustment Performance Optimization
Assigned Bandwidth Algorithm Improvement for Users with Great CQI

Fluctuation
Huawei Confidential
Page 369
1D RSCP HSDPA Serving Cell Change

Issue Scene
Solution
New Event 1D based on RSCP is introduced. It is only used by cells in active set.
If the signal quality of a cell in the active set is higher than best cell HystFor1DRSCP for a period of time specified by
TrigTime1DRSCP ,the UE reports event 1D.
HSDPA serving cell changed is triggered when 1D report is received.
Benefit
HSDPA Serving cell change ping-pong issue due to EcIo fluctuate.
Number of ping-pong HSDPA Serving Cell Change will decrease because CPICH RSCP is not load dependent and fluctuates less
than CPICH Ec/No.
HSDPA User Throughput will improve due to reducing ping-pong HSDPA Serving Cell Change.
Network impact
No negative impact.
Huawei Confidential
Page 370
Dependency Verification and Performance

Evaluation
Dependency
Verification
Check if number of VS.HSDPA.SHO.ServCellChg.SuccOut,VS.HSDPA.SHO.ServCellChg.AttOut decreases.
Check if number of VS.HSDPA.SHO.ServCellChg.SuccOut,VS.HSDPA.SHO.ServCellChg.AttOut
decreases.
We suggest to use drive test to check HSDPA user throughput benefit, the following KPI can also check.
HSDPA User Throughput(Kbit/s) = VS.HSDPA.MeanChThroughput.
Huawei Confidential
Page 371
1X Event Optimization for HSPA Serving Cell

Change
Issue Scene
1D event may wrongly trigger HSPA Serving cell change if there exists cells whose signal
quality are better than trigger cells.
1A/1C event cant directly trigger HSPA Serving cell change even if signal quality of added
cell is good enough.
Solution
1A/1C event can directly trigger HSPA Serving cell change when following condition fulfilled.
Added cell's signal quality > Current Serving cell's signal quality + CIOBest + Hyst1AOr1CTrigSCC/2
Better cell in 1D event can trigger HSPA Serving cell change when following condition
fulfilled.
Better cell's signal quality > 1D Trigger cell's signal quality + CIOBest +
Hyst1DJudgeTrigSCC/2
Huawei Confidential
Page 372
1X Event Optimization for HSPA Serving Cell

Change
Benefit
HSDPA User Throughput will improve due to triggering HSPA Serving Cell Change fast
and accurately .
Network impact
No negative impact.
Huawei Confidential
Page 373
Dependency Verification and Performance

Evaluation
Dependency
Verification
Check if number of VS.HSPA.ServCellChg.1A1COptTrig, VS.HSPA.ServCellChg.1DOptTrig is

higher than zero.
Check if number of VS.HSPA.ServCellChg.1A1COptTrig, VS.HSPA.ServCellChg.1DOptTrig is higher than zero.

We suggest to use drive test to check HSDPA user throughput benefit, the following KPI can also check.
HSDPA User Throughput(Kbit/s) = VS.HSDPA.MeanChThroughput.
Huawei Confidential
Page 374

Solution
HSDPA Mobility Management WRFD-01061006 -- Fast HSDPA

Serving Cell Change Change

Fluctuation
Huawei Confidential
Page 375
Fast HSDPA Serving Cell Change

EX:
1.
The UE moves from HSDPA cell 1 to HSDPA cell 2,

that the two cells are intra-frequency neighboring cells,
and that all the cells in the active set support HSDPA
2.
The RNC updates the HSDPA serving cell according to

the reported event and keeps the HSDPA serving cell
consistent with the best cell.
Problem
Time delay of RNC updating the HSDPA serving cell needs 1 second at least, if signal quality of cell1
becomes worse quickly during RNC updating the HSDPA serving cell, then throughput of HSDPA user
decreases a lot.
Huawei Confidential
Page 376
Description
RNC includes 'Delay restriction flag' IE in serving

cell change RRC: PH CH RECFG message,UE
will send RRC:PH CH RECFG CMP message as
quickly as possible.
It is possible to use predefined HSDPA serving

cell change procedure specific activation time
1> if the IE "Delay restriction flag" is received and activation time T is
value, this predefined activation time impacts only

the PH CH RECFG message used for SCC
procedure, it enables setting SCC activation time
more than 128 frames from the CFN at which the message was
received:
even more aggressive, without impacting other
2> choose an activation time T as soon as possible after reception of
procedures.
the message, respecting the performance requirements in subclause
Unnecessary information elements of RRC:PH
13.5, which is common to all the transport channels that are
CH RECFG CMP message for SCC procedure
multiplexed onto the reference CCTrCh.
are removed, it enables SCC procedure much

faster.
Notes:
All services except CS Over HSDPA & VOIP Over HSDPA & PTT Over
HSDPA &SRB Over HSDPA will apply fast serving cell change.
Huawei Confidential
Page 377
HSDPA Serving Cell Change latency will improve about ~700ms if switching on HSDPA Serving Cell Change
message omission function.
HSDPA Serving Cell Change Success Rate will improve about 5%~10% when switch on Fast HSDPA Serving
Cell Change and message HSDPA Serving Cell Change omission function.
HSDPA User throughput in drive test will improve about ~10% when switch on Fast HSDPA Serving Cell
Change and message HSDPA Serving Cell Change omission function.
Only Switching Fast
HSDPA Serving Cell
Change
Huawei Confidential
Page 378
Dependency and Verification
Dependency on Feature /License
None
This is a Enhancement of Optional Feature : HSDPA Mobility Management WRFD01061006
Verification
Check PH CH RECFG message for HSDPA Serving Cell Change whether IE 'Delay restriction flag
'exists.
Huawei Confidential
Page 379
Check KPI as following
Service Cell Change Success Ratio with SHO (H2H) =

(VS.HSDPA.SHO.ServCellChg.SuccOut/VS.HSDPA.SHO.ServCellChg.AttOut) x 100%
We suggest to use drive test to check HSDPA user throughput benefit, the following KPI can also
check.
HSDPA User Throughput(Kbit/s) = VS.HSDPA.MeanChThroughput .
Huawei Confidential
Page 380

Solution
HSDPA Inter-cell Power Sharing WRFD-160251

Fluctuation
Huawei Confidential
Page 381
This feature is implemented on the NodeB.
When a power amplifier (PA) serves multiple HSDPA cells, an HSDPA cell can dynamically use the available power resources of
another HSDPA cell.
Assumes that cell A has HSDPA data to transmit with insufficient power resources while cell B has available power resources. In
this situation, cell B shares its power resources with cell A. When HSDPA data transmission in cell A is complete, cell B reclaims
the shared power resources. If cell B has HSDPA data to transmit while HSDPA data transmission in cell A is in progress, cell B will
instantly reclaim the shared power resources to provide continued user experience .
DL Power
Available
Power
100%
CELL A
Used Power
time
DL Power
Available
Power
100%
CELL B
Used Power
0
B>A
A>B
BAAHuawei Confidential
>A
>B
>B
time
Page 382
Benefit
This function increases the power resource utilization and average user throughput. When the Max Sharing Power Ratio parameter is set
to a value ranging from 40% to 50%, average user throughput is increased by approximately 5% to 10% and average edge user throughput
is increased by greater than 10%.
Simulation conditions: 3X3 Wrap Around, two carriers, HSDPA cell group with inter-frequency co-coverage, random distribution of users
Burst service model: 1Mbit/10s
Network impact
System capacity
If this function is used for cells with light traffic, both power resource utilization and average user throughput are increased.
If this function is used for cells with heavy traffic, average user throughput does not increase because such cells have high power
resource utilization and few available resources.
If this function is used between a cell with light traffic (cell A) and a cell with heavy traffic (cell B) with long periods of traffic imbalance
between the two, cell A always shares power resources with cell B. In this situation, average user throughput in cell A may deteriorate.
If this function is enabled for small-traffic services or ping services, the data transmission duration is very short and therefore the
shared power resources cannot be reclaimed in a timely manner. As a result, the service rate on the air interface is lowered and the
service delay is prolonged.
Network performance
This function increases the average cell load by 2% to 5%.

The CS/PS call drop rate and CS/PS RAB setup success rate may deteriorate to some extent due to increased downlink cell load and
increased downlink inter-cell interference. If the deterioration is greater than expected, lower the value of the Max Sharing Power
Ratio parameter.
Huawei Confidential
Page 383
Dependency
Prerequisite Features
WRFD-010610 HSDPA Introduction Package

WRFD-150236 Load Based Dynamic Adjustment of PCPICH
Do not enable the Load Based Dynamic Adjustment of PCPICH feature and the HSDPA inter-cell power sharing function to work
together. The Load Based Dynamic Adjustment of PCPICH feature decreases the P-CPICH transmit power for cells with heavy
traffic, thereby increasing cell capacity. However, this feature reduces the Ec/No of users and increases the call drop rate. The
HSDPA inter-cell power sharing function increases the maximum transmit power of cells with light traffic to improve user
experience; however, this function also reduces the Ec/No of users. If the Load Based Dynamic Adjustment of PCPICH feature
and the HSDPA inter-cell power sharing function are both enabled, the call drop rate will deteriorate.
WRFD-020116 Dynamic Power Sharing in Multi-Carriers

MRFD-221801 Multi-mode Dynamic Power Sharing
Do not enable the Multi-mode Dynamic Power Sharing feature and the HSDPA inter-cell power sharing function to work together.
WRFD-021304 RAN Sharing

The RAN Sharing feature is incompatible with the HSDPA inter-cell power sharing function, because power sharing between two cells
owned by different operators leads to unfair power resource allocation.
Huawei Confidential
Page 384
Dependency
Impacted Features
WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
The HSDPA inter-cell power sharing function causes variations in available HSDPA resources. The CQI Adjustment Based on Dynamic BLER Target
feature enables the NodeB to dynamically select a proper BLER target for HSDPA users in a cell based on available cell resources and channel
quality fluctuations, thereby achieving optimal throughput for HSDPA users. It is good practice to enable the HSDPA inter-cell power sharing
function and the CQI Adjustment Based on Dynamic BLER Target feature to work together.
WRFD-150235 DPCH Maximum Power Restriction

It is not recommended to configure the HSDPA inter-cell power sharing function and DPCH Maximum Power Restriction feature to work together. When
the cell load is high, the DPCH Maximum Power Restriction feature restricts the downlink DPCH transmit power and therefore users at the cell
edge may experience downlink synchronization failures. If the HSDPA inter-cell power sharing function and the DPCH Maximum Power
Restriction feature work together, the average cell load becomes even higher and users at the cell edge are more likely to experience dropped
calls.
WRFD-010696 DC-HSDPA, WRFD-150250 3C-HSDPA, and WRFD-150207 4C-HSDPA

The HSDPA inter-cell power sharing function does not yield gains for multi-carrier users when the power sharing cell groups belong to the same multicarrier cell group, because multi-carrier users can use available resources of multiple carriers. Since the multi-carrier user penetration rate has
increased on live networks, gains yielded by this function have been declining.
WRFD-021311 MOCN
It is not recommended to configure the HSDPA inter-cell power sharing function and MOCN feature to work together, because power sharing between
two cells owned by different operators leads to unfair power resource allocation.
Huawei Confidential
Page 385
Dependency
Hardware Dependency
3900 series base stations configured with the WBBPb, WBBPd, WBBPf, or UBBPd board support the HSDPA inter-cell power sharing function.
The BTS3902E and BTS3803E support the HSDPA inter-cell power sharing function.
The DBS3800, BTS3812E, BTS3812A, and BTS3812AE do not support the HSDPA inter-cell power sharing function.
The following table describes RF units that support this function.
Others
A cell cannot be enabled with GSM and UMTS dynamic power sharing, R99 cell and HSDPA cell dynamic power sharing, and HSDPA inter-cell power
sharing simultaneously. For details about GSM and UMTS dynamic power sharing, see GSM and UMTS Dynamic Power Sharing Feature
Parameter Description. For details about R99 cell and HSDPA cell dynamic power sharing, see Dynamic Power Sharing Among Carriers Feature
Parameter Description.
Both the cells must support HSDPA services.
Both the cells must be served by one RF module. In the scenarios of multiple RRUs in one cell, RF modules serving both the cells must be the same.
Both the cells must be owned by one operator. In the MOCN scenario, both the cells must be owned by one operator group.
Both the cells cannot work in MIMO, 2T, or VAM mode.
Both the cells cannot be served by RRUs in cold backup mode.
Both the cells cannot be configured as IMB cells.
License
This is a Trial feature without license control
Type
Model for Power Sharing
RFU
WRFU band 1, full band of the WRFUd, WRFUe, MRFUd, and MRFUe
RRU
Full band of the RRU3804, RRU3806, RRU3801E band 1

RRU3824, RRU3826, RRU3828, RRU3829, RRU3832, RRU3838, RRU3928, RRU3929, RRU3936, RRU3938, and
RRU3924
AAU
AAU3902 full band
Huawei Confidential
Page 386
Verification
Availability
The new counter is VS.HSDPAPwrShare.TtiNum, which indicates the number of TTIs when power sharing persists
between the HSDPA cells.
Gains
VS.PdschPwrRatio.Mean: indicates the average transmit power over the HS-PDSCH in a cell. This counter is
NodeB-related.
VS.PdschPwrRatio.Data: indicates the average transmit power over the HS-PDSCH when at least one HSDPA
user has data to transmit in the queue buffer. This counter is NodeB-related.
VS.PdschPwrRatio.Data: indicates the average cell throughput when at least one HSDPA user has data to
transmit in the queue buffer. This counter is NodeB-related.
Negative Impact
KPI monitoring
The CS/PS call drop rate slightly increases and CS/PS RAB setup success rate slightly decreases compared with
these KPIs before this function is enabled.
Huawei Confidential
Page 387

Solution
Enhanced HSDPA Code Utilization IntFD-160043

Fluctuation
Huawei Confidential
Page 388
Background
If the power-code balanced scheme is adopted and there are insufficient data sources, the system
gradually reduces code and power resources. As a result, there will be available downlink air interface
resources, such as power and code resources.
If the code resource priority allocation scheme is used for the last user to be scheduled in the TFRC
procedure, this saves power resources and reduces downlink load, thereby improving the KPI performance.
Description
This feature is implemented on the NodeB.
If the power-code balanced scheme is adopted and the streaming, interactive, or background services (including
initial transmission or retransmission) in the CELL_DCH state are in the last queue to be scheduled within a TTI, the
code resource priority allocation scheme is used in the queue for TFRC selection. Specially, code resources are
allocated preferentially, thereby reducing power resources .
The power-code balanced scheme is adopted in the previously scheduled queues for TFRC selection. This prevents
code resources or power resources from being exhausted, improving resource usage and ensuring cell capacity..
Huawei Confidential
Page 389
Benefit
This function can effectively reduce average network load. The amplitude of network load decrease
depends on whether data sources are sufficient.
Average HSDPA cell load is reduced by up to approximately 3%. When the HSDPA user queue buffer
has data to transmit, HS-PDSCH transmit power is reduced by approximately 5% to 10%.
Network impact
System capacity
When code resources are sufficient, this function reduces downlink load and downlink interference, thereby
increasing downlink system capacity by approximately 2% to 3%.
When codes are insufficient for the NodeB (less than 10 codes per cell on average) and code utilization for
cells is high, this function may further increase code utilization. In this situation, it is recommended that the
capacity of licensed HSDPA codes be expanded.
Network performance
The CS/PS call drop rate and CS/PS RAB setup success rate may increase slightly due to the reduced downlink
cell load.
Huawei Confidential
Page 390
Dependency
Prerequisite Features
WRFD-010610 HSDPA Introduction Package
None
Impacted Features
When one or more MIMO-related features are enabled and the last priority queue to be scheduled is of
the MIMO user type, the optimized HSDPA code utilization function does not take effect. If the MIMO user
proportion is high, gains yielded by the optimized HSDPA code utilization function are decreased.
Hardware Dependency
3900 series base stations configured with the WBBPb, WBBPd, WBBPf, or UBBP board support the
enhanced HSDPA code utilization function.
The BTS3902E and BTS3803E support the enhanced HSDPA code utilization function.
The DBS3800, BTS3812E, BTS3812A, and BTS3812AE do not support the enhanced HSDPA code
utilization function.
Other NEs
None
License
Basic function without license .

Huawei Confidential
Page 391
Verification
Availability
There is no new counter for the Optimized HSDPA code utilization function.
After optimized HSDPA code utilization is enabled, check the values of the following counters on the live network
and observe the network performance.
The values of NodeB counters VS.PdschCodeUtil.Mean.Data and VS.PdschCodeUsed.Mean increase.
The values of NodeB counters VS.PdschPwrRatio.Data and VS.PdschPwrRatio.Mean and RNC counter VS.MeanTCP
decrease.
Huawei Confidential
Page 392

Solution
Code Channel Usage Optimization During the HSSCCH Allocation IntFD160091

Fluctuation
Huawei Confidential
Page 393
Background
R99 DCH users occupy codes on the live network. Therefore, the HS-SCCH codes
cannot obtain positions near the common channel after the HSDPA is activated. This
results in restricted HS-PDSCH codes and even a loss of 2 to 3 SF16 codes. The
following provides data on the live network in Guangzhou and in the lab.
When cell H is set up on the live network in Guangzhou,

typical positions of HS-SCCH are occupied by R99 users.
When cell H is set up in the lab, typical positions of HS-SCCH are

occupied by R99 users.
Huawei Confidential
Page 394
Background
The following switches are designed in the RNC MML commands to solve the problem that the number of HS-PDSCH
codes is affected because the control channel of cell H cannot obtain typical positions.
SET UQUEUEPREEMPT:PreemptEnhSwitch= PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWITCH
The switch allows the HS-SCCH to obtain codes of R99 users when the HSDPA cell is activated, and allows the HS-SCCH to
configure positions as if there is no R99 user access. Enabling the switch results in call drops of R99 users.
SET UNBMPARA:PerfEnhanceSwitch=PERFENH_HSUPA_CCH_PREEMPT_USER
The switch allows the E-AGCH or E-RGCH to obtain codes of R99 users when the HSUPA cell is activated, and allows the EAGCH or E-RGCH to configure positions as if there is no R99 user access. Enabling the switch results in call drops of R99
users.
However, the following switches in RNC MML commands take effect when only they are enabled before HSDPA or
HSUPA cell activation.
SET UQUEUEPREEMPT:PreemptEnhSwitch=PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWITCH
SET UNBMPARA:PerfEnhanceSwitch=PERFENH_HSUPA_CCH_PREEMPT_USER
If you enable either of the preceding switches after HSDPA or HSUPA cell activation, the switch cannot take effect,
which happens mostly on the live network.
Huawei Confidential
Page 395
Technical Description and Network Impacts

Technical Description
Set the default value of SET UQUEUEPREEMPT:PreemptEnhSwitch=PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWITCH to 1

(ON). The upgrade policy is direct replacement.
Set the default value of SET UNBMPARA:PerfEnhanceSwitch=PERFENH_HSUPA_CCH_PREEMPT_USER to 1 (ON). The

upgrade policy is direct replacement.
Network Impacts
PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWITCH under the PreemptEnhSwitch parameter in the SET

UQUEUEPREEMPT command is set to on by default. However, setting up HSDPA cells may cause call drops of R99 UEs.
Therefore, it is recommended that HSDPA cells be activated when only a small number of R99 UEs process services, for
example, in the early morning.
PERFENH_HSUPA_CCH_PREEMPT_USER under the PerfEnhanceSwitch parameter in the SET UNBMPARA command is

set to on by default. However, setting up HSUPA cells may cause call drops of R99 UEs. Therefore, it is recommended that
HSUPA cells be activated when only a small number of R99 UEs process services, for example, in the early morning.
The preceding network impact descriptions will be added to the precautions for MML commands ACT UCELLHSDPA and ACT
UCELLHSUPA and to the corresponding FPDs.
Huawei Confidential
Page 396

Solution
CQI Adjustment Performance Optimization IntFD-160098

Fluctuation
Huawei Confidential
Page 397
Background
In the FET PK test in Taiwan, it has been found that:
1. When a user download a small file (3 MB), the data transmission throughput is low during the first two
seconds and the BLER during the first two seconds is obviously higher than that after the two seconds. You
can refer to the case of downloading a 9 MB file.
After the analysis, dynamic CQI adjustment does not take effect during the first 1024TTI (2s) of data
transmission, and therefore the BLER cannot be properly controlled.
Rate of downloading a 3 MB file
Rate of downloading a 9 MB file
As shown in the preceding figures, the BLER during the first two seconds for the 9 MB file is almost two
times high as that after the two seconds, which is the disadvantage of downloading a 3 MB file.
Huawei Confidential
Page 398
Technical Principles and Network Impacts

Principles
Optimize the channel type determination period of dynamic CQI adjustment and change it from 2048 ms to 512 ms. This ensures
that the channel type can be determined in a short period of time (512 ms) after RB establishment and that the BLER can be
controlled.
Network Impacts
The following is an example using the CQI analysis of drive test data in Guangzhou (morning, April 9, 2013).
The figure shows that the channel type output with the 500 ms period helps detect channel type changes more
precisely to improve the throughput. In addition, the period modification does not result in significant changes of
channel characteristics (CQI average value and CQI variance). In addition, it does not cause significant changes of
channel type determination, prevent the BLER and throughput performance from converging, and does not bring
significant negative impacts.
Huawei Confidential
Page 399

Solution

Fluctuation IntFD-160108
Huawei Confidential
Page 400
Background
The CQI fluctuation causes the NodeB buffer drop: It is found in the drive test that when the CQI is changing from a low
value to a high value, the NodeB buffer may be emptied, resulting in a throughput decrease. When the CQI is low, the air
interface data rate of the user is low. When the CQI increases, the user applies for the bandwidth based on the preceding
data rate. As a result, the obtained bandwidth is insufficient and cannot meet requirements of the current CQI data rate.
The data buffer in the MAC-hs queue is insufficient when the user has scheduling opportunities, affecting the user
throughput.
As shown in the preceding figure, when the CQI increases from 17 to 29, the NodeB buffer drops to the bottom,
causing the throughput decrease.
Huawei Confidential
Page 401
Background
The data source fluctuation causes the allocated Iub bandwidth insufficiency and NodeB buffer
drop.
10
9.5
9
8.5
8
7.5
7
PDF
6.5
6
5.5
5
4.5
4
3.5
3
2.5
2
1.5
1
0.5
0
10,000
20,000
30,000
40,000
50,000
60,000
Rlc Buf f erSize
RLC Buffer Size

95
90
85
80
75
70
PD F
65
60
55
50
45
40
35
30
25
20
15
10
5
0
0
1
F
Pre-allocated bandwidth
As shown in the preceding figure, when the data source and RLC buffer fluctuate, the pre-allocated
bandwidth is close to 0. The allocated bandwidth insufficiency results in the throughput decrease.
Huawei Confidential
Page 402
Technical Principles
1. The continuous function replaces the piecewise function in the calculation of pre-allocated bandwidth
percentage coefficient, as shown in the following figure. The segmented bandwidth reduces the
possibility of bottom drop caused by the CQI fluctuation and improves the throughput.
Pre-allocated bandwidth coefficient
2. In the process of pre-allocating bandwidth based on RLC buffer restrictions, increase the conditions
of restricting bandwidth to reduce the possibility of pre-allocated bandwidth restrictions and improve
the throughput.
Huawei Confidential
Page 403
Benefits Dependency Verification

Benefits
After the feature is enabled, the gain is about 2% to 5%.
Dependency
Hardware dependency: none
Feature dependency: WRFD-01061010 HSDPA Flow Control
License: no license
None
View the throughout and find that the throughput is increased by 2% to 5%.
Huawei Confidential
Page 404
Thank you
www.huawei.com
Copyright2013 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding
the future financial and operating results, future product portfolio, new technology, etc. There are a number of factors
that could cause actual results and developments to differ materially from those expressed or implied in the predictive
statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an
acceptance. Huawei may change the information at any time without notice.

00-Huawei RAN16.0 Solution Overview Draft (Beta 20140421) V2.9

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

00-Huawei RAN16.0 Solution Overview Draft (Beta 20140421) V2.9

Uploaded by

Copyright:

Available Formats

www.huawei.

RAN16.0 Solutions Overview

RAN16 Solutions in Details

New BBU: BBU3910

UMTS Small-Packet Storm Solution

UMTS Highly Efficient O&M Solution

Control Channel Parallel Interference

Swap Efficiency Improvement for Intra-RNC

UMTS Big Event Solution

RNC in Pool User-Plane Load Sharing

UMTS U900&U850 Solution

UMTS SON Solution

UMTS Uplink narrowband Interference

UMTS Network Sharing Solution

UMTS HetNet Micro BTS Solution

MOCN Cell Resource Demarcation

Uplink CoMP (Joint Reception)

UMTS MBB Visualization Solution

UMTS CS+PS Combined Services KPI Solution

PS initial rate of Multi-RAB is configured

UMTS Service Experience Management Solution

2D Event Type Switch Triggering IFHHO and

Differentiated Service Based on Application

UMTS Uplink Throughput Improvement Solution

UMTS User Experience Management Solution

UMTS Downlink Throughput Improvement Solution

Terminal Black List

HSPA Serving Cell Change Optimization

RAN16 Solutions in Details

UMTS HetNet Micro BTS Solution

UMTS MBB Visualization Solution

UMTS Small-Packet Storm Solution

UMTS CS+PS Combined Services KPI Solution

UMTS Highly Efficient O&M Solution

UMTS Network KPI Improvement Solution

UMTS RNC in Pool Solution

UMTS Service Experience Management Solution

NodeB Capability Improvement

New BBU: BBU3910

New baseband board: UPPB d1~d6;

HUAWEI TECHNOLOGIES CO., LTD.

BBU3910, Well-prepared for Future Evolution

Power Supply capacity increases 55%:

Backplane switch capacity

Use any BBP slot for CPRI connections.

HUAWEI TECHNOLOGIES CO., LTD.

BBU 3910 Full Mesh, No More slot limitation

The same physical size as BBU3900.

HUAWEI TECHNOLOGIES CO., LTD.

BBU 3910 Limitations

Only U-serial Boards can be used in BBU 3910. e.g.

HUAWEI TECHNOLOGIES CO., LTD.

NodeB Capability Improvement

New BBU: BBU3910

New baseband board: UPPB d1~d6;

HUAWEI TECHNOLOGIES CO., LTD.

UBBPd, Supporting Multi-mode Concurrency in One

Software configurable for a

HUAWEI TECHNOLOGIES CO., LTD.

Board number can be saved by

Serial Universal Baseband Board

HUAWEI TECHNOLOGIES CO., LTD.

Data transmission ports that interconnect the