Huawei Solutions 3G

RAN Feature Documentation
Product Version: RAN18.1

Library Version: 10
Date: 2016-12-30
For any question, please contact us.

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.
Solution Description
Contents
1 Solution Description
1.1 Voice Services
1.1.1 UMTS HD Voice Solution
1.2 Experience Management
1.2.1 UMTS HD Video Solution
1.2.2 UMTS Service Experience-based Network Construction Solution
1.2.3 UMTS User Experience Management Solution
1.3 Radio and Performance
1.3.1 UMTS Big Event Solution
1.3.2 UMTS Combined Service KPI Improvement Solution
1.3.3 UMTS Downlink Throughput Improvement Solution
1.3.4 UMTS Network KPI Improvement Solution
1.3.5 UMTS Signaling Storm Solution
1.3.6 UMTS Small Data Packet Storm Solution
1.3.7 UMTS Uplink Throughput Improvement Solution
1.3.8 UMTS Wide Coverage Solution
1.4 Networking
1.4.1 Multi-Sector GUL Joint Deployment and Evolution Solution
1.4.2 UMTS HetNet Macro-Micro Network Solution
1.4.3 UMTS Multi-Carrier Solution
1.4.4 UMTS Multi-Sector Solution
1.4.5 UMTS RNC in Pool Solution
1.4.6 UMTS U900 and U850 Network Solution
1.5 Operation and Maintenance
1.5.1 UMTS SON Solution
1.6 Network Evaluation and Planning
1.6.1 UMTS MBB Visibility Solution
1 Solution Description
Voice Services
Experience Management
Radio and Performance
Networking
Operation and Maintenance
Network Evaluation and Planning
1.1 Voice Services

UMTS HD Voice Solution
Parent topic: Solution Description
WCDMA RAN
UMTS HD Voice Solution Guide
Issue 02
Date 2016-06-23
HUAWEI TECHNOLOGIES CO., LTD.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage
scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not
constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
1.1.1 Contents
1 About This Document
1.1 Scope
1.2 Disclaimer for Trial Features
1.3 Intended Audience
1.4 Change History
2 Overview of Solution
2.1 Background
2.2 Application Scenarios
2.3 Overall Solution
3 Solution Application Guidelines
3.1 Basic HD
3.1.1 Scenario Description
3.1.2 Solution Purpose
3.1.3 Solution Description
3.1.4 Implementation
3.2 The Best Experience
3.3 The Fastest Access
3.4 The Widest Coverage
3.5 Speech Quality Assessment and Maintenance
4 List of Features Involved in the Solution
5 Acronyms and Abbreviations
6 Reference Documents
1.1 Scope
1.4 Change History
1.1 Scope
This document describes HD voice solutions for various application scenarios in UMTS networks.
It helps customers choose one or more features to better suit network deployment requirements. The technical principles, deployment, and maintenance of each feature are beyond the scope of this document. For
details, see the corresponding feature parameter description.

Trial features are features that are not yet ready for full commercial release for certain reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible. However, these features can still
be used for testing purposes or commercial network trials. Anyone who desires to use the trial features shall contact Huawei and enter into a memorandum of understanding (MoU) with Huawei prior to an official
application of such trial features. Trial features are not for sale in the current version but customers may try them for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk due to absence of commercial testing. Before using them, customers shall fully understand not only the expected benefits
of such trial features but also the possible impact they may exert on the network. In addition, customers acknowledge and undertake that since trial features are free, Huawei is not liable for any trial feature
malfunctions or any losses incurred by using the trial features. Huawei does not promise that problems with trial features will be resolved in the current version. Huawei reserves the rights to convert trial features
into commercial features in later R/C versions. If trial features are converted into commercial features in a later version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the said
commercial features. If a customer fails to purchase such a license, the trial feature(s) will be invalidated automatically when the product is upgraded.

This document is intended for personnel who:
Need to understand voice quality improvement solutions

Work with Huawei products
1.4 Change History

This section provides information about the changes in different document versions.
RAN18.1 02 (2016-06-23)
This issue includes the following changes.
Change Type Change Description
Feature change None
Editorial change Optimized the structure and descriptions.
RAN18.1 01 (2016-02-29)
This issue does not include any changes.
RAN18.1 Draft A (2015-12-30)

Compared with Issue 01 (2015-04-20) of RAN17.1, Draft A (2015-12-30) of RAN18.1 includes the following changes.
Change Type Change Description
Feature change Added the eTrFO function in the scenario of multi-rate AMR-NB services.
Added solutions to the scenario of improved voice coverage.
Added accessibility coverage solutions to the improved voice coverage scenario. For details, see the following sections:
Editorial change None
2 Overview of Solution
2.1 Background
2.1 Background
As the most basic and important service in mobile networks, voice services are undergoing constant evolution and development. In the MBB era, the UMTS network is the basic bearer network for voice services,
and user experience requirements become more demanding.
UMTS voice services consist of wideband voice services and narrowband voice services. Their frequency bands are shown in Figure 2-1.
The narrowband voice services denote AMR-NB services. The AMR-NB coder can code voices operating at a frequency band ranging from 300 Hz to 3400 Hz. After coded, the maximum data rate of
voice services can reach 12.2 kbit/s and the minimum data rate 4.75 kbit/s.
The wideband voice services denote AMR-WB services (also called HD voice services). The AMR-WB technique expands the usable frequency band from 300 Hz to 3400 Hz (supported by AMR-NB) to
50 Hz to 7000 Hz. The added low frequency band of 50-300 Hz makes voices sound more natural and comfortable to listen to while the added high frequency band of 3400-7000 Hz makes voices clearer.
Figure 2-1 Frequency bands of AMR-WB and AMR-NB services
Currently, the AMR-NB services are the default UMTS voice services while the AMR-WB services are optional voice services which require the support on both the UE and system sides. As the penetration rate of
AMR-WB-capable UEs increases, AMR-WB services become more popular as AMR-WB significantly improves voice quality and user experience.

Voice services are basic services of the UMTS network, and are AMR-NB services by default. Currently, the AMR-WB services can improve the voice quality and are widely deployed. The AMR-WB services are
applicable to the following scenarios:
Basic HD solution
Based on the AMR-NB services, this solution uses the AMR-WB services to improve the voice quality. Key technologies, such as TrFO and PLVA, are adopted to increase the MOS by 0.5 to 1 compared
with AMR-NB to deliver stellar voice experience.
The AMR-WB services are not mandatory in the UMTS network. After the AMR-WB services are widely deployed, the AMR-NB services still exist due to limited penetration rate of AMR-WB-capable
UEs.
The best experience solution
This solution uses Huawei patented technologies to improve the power control and decoding performance for uplink voice services, reduce the uplink BLER without increasing the UE uplink transmit
power, and solve the problem of signal quality fluctuation. In addition, this solution can:
Increase the MOS of voice services averagely by 0.1 to 0.2 in the entire network.
Increase the MOS of voice services by 0.5 to 1 at most in an area where the network coverage is extremely weak (the packet loss rate is greater than 5%).
Deliver stable voice services in an area where the network coverage is unbalanced.
The fastest access solution

This solution uses adaptive signaling rate to speed up the radio bearer establishment process for voice services, and processes several attach processes at the same time, thereby reducing the access delay
by 500 ms averagely and the access delay can be reduced by 1.5s at most. User experience is greatly improved.
The widest coverage solution
This solution improves the signaling demodulation and decoding performance for UEs at the cell edge through CoMP, SLVA, and other technologies. This solution improves the coverage by 2 dB and
allows users performing voice services at the cell edge to access the network and stay connected, thereby improving user experience.
Speech quality assessment and maintenance solution
By using EVQI, this solution guarantees user experience on voice services through real-time monitoring for 24 hours on voice quality over the entire network in an accurate, high-speed, and low-cost
manner.

The AMR-NB solution ensures basic UMTS voice services. If user experience needs to be further improved, it is good practice to use the basic HD solution and the following solutions:
Use the best experience solution to improve the MOS.

Use the fastest access solution to reduce the access delay.
Use the widest coverage solution to improve the signaling coverage.
Use the speech quality assessment and maintenance solution to monitor the voice quality of the entire network.
Figure 2-2 HD voice solution

click to enlarge
3.1 Basic HD
3.1 Basic HD
HD voice services refer to AMR-WB services. The AMR-WB technique expands the usable frequency band from 300-3400 Hz (supported by AMR-NB) to 50-7000 Hz. The added low frequency band of 50-300
Hz makes voices sound more natural and comfortable to listen to while the added high frequency band of 3400-7000 Hz makes voices clearer. Compared with AMR-NB, AMR-WB significantly increases the
voice quality and makes it easier to recognize the caller.

UMTS voice services consist of AMR-NB and AMR-WB services, of which the AMR-NB services are basic and the AMR-WB services are optional. After the AMR-NB services are deployed, deploying the
AMR-WB services and enabling TFO/TrFO, AMRC, and PLVA features can deliver optimal HD voice quality.
The AMR-NB services involve eight rates and 16 rate sets, of which rate set 1 or 7 is recommended. The rate set is sent by the CN to the RNC through the RAB assignment message. Therefore the rate set does not
need to be configured on the RNC.
Setting Rate Set 0 Rate Set 1 Rate Set 2 Rate Set 3 Rate Set 4 Rate Set 5 Rate Set 6 Rate Set 7 Rate Set 8 Rate Set 9 Rate Set 10 Rate Set 11 Rate Set 12 Rate Set 13 Rate Set 14 Rate Set 15
12.2 kbit/s - (1) - - - - - 1 - - - - - - 1 1
10.2 kbit/s - - - - - - 1 - - - - - 1 1 - -
7.95 kbit/s - - - - - 1 - - - - - - - - 1 1
7.40 kbit/s - 1 - - 1 - - - - - 1 1 - - - -
6.70 kbit/s - - - 1 - - - - - 1 1 1 1 1 - -
5.90 kbit/s - 1 1 - - - - - 1 1 1 1 1 1 1 1
5.15 kbit/s - - - - - - - - - - - - - - - -
4.75 kbit/s 1 1 - - - - - - 1 1 1 1 1 1 1 1
OM F F F F F F F F F F F A F A F A
NOTE:
1 indicates that a rate set contains the rate. (1) indicates that the rate is optional in a rate set. - indicates that a rate set does not contain the rate.
In the OM row, A indicates that the TFO/TrFO mechanism is allowed to automatically optimize and modify the rate set during TFO/TrFO negotiation. F indicates that the optimization and modification are not allowed. Usually, F is used.
The AMR-WB services involve nine rates, five of which are used in 3GPP protocols for UMTS voice services, and six rate sets. The recommended rate set is rate set 0 or 4. The rate set is sent by the CN to the
RNC through the RAB assignment message. Therefore the rate set does not need to be configured on the RNC.
Setting Rate Set 0 Rate Set 1 Rate Set 2 Rate Set 3 Rate Set 4 Rate Set 5
23.85 kbit/s - - - - 1 1
Setting Rate Set 0 Rate Set 1 Rate Set 2 Rate Set 3 Rate Set 4 Rate Set 5
15.85 kbit/s - - 1 1 - -
12.65 kbit/s 1 1 1 1 1 1
8.85 kbit/s 1 1 1 1 1 1
6.6 kbit/s 1 1 1 1 1 1
OM F A F A F A
NOTE:
1 indicates that a rate set contains the rate. - indicates that a rate set does not contain the rate.
In the OM row, A indicates that the TFO/TrFO mechanism is allowed to automatically optimize and modify the rate set during TFO/TrFO negotiation. F indicates that the optimization and modification are not allowed. Usually, F is used.

On live networks with AMR-NB services deployed, deploying AMR-WB services delivers HD voice experience for users and enabling the TFO/TrFO, AMRC, and PLVA features improves the MOS by 0.5 to 1.

List of Features Involved in the Solution
The following table list the features involved in the AMR-WB services.
Feature ID Feature Name Introduced in... Reference Document
WRFD-010613 AMR-WB (Adaptive Multi Rate Wide RAN6.0 AMR Feature Parameter Description
Band)
WRFD-011600 TFO/TrFO RAN3.0 AMR Feature Parameter Description
WRFD-020701 AMR/WB-AMR Speech Rates RAN2.0 AMR Feature Parameter Description

Control
WRFD-140201 AMR Voice Quality Improvement RAN14.0 AMR Voice Quality Improvement Based on PLVA Feature Parameter Description
Based on PLVA
NOTE:
The AMR-WB (Adaptive Multi Rate Wide Band) and TFO/TrFO features must be enabled. On the CN, it is good practice to disable the TFO/TrFO feature between UMTS and GSM networks, or between UMTS and LTE networks to avoid compatibility
issues.
If CN devices are provided by Huawei, it is good practice to enable only the TFO/TrFO-based rate control function for the AMR/WB-AMR Speech Rates Control feature. If CN devices are provided by other vendors, it is good practice to disable the
AMR/WB-AMR Speech Rates Control feature to avoid compatibility issues.
It is good practice to enable the AMR Voice Quality Improvement Based on PLVA feature to further improve the MOS.
For details about how to enable these features, see related feature documentation.
Description of Features Involved in the Solution

The following table describes the features involved in this solution.
Feature ID Feature Name Feature Description
WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band) This feature provides AMR-WB services.
WRFD-011600 TFO/TrFO This feature helps reduce the signal loss during speech encoding/decoding and therefore improves the MOS of
AMR-WB services.
WRFD-020701 AMR/WB-AMR Speech Rates Control This feature supports LDR-, link stability-, and TFO/TrFO-based rate control for AMR services. In this
solution, if CN devices are provided by Huawei, only the TFO/TrFO-based rate control function needs to be
enabled to meet the rate adjustment requirements of the CN. If CN devices are provided by other vendors, it is
good practice to disable this feature.
WRFD-140201 AMR Voice Quality Improvement Based on PLVA This feature helps improve the decoding performance of speech frames in the uplink and reduces the BLER for
speech frames in the uplink. There are many bit errors in speech frames in weak coverage areas and this
feature can correct these bit errors.
Rate Selection
The following two rate sets are usually configured for AMR-WB services:
Rate set 0 with the maximum rate of 12.65 kbit/s and MOS of 3.9
Rate set 4 with the maximum rate of 23.85 kbit/s and MOS of 4.1
It is recommended that rate set 4 be configured for end-to-end HD voice services.

When rate set 0 is configured for AMR-WB services, the AMR-WB services consume nearly the same network resources as the AMR-NB services, imposing little impact on the network.
When rate set 4 is configured for AMR-WB services, the AMR-WB services consume more of the following network resources than the AMR-NB services, imposing limited impact on the network:
Bandwidth: AMR-WB services (23.85 kbit/s) increase the transmission bandwidth for voice services over the Iub and Iu-CS interfaces, relatively by 65% in ATM transmission mode and by 40% in IP
transmission mode.
Code: AMR-WB services (23.85 kbit/s) consume twice as many codes as AMR-NB services (12.2 kbit/s). On a network, PS services account for a majority portion of code resource consumption, and
therefore the code consumption of AMR-WB services barely has impact on the network. Deploying AMR-WB services (23.85 kbit/s) increases the overall code consumption by about 3% to 4% in a cell
where the voice services consume 10% of the codes before the deployment and AMR-WB users account for 30% of all AMR users after the deployment.
Power: AMR-WB services (23.85 kbit/s) consume twice as many power resources as AMR-NB services (12.2 kbit/s). On a network, PS services account for a majority portion of code resource
consumption and the penetration rate of AMR-WB services is limited. Therefore, the power resource consumption of AMR-WB services barely has impact on the network. Deploying AMR-WB services
(23.85 kbit/s) increases the overall power consumption by about 6% to 7% in a cell where voice services consume 20% of the power resources before the deployment and AMR-WB users account for
30% of all AMR users after the deployment.
Coverage: Compared with that of AMR-NB services (12.2 kbit/s), the coverage of AMR-WB services (23.85 kbit/s) shrinks by 2 dB to 3 dB and can be improved using the following methods:
Increase the maximum transmit power for downlink AMR-WB services (23.85 kbit/s) by 3 dB. For details, see AMR Feature Parameter Description. Generally, only 5% to 10% UEs on the live
network are under weak network coverage. Increasing the transmit power by 3 dB for certain UEs performing AMR-WB services (23.85 kbit/s) imposes little impact on the network.
Control the speech rates in the uplink. Currently, a part of UMTS UEs support rate control. If the AMR-WB service (23.85 kbit/s) quality deteriorates, such UEs can automatically reduce the rate,
without requiring a speech rate control request from the network side. After AMR-WB services (23.85 kbit/s) are deployed, if the KPIs deteriorate because some UEs do not support rate control,
you can enable the link stability-based AMRC function in the AMR/WB-AMR Speech Rates Control feature to reduce the rate for UEs under weak network coverage. To enable this function,
contact Huawei technical support engineers. If CN devices are not provided by Huawei, this function is not recommended due to rate control compatibility issues.
Therefore, configuring rate set 4 is more likely to affect the network KPIs but brings more improvement in the voice quality. Data of sites configured with rate set 4 shows that this configuration imposes little
impact on the overall network performance because of good network coverage and low proportion of resource consumption by voice services. To guarantee KPI stability, it is good practice to configure rate set 0.
To provide the best voice quality, it is good practice to configure rate set 4. If deployment conditions permit, you can configure the AMR-WB services in phases: configure rate set 0 first and then configure rate set
4 after the KPIs are stable.
When to Use This Solution

When AMR-WB services are enabled, the TFO/TrFO feature must be enabled on both the CN and RAN to achieve end-to-end HD voice quality. Before a call is set up, the TFO/TrFO feature negotiates the
encoding/decoding codes between the calling party and called party. AMR-WB services can be set up only when both the two parties support AMR-WB services. Generally, the RAB for the calling party is set up
before the negotiation ends. If the negotiation fails, the CN will instruct the calling party to fall back to AMR-NB services and to establish the TFO/TrFO with the called party. During the calling party's fallback
process, call drops may occur. Either of the following two methods can be adopted to avoid call drops:
The calling party does not fall back to the AMR-NB services. If the encoding/decoding code negotiation for the calling party and called party fails, the CN uses encoding/decoding resources to perform
transcoding between AMR-WB and AMR-NB services. Although this method cannot bring the best voice quality and consumes extra encoding/decoding resources, it does not increase the call drop rate.
The CN performs late assignment for the calling party. That is, the CN negotiates encoding/decoding codes for the calling and called parties first and then performs assignment for the calling party. This
method may increase the voice service access delay but does not increase the call drop rate.
The preceding methods are commonly used on the live network. You can select one of them as required on networks enabled with AMR-WB. Enabling the CN to perform late assignment is recommended.
Scenario CN RAN UE Remarks
Configuring rate set 0 (maximum Configure rate set 0, enable the AMR-WB and AMR-WB (Adaptive Multi Rate – It is recommended that the CN perform late assignment for the
rate: 12.65 kbit/s) TFO/TrFO functions, and use late assignment Wide Band) calling party to avoid call drops.
for the calling party. TFO/TrFO On the CN, it is good practice to disable the TFO/TrFO feature
AMR/WB-AMR Speech Rates between UMTS and GSM networks, or between UMTS and
Control LTE networks to avoid compatibility issues.
AMR Voice Quality Improvement If CN devices are provided by Huawei, it is good practice to
Based on PLVA enable only the TFO/TrFO-based rate control function for the
AMR/WB-AMR Speech Rates Control feature. If CN devices
are provided by other vendors, it is good practice to disable
the AMR/WB-AMR Speech Rates Control feature to avoid
compatibility issues.
Configuring rate set 4 (maximum Configure rate set 4, enable the AMR-WB and AMR-WB (Adaptive Multi Rate – It is recommended that the CN perform late assignment for the
rate: 23.85 kbit/s) TFO/TrFO functions, and use late assignment Wide Band) calling party to avoid call drops.
for the calling party. TFO/TrFO On the CN, it is good practice to disable the TFO/TrFO feature
AMR/WB-AMR Speech Rates between UMTS and GSM networks, or between UMTS and
Control LTE networks to avoid compatibility issues.
AMR Voice Quality Improvement If CN devices are provided by Huawei, it is good practice to
Based on PLVA enable only the TFO/TrFO-based rate control function for the
AMR/WB-AMR Speech Rates Control feature. If CN devices
are provided by other vendors, it is good practice to disable
the AMR/WB-AMR Speech Rates Control feature to avoid
compatibility issues.
Increase the maximum transmit power for downlink AMR-
WB services (23.85 kbit/s) by 3 dB in downlink coverage
insufficient scenarios. For details, see AMR Feature
Parameter Description.
To enable the link stability-based AMRC function in the
AMR/WB-AMR Speech Rates Control feature in uplink
coverage insufficient scenarios, contact Huawei technical
support engineers.
If both CN and RAN devices are provided by Huawei, the implementation is as follows:
1. If the AMR-WB feature is enabled for both the CN and RAN, it is recommended that the CN configure rate set 4 (including data rates of 23.85 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.6 kbit/s) for all the
RNCs on the network, and that the CN perform late assignment for the calling party to avoid call drops.
NOTE:
You are advised to enable the AMR-WB feature first for the RNCs and then for the CN. Otherwise, call setup may fail. Disable the AMR-WB feature in a reverse order.
2. To support true HD voices during AMR-WB calls, enable the TFO/TrFO feature for both the CN and RAN.
NOTE:
You are advised to enable the TFO/TrFO feature first for the RNCs and then for the CN. Otherwise, call setup may fail. Disable the TFO/TrFO feature in a reverse order.
3. To obtain better voice quality, enable the AMR Voice Quality Improvement Based on PLVA feature. For the AMR/WB-AMR Speech Rates Control feature, you can enable only TFO/TrFO-based rate
control; If the uplink network coverage is weak and the UEs do not support rate control, enable also link stability-based AMRC. To enable the AMR/WB-AMR Speech Rates Control feature, contact
Huawei technical support engineers. If CN devices are not provided by Huawei, this feature is not recommended due to rate control compatibility issues.
This document does not present details about how to activate these features. For details, see corresponding feature parameter description.

This solution improves the MOS of AMR-NB or AMR-WB services.

The average block error rate (BLER) is about 1% in the UMTS network. In some weak coverage areas, the BLER may be higher than 5%, which leads to a low MOS (less than 3) and severely degrades the user
experience. This solution aims to reduce the BLER over the Uu interface for voice services by improving the performance of voice channels and eventually improve the MOS.

This solution improves power control and speech decoding performance, thereby reducing the BLER in the uplink without requiring higher UE transmit power.
The following table lists the features involved in the best experience solution.
WRFD-160204 CS Voice Precise Power Control RAN16.0 CS Voice Precise Power Control Feature Parameter Description
WRFD-170201 Seamless Crystal Voice RAN17.1 Seamless Crystal Voice Feature Parameter Description
WRFD-171201 Crystal Voice in Deep Coverage RAN17.1 Crystal Voice in Deep Coverage Feature Parameter Description
The following table describes the features involved in the best experience solution.
WRFD-160204 CS Voice Precise Power Control This feature adjusts and controls the uplink transmit power of UEs according to changes of the channel
environment and quality of received signals, thereby reducing the BLER for voice frames in the uplink.
WRFD-170201 Seamless Crystal Voice With this feature, a channel decoder is deployed on the RNC. When a CS AMR voice service experiences a
soft handover, a softer combination is performed on multiple soft handover tributaries, which improves the
voice quality in the soft handover area.
WRFD-171201 Crystal Voice in Deep Coverage This feature performs a high-order channel decoding algorithm (with the maximum decoding number reaching
64 times) to perform high-order channel decoding again on voice frames that experienced a low-order channel
decoding failure. This reduces the BLER and improves the voice quality in deep coverage scenarios.
The best experience solution does not require the support from the CN or UE. The features and functions involved in this solution are independent of each other. These features and functions have different
dependencies on the NodeB or RNC hardware. For details, see the corresponding feature parameter description document. If allowed by hardware, it is recommended that these features and functions be enabled at
the same time to improve the MOS of voice services. The following table describes requirements on solution implementation.
MOS increase is required. – The following features must be enabled: – This feature reduces the BLER of uplink voice frames
CS Voice Precise Power Control when UEs in the cell center have the same transmit
power. UE transmit power reaches the maximum at the
Seamless Crystal Voice
cell edge, which paralyzes the power control function.
Crystal Voice in Deep Coverage Therefore, the CS Voice Precise Power Control feature
cannot increase the MOS at the cell edge as expected.
The Seamless Crystal Voice feature increases the MOS in
the soft handover area. The Crystal Voice in Deep
Coverage feature increases the MOS in non-soft
handover areas.
When a UE in the UMTS network initiates a voice service, this solution reduces the end-to-end access delay. That is, the calling party hears the ring earlier.

This solution uses the following functions to reduce the AMR service access delay during service establishment: fast radio bearer (RB) setup, adaptive SRB rate, and parallel procedure processing.

This solution reduces the end-to-end access delay using functions or features unique to Huawei. It implements fast voice service establishment without sacrificing the service setup success rate.
Procedure optimization: Asynchronous reconfiguration is used during RB setups. This function shortens the RB setup duration and reduces the access delay for voice services.
Signaling bearer: After the coverage-based adaptive SRB rate adjustment function is enabled, during the access procedure, signaling rates of UEs in well-covered areas are improved when signaling is
carried over dedicated channels. With this function, signaling rates of UEs are adaptively adjusted based on the signal quality in places where UEs are located. In this way, user experience in well-covered
areas is improved without sacrificing the service setup success rate.
Parallel procedure processing: This function implements parallel processing of the Iu and Uu paging procedures, parallel processing of the Iu setup and Uu security mode procedures, and parallel
processing of the ringing and RAB setup procedures. This reduces the waiting time of each process and achieves the ultrafast access of voice services.
It is recommended that the preceding functions or features be enabled to ensure better user experience.

The following table lists the features and functions involved in this solution.
WRFD-160106 Fast Radio Bearer Setup RAN16.0 Fast Radio Bearer Setup Feature Parameter Description
N/A Coverage-based Adaptive SRB Rate Adjustment RAN16.0 Radio Bearers Feature Parameter Description
WRFD-171202 Ultrafast CS Call Setup RAN17.1 Ultrafast CS Call Setup Feature Parameter Description
The following table describes the features and functions involved in the solution for scenarios of the fastest access.
WRFD-160106 Fast Radio Bearer Setup With this feature, asynchronous reconfiguration is used during RB setups. This shortens the RB setup duration
and reduces the access delay for voice services.
N/A Coverage-based Adaptive SRB Rate Adjustment With this function, signaling rates of UEs are adaptively adjusted based on the signal quality in places where
UEs are located. In this way, user experience in well-covered areas is improved without sacrificing the service
setup success rate.
WRFD-171202 Ultrafast CS Call Setup This feature optimizes the AMR voice service access procedure. That is, it changes serial processing to
parallel processing, which reduces the waiting time of each process and accelerates the access especially for a
call involving two UMTS UEs.
The features and functions involved in this solution are independent of each other. It is recommended that all these features and functions be enabled at the same time to reduce the access delay for voice services.
The WRFD-160106 Fast Radio Bearer Setup feature requires support from UEs. If some UEs do not support this feature, add these UEs to the blacklist. For details about this feature, see Fast Radio Bearer Setup
Feature Parameter Description. Before enabling the WRFD-171202 Ultrafast CS Call Setup feature, you are advised to enable the TFO/TrFO function for intra-UMTS calls on the CN side and enable the WRFD-
011600 TFO/TrFO feature on the RNC side to ensure the gains provided by parallel processing of paging procedures. The following table describes requirements on solution implementation.
To accelerate the access for UMTS users acting Enable the TFO/TrFO The following features must be enabled: – For a call involving two UMTS users, the gains provided by
as the calling or called party (the called party is feature. the Ultrafast CS Call Setup feature include those provided by
TFO/TrFO
a UMTS user) the Fast Radio Bearer Setup feature. In this case, it is
Coverage-based Adaptive SRB Rate Adjustment recommended that the Fast Radio Bearer Setup feature be
Ultrafast CS Call Setup disabled.
To accelerate the access for UMTS users acting – The following features must be enabled: No requirements (add UEs It is recommended that all these features or functions be
as the calling party (the called party is a user with compatibility issues to enabled.
Fast Radio Bearer Setup
belonging to another operator) the blacklist)
Coverage-based Adaptive SRB Rate Adjustment
Ultrafast CS Call Setup
To accelerate the access for UMTS users acting – The following features must be enabled: – For a call initiated by a user belonging to another operator to
as the called party (the calling party is a user a UMTS user, the gains provided by the Ultrafast CS Call
Coverage-based Adaptive SRB Rate Adjustment
belonging to another operator) Setup feature include those provided by the Fast Radio Bearer
Ultrafast CS Call Setup Setup feature. In this case, it is recommended that the Fast
Radio Bearer Setup feature be disabled.
The following is an example of solution implementation.
1. It is recommended that the TFO/TrFO function be enabled for intra-UMTS calls on both the CN and RNC sides.
NOTE:
If this function is not enabled, the gains provided by parallel processing of paging procedures cannot be ensured and the optimal access performance cannot be fulfilled.
2. Enable the feature and function involved in the fast voice service setup solution one by one.
The features and functions involved in this solution are independent of each other and can be enabled at the same time. This document does not present details about how to activate these features. For
details, see corresponding feature parameter description.
3. If some UEs do not support the Fast Radio Bearer Setup feature, add these UEs to the blacklist.

Voice service coverage is measured by accessibility, service integrity, and retainability. Accessibility indicates the coverage that can provide voice services. Integrity indicates the coverage where the voice service
quality can be ensured. Retainability indicates the coverage where the voice services are not interrupted.
click to enlarge

The uplink coverage of UMTS voice services is limited. The best experience solution improves the uplink TRB performance, therefore increasing the coverage for voice service integrity. This solution improves
the uplink SRB and RACH performance through CoMP and SLVA technologies and increases the coverage for voice service accessibility and retainability.

In scenarios where the uplink coverage is limited, this solution processes SRBs carried over DCH in the uplink and the RNC re-processes and re-decodes the data that is incorrectly decoded by a NodeB. In this
way, the demodulation and decoding performance of SRB over DCH in the uplink is improved, the BLER of the SRB is reduced, and the cell coverage capability for voice service retainability is improved. This
solution reduces the PRACH preamble capture capability, introduces high-order decoding to improve the decoding performance of PRACH messages, implements the functions of the uplink RACH, and improves
the cell coverage capability for voice service accessibility.


WRFD-180201 Improved Uplink Coverage for SRB over DCH RAN18.1 Improved Uplink Coverage for SRB over DCH Feature Parameter Description
WRFD-181201 Uplink Coverage Improvement During Access RAN18.1 Uplink Coverage Improvement During Access Feature Parameter Description

The following table describes the features and functions involved in this solution.
WRFD-180201 Improved Uplink Coverage for SRB over DCH This feature improves the performance of SRBs in the uplink, thereby expanding the voice service
retainability coverage.
WRFD-181201 Uplink Coverage Improvement During Access This feature improves the performance of RACH in the uplink, thereby expanding the voice service
accessibility coverage.
The widest coverage solution aims to improve uplink SRB and RACH performance, and the best experience solution aims to improve the uplink TRB performance. The two functions are independent of each
other. To ensure the improvement of voice service accessibility, retainability, and integrity at the same time, it is good practice to enable these two functions.
Improved uplink coverage for voice N/A It is good practice to enable both functions. N/A The Improved Uplink Coverage for SRB over DCH
services Improved Uplink Coverage for SRB over feature aims to improve the uplink SRB performance and
DCH the Uplink Coverage Improvement During Access
feature aims to improve the uplink RACH performance.
Uplink Coverage Improvement During
Access It is good practice to enable the best experience solution
to improve uplink TRB performance.

A mechanism is required to assess, test, and maintain the speech quality of voice services in UMTS networks.

This solution assesses, tests, and maintains speech quality. In addition, it also determines whether garbled voices occur and locates these voices if they occur.

This solution uses the EVQI to assess the speech quality of voice services. It also uses the Garbled Noise Detection and Correction of AMR Voice feature to detect and correct garbled voices caused by inconsistent
settings for encryption parameters.
WRFD-160102 Garbled Noise Detection and Correction of RAN16.0 Garbled Voice Detection and Correction for AMR Services Feature Parameter
AMR Voice Description
N/A EVQI RAN16.0 AMR Feature Parameter Description

The following table describes the features and functions involved in this solution.
WRFD-160102 Garbled Noise Detection and Correction of AMR Voice For AMR-WB and AMR-NB services, inconsistent settings for encryption parameters cause garbled
voices, greatly affecting user experience. With this feature, the RNC can detect and correct garbled
voices in the uplink or downlink.
N/A EVQI The MOS is used to evaluate the voice quality on the entire network. The EVQI is used to evaluate voice
quality over the air interface and suitable for routine voice quality monitoring.
The features and functions involved in this solution are independent of each other. It is recommended that these features and functions be enabled at the same time. The following table describes requirements on
solution implementation.
Scenarios CN RAN UE Remarks
To evaluate the MOS of voice quality – Enable the EVQI function. – Downlink BLER is required for downlink EVQI
on the entire network (for the air evaluation. Therefore, the UE must send the
interface only) measurement report.
Garbled Noise Detection and – Garbled Noise Detection and Correction of AMR – None
Correction of AMR Voice Voice
Deployment and activation of each feature will not be described in this document and will be included in the corresponding feature parameter description.
WRFD-010613 AMR-WB (Adaptive Multi Rate Wide Band) RAN6.0 AMR Feature Parameter Description
WRFD-011600 TFO/TrFO RAN3.0 AMR Feature Parameter Description
WRFD-020701 AMR/WB-AMR Speech Rates Control RAN2.0 AMR Feature Parameter Description
WRFD-140201 AMR Voice Quality Improvement Based on PLVA RAN14.0 AMR Voice Quality Improvement Based on PLVA Feature Parameter Description
N/A Coverage-based Adaptive SRB Rate Adjustment RAN16.0 Radio Bearers Feature Parameter Description
WRFD-160102 Garbled Noise Detection and Correction of AMR Voice RAN16.0 Garbled Voice Detection and Correction for AMR Services Feature Parameter Description
WRFD-171202 Ultrafast CS Call Setup RAN17.1 Ultrafast CS Call Setup Feature Parameter Description
WRFD-181201 Uplink Coverage Improvement During Access RAN18.1 Uplink Coverage Improvement During Access Feature Parameter Description
WRFD-180201 Improved Uplink Coverage for SRB over DCH RAN18.1 Improved Uplink Coverage for SRB over DCH Feature Parameter Description
Acronym and Abbreviation Full Name
HD High Definition
AMR-WB Adaptive Multirate Wide Band
AMR-NB Adaptive Multirate Narrow Band
MOS Mean Opinion Score
PLVA Parallel List Viterbi Algorithm
CN Core Network
TFO/TrFO Tandem Free Operation/Transcoder Free Operation
AMRC AMR Rate Control
LDR Load Reshuffling
BLER Block Error Rate
RSCP Received Signal Code Power
UE User Equipment
UMTS Universal Mobile Telecommunications System
1. AMR Feature Parameter Description

2. AMR Voice Quality Improvement Based on PLVA Feature Parameter Description
3. CS Voice Precise Power Control Feature Parameter Description
4. Fast Radio Bearer Setup Feature Parameter Description
5. Procedure Optimization Feature Parameter Description
6. Radio Bearers Feature Parameter Description
7. Garbled Voice Detection and Correction for AMR Services Feature Parameter Description
8. Seamless Crystal Voice Feature Parameter Description
9. Crystal Voice in Deep Coverage Feature Parameter Description
10. Ultrafast CS Call Setup Feature Parameter Description
11. Uplink Coverage Improvement During Access Feature Parameter Description
12. Improved Uplink Coverage for SRB over DCH Feature Parameter Description
1.2 Experience Management

UMTS HD Video Solution
UMTS Service Experience-based Network Construction Solution
UMTS User Experience Management Solution
WCDMA RAN
UMTS HD Video Solution Guide
Issue 01
Date 2016-08-30

Notice

1.2.1 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
2.1.1 Growing Demand for Mobile Video
2.1.2 Surge in Mobile Video Service Driven by LTE
2.1.3 UMTS Network Capable of HD Videos
2.2 Solution Benefits
2.3 Mobile Video Experience Assessment and Influencing Factors
2.3.1 Assessment Solution
2.3.2 Factors
2.4 Solution Purpose
2.4.1 Providing Operators with Optimal Video Experience Evaluation Solutions
2.4.2 Providing Terminal Users with High-Quality HD Video Experience
3.1 Solution Application Overview
3.2 Software Feature Solution
3.2.1 Overview
3.2.2 Scenario 1: Basic Video Experience
3.2.3 Scenario 2: Video Delay Decrease
3.2.4 Scenario 3: Video Experience Improvement in Heavy Load Scenarios
3.2.5 Scenario 4: Video Experience Improvement at the Cell Edge
3.3 Video Coverage Solution
3.3.1 Overview
3.3.2 Video Experience Assessment and Goal Setting
3.3.2.1 Video Experience Assessment
3.3.2.2 Goal Setting
3.3.2.3 Defining Areas with and Causes of Poor Video Experience
3.3.3 Network Planning
3.3.4 Network Implementation
3.3.5 Verification
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the UMTS high definition (HD) video solution, including its technical principles and application guidelines.
The technical principles, deployment, and maintenance of each feature are beyond the scope of this document. For details, see the corresponding feature parameter description.

Need to understand the UMTS HD video solution

1.3 Change History

RAN18.1 01 (2016-08-30)
This document is created for RAN18.1.
2 Solution Overview
2.1 Background
2.1 Background
2.1.1 Growing Demand for Mobile Video
Graphics-based information delivery has regularly served as a primary method of communication. Given rapid mobile broadband (MBB) development, mobile video is pressing ahead as an essential mobile
service, second only to voice services.
With huge expectations for HD video experience and growing popularity of high-performance UEs, video services with a definition of 720p and beyond (720p+) are proving a popular form of data traffic
consumption.
The consumption capacity of mobile video services is growing rapidly:
Increased usage of mobile video services
NOTE:
The following data is obtained from Youku, a popular Internet video platform in China.
From 2013 to 2015, mobile video service traffic grew by 70% annually, in large contrast to fixed networks with an annual growth rate of 27%.
Mobile video APPs are among the top 5 mobile APPs, with a usage of 49.3%.
The ratio of video traffic on UEs (nearly 70% in 2014) has overtaken that on PCs.
Higher UE resolution
Figure 2-1 shows the development of smart UEs from 2012 to 2015. As the red line indicates, UEs with a 720p+ resolution have witnessed a noticeable increase in popularity. This reflects that such UEs
have become mainstream and are able to cater to the growing demands of HD mobile video services.
Figure 2-1 Ratio of UEs supporting 720p+ resolution
click to enlarge
Data source: Huawei mLAB Terminals Info Center Samples from top 18 vendors
Higher video source resolution
Figure 2-2 shows the rapid growth of 720p+ HD video sources on YouTube from 2012 to 2015. This rapid growth effectively demonstrates the popularity of mobile HD video services.
Figure 2-2 YouTube 720p+ video source ratio
Table 2-1 lists the video resolution and bitrate.

Table 2-1 Video resolution and bitrate
Definition Resolution Average Bitrate (H.264) Average Bitrate (H.265)
Low definition (LD) 240p: 427 x 240 250 kbit/s N/A
360p: 640 x 360 450 kbit/s N/A

Definition Resolution Average Bitrate (H.264) Average Bitrate (H.265)
Standard definition (SD) 480p: 854 x 480 700 kbit/s N/A
HD 720p: 1280 x 720 1.5 Mbit/s 0.9 Mbit/s
1080p: 1920 x 1080 3 Mbit/s 1.5 Mbit/s
NOTE:
H.264 and H.265 are video coding standards developed by organizations such as the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T). H.265 enables a higher coding efficiency and lower air interface
data rate for the same resolution video. H.264 still dominates and some recently-launched UEs already support H.265.
Increased ratio of HD video traffic

HD video accounts for more than 10% of the total video traffic in UMTS networks.
Figure 2-3 shows the distribution of video resolution for Operator A in October 2015. In the pie chart, the ratio of 720p+ HD video traffic has exceeded 10%.
Figure 2-3 Ratio of HD video traffic for Operator A
Figure 2-4 shows the total video traffic percentage for Operator T in November 2015. In the bar chart, the ratio of 720p+ HD video traffic is close to 15%.
Figure 2-4 Percentage of HD video traffic for Operator T
2.1.2 Surge in Mobile Video Service Driven by LTE

Since 2012, LTE has been deployed on a global scale. By virtue of this context and fair tariff policies, subscribers tend to desire UE-based video services in mobile environments. This consumption habit drives
mobile video service to prosper.
UMTS as the foundation of MBB is also seeing a surge in video traffic.
Figure 2-5 and Figure 2-6 respectively show the growth of video traffic in UMTS and UMTS and LTE traffic ratios for an operator. The operator has deployed more LTE sites than UMTS sites.
Figure 2-5 Growth of total video traffic in UMTS
Figure 2-6 UMTS and LTE traffic ratios
2.1.3 UMTS Network Capable of HD Videos

UMTS as MBB Foundation Network
UMTS currently serves up to 80% of the global population and is expected to have a wide coverage margin of 25% over LTE by 2020. Favorable coverage allows UMTS to maintain service connectivity for MBB
subscribers.
Figure 2-7 illustrates the UMTS coverage distribution.
Figure 2-7 UMTS coverage distribution
In a global context, UMTS networks will still see a soaring subscriber population before 2020 and may outpace GSM networks by 2017 to become the most-populated mobile networks. Figure 2-8 illustrates the
trend of UMTS subscriber growth.
Figure 2-8 UMTS subscriber growth
UMTS Bandwidth Up to HD Videos

720p (H.264), for example, generally enables a bitrate of about 1.5 Mbit/s. According to studies from Huawei mLAB, interruption-free video play is possible if the air interface data rate is 1.3 times the video
bitrate. Consequently, a smooth 720p video experience is out of question at a network data rate of 2 Mbit/s (approximately 1.5 Mbit/s multiplied by 1.3).
Through years of development, UMTS has evolved to higher air interface throughput with the use of solutions such as HSPA+, multiple sectors, and UMTS 900/850 MHz low-frequency spectrum. These
developments make a smooth HD (such as 720P) video experience possible.
Figure 2-9 shows a cumulative distribution function (CDF) curve of downlink throughput through drive tests (DTs) of Operator A. In the figure, the downlink throughput can reach 2 Mbit/s or higher in 90% of
tested areas.
Figure 2-9 CDF curve of single-user downlink throughput of Operator A
click to enlarge
After Operator B has deployed DC-HSDPA, the grid-level analysis of air interface throughput indicates that the throughput can reach 2 Mbit/s or higher in more than 75% of tested areas. Figure 2-10 shows the
grid-level analysis. Figure 2-11 shows the throughput ratio analysis.
Figure 2-10 Grid-level analysis
Figure 2-11 Throughput ratio analysis

Embracing the inevitable rapid development of mobile video services, UMTS-enabled HD videos can encourage the consumption of more data traffic while improving user experience. Accordingly, the network-
wide traffic volume also increases.
Video services can directly boost operators' traffic volume. Several global sites show that the ratio of HD video increases with the growing video traffic volume. This necessitates a higher total traffic volume.
The following analyzes data traffic growth on a site as a result of the provisioning of HD video.
NOTE:
The following data is obtained from Huawei network consultation.
Figure 2-12 shows that the video traffic volume on the site increased from 10.8% to 37.7%.
Figure 2-12 Video traffic ratio
click to enlarge
Over the same period, data traffic throughout the UMTS network on this site increased by 23%, as shown in Figure 2-13.
Figure 2-13 UMTS data traffic growth
click to enlarge

2.3.1 Assessment Solution
Mobile video services include initial buffering and video play. Service KPIs can be used to conduct quantitative assessment on user experience in these two phases. Service KPIs are Huawei-developed lightweight
assessment indicators for user experience based on service awareness, and can provide assessment results on user experience. Such indicators include:
Video start success rate

Video start delay
Video play stalling ratio
Video stalling time ratio
Video download throughput
Based on service KPIs, video experience can be assessed using video mean opinion score (VMOS). Similar to the MOS used for voice service assessment, the VMOS uses a MOS ranging from 1 (worst network
quality) to 5 (best network quality) to rate the subjective quality of video services and provides an overall assessment on video experience.
The VMOS is calculated based on video quality, video start delay, and video stalling time ratio. Under the same video bitrate, the shorter the video start delay, the lower the video stalling time ratio, the higher the
VMOS, and the better the video experience.
The following sections describe service KPIs and VMOS definitions in detail.
Service KPIs
Service KPIs are used to assess various services, such as web pages, videos, file uploading, and specific APPs (such as YouTube, Facebook, WeChat, and Sina Weibo). Assessment statistics are presented using
WINS Space. Table 2-2 shows service KPIs and related user experience descriptions.
Table 2-2 Service KPIs and user experience descriptions
Video Play Phase User Experience Description Service KPI
Video start (accessibility) Does the video start normally? Video start success rate
How long does it take for the video to start playing? Video start delay
Video play (integrity) Does the video stall during play? Video play stalling ratio
How long does it stall for? Video stalling time ratio
N/A Video download throughput
The RNC parses key events reported during video data transmission to obtain the service KPIs. Figure 2-14 shows the signaling process of video play that involves service KPIs.
1. A video service starts when the RNC receives the first video data packet (point A or A' in the figure) from a UE.
2. When the size of the downloaded data reaches the threshold for video play, initial video buffering is complete, and video play begins (point C).
3. The video download procedure completes when the RNC receives a TCP Ack message for the last HTTP data packet (point D) from the UE.
4. When the TCP connection established for the video service is released at point E, the video service process is complete.
The phase from point A to point C is the initial video buffering phase. From point C to point E is the video play phase. If the data rate provided by the network falls below that required by the video service, the UE
clears its buffer and re-buffers data. In this case, video play stops and will not resume until the required amount of data is received.
Figure 2-14 Signaling process of video play
Video start delay and video stalling time ratio are two main service KPIs. Table 2-3 shows the definitions of the two indicators. Figure 2-15 shows the duration involving the two indicators.
Table 2-3 Definitions of video start delay and video stalling time ratio
Service KPI Name Definition Description
Video start delay Indicates the total time between when a user initiates a video request Initial buffering begins after the server responds to the video request. When the UE
and when the video begins to play. receives a certain amount of data, video play begins. Users can directly sense the video
start delay.
Video stalling time ratio Indicates the ratio of the video stalling duration to the video play During video play, if the buffer data of the player is cleared because of network rate
duration. fluctuation, the UE will re-buffer data. After a certain amount of data is received, video
play will resume. As a result, users experience video pauses. The higher the video stalling
time ratio, the larger the ratio of the video stalling duration to the video play duration, and
the worse the user experience.
Figure 2-15 Definitions of video start delay and video stalling time ratio
click to enlarge
VMOS
The VMOS depends on multiple subjective and objective factors. For the sake of evaluating video experience, three core factors are extracted to calculate mobile VMOS: sQuality (video quality, or video bitrate),
sLoading (video start delay), and sStalling (video stalling time ratio). sLoading and sStalling represent impact of network quality on user experience. Under a defined sQuality, the higher sLoading and sStalling,
the better the video experience, and the higher the VMOS. Currently, mobile VMOS is undergoing standardization by ITU-T. It can be calculated using the following formula:
click to enlarge
In which:
sQuality depends on the video source. The higher the resolution, the higher the sQuality.
sLoading is inversely proportional to the video start delay. The shorter the video start delay, the higher the sLoading.
sStalling is inversely proportional to the video stalling time ratio. The smaller the video stalling time ratio the higher the sStalling.
Refer to Table 2-4 and Table 2-5 for the relationship between the indicator and VMOS.
Table 2-4 Video quality score
sQuality VMOS
5K and above 5
4K 4.9
2K 4.8
1080P 4.5
720P 4
480P 3.6
360P 2.8
Table 2-5 Relationship between the video start delay, video stalling time ratio, and VMOS
sLoading sStalling VMOS
100 ms 0% 5
1s 5% 4
3s 10% 3
5s 15% 2
10s 30% 1
2.3.2 Factors
Key factors affecting the video start delay include video bitrate, E2E RTT, and air interface throughput. The air interface throughput is also the key factor affecting the video stalling time ratio. Because the video
bitrate depends on the video source, key factors affecting the mobile video experience include E2E RTT and air interface throughput.
E2E RTT delay

Under similar conditions, the shorter the E2E RTT delay in the UMTS network, the shorter the video start delay, and the better the video experience. Figure 2-16 shows the comparison results in lab tests
where 1080p videos are initiated, the bitrate is around 2.9 Mbit/s, and the air interface rate is 3 Mbit/s to 4 Mbit/s.
Figure 2-16 Relationship between RTT and video start delay
click to enlarge
As shown in the figure above, to reduce video start delay, operators need to reduce the E2E RTT delay. Factors affecting E2E RTT delay include:
Air interface specifications, such as TTI length. The shorter the TTI, the shorter the RTT.
Air interface performance, such as radio throughput, coverage, and load level. In areas with high radio throughput, good coverage, and low load, the RTT is short.
System processing delay, such as Iub delay, equipment delay, and forward delay. The shorter the system processing delay, the shorter the RTT.
Other system processing delay, such as delay caused by transmission network, distance between video server and RAN, and video server performance.
Air interface throughput

Under similar conditions, the higher the radio throughput in the UMTS network, the shorter the video start delay, the lower the video stalling time ratio, and the better video experience. Using the video
stalling time ratio as an example, Figure 2-17 shows the test comparison results at a site (test conditions: 720p video, bitrate around 1.5 Mbit/s). If the perceived rate is 1.3 times of the video bitrate, only
less than 20% of samples show video stall.
Figure 2-17 Relationship between the air interface throughput and video stalling time ratio
click to enlarge
Factors affecting radio throughput include:
Air interface capability: Whether HSPA+ features such as DC-HSDPA and 64QAM are supported. If such features are supported, the radio throughput is improved.
RAN network performance: Such as interference level, coverage, and load status. In areas with strong interference and weak coverage (at cell edge for instance) during traffic peak hours, the
high rate is not available.
Other system performance: Such the packet loss rate at layers above the RAN that affects inbound traffic, the distance between the video server and the RAN, and the video server performance.

2.4.1 Providing Operators with Optimal Video Experience Evaluation Solutions
Traditional network KPIs cannot reflect actual user experience. Operators often resort to DTs and customer surveys to obtain customers' feedback on video experience. However, such high-cost methods provide
only a small amount of data and lack real-time and comparative values. Operators need a more effective and complete user experience evaluation system to accommodate the fast development of video services.
Huawei's UMTS HD Video Solution provides user experience evaluation solutions such as service KPIs and VMOS, helping operators understand video experience of users and guiding their network construction
and solution deployment toward providing optimal video experience.
2.4.2 Providing Terminal Users with High-Quality HD Video Experience

Providing UMTS Users with LTE-standard HD Video Experience
The LTE network boasts higher throughput and shorter delay. The LTE network deployment has facilitated the fast development of mobile video services. However, the deployment scale of the LTE network is and
will remain considerably smaller than that of the UMTS network for a long period. The UMTS provides MBB network infrastructure. LTE users using video services fall back to UMTS network in multiple
scenarios. A large gap between the UMTS and LTE video experience will hamper user satisfaction. Therefore, the UMTS network needs to provide mobile video experience consistent with that provided by the
LTE network.
Mobile video streaming is a human-machine interactive service. User expectations on video experience relate to the response capabilities of the machine, namely speed and stability. For example, if a user gets a
quick response from the request for video play (speed), and video play is not interrupted (stability), the user is satisfied.
The speed and stability are measured as video start delay and video stalling time ratio in service KPIs. The former means after a user clicks play, the video selected responds to the request in a timely manner and
begins playing. The latter means the video plays without stalling.
Based on standard reaction time, good video experience is obtained when both of the following conditions are met:
The video start delay is within 2.5s.

The video stalling time ratio is close to 0.
If such conditions are met when a UE falls back from LTE to UMTS, the user will not experience a noticeable difference in video play. Such consistent HD video experience will improve customer satisfaction.
Providing UMTS Users with Extensive High-Quality HD Video Experience

In addition to video experience consistent with that provided by the LTE network, the UMTS network also ensures that users have optimal experience anytime, anywhere (for instance, in heavy load periods and
cell-edge areas).
In heavy load periods and cell-edge areas, the UMTS network shows poor throughput and delay performance due to factors such as congestion, interference, and weak coverage. Users cannot obtain high-quality
video experience. In such periods and areas, user experience is the poorest. With related software features and video coverage methods, the UMTS HD Video solution can overcome the aforementioned difficulties,
providing ubiquitous HD video experience to users.

By deploying software features and network planning, the UMTS HD Video solution can provide users with ubiquitous HD video experience consistent with that provided by the LTE network. Supported in
RAN18.1 and later versions, this solution includes two sub-solutions:
Software Feature Solution
With the current network conditions, deploying the software feature solution can rapidly reduce E2E RTT delay and increase radio throughput, improving video experience for users on the entire network.
In light-to-medium-load cells and areas near cell centers, the HD video experience is consistent with that provided by the LTE network.
Video Coverage Solution (video experience-based network planning)

By locating and eliminating root causes for deteriorating video experience, the Video Coverage Solution provides accurate network plans to guide network construction, and ubiquitous optimal HD video
experience.
The two sub-solutions can be implemented simultaneously or independently based on network conditions.

3.2.1 Overview
The software feature solution is characterized by lightweight implementation, fast deployment, and fast returns. The effect provided by this solution can be observed within one to two weeks after deployment. The
solution includes a variety of feature combinations used for the following application scenarios.
Basic video experience

The air interface throughput is a basic factor in delivering high-quality video experience. It significantly affects the video start delay and video stalling time ratio. Related features help improve air
interface throughput as well as video experience.
Video delay decrease
The E2E RTT delay significantly affects the video start delay. Related features help shorten the E2E RTT delay and therefore decrease the video start delay.
Video experience improvement in heavy load scenarios
The heavy load scenario always happens at hotspots in densely populated areas. It features high user density, multiple online users, easy network congestion, and possible traffic suppression (traffic storm
control). Heavy load significantly compromises video experience. Regardless of the small ratio (5% to 10%) of heavily-loaded cells in a network, these cells still serve a large number of users, which calls
for improvement of the overall user experience.
Video experience improvement at the cell edge
At the cell edge, user throughput or experience ranks in the bottom 5%-10%. From the coverage aspect, edge areas are usually those at the cell edge, for example, soft handover areas.
The poor video experience of CEUs will lead to the following issues:
Unreliable network quality caused by large differences in user experience between CEUs and CCUs
Poor user experience of users who shift to UMTS networks from LTE networks
The UMTS network is the MBB basic network and needs to accommodate video users who shift from LTE networks through a fallback. Therefore, the experience of such users will be greatly
affected if the edge of UMTS network coverage is weak.
Figure 3-1 illustrates the architecture of the software feature solution used for different application scenarios.
Figure 3-1 Architecture of the software feature solution used for different application scenarios.
click to enlarge
3.2.2 Scenario 1: Basic Video Experience

Scenario Description
The air interface throughput is a basic factor in delivering high-quality video experience. It significantly affects the video start delay and video stalling time ratio. Higher requirements for the video resolution
indicate greater required air interface throughput. In this scenario, video services are running but related features are not deployed yet. Related features can be deployed to improve air interface throughput. The
active features do not need to be deployed again.
Solution Purpose
This solution improves the air interface throughput, thereby improving video experience.
With this solution, the features listed in the following table can be deployed to improve air interface throughput in target areas.
Table 3-1 Description and application of features involved in the solution
Feature ID Feature Name Feature Description Introduced in... Reference Document
WRFD-010629 DL 16QAM Modulation Meets the HSDPA basic modulation requirement. RAN5.0 HSDPA Feature Parameter Description
WRFD-010696 DC-HSDPA Enables the use of two carriers in the same frequency band to RAN12.0 Multi-Carrier HSDPA Feature Parameter
transmit data of a user, improving the average user data rate. Description
WRFD-010683 Downlink 64QAM Increases peak throughput by applying a high-order RAN11.0 Downlink 64QAM Feature Parameter
modulation scheme to users at the cell center. Description
WRFD-010612 HSUPA Introduction Package Supports HSUPA 10 ms TTI. RAN6.0 HSUPA Feature Parameter Description
WRFD-010685 Downlink Enhanced L2 All HSPA+ techniques depend on Downlink Enhanced L2. RAN11.0 Enhanced L2 Feature Parameter
Description
WRFD-150230 DPCH Pilot Power Adjustment Decreases non-HSPA power by decreasing the DPCH pilot RAN15.0 Power Control Feature Parameter
power in heavy load scenarios, thereby increasing available Description
HSDPA power and HSDPA throughput.
WRFD-150235 DPCH Maximum Power Restriction Decreases non-HSPA power by decreasing the maximum RAN15.0 Power Control Feature Parameter
DPCH power, thereby increasing available HSDPA power and Description
HSDPA throughput.
WRFD-150236 Load Based Dynamic Adjustment of PCPICH Decreases HSDPA pilot power in heavily loaded cells to RAN15.0 Load Based Dynamic Adjustment of
increase available HSDPA power and HSDPA throughput. PCPICH Feature Parameter Description
WRFD-160251 HSDPA Inter-Cell Power Sharing Enables one HSDPA cell to dynamically share the idle power RAN16.0 Power Sharing Feature Parameter
resources of another HSDPA cell quickly, thereby improving Description
the throughput of HSDPA users' burst services.
WRFD-171204 DPCH Power Control Based on Radio Quality Restricts the UE's power requirements on the associated RAN17.1 Power Control Feature Parameter
DPCH based on the UE signal quality, improving HSDPA Description
throughput.
WRFD-181207 DPCH TPC Power Adjustment Decreases TPC transmit power and downlink non-HSPA RAN18.1 Power Control Feature Parameter
power based on downlink non-HSDPA power, thereby Description
increasing cell downlink capacity.
WRFD-150208 Flexible Dual Carrier HSDPA Enables the RNC to flexibly select two carriers for data RAN15.0 Multi-Carrier HSDPA Feature Parameter
transmission. It improves the burst service rates of HSDPA Description
users.
WRFD-150209 DB-HSDPA Enables the use of two carriers in different frequency bands to RAN15.0 Multi-Carrier HSDPA Feature Parameter
transmit data to a user, improving the user data rate. Description
NOTE:
The Flexible Dual Carrier HSDPA feature applies to networks with three or more carriers.
The DB-HSDPA feature applies to networks with a high penetration rate of DB-HSDPA capable UEs.
Implementation
It is recommended that the features involved be deployed in target areas to reduce the video start delay and video stalling time ratio. These features can be simultaneously enabled. For details about feature
deployment, see related feature parameter descriptions.
3.2.3 Scenario 2: Video Delay Decrease

A long E2E RTT delay will result in a long video start delay and a low VMOS. In this scenario, E2E RTT decrease and other technologies can be used to reduce the video start delay. This solution significantly
improves user experience in lightly-loaded cells and areas in the middle and center of cells.
NOTE:
For a lightly-loaded cell, its non-HSPA power load is not greater than 20%, the value of VS.CellDCHUEs(BSC6900,BSC6910) is not greater than 20, and the value of VS.MeanULActualPowerLoad(BSC6900,BSC6910) is not greater than
30%.
Non-HSPA power load = VS.MeanTCP.NonHS(BSC6900,BSC6910) (W)/CellMaxPower (W) x 100%
CellMaxPower indicates the maximum transmit power of a cell and is specified by the MAXTXPOWER(BSC6900,BSC6910) parameter in the RNC MML command ADD UCELLSETUP.
For areas in the middle and center of cells, the CQI is not less than 18.
Solution Purpose
For areas where this solution is deployed:
Service KPI statistic results show that both the video start delay and the video stalling time ratio decrease by 10%-20%.
DT results in lightly loaded cells and areas in the middle and center of cells show that, for 720p/1080p videos, the video start delay decreases to 2s-2.5s, the video stalling time ratio is less than 2%, and
the VMOS is not less than 3.2.
NOTE:
The DT tool SpeedVideo is used. The SpeedVideo tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.
With this solution, the features listed in the following table can be deployed to improve air interface throughput in target areas.
N/A Always UL HSPA+ Solution Improves HSUPA 2 ms TTI coverage and shortens the E2E RAN17.1 Features listed in Table 3-3
RTT. In the uplink, transmission of the TCP ACK message is
accelerated and video data can reach UEs at a faster speed. In
this way, the video start delay is shortened.
WRFD-170202 TCP Proxy Is deployed on the RNC to shorten the RTT and increase the RAN17.1 TCP Proxy Feature Parameter Description
TCP data transmission rate by using the TCP slow start
acceleration function and the optimized TCP congestion control
algorithm.
WRFD-180106 User Experience Improvement for Lightly Loaded Allocates more resources (including the power, code, and RAN18.1 User Experience Improvement for Lightly
Cells uplink load resources) in lightly loaded cells to achieve Loaded Cells Feature Parameter
enhanced user experience, thereby decreasing the video start Description
delay and video play stalling ratio.
Table 3-3 Description and application of features involved in the Always UL HSPA+ solution
Category Feature ID Feature Name Introduced in... Reference Document
Uplink power efficiency WRFD-010210 Control Channel Parallel Interference Cancellation RAN10.0 Control Channel Interference Cancellation Feature
improvement (CCPIC) Parameter Description
WRFD-140202 Control Channel Parallel Interference Cancellation RAN14.0 Control Channel Interference Cancellation Feature
(Phase 2) Parameter Description
WRFD-160201 Control Channel Parallel Interference Cancellation RAN16.0 Control Channel Interference Cancellation Feature
(Phase 3) Parameter Description
WRFD-010691 HSUPA UL Interference Cancellation RAN12.0 Interference Cancellation Feature Parameter

Description
WRFD-150206 Turbo IC RAN15.0 Interference Cancellation Feature Parameter

Description
WRFD-160213 Turbo IC Phase 2 RAN16.0 Interference Cancellation Feature Parameter

Description
WRFD-010712 Adaptive Configuration of Traffic Channel Power RAN13.0 Power Control Feature Parameter Description
offset for HSUPA
WRFD-160202 Flexible Power Control for Uplink Low Data Rate RAN16.0 Power Control Feature Parameter Description
Transmission
WRFD-171203 Uplink Control Channel OLPC RAN17.1 Uplink Control Channel OLPC Feature Parameter
Description
WRFD-171207 Virtual CPC RAN17.1 Virtual CPC Feature Parameter Description
Coverage improvement WRFD-020138 HSUPA Coverage Enhancement at UE Power RAN13.0 Power Control Feature Parameter Description
Limitation
WRFD-171209 Coverage Improvement for HSUPA 2 ms TTI Ues RAN17.1 Power Control Feature Parameter Description
KPI guarantee WRFD-010690 TTI Switch for BE Services Based on Coverage RAN12.0 HSUPA TTI Selection Feature Parameter Description
WRFD-01061404 HSUPA 2ms/10ms TTI Handover RAN10.0 HSUPA TTI Selection Feature Parameter Description
WRFD-140103 Call Reestablishment RAN14.0 Call Reestablishment Feature Parameter Description
CE efficiency improvement WRFD-010638 Dynamic CE Resource Management RAN10.0 HSUPA Feature Parameter Description
WRFD-140212 CE Overbooking RAN14.0 CE Overbooking Feature Parameter Description
WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms RAN16.0 CE Efficiency Improvement for HSUPA TTI 2ms
Implementation
It is recommended that the features involved be deployed in target areas to reduce the video start delay. These features can be simultaneously enabled. For details about feature deployment, see related feature
parameter descriptions.
3.2.4 Scenario 3: Video Experience Improvement in Heavy Load Scenarios

Heavy load scenarios are characterized by numerous users, insufficient resources, poor service experience, and traffic suppression (traffic storm control). By use of software features, this solution improves video
service throughput and video experience as well as increases video traffic in heavy load scenarios.
In heavy load scenarios, the non-HSPA power load is not less than 40%, the value of VS.CellDCHUEs(BSC6900,BSC6910) is not less than 35 or the value of
VS.MeanULActualPowerLoad(BSC6900,BSC6910) is not less than 50%.
NOTE:
Non-HSPA power load = VS.MeanTCP.NonHS(BSC6900,BSC6910) (W)/CellMaxPower (W) x 100%
CellMaxPower indicates the maximum transmit power of a cell and is specified by the MAXTXPOWER(BSC6900,BSC6910) parameter in the RNC MML command ADD UCELLSETUP.
Solution Purpose
This solution helps reduce the video start delay and video stalling time ratio in heavy load scenarios, thereby improving video experience.
Service KPI statistic results show that both the video start delay and the video stalling time ratio decrease by 10%-20%.
DT results show that
For 480p/720p videos, the video start delay is less than 3.5s, the video stalling time ratio is less than 5%, and the VMOS ranges between 1.8 and 2.5.
For 1080p videos, the video start delay is less than 5s, the video stalling time ratio is less than 20%, and the VMOS ranges between 1.8 and 2.5.
NOTE:
With this solution, the features listed in the following table can be deployed to improve video experience in heavy load scenarios.
WRFD-171210 Radio-Aware Video Precedence Increases the priorities in video scheduling and flow control to improve HTTP RAN17.1 Service Awareness-based Experience
video experience in heavy load scenarios, where the TCP power ratio is greater Management Feature Parameter
than 65% and there are fewer than 50 CELL_DCH users. Specifically, the video Description
play stalling ratio decreases by 5%-20% and the video start delay decreases by
3%-15%.
WRFD-180210 Service Experience-based Forbids access of new users in heavily-loaded cells, where the TCP power ratio RAN18.1 Service Awareness-based Experience
Admission Control is greater than 80% and there are more than 40 users running best effort (BE) Management Feature Parameter
services, so that service experience of existing users in the cells can be Description
guaranteed. In this situation, an extra 5%-30% service traffic is allowed for the
cells.
WRFD-181203 User Experience Improvement on Differentiates services (including web browsing, video, and file upload) RAN18.1 Service Awareness-based Experience
APPs generated by specific APPs such as Facebook, YouTube, Sina Weibo, and Management Feature Parameter
WeChat, improving service experience on the APPs in heavy load scenarios, Description
where the TCP power ratio is greater than 65% and there are fewer than 50
CELL_DCH users. The video service rate increases by 5%-20%, and the video
start delay and video stalling time ratio decrease by 5%-20%.
NOTE:
This feature also takes effect on HTTP videos generated by the APPs YouTube and
Facebook.
WRFD-181202 Uplink Data Acceleration Compresses uplink PS service data of UEs capable of data compression RAN18.1 Uplink Data Acceleration Feature
to reduce uplink PS service data amount, thereby reducing uplink load. Parameter Description
Decreases the web browsing delay by 25% and reduces the video start
delay and video stalling time ratio for cells with severe power
congestion in the uplink, specifically, the uplink load is greater than or
equal to 75%.
Implementation
It is recommended that the WRFD-180210 Service Experience-based Admission Control feature be enabled in severe downlink power congestion scenarios. For example, when the non-HSPA power ratio
is greater than 60%, the TCP power ratio is greater than 80%, and there are more than 50 PS BE users. This feature is expected to yield more gains in cells where downlink congestion increases and user
experience deteriorates.
It is recommended that the WRFD-181202 Uplink Data Acceleration feature be enabled when both the following conditions apply:
Uplink power resources are in the medium congestion state. For example, the uplink load is greater than or equal to 50%.
There are uplink data acceleration (UDA) UEs in the target area.
In scenarios where downlink power resources are in the basic congestion state, for example, 60% ≥ Non-HSPA power ratio ≥ 40%. 85% ≥ TCP power ratio ≥ 65%, 50 ≥ Number of CELL_DCH UEs ≥ 35,
It is recommended that the WRFD-171210 Radio-Aware Video Precedence feature be enabled if traffic of HTTP videos (non-encrypted type) in the target area accounts for a large proportion (for
example, greater than 70%) of the entire video traffic.
It is recommended that the WRFD-181203 User Experience Improvement on APPs feature be enabled if traffic of HTTPS videos (encrypted type, like videos played on YouTube and Facebook)
in the target area accounts for a large proportion (for example, greater than 70%) of the entire video traffic.
Both features WRFD-171210 Radio-Aware Video Precedence and WRFD-181203 User Experience Improvement on APPs have the same service priority. If they are both enabled in the target area, neither feature
will yield the maximum gains.
3.2.5 Scenario 4: Video Experience Improvement at the Cell Edge

At the cell edge, user throughput or experience ranks in the bottom 5%-10%. Network coverage edge is always caused by weak coverage and strong interference.
This solution is introduced to improve the video experience of CEUs in scenarios described in Table 3-5.
Table 3-5 Scenarios
Scenario Description Feature
Soft handover areas in asymmetric coverage The uplink signal quality of the serving cell for a UE in the soft handover area is poorer than that of a HSDPA Rate Improvement in Asymmetric
neighboring cell. Coverage
The downlink pilot signal quality of the serving cell is better than that of a neighboring cell.
Such a scenario is usually identified in networks where the serving cell experiences strong interference in the uplink or
the serving cell has higher downlink pilot power than neighboring cells.
Softer handover areas Softer handover areas within a NodeB Uplink CoMP (Joint Reception)
Restricted uplink power for a UE in the soft handover area HSUPA UEs continuously perform uplink data services but have limited uplink power. That is, the value of the counter Inter-NodeB Uplink CoMP (Joint
VS.HSUPA.UPHLmtRatio.SI is greater than 10%. Reception)
Inter-NodeB overlapping areas DB-HSDPA capable UEs reside in overlapping areas of the U2100 and U900 serving different NodeBs. Inter-NodeB DB-HSDPA
Solution Purpose
This solution aims to increase the uplink and downlink throughput in cell edge scenarios, thereby improving video experience at the cell edge.
Service KPI statistic results show that downlink user throughput in target areas increases by 5%-20%.
DT results show that
For 480p/720p videos, the video start delay is less than 3.5s, the video stalling time ratio is less than 5%, and the VMOS ranges between 1.8 and 2.5.
For 1080p videos, the video start delay is less than 5s, the video stalling time ratio is less than 20%, and the VMOS ranges between 1.8 and 2.5.
NOTE:
With this solution, the features listed in the following table can be deployed to improve the uplink and downlink throughput in cell edge scenarios.
WRFD-180203 HSDPA Rate Improvement in Increases the throughput of HSDPA UEs in the soft handover area in asymmetric RAN18.1 HSDPA Rate Improvement in Asymmetric
Asymmetric Coverage coverage. Coverage Feature Parameter Description
WRFD-151205 Uplink CoMP (Joint Reception) Increases the uplink throughput of UEs in the softer handover area within a RAN16.0 Uplink CoMP Feature Parameter
NodeB. Description
WRFD-181204 Inter-NodeB Uplink CoMP (Joint Increases the uplink throughput of UEs in the soft handover area with restricted RAN18.1 Inter-NodeB Uplink CoMP Feature
Reception) uplink power. Parameter Description
WRFD-180212 Inter-NodeB DB-HSDPA Increases the downlink throughput of DB-HSDPA UEs residing in overlapping RAN18.1 Multi-Carrier HSDPA Feature Parameter
areas of the U2100 and U900 serving different NodeBs. Description
NOTE:
Ensure that uX2 interfaces have been deployed between NodeBs before deploying the Inter-NodeB Uplink CoMP (Joint Reception) feature.
The Inter-NodeB DB-HSDPA feature applies to networks with a high penetration rate of DB-HSDPA capable UEs. Ensure that uX2 interfaces have been deployed between NodeBs before deploying the Inter-NodeB DB-HSDPA feature.
Implementation
It is recommended that the preceding features be enabled to improve the air interface throughput and video experience in cell edge areas. These features are mutually compatible and can be enabled simultaneously.

3.3.1 Overview
In addition to the software feature solution, a more precise plan is required for improving video experience. A traditional network plan fails to provide such a solution due to the complexity of video services. A
traditional network plan can neither be specifically related to the video experience, nor predict any changes that may occur. Initiated by Huawei, the Video Coverage solution is a mobile network plan focusing on
enhanced video experience. This solution provides a visual display of the video experience condition, root analysis, expected plan result, and improvement predictions.
As shown in Figure 3-2, the video coverage solution covers four phases: video experience assessment and goal setting, network planning, network implementation, and verification.
Figure 3-2 Process of the video coverage solution
Descriptions of the process:
Video experience assessment and goal setting: Evaluates video experience related KPIs, such as the video start delay, video stalling time ratio, and video bitrate distribution. Performs gap and root cause
analysis in areas with low VMOS and poor video experience, identifies the main causes, summarizes typical scenarios, and determines the target network VMOS.
Network planning: Achieves planned goals by adding carriers, splitting sectors, deploying macro and micro NodeBs, or deploying features as required in gap areas caused by different root causes. This
phase is an iterative process, during which future network experience can be predicted based on the growth of the network user quantity and the traffic volume.
Network implementation: Implements scenario-specific network plans. During this phase, the software feature solution can also be deployed to further improve video experience.
Verification: Verifies whether the expected result has been achieved by analyzing data collected using DTs or service KPI statistics.
This document only outlines the deployment process and provides application examples of the video coverage solution. For detailed information about this solution, contact Huawei technical support.
3.3.2 Video Experience Assessment and Goal Setting

3.3.2.1 Video Experience Assessment
Video experience assessment enables an operator to quickly and comprehensively analyze aspects of video experience in its network, such as the video start delay, video stalling time ratio, and other service KPIs
as well as the VMOS. The video experience assessment can evaluate both non-encrypted videos (such as HTTP videos) and encrypted videos (such as videos played by YouTube and other APPs). Figure 3-3 shows
the video experience assessment process.
Figure 3-3 Video experience assessment process
NOTE:
WINS Space is currently available to customers. For details about this tool, contact Huawei technical support.
Based on service KPIs, the following information can be obtained: service composition of the live network, APP traffic proportions, and the video resolution percentage. Figure 3-4 shows the result of an analysis.
Figure 3-4 Video experience assessment result (example 1)
click to enlarge
Figure 3-5 shows the video start delay, video stalling time ratio, initial video start success ratio, and video download ratio for a site.
Figure 3-5 Video experience assessment result (example 2)
click to enlarge
By combining PCHR and MR data, a grid-level geographical display of the video start delay, video stalling time ratio, video start bitrate, video start success ratio can be achieved, facilitating identification of
typical scenarios for video service improvement. Figure 3-6 shows the assessment result for a site.
Figure 3-6 Grid-level video experience assessment result
click to enlarge
3.3.2.2 Goal Setting

The goal setting process is as follows:
1. Collects data on the target network and obtains the network's video resolution distribution.
2. Specifies the target resolution and determines the VMOS for the resolutions.
3. Determines the mapping of service KPIs to resolution and VMOS and works out the target service KPIs.
Figure 3-7 shows the proportion of video traffic by resolution for a site. The target VMOS can be specified based on the site's resolution-specific VMOS distribution and requirements for the video start delay and
video play stalling.
Figure 3-7 Video resolution distribution in a site
Use 720p HD videos as example. Set the target VMOS as 3.2 for this site because good video experience requires that the VMOS must be 3.2 or higher. To achieve the target, the video start delay must be shorter
than 3s and the video stalling time ratio must be 0.
After setting the video experience target counters, analyze the network conditions at the grid level to locate areas that cannot meet the target and require optimization.
At this site, 55.9% of areas cannot meet the target VMOS 3.2, as shown in Figure 3-8.
Figure 3-8 Areas with VMOS less than 3.2
click to enlarge
In 31.57% of areas at this site, the video start delay is longer than 3s, as shown in Figure 3-9.
Figure 3-9 Areas with video start delay longer than 3s
click to enlarge
In 28.47% of areas at this site, the video play stalling time ratio is greater than 1%, as shown in Figure 3-10.
Figure 3-10 Areas with video play stalling time ratio greater than 1%
click to enlarge
3.3.2.3 Defining Areas with and Causes of Poor Video Experience
Defining Poor Video Experience Areas

The VMOSs or service KPIs of a single counter based on the performance evaluation of the live network are displayed geographically with 50 m x 50 m grids.
Grid-level VMOS analysis

The grids with VMOS below the target value make up unqualified areas.
Assume that the target VMOS in a site is 3.2. The grid-level VMOS analysis shows that VMOS is smaller than the target value in 46.3% of grids. Figure 3-11 shows the grid-level VMOS analysis. Table
3-7 lists the grid-level VMOS results.
Figure 3-11 Grid-level VMOS analysis
Table 3-7 Grid-level VMOS analysis
VMOS Number of Grids Grid Ratio Qualified/Unqualified
[3.5, 4) 271 4.7% Qualified
[3.2, 3.5] 2788 49% Qualified
[2.9, 3.2) 1885 33% Unqualified
[2.5, 2.9) 342 6% Unqualified
[1, 2.5) 413 7.3% Unqualified
Grid-level analysis by counter
In terms of the video start delay, if basic video experience for 720p videos requires the delay to be 3s or shorter in a site, 30.7% of grids fail to meet the requirement. Table 3-8 shows the grid-level
analysis by counter.
Table 3-8 Grid-level analysis by counter
Video Start Delay (s) Number of Grids Grid Ratio Qualified/Unqualified

Video Start Delay (s) Number of Grids Grid Ratio Qualified/Unqualified
≤3 3949 69.3% Qualified
3-6 370 6.5% Unqualified
>10 965 16.9% Unqualified
Defining Causes of Poor Video Experience
After spotting poor video experience areas, perform further analysis to identify the causes. Figure 3-12 outlines the procedure for defining causes for poor video experience.
Figure 3-12 Procedure for defining causes of poor video experience
To define the scope of poor video experience, the following service KPIs have to be considered:
Video start delay

Video stalling time
Video start failure
For Layer 1 fault locating in Step 2 in the preceding figure, the causes for poor video experience fall into three categories based on the service KPI defining algorithm:
Faults on the RAN

Faults on the upper-level network of the RAN, such as the CN PS domain
Faults on the UE
Figure 3-13 shows the Layer 1 categories of causes for poor video experience.
Figure 3-13 Layer 1 categories of causes
Layer 2 cause locating in Step 3 in figure 2 is conducted based on the association of performance counters and PCHR data. The causes for poor video experience on the RAN are classified into four categories in
this step:
Uplink capacity
Downlink capacity
Coverage
Interference
Figure 3-14 and Figure 3-15 show the Layer 1 and Layer 2 cause locating results for a site, respectively.
Figure 3-14 Layer 1 cause locating result (example)
Figure 3-15 Layer 2 cause locating result (example)
Locating Root Causes

Perform grid-level analysis for unqualified areas in terms of low VMOSs and poor video experience. Locate root causes in terms of capacity (including TCP, User, and RTWP), coverage (RSCP), and interference
(Ec/Io).
The following are cases of unqualified VMOSs for a site.
Case 1: High RTWP results in unqualified VMOS. Figure 3-16 shows the cause locating result.
Figure 3-16 Unqualified VMOSs caused by high RTWP
click to enlarge
Case 2: Poor downlink coverage results in unqualified VMOS. Figure 3-17 shows the cause locating result.
Figure 3-17 Unqualified VMOSs caused by poor downlink coverage
click to enlarge
Case 3: The absence of indoor hotspots coverage results in unqualified VMOS. Figure 3-18 shows the cause locating result.
Figure 3-18 Unqualified VMOSs caused by the absence of indoor hotspots coverage
click to enlarge
3.3.3 Network Planning

Based on the video experience assessment result and target goals, specify the priority policy and prediction factors for the network improvement plan, such as sector splitting, adding carriers, macro NodeBs or
small cells. Based on the plans, perform iteration tests and simulation prediction to understand the expansion performance and video experience improvement effect in the VMOS in gap areas. Figure 3-19 shows
the overall process of network planning.
Figure 3-19 Network planning process
click to enlarge
In the simulation process, the video experience model needs to be created based on data collected from the live network. Figure 3-20 shows the simulation process.
Figure 3-20 Simulation process
click to enlarge
For example, after continuous optimization based on iterative simulation on site A, the VMOS and video experience of this site improves:
Splitting sectors and adding NodeBs are performed for the capacity expansion. The average VMOS after capacity expansion is greater than 3. The proportion of areas with VMOS greater than 3 increases from
15.9% to 33.2%. The video start delay is reduced from 9.33s to 6.47s.
Figure 3-21 Optimization result of the network capacity expansion in site A
3.3.4 Network Implementation

According to the network plan, perform network optimization, such as splitting sectors, adding carriers or NodeBs in target areas so as to improve the video experience in these areas.
3.3.5 Verification
Collect data on the network after the solution is implemented to evaluate solution performance.
Figure 3-22 shows the grid-level VMOSs collected before solution deployment, during planning and implementation, and after solution deployment.
Figure 3-22 Grid-level VMOSs before and after solution deployment
click to enlarge
Figure 3-23 shows the grid-level VMOS ratio.
Figure 3-23 Grid-level VMOS ratio
After the Video Coverage solution is deployed, the video play stalling ratio reduces by 1.24%, as shown in Figure 3-24.
Figure 3-24 Video play stalling time distribution
As shown in Figure 3-25, the video start delay reduces by 0.72s.

Figure 3-25 Video start delay distribution
click to enlarge
VMOS Video mean opinion score
MBB Mobile broadband
HSDPA Feature Parameter Description

Multi-Carrier HSDPA Feature Parameter Description
Downlink 64QAM Feature Parameter Description
HSUPA Feature Parameter Description
Enhanced L2 Feature Parameter Description
Power Control Feature Parameter Description
Load Based Dynamic Adjustment of PCPICH Feature Parameter Description
TCP Proxy Feature Parameter Description
User Experience Improvement for Lightly Loaded Cells Feature Parameter Description
Control Channel Interference Cancellation Feature Parameter Description
Uplink Control Channel OLPC Feature Parameter Description
Virtual CPC Feature Parameter Description
HSUPA TTI Selection Feature Parameter Description
Call Reestablishment Feature Parameter Description
CE Overbooking Feature Parameter Description
CE Efficiency Improvement for HSUPA TTI 2ms
Service Awareness-based Experience Management Feature Parameter Description
Uplink Data Acceleration Feature Parameter Description
HSDPA Rate Improvement in Asymmetric Coverage Feature Parameter Description
Uplink CoMP Feature Parameter Description
WCDMA RAN
UMTS Service Experience-based Network Construction Solution Guide

Issue 01
Date 2016-02-29

Notice
1.2.2 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3 Service Experience Optimization
3.1 Scenario 1: Web Browsing Services
3.2 Scenario 2: Video Services
3.3 Scenario 3: File Access Services
4 Service Experience-based Network Planning
4.1 Scenario Description
4.3 Solution Description
4.4 Implementation
4.4.1 Target Setting
4.4.2 Live Network Evaluation
4.4.3 Planning
4.4.4 Acceptance
1.1 Scope
1.3 Change History
1.1 Scope
Experience includes user experience and service experience. User experience management can be implemented by configuring the gold, silver, and copper user priorities, and UE differentiation. This document
focuses only on service experience and describes the service experience-based network construction solution, which consists of service experience optimization and service experience-based network planning. For
details about how to manage user experience, see UMTS User Experience Management Solution.

Need to understand the service experience-based network construction solution.

Work with Huawei products.
1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Added features WRFD-181203 User Experience Improvement on APPs and WRFD-181202 Uplink Data Acceleration to 3 Service Experience Optimization.
2 Solution Overview
2.1 Background
2.1 Background
As MBB networks develop, conventional network KPIs which indicate network accessibility and traffic volume cannot accurately represent network quality. For example, despite the good network accessibility, a
large number of users continue to report problems such as one-way audio, low throughput, and long delay. The reason is that conventional network KPIs do not indicate user-plane network quality. In addition, a
growing number of operators expect to plan and optimize their networks based on service experience to achieve satisfying service experience goals.
To ensure better service experience, Huawei introduces service experience KPIs to reflect actual service experience and provides a service experience-based network construction solution. This solution guides
service experience-oriented network planning and provides feature combination to improve user experience.

Different types of services have different service experience requirements. The same applies to operators' requirements on service assurance. As a result, operators must consider service experience during network
construction, capacity expansion, and optimization. Huawei service experience-based network construction solution applies to the following types of services:
Web browsing services

Video services
File access services
NOTE:
For details about how to improve voice service experience, see UMTS HD Voice Solution.

Huawei service experience-based network construction solution consists of the following functions:
Service experience evaluation and problem identification

Service experience optimization
Service experience-based network planning
NOTE:
For a new network or a swapped network, only service experience-based network planning is involved. You can use the KPIs of other networks in the same area as the criteria for network planning in this scenario.
Figure 2-1 illustrates these functions.

Figure 2-1 Overview of the service experience-based network construction solution
click to enlarge
Service Experience Evaluation and Problem Identification

Use the WINS Space tool to conduct a drive test to evaluate service experience and identify problems. This tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.
Service Experience Optimization

Service experience optimization applies to scenarios where poor service experience is caused by RAN network congestion.
In RAN12.0 or earlier, service experience is optimized based on service type awareness results. The feature WRFD-020128 Quality Improvement for Subscribed Service is used to improve the experience of
subscribed services.
A network intelligence unit (NIU) board is introduced in RAN13.0 to implement the service type awareness function. With this function, RAN13.0 provides the WRFD-020132 Web Browsing Acceleration and
WRFD-020133 P2P Rate Restriction During Busy Hours features to optimize service experience.
RAN15.0 introduces an open QoS management platform. This platform obtains the protocol types of MBB services using an NIU board and maps protocol types to service types. In this scenario, more elaborate
QoS management is implemented to promote network resource utilization, enhance quality for high-value services, and improve experience for high-end users.
RAN16.0 introduces features WRFD-150252 Video Service Rate Adaption and WRFD-150254 Differentiated Service Based on Application Resource Reservation. These features enrich the service experience
optimization solution.
RAN17.1 introduces the WRFD-170202 TCP Proxy feature. This feature improves user experience of web browsing, file access, and video services by optimizing TCP transmission performance in radio
environment.
RAN17.1 introduces the WRFD-171210 Radio-Aware Video Precedence feature. This feature preferentially improves service experience of video users by scheduling services according to the results of real-time
service experience measurement.
RAN18.1 introduces WRFD-180210 Service Experience-based Admission Control. This feature improves the volume of services in power congestion cells by controlling UE access.
RAN18.1 introduces WRFD-180106 User Experience Improvement for Lightly Loaded Cells. This feature improves user experience by increasing resources allocated to lightly loaded cells.
RAN18.1 introduces WRFD-181203 User Experience Improvement on APPs. This feature improves APP service experience by performing HSUPA/HSDPA scheduling for services generated by specific APPs
such as FaceBook, YouTube, Sina MicroBlog, and WeChat.
RAN18.1 introduces WRFD-181202 Uplink Data Acceleration. This feature increases uplink capacity, reduces data transmission delay, and improves web service experience by compressing uplink data on the UE
side and decompressing uplink data on the RNC side to reduce the amount of transmitted data and uplink interference over the air interface.
Service Experience-based Network Planning

Service experience-based network planning:
Sets service experience targets.

Evaluates service experience KPIs on the live network.
Identifies grids where the service experience is poor and converges these grids.
Performs iterative simulation on the converged grids by taking measures such as adding carriers/macro cells/SmallCells or splitting sectors.
Predicts service experience after network planning.
NOTE:
This document does not describe user experience management, which includes measures such as user differentiation, experience improvement for specific users, and special UE experience management. For details about how to manage user experience, see
UMTS User Experience Management Solution.
3 Service Experience Optimization

Web browsing services are carried over a web browser or an application software. Users can obtain media information such as texts or pictures from the server through the HTTP, for example, web browsing,
picture refreshing on Facebook, or non-video linking. Web browsing is one of the most popular data services offered by networks and users expect web pages to load quickly anytime and anywhere. This section
describes how to evaluate and optimize web browsing service experience.

This solution aims to reduce the page response and browsing delay, and increase the page download throughput.

Use the WINS Space to obtain KPIs such as the page response delay, page browsing delay (small page), and page download throughput (large page) on the live network. Compare the obtained values with Huawei-
defined reference KPI values to evaluate service experience and identify problem causes. The WINS Space tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.

The following measures are taken to improve experience of web browsing services:
HTTP response delay optimization
Fast F2D state transition for HTTP services can be used to reduce the delay of HTTP services. Most HTTP services in the network are transmitted over TCP port 80 or 8080. After receiving IP data flow
from TCP port 80 or 8080, the RNC immediately enables a CELL_FACH-to-CELL_DCH (F2D) state transition to reduce the response delay of HTTP services (including web browsing and video
services) and improve transmission efficiency on the Uu interface.
Optimized scheduling weight for subscribed services
If operators expect to accelerate self-operating services or services offered by providers that have a subscription relationship with the operator, the WRFD-020128 Quality Improvement for Subscribed
Service feature can be used to improve service experience. This feature enables the RNC to analyze IP packets and obtain the server IP address and port number. If the IP data flow contains the server IP
address and port number for the service that the user has subscribed to, the RNC allocates a greater scheduling weight and a higher bandwidth to increase the data rate in a congested network, thereby
improving user experience.
TCP Proxy
The majority of PS data in the wireless network is sent over the TCP protocol. The round trip time (RTT) between the UE and service provided (SP) is long. As a result, the TCP data transmission rate is
low. The slow start function is used during the initial stage of TCP data transmission, which causes the TCP data transmission rate to increase slowly. Packet loss on the Uu interface reduces the size of the
TCP congestion window and as a result, slows down the data transmission rate. The WRFD-170202 TCP Proxy feature introduced on the RAN side can improve TCP performance in the wireless network
and therefore improve service experience.
Web page access acceleration
If operators expect to improve user experience for all web browsing services, the WRFD-020132 Web Browsing Acceleration feature can be enabled to preferentially allocate higher bandwidth to web
browsing services. This shortens the delay in downloading web pages and improves service experience.
P2P downloading rate control
P2P downloading services generate high volume and last for a long time. Users performing P2P downloading services have low requirements on data transmission delay. P2P traffic consumes a large
amount of system resources, which significantly increases the operating expense (OPEX) and adversely affects the quality of delay-sensitive services. After the NIU board is deployed, the service type
awareness function can identify mainstream P2P downloading services.
If operators expect to limit the data rates of all P2P downloading services in busy hours, the WRFD-020133 P2P Downloading Rate Control During Busy Hour feature can be enabled. When the Uu load
is heavy, this feature limits the data rates of P2P downloading services to release some occupied resources for other types of services. When the Uu load is light, this feature returns resources to P2P
downloading services to achieve a high P2P service downloading rate. This enables radio resources to be fully utilized.
Service-based resource management
In a network with heavy HSDPA traffic, service experience deteriorates if downlink power resources become insufficient. The WRFD-150254 Differentiated Service Based on Application Resource
Reservation feature can be used to limit the number of downlink HSDPA power resources available to low-value services and reserves sufficient downlink HSDPA power resources for high-value services
when downlink power resources are insufficient. This feature improves user experience for high-value services.
Open QoS management platform
If operators expect to improve web browsing experience on certain websites, the open QoS management platform can be used for QoS customization.
Service Experience-based Admission Control
This feature guarantees the service experience in cells with insufficient power resources by controlling UE access to the cells, thereby increasing the number of satisfactory web services in the cells.
User Experience Improvement for Lightly Loaded Cells
This feature improves the service experience in networks with a large number of lightly loaded cells.
User Experience Improvement on APPs

This feature performs HSUPA/HSDPA scheduling for services generated by specific APPs such as Facebook, YouTube, Sina microblog, and WeChat, improving web access experience.
Uplink Data Acceleration

This feature compresses uplink data on the UE side and decompresses the data on the RNC side to decrease the amount of transmitted data over the Uu interface, and decrease uplink transmission delay
for web services, improving user experience.
List of Features and Functions Involved in the Solution

Table 3-1 List of features and functions involved in the solution for managing web browsing experience
Function Classification Feature ID Feature Name Introduced In... Reference Document
Service Experience Optimization WRFD-020128 Quality Improvement for Subscribed Service RAN12.0 Service Awareness-based Experience
Management Feature Parameter
Description
Service Experience Optimization N/A Fast F2D state transition for HTTP services RAN16.0 State Transition Feature Parameter
Description
Service Experience Optimization WRFD-170202 TCP Proxy RAN17.1 TCP Proxy Feature Parameter Description
Service Experience Optimization WRFD-020132 Web Browsing Acceleration RAN13.0 Service Awareness-based Experience
Description
Service Experience Optimization WRFD-150254 Differentiated Service Based on Application RAN16.0 Service Awareness-based Experience
Resource Reservation Management Feature Parameter
Description
Service Experience Optimization WRFD-020133 P2P Downloading Rate Control during Busy RAN13.0 Service Awareness-based Experience
Hour Management Feature Parameter
Description
Service Experience Customization N/A Open QoS management platform RAN15.0 Service Awareness-based Experience
Description
Service Experience Optimization WRFD-180210 Service Experience-based Admission RAN18.1 Service Awareness-based Experience
Control Management Feature Parameter
Description
Service Experience Optimization WRFD-180106 User Experience Improvement for Lightly RAN18.1 User Experience Improvement for Lightly
Loaded Cells Loaded Cells Feature Parameter
Description
Service Experience Optimization WRFD-181203 Experience Improvement RAN18.1 Service Awareness-based Experience
Description
Service Experience Optimization WRFD-181202 Uplink Data Acceleration RAN18.1 Uplink Data Acceleration Feature
Parameter Description
Description of Features and Functions Involved in the Solution
WRFD-020128 Quality Improvement for Subscribed Service

When radio resources or Iub resources are insufficient, the WRFD-020128 Quality Improvement for Subscribed Service feature accelerates the data rates of subscribed services.
Fast F2D state transition for HTTP services
This function accelerates the F2D state transition for HTTP services and reduces the delay in downloading web pages.
WRFD-170202 TCP Proxy
The TCP Proxy feature introduced on the RAN side improves TCP performance in the wireless network, thereby improving service experience.
WRFD-020132 Web Browsing Acceleration
When radio resources or Iub resources are insufficient, the WRFD-020132 Web Browsing Acceleration feature accelerates the web page downloading rate.
WRFD-150254 Differentiated Service Based on Application Resource Reservation
When downlink power resources are congested, this feature allocates a higher maximum HSDPA power ratio to the resource group where web browsing services belong. For non-paid services that occupy
high bandwidth, this feature maps these services to other resource groups and configures a low maximum HSDPA power ratio for these resource groups so that power resources can be allocated to high-
value services. The configured proportion of the maximum HSDPA transmit power should be lower than 75% for at least one resource group.
WRFD-020133 P2P Downloading Rate Control During Busy Hour
When resources over the Iub and Uu interfaces are congested, this feature reduces the scheduling priority of P2P services to decrease the P2P service rate, thereby reducing resource consumption.
The open QoS management platform uses an NIU board to obtain the protocol types of MBB services, maps protocol types to service types, and maps service types to QoS policies. As a result, this
feature implements more elaborate QoS management to increase network resource utilization. With this open QoS management platform, Huawei provides a service solution named SmartCare SQI-Data
professional services to cover various MBB services and quickly respond to diversified optimization requirements. Contact Huawei technical support engineers to purchase SmartCare SQI-Data
professional services.
WRFD-180210 Service Experience-based Admission Control
This feature applies to scenarios where power resources are congested and the proportion of satisfactory services is low. This feature adaptively increases or reduces the threshold of admitted PS BE RABs
based on the service satisfaction rate.
WRFD-180106 User Experience Improvement for Lightly Loaded Cells
This feature monitors the network load status in real time. When the network is lightly loaded, this feature automatically activates related algorithms or adjusts related configuration parameters to improve
user experience. The algorithms include:
Rapid state transition from Cell_FACH to Cell_DCH and slow return from Cell_DCH to Cell_FACH
Increasing the initial rates of uplink PS R99 services
Increasing the uplink DCCC rate threshold for PS R99 services
WRFD-181203 User Experience Improvement on APPs

This feature provides differentiated services and improved web service experience by decreasing the page display delay or page downloading rate by 5% to 20%.
WRFD-181202 Uplink Data Acceleration
This feature compresses uplink data on the UE side and decompresses the data on the RNC side to decrease the amount of transmitted data over the Uu interface, and decrease uplink transmission delay
for web services by 20% to 70% for congested cells or cell edge users.
The deployment and activation of each feature will not be described in this document and will be included in the corresponding feature parameter description.
In this application scenario, features and functions are independent of each other. They do not have constraint relationships and can be deployed together.
If WRFD-181203 User Experience Improvement on APPs and WRFD-020128 Quality Improvement for Subscribed Service are simultaneously enabled, APP services are preferentially scheduled and subscribed
services are scheduled based on the SPI weight. This affects the performance of WRFD-020128 Quality Improvement for Subscribed Service.
If WRFD-181203 User Experience Improvement on APPs and WRFD-020132 Web Browsing Acceleration are simultaneously enabled, APP services are preferentially scheduled and then web browsing services
are scheduled based on the SPI weight. This affects the performance of WRFD-020132 Web Browsing Acceleration.
If WRFD-181203 User Experience Improvement on APPs and WRFD-150254 Differentiated Service Based on Application Resource Reservation are simultaneously enabled, the amount of power resources for
APP services cannot exceed the reserved power resources in the resource group of the UE.

Video services are carried over a web browser or an application software. Users obtain video information from the server through the HTTP, for example, watching videos on Youku or Facebook. Video service is
becoming one of the most important data services on MBB networks. Smooth video playback is the prime concern for users. This section describes how to evaluate and optimize video service experience.

This solution aims to:
Increase the success rate of initial video play

Reduce the initial buffering delay as well as the video stall rate and duration
Increase the video download throughput

Use the WINS Space tool to obtain KPIs such as the success rate of initial video play, initial buffering delay, video stall rate, video stall duration, and video downloading throughput on the live network. Compare
the obtained values with Huawei-defined reference KPI values to evaluate service experience and identify problem causes. The WINS Space tool is currently unavailable to customers. For details about this tool,
contact Huawei technical support.
Video services use the same service optimization measures as web browsing services. These measures include HTTP response delay optimization, subscribed service scheduling weight optimization, TCP
proxy, P2P service suppression, service-based resource reservation, and user experience improvement for lightly loaded cells. For details, see 3.1.3 Solution Description.
Video service rate adaption
If operators expect to improve user experience for all video services, the WRFD-150252 Video Service Rate Adaption feature can be used to allocate bandwidth required for video services. This ensures
smooth video playback and improves service experience. The cell-level video service experience KPIs can be used to evaluate the effects of the WRFD-150252 Video Service Rate Adaption feature.
Video service precedence
The WRFD-171210 Radio-Aware Video Precedence feature preferentially improves user experience of video services by scheduling services based on the results of real-time service experience
measurement.

If operators expect to improve experience of a certain type of services, the open QoS management platform can be used for QoS customization.
Service Experience-based Admission Control
This feature guarantees the service experience in cells with insufficient power resources by controlling UE access to the cells, thereby increasing the number of satisfactory video services in the cells.
User Experience Improvement for Lightly Loaded Cells
This feature improves the service experience in networks with a large number of lightly loaded cells.
User Experience Improvement on APPs
This feature performs HSUPA/HSDPA scheduling for services generated by specific APPs such as FaceBook, YouTube, Sina MicroBlog, and WeChat, improving video service experience.

Table 3-2 List of features and functions involved in the solution for service experience management based on RAN-initiated service type awareness
Service Experience Optimization WRFD-020133 P2P Downloading Rate Control during Busy RAN13.0 Service Awareness-based Experience
Hour Management Feature Parameter
Description
Service Experience Optimization WRFD-150252 Video Service Rate Adaption RAN16.0 Service Awareness-based Experience
Description
Description
Service Experience Optimization N/A Fast F2D state transition for HTTP services RAN16.0 State Transition Feature Parameter
Description
Service Experience Optimization WRFD-171210 Radio-Aware Video Precedence RAN17.1 Service Awareness-based Experience
Description
Description
Service Experience Optimization WRFD-180210 Service Experience-based Admission RAN18.1 Service Awareness-based Experience
Control Management Feature Parameter
Description
Service Experience Optimization WRFD-180106 User Experience Improvement for Lightly RAN18.1 User Experience Improvement for Lightly
Loaded Cells Loaded Cells Feature Parameter
Description
Service Experience Optimization WRFD-181203 User Experience Improvement on APPs RAN18.1 Service Awareness-based Experience
Description
WRFD-020133 P2P Downloading Rate Control During Busy Hour

When air interface resources or Iub resources are insufficient, the WRFD-020133 P2P Downloading Rate Control During Busy Hour feature limits the data rates of P2P downloading services, thereby
improving user experience of other delay-sensitive services.
WRFD-150252 Video Service Rate Adaption
When radio resources or Iub resources are insufficient, the WRFD-150252 Video Service Rate Adaption feature allocates the bandwidth required for video services so that video playback is smooth and
unnecessary high data rates are not allocated.
When downlink power resources become insufficient, the WRFD-150254 Differentiated Service Based on Application Resource Reservation feature limits the number of downlink HSDPA power
resources available to low-value services and reserves sufficient downlink HSDPA power resources for high-value services.
Fast F2D state transition for HTTP services
This function accelerates the F2D state transition for HTTP services and reduces the delay in downloading web pages.
WRFD-171210 Radio-Aware Video Precedence
When air interface resources or Iub resources are insufficient, the WRFD-171210 Radio-Aware Video Precedence feature preferentially improves user experience of video services by scheduling services
based on the results of real-time service experience measurement. This feature makes the initial buffer delay of video services reach the configured target value and increases the proportion of video
services that do not experience video freezing in the cell.
WRFD-180210 Service Experience-based Admission Control
This feature applies to scenarios where power resources are congested and the proportion of satisfactory services is low. This feature adaptively increases or reduces the threshold of admitted PS BE RABs
based on the service satisfaction rate.
WRFD-180106 User Experience Improvement for Lightly Loaded Cells
This feature monitors the network load status in real time. When the network is lightly loaded, this feature automatically activates related algorithms or adjusts related configuration parameters to improve
user experience. The algorithms include:
Rapid state transition from Cell_FACH to Cell_DCH and slow return from Cell_DCH to Cell_FACH
Increasing the initial rates of uplink PS R99 services
Increasing the uplink DCCC rate threshold for PS R99 services

This feature performs HSUPA/HSDPA scheduling for services generated by specific APPs such as FaceBook, YouTube, Sina MicroBlog, and WeChat, improving video service experience.
If Quality Improvement for Subscribed Service and Radio Aware Video Preference are both enabled, video services are preferentially scheduled. Subscribed services and other types of services are scheduled based
on the SPI weight. The quality of subscribed services is affected.
If Web Browsing Acceleration and Radio Aware Video Preference are both enabled, video services are preferentially scheduled. Web services and other types of services are scheduled based on the SPI weight. The
quality of web services is affected.
If WRFD-171210 Radio-Aware Video Precedence and WRFD-150252 Video Service Rate Adaption are both enabled, only the former takes effect for HTTP videos.
If WRFD-171210 Radio-Aware Video Precedence and WRFD-150254 Differentiated Service Based on Application Resource Reservation are both enabled, the amount of power allocated to video services cannot
exceed the amount of reserved power.
If WRFD-181203 User Experience Improvement on APPs and WRFD-150252 Video Service Rate Adaption are both enabled, APP services are preferentially scheduled and non-APP video services are scheduled
based on the SPI weight. This affects the performance of WRFD-150252 Video Service Rate Adaption.
If WRFD-181203 User Experience Improvement on APPs and WRFD-171210 Radio-Aware Video Precedence are both enabled, both APP services and video services are preferentially scheduled, which reduces
gains of WRFD-171210 Radio-Aware Video Precedence.
If WRFD-181203 User Experience Improvement on APPs and WRFD-150233 Differentiated Service Based on Resource Reservation are both enabled, the amount of power allocated to video services cannot
exceed the amount of reserved power.

File access services are delivered through a web browser or an application software. Users download files from or upload files to the server using HTTP. Users expect a higher data rate and shorter delay during file
access.

This solution aims to increase the file upload and download rates, and reduce the file upload and download delay.

Use the WINS Space tool to obtain KPIs such as the file downloading delay, downloading rate, file uploading delay, and file uploading rate on the live network. Compare the obtained values with Huawei-defined
reference KPI values to evaluate service experience and identify problem causes. The WINS Space tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.

File access services use the same service optimization measures as web browsing services. These measures include optimized scheduling weight for subscribed services, TCP proxy, service-based resource
reservation, and open QoS platform. For details, see 3.1.3 Solution Description.

Table 3-3 List of features and functions involved in the solution for improving file access experience
Description
Service Experience Optimization WRFD-020128 Quality Improvement for Subscribed Service RAN12.0 Service Awareness-based Experience
Description
Description
Service Experience Optimization WRFD-181203 User Experience Improvement on APPs RAN18.1 Service Awareness-based Experience
Description

When downlink power resources become insufficient, the WRFD-150254 Differentiated Service Based on Application Resource Reservation feature limits the number of downlink HSDPA power
resources available to low-value services and reserves sufficient downlink HSDPA power resources for high-value services.
WRFD-020128 Quality Improvement for Subscribed Service
When air interface resources or Iub resources are insufficient, the WRFD-020128 Quality Improvement for Subscribed Service feature accelerates the data rates of subscribed services.
This feature performs HSUPA scheduling for services generated by specific APPs such as FaceBook, YouTube, Sina MicroBlog, and WeChat, improving experience of APP file uploading services.
In this application scenario, features and functions are independent of each other. They do not have constraint relationships and can be deployed together.
4 Service Experience-based Network Planning
4.4 Implementation

Service experience-based network planning applies to the following scenarios:
The NIU and SAU boards have been deployed.

Customers want to improve user experience for voice, web browsing, or video services.
For a new network or a swapped network where service experience cannot be obtained, use network KPIs of other networks in the same area as the network construction criteria.

Service experience-based network planning helps users achieve service experience targets through planning and prediction, and provides network topology changes, thereby simplifying network optimization.

Service experience-based network planning works as follows:
Improves grids that have service experience gaps by:

Setting service experience targets
Evaluating service KPIs on the live network
Identifying grids with service experience gaps and converging these grids
Performing iterative simulation on the converged grids (such as adding carriers/macro cells/small cells or splitting sectors)
Predicts service experience after network planning.
Figure 4-1 Service experience-based network planning
4.4 Implementation
This section describes how to perform service experience-based network planning and how to verify the planning results. The planning involves the following tasks:
1. Target setting
2. Live network evaluation
3. Planning
4. Acceptance
4.4.1 Target Setting

Set the targets of service experience-based network planning based on commercial network conditions. The planning target can be set according to the following standards:
Absolute standard
Service experience reference KPI values are used as the network construction standard.
Relative standard
Use any of the following standards:
Use the best KPIs of other networks that are deployed in the same area as the current network as the network construction standard.
Use KPIs of the area with best network quality in the current network as the network construction standard.
Use the best xx percentage of KPIs in the current network as the network construction standard.
4.4.2 Live Network Evaluation

Live network evaluation includes data acquisition and processing.
Data acquisition
Collect the following data on the live network before performing service experience-based network planning:
RNC PCHR data
PCHR contains data related to service experience and can be used for service experience analysis.
RNC performance counters
Conventional RNC performance counters can be used to determine the traffic volume and user number.
NodeB traffic statistics
Conventional NodeB traffic statistics can be used to calculate the data rate of a single user.
RNC MR data
Conventional RNC MR data can be used to collect traffic statistics. When MR is used together with the PCHR for data analysis, you are advised to enable the A-GPS function.
Engineering parameters
Use engineering parameters of sites on the live network.
E-map
E-map of related areas can truly display the terrain features of the planned area.
Data processing
After data collection, use the WINS Space tool to evaluate the collected data, generate geographical data, and provide mapping between service experience and the planning elements. The WINS Space
tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.
4.4.3 Planning
At present, the U-Net is used for network planning. For the U-Net use guide, contact Huawei technical support engineers.
4.4.4 Acceptance
After service experience-based network planning is implemented, use the WINS Space tool to verify the planned KPIs after network optimization. The smallest area for verification must be a cluster. The WINS
Space tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.
For details about how to verify voice services, see UMTS HD Voice Solution.
Feature ID Feature Name Introduced In... Reference Document
WRFD-020128 Quality Improvement for Subscribed Service RAN12.0 Service Awareness-based Experience Management
Feature Parameter Description
N/A Fast F2D state transition for HTTP services RAN16.0 State Transition Feature Parameter Description
WRFD-020132 Web Browsing Acceleration RAN13.0 Service Awareness-based Experience Management

WRFD-020133 P2P Downloading Rate Control during Busy Hour RAN13.0 Service Awareness-based Experience Management
WRFD-150252 Video Service Rate Adaption RAN16.0 Service Awareness-based Experience Management
WRFD-150254 Differentiated Service Based on Application Resource RAN16.0 Service Awareness-based Experience Management
Reservation Feature Parameter Description
N/A Open QoS management platform RAN15.0 Service Awareness-based Experience Management
WRFD-170202 TCP Proxy RAN17.1 TCP Proxy Feature Parameter Description
WRFD-171210 Radio-Aware Video Precedence RAN17.1 Service Awareness-based Experience Management

WRFD-180210 Service Experience-based Admission Control RAN18.1 Service Awareness-based Experience Management
WRFD-180106 User Experience Improvement for Lightly Loaded Cells RAN18.1 User Experience Improvement for Lightly Loaded Cells
WRFD-181203 User Experience Improvement on APPs RAN18.1 Service Awareness-based Experience Management
WRFD-181202 Uplink Data Acceleration RAN18.1 Uplink Data Acceleration Feature Parameter
Description
Acronyms and Abbreviations Full Name
SA Service Awareness
MBB Mobile Broadband
NIU Network Intelligence Unit
QoS Quality of Service
1. Service Awareness-based Experience Management Feature Parameter Description

2. TCP Proxy Feature Parameter Description
3. State Transition Feature Parameter Description
4. User Experience Improvement for Lightly Loaded Cells Feature Parameter Description
WCDMA RAN
UMTS User Experience Management Solution Guide
Issue 01
Date 2015-04-20

Notice
1.2.3 Contents
1.1 Overview
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Scenario 1: Differentiated User Experience Management for Different Users
3.2 Scenario 2: User Experience Improvement of Special Users
3.3 Scenario 3: Differentiated User Experience Management for Different Terminals
3.4 Scenario 4: User Experience Management of Special Terminals
1.1 Overview
1.3 Change History
1.1 Overview
This document describes user experience management solutions provided by Huawei for different application scenarios in UMTS networks.

Need to understand UMTS user experience
1.3 Change History

This section provides information on the changes in different document versions.
RAN17.1 01 (2015-04-20)
This is the first commercial release of RAN17.1.
Compared with Issue 01 (2014-05-15) of RAN16.0, 01 (2015-04-20) for RAN17.1 includes the following changes:
Added lightweight user experience evaluation to 3.1 Scenario 1: Differentiated User Experience Management for Different Users.
Added the platinum user enhancement function to 3.2 Scenario 2: User Experience Improvement of Special Users.
Added the feature WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals to 3.4 Scenario 4: User Experience Management of Special Terminals.
2 Solution Overview
2.1 Background
2.1 Background
Since intelligent terminals become more and more popular and requirements for PS services increase dramatically, congestion often occurs on UMTS networks and user experience deteriorates in different degrees.
To mitigate network congestion, network optimization can be performed to improve resource utilization or capacity expansion can be performed, which improves user experience. In some networks, capacity
expansion cannot be performed and congestion cannot be avoided. Operators propose some requirements for user experience improvement under network congestion circumstances:
High-priority subscribers (such as those who pay more fees, high-value gold subscribers, and VIP subscribers like platinum subscribers) are provided better services and can preferentially utilize network
resources.
Certain types of terminals (such as those customized for operators) are set to high- or low-priority UEs to limit resource utilization of low-valued terminals such as data cards, which may occupy much
radio resources if not limited.
The performance or compatibility problems of some terminals need to be mitigated to improve user experience.
To meet these requirements, this solution provides the following user experience management functions: Users are distinguished using the following methods:
Distinguishing gold, silver, and copper users by QoS parameters of the CN

Identifying platinum users by IMSI configured on the RNC
Distinguishing different types of terminals by IMEI TAC

This solution applies to four scenarios:
Differentiated User Experience Management for Different Users

If there are users of different priorities in the networks, for example, gold users with high fees and high values and copper users with low fees and low values, users of different priorities such as gold, silver, and
copper users can obtain different service quality and user experience when network resources are insufficient. Services of gold users are guaranteed preferentially.
User Experience Improvement of Special Users

In heavy-traffic scenarios, for example, gathering, events, and festivals, the traffic volume increases dramatically, which causes severe congestion of the network and a significant decrease in the access success
rate. In this case, the network access of some special users such as platinum users needs to be preferentially guaranteed.
Differentiated User Experience Management for Different Terminals

If there are many low-valued terminals such as data cards in networks, which occupy a huge amount of radio resources but provide limited revenues to operators and they are less sensitive to user experience, these
low-valued terminals can be set to low-priority UEs and some other terminals can be set to high-priority UEs to control radio resource utilization. Different types of terminals are granted different priorities so that
they are provided with services of different qualities when network resources are insufficient.
User Experience Management of Special Terminals

User experience of some problematic terminals in networks needs to be improved, for example, terminals with poor reception performance or terminals with compatibility problems.

Figure 2-1 shows functions involved in the user experience management solution.
Figure 2-1 User experience management solution
click to enlarge
Delivering parameters over the RANAP (Iu) interface

The CN transfers some QoS parameters to the RNC, including the traffic class, ARP, MBR, and GBR. The gold, silver, and copper users are distinguished by ARP.
Experience management (SRNC)
QoS parameter mapping
The SRNC converts QoS parameters from the CN into those used by the RAN, for example, SPI, SPI Weight, MBR, GBR, and HBR. For details, see QoS Feature Parameter Description. Gold,
silver, and copper users are differentiated by these parameters. In addition to QoS parameters delivered by the CN, the RAN provides the IMSI for identifying platinum users.
RRM/TRM algorithm
Parameters for differentiating users are used in wireless algorithms such as the RB configuration, admission control, load control, flow control algorithms to guarantee resource utilization of
high-priority users during radio resource congestion.
Delivering NBAP (Iub) and RNSAP (Iur) parameters

The SRNC transfers some parameters to the NodeB over the Iub and Iur interfaces, which are used by algorithms on the NodeB side.
Experience management (NodeB)
The scheduling algorithm and flow control algorithm guarantee that high-priority subscribers preferentially use air interface resources and transport resources.
User experience evaluation

RAN17.1 supports SPI- and terminal group-based experience evaluation of web services and video services. For details, see Service Awareness-based Experience Management Feature Parameter
Description and Differentiated HSPA Service Feature Parameter Description.


In networks that sometimes experience congestion, there are gold, silver, and copper users, which are prioritized based on factors such as the paid fees. Gold users have the highest priority and copper users have
the lowest priority. When resources are insufficient, users with different priorities obtain different network resources. Users with higher priority preferentially obtain services and are guaranteed better experience.
Resource congestion mainly consists of power resource congestion and transport resource congestion. Various counters can be used to define different types of network congestion. The following methods are used
for reference only:
Downlink power
Total TCP usage = VS.MeanTCP(BSC6900,BSC6910) (W)/Configured PA Capacity (W) x 100%
Non-HS TCP usage = VS.MeanTCP.NonHS(BSC6900,BSC6910) (W)/Configured PA Capacity (W) x 100%
When the total TCP usage is greater than or equal to 80% or the non-HS TCP usage is greater than or equal to 70%, it is regarded that downlink power congestion occurs.
Uplink power
Assuming that the target load of the target cell is configured to 75% and the minimum RTWP of a day is the floor noise, the cells that experience load rises of more than 6 dB are regarded as having uplink
power congestion.
Downlink Iub transmission
Downlink bandwidth utility during busy hours = Downlink throughput during busy hours (equal to the sum of throughput of all IP paths VS.IPPATH.IPLAYER.RXBYTES)/Receive bandwidth
RX_BW_CFG (equal to the value of RxBW)
When the downlink bandwidth utility during busy hours is greater than or equal to 70%, it is regarded that downlink Iub transmission congestion occurs.
Uplink Iub transmission

Uplink bandwidth utility during busy hours = Uplink throughput during busy hours (equal to the sum of throughput of all IP paths VS.IPPATH.IPLAYER.RXBYTES)/Transmit bandwidth
TX_BW_CFG (equal to the value of TxBW )
When the uplink bandwidth utility during busy hours is greater than or equal to 70%, it is regarded that uplink Iub transmission congestion occurs.

In RAN congestion scenarios, operators can provide differentiated services to users with different priorities. Gold users have the highest priority. They can access the network and utilize network resources
preferentially.

Mapping between gold/silver/copper users and the ARP
The RNC distinguishes gold, silver, and copper users by the ARPs in the RAB Assignment Request message sent by the CN. The ARP indicates the priority of a user. For the mapping between the ARP
and the gold, silver, and silver users, see QoS Management Feature Parameter Description.
RAN17.1 introduces the enhanced differentiated UTRAN QoS management function. This function enhances the QoS mapping mechanism over the Uu interface and provides diversified differentiated
QoS experience for users.
This function enhancement involves the following three aspects:
Enhanced RAB integrated priority mapping. That is, RAB integrated priorities are configured based on the traffic class (TC, SSD, SI, or THP), service bearer type (R99 or HSPA), and ARP (1 to
15).
Enhanced SPI mapping. That is, SPIs of HSPA services are configured based on the traffic class (TC, SSD, SI, or THP) and ARP (1 to 15).
Enhanced GBR mapping. That is, GBRs of services are configured based on the traffic class (TC, SSD, SI, or THP), service bearer type (R99 or HSPA), and ARP (1 to 15).
Service experience evaluation for gold, silver, and copper users

RAN17.1 provides counters for SPI-based lightweight user experience evaluation. These counters can be used to evaluate the service experience of gold, silver, and copper users on live networks. For
details, see Differentiated HSPA Service Feature Parameter Description.
Differentiated service experience of gold, silver, and copper users
click to enlarge
1. Service admission
The comprehensive user priority is related to QoS parameters such as ARP, THP, and Traffic class, which are used in the pre-emption process triggered by a failure in admission of RAB resources
(power, code resources, CE resources, and Iub transmission resources). High-priority users can preempt resources of low-priority users.
2. Cell congestion control
The comprehensive user priority is also used for load control of a cell, for example, user selection during load-based inter-frequency handovers for LDR and user selection during switchover the BE
services to the CCH. High-priority users will be selected with the lowest probability.
3. Differentiated HSPA services
Based on ARP and other QoS parameters such as THP and Traffic Class, SPI, SPI Weight, GBR, and HBR can be configured and used in scheduling algorithm and flow control algorithm, which ensure
that high-priority users take precedence over low-priority users in the scheduling opportunities and transmission bandwidth so that they can obtain better HSPA services.

Table 3-1 lists the features involved in the solution of differentiated user experience management for different users.
Table 3-1 Features involved in the solution of differentiated user experience management for different users
Differentiated service experience of WRFD-010505 Queuing and Pre-Emption RAN5.0 Load Control Feature Parameter Description
gold, silver, and copper users
Differentiated service experience of WRFD-020806 Differentiated Service Based on SPI Weight RAN11.0 Differentiated HSPA Service Feature Parameter
gold, silver, and copper users Description
Differentiated service experience of WRFD-150233 Differentiated Service Based on Resource Reservation RAN15.0 Differentiated Service Based on Resource Reservation
gold, silver, and copper users Feature Parameter Description
Service experience evaluation for gold, NA Lightweight User Experience Evaluation RAN16.0 Service Awareness-based Experience Management Feature
silver, and copper users Parameter Description
WRFD-010505 Queuing and Pre-Emption

This feature provides the function of queuing and preemption, allowing high-priority users to preempt resources of online low-priority users so that high-priority users can be successfully admitted.
WRFD-020806 Differentiated Service Based on SPI Weight
This feature allows different users to be configured with different SPI weights. High-priority users are configured with greater SPI weights so that they can preferentially consume power and transport
resources when power and transport resources are congested.
WRFD-150233 Differentiated Service Based on Resource Reservation
This feature limits power resources to be consumed by users of different priorities.
Lightweight User Experience Evaluation
This feature supports SPI-based lightweight user experience evaluation.
The deployment anVoice Experience Improvement for Weak Reception UEsbed in this document and will be included in the corresponding documents about RAN features.
Pay attention to the following issues when deploying these features:
WRFD-010505 Queuing and Pre-Emption

There are no requirements for deploying this feature. However, preemption may cause an increase in the call drop rate.
It is recommended that this feature be enabled in power congestion and transmission resource congestion scenarios. It is used to specify different SPI weights for users of different priorities by configuring
QoS parameters on the CN side.
WRFD-150233 Differentiated Service Based on Resource Reservation
This feature can be used with the WRFD-020806 Differentiated Service Based on SPI Weight feature together. If the downlink power congestion occurs frequently or the congestion is severe, and a
specific type of users occupies a high percentage of all users and these users consume more resources than other users, affecting experience of other users. For example, if there are too many copper users
in a cell, who consume many downlink power resources, resources that can be used by gold users are affected, leading to poor experience of the gold users. In this circumstance, you can enable this
feature to limit resources that can be used by a type of users. This feature restricts HSDPA power resources that can be used by low-valued user groups and reserves downlink power resources for other
high-valued user groups during downlink power congestion so that user experience of users groups with higher QoS requirements is guaranteed.
Lightweight User Experience Evaluation
The NIUa/ENIUa/EGPUb board must be configured.

In general network congestion scenarios, network KPIs such as the access success rate do not deteriorate much. However, some special scenarios, for example, large gatherings, sports events, or festivals, the traffic
volume increases sharply and the network is severely congested, causing a substantial decrease in the access success rate. Some important UEs may fail to access the network. For example, policemen can hardly
make calls and the CS/PS call completion success rate is lower than 70%. Under this circumstance, you need to ensure that platinum users preferentially access the network with the QoE quality guaranteed.

This solution provides service experience assurance for certain personnel such as platinum users, including preferential access to wireless networks during congestion, improving downlink voice quality of
platinum users in weak coverage, and providing higher HSPA service throughput for platinum users.

This solution ensures the service experience of users such as platinum users. Figure 3-1 illustrates the working mechanism.
Figure 3-1 Experience assurance of platinum users
The procedure for ensuring the experience of platinum uses is as follows:
1. Identify and maintain platinum users.

Operators run the ADD UPLATINUMIMSI command to configure an IMSI list for platinum users on the RNC and use the RRC Connection Request, Common ID, and NAS (Non-Access Stratum)
messages to maintain the IMSI-to-TMSI mapping relationship table. If the RNC receives an RRC Connection Request message and the message carries a TMSI/IMSI identifier, the RNC can identify
platinum users by checking the IMSI-to-TMSI mapping relationship table and label the platinum users. If the message carries a P-TMSI, the RNC identifies this UE as a non-platinum user.
NOTE:
For details about how to identify a platinum user, see Platinum User Prioritizing Feature Parameter Description.
2. In the paging stage, platinum users take precedence over other users.
When the paging channel is congested, platinum users can preempt resources of other users to ensure a higher CS and PS paging success rate.
3. In the RRC setup stage, platinum users take precedence over other users.
During the flow control in the RRC setup stage, the priority of all services for platinum users is increased to the same level as conversational services so that they can access the network preferentially (in
all services, excluding emergent calls, the priority of conversational services is the highest). In the RRC setup stage, platinum users can unconditionally preempt resources of other users to obtain a
higher RRC connection setup success rate.
4. In the RAB setup stage, platinum users take precedence over other users.
In the RAB setup stage, platinum users can unconditionally preempt resources of other users to obtain a higher RAB setup success rate.
5. The following measures are taken to improve the experience of platinum users when services are ongoing.
QoE assurance for platinum users
Basic QoE assurance for platinum users
Increase the maximum downlink transmit power of conversational services for platinum users to improve the voice quality of platinum users in weak downlink coverage areas.
Set the initial SPI weight of platinum users to 100% so that platinum users can be preferentially scheduled when SPI weights are configured to different values for different types of users. If the
SPI weight for other users (for example: gold users) is also set to 100%, these users have the same scheduling priority as platinum users.
Enhanced QoE assurance for platinum CS users
This function improves the experience of platinum CS users by means such as restricting common PS users from accessing platinum CS cells, and limiting the downlink rate and increasing the
BLER of common PS BE users in platinum CS cells.
State transition policies for platinum users
Flexible state transition policies can be configured for platinum users based on their international mobile subscriber identities (IMSIs) in order to accommodate the state transition requirements
of different platinum users.

Table 3-2 lists the features involved in the solution of providing differentiated experience for special users.
Table 3-2 Features involved in the solution of providing differentiated experience for special users
Platinum User Prioritizing WRFD-150204 Platinum User Prioritizing RAN15.0 Platinum User Prioritizing Feature Parameter Description

The WRFD-150204 Platinum User Prioritizing feature is used to guarantee access of platinum users and provide QoE assurance to a certain degree in congestion scenarios. This feature identifies platinum users
and ensures preferential RRC setup and RAB setup. It also ensures platinum users' service quality when the services are ongoing. The Platinum User Prioritizing feature is introduced in RAN17.1, including CS
voice quality enhancement, paging prioritizing during the paging phase, scheduling prioritizing on FACH, and flexible state transition policies.
For details, see Platinum User Prioritizing Feature Parameter Description.
Suggestions on deployment of different features and functions are as follows:
WRFD-150204 Platinum User Prioritizing

This feature must be enabled, because it provides basic functions.
If both the WRFD-020806 Differentiated Service Based on SPI Weight and WRFD-150204 Platinum User Prioritizing features are enabled, the QoS-related rates of platinum users such as GBR and HBR
are set based on the ARP of these users. If a platinum user is also a copper user, the admission and scheduling algorithms use GBR and HBR configured for the copper user, whereas the RRC admission
and RAB admission processes use parameters configured for the platinum user, including the SPI weight.
If the WRFD-150233 Differentiated Service Based on Resource Reservation feature is enabled, platinum users are not subject to the restriction on reserved resources.
If the WRFD-150255 Differentiated Service Based on Terminal feature is enabled, the SPI weight configured based on terminals does not take effect for platinum users. Instead, the SPI weight specified
by the WRFD-150204 Platinum User Prioritizing feature for platinum users takes effect.
If the WRFD-140205 Voice Experience Improvement for Weak Reception UEs feature is enabled, the downlink transmit power of voice services is the value of the formula: max {The 3 dB increase in the
transmit power of platinum users, The increase in the transmit power of special users (dB)}

Operators want to provide HSPA services of different quality for different types of terminals (distinguished by IMEI TAC). The scenario is divided into the following types:
Limiting resources that can be used by low-valued terminals: In congested networks (for definitions of network congestion, see 3.1.1 Scenario Description), there are many low-valued terminals such as
data cards, which occupy a huge amount of radio resources but provide limited revenues to operators and they are less sensitive to user experience. These low-valued terminals can be set to low-priority
UEs and some other terminals can be set to high-priority UEs to control radio resource utilization.
Fixing the priorities of special terminals: The UEs that use some types of terminals (such as terminals customized for an operator) are always set to high- or low-priority users so that differentiated HSPA
services are provided when the network is congested. For definitions of network congestion, see 3.1.1 Scenario Description.

This solution is used to evaluate service experience of different types of terminals and to provide differentiated HSPA services during congestion.

Evaluation of service experience for different types of terminals
RAN17.1 provides KPIs for evaluating the service experience of users belonging to different IMEI TAC groups. For details, see Service Awareness-based Experience Management Feature Parameter
Description and Differentiated HSPA Service Feature Parameter Description.
Service experience differentiation for different types of terminals

If the operator wants to provide differentiated services for all UEs that use certain types of terminals (distinguished by IMEI TAC), the following measures can be taken: Enable WRFD-150255
Differentiated Service Based on Terminal, configure different types of terminals in different terminal groups based on their IMEI_TACs, and set different SPI weights of BE services for UEs in different
terminal groups. With these measures, the HSPA resource scheduling algorithm will adjust the opportunities for different types of terminals to obtain resources, thereby changing the quality of services
provided for the UEs.
If the operator wants to improve experience of a certain type of terminals with the same IMEI TAC (for example, gold users), the Open QoS platform can be used to provide QoS customization. The Open
QoS platform is provided through the SmartCare SQI-Data professional service.

Table 3-3 lists the features involved in the solution of differentiated user experience management for different terminals.
Table 3-3 Features involved in the solution of differentiated user experience management for different terminals
Service experience differentiation for WRFD-150255 Differentiated Service Based on SPI Weight RAN15.0 Differentiated HSPA Service Feature Parameter
different types of terminals Description
Service experience differentiation for N/A Open QoS Platform RAN15.0 Service Awareness-based Experience Management
different types of terminals Feature Parameter Description
Evaluation of service experience for N/A Lightweight User Experience Evaluation RAN16.0 Service Awareness-based Experience Management
different types of terminals Feature Parameter Description
Differentiated HSPA Service Feature Parameter
Description
WRFD-150255 Differentiated Service Based on Terminal

It is used to set different SPI weights for different types of terminals and provide differentiated HSPA services.
Open QoS Platform

It supports fast QoS customization. This platform supports differentiated QoS customization based on the user priority, terminal type, and data service type to improve service experience.
This function is provided by the SmartCare SQI-Data professional service.
The Open QoS platform is mainly used for SmartCare SQI-Data professional services. It provides comprehensive QoS differentiation based on user priority, terminal model, and data service type.
When both Open QoS Platform and WRFD-020806 Differentiated Service Based on SPI Weight are enabled, run the SET UQOSALGOPARA command and set SPI weights for different terminal
groups, which are distinguished by UserMatchPriority(BSC6900,BSC6910) or for different users (gold, silver, and copper).

In existing networks, some certain types of terminals have performance problems. For example, these terminals may experience call setup failures or call drops due to weak reception capabilities.

This solution aims to solve the following problems:
Some UEs experience poor voice quality due to weak reception capabilityand compatibility issues. A UE blacklist is configured to avoid problems caused by special users and improve the user experience
of UEs with compatibility issues.
Abnormal terminals
The function of automatic detection of abnormal terminals is used to identify different terminals by TAC. It also measures the corresponding KPIs to identify abnormal terminals. In addition, the feature
provides a blacklist of terminals that may be abnormal to avoid terminal compatibility issues.

Voice Experience Improvement for Weak Reception UEs
For CS voice services, WRFD-140205 Voice Experience Improvement for Weak Reception UEs enables the RNC to perform a new International Mobile Station Equipment Identity (IMEI) acquisition
procedure. During this procedure, the RNC detects the IMEI Type Allocation Code (TAC) and determines the UE type. If the UE is a weak reception UE, the RNC configures dedicated power control and
handover parameters for the UE. Based on the parameter settings, the weak reception UE obtains a high downlink power control threshold in weak coverage areas and performs handovers at the
designated threshold. For details, see Voice Service Experience Improvement for Weak Reception UEs Feature Parameter Description.
Terminal Black List

The radio network controller (RNC) obtains the list of UEs that are involved in feature incompatibilities based on actual conditions on the live network. This is known as the UE blacklist. The UE
blacklist is preconfigured on the RNC through parameter configuration, and the IMEI TACs of these UEs as well as incompatible features are listed. When a UE accesses the network, the RNC obtains the
IMEI from the IMEI identification procedure. Alternatively, the RNC simulates the core network (CN) mechanism and sends an IDENTITY REQUEST message to the UE, which then reports its IMEI to
the RNC. If the reported IMEI TAC is the same as one in the UE blacklist, the incompatible features will not take effect for the UE. Consequently, issues related to UE incompatibility do not occur, and
service setup failures or call drops are prevented.
Automatic detection and optimization for abnormal terminals
With the feature Automatic Detection and Optimization for Abnormal Terminals, the RNC first checks whether UE's KPIs are abnormal, and then identifies abnormal UEs with the same TAC and
measures their KPIs by day, such as the CS RAB setup success rate, PS RAB setup success rate, CS+PS setup success rate, CS call drop rate, PS call drop rate, CS call drop rate during CS+PS combined
services, CS paging success rate by UEs in CELL_PCH state, D2P state transition success rate, P2D state transition success rate, and D2F state transition success rate. If the KPIs that are validly measured
for UEs of the same TAC (these UEs are also referred to as TAC UEs hereinafter) are lower than specified thresholds, these UEs are identified as abnormal UEs. Then, the RNC analyzes the data of these
UEs collected in both current and historical measurement periods and outputs analysis results.
After the causes and incompatible features are determined, the OM personnel configure parameters for the Terminal Black List feature based on the UE type and feature ID and preconfigure a blacklist on
the RNC side. When a UE accesses the network, the RNC obtains the IMEI of the UE. If the obtained IMEI TAC is the same as one in the UE blacklist, the incompatible features will not take effect for
the UE. Consequently, issues caused by UE compatibility do not occur, such as service setup failures or call drops.
The feature Automatic Detection and Optimization for Abnormal Terminals cannot be used to identify the abnormal UEs that have problems other than the exceptions in the following KPIs: service setup
success rate, call drop rate, CS paging success rate by UEs in CELL_PCH state, D2P state transition success rate, P2D state transition success rate, and D2F state transition success rate.

Table 3-4 lists the features involved in the solution of providing differentiated experience for special terminals.
Table 3-4 Features involved in the solution of providing differentiated experience for special terminals
Special UE Experience WRFD-140205 Voice Experience Improvement for Weak Reception UEs RAN14.0 Voice Service Experience Improvement for Weak Reception UEs Feature
Improvement Parameter Description
Special UE Experience WRFD-160103 Terminal Black List RAN16.0 Terminal Black List Feature Parameter Description
Improvement
Special UE Experience WRFD-171107 Automatic Detection and Optimization for Abnormal RAN17.1 Terminal Black List Feature Parameter Description
Improvement Terminals
WRFD-140205 Voice Experience Improvement for Weak Reception UEs

If some terminals have weak reception capabilities, consider using this feature to increase the maximum downlink transmit power for voice services and reduce the call drop rate.
WRFD-160103 Terminal Black List
In commercial networks, some terminals may be not able to support some features that have been activated due to design or hardware problems of the terminals. In this circumstance, it is recommended
that this feature be enabled to identify problematic terminals according to the terminal black list and prohibit these terminals from using specific features. This mechanism reduces impacts caused by
special terminals' incompatibility with some features.
WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals
This feature automatically identifies different terminals by TAC. It also measures the corresponding KPIs to identify abnormal terminals. In addition, the feature provides a blacklist of terminals that may
be abnormal to avoid terminal compatibility issues.
The deployment and activation of each feature or function will not be described in this document and will be included in the corresponding documents about RAN features.
The WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals enables the RNC to automatically identify and detect abnormal UEs and propose suggestions on analyzing and handling UE
compatibility issues. After the causes and incompatible features are determined, the WRFD-160103 Terminal Black List feature can be enabled to prevent the impact of the compatibility issues, thereby improving
user experience and network performance.
Voice Experience Improvement for Weak Reception UEs, Terminal Black List, and Automatic Detection and Optimization for Abnormal Terminals can be used separately and simultaneously.
WRFD-010505 Queuing and Pre-Emption RAN5.0 Load Control Feature Parameter Description
WRFD-020806 Differentiated Service Based on SPI Weight RAN11.0 Differentiated HSPA Service Feature Parameter Description
WRFD-150233 Differentiated Service Based on Resource Reservation RAN15.0 Differentiated Service Based on Resource Reservation Feature Parameter Description
WRFD-150204 Platinum User Prioritizing RAN15.0 Platinum User Prioritizing Feature Parameter Description
WRFD-140205 Voice Experience Improvement for Weak Reception RAN14.0 Voice Service Experience Improvement for Weak Reception UEs Feature Parameter
UEs Description
WRFD-150255 Differentiated Service Based on Terminal RAN15.0 Differentiated HSPA Service Feature Parameter Description
WRFD-160103 Terminal Black List RAN16.0 Terminal Black List Feature Parameter Description
WRFD-171107 Automatic Detection and Optimization for Abnormal RAN17.1 Terminal Black List Feature Parameter Description
Terminals
QoE Quality of experience
TCP Transmitted Carrier Power
SPI Scheduling Priority Indicator

1. QoS Management Feature Parameter Description

2. Load Control Feature Parameter Description
3. Differentiated HSPA Service Feature Parameter Description
4. Differentiated Service Based on Resource Reservation Feature Parameter Description
5. Platinum User Prioritizing Feature Parameter Description
6. Voice Service Experience Improvement for Weak Reception UEs Feature Parameter Description
7. Terminal Black List Feature Parameter Description
1.3 Radio and Performance

UMTS Big Event Solution
UMTS Combined Service KPI Improvement Solution
UMTS Downlink Throughput Improvement Solution
UMTS Network KPI Improvement Solution
UMTS Signaling Storm Solution
UMTS Small Data Packet Storm Solution
UMTS Uplink Throughput Improvement Solution
UMTS Wide Coverage Solution

WCDMA RAN
UMTS Big Event Solution Guide
Issue 01
Date 2016-02-29

Notice

1.3.1 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Unplanned Big Events
3.1.3.1 List of Features and Functions Involved in the Solution
3.1.3.2 Description of Features and Functions Involved in the Solution
3.2 Planned Big Events
4 List of Features and Functions Involved in the Solution
1.1 Scope
1.3 Change History

1.1 Scope
This document describes the UMTS big event solution for different application scenarios.

Need to understand the UMTS big event solution

1.3 Change History

RAN18.1 01 (2016-02-29)
This issue is the first commercial release of RAN18.1.
RAN18.1 Draft A (2015-12-30)

Compared with Issue 02 (2014-10-15) of RAN16.0, Draft A (2015-12-30) of RAN18.1 includes the following changes:
Introduced the Automatic Congestion Handler (Phase 2) feature in 3.1 Unplanned Big Events.
2 Solution Overview
2.1 Background
2.1 Background
As 3rd Generation (3G) networks develop, especially the rapid popularization of smartphones, big events featuring heavy traffic occur frequently. Big events, such as large gatherings, major sporting events, and
holiday celebrations, often result in a significant increase in traffic volume in certain areas. Under extreme conditions, network congestion is abrupt and user experience sharply deteriorates.
The following examples show a significant increase in traffic volume during big events:
During the opening ceremony of the 2008 Beijing Olympic Games, the number of users doubled, the busy hour call attempts (BHCA) increased by 40%, and the traffic volume increased by 170%,
compared with that in normal conditions.
During the annual Hajj in Saudi Arabia, the number of users in the ten square kilometer area around Mecca hit 2 million, the standard peak BHCA under a mobile switching center (MSC) was 38 times
that of a normal period, and the number of short messages sent per hour reached 4 million during busy hours, which is 32 times that of a normal period.
During the annual Munich Oktoberfest in Germany, nearly 7 million visitors gathered in the area of 0.42 square kilometer area around Munich. Both voice and data traffic volume reached 2 to 3 times that
of a normal period.
To cope with such big events, adequate hardware capacity must be planned before the events. Most importantly, a solution covering networking policies and feature combinations needs to be provided to ensure
normal network operation during big events.
The Huawei UMTS big event solution is introduced to guarantee user services and ensure reliable and stable network operation during big events.
Big events can be classified into the following two types:
Unplanned big events: Traffic volume cannot be predicted, such as during mass demonstrations, marches, and natural disasters.
Planned big events: Traffic volume can be predicted, such as during major sporting events and holiday celebrations.

Huawei provides different solutions to cope with unplanned big events and planned big events.
Using the following functions for unplanned big events

System stability enhancement
User differentiation
Scenario identification and adaptive optimization
Capacity improvement
Using Huawei professional services for planned big events
This chapter describes the solution application guidelines for unplanned and planned big events.

During unplanned big events where the traffic volume cannot be predicted, hardware capacity expansion or parameter adjustments cannot be performed in advance.
An unplanned big event is underway if any of the following conditions applies within the 30-minute measurement period:
The value of the VS.CellDCHUEs(BSC6900,BSC6910) counter indicating the number of DCH UEs in a cell is greater than 55.
The downlink non-HSPA power load factor is higher than 80%, which can be calculated using the following formula:
Downlink non-HSPA power load factor = 10(VS.MeanTCP.NonHS/10) / 10(MaxTxPower/100)
The value of the VS.RRC.AttConnEstab.Sum(BSC6900,BSC6910) counter indicating the number of RRC connection setups in a cell is greater than 3600.
The value of the VS.AttCellUpdt(BSC6900,BSC6910) counter indicating the number of cell updates is greater than 5400.

The UMTS big event solution enables the RNC to automatically identify big events, adaptively adjust network configurations, and then achieve the largest network capacity possible while ensuring optimal KPIs.
When the traffic volume returns to normal, the system adaptively restores the original network configurations.

Huawei provides the following functions to cope with unplanned big events.
System stability enhancement
When the system is severely loaded with excessive traffic volume, the UMTS big event solution takes the following measures to reduce the impact of traffic bursts on the system, thereby ensuring system
stability:
Confining UEs in the CELL_FACH state
Discarding some low-priority services
Preventing some UEs from setting up RRC connections
User differentiation
User differentiation is implemented as follows:
VIP user prioritizing
The quality of service (QoS) of VIP users is preferentially guaranteed in the event of network congestion.
CS service guarantee during big events
CS services take preference over PS services during big events.
PS service differentiation during big events
PS services are differentiated during big events.
Scenario identification and adaptive optimization
The UMTS big event solution achieves the largest cell capacity possible while ensuring optimal network KPIs in different network load states by:
Determining the current load status based on the uplink and downlink loads and the number of users in connected mode.
Triggering load status-based parameter optimization actions to alleviate network congestion.
Capacity improvement
During big events, the UMTS big event solution temporarily reduces the QoS according to a predefined profile to maximize system capacity. For details about capacity improvement solutions, see UMTS
Uplink Throughput Improvement Solution, UMTS Downlink Throughput Improvement Solution, and UMTS Small Data Packet Storm Solution.

Function Type Feature ID Feature Name Introduced in … Reference Document
System stability WRFD-140213 Intelligent Access Class Control RAN14.0 Intelligent Access Class Control Feature Parameter Description
enhancement
WRFD-020114 Domain Specific Access Control (DSAC) RAN11.0 Domain Specific Access Control Feature Parameter Description
N/A E2E Flow Control RAN13.0 E2E Flow Control Feature Parameter Description
WRFD-160206 RB parking RAN16.0 RB Parking Feature Parameter Description
User differentiation WRFD-150204 Platinum User Prioritizing RAN15.0 Platinum User Prioritizing Feature Parameter Description
Scenario identification WRFD-160253 Automatic Congestion Handler RAN16.0 Automatic Congestion Handler Feature Parameter Description
and adaptive optimization
WRFD-151203 Camping Strategy Switch for Mass Event RAN16.0 Camping Strategy Switch for Mass Event Feature Parameter
Description
WRFD-181210 Automatic Congestion Handler (Phase 2) RAN18.1 Automatic Congestion Handler Feature Parameter Description

WRFD-140213 Intelligent Access Class Control This feature uses access class control to prevent a large number of UEs from sending RRC connection setup requests simultaneously.
After determining that a cell is congested, the RNC restricts the access of UEs of more access classes.
After determining that congestion is relieved in the cell, the RNC decreases the number of access classes on which access control is
performed.
WRFD-020114 Domain Specific Access Control When the RNC knows through the Iu interface that the CN is overloaded, the RNC restricts the access classes of certain UEs to prevent these
(DSAC) UEs from accessing the cell.
N/A E2E Flow Control E2E Flow Control protects network elements (NEs) in a RAN from being overloaded. The NEs that participate in flow control are RNCs and
NodeBs. This feature involves the following functions:
NodeB CPU-load-based E2E flow control phase 1 and phase 2
E2E Flow Control Based on Power Congestion This function is intended to reduce the probability of downlink power congestion. In
addition, it ensures that high-priority real-time services (including conversational and streaming services) are preferentially processed.
WRFD-160206 RB parking This feature allows smartphones to enter the parking state after being rejected access to a congested network, which prevents a large number of
repetitive access attempts from undermining network stability.
WRFD-150204 Platinum User Prioritizing This feature improves user experience for platinum users by:
Allocating a high admission priority to users when network congestion occurs.
Allocating the higher High Speed Packet Access (HSPA) throughput to users.
Enhancing voice quality for users when downlink coverage is weak.
WRFD-020806 Differentiated Service Based on SPI When the air interface resources are insufficient, services with larger SPI weights can reach higher rates or have shorter transmission delay than
Weight services with smaller SPI weights.
WRFD-160253 Automatic Congestion Handler This feature monitors network congestion in real time. If network congestion occurs, this feature automatically activates existing congestion
relief algorithms or adjusts the settings of existing network configuration parameters (such as N300, T300, and the wait time) to relieve network
congestion and improve system stability.
WRFD-151203 Camping Strategy Switch for Mass On multi-carrier networks enabled with the preferred camping strategy, a sharp traffic increase generally leads to access congestion in
Event preferentially camped cells and causes KPIs to deteriorate. To alleviate access congestion and increase the RRC connection setup success rate,
this feature detects access congestion and changes the network camping strategy from preferred camping to random camping.
WRFD-181210 Automatic Congestion Handler This feature monitors network congestion in real time. If the network is congested, this feature helps network congestion and improve network
(Phase 2) performance by enabling the following related functions or features:
SIB7 protection
RRC signaling duration optimization
RB Parking
Dynamic Configuration of HSDPA CQI Feedback Period
Features related to system stability enhancement, user differentiation, and scenario identification and adaptive optimization do not mutually exclude or affect each other. A network that has experienced big events
can have these features enabled to ensure system stability and user differentiation during the incoming big events.
For details about the deployment of each feature, see the related feature parameter description documentation.
System Stability Enhancement
Feature ID Feature Name
WRFD-140213 Intelligent Access Class Control
WRFD-020114 Domain Specific Access Control (DSAC)
NA E2E Flow Control
WRFD-160206 RB parking
Before deploying WRFD-140213 Intelligent Access Class Control and WRFD-020114 Domain Specific Access Control, check whether the ACs of SIM cards are randomly distributed. If all SIM cards released by
an operator belong to a certain AC, you are not advised to use the two features. Otherwise, all users of this operator will be barred from accessing the network. If ACs are randomly distributed, all features listed in
the preceding table can be deployed. These features take effect at different time points:
When a cell becomes congested, the RB Parking feature preferentially takes effect, which increases the RAB setup success rate.
If the number of RRC connection setup requests in the cell continues to increase and the rejection rate of RRC connection setup requests is greater than or equal to the value of the CongRejTrigThd
parameter, the Intelligent Access Class Control feature takes effect. After both the Intelligent Access Class Control and Domain Specific Access Control features take effect, the number of RRC
connection setup requests in the cell decreases and the RRC connection setup success rate increases.
If the CPU becomes overloaded due to the increasing number of RRC connection setup requests, flow control measures take effect to maintain a stable CPU usage.
User Differentiation
The two features can be deployed at the same time.
NOTE:
After the Intelligent Access Class Control and Domain Specific Access Control features are enabled, UEs whose ACs ranging from 0 to 9 are barred from accessing the cell in rotation. As a result, the experience of platinum users whose ACs ranging from
0 to 9 is also affected. However, platinum users are still preferentially admitted after the restriction on their ACs is lifted.
Scenario Identification and Adaptive Optimization
WRFD-160253 Automatic Congestion Handler
WRFD-151203 Camping Strategy Switch for Mass Event
WRFD-181210 Automatic Congestion Handler (Phase 2)
WRFD-151203 Camping Strategy Switch for Mass Event requires that the live network uses the preferred camping strategy. If the random camping strategy is used on the live network, this feature does not need to
be deployed. For details, see Camping Strategy Switch for Mass Event Feature Parameter Description.

During big events where the traffic volume can be predicted, for example, hotspot areas or crowded stadiums, plans to cope with heavy traffic (such as hardware capacity expansion) can be made in advance.
You can perform network prediction with the assistance of Huawei technical support. If the network prediction results meet the conditions described in 3.1.1 Scenario Description, a planned big event is underway.

The UMTS big event solution optimizes basic KPIs while ensuring system stability, for example, reducing the number of CS and PS service drops, and increasing the uplink and downlink throughput in a cell.

Huawei has extensive experience in coping with planned events and festivals such as the Hajj, World Cup, and New Year's Eve. Therefore, you are advised to cope with planned big events by purchasing Huawei
1. Before the occurrence of big events, Huawei performs hardware checks, and parameter adjustment and optimization.
Hardware check: Detects device problems in the live network and performs hardware capacity expansion and adjustment to get ready for the incoming big events.
Parameter adjustment and optimization: Guarantees the access of CS services, reduces the load on devices, and mitigates the impact of resource congestion on services. Parameter adjustment and
optimization apply to all sites that will experience big events and have no negative gains for non-hotspot areas.
The following table lists features recommended for planned big events.
WRFD-160206 RB parking
WRFD-160253 Automatic Congestion Handler
WRFD-181210 Automatic Congestion Handler (Phase 2)
2. In the progress of big events, Huawei keeps the KPIs in check and adjusts related parameters based on load states in a timely manner.
Reducing cell pilot power Reduces cell pilot power to narrow down the cell coverage scope. In this way, some users are transferred to cells under other NodeBs.
This solution applies to cells with imbalanced traffic.
2G and 3G traffic sharing Adjusts parameters related to camping and reselection to transfer 3G traffic to 2G, thereby relieving 3G network congestion.
Cell-level dynamic CAPS flow control Reduces the number of RRC connection setup requests admitted to a cell per second.
Blocking the PS domain Restricts the access of users processing PS services.
3. After big events are complete, Huawei restores the configurations of adjusted parameters.
You are advised to cope with planned big events by purchasing Huawei professional services.
For details about the deployment of each feature, see the related feature parameter description.
Feature ID Feature Name Introduced in… Reference Document
WRFD-140213 Intelligent Access Class Control RAN14.0 Intelligent Access Class Control Feature Parameter Description
WRFD-020114 Domain Specific Access Control (DSAC) RAN11.0 Domain Specific Access Control Feature Parameter Description
NA E2E Flow Control RAN13.0 E2E Flow Control Feature Parameter Description
WRFD-160206 RB parking RAN16.0 RB Parking Feature Parameter Description
WRFD-150204 Platinum User Prioritizing RAN15.0 Platinum User Prioritizing Feature Parameter Description
WRFD-160253 Automatic Congestion Handler RAN16.0 Automatic Congestion Handler Feature Parameter Description
WRFD-151203 Camping Strategy Switch for Mass Event RAN16.0 Camping Strategy Switch for Mass Event Feature Parameter Description
WRFD-181210 Automatic Congestion Handler (Phase 2) RAN18.1 Automatic Congestion Handler Feature Parameter Description
BHCA busy hour call attempts
HSPA High Speed Packet Access
KPI key performance indicator
QoS quality of service
1. Camping Strategy Switch for Mass Event Feature Parameter Description

2. Automatic Congestion Handler Feature Parameter Description
3. Platinum User Prioritizing Feature Parameter Description
4. RB Parking Feature Parameter Description
5. Intelligent Access Class Control Feature Parameter Description
6. Domain Specific Access Control Feature Parameter Description
7. Differentiated HSPA Service Feature Parameter Description
8. E2E Flow Control Feature Parameter Description
9. UMTS Uplink Throughput Improvement Solution
10. UMTS Downlink Throughput Improvement Solution
11. UMTS Small Data Packet Storm Solution
WCDMA RAN
UMTS Combined Service KPI Improvement Solution Guide
Issue 01
Date 2015-04-20

Notice
1.3.2 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Scenario: CS+PS Combined Services
3.1.4.1 Solution 1: Absolute CS Preference
3.1.4.2 Solution 2: Considering the Experience of PS BE Users
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the solution for improving the KPIs for CS+PS combined services.

Need to understand the KPI improvement solution for CS+PS combined services
1.3 Change History

RAN17.1 01 (2015-04-20)
Compared with Issue 01 (2014-05-15) of RAN16.0, 01 (2015-04-20) for RAN17.1 includes the following changes:
Optimized the engineering guidelines for combined service setups in solution 1 and solution 2. For details, see 3.1.4 Implementation.
2 Solution Overview
2.1 Background
2.1 Background
The UMTS combined service KPI improvement solution applies to networks with CS+PS combined services. If the number of RAB setup requests for CS+PS combined services (indicated by the
VS.MultiRAB.AttEstab.CSPS(BSC6900,BSC6910) counter) is greater than 0, this solution can be enabled.
NOTE:
If the proportion of CS+PS combined services in CS services is small, this solution provides minor gains in reducing the CS call drop rate. If CS+PS combined services account for 50% of CS services, this solution provides noticeable gains in reducing the
CS call drop rate.
The proportion of CS+PS combined services in CS services can be calculated using the following formula: VS.MultiRAB.AttEstab.CSPS(BSC6900,BSC6910)/(VS.RAB.AttEstabCS.Conv(BSC6900,BSC6910) +
VS.RAB.AttEstabCS.Str(BSC6900,BSC6910)) x 100%

The UTMS combined service KPI improvement solution applies to networks with a high proportion of CS+PS combined services. This solution is recommended for a network where the proportion of CS+PS
combined services in all CS services is higher than 50%.
The proportion of CS+PS combined services in all CS services can be calculated using the following formula:
VS.MultiRAB.AttEstab.CSPS(BSC6900,BSC6910)/(VS.RAB.AttEstabCS.Conv(BSC6900,BSC6910) + VS.RAB.AttEstabCS.Str(BSC6900,BSC6910)) x 100%

The UMTS combined service KPI improvement solution addresses the high call drop rate of the CS service in CS+PS combined services by using the following features:
WRFD-140104 Enhanced Combined Services

WRFD-021101 Dynamic Channel Configuration Control (DCCC)
WRFD-140103 Call Reestablishment
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period
For details about the functions involved in the Enhanced Combined Services feature, see Enhanced Combined Services Feature Parameter Description.
The main causes why the CS service in CS+PS combined services experiences a higher call drop rate than a single CS service are as follows:
Due to the PS services in CS+PS combined services, the uplink or downlink coverage of CS+PS combined services is worse that of a single CS service.
Signaling interactions specific to PS services in CS+PS combined services increase the call drop rate for the CS service in CS+PS combined services.
Huawei takes a series of measures to reduce the call drop rate for the CS service in CS+PS combined services. As shown in Figure 2-1:
During the setup of CS+PS combined services, this solution sets the bearer channel type and access rate for PS BE services in CS+PS combined services. In addition, this solution addresses problems
caused by concurrent procedures during the setup of the second service in CS+PS combined services.
During the processing of CS+PS combined services, this solution sets the conditions for channel type change and rate increase/decrease for PS BE services.
During the release of CS+PS combined services, this solution checks the PS data transmission state and quickly transits UEs processing PS services to the CELL_FACH state if there is no PS data to
transmit, which saves system resources.
Figure 2-1 Working principle of the UTMS combined service KPI improvement solution
click to enlarge
NOTE:
Figure 2-1 shows an example of CS+1 PS combined services. Unless otherwise specified, the algorithm for CS+ multiple PS combined services is the same as that for CS+ 1 PS combined services.
The UTMS combined service KPI improvement solution can be classified into the following two solutions based on the PS service bearing policy:
Solution 1: Absolute CS preference

During the setup of CS+PS combined services, the PS BE services are carried on the DCH and the access date rate is 0 kbit/s or 8 kbit/s (referred to as DCH0K or DCK8K).
During the processing of CS+PS combined services, channel type change and rate increase cannot be performed for PS BE services.
During the release of CS+PS combined services, UEs processing PS BE services can be quickly transited to the CELL_FACH state if there is no PS BE data to transmit. If PS BE data needs to be
transmitted, the RNC switches UEs to HSPA channels again or configures a higher rate for PS BE data transmission on the DCH.
Solution 2: Considering the experience of PS BE users

During the setup of CS+PS combined services, the bearer channel type and data rate for PS BE service can be set to DCH0K, DCK8K, or DCH8K/HSDPA (DCH8K in the uplink and HSDPA in
the downlink).
During the processing of CS+PS combined services, rate increase and decrease can be performed on PS BE services based on the traffic volume of PS BE services.
During the release of CS+PS combined services, UEs processing PS BE services can be quickly transited to the CELL_FACH state if there is no PS BE data to transmit.
Table 2-1 provides the advantages and disadvantages of the two solutions.
Table 2-1 Advantages and disadvantages of the two solutions
Solution Advantages Disadvantages
Solution 1: Absolute CS preference This solution achieves the lowest call drop rate for the CS service in Few or no data can be transmitted for PS services in CS+PS combined services.
CS+PS combined services.
Solution 2: Considering the experience of PS BE users This solution saves system resources when there is no PS data to transmit. The call drop rate for the CS service in CS+PS combined services is higher than that in
Unlike solution 1, PS data can be transmitted in this solution. solution 1.
The number of call drops can be reduced by using the radio link reestablishment function
during physical channel reconfiguration and RB reconfiguration in the Call Reestablishment
feature. However, this feature introduces an 8s or longer mute voice, which affects the
experience of CS users.
You can choose a solution based on actual network conditions:

Use solution 2 if the Call Reestablishment feature has been activated or will be activated for CS services. This solution adjusts the bearer channel type and access rate for PS BE services based on PS BE
data transmission requirements. Procedure failures caused by the adjustment can be recovered by using the radio link reestablishment function in the Call Reestablishment feature.
If the Call Reestablishment feature is not activated or will be activated for CS services, use solution 1 to achieve the lowest CS call drop rate.

If the value of the VS.MultiRAB.AttEstab.CSPS(BSC6900,BSC6910) counter in a network is greater than 0, there are requirements for CS+PS combined services.

This solution aims to solve the high call drop rate for CS+PS combined services when the proportion of CS+PS combined services is high.

As described in section 2.3 Overall Solution, the UMTS combined service KPI improvement solution provides the following functions during the setup, processing, and release of CS+PS combined services:
During the setup of CS+PS combined services

Setting the bearer channel type and access rate for PS BE services
Solving problems caused by concurrent procedures during the setup of CS+PS combined services
Optimizing the setup of CS+PS combined services
Optimizing the activation time during the setup of CS+PS combined services
Call reestablishment during RB setup
During the processing of CS+PS combined services

Setting conditions for channel type change and rate increase for PS BE services
Optimizing the rate increase and decrease procedures for CS+PS combined services
Cell load-based rate increase for PS BE services in CS+PS combined services
Call reestablishment during physical channel reconfiguration and RB reconfiguration
Optimizing the link reestablishment function
During the release of CS+PS combined services

Fast state transition to CELL_FACH for PS BE UEs after a CS service release if there is no PS BE data to transmit
Optimizing PS service release
Call reestablishment during RB release

Table 3-1 lists the features involved in the UMTS combined service KPI improvement solution.
Table 3-1 Features involved in the UMTS combined service KPI improvement solution
WRFD-140104 Enhanced Combined Services RAN14.0 Enhanced Combined Services Feature Parameter Description
WRFD-021101 Dynamic Channel Configuration Control (DCCC) RAN2.0 DCCC Feature Parameter Description
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback RAN14.0 Dynamic Configuration Based on the Uplink Load Feature Parameter Description
Period (used only for solution 2: Considering the
Experience of PS BE Users)

Table 3-2 provides the description of features involved in the UMTS combined service KPI improvement solution.
Table 3-2 Description of features involved in the UMTS combined service KPI improvement solution
Feature ID Feature Name Feature Description in This Solution
WRFD-140104 Enhanced Combined Services During the setup of CS+PS combined services:
During the processing of CS+PS combined services:
Cell load-based rate increase for PS BE services in CS+PS combined services
During the release of CS+PS combined services:
Fast state transition to CELL_FACH for PS BE UEs after a CS service release if there is no PS BE
data to transmit
Optimizing PS service release
WRFD-021101 Dynamic Channel Configuration Control (DCCC) During the processing of CS+PS combined services:
WRFD-140103 Call Reestablishment During the setup of CS+PS combined services:

call reestablishment during RB setup
During the processing of CS+PS combined services:
call reestablishment during physical channel reconfiguration and RB reconfiguration
During the release of CS+PS combined services:
call reestablishment during RB release
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period (used only During the setup of CS+PS combined services:
for solution 2: Considering the Experience of PS BE Users) setting the bearer channel type and access rate for PS BE services (supporting CQI feedback period
optimization for HSDPA services in an ongoing combined service)
This section describes how to implement the two solutions in the UMTS combined service KPI improvement solution.
3.1.4.1 Solution 1: Absolute CS Preference

This solution combines algorithms involved in the setup, processing, and release of CS+PS combined services.

Two configurations can be used:
Configuration 1: Setting the bearer channel type and access rate for PS BE services to DCH0K and prohibiting rate increase for PS BE services PS BE data cannot be transmitted when this configuration
is used.
If the duration of CS+PS combined services exceeds the heartbeat transmission time between the terminal application and the server, the terminal application is in offline state after the call is terminated.
Run the RNC MML command SET UFRC with BeInitBitrateTypeforCsPs(BSC6900,BSC6910) set to DCH0K. Run the RNC MML command SET UCORRMALGOSWITCH with the
DRA_CSPS_0K_RATE_UP_SWITCH check box under the DraSwitch2(BSC6900,BSC6910) parameter deselected.
Configuration 2: Setting the bearer channel type and access rate for PS BE services to DCH8K and prohibiting rate increase for PS BE services
This setting ensures data transmission for heartbeat packets but cannot ensure PS services such as web browsing, instant message, email, and video services.
Compared with DCH0K, more SF128 code resources are consumed when DCH8K is used. This configuration is recommended if code resources in the network are sufficient.
Run the RNC MML command SET UFRC with BeInitBitrateTypeforCsPs(BSC6900,BSC6910) set to DCH8K, and with both UlDchBeUpperLimitforAmr(BSC6900,BSC6910) and
DlDchBeUpperLimitforAmr(BSC6900,BSC6910) set to D8.
NOTE:
You can also achieve this configuration by running the following command:
Run the RNC MML command SET UCORRMALGOSWITCH with both the MAP_CSPS_PS_UL_USE_DCH_SWITCH and MAP_CSPS_PS_DL_USE_DCH_SWITCH check boxes under the
MapSwitch(BSC6900,BSC6910) parameter selected. Run the RNC MML command SET UFRC with both UlDchBeUpperLimitforAmr(BSC6900,BSC6910) and
DlDchBeUpperLimitforAmr(BSC6900,BSC6910) set to D8.
Set the process optimization switches for the following concurrent procedures to on: concurrence of security mode control and cell updates, and concurrence of CS service setup and F2D state transition
(CELL_FACH to CELL_DCH). Run the RNC MML command SET URRCTRLSWITCH with both the SECU_CU_CROSS_SWITCH and RB_CU_CROSS_COMPATIBLE_SWITCH check
boxes under the OptimizationSwitch2(BSC6900,BSC6910) parameter selected, and with the AMR_F2D_OVERLAP_CELLUPT_SWITCH check box under the
OptimizationSwitch(BSC6900,BSC6910) parameter selected. Run the RNC MML command SET UCORRMPARA with the PERFENH_F2P_LIMIT_WITH_CS_IU_CON_SWITCH check
box under the PerfEnhanceSwitch1(BSC6900,BSC6910) parameter selected.
If a UE in the CELL_FACH state initiates a CS+PS combined service, the Radio Link Control (RLC) mode is changed to the acknowledged mode (AM). Run the RNC MML command SET
URRCTRLSWITCH with the RB_SETUP_F2D_USE_AM_RLC_SWITCH check box under the OptimizationSwitch4(BSC6900,BSC6910) parameter selected.
Set which report to be preferentially processed if intra-frequency measurement report and event 2D/2F report that are received at the same time during the setup of CS+PS combined services. Run the
RNC MML command SET UCORRMALGOSWITCH with the HO_INTRA_FREQ_HIGHPRIOR_2D2F_SWITCH check box under the HoSwitch(BSC6910,BSC6900) parameter selected.
The retransmission rate of signaling packets during the setup of CS+PS combined services and RB reconfiguration is increased to ensure that more complete RB RECFG messages can be received by a
UE. Run the RNC MML command MOD UCELLRLACTTIME with PacketReTransRatio set to 8.
(Optional) PS F2D prior to CS service setup in the CELL_FACH state
Run the RNC MML command SET URRCTRLSWITCH with the CS_TRIG_PS_F2D_SWITCH check box under the OptimizationSwitch6(BSC6900,BSC6910) parameter selected.
This function is optional. After a UE that processes a PS service is switched to the CELL_FACH state, the UE initiates a CS service setup request. In this scenario, the RB setup procedure is more likely to
overlap with the cell update procedure, causing the CS service setup to fail. After this function is enabled, the RNC first switches the PS service to the CELL_DCH state before setting up the CS service.
This reduces the probability of overlapped RB setup and cell update, increasing the CS RAB setup success rate but prolonging the CS service access by about 1s. This function is recommended if you
need to ensure the CS RAB setup success rate but do not worry about a longer access delay.
(Optional) Call reestablishment during RB setup
Run the RNC MML command LST URRCTRLSWITCH to query whether the SRB_RESET_RL_SETUP_SWITCH, RLFAIL_RL_SETUP_SWITCH, and CS_RL_SETUP_SWITCH check
boxes under the OptimizationSwitch(BSC6900,BSC6910) parameter are selected. If they are, run the RNC MML command SET URRCTRLSWITCH with the
RB_SETUP_ENHANCE_RL_REEST_SWITCH check box under the PROCESSSWITCH4(BSC6900,BSC6910) parameter selected.
This function is optional. After this function is enabled, the delay caused by previous failed RB setups prolongs. You can configure this function based on actual network conditions. This function is
recommended if call reestablishment for CS services has been enabled in the network.
The conditions have been set when the RNC sets the bearer channel type and access rate for PS BE services during the setup of CS+PS combined services.
If the call reestablishment function has been enabled for CS services, that is, the CS_RL_SETUP_SWITCH check box under the OptimizationSwitch(BSC6900,BSC6910) parameter has been
selected, run the RNC MML command SET UCORRMPARA with both the PERFENH_RLRESETUP_GUARANTEE_SWITCH and PERFENH_RLRESETUP_PREEMPT_SWITCH check
boxes under the PerfEnhanceSwitch3(BSC6900,BSC6910) parameter selected. In this way, channel fallback and preemption can be initiated if admission fails during the link reestablishment.
After this function is enabled, UEs processing PS BE services do not need to wait for the decision for state transmission if there is no PS BE data to transmit. Instead, the UE can quickly transit to the
CELL_FACH state. Run the RNC MML command SET UCORRMALGOSWITCH with the DRA_PS_STATE_TRANS_WHEN_CS_REL_SWITCH check box under the
DraSwitch2(BSC6900,BSC6910) parameter selected.
(Optional) Optimized PS service release
The RNC does not release PS RABs for inactive UEs after the PS user inactivity timer has expired, which reduces the CS call drops during PS service release. Run the RNC MML command SET
URRCTRLSWITCH with the PS_INACT_NOTREL_FOR_CSPS_SWITCH check box under the PROCESSSWITCH3(BSC6900,BSC6910) parameter selected.
This function is optional. You do not need to configure this function if the PS user inactivity timer (specified by the PsInactTmrForInt(BSC6900,BSC6910) and
PsInactTmrForBac(BSC6900,BSC6910)(RNC level), or PsInactTmrForInt(BSC6900,BSC6910) and PsInactTmrForBac(BSC6900,BSC6910)(cell level) parameter) is set to a value
greater than 600s or the enhanced fast dormancy algorithm is enabled (the FAST_DORMANCY_SWITCH check box under the PROCESSSWITCH(BSC6900,BSC6910) parameter is selected).
If the call reestablishment function has been enabled for CS services, run the RNC MML command LST URRCTRLSWITCH to check whether the SRB_RESET_RL_SETUP_SWITCH,
RLFAIL_RL_SETUP_SWITCH, and CS_RL_SETUP_SWITCH check boxes under the OptimizationSwitch(BSC6900,BSC6910) parameter are selected. If they are, run the RNC MML
command SET URRCTRLSWITCH with the RB_REL_RL_REEST_SWITCH check box under the PROCESSSWITCH4(BSC6900,BSC6910) parameter selected.
3.1.4.2 Solution 2: Considering the Experience of PS BE Users

The RNC adjusts the bearer channel type f PS BE services in real time based on the traffic volume of PS BE services. If PS BE data needs to be transmitted, the RNC reconfigures PS BE services to HSPA
channels. This increases signaling interactions for CS+PS combined services and therefore increases the risk of call drops for the CS service in CS+PS combined services. Before using this solution, you are
advised to enable the call reestablishment feature for CS services. For details about how to enable this feature, see Call Reestablishment Feature Parameter Description.
This solution combines algorithms involved in the setup, processing, and release of CS+PS combined services.
During the setup of CS+PS combined services, the bearer channel type and access rate for PS BE services can be set to DCH0K, DCH8K, or DCH8K/HSDPA. You can also set no limit on the initial rate
for PS BE services. It is recommended that DCH8K be used and the dynamic initiate rate allocation function be enabled for the PS BE services in a CS+PS combined service. It is recommended that the
switch controlling adaptive configuration of initial rate type for PS BE services in combined services be turned on to alleviate the downlink power and code resource congestion caused by the use of
DCH8K.Run the RNC MML command SET UFRC with the BeInitBitrateTypeforCsPs(BSC6900,BSC6910) parameter set to DCH8K. Run the RNC MML command SET UCORRMPARA with
the PERFENH_DYC_INIBITRATE_MULTI_SWITCH check box under the PerfEnhanceSwitch3(BSC6900,BSC6910) parameter selected.Run the RNC MML command SET
UCORRMALGOSWITCH with the DRA_CSPS_BE_INIT_OPT_SWITCH check box under the DraSwitch2(BSC6900,BSC6910) parameter selected.
NOTE:
If the number of CS users in a cell exceeds 40 during busy hours, use DCH0K or DCH8K/HSDPA. If DCH8K/HSDPA is used, set the initial rate for PS BE services to DCH0K if a PS BE UE in the CELL_PCH state needs to initiate a CS
service. Run the RNC MML command SET URRCTRLSWITCH with the CS_SETUP_P2D_SWITCH check box under the OptimizationSwitch(BSC6900,BSC6910) parameter selected. Run the RNC MML command SET
UCORRMPARA with both the PERFENH_P2D_LIMIT_ON_DCH_LOWRATE_SWITCH PERFENH_CS_TRIG_PS_P2D_ZERO_SWITCH check boxes under the PerfEnhanceSwitch1(BSC6900,BSC6910) parameter selected.
Set the process optimization switches for the following concurrent procedures to on: concurrence of security mode control and cell updates, and concurrence of CS service setup and F2D state transition
(CELL_FACH to CELL_DCH). Run the RNC MML command SET URRCTRLSWITCH with both the SECU_CU_CROSS_SWITCH and RB_CU_CROSS_COMPATIBLE_SWITCH check
boxes under the OptimizationSwitch2(BSC6900,BSC6910) parameter selected, and with the AMR_F2D_OVERLAP_CELLUPT_SWITCH check box under the
OptimizationSwitch(BSC6900,BSC6910) parameter selected. Run the RNC MML command SET UCORRMPARA with the PERFENH_F2P_LIMIT_WITH_CS_IU_CON_SWITCH check
box under the PerfEnhanceSwitch1(BSC6900,BSC6910) parameter selected.
If a UE in the CELL_FACH state initiates a CS+PS combined service, the RLC mode is changed to the AM. Run the RNC MML command SET URRCTRLSWITCH with the
RB_SETUP_F2D_USE_AM_RLC_SWITCH check box under the OptimizationSwitch4(BSC6900,BSC6910) parameter selected.
Set which report to be preferentially processed if intra-frequency measurement report and event 2D/2F report that are received at the same time during the setup of CS+PS combined services. Run the
RNC MML command SET UCORRMALGOSWITCH with the HO_INTRA_FREQ_HIGHPRIOR_2D2F_SWITCH check box under the HoSwitch(BSC6900,BSC6910) parameter selected.
The retransmission rate of signaling packets during the setup of CS+PS combined services and RB reconfiguration is increased to ensure that more complete RB RECFG messages can be received by a
UE. Run the RNC MML command MOD UCELLRLACTTIME with PacketReTransRatio(BSC6900,BSC6910) set to 8.
(Optional) PS F2D prior to CS service setup in the CELL_FACH state
Run the RNC MML command SET URRCTRLSWITCH with the CS_TRIG_PS_F2D_SWITCH check box under the OptimizationSwitch6(BSC6900,BSC6910) parameter selected.
This function is optional. After a UE that processes a PS service is switched to the CELL_FACH state, the UE initiates a CS service setup request. In this scenario, the RB setup procedure is more likely to
overlap with the cell update procedure, causing the CS service setup to fail. After this function is enabled, the RNC first switches the PS service to the CELL_DCH state before setting up the CS service.
This reduces the probability of overlapped RB setup and cell update, increasing the CS RAB setup success rate but prolonging the CS service access by about 1s. This function is recommended if you
need to ensure the CS RAB setup success rate but do not worry about a longer access delay.
(Optional) Call reestablishment during RB setup
Run the RNC MML command LST URRCTRLSWITCH to query whether the SRB_RESET_RL_SETUP_SWITCH, RLFAIL_RL_SETUP_SWITCH, and CS_RL_SETUP_SWITCH check
boxes under the OptimizationSwitch(BSC6900,BSC6910) parameter are selected. If yes, run the RNC MML command SET URRCTRLSWITCH with the RB_SETUP_RL_REEST_SWITCH
and RB_SETUP_ENHANCE_RL_REEST_SWITCH check boxes under the PROCESSSWITCH4(BSC6900,BSC6910) parameter selected.
This function is optional. After this function is enabled, the delay caused by previous failed RB setups prolongs. You can configure this function based on actual network conditions. This function is
recommended if call reestablishment for CS services has been enabled in the network.
Set the upper limit of data rate for CS+PS combined services carried on the DCH and set the conditions for rate increase and channel type change.
To set the upper limit of data rate for CS+PS combined services carried on the DCH, run the RNC MML SET UFRC with both the UlDchBeUpperLimitforAmr(BSC6900,BSC6910) and
DlDchBeUpperLimitforAmr(BSC6900,BSC6910) parameters set to D16.
To lift the limit on rate increase and channel type change, run the RNC MML command SET UCORRMALGOSWITCH with the DRA_CSPS_0K_RATE_UP_SWITCH check box under the
DraSwitch2(BSC6900,BSC6910) parameter selected, with both the MAP_CSPS_PS_UL_USE_DCH_SWITCH and MAP_CSPS_PS_DL_USE_DCH_SWITCH check boxes under the
MapSwitch(BSC6900,BSC6910) parameter deselected.
To prohibit periodic channel retry, run the RNC MML command SET UCORRMALGOSWITCH with the DRA_CSPS_NO_PERIOD_RETRY_SWITCH check box under the
DraSwitch(BSC6900,BSC6910) parameter selected. This command does not take effect on traffic volume-based rate increase.
To set the weak coverage threshold for HSPA serving cell change, run the RNC MML command SET UHOCOMM with the WeakCovHSPAQualThds(BSC6900,BSC6910) parameter set to -14.
The upper limit of data rate for CS+PS combined services carried on the DCH must be higher than the 8 kbit/s for service setup so that rate increase can be triggered by event 4A. It is recommended that
the upper limit of data rate be set to 16 kbit/s. If the uplink upper limit of data rate for CS+PS combined services carried on the DCH (UlDchBeUpperLimitforAmr) is set to a large value, CE resource
consumption increases because the amount of CE resources allocated to the DCH is fixed. If the downlink upper limit of data rate for CS+PS combined services carried on the DCH
(DlDchBeUpperLimitforAmr) is set to a large value, more code resources are consumed and the number of call drops increases when the downlink coverage for a CS+PS combined service is 3 dB
worse than a single CS service.
NOTE:
If the uplink external interference is strong or the uplink RTWP is high, use only HSUPA 10 ms TTI for PS services in CS+PS combined services or prohibit CS+PS combined services from using HSUPA channels. If rate increase to HSDPA is
performed in the subsequent procedure, set the CQI for CS+PS combined services to a larger value.
To use only HSUPA 10 ms TTI for PS services in CS+PS combined services,
run the RNC MML command SET UCORRMALGOSWITCH with the MAP _CSPS_TTI_2MS_LIMIT_SWITCH check box under the MapSwitch(BSC6900,BSC6910) parameter selected.
If HSUPA cannot be used for CS+PS combined services:
The uplink rate on the DCH can be increased to 128 kbit/s or higher, which consumes more uplink CE resource because the amount of CE resources allocated to the DCH is fixed. Due to the code resource consumption and coverage differences,
it is recommended that the downlink rate on the DCH be equal to or lower than 16 kbit/s. Run the RNC MML command SET UCORRMALGOSWITCH with the MAP_CSPS_PS_UL_USE_DCH_SWITCH check box under the
MapSwitch(BSC6900,BSC6910) parameter selected. Run the RNC MML command SET UFRC with UlDchBeUpperLimitforAmr(BSC6900,BSC6910) set to D128 and with DlDchBeUpperLimitforAmr(BSC6900,BSC6910) set
to D16.
Set the CQI for CS+PS combined services:
Run the RNC MML command SET UCORRMALGOSWITCH with the PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH check box under the PcSwitch(BSC6900,BSC6910) parameter selected. Then run the RNC MML command
ADD UCELLHSDPCCH with the CQIFBckBaseCsCombServ(BSC6910,BSC6900) parameter set to D20.
Optimize simultaneous uplink and downlink rate increase for CS+PS combined services and support channel fallback for the HSPA services in CS+PS combined services. It is recommended that the
switch controlling adaptive configuration of low-activity rate be turned on to alleviate the downlink power and code resource congestion caused by the use of DCH8K.
Run the RNC MML command SET UCORRMALGOSWITCH with the DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH check box under the DraSwitch2(BSC6900,BSC6910) parameter
selected.
Run the RNC MML command SET UDCCC with LittleRateChlFlBkForCSPS(BSC6900,BSC6910) set to HSPA_FALLBACK and with LittleRateThd(BSC6900,BSC6910) set to D8.
Run the RNC MML command SET UCORRMALGOSWITCH with the DRA_BE_LITTLE_RATE_OPT_SWITCH check box under the DraSwitch2(BSC6900,BSC6910) parameter selected.
(Optional) Cell load-based rate increase for PS BE services
Rate increase is allowed only when the uplink and downlink cell loads are lower than a threshold. Run the RNC MML command SET UCORRMPARA with the
PERFENH_CSPS_NO_RATEUP_IN_CONJ_SWITCH check box under the PerfEnhanceSwitch1(BSC6900,BSC6910) parameter selected. The decision thresholds for cell uplink and downlink
loads can be set by the following parameters: MultiRabUlDcccLoadFactor(BSC6900,BSC6910), MultiRabDlDcccLoadFactor(BSC6900,BSC6910), UlLdrTrigThd(BSC6900,BSC6910)
and DlLdrTrigThd(BSC6900,BSC6910). The default values are recommended.
This function is optional. If the cell load exceeds a threshold, rate increase cannot be performed for PS BE services in CS+PS combined services and the remaining resources in the cell are allocated to
services other than CS+PS combined services. If PS BE services are carried on DCH8K, PS BE data cannot be transmitted and the experience of PS BE UEs is affected. Set this function based on actual
network conditions.
Call reestablishment during physical channel reconfiguration and RB reconfiguration
If the call reestablishment function has been enabled for CS services, run the RNC MML command LST URRCTRLSWITCH to query whether the SRB_RESET_RL_SETUP_SWITCH,
RLFAIL_RL_SETUP_SWITCH, and CS_RL_SETUP_SWITCH check boxes under the OptimizationSwitch(BSC6900,BSC6910) parameter are selected. If yes, run the RNC MML command
SET URRCTRLSWITCH with the PHY_RECFG_REEST_SWITCH, PHYCHRECFG_ENH_RL_REEST_SWITCH, and RBRECFG_ENH_RL_REEST_SWITCH check boxes under the
PROCESSSWITCH4(BSC6900,BSC6910) parameter selected, with the RB_RECFG_RL_REEST_SWITCH check box under the OptimizationSwitch(BSC6900,BSC6910) parameter
selected, and with the NON_DCCC_RBRECFG_RL_REEST_SWITCH check box under the ImprovementSwitch(BSC6900,BSC6910) parameter selected.
If the call reestablishment function has been enabled for CS services, that is, the CS_RL_SETUP_SWITCH check box under the OptimizationSwitch(BSC6900,BSC6910) parameter has been
selected, run the RNC MML command SET UCORRMPARA with both the PERFENH_RLRESETUP_GUARANTEE_SWITCH and PERFENH_RLRESETUP_PREEMPT_SWITCH check
boxes under the PerfEnhanceSwitch3(BSC6900,BSC6910) parameter selected. In this way, channel fallback and preemption can be initiated if admission fails during the link reestablishment.
After this function is enabled, UEs processing PS BE services do not need to wait for the decision for state transmission if there is no PS BE data to transmit. Instead, the UE can quickly transit to the
CELL_FACH state. Run the RNC MML command SET UCORRMALGOSWITCH with the DRA_PS_STATE_TRANS_WHEN_CS_REL_SWITCH check box under the
DraSwitch2(BSC6900,BSC6910) parameter selected.
(Optional) Optimized PS service release
The RNC does not release PS RABs for inactive UEs after the PS user inactivity timer has expired, which reduces the CS call drops during PS service release. Run the RNC MML command SET
URRCTRLSWITCH with the PS_INACT_NOTREL_FOR_CSPS_SWITCH check box under the PROCESSSWITCH3(BSC6900,BSC6910) parameter selected.
This function is optional. You do not need to configure this function if the PS user inactivity timer (specified by the PsInactTmrForInt(BSC6900,BSC6910) and
PsInactTmrForBac(BSC6900,BSC6910)(RNC level), or PsInactTmrForInt(BSC6900,BSC6910) and PsInactTmrForBac(BSC6900,BSC6910)(cell level) parameter) is set to a value
greater than 600s or the enhanced fast dormancy algorithm is enabled (the FAST_DORMANCY_SWITCH check box under the PROCESSSWITCH(BSC6900,BSC6910) parameter is selected).
If the call reestablishment function has been enabled for CS services, run the RNC MML command LST URRCTRLSWITCH to check whether the SRB_RESET_RL_SETUP_SWITCH,
RLFAIL_RL_SETUP_SWITCH, and CS_RL_SETUP_SWITCH check boxes under the OptimizationSwitch(BSC6900,BSC6910) parameter are selected. If they are, run the RNC MML
command SET URRCTRLSWITCH with the RB_REL_RL_REEST_SWITCH check box under the PROCESSSWITCH4(BSC6900,BSC6910) parameter selected.

WRFD-021101 Dynamic Channel Configuration Control (DCCC) RAN2.0 DCCC Feature Parameter Description
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback RAN14.0 Dynamic Configuration Based on the Uplink Load Feature Parameter Description
Period
(used only for solution 2: Considering the
Experience of PS BE Users)
AM acknowledged mode
BE best effort
CQI channel quality indicator
DCCC dynamic channel configuration control
RLC Radio Link Control
RTWP received total wideband power
1. Enhanced Combined Services Feature Parameter Description

2. DCCC Feature Parameter Description
3. Call Reestablishment Feature Parameter Description
4. Dynamic Configuration Based on the Uplink Load Feature Parameter Description
WCDMA RAN
UMTS Downlink Throughput Improvement Solution Guide
Issue 01
Date 2016-02-29

Notice

1.3.3 Contents
1.1 Overview
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Scenario 1: Downlink Single-User Throughput Improvement
3.1.1.1 Light Load Scenario
3.1.1.2 Multi-Carrier Scenario
3.2 Scenario 2: Downlink Multi-User Throughput Improvement

1.1 Overview
1.3 Change History
1.1 Overview
This document describes downlink throughput improvement solutions for different application scenarios in UMTS networks.

Need to understand downlink throughput improvement solutions in UMTS networks

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)
Added the feature WRFD-180203 HSDPA Rate Improvement in Asymmetric Coverage in 3.1 Scenario 1: Downlink Single-User Throughput Improvement and 3.2 Scenario 2: Downlink Multi-User
Throughput Improvement.
Added the feature WRFD-020116 Dynamic Power Sharing in Multi-Carriers in 3.1 Scenario 1: Downlink Single-User Throughput Improvement.
Added the feature WRFD-181207 DPCH TPC Power Adjustment and the HSDPA power margin cancellation function in 3.2 Scenario 2: Downlink Multi-User Throughput Improvement.
2 Solution Overview
2.1 Background
2.1 Background
In recent years, intelligent terminals and mobile Internet services have developed rapidly. Regarding user requirements, the users of intelligent terminals obtain services from mobile Internet. Downlink traffic
accounts for a large portion of the total traffic in the uplink and downlink. Most of the downlink traffic comes from services such as web browsing, MP3/ringtone downloads, software downloads, online video
(video clips downloading), and online shopping (a lot of pictures). Users expect high downlink rates and always-on data services with rapid response times and download speeds.
To meet these expectations, the downlink throughput improvement solution improves service data rates and increases the number of online users.
The purpose of this solution is to increase single-user data rates in light load scenarios and improve cell throughput in multi-user scenarios.
In accordance with these goals, the application scenarios of this solution can be classified into single-user throughput improvement and multi-user throughput improvement.
The single-user throughput improvement solution is used to improve user throughput when the downlink load is light. For details on scenario definitions, see 3.1.1 Scenario Description. This solution applies to
light load scenarios and multi-carrier scenarios.
The multi-user throughput improvement solution is used in scenarios where there are a large number of online users and the downlink load is heavy. In such a scenario, the solution focuses on improving the
downlink throughput while enabling as many users as possible to be online. For details about the scenario definition, see 3.2.1 Scenario Description.

The downlink throughput improvement solution adapts to different application scenarios with the purpose of improving user data rates and system capacity.
Downlink Single-User Throughput Improvement

The downlink single-user throughput improvement solution can be used to improve user throughput in light load scenarios and multi-carrier scenarios. In light load scenarios, downlink single-user HSDPA
throughput can be improved by using the techniques shown in Figure 2-1.
Figure 2-1 Solution for light load scenarios
click to enlarge
In multi-carrier scenarios, HSPA+ techniques and resource sharing among multiple carriers are used to increase the downlink throughput, as shown in Figure 2-2.
Figure 2-2 Solution for multi-carrier scenarios
click to enlarge
Downlink Multi-User Throughput Improvement

The downlink throughput improvement solution enables HSDPA users to use more resources by optimizing control channel power overhead, thereby increasing cell throughput in heavy load scenarios, as shown in
Figure 2-3.
Figure 2-3 Solution for heavy load scenarios
click to enlarge

The downlink single-user throughput improvement solution is used to improve burst service rates and reduce service delay. In this application scenario, cell capacity and resources are sufficient. This solution
applies to two scenarios: light load scenarios and multi-carrier scenarios.

A cell is considered lightly loaded if the duration when non-HSPA load is less than 40% reaches 60% of the total time period and the value of VS.CellDCHUEs(BSC6900,BSC6910) is smaller than 15.
Non-HSPA load = VS.MeanTCP.NonHS(BSC6900,BSC6910)/CellMaxPower
where,
CellMaxPower indicates the maximum transmit power in a cell, which is specified by the MAXTXPOWER(BSC6900,BSC6910) parameter in the ADD UCELLSETUP command.
The number of online users in the CELL_DCH state is measured by the VS.CellDCHUEs(BSC6900,BSC6910) counter.
Figure 3-1 Load distribution in a live network
click to enlarge

In multi-carrier scenarios, the cells in a sector operate in frequencies in the same frequency band or in different frequency bands.

This solution improves user throughput and user peak data rate in light load and multi-carrier scenarios, thereby improving downlink user experience. It is recommended that this solution be enabled to improve
downlink throughput.

A series of HSPA+ techniques have been introduced since 3GPP Release 7. Most of these HSPA+ techniques are used to improve downlink throughput. In light load scenarios, this solution uses HSPA+ techniques
to improve capacity and uses non-HSPA+ techniques to improve HSDPA performance.
This downlink single-user throughput improvement solution provides an obvious gain in light load scenarios but does not provide an obvious gain in heavy load scenarios.

Table 3-1 List of features and functions involved in the solution for light load scenarios
Classification Feature ID Feature/Function Name Function Description Introduced In… Reference Document
Peak rate WRFD-010681 HSPA+ Downlink 21Mbps per Enables a peak single-user data rate of 21 Mbit/s. RAN11.0 HSPA Evolution Feature
improvement User Parameter Description
WRFD-010683 Downlink 64QAM Increases peak throughput by applying a high-order modulation scheme to users at RAN11.0 Downlink 64QAM
the center of a cell. Feature Parameter
Description
WRFD-010685 Downlink Enhanced L2 All downlink HSPA+ techniques depend on downlink L2 enhancement. RAN11.0 Enhanced L2 Feature
BLER control WRFD-030010 CQI Adjustment Based on Enables the NodeB to learn and identify channel types and select the optimal target RAN13.0 HSDPA Feature
Dynamic BLER Target BLER to improve the average downlink user throughput. Parameter Description
N/A BLER Optimization for HSDPA When the cell load is light and there are burst services, the NodeB reduces the RAN14.0 HSDPA Feature
Burst Services BLER to decrease the delay of burst services. Parameter Description
HSDPA WRFD-140215 Dynamic Configuration of Dynamically adjusts CQI feedback period based on the uplink load. When the RAN14.0 Dynamic Configuration
resource HSDPA CQI Feedback Period uplink load is light, this feature shortens the CQI feedback period to improve Based on the Uplink Load
allocation downlink performance. Feature Parameter
Description
WRFD-180203 HSDPA Rate Improvement in This feature is designed for UEs performing soft handovers in areas with RAN18.1 HSDPA Rate
Asymmetric Coverage asymmetric uplink and downlink coverage. This feature increases the uplink Improvement in
transmit power and the reliability of uplink control channels for the UEs, thereby Asymmetric Coverage
increasing the downlink transmission efficiency of these UEs and improving user Feature Parameter
experience. Description
N/A Balanced allocation of power and The TFRC algorithm takes both power and code consumption into consideration RAN11.0 HSDPA Feature
codes in the TFRC algorithm and performs as balanced power and code allocation as possible. This algorithm Parameter Description
increases downlink cell throughput when multiple users are scheduled in one TTI.
N/A HSDPA remaining power If there are remaining power resources after TFRC resources are allocated, the RAN15.0 HSDPA Feature
appending HSDPA remaining power appending algorithm appends certain HSDPA transmit Parameter Description
power to the last user scheduled in the current TTI. In light load scenarios, this
function reduces the BLER of burst services and the service delay.
N/A Code utilization optimization Increases the HSDPA code usage, reduces the power usage and downlink load, and RAN16.0 HSDPA Feature
improves user throughput. Parameter Description
N/A HS-SCCH and E-RGCH code When a small number of users are online, this function allows the preemption of RAN12.0 HSDPA Feature
allocation based on requirements unused E-RGCHs to increase the maximum number of HS-PDSCH codes to 15. Parameter Description
to increase the number of This function improves the peak user data rate.
available HS-PDSCH codes
N/A H-RNTI allocation implemented Prevents the decrease of downlink throughput due to incorrect H-RNTI detection. RAN13.0 HSDPA Feature
by RM coding Parameter Description
Mobility N/A Optimized fast HSDPA serving Shortens the HSDPA serving cell change delay and reduces rate drops caused by RAN16.0 Procedure Optimization
cell change handover signaling procedures. Feature Parameter
Description
N/A RSCP/RTWP-based Algorithm When the uplink load and coverage are not limited, this function reduces the RAN16.0 Adaptive Adjustment of
for Adaptively Adjusting the uplink BLER and uplink feedback delay, thereby improving the downlink HSUPA Small Target
Little Retransmission Times for throughput. Retransmissions Feature
HSUPA UEs Parameter Description

The downlink throughput improvement solution applicable to multi-carrier scenarios mainly uses HSPA+ techniques. As HSPA+ techniques require the support from UEs, this solution also uses enhanced multi-
carrier allocation features or functions that do not require support from UEs.

Table 3-2 List of features and functions involved in the solution for multi-carrier scenarios
Single-user WRFD-010680 HSPA+ Downlink 28Mbps per User* Enables a peak single-user data rate of 28 RAN11.0 HSPA Evolution Feature Parameter Description
peak rate Mbit/s.
WRFD-010689 HSPA+ Downlink 42Mbps per User* Enables a peak single-user data rate of 42 RAN12.0 HSPA Evolution Feature Parameter Description
Mbit/s.
WRFD-010703 HSPA+ Downlink 84Mbit/s per User* Enables a peak single-user data rate of 84 RAN13.0 HSPA Evolution Feature Parameter Description
Mbit/s.
WRFD-010696 DC-HSDPA* Enables the use of two carriers in the RAN12.0 Multi-Carrier HSDPA Feature Parameter
same frequency band to transmit data to Description
a user, improving the average user data
rate.
WRFD-150209 DB-HSDPA* Enables the use of two carriers in RAN15.0 Multi-Carrier HSDPA Feature Parameter
different frequency bands to transmit Description
data to a user, improving the user data
rate.
WRFD-150250 3C-HSDPA* Enables the use of three carriers to RAN15.0 Multi-Carrier HSDPA Feature Parameter
transmit data to a user, improving the Description
average and peak data rates.
WRFD-150207 4C-HSDPA* Enables the use of four carriers to RAN15.0 Multi-Carrier HSDPA Feature Parameter
transmit data to a user, improving the Description
average and peak data rates.
Resource WRFD-150208 Flexible Dual Carrier HSDPA Enables the RNC to flexibly select two RAN15.0 Multi-Carrier HSDPA Feature Parameter
sharing carriers for data transmission. It Description
improves the burst service rates of DC-
HSDPA users.
WRFD-020116 Dynamic Power Sharing in Multi-Carriers Enables HSPA carriers to use the RAN11.0 Power Sharing Feature Parameter Description
remaining power of R99 carriers,
improving the burst service throughput
of HSDPA users.
WRFD-160251 HSDPA Inter-Cell Power Sharing Enables one HSDPA cell to dynamically RAN17.1 HSDPA Feature Parameter Description
share the idle power resources of another
HSDPA cell, thereby improving the
throughput of HSDPA users' burst
services.
WRFD-160251 HSDPA Inter-Cell Power Sharing Enables one HSDPA cell to dynamically RAN18.1 HSDPA Feature Parameter Description
share the idle power resources of another
HSDPA cell, thereby improving the
throughput of HSDPA users' burst
services.
Macro-micro WRFD-151209 Macro-Micro DC-HSDPA Enables UEs to simultaneously use the RAN16.0 Multi-Carrier HSDPA Feature Parameter
multiple carriers resources of a macro cell and a micro Description
cell to guarantee the UE's peak
throughput and user experience under the
following conditions:
When the two cells are using
different frequencies in the
same frequency band
When the coverage of the
micro cell is within the
coverage of the macro cell
NOTE:
*: indicates that the corresponding feature requires support from UEs.

3GPP has introduced a lot of HSPA+ techniques. Figure 3-2 shows the development of these HSPA+ techniques.
Figure 3-2 Development of HSPA+ techniques
All HSPA+ techniques depend on Downlink Enhanced L2. Based on this dependency, HSPA+ techniques have developed in three directions: high-order modulation, multiple antennas, and multiple carriers.
Each HSPA+ technique has its own benefits as described follows:
64QAM increases the data rates of UEs at the cell center.

MIMO improves spectral efficiency and user throughput.
DC-HSDPA enables the use of two carriers to transmit user data, thereby improving the user data rate.
DC-HSDPA can be used with 64QAM or MIMO to further improve the data rates and throughput of UEs at the cell center.
3C-HSDPA and 4C-HSDPA can further increase the data rate compared with DC-HSDPA.
Dynamic Power Sharing in Multi-Carriers can be used with any of the preceding HSPA+ techniques to increase the available HSDPA power of carriers and further improve the downlink user throughput.
Dynamic Power Sharing in Multi-Carriers enables an inter-frequency co-coverage HSDPA cell to use the remaining power resources of an R99 only cell. When HSDPA is enabled in the R99 only cell,
this feature becomes unavailable.
Two or more of the preceding functions and features can be used together. These functions and features can be used in lightly loaded cells or heavily loaded cells. However, when used in heavily loaded cells, these
functions and features bring fewer gains. All the preceding features and functions can be used together in light load conditions.
If the operator wants to reduce the delay of small-packet burst services, the following features and functions can be enabled:
HSDPA remaining power appending

BLER Optimization for HSDPA Burst Services
Scheduling of UEs not based on data rates
H-RNTI allocation implemented by RM coding
Balanced allocation of power and codes in the TFRC algorithm
If the operator expects to increase the single-user peak rate in the center of a cell, the following functions and features can be enabled:
HS-SCCH and E-RGCH code allocation based on requirements to increase the number of available HS-PDSCH codes
Code utilization optimization
Downlink Enhanced L2
Downlink 64QAM
HSPA+ Downlink 21Mbps per User
In heavily loaded cells, it is recommended that the HSDPA remaining power appending algorithm and HSDPA BLER optimization algorithm be disabled because they increase the downlink load.
In light load scenarios, the WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period feature can be enabled to reduce the CQI feedback period and thereby improve downlink performance. If the
configured CQI feedback period is longer than 2 ms, the WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period feature can be enabled, and the
CQIFBckBaseCellLoad(BSC6900,BSC6910) and CQIFBckBaseCoverage(BSC6900,BSC6910) parameters should be set to 4 ms. Otherwise, this feature does not need to be enabled.

Multiple HSPA+ techniques can be used together. It is recommended that HSPA+ techniques be deployed according to the HSPA+ development path.
The following describes the principles of deploying multi-carrier-related features. If the DC-HSDPA-capable terminal penetration rate is high and adjacent carriers are used in the live network, the DC-HSDPA
feature is recommended. If the operator has deployed more than two carriers and the DC-HSDPA-capable terminal penetration rate is high, the Flexible Dual Carrier HSDPA feature is recommended. If the
operator has deployed more than two carriers and expects to further improve downlink user experience, the 3C-HSDPA feature is recommended.
If the operator has deployed carriers in different frequency bands, the DB-HSDPA feature can be deployed. If the operator has deployed carriers in different frequency bands and each frequency band is configured
with multiple carriers, the DB-HSDPA and Flexible Dual Carrier HSDPA features are recommended.
If R99 only cells exist, the Dynamic Power Sharing of Multi-Carriers feature can be deployed. The Dynamic Power Sharing of Multi-Carriers feature is used when traffic steering is required between R99 and
HSDPA cells. With this feature, R99 only cells share power with HSDPA cells.
Multi-carrier HSDPA features greatly increase user throughput in lightly loaded networks. If the downlink load is heavy, the number of online users is large, and there are a small number of available HSPA power
resources, the gains provided by multi-carrier HSDPA features decrease.
The penetration rate of multi-carrier terminals can be observed by using the following RNC counters:
(VS.HSDPA.UE.Mean.CAT25.28(BSC6900,BSC6910) + VS.HSDPA.UE.Mean.CAT21.24(BSC6900,BSC6910))/(VS.HSDPA.UE.Mean.CAT1.6(BSC6900,BSC6910) +
VS.HSDPA.UE.Mean.CAT7.10(BSC6900,BSC6910) + VS.HSDPA.UE.Mean.CAT11.12(BSC6900,BSC6910) + VS.HSDPA.UE.Mean.CAT13.14(BSC6900,BSC6910) +
VS.HSDPA.UE.Mean.CAT25.28(BSC6900,BSC6910))
(VS.HSDPA.UE.Max.CAT25.28(BSC6900,BSC6910) + VS.HSDPA.UE.Max.CAT21.24(BSC6900,BSC6910))/(VS.HSDPA.UE.Mean.CAT1.6(BSC6900,BSC6910) +
VS.HSDPA.UE.Mean.CAT15.16(BSC6900,BSC6910) + VS.HSDPA.UE.Mean.CAT17.20(BSC6900,BSC6910) + VS.HSDPA.UE.Mean.CAT21.24(BSC6900,BSC6910)) +
VS.HSDPA.UE.Mean.CAT25.28(BSC6900,BSC6910))
Table 3-3 describes these counters.
Table 3-3 Counter description
Counter Name Description
VS.HSDPA.UE.Mean.CAT1.6(BSC6900,BSC6910) Average Number of HSDPA UEs with Category 1-6 in a Cell
VS.HSDPA.UE.Max.CAT1.6(BSC6900,BSC6910) Maximum Number of HSDPA UEs with Category 1-6 in a Cell

Counter Name Description

Note: UEs of category 13-14 support 64QAM.

Note: UEs of category 13-14 support 64QAM.

Note: UEs of category 15-16 support MIMO or 64QAM.

Note: UEs of category 17-20 support MIMO and 64QAM.

Note: UEs of category 17-20 support MIMO and 64QAM.

Note: UEs of category 21-24 support DC-HSDPA.

Note: UEs of category 21-24 support DC-HSDPA.

Note: UEs of category 25-28 support DC-HSDPA and MIMO.

Note: UEs of category 25-28 support DC-HSDPA and MIMO.

The downlink multi-user throughput improvement solution is mainly applicable to densely populated urban areas and central business district (CBD) areas. The cells in these areas have a large number of online
users and high downlink non-HSPA power and TCP power. The following situation may occur in multi-user scenarios: downlink load is heavy, downlink throughput is low but the TCP load is high, and the number
of admission rejections due to power limitation is greater than that in other cells.
The non-HSPA load can be calculated using the following formula:
Non-HSPA load = VS.MeanTCP.NonHS(BSC6900,BSC6910)/CellMaxPower
where
CellMaxPower indicates the maximum transmit power in a cell, which is specified by the MAXTXPOWER parameter in the ADD UCELLSETUP command.
The number of online users in the CELL_DCH state is measured by the VS.CellDCHUEs(BSC6900,BSC6910) counter.
A cell is considered heavily loaded if the duration when non-HSPA load is greater than 60% exceeds 10% of the total time period and the value of VS.CellDCHUEs(BSC6900,BSC6910) is greater than 40.
The number of HSDPA users can be observed by using the following RNC counters.
VS.HSDPA.UE.Max.Cell(BSC6900,BSC6910) Maximum Number of HSDPA UEs in a Cell
VS.HSDPA.UE.Mean.Cell(BSC6900,BSC6910) Average Number of HSDPA UEs in a Cell
Downlink load can be observed by using the following RNC counters.

VS.MeanTCP(BSC6900,BSC6910) Mean Transmitted Power of Carrier for Cell
VS.MeanTCP.NonHS(BSC6900,BSC6910) Mean Non-HSDPA Transmitted Carrier Power for Cell

In multi-user scenarios, the downlink multi-user throughput improvement solution increases the downlink cell throughput and the number of online users and decreases the downlink load.

The downlink throughput improvement solution in multi-user scenarios involves improving DCH power efficiency, common channel power efficiency, SRB power efficiency, and resource specifications.

Table 3-4 List of features and functions involved in the solution for multi-user scenarios
DCH power WRFD-150230 DPCH Pilot Power In heavy load scenarios, this feature RAN15.0 Power Control Feature Parameter Description
efficiency Adjustment decreases non-HSPA power by decreasing
improvement the DPCH pilot power, thereby increasing
available HSDPA power and HSDPA
throughput.
WRFD-150235 DPCH Maximum Power Decreases non-HSPA power by decreasing RAN15.0 Power Control Feature Parameter Description
Restriction the maximum DPCH power, thereby
increasing available HSDPA power and
HSDPA throughput.
N/A Load-based DPCH Decreases DPCH transmit power in RAN15.0 Power Control Feature Parameter Description
maximum power adjustment congestion scenarios to relieve power
congestion.
WRFD-171204 DPCH Power Control Based Restricts the UE's power requirements on the RAN17.1 Power Control Feature Parameter Description
on Radio Quality associated DPCH based on the UE signal
quality.
WRFD-181207 DPCH TPC Power Decreases TPC transmit power and RAN18.1 Power Control Feature Parameter Description
Adjustment downlink non-HSPA power based on non-
HSDPA power, thereby increasing cell
downlink throughput.
Common channel WRFD-150236 Load Based Dynamic Decreases HSDPA pilot power in heavily RAN15.0 Load Based Dynamic Adjustment of PCPICH
power efficiency Adjustment of PCPICH loaded cells to increase available HSDPA Feature Parameter Description
improvement power and HSDPA throughput.
Resource WRFD-150242 HSDPA Scheduler Pool Enables the load in a cell to be shared among RAN15.0 HSDPA Scheduler Pool Feature Parameter
specification HSDPA schedulers. Description
improvement
SRB efficiency WRFD-010652 SRB over HSDPA Enables the downlink SRB to be carried on RAN11.0 HSDPA Feature Parameter Description
improvement HSDPA channels and the associated HSDPA
channel is the F-DPCH.
N/A Blind detection + SRB 1*0 With this function, the TFCI bit is not RAN15.0 Radio Bearers Feature Parameter Description
transmitted on the downlink DPCH, and a
transmission format (TF) in length 0 is
added to the TFCS of the SRB. This
function can reduce the power overhead on
combined HSDPA+DPCH and non-HSDPA
load, and increase HSDPA throughput.
One or more features and functions involved in the solution for multi-user scenarios can be used together. Each feature or function has different network impacts, depending on the load status. If a feature or
function has a larger network impact, it takes effect when the load is heavier.
The Load Control feature defines five load states based on the downlink non-HSPA load. The effective threshold of each feature can be configured based on the load state threshold, as shown in Figure 3-3. For
details, see Load Measurement Feature Parameter Description.
Figure 3-3 Load status
click to enlarge
Figure 3-4 shows the relationships between features and load status. It is recommended that features and functions be enabled in the following sequence:
SRB over HSDPA

Blind detection + SRB 1*0
HSDPA Scheduler Pool
DL DPCH pilot power optimization/DPCH Pilot Power Adjustment
Load Based Dynamic Adjustment of PCPICH
DPCH Maximum Power Restriction
Load-based DPCH Maximum Power Adjustment
Figure 3-4 Relationships between features and load status

click to enlarge
If the network has not been upgraded to RAN15.0, the DPCH pilot power optimization function can be used. If the network has been upgraded to RAN15.0, it is recommended that the DPCH pilot power
optimization function be disabled and DPCH Pilot Power Adjustment be enabled.
The Load Based Dynamic Adjustment of PCPICH feature has negative impacts on network coverage and KPIs. It is recommended that this feature be used when the non-HSPA load is greater than 50%.
WRFD-010681 HSPA+ Downlink 21Mbps per User RAN11.0 HSPA Evolution Feature Parameter Description
WRFD-010683 Downlink 64QAM RAN11.0 Downlink 64QAM Feature Parameter Description
WRFD-010685 Downlink Enhanced L2 RAN11.0 Enhanced L2 Feature Parameter Description
WRFD-030010 CQI Adjustment Based on Dynamic BLER Target RAN13.0 HSDPA Feature Parameter Description
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period RAN14.0 Dynamic Configuration Based on the Uplink Load Feature Parameter Description
WRFD-180203 HSDPA Rate Improvement in Asymmetric Coverage RAN18.1 HSDPA Rate Improvement in Asymmetric Coverage Feature Parameter Description
N/A Balanced allocation of power and codes in the TFRC algorithm RAN11.0 HSDPA Feature Parameter Description
N/A HSDPA remaining power appending RAN15.0 HSDPA Feature Parameter Description
N/A BLER Optimization for HSDPA Burst Services RAN14.0 HSDPA Feature Parameter Description
N/A H-RNTI allocation implemented by RM coding RAN13.0 HSDPA Feature Parameter Description
N/A Scheduling of UEs not based on data rates RAN15.0 HSDPA Feature Parameter Description
N/A HS-SCCH and E-RGCH code allocation based on requirements to RAN12.0 HSDPA Feature Parameter Description
increase the number of available HS-PDSCH codes
WRFD-010703 HSPA+ Downlink 84Mbit/s per User RAN13.0 HSPA Evolution Feature Parameter Description
WRFD-150207 4C-HSDPA RAN15.0 Multi-Carrier HSDPA Feature Parameter Description
WRFD-020116 Dynamic Power Sharing in Multi-Carriers RAN11.0 Power Sharing Feature Parameter Description
WRFD-150230 DPCH Pilot Power Adjustment RAN15.0 Power Control Feature Parameter Description
WRFD-181207 DPCH TPC Power Adjustment RAN18.1 Power Control Feature Parameter Description
WRFD-150236 Load Based Dynamic Adjustment of PCPICH RAN15.0 Load Based Dynamic Adjustment of PCPICH Feature Parameter Description
WRFD-150242 HSDPA Scheduler Pool RAN15.0 HSDPA Scheduler Pool Feature Parameter Description
WRFD-150235 DPCH Maximum Power Restriction RAN15.0 Power Control Feature Parameter Description
WRFD-010652 SRB over HSDPA RAN11.0 HSDPA Feature Parameter Description
N/A Blind detection + SRB 1*0 RAN15.0 Radio Bearers Feature Parameter Description
N/A DL DPCH Pilot power optimization RAN14.0 Radio Bearers Feature Parameter Description
N/A Load-based DPCH Maximum Power Adjustment RAN15.0 Radio Bearers Feature Parameter Description
3G The Third Generation
3GPP2 3rd Generation Partnership Project 2
BOSS Business and Operation Support System
1. HSPA Evolution Feature Parameter Description

2. Downlink 64QAM Feature Parameter Description
3. Enhanced L2 Feature Parameter Description
4. HSDPA Feature Parameter Description
5. Dynamic Configuration Based on the Uplink Load Feature Parameter Description
6. Adaptive Adjustment of HSUPA Small Target Retransmissions Feature Parameter Description
7. Multi-Carrier HSDPA Feature Parameter Description
8. Power Sharing Feature Parameter Description
9. Power Control Feature Parameter Description
10. Load Based Dynamic Adjustment of PCPICH Feature Parameter Description
11. HSDPA Scheduler Pool Feature Parameter Description
WCDMA RAN
UMTS Network KPI Improvement Solution Guide
Issue 01
Date 2016-02-29

Notice

1.3.4 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Solution for Improving Access-related KPIs
3.2 Solution for Improving Call Drop-related KPIs
3.3 Solution for Improving Handover-related KPIs
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the UMTS network KPI improvement solution for different application scenarios.

Need to understand the UMTS network KPI improvement solution

1.3 Change History

This section provides the changes in different versions of this document.
RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Added the implementation of RB reconfiguration for AMR services to the solution of improving call drop-related KPIs through the Fast Radio Bearer Setup feature. For details, see 3.2.1 Solution Description.
2 Solution Overview
2.1 Background

2.1 Background
On networks suffering from low access success rate and high call drop rate, the UMTS network KPI improvement solution can be used to improve user experience by improving access-, call drop-, and handover-
related KPIs.
This solution describes how to evaluate, analyze, and improve network KPIs.

This solution applies to networks where the access success rate, call drop rate, and handover success rate fall short of user expectations.

The UMTS network KPI improvement solution provides the following functions:
Improvement of access-related KPIs

Provides measures for improving access-related KPIs based on the causes of RRC connection setup failures and RAB setup failures.
Improvement of call drop-related KPIs
Provides measures for improving call drop-related KPIs based on the causes of call drops.
Improvement of handover-related KPIs
Provides measures for improving handover-related KPIs based on the causes of common inter-frequency hard handover failures.

The solution for improving access-related KPIs provides the following functions:
Improvement of the paging success rate

Improvement of the RRC connection setup success rate
Improvement of the RAB setup success rate
The called parties are paged before accessing the network. If a called party is in the border of a location area (LA), the paging may fail if the called party is performing a cross-LA cell reselection. This is because
the LA information may not be updated for the UE in time. Under these circumstances, the seamless paging feature can be enabled to prevent the paging failures caused by cross-LA cell reselections.
Table 3-1 lists the causes of RRC connection setup failures and the improvement measures.
Table 3-1 Causes of RRC connection setup failures and the improvement measures
Cause for RRC Connection Setup Failures Symptom Improvement Measure

Cause for RRC Connection Setup Failures Symptom Improvement Measure
Resource congestion VS.RRC.FailConnEstab.Cong > 0 1. Prolong the waiting time for UEs to send another RRC connection setup
request by running the SET USTATETIMER command with the
Power congestion VS.RRC.Rej.ULPower.Cong > 0 RrcConnRejWaitTmr parameter set to a larger value.
Downlink power resource congestion VS.RRC.Rej.DLPower.Cong > 0 2. Enable the Enhanced Fast Dormancy feature to reduce the resource usage of
UEs in the CELL_DCH state so as to increase the access success rate.
Uplink Iub bandwidth congestion VS.RRC.Rej.ULIUBBand.Cong > 0 3. Adjust the network bearing policy or expand the network capacity according
to the instructions in UMTS Multi-Carrier Solution.
Downlink Iub bandwidth congestion VS.RRC.Rej.DLIUBBand.Cong > 0
Uplink CE resource congestion VS.RRC.Rej.ULCE.Cong > 0
Downlink CE resource congestion VS.RRC.Rej.DLCE.Cong > 0
Code resource congestion VS.RRC.Rej.Code.Cong > 0
NodeB resource unavailable VS.RRC.Rej.NodeBResUnavail > 0
Failure in the Uu interface procedure VS.RRC.FailConnEstab.NoReply > 0 Take either of the following measures:
Reduce the size of the RRC CONNECTION SETUP message and perform UE
incompatibility processing during RRC connection setups. For details about
these two functions, see sections "RRC CONNECTION SETUP Message Size
Reduction" and "UE Incompatibility Processing During RRC Connection
Setup" in Procedure Optimization Feature Parameter Description.
Automatically increase the FACH power during the RRC connection setup
procedure. For details, see section "FACH Power Control During RRC Phase"
in Power Control Feature Parameter Description.
Table 3-2 lists the causes of RAB setup failures and the improvement measures.
NOTE:
The causes of RAB setup failures and the improvement measures are domain-specific. The following table takes the CS domain as an example.
Table 3-2 Causes of RAB setup failures and the improvement measures
Cause Classification Specific Cause of RAB Setup Failures Symptom Improvement Measure
Resource congestion Downlink Iub bandwidth congestion VS.RAB.FailEstabCS.DLIUBBand.Cong > 0 Modify the activity factors by running the MOD TRMFACTOR command
with activity factors for R99 PS services and HSPA services changed to 50%.
The following parameters are involved:
PSINTERDL
PSINTERUL
PSBKGDL
Uplink Iub bandwidth congestion VS.RAB.FailEstabCS.ULIUBBand.Cong > 0 PSBKGUL
HDINTERDL
HDBKGDL
HUINTERUL
HUBKGUL
Uplink CE resource congestion VS.RAB.FailEstabCS.ULCE.Cong > 0 Enable the WRFD-010638 Dynamic CE Resource Management feature. For
details, see HSUPA Feature Parameter Description.
Code resource congestion VS.RAB.FailEstabCS.Code.Cong > 0 Reduce the initial rate of R99 PS services by running the SET UFRC command
with the value of the DlBeTraffInitBitrate parameter changed from the default
value D64 to D32.
Downlink power resource congestion VS.RAB.FailEstabCS.ULPower.Cong > 0 Run the SET USTATETIMER command with the value of the
IuPSRelNoRABTmr parameter changed from the default value 300s to 60s.
Downlink power resource congestion VS.RAB.FailEstabCS.DLPower.Cong > 0
Cause Classification Specific Cause of RAB Setup Failures Symptom Improvement Measure
Uu reason UE no replay during RB setup VS.RAB.FailEstabCS.UuNoReply > 0 Take any of the following measures:
Enable the fast RB setup during the DRD procedure function. For
Signaling RLC reset VS.RAB.FailEstabCS.SRBReset > 0
details, see section "Fast RB Setup During Combined RB Setup and
Concurrent procedures VS.RAB.FailEstabCS.CellUpd > 0 DRD" in Procedure Optimization Feature Parameter Description.
Dynamically adjust the activation time during RB setup. For details,
see section "Dynamic Activation Time Adjustment During RB Setup"
in Procedure Optimization Feature Parameter Description.
Reduce the size of the RRC CONNECTION SETUP message. For
details, see section "RRC CONNECTION SETUP Message Size
Reduction" in Procedure Optimization Feature Parameter
Description.
Adaptively adjust SRB rates based on coverage. For details, see
section "Coverage-based Adaptive SRB Rate Adjustment" in Radio
Bearers Feature Parameter Description.
Enable the fast RB setup function. For details, see Fast Radio Bearer
Setup Feature Parameter Description.
Reestablish radio links during RB setup. For details, see Call
Reestablishment Feature Parameter Description.

Table 3-3 lists features and functions involved in the solution for improving access-related KPIs.
Table 3-3 List of features and functions involved in the solution for improving access-related KPIs
Feature ID Feature Name Feature Description Introduced in… Reference Document
WRFD-140103 Call Reestablishment This feature improves the RAB setup success rate through call RAN14.0 Call Reestablishment Feature Parameter
reestablishment during the RAB setup procedure. Description
WRFD-160106 Fast Radio Bearer Setup This feature increases the RAB setup success rate by reducing the RAN16.0 Fast Radio Bearer Setup Feature Parameter
access delay in the case of good coverage or increasing the success rate Description
of downlink signaling message transmission in the case of weak
coverage.
N/A FACH Power Control During RRC Phase This feature controls the FACH power during the RRC connection RAN15.0 Power Control Feature Parameter Description
setup procedure based on UE's signal quality. When the coverage is
weak, this feature increases the FACH power and therefore increases
the access success rate.
N/A Dynamic Activation Time Adjustment This feature dynamically adjusts the activation time for RAB setups RAN14.0 Procedure Optimization Feature Parameter
During RB Setup based on UE's signal quality, which increases the success rate of Description
downlink signaling message transmission and therefore increases the
RAB setup success rate.
WRFD-170104 Seamless Paging This feature prevents paging failures caused by cross-LA cell RAN17.1 Seamless Paging Feature Parameter Description
reselections, thereby increasing the paging success rate for the calling
party of CS services.
The features and functions involved in this solution can be enabled at the same time.
When enabling the functions for improving the RAB setup success rate, pay attention to the following restrictions:
The Dynamic Activation Time Adjustment During RB Setup function becomes ineffective when the Fast Radio Bearer Setup feature is enabled.

The following table describes causes of call drops and the improvement measures.
Cause Cause of Call Drops Symptom Improvement Measure

Classification
Resource Cell Congestion VS.RAB.AbnormRel.CS.OLC(BSC6900,BSC6910)>0 Expand the capacity of base stations experiencing resource
congestion insufficiency.
RAB preemption VS.RAB.AbnormRel.CS.Preempt(BSC6900,BSC6910)>0
Uu interface Uplink synchronization failure VS.RAB.AbnormRel.CS.RF.ULSync(BSC6900,BSC6910)>0 Take any of the following measures:
causes Adjust the minimum signal quality threshold for soft
handovers: Change the value of the SHOQualmin parameter
from the recommended value -20 dB to -18 dB.
Enable the Call Reestablishment feature. For details, see Call
Reestablishment Feature Parameter Description.
Failure in the Uu interface VS.RAB.AbnormRel.CS.RF.UuNoReply(BSC6900,BSC6910)>0 Optimize the handling upon soft handover timeout. For
procedure details, see Procedure Optimization Feature Parameter
Description.
Enhance the algorithm of adding cells in intra-frequency
detected set to active set, which can be set by running the
SET UCORRMALGOSWITCH command. For details
about this function, see Procedure Optimization Feature
Enable the optimization solution to out-of-service issues of
UEs in the CELL_FACH state. For details about this
Signaling RLC reset VS.RAB.AbnormRel.CS.RF.SRBReset(BSC6900,BSC6910)>0 function, see State Transition Feature Parameter
Description.
Enable RB reconfiguration for AMR services in scenarios
where fast radio bearer setup is enabled. For details, see Fast
Radio Bearer Setup Feature Parameter Description.
Combined Abnormal release of the CS service VS.MultiRAB.CSAbnormRel.CSPS(BSC6900,BSC6910)>0 Use the combined service KPI improvement solution. For details about
services in CS+PS combined services this solution, see UMTS Combined Service KPI Improvement Solution.
WRFD-140103 Call Reestablishment This feature reestablishes radio links in the case of link out of synchronization or RAN14.0 Call Reestablishment Feature Parameter
failed Uu interface procedures after RRC connection setup, thereby reducing the Description
call drop rate.
WRFD-140104 Enhanced Combined Services This feature reduces the call drop rate of the CS service in CS+PS combined RAN14.0 Enhanced Combined Services Feature
services. Parameter Description
N/A Optimized Handling upon Soft This function optimizes the handling of the soft handover procedure, thereby RAN14.0 Procedure Optimization Feature Parameter
Handover Timeout preventing incorrect service release and ultimately reducing the call drop rate. Description
N/A Enhanced Algorithm of Adding This function reduces the occurrence of missing neighboring cells and decreases RAN15.0 Procedure Optimization Feature Parameter
Cells in Intra-Frequency Detected inter-cell interference, thereby reducing the call drop rate. Description
Set to Active Set
N/A Scenario Optimization for Out of This function optimizes the scenario of SRB reset, TRB reset, and air-interface RAN17.1 State Transition Feature Parameter
Service in the CELL_FACH State expiration in the CELL_FACH state, thereby reducing the PS call drop rate. Description
WRFD-160106 Fast Radio Bearer Setup This feature increases the RAB setup success rate by reducing the access delay in RAN16.0 Fast Radio Bearer Setup Feature Parameter
the case of good coverage or increasing the success rate of downlink signaling Description
message transmission in the case of weak coverage.

The solution for improving handover-related KPIs addresses the inter-frequency hard handover failures.
Table 3-4 describes the causes of inter-frequency hard handover failures and the improvement measures.
Table 3-4 Causes of inter-frequency hard handover failures and the improvement measures
Cause of Handover Failures Symptom Improvement Measure
Number of Failed Outgoing Inter-Frequency Hard VS.HHO.FailInterFreqOut.PyhChFail > 0 1. Enable the function of activating the inter-frequency compressed mode sequence prior to GSM
Handovers for Cell (Physical Channel Failure) compressed mode sequence to improve the accuracy and timeliness of the measurement in the target cells
for the inter-frequency hard handovers. The synchronization success rate of the target cells is increased as
a result, thereby reducing the inter-frequency hard handover failures caused by synchronization failures
on physical channels.
2. Enable the asynchronous reconfiguration for inter-frequency hard handover so that the UE can be handed
over to the target cell in a short time, thereby improving the success rate of inter-frequency hard
handovers.
Number of Failed Outgoing Inter-Frequency Hard VS.HHO.FailInterFreqOut.NoReply > 0 1. Enable the optimized measurement for inter-frequency hard handover so that inter-frequency hard
Handovers Due to No Response from the UE for handovers are not triggered in poor signal quality scenarios.
Cell 2. When more than two frequencies of the neighboring cells differ from that of the serving cell, the function
of delivering measurement control message for inter-frequency hard handover based on frequency
priority can be enabled.
N/A Activating the inter-frequency compressed mode The IFThenGSMMeaTypSwitch parameter is added to control the RAN17.1 Procedure Optimization Feature Parameter
sequence prior to GSM compressed mode sequence function that when inter-frequency and inter-RAT handovers coexist, Description
the RNC preferentially activates inter-frequency transmission gap
pattern sequences (TGPSs); if inter-frequency handovers fail to be
initiated, the RNC starts only GSM measurements.
N/A Asynchronous reconfiguration for inter-frequency The RNC does not include the activation time in the Uu interface RAN14.0 Procedure Optimization Feature Parameter
hard handover configuration message sent to the UE. The UE is handed over to the Description
target cell upon receiving the Uu interface configuration message.
N/A Optimized measurement for inter-frequency hard The RNC sends periodic inter-frequency and intra-frequency RAN14.0 Procedure Optimization Feature Parameter
handover measurement control messages at the same time, and includes the IE Description
measurementIdentity in the periodic inter-frequency measurement
control message to instruct the UE to report the signal quality of cells
in the active set.
N/A Delivering measurement control message for inter- If CS or PS inter-RAT and inter-frequency hard handovers coexist, the RAN16.0 Procedure Optimization Feature Parameter
frequency hard handover based on frequency priority RNC first sends the UE an inter-frequency measurement control Description
message, instructing the UE to measure the signal quality of inter-
frequency neighboring cells. If the inter-frequency hard handover fails
within the time specified by the corresponding timer, the RNC sends
the UE inter-frequency and inter-RAT measurement control messages,
instructing the UE to measure the signal quality of inter-frequency
and inter-RAT neighboring cells.
N/A FACH Power Control During RRC Phase RAN15.0 Power Control Feature Parameter Description
N/A Dynamic Activation Time Adjustment During RB Setup RAN14.0 Procedure Optimization Feature Parameter Description
WRFD-170104 Seamless Paging RAN17.1 Seamless Paging Feature Parameter Description
N/A Optimized Handling upon Soft Handover Timeout RAN14.0 Procedure Optimization Feature Parameter Description
N/A Enhanced Algorithm of Adding Cells in Intra-Frequency Detected Set RAN15.0 Procedure Optimization Feature Parameter Description
to Active Set
NA Scenario Optimization for Out of Service in the CELL_FACH State RAN17.1 State Transition Feature Parameter Description
N/A Activating the inter-frequency compressed mode sequence prior to RAN17.1 Procedure Optimization Feature Parameter Description
GSM compressed mode sequence
N/A Asynchronous reconfiguration for inter-frequency hard handover RAN14.0 Procedure Optimization Feature Parameter Description
N/A Optimized measurement for inter-frequency hard handover RAN14.0 Procedure Optimization Feature Parameter Description
N/A Delivering measurement control message for inter-frequency hard RAN16.0 Procedure Optimization Feature Parameter Description
handover based on frequency priority
RRC Radio Resource Control
RAB Radio Access Bearer
RB radio bearer
1. 3GPP TS 25.331, "Radio Resource Control (RRC) protocol specification"

3. Call Reestablishment Feature Parameter Description
4. Procedure Optimization Feature Parameter Description
5. UMTS Combined Service KPI Improvement Solution
7. HSUPA Feature Parameter Description
8. UMTS Multi-Carrier Solution
9. Fast Radio Bearer Setup Feature Parameter Description
10. Seamless Paging Feature Parameter Description
WCDMA RAN
UMTS Signaling Storm Solution Guide

Issue 01
Date 2016-02-29

Notice

1.3.5 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Scenario 1: Access Signaling Storm
3.2 Scenario 2: Paging Signaling Storm
1.1 Scope
1.3 Change History
1.1 Scope
This document describes signaling storm solutions for different application scenarios in UMTS networks.

Need to understand the signaling storm solution

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Compared with RAN16.0 01 (2014-10-15), RAN18.1 Draft A (2015-12-30) includes the following changes.
Change Type Change Description Parameter Change
Feature change Added the UBBPe board to support NodeB signaling capability improvement. For details, see 3.1.3 Solution None.
Description.
Editorial change None. None.

2 Solution Overview
2.1 Background
2.1 Background
Some packet switched (PS) applications (such as instant message and e-Mail) in smartphones frequently communicate with the Internet server in a short period of time. As the penetration rate of smartphones in
UMTS networks rises continuously, a large number of PS calls occur and each single PS call generates only a small amount of data. In order to save the battery power, some smartphones send a Signaling
Connection Release Indication (SCRI) message to the RNC after PS data transmission is complete. Therefore, such smartphones go through the whole procedure of RRC connection setup, PS data transmission,
and RRC connection release each time they have data to transmit. Frequent RRC connection setups and releases generate a large number of signaling messages and may lead to signaling storms.
Signaling storms consume more central processing unit (CPU) resources of the baseband processing boards in the NodeB and SPU and PIU boards in the RNC without bringing any revenues for operators. In
addition, if signaling storms are not handled properly, the CPU of the NodeB or RNC may be overloaded, affecting the network capacity and stability.
In addition, the Uu-interface paging load increases significantly because smartphones frequently communicate with the Internet server and each communication lasts for a very short period of time with only a
small amount of data to transmit. Statistics of typical networks show that the PS paging load over the Uu interface doubles every several months when traffic volume remains unchanged, and the total Uu-interface
paging load will exceed the capacity threshold of the RNC soon.
As a response to the preceding situations, Huawei introduces the signaling storm solution.

The signaling storm solution applies to scenarios where signaling storms are caused by a large amount of access or paging messages.
Access Signaling Storm
RRC connections are frequently established and released due to battery-power saving and always-on-line service requirements. As a result, a large number of PS RAB setup messages are received on the
RAN side.
When many UEs in the network are in the CELL_PCH state, a large number of cell reselection messages are generated if these UEs move frequently.
Paging Signaling Storm

Due to battery-power saving and always-on-line service requirements, some UEs frequently enters the idle or URA_PCH state. Paging these UEs brings a large number of signaling messages.

The signaling storm solution uses the following strategies:
Hardware capability improvement: Improves the signaling processing capability of the NodeB and RNC by introducing new boards or improving the signaling processing capability of existing boards.
Signaling suppression
After the R8 fast dormancy (FD) or enhanced fast dormancy (EFD) function is enabled, the RNC does not release the RRC connection when receiving an SCRI message from a UE. Instead, the
RNC transits this UE to the CELL_FACH, CELL_PCH, or URA_PCH state to reduce the number of access messages.
Layered paging is used to reduce the number of paging messages.
Flow control: When the RNC or NodeB hardware is heavily loaded, some types of access signaling messages are refused to avoid RNC or NodeB overload.

As the penetration rate of smartphones rises in UMTS networks, more UEs in idle mode attempt to set up PS RABs and more UEs in the CELL_PCH state attempt to perform cell reselection. This increases the
number of signaling messages and therefore increases the SPU load, NodeB signaling load, and NodeB CE resource usage.
The solution for access signaling storm applies to the following scenarios:
The PS traffic model changes due to the high smartphone penetration rate and service bursts occur (which are characterized by small data size during one RRC connection, short RRC connection period,
and frequent RRC connection requests). This solution is recommended when the number of signaling messages for PS RAB setups increases.
When UEs in the CELL_PCH state move frequently between cells, the number of cell reselection requests increases, which increases the SPU load. For example, this solution is recommended when the
number of signaling messages for cell reselection exceeds 50,000 per hour for top cells.

This solution increases the signaling processing capability of RNC and NodeB hardware, and reduces the SPU load, NodeB signaling load, and NodeB CE resource usage caused by increased number of signaling
messages for PS RAB setups and cell reselection when the penetration rate of smartphones is high.

This solution provides the following functions:
Increases hardware capability

This solution constantly increases the signaling processing capability of RNC and NodeB hardware in order to meet the future requirements for signaling capacity.
In RAN13.0 and RAN14.0, the maximum signaling processing capability of the RNC depends on the SPUb board in the BSC6900. In RAN15.0, the maximum signaling processing capability of the RNC
depends on SPUb board in the BSC6900 and GPU board in the BSC6910.
In RAN14.0 and RAN15.0, the maximum signaling processing capability of the NodeB depends on the UTRPc, UMPT, UBBPd, UBBPe, or WBBPf board.
Figure 3-1 shows increased RNC signaling processing capability.
Figure 3-1 Increased RNC signaling processing capability
click to enlarge
Figure 3-2 shows increased NodeB signaling processing capability.
Figure 3-2 Increased NodeB signaling processing capability
click to enlarge
For details about RNC and NodeB hardware capacity, see UMTS product documentation and NodeB product documentation.
Suppresses access signaling

To save battery power, some UEs send an SCRI message to the RNC after completing PS data transmission, instructing the RNC to transmit them to a power-saving mode. After the FD or EFD feature is
enabled for UEs complying with 3GPP Release 8, the RNC does not release the RRC connections of these UEs but transmits them to the CELL_FACH or CELL_PCH state upon reception of the SCRI
message. This significantly reduces the number of signaling messages for PS RAB setups.
After the UE inactivity timer expires, the RNC transmits the UE to the CELL_PCH state instead of the idle mode. If the UE then has data to transmit, data transmission is completed through a P2F2D2F2P
or P2F2P procedure. This reduces signaling overheads and saves system resources.
When URA_PCH is used, multiple cells are grouped into one URA (the URA can be the same as the LA) so that the UTRAN can learn the current URA of the UE and page the UE within this URA.
When the UE moves between cells in the URA, the UE does not need to send cell reselection requests to the RNC. When the UE moves to another URA, it sends a URA UPDATE message to request for a
URA change. This significantly reduces the number of signaling messages for cell reselection. URA is short for UTRAN registration area and LA is short for location area. After this solution is used, the
paging signaling increases and therefore this solution must be used together with the solution for paging signaling storm.
Performs flow control: Flow control is classified into RNC flow control and E2E flow control based on NodeB CPU load.
RNC flow control: When the CPU usage of an RNC board exceeds the CPU flow control threshold, this function prevents this RNC board from becoming overloaded by performing the following
signaling access control: access control, paging control, RRC flow control, Iur flow control, CBS flow control, cell/URA update flow control, Iur-g flow control, DCCC flow control, and MR flow
control. CBS is short for cell broadcast service. DCCC is short for dynamic channel configuration control. MR is short for measurement report. For details, see Flow Control Feature Parameter
Description.
E2E flow control based on NodeB CPU load protects NEs in a RAN from being overloaded. The NEs that participate in flow control are the RNC and NodeB. E2E flow control based on NodeB CPU load
is divided into two phases. In E2E Flow Control Phase 1, RADIO LINK SETUP REQUEST messages sent by the RNC to the NodeB are categorized according to service priority. The NodeB performs
flow control based on service priorities to reduce the NodeB CPU load and ensures preferential access of high-priority services. In E2E Flow Control Phase 2, the RNC performs flow control on RRC
CONNECTION REQUEST messages for new services (excluding emergency calls) based on the CPU congestion level reported by the NodeB and service priorities. The RRC CONNECTION
REQUEST messages of low-priority services are preferentially rejected. Phase 2 serves as a supplement to Phase 1 and aims to reduce the NBAP signaling flow over the Iub interface and saves more
RAN resources.

Table 3-1 lists features and functions involved in the solution for access signaling storm.
Table 3-1 List of features and functions involved in the solution for access signaling storm
Function Category Feature ID Feature Name Introduced in… Reference Document
Suppression of access signaling WRFD-020500 Enhanced Fast Dormancy RAN12.0 Enhanced Fast Dormancy Feature Parameter Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, RAN12.0 State Transition Feature Parameter Description
CELL-PCH, URA-PCH, CELL-FACH)
WRFD-01061111 HSDPA State Transition RAN5.0 State Transition Feature Parameter Description
Flow control NA E2E Flow Control Phase 1 RAN12.0 E2E Flow Control Feature Parameter Description
NA E2E Flow Control Phase 2 RAN13.0 E2E Flow Control Feature Parameter Description
WRFD-040100 Flow Control RAN12.0 Flow Control Feature Parameter Description

Table 3-2 describes features and functions involved in the solution for access signaling storm.
Table 3-2 Description of features and functions involved in the solution for access signaling storm
WRFD-020500 Enhanced Fast Dormancy This feature reduces the resource consumption of signaling processing in the Fast Dormancy procedure. After
receiving an SCRI message from a UE or the UE inactivity timer expires, the RNC transmits the UE to the
CELL_FACH state or to the CELL_PCH/URA_PCH state through the CELL_FACH state instead of
transmitting the UE to the idle mode.
WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, This feature enhances UE's support for the Fast Dormancy procedure. Conventionally, the process for UEs to
CELL-FACH) enter the power saving mode is controlled by the inactive timer delivered by the network side, which takes a
lot of time. Currently, some UEs complying with 3GPP Release 8 support the Fast Dormancy function defined
in 3GPP TS 25.331 CR3483. When a UE performing only PS services completes PS data transmission, the UE
immediately sends the RNC an SCRI message with the cause value of "UE Requested PS Data session end".
Upon reception of this message, the RNC immediately releases the RRC connection of the UE and enables the
UE to rapidly enter the power saving mode.
WRFD-01061111 HSDPA State Transition This feature enables channel switches between DCH and HS-DSCH. When a UE establishes BE services or
streaming services on the HS-DSCH and no data has been transmitted for a long period of time, the RNC
transmits the UE to the CELL_FACH state to save system resources.
N/A E2E Flow Control Phase 1 In E2E Flow Control Phase 1, RADIO LINK SETUP REQUEST messages sent by the RNC to the NodeB are
categorized according to service priority. The NodeB performs flow control based on service priorities to
reduce the NodeB CPU load and ensures preferential access of high-priority services.
N/A E2E Flow Control Phase 2 In E2E Flow Control Phase 2, the RNC performs flow control on RRC CONNECTION REQUEST messages
for new services (excluding emergency calls) based on the CPU congestion level reported by the NodeB and
service priorities. The RRC CONNECTION REQUEST messages of low-priority services are preferentially
rejected. This reduces NodeB CPU load and ensures that high-priority services are preferentially admitted.
WRFD-040100 Flow Control This feature prevents RNC boards from becoming overloaded by performing the following access signaling
control: access control, paging control, RRC flow control, Iur flow control, CBS flow control, cell/URA
update flow control, Iur-g flow control, DCCC flow control, and MR flow control.
To support the increasing number of signaling messages, new hardware and a new version can be used in the live network to improve the signaling processing capacity of the hardware. Features under the
suppression of access signaling function do not depend on or are not mutually exclusive to features under the flow control function. Therefore, features under these two functions can be simultaneously deployed in
a network where the penetration rate of smartphones is high.
For details about the deployment and activation of each feature, see the corresponding feature parameter description. Features under the suppression of access signaling function can be deployed at the same time
and features under the flow control function can also be deployed at the same time.

The increasing penetration rate of smartphones brings more services and more services result in more paging messages, especially more PS paging messages. This solution is recommended when the Uu-interface
paging load is heavy (for example, the PCH usage is greater than 60%).
NOTE:
PCH usage = VS.UTRAN.AttPaging1(BSC6900,BSC6910) / (SP x 100 x 5). In this formula, SP is the measurement period of the VS.UTRAN.AttPaging1(BSC6900,BSC6910) counter and is in units of seconds.

This solution significantly reduces the Uu-interface paging load for UEs in idle mode or in the URA_PCH state and improves system paging capacity.
For details, see Layered Paging in Idle Mode Feature Parameter Description and Layered Paging in URA_PCH Feature Parameter Description.

The solution for paging signaling storm provides the following functions:
Reduces the Uu-interface paging load using layered paging: Conventionally, paging messages are sent to the entire LA, RA, or URA. Due to the large paging area, the conventional paging mechanism
causes high Uu-interface paging load. To reduce the number of unnecessary paging messages and relieve the PCH congestion caused by excessive paging messages, the RNC perform layered paging on a
UE in idle mode as follows: The RNC first pages the UE in the last camped-on cell and the cell's neighboring cells under the same RNC. If no response is received, the RNC pages the UE in the entire LA
or RA. In this way, paging load in the entire system is significantly reduced. This prevents PCH congestion. For details about layered paging, see Layered Paging in URA_PCH Feature Parameter
Description and Layered Paging in Idle Mode Feature Parameter Description.
Reduces Uu-interface paging load by splitting the LA, RA, or URA: When the Uu-interface paging load is high, one LA, RA, or URA is split into N LAs, RAs, or URAs. In this case, the area of one LA,
RA, or URA is decreased and therefore the paging area is decreased. This reduces the paging load in the whole system and avoids PCH congestion.

Table 3-3 lists the features involved in the solution for paging signaling storm.
Table 3-3 List of features involved in the solution for paging signaling storm
Reducing the Uu-interface paging load using WRFD-140206 Layered Paging in URA_PCH RAN14.0 Layered Paging in URA_PCH
layered paging Feature Parameter Description
WRFD-150205 Layered Paging in Idle Mode RAN15.0 Layered Paging in Idle Mode
Descriptions of Features Involved in the Solution

Table 3-4 describes the features involved in the solution for paging signaling storm.
Table 3-4 Description of features involved in the solution for paging signaling storm
WRFD-140206 Layered Paging in URA_PCH Due to the rapid rise of smartphone use in recent years, PS paging messages have accounted for an increasingly
large proportion of paging messages. Conventionally, PS paging messages are sent to the entire URA. With this
feature, the RNC performs layered paging on UEs in the URA_PCH state. This significantly reduces the paging
load in the entire system and avoids PCH congestion.
WRFD-150205 Layered Paging in Idle Mode Due to the rapid rise of smartphone use in recent years, PS paging messages have accounted for an increasingly
large proportion of paging messages. Conventionally, PS paging messages are sent to the entire LA or RA. With
this feature, the RNC performs layered paging on UEs in idle mode. This significantly reduces the paging load in
the entire system and avoids PCH congestion.
For details about the engineering guidelines of the layered paging function, see the corresponding feature parameter description. Layered Paging in URA_PCH and Layered Paging in Idle Mode can be deployed at
the same time.
For details about how to split an LA, RA, or URA, contact Huawei technical engineers.
WRFD-020500 Enhanced Fast Dormancy RAN12.0 Enhanced Fast Dormancy Feature Parameter Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL- RAN12.0 State Transition Feature Parameter Description
PCH, URA-PCH, CELL-FACH)
WRFD-01061111 HSDPA State Transition RAN5.0 State Transition Feature Parameter Description
WRFD-040100 Flow Control RAN12.0 Flow Control Feature Parameter Description
WRFD-140206 Layered Paging in URA_PCH RAN14.0 Layered Paging in URA_PCH Feature Parameter Description
WRFD-150205 Layered Paging in Idle Mode RAN15.0 Layered Paging in Idle Mode Feature Parameter Description
URA UTRAN Registration Area
LA Location Area
RA Routing Area

2. Enhanced Fast Dormancy Feature Parameter Description
3. Layered Paging in Idle Mode Feature Parameter Description
4. Layered Paging in URA_PCH Feature Parameter Description
5. E2E Flow Control Feature Parameter Description
WCDMA RAN
UMTS Small Data Packet Storm Solution Guide
Issue 01
Date 2016-02-29

Notice

1.3.6 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3.3.1 Common Channel Solution
3.3.2 Power Efficiency Improvement for UEs in the CELL_DCH State
3.4 Implementation
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the small data packet storm solution, which is used to improve user experience for UMTS networks.

Need to understand the small data packet storm solution

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Added the following features in 3.3.2 Power Efficiency Improvement for UEs in the CELL_DCH State:
WRFD-180206 Precise Channel Estimation for HSUPA 2 ms UEs

WRFD-181205 Moving Speed-based Adaptive Demodulation
WRFD-181206 Control Channel Parallel Interference Cancellation (Phase 4)
WRFD-181207 DPCH TPC Power Adjustment
2 Solution Overview
2.1 Background
2.1 Background
Small data packets, such as those generated by Facebook, microblog, and free instant messaging applications have become the major service mode of smartphones. Small data packets are characterized by small
data volumes and long transmission intervals. Compared with traditional services, small data packet services generate more signaling and consume more Uu interface resources over control channels.
With the ever-increasing penetration rate of smartphones, signaling storms are the first network challenge that greatly impacts the network. For details about signaling storm solutions, see UMTS Signaling Storm
Solution.
The high penetration rate of smartphones also poses great challenges to the performance of the Uu interface. For example, with excessive small data packet services, the uplink control channels contribute to above
50% of the loads over the Uu interface, severely restricting the number of UEs that can be admitted by the network. Uplink control channels are the HS-DPCCH, DPCCH, and E-DPCCH. In addition, the Uu
interface resources available to data channels are significantly reduced, severely affecting the cell throughput. These challenges on the performance of the Uu interface are termed the small data packet storm.
The solution helps improve the performance of the Uu interface, including increasing the number of UEs that can be admitted by the network and improving the cell throughput.

The solution applies to small data packet storm scenarios. With the ever-increasing penetration rate of smartphones, more and more small data packets are generated by application software, which significantly
increases the power consumption of control channels. As a result, the number of UEs that can be admitted by the network is restricted, or cell throughput drastically decreases with an increase in the number of
online UEs. User experience is affected as a result.

The small data packet storm solution comprises the following sub-solutions or functions:
Common Channel Solution

During initial access or after data transmission, UEs processing small data packet services choose to stay in an appropriate state, such as CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH, based on
service requirements after the CELL_FACH, CELL_PCH, or URA_PCH function is enabled. This solution helps reduce the proportion of UEs that occupy dedicated channels and decreases signaling
overheads of UEs, thereby improving the transmission efficiency on the Uu interface.
Power Efficiency Improvement for UEs in the CELL_DCH State
Dedicated channels need to be established for UEs in the CELL_DCH state. However, UEs processing small data packet services require excessive power consumption of control channels, which
decreases the Uu interface resources available for data transmission. This function helps improve the power efficiency of the Uu interface when UEs are in the CELL_DCH state.
3.4 Implementation

Generally, small data packet storms are likely to occur when a cell serves many UEs, considering that normal networks usually accommodate a high proportion of smartphones.
In addition, a small data packet storm can be determined by observing the number of UEs in the CELL_DCH state.
When the traffic load is moderately balanced between cells under the same RNC, you can determine a small data packet storm scenario if the average number of UEs in the CELL_DCH state under the
RNC exceeds 20 during peak hours (that is, the value of VS.CellDCHUEs.RNC(BSC6900,BSC6910) divided by the number of cells is greater than 20).
When the traffic load is extremely unbalanced between cells under the same RNC, you can apply this solution in a cell with a large number of UEs and determine a small data packet storm scenario if the
number of UEs in the CELL_DCH state in the cell exceeds 20 (that is, the value of VS.CellDCHUEs(BSC6900,BSC6910) is greater than 20).
Because the proportion of UEs that are processing different types of services is relatively stable in normal networks (for example, the proportion of AMR UEs is usually about 30%), the number of UEs in the
CELL_DCH state is used to determine a small data packet storm scenario, regardless of the types of services these UEs are processing. If the number of UEs that are processing AMR services differs greatly among
actual networks, the threshold number of UEs for determining a small data packet storm scenario may also be different.

The solution to small data packet storms helps increase the capacity of the Uu interface, including increasing the number of UEs that can be admitted by the network and improving the cell throughput.

When many UEs that are processing small data packet services stay in the CELL_DCH state, these UEs consume excessive Uu interface resources of the DCH. Switching these UEs to other states, such as
CELL_FACH, CELL_PCH, or URA_PCH can help reduce the Uu interface resource consumption and improve the efficiency in which channels carry small data packet services. For details about the four states of
UEs in connected mode, see State Transition Feature Parameter Description.
In addition, this solution can be used together with the WRFD-010688 Downlink Enhanced CELL_FACH and WRFD-010701 Uplink Enhanced CELL_FACH features to increase the uplink and downlink
throughput of UEs in the CELL_FACH state by allocating the HS-DSCH and E-DPDCH to them.

Table 3-1 lists the features and functions involved in the common channel solution.
Table 3-1 Features and functions involved in the common channel solution
Feature ID Feature Name Introduced in… Reference Document Remarks
WRFD-020500 Enhanced Fast Dormancy RAN12.0 Enhanced Fast Dormancy Feature Parameter None
Description
WRFD-010688 Downlink Enhanced CELL_FACH RAN11.0 Enhanced CELL_FACH Feature Parameter Recommended when the penetration rate of E-
Description FACH UEs reaches 20%. In this case, the gains are
obvious.
Feature ID Feature Name Introduced in… Reference Document Remarks
WRFD-010701 Uplink Enhanced CELL_FACH RAN13.0 Enhanced CELL_FACH Feature Parameter Recommended when the penetration rate of E-
Description RACH UEs reaches 20%. In this case, the gains are
obvious.
N/A State transmission parameter optimization RAN12.0 State Transition Feature Parameter Description None
N/A Multi-carrier networking policy adjustment RAN12.0 UMTS Multi-Carrier Solution None
N/A RTWP reduction for SIB7 RAN14.0 Power Control Feature Parameter Description None
WRFD-020500 Enhanced Fast Dormancy

This feature comprises both the state transmission parameter optimization and the multi-carrier networking policy adjustment functions.
Some smartphones on a live network send a Signaling Connection Release Indication (SCRI) message to the RNC after PS data transmission is complete. By sending the SCRI message, the smartphones request
for a transition to idle mode or the CELL_PCH state to reduce power consumption. Upon receiving the SCRI message, the RNC monitors the smartphones for a period of time. If the smartphones do not transmit
data in either uplink or downlink, the RNC releases the signaling connections and switches the smartphones to idle mode, or the RNC maintains the signaling connections and switches the smartphones to the
CELL_FACH, CELL_PCH, or URA_PCH state.
If the Enhanced Fast Dormancy (EFD) feature is disabled, the RNC switches the smartphones to idle mode after receiving the SCRI message by default. A smartphone setting up PS services in idle mode consumes
more signaling resources than that in the CELL_PCH state. If the smartphone is to perform small data packet services, there is a high probability that the Uu resource consumption for signaling connections is
much more than that for data transmission.
The EFD feature optimizes the state transition algorithm for fast dormancy UEs so that they can switch to the CELL_FACH, CELL_PCH, or URA_PCH state more quickly and efficiently. Details are listed in the
following table.
Table 3-2 State transitions by UEs of different types after the EFD feature is enabled
UE Type Fast Dormancy UE or Not State Transition
UE that does not send the SCRI message (earlier than Release No An event 4B is triggered and the UE switches to the CELL_FACH, CELL_PCH, or URA_PCH state.
5)
UE that does not send the SCRI message (Release 5 or later) Yes The PS inactivity timer for EFD expires and the UE switches to the CELL_FACH, CELL_PCH, or URA_PCH
state.
An event 4B is triggered and the UE switches to the the CELL_FACH, CELL_PCH, or URA_PCH state.
UE that sends the SCRI message (with a cause value of "UE Yes The UE switches to the CELL_FACH, CELL_PCH, or URA_PCH state after sending the SCRI message to the
Requested PS Data session end") RNC.
The PS inactivity timer for EFD expires and the UE switches to the CELL_FACH, CELL_PCH, or URA_PCH
state.
An event 4B is triggered and the UE switches to the the CELL_FACH, CELL_PCH, or URA_PCH state.
UE that sends the SCRI message (with other cause values or Yes The UE switches to idle mode after sending the SCRI message to the RNC.
without any cause value) The PS inactivity timer for EFD expires and the UE switches to the CELL_FACH, CELL_PCH, or URA_PCH
state.
An event 4B is triggered and the UE switches to the CELL_FACH, CELL_PCH, or URA_PCH state.
Optimizing the parameters for state transition, including Dynamic Channel Configuration Control (DCCC), HSDPA State Transition, and HSUPA DCCC features aim to perform as follows:
Fast transition to the CELL_FACH state after data transmission is complete

Choose an appropriate timer to reduce the ping-pong state transitions as much as possible and shorten the time that a UE having no data transmission stays in the CELL_DCH state.
Appropriate configuration of data volume transmitted on the FACH Properly configure the data volume transmitted on the FACH to prevent congestion on the channel and transition to the CELL_DCH
state after a UE sends one or two PDUs.
Table 3-3 lists the optimization of state transition parameters.
Table 3-3 Optimization of state transmission parameters
Category Parameter Recommended Value Default Value (Current)
HSDPA BEH2FSTATETRANSTIMER(BSC6900,BSC6910) 2 5
BEH2FTVMPTAT(BSC6900,BSC6910) D1000 D1000
BEH2FTVMTIMETOTRIG(BSC6900,BSC6910) D1280 D5000
HSUPA BEE2FSTATETRANSTIMER(BSC6900,BSC6910) 2 5
E2FTHROUMEASPERIOD(BSC6900,BSC6910) 30 100
E2FTHROUPTAT(BSC6900,BSC6910) 4 16
DCH STATETRANSTRAFFREDUNDCOEF(BSC6900,BSC6910) 90 80
D2FTVMPTAT(BSC6900,BSC6910) D1000 D1000
D2FTVMTIMETOTRIG(BSC6900,BSC6910) D1280 D5000
BED2FSTATETRANSTIMER(BSC6900,BSC6910) 2 5
BeF2PStateTransTimer(BSC6900,BSC6910) 5 5
H2F optimization switch PerfEnhanceSwitch(BSC6900,BSC6910):PERFENH_H2F_OPT_SWITCH 1 0
F2D thresholds BeF2HTvmThd(BSC6900,BSC6910) D512 D1024

BeF2CpcHTvmThd(BSC6900,BSC6910)
BeF2ETvmThd(BSC6900,BSC6910) D256 D1024

BeF2DTvmThd(BSC6900,BSC6910)
BeF2CpcETvmThd(BSC6900,BSC6910)
After the EFD feature is introduced, the original camping strategies (that is, forced camping, preferential camping, or random camping) may lead to a large number of unnecessary cell reselections and PS service
drops may also occur in multi-carrier networking.
NOTE:
There are two features related to multi-carrier network management: WRFD-020110 Multi-Frequency Band Networking Management and WRFD-020160 Enhanced Multiband Management.
The original camping strategies are detailed as follows:
1. Forced camping
The forced camping strategy forces UEs in idle mode to camp on a specific frequency. For example, in Figure 3-1 UEs in idle mode are forced to camp on F1 and are not allowed to camp on F2.
However, if UEs in idle mode initiate services, they can choose to use F1 or F2 based on the service type.
Figure 3-1 An example of forced camping
2. Preferential camping
The preferential camping strategy enables UEs in idle mode to camp on the preferential camping frequency through cell selection and reselection parameter configurations. For example, in Figure 3-2,
UEs in idle mode camp on the preferential camping frequency F1, and some UEs are allowed to camp on F2. All UEs initiate services on their camping frequencies.
Figure 3-2 An example of preferential camping
3. Random camping
The random camping strategy enables UEs in idle mode to randomly camp on frequencies. For example, in Figure 3-3, UEs in idle mode randomly camp on frequency F1, F2, or F3.
Figure 3-3 An example of random camping
The camping strategies may need to be adjusted to accommodate current networking policies.
Table 3-4 Camping strategy adjustment in a multi-carrier networking scenario
Current Strategy Optimization Strategy Remarks
Forced camping Scenario 1 (recommended): F1/F2 preferential camping Most smartphones support HSPA. After receiving a reconfiguration message, UEs in the
CELL_FACH, CELL_PCH, or URA_PCH state cannot respond to the message in a barred cell.
Advantage: This strategy has small impact on traffic distribution among carriers
Therefore, these UEs must reselect F1 and respond to the message. If the forced camping strategy is
in the network.
used, UEs send a response message during HSPA-to-CELL_FACH (H2F) state transitions after
Disadvantage: UEs in the CELL_FACH, CELL_PCH, or URA_PCH state need reselecting F1. Under this circumstance, there is a high probability that the timer to wait for the
to reselect F1. After these UEs switch to the CELL_DCH state, they need to response message expires, and consequently PS service drops occur.
perform a DRD procedure to use F2. As a result, the common channel load of F1
is comparatively high.
Scenario 2: F1/F2 random camping
Advantage: Load balancing is achieved.
Disadvantage: This strategy requires a large amount of modifications and greatly
affects traffic distribution among carriers in the network.
Preferential camping The current camping strategy does not need to be changed in this scenario. It is UEs do not stay in the CELL_FACH state for a long time. Generally, most UEs stay in the
recommended that the inter-frequency measurement function be disabled for CELL_FACH state for a period ranging from 2 seconds to 10 seconds, and most UEs do not initiate
UEs in the CELL_FACH state. CS services within this short period of time. In addition, if all UEs in the CELL_FACH state camp
on F1, FACH congestion occurs on F1. Therefore, it is recommended that UEs in the CELL_FACH
state camp on their current carriers. During H2F state transitions, cell update caused by cell
reselection to F1 should also be avoided, because the procedure overlap may lead to a large number
of H2F state transition failures. Therefore, it is recommended that the inter-frequency measurement
function be disabled for UEs in the CELL_FACH state.
Random camping The current camping strategy does not need to be changed in this scenario. None
WRFD-010688 Downlink Enhanced CELL_FACH

The Downlink Enhanced CELL_FACH feature enables a UE in the CELL_FACH state to receive data with a high speed from the HS-DSCH.
Traditionally, the UEs in the CELL_FACH state use low-speed data transmission (32 kbit/s) only. With this feature, data on logical channels, such as the BCCH, CCCH, DCCH, and DTCH can be mapped to the
HS-DSCH and then transmitted to UEs in the CELL_FACH state through the HS-DSCH on the Uu interface. In this situation, UEs in the CELL_FACH state can share HSDPA code and power resources as UEs in
the CELL_DCH state do.
This feature accelerates downlink data transmission for UEs in the CELL_FACH state and shortens delays in service setup and state transitions, improving always-online experience.
WRFD-010701 Uplink Enhanced CELL_FACH

The Uplink Enhanced CELL_FACH feature enables a UE in the CELL_FACH state to transmit data or signaling with a high speed on the E-DPDCH.
When UEs in the CELL_FACH state transmit data in the uplink, the data is mapped to the E-DPDCH, not the PRACH, to realize a high-speed service rate in the uplink. The E-DPDCH provides higher data rates
because it uses a 2 ms TTI or 10 ms TTI. Theoretically, it can provide a data rate of 5.76 Mbit/s. In contrast, the PRACH uses a 20 ms TTI, providing a data rate of 8 kbit/s.
Using the extended acknowledgment indicator (E-AI) to make better use of the signatures, this feature reduces the probability of uplink channel collision, allowing for smoother data transmission.
In RAN15.0, feedback on the HS-DPCCH from UEs in the CELL_FACH state is supported. The UEs send ACK/CK responses and channel quality indicator (CQI) information to the NodeBs over the High Speed
Dedicated Physical Control Channel (HS-DPCCH). This function improves the downlink average throughput for the downlink enhanced CELL_FACH feature. The FACH is mapped onto the HS-DSCH.
RTWP Reduction for SIB7

This function reduces the uplink RTWP spikes caused by the open-loop power control on preamble signals sent by the UE during its initial access on the RACH. The reduction is noticeable in heavy traffic
scenarios. The RTWP in SIB7 is broadcast in real time. It is reduced to decrease the transmit power of the first preamble signal sent by the UE.

Different measures are taken in the uplink and downlink to decrease the Uu resource consumption of UEs in the CELL_DCH state, thereby improving power efficiency over the Uu interface.
Uplink
The uplink measures involve decreasing the power consumption of uplink control channels. Uplink control channels are the HS-DPCCH, DPCCH, and E-DPCCH.
Prolong the CQI feedback period and decrease the power offset to decrease the power consumption of the HS-DPCCH.
When a large number of UEs are in connected mode, the number of downlink scheduling chances is reduced for each UE. In addition, the requirements for the accuracy and frequency of CQI
demodulation on the HS-DPCCH are lowered. Under these circumstances, you can prolong the CQI feedback period for HSDPA UEs (by decreasing the number of times HSDPA UEs report CQI),
thereby decreasing the average power consumption of the uplink HS-DPCCH.
You can also decrease the power offset of the HS-DPCCH to decrease the power consumption of the HS-DPCCH.
Increase the power offset of HSUPA service channels to decrease the power consumption of the DPCCH.
When the HSUPA rate is low, for example, in common small data packet service scenarios, the requirements for channel estimation are comparatively low. That is, the signal-to-interference ratio (SIR) of
the DPCCH can be reduced. Under these circumstances, you can configure a comparatively large power offset for the E-DPDCH carrying HSUPA services, thereby decreasing the uplink power
consumption of control channels.
A comparatively small power offset should be configured for the E-DPDCH carrying HSUPA services with high data rates, thereby improving the SIR of the DPCCH and ensuring channel performance.
Optimize the working mechanism of outer loop power control (OLPC) to decrease the power consumption of HSUPA UEs on uplink control channels (DPCCH and HS-DPCCH) when these UEs have no
data to transmit.
The SIRtarget exported by the OLPC when there is no data transmission is generally lower than that exported by the OLPC when there is data transmission.
When there is no data transmission, the NodeB only needs to ensure that the UE is synchronized with the network in the uplink and that the UE correctly receives information on the HS-DPCCH.
When there is data transmission, the NodeB needs to ensure that the UE is synchronized with the network in the uplink and that the UE correctly receives information on the HS-DPCCH, E-DPCCH, and
E-DPDCH. In addition, the data rates on the E-DPCCH and E-DPDCH are much higher than those on other channels. Therefore, the NodeB receiver requires a large SIR to demodulate data. However, the
NodeB receiver requires only a low SIR to demodulate data when where is no data transmission.
Before this feature is introduced, when an HSUPA UE has no data to transmit, the RAN retains the SIRtarget exported by the OLPC when there is data transmission. After this feature is introduced, the
RAN performs OLPC based on the current quality of control channels when an HSUPA UE has no data to transmit. The SIRtarget exported under these circumstances is lower than that before this feature
is introduced.
Use the estimation of multiple control channels to improve the estimation precision, thereby further reducing the transmit power of the uplink DPCCH.
Identify the UEs with low moving speeds and low data rates and perform fundamental performance optimization at the physical player (such as channel estimation and multipath search) for these UEs.
The purpose is to decrease the uplink control channel power.
Configure a large target retransmission rate to obtain high HARQ combination gains, decrease the link load, improve the power efficiency per bit, and decrease the power consumption of control channels.
In a UMTS system, a large signal-to-noise ratio (SNR) increases the probability of data blocks being correctly received and the data transmission throughput. However, a large SNR requires high transmit
power, which results in increased interference to the system. This cannot achieve the highest possible bit efficiency. When the system is heavily loaded, a large target retransmission rate can be configured
for uplink R99 and HSUPA channels. This helps obtain high HARQ combining gains and lower the SNR, aiming at improving the uplink power efficiency of R99 and HSUPA UEs.
Use the interference cancellation technique to reduce interference between UEs, to decrease the interference against the DPDCH or E-DPDCH caused by the DPCCH, HS-DPCCH, or E-DPCCH, and to
decrease the power consumption of the DPCCH, HS-DPCCH, or E-DPCCH.
Universal Mobile Telecommunications System (UMTS) is a self-interference system. The transmission efficiency of the Uu interface is limited by inter-user interference. The interference cancellation
technique is the preferential multiuser detection (MUD) technique used by the UMTS system. It helps decrease the inter-user interference and therefore increases cell uplink capacity. In small data packet
storm scenarios, the interference cancellation technique helps improve the uplink transmission efficiency over the Uu interface.
Downlink
The following downlink measures are taken to decrease the power consumption of non-HSPA UEs:
Decrease the power consumption of common channels such as the CPICH.

In heavy load scenarios, reducing the power consumption of the CPICH increases the resources available to data channels but also reduces the cell coverage. Therefore, this method is recommended for
cells with good coverage performance (for example, in urban areas).
Decrease the power consumption of the A-DCH.

The transport format of the A-DCH is changed to reduce its power consumption. In addition, you can also improve the transmission efficiency of the A-DCH by decreasing the power consumption of the
UEs at the cell edge, as UEs at the cell edge require comparatively large downlink transmit power.

Table 3-5 lists the features and functions involved in power efficiency improvement for UEs in the CELL_DCH state.
Table 3-5 Features and functions involved in power efficiency improvement for UEs in the CELL_DCH state
Classification Feature ID Feature Name Introduced in… Reference Document
Parameters adaptively optimized to reduce the WRFD-010712 Adaptive Configuration of Traffic RAN13.0 Power Control Feature Parameter Description
power consumption of uplink control channels Channel Power Offset for HSUPA
Classification Feature ID Feature Name Introduced in… Reference Document
Parameters adaptively optimized to reduce the WRFD-160202 Flexible Power Control for Uplink Low RAN16.0 Flexible Power Control for Uplink Low Data Rate
power consumption of uplink control channels Data Rate Transmission Transmission Feature Parameter Description
Parameters adaptively optimized to reduce the WRFD-140215 Dynamic Configuration of HSDPA CQI RAN14.0 Power Control Feature Parameter Description
power consumption of uplink control channels Feedback Period
Parameters adaptively optimized to reduce the WRFD-140216 Load-based Uplink Target BLER RAN14.0 Power Control Feature Parameter Description
power consumption of uplink control channels Configuration
Parameters adaptively optimized to reduce the WRFD-140222 Adaptive Adjustment of HSUPA Small RAN14.0 Power Control Feature Parameter Description
power consumption of uplink control channels Target Retransmissions
OLPC optimized to reduce the power consumption N/A RTWP-based SIRtarget protection RAN14.0 Power Control Feature Parameter Description
of uplink control channels
OLPC optimized to reduce the power consumption N/A OLPC fast decrease RAN14.0 Power Control Feature Parameter Description
OLPC optimized to reduce the power consumption WRFD-171203 Uplink Control Channel OLPC RAN17.1 Uplink Control Channel OLPC Feature Parameter
of uplink control channels Description
OLPC optimized to reduce the power consumption WRFD-171207 Virtual CPC RAN17.1 Virtual CPC Feature Parameter Description
Using the estimation of multiple control channels to WRFD-180206 Precise Channel Estimation for HSUPA 2 RAN18.1 Precise Channel Estimation for HSUPA 2 ms UEs
reduce the transmit power of the DPCCH ms UEs Feature Parameter Description
Interference cancelled to reduce the power WRFD-140202 Control Channel Parallel Interference RAN14.0 Control Channel Interference Cancellation Feature
consumption of uplink control channels Cancellation (Phase 2) Parameter Description
Interference cancelled to reduce the power WRFD-160201 Control Channel Parallel Interference RAN16.0 Control Channel Interference Cancellation Feature
consumption of uplink control channels Cancellation (Phase 3) Parameter Description
Interference cancelled to reduce the power WRFD-160213 Turbo IC PHASE II RAN16.0 HSUPA Data Channel Interference Cancellation
consumption of uplink control channels Feature Parameter Description
- WRFD-010686 CPC - DTX / DRX RAN11.0 HSPA Evolution Feature Parameter Description
Reducing the power consumption of downlink WRFD-150236 Load Based Dynamic Adjustment of RAN15.0 Power Control Feature Parameter Description
common channels PCPICH
Reducing the power consumption of the A-DCH WRFD-150235 DPCH Maximum Power Restriction RAN15.0 Power Control Feature Parameter Description
Reducing the power consumption of the A-DCH WRFD-150230 DPCH Pilot Power Adjustment RAN15.0 Power Control Feature Parameter Description
Reducing the power consumption of the A-DCH WRFD-171204 DPCH Power Control Based on Radio RAN17.1 Power Control Feature Parameter Description
Quality
Reducing the power consumption of the A-DCH WRFD-181207 DPCH TPC Power Adjustment RAN18.1 Power Control Feature Parameter Description
Reducing the power consumption of the A-DCH WRFD-010652 SRB over HSDPA RAN10.0 Power Control Feature Parameter Description
Reducing the power consumption of the A-DCH N/A A-DCH using transmission format 1*0 RAN15.0 Radio Bearers Feature Parameter Description
when carrying only SRBs
Reducing the power consumption of the A-DCH N/A Blind detection started on the A-DCH RAN15.0 Radio Bearers Feature Parameter Description
when the A-DCH carrying only SRBs
- N/A Channel quality indicator (CQI) RAN15.0 HSDPA Feature Parameter Description
adjustment for small data packet services
with a large BLER

Table 3-6 lists the features and functions involved in power efficiency improvement for UEs in the CELL_DCH state.
Table 3-6 Descriptions of features and functions involved in power efficiency improvement for UEs in the CELL_DCH state
Feature ID Feature Name Description
WRFD-010712 Adaptive Configuration of Traffic Channel Power Offset for HSUPA Improves the power efficiency for HSUPA services:
The power consumption of the uplink DPCCH is reduced by increasing the power offset of the E-
DPDCH and DPCCH for UEs with low throughput.
WRFD-160202 Flexible Power Control for Uplink Low Data Rate Transmission Configures an extremely low rate (for example, a rate lower than 40 kbit/s) for HSUPA UEs and an
appropriate E-DPDCH HARQ offset for HSUPA UEs with an extremely low rate so as to reduce the
target SIR and power consumption of control channels, thereby increasing uplink capacity.
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period Reduces the power consumption on the HS-DPCCH:
When the uplink load is high, the CQI feedback period is prolonged to decrease the uplink power
consumption of the CQI on the HS-DPCCH.
WRFD-140216 Load-based Uplink Target BLER Configuration Improves the power efficiency for R99 PS services in the uplink:
When the uplink load is high, the target BLER of R99 PS users is increased to obtain larger
retransmission gains, thereby reducing the uplink power consumption without sacrificing the effective
rate.
WRFD-140222 Adaptive Adjustment of HSUPA Small Target Retransmissions Improves the power efficiency for HSUPA services:
The target retransmission rate of UEs with low throughput is increased. The target retransmission rate
of UEs using the 10 ms TTI is increased from 1% to 10%. The gains provided by HARQ
retransmissions help increase the HSUPA power efficiency.
WRFD-140202 Control Channel Parallel Interference Cancellation (Phase 2) Reduces inter-UE interference using the interference cancellation technique:
The interference on the DPCCH is canceled to decrease the interference from UEs on the DPCCH to
other UEs in the system.
The interference on the HS-DPCCH and E-DPCCH is canceled to minimize the interference from HS-
DPCCH and E-DPCCH to UEs.
A new interference cancellation scheme is used so that the control channels can benefit from
interference cancellation, maximizing the gains provided by interference cancellation.
WRFD-160213 Turbo IC PHASE II The NodeB selects low-rate HSUPA UEs using the 2 ms TTI for single HARQ process scheduling
when the uplink Uu interface is congested in a cell. This reduces the number of UEs that performing
data transmission at the same time, thereby reducing interference between UEs.
WRFD-181205 Moving Speed-based Adaptive Demodulation Identify the UEs with low moving speeds and low data rates and perform fundamental performance
optimization at the physical player (such as channel estimation and multipath search) for these UEs.
The purpose is to reduce the uplink control channel power.
N/A RTWP-based SIRtarget protection The uplink RTWP is checked every 10 ms. Under general congestion conditions, the SIRtarget is
reduced for HSUPA BE UEs using DTX. Under extreme congestion conditions, the SIRtarget is
reduced for R99 BE UEs and HSUPA BE UEs that do not use DTX.
N/A OLPC fast decrease In the early phase of service setup, the SIRtarget can be reduced by a maximum of 1 dB (configurable).
In addition, in the scenario of sudden interference or limited UE transmit power, the SIRtarget increase
is restricted.
WRFD-171203 Uplink Control Channel OLPC Reduces the power consumption of HSUPA UEs on uplink control channels by optimizing the working
mechanism of OLPC.
The RAN performs OLPC on HSUPA UEs based on the quality of control channels instead of that of
data channels when HSUPA UEs have no data to transmit. The SIR required for demodulating data on
control channels is lower than that required for demodulating data on data channels. As a result, the
power consumption of HSUPA UEs on uplink control channels is reduced.
WRFD-171207 Virtual CPC Reduces the power consumption of HSUPA UEs on uplink control channels by optimizing the working
mechanism of OLPC.
The Turbo IC Phase II feature triggers HSUPA UEs with 2 ms TTI to enter the single HARQ
scheduling state when uplink power resources are insufficient. Active processes of single-HARQ
HSUPA UEs are controlled by the network side. The NodeB can automatically identify active and
inactive processes of HSUPA UEs and calculate SIRtarget values by using different OLPC policies.
For active processes, inner loop power control is performed using the SIRtarget calculated
through OLPC on the RNC side. This SIRtarget is recorded as DCHSIRTarget.
For inactive processes, the SIRtarget is calculated based on signal quality on control channels.
This SIRtarget is recorded as DCHVCPCSIRTarget. Generally, DCHVCPCSIRTarget is lower
than DCHSIRTarget.
WRFD-180206 Precise Channel Estimation for HSUPA 2 ms UEs Huawei's existing features WRFD-160202 Flexible Power Control for Uplink Low Data Rate
Transmission, WRFD-171203 Uplink Control Channel OLPC, and WRFD-171207 Virtual CPC can
significantly reduce the transmit power of the uplink DPCCH. However, to maintain a high channel
estimation precision, the transmit power of the uplink DPCCH cannot be too low.
The WRFD-180206 Precise Channel Estimation for HSUPA 2 ms UEs feature involves multiple control
channels in channel estimation to improve the estimation precision, thereby further reducing the
transmit power of the uplink DPCCH.
The WRFD-180206 Precise Channel Estimation for HSUPA 2 ms UEs feature provides the greatest
gains when WRFD-160202 Flexible Power Control for Uplink Low Data Rate Transmission, WRFD-
171203 Uplink Control Channel OLPC, and WRFD-171207 Virtual CPC are all enabled.
WRFD-010686 CPC - DTX / DRX Reduces the power consumption of the DPCCH for HSUPA UEs: This feature consists of DTX and
DRX.
DTX is a method through which UEs momentarily stop the data transmission on the DPCCH to
decrease the interference on the DPCCH when there is no data transmission on the E-DCH. In addition,
to ensure the synchronization between power control and links, UEs periodically send DPCCH bursts
during the DTX.
Recommended when the penetration rate of CPC UEs reaches 20%. In this case, the gains are obvious.
WRFD-150236 Load Based Dynamic Adjustment of PCPICH Reduces the downlink power consumption of common channels:
When the required downlink non-HSPA power is large, the pilot transmit power is automatically
reduced to decrease the power consumption of common channels. In addition, the cell coverage is also
reduced and the UEs at the cell edge are handed over to neighboring cells to decrease the downlink load
of the current cell. In this way, more UEs at the cell center can be admitted by the network or the cell
can provide larger transmit power for online HSDPA UEs.
WRFD-150235 DPCH Maximum Power Restriction Reduces downlink load consumption of the DPCH:
In heavy downlink load scenarios, the maximum transmit power of the A-DCH is reduced when the A-
DCH does not have any signaling to transmit. This reduces the overall maximum transmit power.
WRFD-150230 DPCH Pilot Power Adjustment Reduces downlink load consumption of the DPCH:
When the downlink load is heavy, the power offset of the pilot channel is reduced to decrease the power
consumption of the pilot field on the DPCH, thereby saving the non-HSDPA power.
WRFD-171204 DPCH Power Control Based on Radio Quality Reduces downlink load consumption of the DPCH:
When the downlink load is heavy, the power offset of the pilot channel is reduced to decrease the power
consumption of the pilot field on the DPCH, thereby saving the non-HSDPA power.
WRFD-181207 DPCH TPC Power Adjustment Reduces downlink load consumption of the DPCH:
The cell-level TPC power offset is dynamically controlled based on the downlink non-HSPA power
load of the cell, reducing the non-HSPA power load and improving the downlink cell capacity when the
cell is heavily loaded.
WRFD-010652 SRB over HSDPA Reduces the number of code channels for the A-DCH and the power consumption of the A-DCH:
The F-DPCH and enhanced F-DPCH allow multiple HSDPA UEs to be multiplexed onto the same A-
DCH code channel, thereby reducing the code channel overhead and power consumption of the A-
DCH. The F-PDCH can be used only when the WRFD-010652 SRB over HSDPA feature is enabled.
As long as this feature is enabled, the F-DPCH and enhanced F-DPCH are available.
N/A A-DCH using transmission format 1*0 when carrying only SRBs PS services are carried on HSDPA channels, and the downlink R99 channel (A-DCH) carries only 3.4
kbit/s SRBs. The transmission format of the SRB is fixed at 1*0 so as to decrease the power
consumption of the A-DCH.
N/A Blind detection started on the A-DCH when the A-DCH carrying only PS services are carried on HSDPA channels, and blind detection is started when the downlink R99
SRBs channel (A-DCH) carries only 3.4 kbit/s SRBs. The overhead of the downlink TFCI is reduced as a
result.
The gain provided by this function is noticeable only when the A-DCH uses transmission format 1*0.
N/A CQI adjustment for small data packet services with a large BLER The CQI value is reduced during the initial data transmission of small data packet services, thereby
reducing the BLER.
3.4 Implementation
Features and functions involved in this solution do not cause negative gains on each other, that is, they are not mutually exclusive. Therefore, all earlier mentioned features and functions can be enabled at the same
time. For details, see the related feature parameter description document.

Features and functions involved in this solution do not cause negative gains on each other, that is, they are not mutually exclusive. Therefore, all earlier mentioned features and functions can be enabled at the same
time. For details, see the related feature parameter description document.
For details about the enhanced fast dormancy function and the required activation steps, see Enhanced Fast Dormancy Feature Parameter Description.
For details about how to optimize state transition parameters, see State Transition Feature Parameter Description.
For details about how to adjust multicarrier networking policies, see UMTS Multi-Carrier Solution.

Features and functions involved in the small data packet storm solution do not cause negative gains on each other. That is, they are not mutually exclusive. Therefore, all earlier mentioned features and functions
can be enabled at the same time. For details, see the feature parameter description documents listed in Table 3-5.
WRFD-020500 Enhanced Fast Dormancy RAN12.0 Enhanced Fast Dormancy Feature Parameter Description
WRFD-010688 Downlink Enhanced CELL_FACH RAN11.0 Enhanced CELL_FACH Feature Parameter Description
WRFD-010701 Uplink Enhanced CELL_FACH RAN13.0 Enhanced CELL_FACH Feature Parameter Description
N/A State transmission parameter optimization RAN12.0 State Transition Feature Parameter Description
N/A Multi-carrier networking policy adjustment RAN12.0 UMTS Multi-Carrier Solution
WRFD-140216 Load-based Uplink Target BLER Configuration RAN14.0 Power Control Feature Parameter Description
WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback RAN14.0 Power Control Feature Parameter Description
Period
WRFD-010712 Adaptive Configuration of Traffic Channel Power Offset RAN13.0 Power Control Feature Parameter Description
for HSUPA
WRFD-140222 Adaptive Adjustment of HSUPA Small Target RAN14.0 Power Control Feature Parameter Description
Retransmissions
WRFD-140202 Control Channel Parallel Interference Cancellation RAN14.0 Control Channel Interference Cancellation Feature Parameter Description
(Phase 2)
WRFD-160213 Turbo IC PHASE II RAN16.0 Interference Cancellation Feature Parameter Description
WRFD-160201 Control Channel Parallel Interference Cancellation RAN16.0 Control Channel Interference Cancellation Feature Parameter Description
(Phase 3)
WRFD-160202 Flexible Power Control for Uplink Low Data Rate RAN16.0 Power Control Feature Parameter Description
Transmission
WRFD-171203 Uplink Control Channel OLPC RAN17.1 Uplink Control Channel OLPC Feature Parameter Description
WRFD-171207 Virtual CPC RAN17.1 Virtual CPC Feature Parameter Description
WRFD-180206 Precise Channel Estimation for HSUPA 2 ms UEs RAN18.1 Precise Channel Estimation for HSUPA 2 ms UEs Feature Parameter Description
WRFD-150236 Load Based Dynamic Adjustment of PCPICH RAN15.0 Power Control Feature Parameter Description
WRFD-150235 DPCH Maximum Power Restriction RAN15.0 Power Control Feature Parameter Description
WRFD-150230 DPCH Pilot Power Adjustment RAN15.0 Power Control Feature Parameter Description
WRFD-010686 CPC - DTX / DRX RAN11.0 HSPA Evolution Feature Parameter Description
WRFD-010652 SRB over HSDPA RAN10.0 HSDPA Feature Parameter Description
WRFD-171204 DPCH Power Control Based on Radio Quality RAN17.1 Power Control Feature Parameter Description
N/A RTWP reduction for SIB7 RAN14.0 Power Control Feature Parameter Description
N/A RTWP-based SIRtarget protection RAN14.0 Power Control Feature Parameter Description
N/A OLPC fast decrease RAN14.0 Power Control Feature Parameter Description
N/A CQI adjustment for small data packet services with a RAN15.0 HSDPA Feature Parameter Description
large BLER
N/A A-DCH using transmission format 1*0 when carrying RAN15.0 Radio Bearers Feature Parameter Description
only SRBs
N/A Blind detection started on the A-DCH when the A-DCH RAN15.0 Radio Bearers Feature Parameter Description
carrying only SRBs
A-DCH Associated Dedicated Channel

AMR Adaptive Multirate
BLER Block Error Rate
CPICH Common Pilot Channel
CQI Channel Quality Indicator
DCCC Dynamic Channel Configuration Control
DPCCH Dedicated Physical Control Channel
DPDCH Dedicated Physical Data Channel
DTX BE Discontinuous Transmission Best Effort
E-DPCCH Enhanced Dedicated Physical Control Channel
E-DPDCH Enhanced Dedicated Physical Data Channel
HS-DPCCH High speed Dedicated Physical Control Channel
FPD Feature Parameter Description
EFD Enhanced Fast Dormancy
HARQ Hybrid Automatic Repeat Request
HSPA High Speed Downlink Packet Access
HSDPA High Speed Downlink Packet Access
HSUPA High Speed Uplink Packet Access
IC Interference Cancellation
OLPC Outer Loop Power Control
PO Power Offset
PRACH Physical Random Access Channel
PS Packet Switched
RACH Random Access Channel
RAB Radio Access Bearer
RLC Radio Link Control
RNC Radio Network Controller
RTWP Received Total Wideband Power
SCRI Signaling Connection Release Indication
SIR Signal-to-Interference Ratio
TFCI Transport Form Combination Indicator
TTI Transmission Time Interval
UE User Equipment
1. 3GPP TS 25.101, "User Equipment (UE) radio transmission and reception (FDD)"
2. 3GPP TS 25.211, "Physical channels and mapping of transport channels onto physical channels (FDD)"
3. 3GPP TS 25.306, "UE Radio Access capabilities"
4. 3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSPDA); Overall description"
5. 3GPP TS 25.321, "Medium Access Control (MAC) protocol specification"
6. UMTS Signaling Storm Solution
8. Enhanced Fast Dormancy Feature Parameter Description
10. Interference Cancellation Feature Parameter Description
11. HSUPA Data Channel Interference Cancellation Feature Parameter Description
12. Control Channel Interference Cancellation Feature Parameter Description
13. Enhanced CELL_FACH Feature Parameter Description
17. Flexible Power Control for Uplink Low Data Rate Transmission Feature Parameter Description
18. Uplink Control Channel OLPC Feature Parameter Description
19. Precise Channel Estimation for HSUPA 2 ms UEs Feature Parameter Description
WCDMA RAN
UMTS Uplink Throughput Improvement Solution Guide
Issue 01
Date 2016-02-29

Notice
1.3.7 Contents
1.1 Overview
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Scenario 1: Increasing Single Users' Uplink Throughput
3.2 Scenario 2: Increasing Multiple Users' Uplink Throughput
1.1 Overview
1.3 Change History

1.1 Overview
This document describes uplink throughput improvement solutions for different application scenarios in UMTS networks.

Need to understand uplink throughput improvement solutions in UMTS networks

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Added "WRFD-181206 Control Channel Parallel Interference Cancellation (Phase 4)" in 3.2 Scenario 2: Increasing Multiple Users' Uplink Throughput.
2 Solution Overview
2.1 Background
2.1 Background
Continuous innovation of the mobile Internet and growing UE capabilities provide access to more services, for example, microblogging, instant messaging, photographing, and video recording. Accordingly, the
demand increases for uplink data services, such as picture and video uploading and file sharing. These services require a higher uplink throughput to guarantee user experience, particularly in scenic spots and
during major events.
The solution is intended to improve the uplink throughput of UEs that transmit data continuously in commercial networks.
NOTE:
The uplink capacity is reflected by the number of uplink online users and uplink throughput. In actual networks, most UEs transmit small packets intermittently and a small number of UEs transmit data continuously. For the small data packet solution, see
UMTS Small Data Packet Storm Solution.

The solution applies to cells where there are a comparatively large number of UEs that are transmitting data continuously.
To be exact, these cells need to meet the following requirements:
UEs transmitting data continuously are those that need to transmit data for a comparatively long period of time, for example, UEs that need to upload data through FTP (to share or back up large files) or
UEs that need to upload pictures or videos.
There must be at least one UE transmitting data continuously in the cell.

On commercial networks, a small number of UEs transmit data continuously and a large number of UEs transmit small packets intermittently. To increase uplink throughput on UMTS networks, UE performance
must be improved. For the small data packet solution, see UMTS Small Data Packet Storm Solution.
This document only describes how to improve performance of UEs transmitting data continuously using the following methods:
Supporting more features and functions of high-end terminals with protocol evolution
The major purpose of protocol evolution is to support the peak rate of single users. To reach this goal, Huawei introduces the following features: HSUPA Introduction Package, HSUPA Phase II, HSPA+
Uplink 11.5Mbit/s per User, SRB over HSDPA, DC-HSUPA, UL 16QAM, and E-DPCCH Boosting.
To reduce impacts of HSUPA and HSUPA Phase 2 on coverage, the following features are introduced:
TTI Switch for BE Services Based on Coverage: bridges the gap between the coverage supported by HSUPA 2 ms TTI and coverage supported by HSUPA 10 ms TTI.
Coverage-based Fallback from the E-DCH to the DCH: bridges the gap between the coverage supported by HSUPA and coverage supported by R99.
Adopting an advanced receiver to improve performance of single links

The receiver supporting frequency domain equalization is introduced to solve crosstalk/harassment between codes in fast fading environments and improve performance of the links.
The interference suppression mechanism is introduced to improve the receiver's performance when there is strong interference.
Adding parameters for adaptive QoS to balance between the QoS and capacity
A proper number of times that data will be retransmitted is determined based on the air interface resource status of a cell and the UE rate. In this way, a large HARQ retransmission gain can be obtained.
Therefore, HSUPA throughput is improved. However, the UE delay will increase by a certain degree. The major feature is Adaptive Adjustment of HSUPA Small Target Retransmissions.
Interference cancellation (IC) and coordination
The interference cancellation technology is an important method of improving capacity in the CDMA system. This technology increases the signal-to-noise ratio (SNR) of a UE by eliminating interference
to other UEs in the CDMA system. For the uplink channel, the following interference cancellation features are introduced:
Interference cancellation on the uplink control channel
CCPIC Phase 2 implements interference cancellation on the DPCCH.
CCPIC Phase 3 implements interference cancellation on the HS-DPCCH and E-DPCCH.
Interference cancellation on the data channel
HSUPA IC implements interference regeneration and cancellation on the E-DPDCH according to demodulation information. It supports HSUPA 2 ms TTI UEs and HSUPA 10 ms TTI UEs.
Turbo IC implements IC on the E-DPDCH according to the decoded information. Compared to HSUPA IC, Turbo IC improves the IC efficiency because of more precise regeneration caused by
decoding gains. It supports HSUPA 2 ms TTI UEs.
Interference cancellation and coordination
Turbo IC Phase 2 performs restrictions so that HSUPA 2 ms TTI UEs can send data only in one HARQ process. Therefore, the number of UEs that can send data in a TTI is reduced, which
decreases interference between UEs. Turbo IC Phase 2 improves the resource allocation algorithm of Turbo IC to increase resource utilization and maximize the gains of Turbo IC.
Power control enhancement

When HSUPA UEs performing high-rate data transmission (such as higher than 2 Mbit/s) in the scenario with multi-path effect (such as that of the PB3 and VA30 channels), the SIR estimations are far
from accurate. As a result, the RTWP abnormally increases, which causes interference to other UEs in the cell. After enhancement of HSUPA Power Control is enabled, the SIR estimations are optimized
to decrease the interference to other UEs. In this way, the cell throughput increases.
Compromising coverage to increase capacity
When the coverage is good (the guaranteed KPIs do not deteriorate compared with baseline values or target values of the network plan), the RTWP scheduling target threshold can be increased to improve
system capacity, using the following features:
Dual-Threshold Scheduling with HSUPA Interference Cancellation
Dynamic Target RoT Adjustment
HSUPA anti-interference scheduling

To avoid out-of-service of the entire cell when there is strong external interference, the scheduler identifies strong interference periodically and raises the target RTWP threshold to increase the cell
throughput by compromising coverage performance at the edge of the cell.
NOTE:
In scenarios where external interference exists but HSUPA anti-interference scheduling is not used, the access success rate of UEs at the cell edge may be improved slightly, but the basic throughput requirement of these UEs cannot be guaranteed after
accessing the network.

Only one UE is transmitting data continuously in the cell within a certain period of time.
The average number of users performing data transmission simultaneously in a cell is 1 if:
VS.HSUPA.DataUserSumNum.ROTMorX/VS.HSUPA.DataTtiNum.ROTMorX = 1
where,
X is the maximum integer (3, 6, 7, 9, 10, 13, or 20) less than or equal to the target RoT threshold (dB) for cell HSUPA scheduling (this threshold is converted from the value of the
MaxTargetUlLoadFactor(BSC6900,BSC6910) parameter).
If the cell HSUPA throughput (calculated by VS.HSUPA.Thruput.ROTAll/Measurement period) is greater than 2 Mbit/s, this UE requires continuous data uploading.
NOTE:
The throughput of 2 Mbit/s applies to the typical configuration scenario where two antennas are configured and the target RoT threshold for cell HSUPA scheduling is 6 dB. This value varies with the number of antennas and the target RoT
threshold for cell HSUPA scheduling.
The throughput of 2 Mbit/s applies to the common wireless channels in the live network, such as PB, TU, and VA. If the channel quality is good, especially in a lab test, a value larger than 2 Mbit/s is required.

This solution can increase uplink throughput of the UEs that are uploading data continuously.

This solution increases the peak rates of single UEs to improve user experience. Meanwhile, to reduce impacts on the coverage performance and related KPIs, it introduces related coverage-based handover
algorithms. In addition, the advanced receiver is adapted to improve performance of single links and the peak rates of single UEs.

Table 3-1 List of features involved in the solution of increasing the uplink peak rates of single UEs
Functions developed for protocol evolution WRFD-010612 HSUPA Introduction Package RAN10.0 HSUPA Feature Parameter Description
WRFD-010614 HSUPA Phase 2 RAN10.0 HSUPA Feature Parameter Description

WRFD-010636 SRB over HSUPA RAN10.0 HSUPA Feature Parameter Description
WRFD-010690 TTI Switch for BE Services Based on Coverage RAN12.0 HSUPA TTI Selection Feature Parameter Description
N/A Coverage-based Fallback from the E-DCH to the RAN13.0 State Transition Feature Parameter Description
DCH
WRFD-010698 HSPA+ Uplink 11.5Mbps per User RAN12.0 HSPA Evolution Feature Parameter Description
WRFD-140204 DC-HSUPA RAN14.0 HSPA Evolution Feature Parameter Description
WRFD-010694 UL 16QAM RAN12.0 HSPA Evolution Feature Parameter Description
WRFD-010697 E-DPCCH Boosting RAN13.0 HSPA Evolution Feature Parameter Description
Advanced receiver WRFD-010692 HSUPA FDE RAN12.0 Frequency Domain Equalization Feature Parameter
Description
WRFD-160250 Interference Rejection Combining (IRC) RAN16.0 Interference Rejection Combining Feature Parameter
Description
Interference cancellation WRFD-010691 HSUPA UL Interference Cancellation RAN12.0 Interference Cancellation Feature Parameter Description
WRFD-150206 Turbo IC RAN15.0 Interference Cancellation Feature Parameter Description
Power control enhancement WRFD-01061203 Enhancement of HSUPA Power Control RAN16.0 Power Control Feature Parameter Description
Compromising coverage to increase capacity WRFD-020137 Dual-Threshold Scheduling with HSUPA RAN13.0 HSUPA Feature Parameter Description
Interference Cancellation
WRFD-140211 Dynamic Target RoT Adjustment RAN14.0 HSUPA Feature Parameter Description
WRFD-020136 Anti-Interference Scheduling for HSUPA RAN13.0 HSUPA Feature Parameter Description

This solution introduces some features to improve the maximum throughput of single UEs. The features include HSUPA Introduction Package, HSUPA Phase 2, HSPA+ Uplink 11.5Mbit/s per User, SRB over
HSUPA, DC-HSUPA, UL 16QAM, and E-DPCCH Boosting. To reduce impacts of HSUPA and HSUPA Phase 2 on coverage, the following features are introduced:
TTI Switch for BE Services Based on Coverage: bridges the gap between the coverage supported by HSUPA 2 ms TTI and the coverage supported by HSUPA 10 ms TTI.
Coverage-based Fallback from the E-DCH to the DCH: bridges the gap between the coverage supported by HSUPA and the coverage supported by R99.
As advanced receivers, HSUPA FDE and Interference Rejection Combining (IRC) improve the receiver performance in multi-path channel scenarios and in scenarios with a few intensive interfering sources,
respectively.
HSUPA IC reduces interference among multiple code channels for one UE. Turbo IC reduces interference among paths for one UE. Therefore, HSUPA IC and Turbo IC provide gains for even a single UE when
multi-path interference occurs.
Dynamic Target RoT Adjustment adjusts the HSUPA target scheduling threshold to increase the HSUPA throughput when there is good coverage performance at the edge of the cell.
Enhancement of HSUPA Power Control uses the optimized SIR estimation algorithm to suppress the increase in RTWP and improve the cell throughput.
Dual-Threshold Scheduling with HSUPA Interference Cancellation uses the interference cancellation algorithm to reduce interference between UEs so that the RTWP of the cell is reduced after the interference
cancellation algorithm is enabled. Meanwhile, this feature increases the RTWP scheduling target threshold to improve the HSUPA throughput.
To help the HSUPA scheduler control target RoT of a cell effectively and ensure satisfactory coverage performance, Dynamic Target RoT Adjustment monitors the coverage performance of UEs at the cell edge
and dynamically adjusts the target RoT. For example, this function uses a target RoT greater than the static one in a cell where the coverage performance for UEs at the cell edge is sound.
Anti-interference Scheduling for HSUPA monitors external interference in real time. When the cell experiences strong interference, the HSUPA scheduling target threshold is increased to ensure appropriate
HSUPA throughput.
For specific principles of each feature, see the related feature parameter description.
Features in this solution do not have any negative impacts on each other, which means that they are not mutually exclusive. Therefore, they can be enabled at the same time. For deployment of each feature, see the
related feature parameter description.

Multiple UEs are transmitting data continuously in the cell simultaneously within a certain period of time.
The average number of users performing data transmission simultaneously in a cell is greater than 1 if:
VS.HSUPA.DataUserSumNum.ROTMorX/VS.HSUPA.DataTtiNum.ROTMorX > 1
where,
X is the maximum integer (3, 6, 7, 9, 10, 13, or 20) less than or equal to the target RoT threshold (dB) for cell HSUPA scheduling. This threshold is converted from the value of the Maximum Target Uplink Load
Factor parameter. If the cell HSUPA throughput (calculated by VS.HSUPA.Thruput.ROTAll/Measurement period) is greater than 2 Mbit/s, this UE requires continuous data uploading.
NOTE:
The throughput of 2 Mbit/s applies to the typical configuration scenario where two antennas are configured, the target RoT threshold for cell HSUPA scheduling is 6 dB, and only a few UEs (such as less than 6) transmit data simultaneously. This
value varies with the number of antennas, the target RoT threshold for cell HSUPA scheduling, and the number of UEs performing data transmission simultaneously.
The throughput of 2 Mbit/s applies to the common wireless channels in the live network, such as PB, TU, and VA. If the channel quality is good, especially in a lab test, a value larger than 2 Mbit/s is required.

This solution can improve the uplink throughput of a cell.

Different from the solution used to increase the uplink peak rates of single UEs, this solution uses the following methods to improve the uplink throughput of multiple UEs:
Introduces the adaptive configuration algorithm of QoS parameters to balance between the QoS and capacity and obtain the optimum performance.
Performs interference cancellation (IC) and coordination to reduce interferences between UEs.

Table 3-2 List of features involved in the solution of increasing the uplink peak rates of multiple UEs
Functions developed for protocol evolution WRFD-010612 HSUPA Introduction Package RAN10.0 HSUPA Feature Parameter Description
WRFD-010690 TTI Switch for BE Services Based on RAN12.0 HSUPA TTI Selection Feature Parameter Description
Coverage
N/A Coverage-based Fallback from the E-DCH to RAN13.0 State Transition Feature Parameter Description
the DCH
Advanced receiver WRFD-010692 HSUPA FDE RAN12.0 Frequency Domain Equalization Feature Parameter
Description
WRFD-160250 Interference Rejection Combining (IRC) RAN16.0 Interference Rejection Combining Feature Parameter
Description
Interference cancellation WRFD-010691 HSUPA UL Interference Cancellation RAN12.0 Interference Cancellation Feature Parameter Description
WRFD-160213 Turbo IC Phase 2 RAN16.0 Interference Cancellation Feature Parameter Description
WRFD-140202 Control Channel Parallel Interference RAN14.0 Interference Cancellation Feature Parameter Description
Cancellation (Phase 2)
Adaptive QoS parameter adjustment for optimizing WRFD-140222 Adaptive Adjustment of HSUPA Small Target RAN14.0 Adaptive Adjustment of HSUPA Small Target
performance of single links Retransmissions Retransmissions Feature Parameter Description
Power control enhancement WRFD-01061203 Enhancement of HSUPA Power Control RAN16.0 Power Control Feature Parameter Description
Compromising coverage to increase capacity WRFD-020137 Dual-Threshold Scheduling with HSUPA RAN13.0 HSUPA Feature Parameter Description
Interference Cancellation
Adaptive Adjustment of HSUPA Small Target Retransmissions:

Based on the air interface resources and user rate of a cell, this feature determines an appropriate number of retransmission times. It increases the delay slightly but maximizes retransmission gains,
therefore improving HSUPA throughput.
HSUPA UL Interference Cancellation, Turbo IC, Control Channel Parallel Interference Cancellation (Phase 2), and Control Channel Parallel Interference Cancellation (Phase 3):
These features implement regeneration and cancellation on different channels to reduce interference between UEs.
Turbo IC Phase 2:
This feature uses an algorithm for more efficient Turbo IC resource allocation and an interference suppression technology that complies with the protocol. This technology limits the number of HARQ
processes that can be activated at a time to reduce the number of UEs transmitting data at a 2 ms TTI. In this way, interference between UEs is reduced.
For details about other features and functions, see 3.1.3 Solution Description. For specific principles of each feature, see the related feature parameter description.
Features in this solution do not have any negative impacts on each other, which means that they are not mutually exclusive. Therefore, they can be enabled at the same time. For deployment of each feature, see the
related feature parameter description.

WRFD-010612 HSUPA Introduction Package RAN10.0 HSUPA Feature Parameter Description
WRFD-010690 TTI Switch for BE Services Based on Coverage RAN12.0 HSUPA TTI Selection Feature Parameter Description
WRFD-010692 HSUPA FDE RAN12.0 Frequency Domain Equalization Feature Parameter Description
WRFD-160250 Interference Rejection Combining (IRC) RAN16.0 Interference Rejection Combining Feature Parameter Description
WRFD-010691 HSUPA UL Interference Cancellation RAN12.0 Interference Cancellation Feature Parameter Description
WRFD-140222 Adaptive Adjustment of HSUPA Small Target RAN14.0 Adaptive Adjustment of HSUPA Small Target Retransmissions Feature Parameter
Retransmissions Description
WRFD-160213 Turbo IC Phase 2 RAN16.0 Interference Cancellation Feature Parameter Description
WRFD-140202 Control Channel Parallel Interference Cancellation RAN14.0 Interference Cancellation Feature Parameter Description
(Phase 2)
(Phase 3)
WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference RAN13.0 HSUPA Feature Parameter Description
Cancellation
WRFD-01061203 Enhancement of HSUPA Power Control RAN16.0 Power Control Feature Parameter Description
N/A Coverage-based Fallback from the E-DCH to the DCH RAN13.0 State Transition Feature Parameter Description
(Phase 4)
3G The Third Generation

3GPP2 3rd Generation Partnership Project 2
BOSS Business and Operation Support System
1. 3GPP TS 25.101: User Equipment (UE) radio transmission and reception (FDD)
2. 3GPP TS 25.211: Physical channels and mapping of transport channels onto physical channels (FDD)
3. 3GPP TS 25.306: UE Radio Access capabilities
4. 3GPP TS 25.308: UTRA High Speed Downlink Packet Access (HSPDA) - Overall description
5. 3GPP TS 25.321: Medium Access Control (MAC) protocol specification
8. HSUPA TTI Selection Feature Parameter Description
9. Frequency Domain Equalization Feature Parameter Description
10. Interference Rejection Combining Feature Parameter Description
11. Interference Cancellation Feature Parameter Description
12. Adaptive Adjustment of HSUPA Small Target Retransmissions Feature Parameter Description
15. UMTS Small Data Packet Storm Solution
WCDMA RAN
UMTS Wide Coverage Solution Guide

Issue 01
Date 2016-02-29

Notice
1.3.8 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3 Guidelines on Solutions
3.1 Purpose
3.3 Guidelines
3.3.1 Scenario Analysis
3.3.2 Network Planning and Site Project
3.3.3 Network Optimization
4 Involved Features
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the UMTS wide coverage solutions provided by Huawei for various application scenarios.

Need to understand UMTS wide coverage solutions

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

This document is created for RAN18.1.
2 Solution Overview
2.1 Background
2.1 Background
With the development of mobile services, UMTS networks have become the foundation for building MBB. However, acquisition of site resources is time-consuming and lease costs are ever-increasing, creating a
bottleneck in adding base stations to improve coverage.
Huawei's wide coverage solution allows operators to improve performance of existing base stations to enhance network coverage.

Coverage performance of each base station, especially in rural and suburban areas, needs to be improved to ensure wide coverage, without the need to add new base stations. The following solutions are available:
Solution 1
Use of existing low frequencies
GSM 900 MHz or CDMA 850 MHz refarming
Solution 2
Use of high frequencies, including UMTS 2100 MHz and 1900 MHz
NOTE:
Solution 2 is used if solution 1 is unfeasible.
Huawei's wide coverage solution includes both hardware and software solutions.
Hardware Solution
1. Four receive antennas

The RAKE receiver is adopted in WCDMA to receive radio signals. It uses several receive antennas to process signals on multi-paths individually. The signals are decoded individually and then
combined together. In this manner, the transport channels are fully utilized, and multipath fading is reduced. Compared with that in scenarios of two receive antennas, the SNR decreases by 3 dB with
four receive antennas.
2. High-power RF module
An RF module with high downlink transmit power delivers wider downlink coverage. To obtain suggestions on RF module selection, see 3900 Series Base Station Product Documentation. The virtual
antenna mapping (VAM) technique can be used to provide 100 W for a single cell at most. For VAM details, see MIMO Prime Feature Parameter Description.
3. High-gain antenna
Most antennas have a horizontal 3 dB beamwidth of 65 degrees. Antennas with narrower horizontal beamwidths yield higher gains. In specific scenarios, such as linear coverage, antennas with a
horizontal 3 dB beamwidth of 33 degrees can be used to improve coverage.
Software Solution
1. Increased CPICH power

In most cases, CPICH power accounts for 10% of the total cell power and all common channel power accounts for 20% of the total cell power. In cells with light downlink load (downlink non-HSPA
power load is less than 30% during busy hours), it is good practice to increase CPICH power to improve coverage.
FACH transmit power is configured based on the CPICH power offset. Consequently, the maximum FACH transmit power increases with CPICH power.
2. Improved uplink coverage during access
Enhanced decoding is used to improve RACH message demodulation performance and enhance RACH coverage.
3. Improved signaling coverage
In weak coverage scenarios, the SRB rate is reconfigured from 13.6 kbit/s to 3.4 kbit/s. For details, see Radio Bearers Feature Parameter Description.
Enhanced decoding is used to improve uplink coverage for SRBs over DCH. For details, see Improved Uplink Coverage for SRB over DCH Feature Parameter Description.
4. Increased maximum downlink transmit power of radio links for voice services
The maximum downlink transmit power of radio links for voice services is equal to CPICH transmit power by default. In lightly loaded cells (downlink non-HSPA power load is less than 30% during
busy hours), it is good practice to increase the maximum downlink transmit power by 3 dB.
5. Uplink receive enhancement for voice services
The RAN side performs decoding and then softer combination to improve uplink coverage for voice services. For details, see the following:
AMR Voice Quality Improvement Based on PLVA Feature Parameter Description
CS Voice Precise Power Control Feature Parameter Description
Crystal Voice in Deep Coverage Feature Parameter Description
Seamless Crystal Voice Feature Parameter Description
6. Improved coverage for data services

Enhanced HSUPA power scaling and optimized outer loop power control are used to improve uplink coverage for data services. For details, see Power Control Feature Parameter Description.
Figure 2-1 Software solution

click to enlarge
3 Guidelines on Solutions
3.1 Purpose
3.3 Guidelines
3.1 Purpose
In weak coverage areas, use the wide coverage solution to improve coverage per base station.

This section details both hardware and software solutions.
Hardware Solution
Four receive antennas
Table 3-1 lists 4-antenna deployment modes.

Table 3-1 4-antenna deployment mode
Deployment Mode Antenna Solution RF Scheme
Antenna+RRU Use 4-port antennas. Add a 1T2R RF module if a 1T2R RF module is used onsite.
Use a 2T4R RF module.
Integrated RRU/antenna solution Use a 4R-capable AAU, such as AAU3911 or AAU3910.
The lower the working frequency, the larger the antenna dimensions. An antenna is about 2 meters long and weighs more than 10 kg if its working frequency is low. It is difficult to add an antenna to
achieve four receive antennas. Consequently, four receive antennas are not used to provide wide coverage over low frequencies.
To use four receive antennas, activate the WRFD-010209 4-Antenna Receive Diversity feature. For feature details, see TX Diversity and RX Diversity Feature Parameter Description.
High-power RF module
The maximum power of a 1T2R RF module is 80 W. In DC or single-carrier scenarios, each cell can be configured with 40 W power.
In other multicarrier scenarios, it is good practice to use two 1T2R RF modules or one 2T4R RF module with VAM to provide high power. For details, see MIMO Prime Feature Parameter Description.
To use VAM, activate the WRFD-030011 MIMO Prime feature. For feature details, see MIMO Prime Feature Parameter Description.
It is good practice to use a 2T4R RF module or two 1T2R RF modules to achieve four receive antennas in the uplink to prevent imbalanced uplink and downlink coverage if a cell needs to be configured
with 60 W or 80 W power.
If low frequencies are used, the maximum cell power can be 40 W. This is because low frequencies deliver excellent coverage.
High-gain antenna
Most antennas have a horizontal 3 dB beamwidth of 65 degrees. Antennas with narrower horizontal beamwidths yield higher gains. In specific scenarios, such as linear coverage, antennas with a
horizontal 3 dB beamwidth of 33 degrees can be used to improve coverage.
An antenna with a narrow horizontal beamwidth can be 2.2 meters long and weighs about 20 kg if its working frequency is low. It is difficult to install such a high-gain antenna. Consequently, high-gain
antennas are not used to provide wide coverage over low frequencies.
Software Solution
By default, cell power is 20 W and pilot power is 2 W. If a high-power RF module is used, cell power can be greater than 20 W. To improve coverage, it is good practice to increase pilot power with cell power. For
example, if cell power is set to 40 W, pilot power needs to be set to 4 W.
FACH transmit power and other common channel power are configured based on the CPICH power offset. In most cases, their power increases with CPICH power and does not need to be manually modified.
The downlink transmit power for CS services can be modified by running the MOD UCELLRLPWR command with the RlMaxDlPwr(BSC6900,BSC6910) parameter specified.
Table 3-2 lists the features and functions used in wide coverage solutions.
Table 3-2 Features and functions used in wide coverage solutions
Item Feature ID Feature Name Introduced in... Reference Document
RACH access WRFD-181201 Uplink Coverage Improvement During Access RAN18.1 Uplink Coverage Improvement During
Access Feature Parameter Description
Improved signaling coverage N/A Coverage-based adaptive SRB rate adjustment RAN16.0 Radio Bearers Feature Parameter
Description
WRFD-180201 Improved Uplink Coverage for SRB over DCH RAN18.1 Improved Uplink Coverage for SRB over
DCH Feature Parameter Description
Improved coverage for voice services WRFD-140201 AMR Voice Quality Improvement Based on PLVA RAN14.0 AMR Voice Quality Improvement Based on
PLVA Feature Parameter Description
WRFD-160204 CS Voice Precise Power Control RAN16.0 CS Voice Precise Power Control Feature
WRFD-171201 Crystal Voice in Deep Coverage RAN17.1 Crystal Voice in Deep Coverage Feature
WRFD-170201 Seamless Crystal Voice RAN17.1 Seamless Crystal Voice Feature Parameter
Description
Improved coverage for data services WRFD-020138 HSUPA Coverage Enhancement at UE Power RAN13.0 Power Control Feature Parameter
Limitation Description
WRFD-171209 Coverage Improvement for HSUPA 2 ms TTI UEs RAN17.1 Power Control Feature Parameter
Description
Feature and Function Descriptions

Table 3-3 Feature and function descriptions
Feature ID Feature Name Function
WRFD-181201 Uplink Coverage Improvement During Access In scenarios where uplink coverage is limited, this feature enables RACH messages that fail to be
decoded to be re-processed. In this way, the block error rate (BLER) is reduced, and uplink RACH
coverage is improved.
N/A Coverage-based adaptive SRB rate adjustment This feature allows the SRB rate to be reconfigured to 3.4 kbit/s in weak coverage scenarios to
improve coverage for SRBs.
WRFD-180201 Improved Uplink Coverage for SRB over DCH In scenarios where uplink coverage is limited, this feature enables the RNC to re-process SRB
frames that the NodeB fails to decode. In this way, the BLER is reduced, and uplink coverage is
improved.
WRFD-140201 AMR Voice Quality Improvement Based on PLVA This feature improves adaptive multi-rate (AMR) voice quality by using Huawei Parallel List
Viterbi Algorithm (PLVA), especially in weak coverage scenarios.
WRFD-160204 CS Voice Precise Power Control This feature optimizes uplink power control for voice services to make power control more
adaptable to changes in user behaviors and radio channels. This improves uplink coverage for voice
services.
Feature ID Feature Name Function
WRFD-171201 Crystal Voice in Deep Coverage This feature deploys a high-order channel decoding algorithm (with a stronger decoding capability)
on the DEUa board of the RNC to perform high-order channel decoding on voice frames that
experience channel decoding failures on the NodeB. This reduces the BLER and improves uplink
voice quality in deep coverage scenarios, especially in weak coverage scenarios.
WRFD-170201 Seamless Crystal Voice With this feature, a channel decoder is deployed on the RNC. When a CS AMR voice service
experiences a soft handover, the RNC performs softer combination on multiple soft handover
tributaries, thereby improving coverage for voice services.
WRFD-020701 AMR/WB-AMR Speech Rates Control For the same transmit power, a lower-rate AMR codec can provide wider uplink coverage.
WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation This feature improves coverage for HSUPA services at HSUPA cell edges. The feature is based on
the enhanced HSUPA power scaling technique introduced in 3GPP Release 8.
WRFD-171209 Coverage Improvement for HSUPA 2 ms TTI UEs This feature uses the virtual power scaling technology. With this technology, the network side
controls the power ratio of control channels to data channels for HSUPA 2 ms TTI users, thereby
improving coverage performance for HSUPA 2 ms TTI users.
WRFD-030011 MIMO Prime With MIMO Prime, every signal from a cell is equally split into two and the two signals are
distributed to two respective PAs. In this way, two PAs are used for power TX of a cell, thereby
increasing the utilization of the PAs.
WRFD-010209 4-Antenna Receive Diversity The 4-antenna RX diversity technology enables the NodeB to provide twice the number of RF
uplink channels compared with the 2-antenna RX diversity technology. In this way, the system can
obtain a higher uplink coverage gain.
3.3 Guidelines
A wide coverage solution involves the following processes:
1. Scenario analysis
2. Network planning and site project
3. Network optimization
4. Performance evaluation
The following figure shows the processes.

click to enlarge
3.3.1 Scenario Analysis

Analyze scenarios to identify weak coverage.
1. MR analysis
Analyze MR to determine areas that require optimization.
Recommendation: RSCP < -95 dBm
2. Counter analysis
Check whether the inter-RAT handover rate is greater than 10% (recommended) and 50% (recommended) of the inter-RAT handovers are initiated due to RSCP differences.
Inter-RAT handover rate = IRATHO.AttOutCS(BSC6900,BSC6910)/VS.RAB.SuccEstabCS.Conv(BSC6900,BSC6910)
RSCP difference-triggered inter-RAT handover rate = VS.IRATHO.AttOutCS.TrigRscp(BSC6900,BSC6910)/IRATHO.AttOutCS(BSC6900,BSC6910)
NOTE:
The recommendations are for reference only. Adjustment is allowed depending on network requirements.
Do not select overloaded cells or cells with overshoot coverage. Overloaded cells will absorb more traffic after coverage improvement, causing cell congestion. To check for overshoot coverage, contact Huawei
technical support.
NOTE:
For an overloaded cell, its transmitted carrier power (TCP) is greater than 70% or RTWP is greater than -100 dBm.
3.3.2 Network Planning and Site Project

If hardware solutions are used to provide wide coverage, it is good practice to perform network planning before deployment to eliminate the need for unnecessary RF optimization.
The WINS Space tool can be used during network planning. The WINS Space tool is currently unavailable to customers. For details about this tool, contact Huawei technical support.
If software solutions are used, activate required features following instructions provided in feature parameter descriptions. The features and functions used in the solutions are not mutually exclusive and therefore
no special handling is required in feature activation.
3.3.3 Network Optimization

Optimize RF settings, parameters, pilot power, and common channel power. RF optimization can be conducted using Automatic Cell Planning (ACP) provided by the U-Net. The U-Net tool is currently
unavailable to customers. For details about this tool, contact Huawei technical support.
click to enlarge
4 Involved Features
WRFD-140201 AMR Voice Quality Improvement Based on PLVA RAN14.0 AMR Voice Quality Improvement Based on PLVA Feature
WRFD-180201 Improved Uplink Coverage for SRB over DCH RAN18.1 Improved Uplink Coverage for SRB over DCH Feature
WRFD-181201 Uplink Coverage Improvement During Access RAN18.1 Uplink Coverage Improvement During Access Feature
WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation RAN13.0 Power Control Feature Parameter Description
WRFD-171209 Coverage Improvement for HSUPA 2 ms TTI UEs RAN17.1 Power Control Feature Parameter Description
WRFD-030011 MIMO Prime RAN13.0 MIMO Prime Feature Parameter Description
WRFD-010209 4-Antenna Receive Diversity RAN3.0 TX Diversity and RX Diversity Feature Parameter Description
VAM Virtual Antenna Mapping
CPICH Common Pilot Channel
RACH Random Access Channel
DCH Dedicated Channel
SRB Signaling Radio Bearer
PLVA Parallel List Viterbi Algorithm
AMR Adaptive Multirate
MIMO Multi-Input Multi-Output
TCP Transmitted Carrier Power
ACP Automatic Cell Planning
1. AMR Voice Quality Improvement Based on PLVA Feature Parameter Description

2. CS Voice Precise Power Control Feature Parameter Description
3. Crystal Voice in Deep Coverage Feature Parameter Description
4. Seamless Crystal Voice Feature Parameter Description
5. AMR Feature Parameter Description
6. Improved Uplink Coverage for SRB over DCH Feature Parameter Description
7. Uplink Coverage Improvement During Access Feature Parameter Description
9. MIMO Prime Feature Parameter Description
10. 3900 Series Base Station Product Documentation
1.4 Networking
Multi-Sector GUL Joint Deployment and Evolution Solution
UMTS HetNet Macro-Micro Network Solution
UMTS Multi-Carrier Solution
UMTS Multi-Sector Solution
UMTS RNC in Pool Solution
UMTS U900 and U850 Network Solution
WCDMA RAN
Multi-Sector GUL Joint Deployment and Evolution Solution Guide

Issue 02
Date 2016-04-28

Notice

1.4.1 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
2.3.1 Multi-Sector Solution to Radio Technologies Evolution
2.3.2 Multi-Sector Solution to Networking Evolution
3.1.1 Single-Mode Single-Band Scenarios
3.1.1.1 Scenario Description
3.1.1.2 Purpose
3.1.1.3 Solution Description
3.1.1.4 Implementation
3.1.2 Multi-Mode Single-Band Scenarios
3.1.2.2 Purpose
3.1.3 Multi-Mode Multi-Band Scenarios
3.1.3.2 Purpose
3.2 Special Scenarios
3.2.1 Special Traffic Scenarios
3.2.1.2 Purpose
3.2.2 Multi-Mode Multi-Band Co-Antenna Scenarios
3.2.2.2 Purpose
3.2.3 Special Clutter Scenarios
3.2.3.2 Purpose
1.1 Scope
1.3 Change History
1.1 Scope
This document describes joint deployment and evolution of the multi-sector solutions in different frequency bands on GSM, UMTS, and LTE networks.

Need to understand multi-sector solutions
1.3 Change History

RAN18.1 02 (2016-04-28)
Compared with Issue 01 (2016-02-29) of RAN18.1, Issue 02 (2016-04-28) of RAN18.1 includes the following changes.
Added recommended reconstruction scheme 2 in 3.1.3.3 Solution Description.

Added the method of using GSM sector splitting to work around the restriction that the GSM network does not support the RRUs in one cell solution in the left and right sectors. For details, see Hardware
Reconstruction Scheme.
RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

This is the first release of RAN18.1.
2 Solution Overview
2.1 Background
2.1 Background
On the live network, capacity and coverage have become the top concerns for operators to improve user experience.
Traditionally, most operators improve capacity and coverage by adding sites. However, it is difficult to obtain new sites and the cost for site addition is high due to high site rent and site loss.
In some cases, operators perform capacity expansion by adding carriers, as shown in Figure 2-1. However, operators are facing issues of spectrum scarcity, and only a small number of operators have bandwidth of
more than 15 MHz, making this solution unfeasible in most cases. It is difficult to resolve the capacity and coverage issues in complex dense urban areas and dense urban areas by adding carriers.
Figure 2-1 Frequency resources for operators
The GSM 900 MHz network keeps evolving to the UMTS 900 MHz network, and 900 MHz frequency resources are now being more used on UMTS networks, which increases the capacity requirements on the
GSM 1800 MHz network and those on the GSM 900 MHz network. If the capacity requirements still cannot be met when the GSM software features are enabled, operators can adopt the GSM six-sector solution.
On UMTS networks, with the ever-increasing growth of UMTS users, capacity expansion is required when air interface resources such as code resources and power resources are insufficient. Huawei's multi-sector
solution adopts sector splitting on UMTS frequency bands for network expansion and increases the capacity of single sites and areas, making it an important means for eliminating the network capacity bottlenecks.
The UMTS 900 MHz network is mainly evolved from the GSM 900 MHz network, and the GSM 900 MHz network and UMTS 900 MHz network will coexist for a long time. If the UMTS 900 MHz network
adopts the six-sector solution, the GSM 900 MHz network will also adopt the six-sector solution.
On LTE networks, the majority operators have multiple frequency bands, and frequency resources are sufficient for future use. The multi-sector solution is recommended only in some hotspots on LTE networks.
In conclusion, the multi-sector solution is not limited to a single network mode or frequency band. Instead, the multi-sector solution in multiple frequency bands and multiple modes becomes utterly necessary on
live networks.
The multi-sector solution uses different antenna solutions for dense urban, urban, suburban, and rural areas for maximum coverage and capacity gains. Specifications about solution gains are detailed in the multi-
sector solution guide, for example, UMTS Multi-Sector Solution.
The multi-sector solution facilitates network expansion without adding sites. The solution mainly addresses the following issues:
Frequency resources are insufficient and expansion cannot be implemented by adding carriers.
No proper site can be used for hotspots due to difficulties in acquiring sites, long expansion periods, and high costs.
Based on network modes and frequency bands, the multi-sector solution applies to the following scenarios:
Scenario 1: Sector splitting on single-mode single-band networks, for example, the UMTS 2100 MHz network.
Scenario 2: Sector splitting on multi-mode single-band networks, for example, the GSM+UMTS 900 MHz refarmed network.
Scenario 3: Sector splitting on multi-mode multi-band networks, for example, the UMTS2100 MHz and UMTS 900 MHz network, and the GSM 1800 MHz and UMTS 2100 MHz network.
NOTE:
This document focuses on the multi-mode multi-band scenarios. For details about single-mode single-band scenarios, see UMTS Multi-Sector Solution.
Figure 2-2 Multi-sector solution scenarios
Table 2-1 lists the solution application in multi-mode multi-band scenarios.

Table 2-1 Multi-sector solution in multi-mode multi-band scenarios
Multi-mode single-band (Refarming) Multi-mode multi-band
High or low frequency bands High and low frequency bands
GSM+UMTS 900 MHz/GSM+UMTS 850 MHz GSM 1800 MHz & UMTS 2100 MHz/UMTS 1900 MHz GSM+UMTS 900 MHz & UMTS 2100 MHz/UMTS 1900 MHz
UMTS+LTE 2100 MHz LTE 1800 MHz & UMTS 2100 MHz/UMTS 1900 MHz GSM+UMTS 850 MHz & UMTS 2100 MHz/UMTS 1900 MHz
GSM+LTE 1800 MHz LTE 2600 MHz & UMTS 2100 MHz/UMTS 1900 MHz GSM+LTE 1800 MHz & UMTS 900 MHz/UMTS 850 MHz
UMTS+LTE 1900 MHz GSM+UMTS 850 MHz/GSM+UMTS 900 MHz LTE 2600 MHz & UMTS 900 MHz/UMTS 850 MHz
All the commercial deployment scenarios are listed in the preceding table. The following describes some special scenarios:
Special scenario 1: Special traffic distribution

Traffic balance between sectors: The multi-sector solution generates the maximum gains if the traffic is comparatively balanced in each sector. However, on the GSM, UMTS, and LTE networks, traffic is
relatively balanced only on 20% of the networks, with the rest 70% being imbalanced and 10% being extremely imbalanced. Traffic balance affects the capacity gains and KPIs of networks enabled with
the multi-sector solution.
Hotspots in overlapping areas: If two sectors under the left and right lobes of a split antenna use the same frequency, the overlapping area will experience severe co-channel interference. If most users are
in the overlapping area after sector splitting, especially when the traffic distribution follows the stripe pattern, the capacity gains and KPIs will be affected on multi-sector networks.
Under the preceding conditions, the traffic distribution may be different for different frequency bands and network modes. In multi-mode multi-band scenarios, coordination between network modes and
frequency bands is required during deployment.
Special scenario 2: multi-mode multi-band co-antenna

When the multi-sector solution is used in multi-mode multi-band scenarios, the multi-mode co-antenna or multi-band co-antenna is required for sector splitting on, for example, UMTS high- and low-band
networks and GSM and UMTS low-band networks. Due to the differences between network modes and frequency bands, the optimal parameter settings vary with network modes or frequency bands. You
need to identify the priorities for different network modes or frequency bands.
Special scenario 3: Special clutter

In special clutter scenarios, the challenges are the same for different frequency bands and network modes.
In complex dense urban areas, the interference is difficult to control due to complex clutter environment. KPIs deteriorate by 30% to 50% when the multi-sector solution is implemented.
For some special clutters, such as high-speed railways, highways, cross-river bridges, the multi-sector solution needs to be determined based on site conditions. However, most special clutters
can only be manually identified.
This document describes how to implement the multi-sector solution in multi-mode multi-band scenarios.

2.3.1 Multi-Sector Solution to Radio Technologies Evolution
In the multi-sector solution in the multi-mode and multi-band scenarios, if an antenna is shared by multiple network modes or the roof top space is limited, sector splitting for one network mode will affect network
performance of other modes. Therefore, the network mode evolution policies must be clear.
GSM to UMTS
Huawei split antennas now support GSM and UMTS co-antenna in both high and low frequency bands. In the high frequency band, Huawei split antennas support 1800 MHz and 2100 MHz multi-sector
reconfiguration. In the low frequency band, Huawei split antennas support GSM and UMTS combined multi-sector reconfiguration together with RRUs in GSM+UMTS mode.
If only one network mode requires sector splitting, the other mode can still use the multiple RRUs in one cell solution in the three-sector networking.
GSM+UMTS to LTE
The GSM+UMTS network using the six-sector solution can evolve into the LTE network. If the GSM+UMTS network uses the six-sector solution, the LTE network can adopt the Single Frequency
Network (SFN) solution or the Adaptive SFN (ASFN) solution. The LTE network can still use the three-sector solution and use the six-sector solution when overloaded.
NOTE:
For details about the SFN and ASFN solutions, see SFN Feature Parameter Description. The ASFN feature applies to eRAN8.1 or later.
Figure 2-3 GSM+UMTS six-sector to LTE
2.3.2 Multi-Sector Solution to Networking Evolution

Single-mode single-band scenario: The networking evolution from three-sector to six-sector is based on capacity or coverage. For details, see UMTS Multi-Sector Solution.
Multi-mode single-band scenario: There are two networking evolution strategies. The one marked in bold red lines is the most frequently used strategy.
Figure 2-4 Multi-mode single-band networking evolution diagram
Category 1: Sector splitting triggered by refarming

The sector splitting is triggered when the frequency resources are refarmed to other network modes, for example, the GSM network after GSM+UMTS 900 MHz refarming. The evolution strategy is
reconstructing the original network to a multi-mode multi-sector network.
Category 2: Multi-mode steady networking after refarming
The sector splitting is separately triggered for the individual network mode, usually for the new network mode, for example, the UMTS network after GSM+UMTS 900 MHz refarming. The evolution
strategy is using the multi-sector solution for the new network mode and the multiple RRUs in one cell solution (three-sector networking) for the original network mode.
The multi-mode single-band networking uses the software-defined Radio (SDR) module and shares the same antenna.
Multi-mode multi-band scenario: For multi-mode networking, the network evolves from co-antenna three-sector to co-antenna six-sector. For high- and low-frequency networking, the network evolves from
separate-antennas three-sector to co-antenna six-sector, as shown in Figure 2-5.
Figure 2-5 Multi-mode multi-band networking evolution diagram
Multi-mode multi-band co-antenna three-sector networking

This type of networking mainly evolves to the multi-mode co-antenna six-sector networking. You can determine whether to use sector splitting based on the capacity and coverage requirements of each
network mode or frequency band. If sector splitting is not implemented on a network mode or frequency band, use the multiple RRUs in one cell strategy for the GSM+UMTS network and the SFN
strategy for the LTE network.
Multi-mode separate-antenna three-sector networking
This type of networking mainly evolves to the multi-mode separate-antenna six-sector networking.
Multi-band separate-antenna three-sector networking
This type of networking mainly evolves to the multi-band separate-antenna six-sector networking. However, If the single-mode high- and low-frequency networking or split antenna for only the high-
frequency networking evolve to the multi-band separate-antenna six-sector networking, you can determine whether to implement sector splitting based on the capacity or coverage requirements. If some
frequency bands do not use sector splitting, you can use the multiple RRUs in one cell solution for the GSM or UMTS network or the SFN solution for the LTE network.
The antenna reconstruction solution is based on the networking evolution solution, the antenna scenarios on the live network, and the split rules. For details about how to select antennas, see antenna selection
sections in the multi-sector solution guide, for example, "Antenna Selection" in UMTS Multi-Sector Solution.

3.1.1 Single-Mode Single-Band Scenarios
In single-mode single-band networking, the multi-sector solution is implemented on a single frequency band for a single network mode. The network mode and frequency band use a separate antenna in three-
sector scenarios, and therefore other frequency bands in the same network mode or other network mode are not involved. A typical scenario is the multi-sector reconfiguration on a UMTS 2100 MHz network.
3.1.1.2 Purpose
The sector splitting solution is used when capacity expansion and coverage improvement cannot be performed by carrier addition or new site deployment. The solution is used for capacity expansion and coverage
improvement in single-mode single-band scenarios.

The solution applies to capacity expansion and coverage improvement in single-mode single-band networking.
Hardware Reconstruction Scheme

The following table lists the recommenced hardware reconstruction schemes for sector splitting in single-mode single-band networking.
Original Network Typical Sector-Splitting Solution
U2100/G1800/L1800/U850/U900 Replace the original 65° antenna with a split antenna. The 2T4R RRUs are recommended.
Reconstruction description: RRUs on the legacy network can be used. Three RRUs are added (If 2T4R RRUs are used, the number of RRUs remains unchanged). The number of antennas remains unchanged.
Impact: The scheme does not have special impacts.
Figure 3-1 Split antenna in single-mode single-band networking
Multi-Carrier Strategy
In non-special scenarios, it is recommended that all carriers in the same frequency band of the same network mode are split. The multi-carrier strategy can reuse that on the original network.
Features and Functions in the Multi-Sector Solution

The enhanced or mapping multi-sector features for each network mode must be enabled. For details about features and functions, see the multi-sector solution guide for a specific network mode, for example,
UMTS Multi-Sector Solution.
When implementing the multi-sector solution in the single-mode single-band networking, enable the enhanced or mapping multi-sector features of the corresponding network mode. For details, see the multi-sector
solution guide for a specific network mode, for example, UMTS Multi-Sector Solution.
Contact Huawei engineers to implement the multi-sector solution.
3.1.2 Multi-Mode Single-Band Scenarios

In multi-mode single-band networking, the multi-sector solution is implemented on a single frequency band in multiple network modes. This scenario combines frequency refarming and multi-sector
reconstruction. Specifically, multi-sector reconstruction is implemented on networks where frequency refarming will be performed or has been performed.
3.1.2.2 Purpose
improvement on multi-mode single-band networks when frequency refarming is applied.

The solution applies to capacity expansion and coverage improvement on multi-mode single-band networks in frequency refarming scenarios. Currently, the solution mainly applies to low frequency bands of
GSM, UMTS, and LTE, GSM+LTE 1800 MHz. In the later version, the solution will apply to UMTS+LTE 2100 MHz.
Hardware Reconstruction Scheme

The following table lists the recommended hardware reconstruction schemes for sector splitting in multi-mode single-band networking.
Original Network Typical Sector-Splitting Solution
GSM+UMTS 900 MHz/GSM+LTE 1800 MHz Support for separate or joint sector splitting for multiple network modes.
Replace the 65° antenna with a split antenna, and perform sector splitting for both modes, or for one mode with the other mode using the
multiple RRUs in one cell solution.
The antenna networking mode and connections are the same for both methods. You can configure whether to perform sector splitting on the BBU.
Reconstruction description: The SDR connection remains unchanged after sector splitting for the dual-mode single-band network. Three RRUs are added if sector splitting is implemented on both modes.
Figure 3-2 Split antenna in multi-mode single-band networking
NOTE:
When a 2T4R RRU is used to support the six-sector solution, the GSM network does not support the RRUs in one cell solution in the left and right sectors. Therefore, the sector splitting solution can be used on the GSM network to ensure stable KPIs.
RRUs of other TX/RX mode do not have such restrictions.
Interoperation Policies
The following interoperation policies for the multi-mode single-band six-sector co-antenna networking can reuse those for the multi-mode single-band three-sector networking: Camping policies for UEs in idle
mode, redirection policies for UEs in connected mode, handover policies for UEs in the access phase, load balancing policies in the same network mode or between network modes. For example, the interoperation
policies for GSM six-sector&UMTS six-sector, GSM six-sector&UMTS three-sector, and GSM three-sector&UMTS six-sector are the same for those for GSM three-sector&UMTS three-sector.

The enhanced multi-sector features for each network mode must be enabled. For details about features and functions, see the multi-sector solution guide for a specific network mode, for example, UMTS Multi-
Sector Solution.
Table 3-1 Feature list
Feature ID Feature Name Function Introduced in... FPD Document

WRFD-030011 MIMO Prime With MIMO Prime, every signal from a cell is split into two signals, which are RAN13.0 MIMO Prime Feature Parameter Description
distributed to two respective PAs. In this way, two PAs are used for power TX
of a cell, thereby increasing the utilization of the PA. MIMO Prime can enhance
signals from HSDPA UEs to increase throughput of the HSDPA UEs and cell
capacity.
Besides enabling the enhanced multi-sector solution for multiple modes, you can enable the following feature:
WRFD-030011 MIMO Prime

In UMTS and LTE single-band scenarios, if the LTE network is enabled with the MIMO feature, the UMTS can be enabled with WRFD-030011 MIMO Prime. For details, see MIMO Prime Feature
3.1.3 Multi-Mode Multi-Band Scenarios

In multi-mode multi-band networking scenarios, the multi-sector solution is implemented in the following scenarios: multi-mode high-band or low-band (for example, GSM 1800 MHz and UMTS 2100 MHz
sector splitting), single-mode high- and low-band (for example, UMTS 900 MHz and UMTS 2100 MHz sector splitting), and multi-mode high- and low-band (for example, GSM 900 MHz and UMTS 2100 MHz
sector splitting).
3.1.3.2 Purpose
improvement for each network mode and frequency band based on the specific requirements.

The sector splitting solution applies to capacity expansion and coverage improvement on multi-mode multi-band networks. The sector splitting solution is mainly used for GSM 1800 MHz & UMTS 2100 MHz
networks and GSM+UMTS 900 MHz & UMTS 2100 MHz networks. In some cases, the solution is used in GSM & UMTS & LTE modes and high- and low-band networking.
Hardware Reconstruction Scheme (Multi-Mode High-Band or Low-Band)

The following table lists the hardware reconstruction schemes for the multi-mode high-band or low-band networking.
Original Network No. Typical Sector-Splitting Solution Recommended/Alternative
GSM+LTE 1800 MHz & UMTS 2100 MHz Scheme 1 Support for separate or joint sector splitting for different network modes (No antenna needs to be added). Recommended
Scheme 2 Perform sector splitting for the high-band UMTS network only and replace the original antenna with an Recommended
8-port antenna (No antenna needs to be added).
Scheme 3 Perform sector splitting for different network modes independently, replace the original antenna with the Alternative
split antenna (No antenna needs to be added), and use only one RRU for the network mode in which
sector splitting is not performed.
Scheme 4 Perform sector splitting for different network modes independently, replace the original antenna with the Alternative
common antenna and install the split antenna (the number of antennas increases), and use only one RRU
for the network mode in which sector splitting is not performed.
Scheme 1: Add no antennas, and perform sector splitting for two network modes, or for one mode with the other mode using the multiple RRUs in one cell solution. The antenna networking
mode and connections are the same for both methods. You can configure whether to perform sector splitting on the BBU.
Reconstruction description: Six RRUs are added, and twelve combiners are added.
Impact: The combiner loss is about 0.5 dB, but the split antenna has about 1 dB more gains than the 65° antenna does. Therefore, the coverage performance improves by about 1.5 dB.
Figure 3-3 Antenna splitting scheme 1 for the multi-mode high-band or low-band networking
Scheme 2: Add no antennas, perform sector splitting for the high-band UMTS network and perform 4T for the LTE network, and use 8-port antennas.
Reconstruction description: Three RRUs are added, and no antenna is added.
In the following figure, the LTE 1800 MHz uses 4T MIMO, and the UMTS 2100 MHz uses split antennas.
Figure 3-4 Hardware reconstruction scheme for high-band network modes (8-port antenna and sector splitting for the high-band UMTS network)
Scheme 3: Perform sector splitting for one network mode without adding antennas.
Reconstruction description: Three RRUs and 18 combiners are added. The number of antennas remains unchanged (the original antenna is replaced by the high-band or low-band split antenna).
Impact: Combiner loss is about 0.5 dB, and the TX power decreases by 3 dB due to power splitting in the frequency band on which sector splitting is not performed. The antenna gains increase by about 1
dB. For example, on the GSM 1800 MHz & UMTS 2100 MHz network, if sector splitting is not performed on the GSM 1800 MHz frequency band, the TX power loss is 2.5 dB (0.5+3-1=2.5) in the
downlink and 0.5 dB in the uplink.
The TX power of frequency band enabled with power splitting decreases by 3 dB. The improvement schemes are as follows:
Use 1T2R RRUs with high output power (applicable to the GSM and UMTS network).
The TX power is doubled to counteract the TX power loss of 3 dB. For example, the original RRU is configured with 1T2R with the maximum TX power of 80 W. Each sector is configured with
two carriers and 20 W per carrier. After the split antenna is installed, the three-sector network becomes the six-sector network. Power splitting is performed and the multiple RRUs in one cell
solution is implemented. New power licenses are configured. The TX power is 40 W per sector and 20 W per carrier. The connection mode remains unchanged.
Use 2T2R RRUs (applicable to the LTE network).
The original RRU is configured with 2T2R and 20 MHz bandwidth with the maximum TX power of 40 W for each channel. Each sector is configured with 20 W. After the split antenna is
installed, the three-sector network becomes the six-sector network. Power splitting is performed and the multiple RRUs in one cell solution (for GSM and UMTS) or single frequency network
(for LTE) is implemented. The 2 x 40 W 2T2R RRU is used. In this way, the TX power per cell remains unchanged. The connection mode remains unchanged.
Figure 3-6 Power splitting and co-cell
Scheme 4: Perform sector splitting for one network mode and add antennas.
Reconstruction description: Three RRUs are added (If 2T4R RRUs are used, the number of RRUs remains unchanged). Three antennas are added.
Hardware Reconstruction Scheme (Single-Mode or Multi-Mode High- and Low-Band)

The following table lists the single-mode or multi-mode high- and low-band hardware reconstruction schemes.
Original Network Scheme No. Typical Sector-Splitting Solution Recommended/Alternative
GSM 900 MHz & UMTS 2100 MHz Scheme 1 Perform sector splitting for the high-band only, use the high-band split and low-band non-split Recommended
UMTS 900 MHz & UMTS 2100 MHz antenna (no antenna is added) and the 2T4R RRU (the number of RRUs remain unchanged).
Scheme 2 Perform concurrent high- and low-band sector splitting and use the high- and low-band split Alternative
antenna (no antenna is added). If the antenna performance of the high- and low-band antenna does
not meet expectations, the 2T4R RRU is recommended (the number of RRUs remains unchanged).
Scheme 3 Perform sector splitting for high- or low-band, use the common antenna, add high- or low-band Alternative
split antenna (the number of antennas increases), and use the 2T4R RRU (The number of RRUs
remains unchanged).
Scheme 4 Perform concurrent high- and low-band sector splitting, use the high-band and low-band split Alternative
antenna (the number of antennas increases) and the 2T4R RRU (the number of RRUs remain
unchanged).
Scheme 1: Perform sector splitting for high-band only without adding antennas
Reconstruction description: Three RRUs are added (If 2T4R RRUs are used, the number of RRUs remains unchanged). The original antenna is replaced with the high-band split low-band non-split
antenna.
Figure 3-8 Hardware reconstruction scheme 1 for high- and low-band sector splitting
Scheme 2: Perform concurrent high- and low-band sector splitting or perform sector splitting for only one band and enable the multiple RRUs in one cell solution for the other band without
adding antennas.
The antenna networking mode and connections are the same for both methods. You can configure whether to enable sector splitting on the BBU.
Reconstruction description: Three RRUs are added for a single mode or a single band. Six RRUs are added for multiple modes and multiple bands. If the 2T4R RRU is used, the number of RRUs remains
unchanged.
Figure 3-9 Hardware reconstruction scheme 2 for concurrent high- and low-band sector splitting
NOTE:
When a 2T4R RRU is used to support the six-sector solution, the GSM network does not support the RRUs in one cell solution in the left and right sectors. Therefore, the sector splitting solution can be used on the GSM network to ensure stable
KPIs. RRUs of other TX/RX mode do not have such restrictions.
The concurrent high- and low-band split antennas cannot generate the maximum capacity gains. Contact Huawei GTS engineers before using this scheme.
Scheme 3: Perform sector splitting for the high-band or low-band and add antennas.
Reconstruction description: Three RRUs are added (If 2T4R RRUs are used, the number of RRUs remains unchanged). Three antennas are added.
Scheme 4: Perform concurrent high- and low-band sector splitting, and add antennas.
Reconstruction description: Six RRUs are added (If 2T4R RRUs are used, the number of RRUs remains unchanged). Three high-band split antennas and three low-band split antennas are installed on the
rooftop.
Hardware Reconstruction Scheme (Hybrid-Mode High- and Low-Band)
The following table lists the hardware reconstruction schemes for GSM/UMTS/LTE high- and low-band hybrid networking:

(Typical hybrid networking scenario)
GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 Scheme 1 Perform sector splitting for the UMTS high-band network only and replace the Recommended
MHz co-antenna original antenna with a 10-port antenna (No antenna is added).
GSM 850 MHz & GSM+LTE 1800 MHz & UMTS 2100
Scheme 2 Perform sector splitting for the UMTS high-band network only and add the high- Recommended
MHz co-antenna
band split antenna.
Scheme 3 Perform sector splitting for the UMTS low-band network only and add the low- Recommended
band split antenna.
Scheme 4 Perform concurrent high- and low-band sector splitting and add high-band and Alternative
low-band split antennas.
GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz & Scheme 5 Perform sector splitting for only the UMTS high-band or low-band, and add a Recommended
LTE 2600 MHz co-antenna. The GSM+UMTS 850 MHz shares an high-band or low-band split antenna.
RRU, and the GSM 1800 MHz and the UMTS 2100 MHz share an
RRU. Scheme 6 Perform sector splitting for both the high-and low-band UMTS networks and add Alternative
high-band and low-band split antennas.
(Typical hybrid networking scenario)
In antenna integration scenarios, single band splitting is supported, Scheme 7 Replace two antennas with a multi-port antenna and add a split antenna to perform Recommended
for example, the GSM 850 MHz and the UMTS 2100 MHz share an sector splitting.
antenna, and the LTE 2600 MHz uses an antenna.
In antenna integration scenarios, two antennas support high- and low- Scheme 8 The 10 or 8-port antenna and split antenna are used to support high- and low-band Recommended
band sector splitting and LTE 4T. sector splitting and LTE 4T.
Scheme 1 (GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz or GSM+LTE 1800 MHz & UMTS 2100 MHz co-antenna): Perform sector splitting for the high-band UMTS
network only and use the 10-port antenna. No antenna is added.
Reconstruction description: Three RRUs are added, and no antenna is added.
Figure 3-12 shows the typical networking. The LTE 1800 MHz uses 4T MIMO, the UMTS 2100 MHz uses a split antenna, and the GSM 850 MHz is also deployed.
Figure 3-12 Hardware reconstruction scheme 1 for hybrid network modes and frequency bands (10-port antenna and sector splitting for the high-band UMTS network)
Scheme 2 (GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz or GSM 850 MHz & GSM+LTE 1800 MHz & UMTS 2100 MHz co-antenna): Perform sector splitting for the high-
band UMTS network only and add antennas.
Reconstruction description: Three RRUs are added, and three high-band split antennas are added.
Figure 3-13 Hardware reconstruction scheme 2 for hybrid network modes and frequency bands (sector splitting for the high-band UMTS network)
Scheme 3 (GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz or GSM 850 MHz & GSM+LTE 1800 MHz & UMTS 2100 MHz co-antenna): Perform sector splitting for the low-
band network only and add antennas.
Reconstruction description: Six RRUs are added, and three low-band split antennas are added.
Figure 3-14 Hardware reconstruction scheme 3 for hybrid network modes and frequency bands (sector splitting for the low-band network)
Scheme 4 (GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz or GSM 850 MHz & GSM+LTE 1800 MHz & UMTS 2100 MHz co-antenna): Perform concurrent high- and low-
band sector splitting and add antennas.
Reconstruction description: Nine RRUs are added. The low-band dual-mode SDRs or single-band single-mode RRUs can be used (If 2T4R RRUs are used, three RRUs need to be added). Three high-
band and low-band split antennas are added.
Figure 3-15 Hardware reconstruction scheme 4 for hybrid network modes and frequency bands (sector splitting for the high-band and low-band network)
Scheme 5 (GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz & LTE 2600 MHz co-antenna): Perform sector splitting for the low-band network or the high-band UMTS network.
Reconstruction description: Three RRUs are added, and three split antennas are added.
Impact: After sector splitting, the uplink and downlink power of GSM 1800 MHz and UMTS 2100 MHz increase by 0.5 dB because the combiner is removed.
Figure 3-16 Hardware reconstruction scheme 5 for hybrid network modes and frequency bands (sector splitting for the low-band or high-band UMTS network)
Scheme 6 (GSM+UMTS 850 MHz & GSM 1800 MHz & UMTS 2100 MHz & LTE 2600 MHz co-antenna): Perform concurrent high- and low-band sector splitting on the UMTS network and
add antennas.
Reconstruction description: Nine RRUs are added (If 2T4R RRUs are used, only three RRUs need to be added). Three high-band and low-band split antennas are added.
Impact: After sector splitting, the uplink and downlink power of GSM 1800 MHz and UMTS 2100 MHz increase by 0.5 dB because the combiner is removed.
Figure 3-17 Hardware reconstruction scheme 6 for hybrid network modes and frequency bands (sector splitting for the high-band and low-band UMTS network)
Scheme 7 (In antenna integration scenarios, for example, the GSM 850 MHz and the UMTS 2100 MHz share an antenna, and the LTE 2600 MHz uses an antenna): Replace two antennas with
one multi-port antenna, and add a split antenna for sector splitting.
Reconstruction description: Three RRUs are added (If 2T4R RRUs are used, the number of RRUs remains unchanged). The GSM 850 MHz and LTE 2600 MHz shares an antenna, and the UMTS 2100
MHz uses a split antenna. The number of antennas remains unchanged.
Figure 3-18 Hardware reconstruction scheme 7 for hybrid network modes and frequency bands (Multi-port antenna)
Scheme 8 (In antenna integration scenarios, two antennas support high- and low-band sector splitting and LTE 4T): Two antennas are used for all high- and low-band network modes and
support high- and low-band sector splitting and LTE 4T).
Reconstruction description: In a typical integration scenario, sector splitting is performed for the GSM 1800 MHz and the UMTS 2100 MHz networks. 4T is available for the LTE 2600 MHz network.
Sector splitting is not performed for the LTE 700 MHz network that uses a 10-port antenna. A low-band split antenna is configured for the GSM+UMTS 900 MHz network. Only two antennas are used.
Impact: Combiner loss is about 0.5 dB.
Figure 3-19 Hardware reconstruction scheme 8 for hybrid network modes and frequency bands (Two antennas are integrated to cover multiple frequencies and modes)
Interoperation Policies
The following interoperation policies for the multi-mode multi-band six-sector co-antenna networking can reuse those for the multi-mode three-sector networking: Camping policies for UEs in idle mode,
redirection policies for UEs in connected mode, handover policies for UEs in the access phase, load balancing policies in the same network mode or between network modes.
If sector splitting is performed on the high-band but not on the low-band of a UMTS network, for example, the UMTS 2100 MHz becomes a six-sector network after sector splitting and the UMTS 900 MHz
remains to be the three-sector network, a heterogeneous multi-sector network is generated, see Figure 3-20.
Figure 3-20 Sector splitting for high-band only on a UMTS network
click to enlarge
In this case, suggestions for the interoperation policies are listed as follows:
Camping Policy
The UMTS 900 MHz has far better coverage than the UMTS 2100 MHz with the same antenna and RF parameter settings does. To ensure load balance, set parameters to enable UEs to preferentially
camp on the UMTS 2100 MHz. Specifically, set IDLEQOFFSET2SN on the UMTS 2100 MHz to 3 and IDLEQOFFSET2SN on the UMTS 900 MHz to -3.
The parameter settings can be modified based on the load on the UMTS 900 MHz and the UMTS 2100 MHz. If the load on the UMTS 900 MHz network becomes too high, increase the value of
IDLEQOFFSET2SN on the UMTS 900 MHz. Otherwise, decrease the value. The downlink load difference between two frequency bands must be within 10%.
Handover Policy
The coverage scope varies with inter-frequency bands because sector splitting is enabled on one frequency band but not on the other. The inter-frequency bands do not have blind handover relationships,
and therefore the DRD- or LDR-based inter-frequency blind handovers are not applicable in this scenario. Only the measurement-based LDR inter-frequency handovers can be performed.
The general rules for configuring blind handover policies are that blind handovers can be performed only between co-coverage cells or from overlapping cells with a small coverage area to cells with a
large coverage area.
For details about interoperation policies, contact Huawei technical support engineers.

The enhanced multi-sector features for each network mode must be enabled. For details about features and functions, see the multi-sector solution guide for a specific network mode, for example, UMTS Multi-
Sector Solution.
WRFD-030011 MIMO Prime With MIMO Prime, every signal from a cell is split into two signals, which are RAN13.0 MIMO Prime Feature Parameter Description
distributed to two respective PAs. In this way, two PAs are used for power TX of a
cell, thereby increasing the utilization of the PA. MIMO Prime can enhance signals
from HSDPA UEs to increase throughput of the HSDPA UEs and cell capacity.
N/A Inter-Frequency Mutual Aid When used in newly deployed dual-band networks or during transitions from RAN17.1 Inter-Frequency Mutual Aid Feature
single-band networks to dual-band networks, this feature provides 4RX for each Parameter Description
frequency band, requires fewer external combiners or antennas, thereby saving site TX Diversity and RX Diversity Feature
construction costs. Parameter Description
Inter-Frequency Mutual Aid depends on WRFD-010209 4-Antenna Receive
Diversity.
Besides enabling the enhanced multi-sector feature for multiple modes, you can enable the following features:
Inter-Frequency Mutual Aid

In GUL multiband, multi-sector and co-site scenarios, uplink 4RX can be achieved after the Inter-Frequency Mutual Aid feature is enabled. For details, see Inter-Frequency Mutual Aid Feature Parameter
Description.
WRFD-030011 MIMO Prime

In UMTS+LTE co-RRU and co-antenna scenarios, if the LTE network is enabled with the MIMO feature, the UMTS can be enabled with WRFD-030011 MIMO Prime. For details, see MIMO Prime
Feature Parameter Description.

3.2.1 Special Traffic Scenarios
Scenario 1: After sector splitting, traffic is imbalanced in two sectors under the left and right lobes of a split antenna
The multi-sector solution generates the maximum gains if the traffic is relatively balanced in each sector. However, on the GSM, UMTS, and LTE networks, traffic is relatively balanced only on 20% of
the networks, with the rest 70% being imbalanced and 10% being extremely imbalanced. Traffic imbalance affects the capacity gains and KPIs of the multi-sector solution. You need to identify the traffic
imbalance scenarios and adjust traffics on related network modes or frequency bands.
See the following figure.
Figure 3-21 Traffic imbalance between two sectors after sector splitting
click to enlarge
Scenario 2: After sector splitting, traffic is concentrated in the overlapping area.

If two sectors under the left and right lobes of a split antenna use the same frequency, severe co-channel interference will occur in the overlapping areas. If most users are in the overlapping area after
sector splitting, especially for stripped coverage, the capacity gains and KPIs will be affected on networks enabled with the multi-sector solution. You need to adjust traffics on related network modes and
frequency bands.
Figure 3-22 Traffic concentrated in the overlapping area after sector splitting
click to enlarge
3.2.1.2 Purpose
Before sector splitting, it is good practice to identify the special traffic scenario on different network modes and frequency bands and adjust the traffic distribution accordingly. If the special traffic scenario still
exists after adjustment, it is good practice not to perform sector splitting on the specific frequency band or in the specific network mode.

In the planning phase, adjust the sector azimuth or reconfigure RF parameters to modify the traffic distribution based on the traffic maps and engineering parameters of different network modes.
It is good practice not to perform sector splitting in sectors where traffic distribution cannot be adjusted or optimized.
In the planning phase, identify the traffic proportion in the soft handover (SHO) zone and reconfigure RF parameters to adjust the traffic distribution in the overlapping area.
It is good practice not to perform sector splitting in sectors where traffic distribution cannot be adjusted.
In multi-mode multi-band multi-sector joint plan and deployment scenarios, first determine the multi-sector reconstruction priorities of each frequency band or mode and then implement the reconstruction based
on the priorities. If the requirements for high-priority modes or bands and those for low-priority modes or bands cannot be both met, it is good practice not to perform sector splitting for network modes or
frequency bands with low reconstruction priorities.
For example, in the planning phase of sector splitting on a GSM 1800 MHz and UMTS 2100 MHz network, if the UMTS 2100 MHz provides higher capacity and does not have special traffic scenario after
optimization, it is recommended that sector splitting be performed on the UMTS 2100 MHz. You can optimize parameters on the GSM 1800 MHz. If the traffic is imbalanced in two sectors under the same split
antenna on the GSM 1800 MHz network, it is good practice not to perform sector splitting but to enable the multiple RRUs in one cell solution on the GSM 1800 MHz network.
Figure 3-23 Sector splitting policies in multi-band multi-mode special traffic scenarios
3.2.2 Multi-Mode Multi-Band Co-Antenna Scenarios

When the multi-sector solution is used in multi-mode multi-band scenarios, the multi-mode or multi-band co-antenna is required for sector splitting on, for example, high- and low-band UMTS networks or low-
band GSM and UMTS networks. The optimal parameter setting for different network modes or frequency bands are different, but the parameter settings need to be unified for different network modes or frequency
bands because they share the same antenna.
3.2.2.2 Purpose
In multi-mode multi-band multi-sector co-antenna scenarios, the optimal parameters settings vary with frequency bands and network modes. You need to determine the priorities for different network modes or
frequency bands and preferentially meet the requirements of high-priority network modes or frequency bands even if this will adversely affect the performance of other network modes or frequency bands.

This solution provides the plan and optimization principles in multi-mode multi-band multi-sector co-antenna scenarios.
Priority principles:
The priorities of different network modes and frequency bands are determined based on traffic distribution, customer suggestions, coverage continuity, and traffic growth and evolution. The performance
of high-priority network modes and frequency bands is preferentially ensured and that of other modes and bands is also considered.
The plan and optimization of non-high-priority network modes and frequency bands are performed on the basis that the performance target of the high-priority network modes and frequency bands are
achieved. After several rounds of optimization, if the performance target of non-high-priority network modes or frequency bands cannot be achieved, you need to determine whether to lower the
performance target of high-priority network modes and frequency bands. If the performance target cannot be lowered, the latest plan and optimization result can be the final result. Otherwise, you can
continue optimizing the network performance of different network modes and frequency bands.
Plan & Optimization rule:

Preferentially modify the internal parameters (for example, cell-level parameters such as pilot power and handover parameters) of different network modes and frequency bands. If the optimization target
cannot be achieved, modify the common parameters such as the electrical tilt, mechanical tilt, azimuth, antenna installation height, and antenna model.
3.2.3 Special Clutter Scenarios

In complex dense urban areas, the interference is difficult to control due to complex clutter environment. KPIs deteriorate by 30% to 50% when the multi-sector solution is implemented.
For special clutters, such as high-speed railways, highways, cross-river bridges, you can identify the special clutters and determine whether to implement the multi-sector solution based on site conditions.
In special clutter scenarios, the challenges are the same for different frequency bands and network modes. For definitions of special clutters, see the multi-sector solution guide for a specific network mode, for
example, UMTS Multi-Sector Solution.
3.2.3.2 Purpose
This solution improves KPIs of the multi-sector network in complex dense urban areas.
For special clutters, such as high-speed railways, highways, cross-river bridges, you can identify the special clutters and determine whether to implement the multi-sector solution based on site conditions.

In special clutter scenarios, challenges for different network modes and frequency bands are basically the same. For details, see the multi-sector solution guide for a specific network mode, for example, UMTS
Multi-Sector Solution.

The enhanced or mapping multi-sector features for each network mode must be enabled. For details about features and functions, see the multi-sector solution guide for a specific network mode, for example,
UMTS Multi-Sector Solution.
N/A Inter-Frequency Mutual Aid RAN17.1 Inter-Frequency Mutual Aid Feature Parameter Description
TX Diversity and RX Diversity Feature Parameter Description
ASFN Adaptive SFN
CDU Complex Dense Urban
DU Dense Urban
GSM Global System for Mobile Communications
LTE Long Term Evolution
GUL GSM, UMTS, LTE
KPI Key Performance Indicator
RRU Remote Radio Unit
SDR Software-defined Radio
SFN Single Frequency Network

1. MIMO Prime Feature Parameter Description

2. UMTS Multi-Sector Solution
3. Inter-Frequency Mutual Aid Feature Parameter Description
4. TX Diversity and RX Diversity Feature Parameter Description
WCDMA RAN
UMTS HetNet Macro-Micro Network Solution Guide
Issue 02
Date 2016-06-23

Notice

1.4.2 Contents
1.1 Scope
1.3 Change History
2 Overview
2.1 Background
3.1 Scenario 1: Filling Coverage Holes
3.1.4 Application Guidelines
3.1.4.1 Mobility Policy
3.1.4.2 Load Balancing Policy
3.1.4.3 Interference Control Policy
3.2 Scenario 2: Offloading Hotspot Traffic
3.2.1 Scenario Definition
3.2.4.2 Load Balancing Policy (Service Steering on the Macro Network)
3.2.4.3 Load Balancing Policy (No Service Steering on the Macro Network)
1.1 Scope
1.3 Change History
1.1 Scope
This document describes Huawei HetNet solutions for UMTS networks in different scenarios.

Need to understand the solutions described herein

Maintain Huawei products
1.3 Change History

RAN18.1 02 (2016-06-23)
Compared with Issue 01 (2016-02-29) of RAN18.1, Issue 02 (2016-06-23) of RAN18.1 adds the description of the BookRRU.
RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Compared with Issue 01 (2015-04-20) of RAN17.1, Draft A (2015-12-30) of RAN18.1 adds the description of the BTS3911E.
2 Overview
2.1 Background
2.1 Background
The explosive growth of users requires macro networks to provide wider network coverage and larger network capacity. However, new sites are difficult to acquire and people's awareness of environmental
protection increases. In this situation, operators call for a radio networking solution that has low site requirements and can be deployed quickly to fill coverage holes and expand network capacity. Due to limited
frequency resources, this radio networking solution must utilize the existing frequencies of macro networks.
In this mobile broadband era requiring continuous capacity expansion, the heterogeneous network (HetNet) that layers coverage, frequency bands, and RATs has become an optimal choice for mainstream operators
all around the world.

Huawei HetNet solution covers multiple RATs and products. This document describes the simple base station solution for UMTS networks.
Huawei UMTS simple base stations include the micro base station, BookRRU, and Easy Macro.
A micro base station integrates the functions of a BBU, an RRU, and an antenna. The single-carrier power of a micro base station is less than 5 W. Micro base stations include BTS3902E, BTS3803E, and
BTS3911E.
A BookRRU, as well as an Easy Macro, integrates the functions of an RRU and an antenna, and it must be connected to a BBU. The single-carrier power of a BookRRU is less than 5 W. The products of
BookRRU include RRU3930E. The single-carrier power of an Easy Macro can be greater than 20 W. The products of Easy Macro include AAU3940.
In the Huawei HetNet solution, UMTS simple base stations can be used for:
Filling coverage holes: Apart from their light weight and small sizes, simple base stations support various transmission modes. They can be easily camouflaged and flexibly deployed to improve outdoor
and indoor coverage in areas such as commercial streets, residential areas, campuses, small-sized office buildings, and hotels.
Offloading hotspot traffic: Simple base stations can be deployed in traffic hotspots to offload some traffic from macro networks, thereby improving user experience in both macro cells and micro cells.

In Huawei HetNet solutions, micro and macro base stations can work on the same frequency or different frequencies.
In inter-frequency networking, operators must plan separate frequencies for simple base stations. Inter-frequency networking yields better performance than intra-frequency networking.
Intra-frequency networking allows operators to utilize the existing frequency spectrum resources to the utmost. The WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control feature can be enabled to
minimize macro-micro uplink interference.
Figure 2-1 HetNet networking
click to enlarge


In this scenario, simple base stations are used to improve signal strength in weak coverage areas, that is, areas with the received signal code power (RSCP) less than -95 dBm. Table 3-1 lists typical areas.
Table 3-1 Typical areas
Outdoor or Indoor Typical Areas Scenario Description
Outdoor Streets Non-arterial roads, along which signals are blocked by buildings and macro coverage is weak
Residential areas Areas with weak coverage indoors and outdoors because macro site acquisition is discouraged by residents
Islands Isolated and small villages in suburbs with few traffic requirements
Indoor Small-sized hotels and office buildings Small- or medium-sized buildings for which the DAS system is difficult to be deployed. Such buildings have weak
coverage or coverage holes. Simple base stations can be deployed around to provide indoor coverage.
Small- or medium-sized supermarkets and shopping Spacious buildings with a single-floor area of 1000-3000 square meters. Micro base stations or BookRRU can be
malls deployed indoors.

Simple base stations can be flexibly deployed around target areas in a way that their signals bypass obstacles from high-rise buildings or terrain restraints but directly cover the target areas, thereby effectively
improving the RSCP and Ec/Io. The small size, light weight, easy camouflage, and ability to support multiple transmission modes of micro base stations make the flexible deployment possible.

Feature List
Table 3-2 lists the features to be deployed when micro base stations are used for filling coverage holes.
Table 3-2 Features
WRFD-150201 Macro & Micro Co-carrier Uplink RAN15.0 Macro and Micro Co-carrier Uplink Interference Control Feature Parameter Description
Interference Control
WRFD-020106 Load Reshuffling RAN2.0 Load Control Feature Parameter Description
WRFD-020302 Inter Frequency Hard Handover Based RAN2.0 Handover Feature Parameter Description
on Coverage
Feature Description
Table 3-3 describes the functions of involved features.
Table 3-3 Feature description
Feature ID Feature Name Function in the Solution
WRFD-150201 Macro & Micro Co-carrier Uplink Its sub-feature Micro Cell Dynamic Rx Sensitivity Control is used to eliminate uplink interference caused by UEs in macro cells to micro cells
Interference Control and resolve uplink out-of-synchronization in soft handover (SHO) areas between macro and micro cells in intra-frequency networking. The
out-of-synchronization is caused by power difference between macro and micro cells.
WRFD-020106 Load Reshuffling Allows load-based handovers between multiple carriers configured for a micro base station.
WRFD-020302 Inter Frequency Hard Handover Based Allows coverage-based inter-frequency hard handovers between inter-frequency macro and micro cells. Such handovers are required when the
on Coverage macro and micro base stations have different carriers, for example, a single-carrier micro base station is used to fill coverage holes for a dual-
carrier macro base station.

The planning of mobility, load balancing, and interference control policies in this scenario requires coordination between multiple features. The following description applies both to indoor and outdoor scenarios
for filling coverage holes.
Micro Cell Single-Carrier Networking

Single-carrier base stations are deployed in the coverage holes of the macro network to provide continuous coverage together with the macro network.
As shown in Figure 3-1, neighbor relationship is configured between intra-frequency micro cells and between intra-frequency micro and macro cells, and the reselection offset specified by
IdleQoffset2sn/IdleQoffset1sn and handover offset specified by CIOOffset are set to 0, to allow random camping for UEs in idle mode and soft handovers for UEs in connected mode.
Figure 3-1 Camping policy for single-carrier networking
click to enlarge
Micro Cell Multi-Carrier Networking

Table 3-4 Suggestions on multi-carrier networking for different types of base stations
Base Station Type Number of Carriers Networking Suggestion
BTS3911E Supports a maximum of four carriers. For macro base stations configured with two or more carriers, it is recommended that macro base stations have the same number of carriers
and networking policy as neighboring macro base stations to ensure continuous coverage between macro carriers and carriers of
neighboring macro base stations.
BookRRU Supports a maximum of four carriers. For macro base stations configured with two or more carriers, it is recommended that macro base stations have the same number of carriers
EasyMacro Supports a maximum of six carriers. For macro base stations configured with two or more carriers, it is recommended that Easy Macro base stations have the same number of
carriers and networking policy as neighboring macro base stations to ensure continuous coverage between Easy Macro carriers and carriers
of neighboring macro base stations.
During coverage hole filling, dual-carrier micro base stations can be used in hotspots with weak coverage or coverage holes, for example, some densely populated shopping malls that require high traffic but
receive weak signals from the micro network because no DAS is deployed.
Camping policy
As shown in Figure 3-2, micro cells are configured as neighboring cells, the reselection offset specified by IdleQoffset2sn/IdleQoffset1sn and handover offset specified by CIOOffset are set to 0, and
random camping is adopted.
Figure 3-2 Camping policy after dual-carrier micro base station deployment
click to enlarge
Handover policy
Soft handovers between intra-frequency micro cells and between intra-frequency macro and micro cells
Blind handover- or measurement-based inter-frequency handovers (WRFD-020106 Load Reshuffling) between inter-frequency micro cells
Coverage-based inter-frequency hard handovers (WRFD-020302 Inter Frequency Hard Handover Based on Coverage) between inter-frequency macro and micro cells if macro and micro cells on
the same frequency (for example, f2 in Figure 3-3) do not provide continuous coverage.
When a UE moves from a macro cell at f1 to a micro cell, an intra-frequency handover, but not coverage-based inter-frequency hard handover from a macro cell at f1 to a micro cell at f2, is
required.
Figure 3-3 Handover policy after dual-carrier micro base station deployment
click to enlarge
3.1.4.2 Load Balancing Policy
When a micro base station is used for filling coverage holes, load balancing policies are required only when the micro base station is configured with multiple carriers. Inter-frequency load-based handovers
(WRFD-020106 Load Reshuffling) are required between inter-frequency micro cells in high-traffic areas.
As shown in Figure 3-4, no macro cells are deployed at f2 and therefore micro cells at f2 provide better coverage than those at f1. In this case, measurement-based handovers, but not blind handovers, are allowed
from f2 to f1.
Figure 3-4 Load balancing policy after dual-carrier micro base station deployment
click to enlarge

When filling coverage holes, micro base stations are deployed in areas with poor macro coverage. Therefore, downlink interference from macro cells to micro cells is little.
If there are multiple UEs at the boundary between macro and micro cells, UEs in macro cells may cause severe uplink interference to micro cells and it is good practice to enable WRFD-15020103 Micro Cell
Dynamic Rx Sensitivity Control.

3.2.1 Scenario Definition
In this scenario, micro base stations are deployed in hotspots where the high traffic is beyond the macro network capacity. Typical areas are dense urban areas, such as walking streets, stations, commercial squares,
and large-sized shopping malls and office buildings without the DAS. The following table lists typical areas.
Table 3-5 Typical areas for traffic offload
Outdoor or Indoor Typical Areas Description
Outdoor Commercial streets and walking streets Bustling and dense areas with extremely high traffic that is beyond the macro network capacity
Municipal squares and leisure squares Dense areas in nonworking hours, especially during holidays and important celebrations, at which time the high
traffic is beyond the macro network capacity
Indoor Dining halls and cafes along the streets Stores that are located along the street and often without the DAS. During meal time, these stores accommodate a
large number of customers and high data traffic is generated, sharply burdening the macro network.
Small- or medium-sized supermarkets and shopping malls Spacious buildings with a single-floor area of 1000-3000 square meters. These areas have high traffic but weak
coverage because the property management often opposes the DAS deployment.

Deploying simple base stations in traffic hotspots of a macro network helps effectively lessen the load of macro cells and improve user experience.
In addition, the deployment increases available power resources and code resources to improve the entire network capacity and allow operators to attract more users.

Feature List
Table 3-6 lists the features to be deployed when simple base stations are used for offloading hotspot traffic.
Table 3-6 Feature list
WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control RAN15.0 Macro and Micro Co-carrier Uplink Interference Control Feature Parameter
Description
WRFD-150246 Service Steering and Load Sharing in CELL_FACH State RAN16.0 Service Steering and Load Sharing in CELL_FACH State Feature Parameter
Description
WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load RAN14.0 Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature
Threshold Parameter Description
WRFD-020400 DRD Introduction Package RAN10.0 Directed Retry Decision Feature Parameter Description
WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup RAN11.0 Load Control Feature Parameter Description
Enhancement
Feature Description
Table 3-7 describes the functions of involved features.
Table 3-7 Feature description
WRFD-150201 Macro & Micro Co-carrier Uplink Interference Identifies whether UEs exist in macro-micro problem areas, that is, areas with uplink and downlink unbalance arising from transit
Control power differences between macro and micro cells. The unbalance results in strong uplink interference caused by UEs in macro cells to
micro cells as well as uplink out-of-synchronization in soft handover areas between macro and micro cells.
If this feature detects UEs in the problem areas, the Macro & Micro Joint Inter-frequency Redirection and Macro & Micro Joint Inter-
frequency Handover features will be applied to transfer the UEs to an inter-frequency carrier with no micro cells. If some UEs remain
in the problem areas, the Micro Cell Dynamic Rx Sensitivity Control feature will be used to perform uplink desensitization for micro
cells, thereby resolving uplink out-of-synchronization and eliminating uplink interference caused by UEs in macro cells to micro cells.
If no UEs camp on the problem areas, uplink desensitization for micro cells is canceled.
WRFD-150246 Service Steering and Load Sharing in Enables the RNC to distribute non-real-time services to non-preferential camping frequencies (including frequencies that do not share
CELL_FACH State the coverage with preferential camping frequencies) when the RNC on a preferential camping frequency receives a cell update request
from a UE in the URA_PCH or CELL_PCH state.
WRFD-020106 Load Reshuffling Balances load between inter-frequency macro cells and between inter-frequency macro and micro cells.
WRFD-140217 Inter-Frequency Load Balancing Based on Balances load between inter-frequency macro cells.
Configurable Load Threshold
WRFD-020400 DRD Introduction Package Performs service steering-based inter-frequency DRD and HSDPA user quantity-based inter-frequency DRD.
WRFD-020120 Service Steering and Load Sharing in RRC Performs service steering-based RRC redirections for HSPA services.
Connection Setup Enhancement

The planning of mobility, load balancing, and interference control policies in this scenario requires coordination between multiple features. The following description applies both to indoor and outdoor scenarios
for offloading hotspot traffic.
Camping policy
As shown in Figure 3-5, adjacent micro cells and intra-frequency macro and micro cells apply random camping.
In order for micro cells to offload more traffic from the macro network with two or more carriers, preferential camping from inter-frequency macro cells to micro cells can be enabled. Preferential
camping is controlled by parameter settings. As shown in Figure 3-5, to enable preferential camping from a macro cell at f2 to a micro cell at f1, increase the value of IdleSintersearch for the macro cell
and decrease the reselection offset specified by IdleQoffset2sn.
Figure 3-5 Camping policy after single-carrier micro base station deployment
click to enlarge
Handover policy
Measurement-based inter-frequency handovers (WRFD-020106 Load Reshuffling) between inter-frequency macro and micro cells
If blind handovers, for example, bidirectional blind handovers between macro cells at f1 and macro cells at f2 shown in Figure 3-6, are supported on the macro network before the micro base
station deployment, blind handovers from macro cells at f2 to macro cells at f1 must be disabled after the micro base station deployment. This is because the blind handovers may fail.
Figure 3-6 Camping policy after single-carrier micro base station deployment
click to enlarge

Camping policy
Random camping is used between inter-frequency or intra-frequency micro cells and between inter-frequency or intra-frequency macro and micro cells. As shown in Figure 3-7, micro cells are deployed
at three or more carriers of the macro network. Preferential camping from inter-frequency macro cells to micro cells can also be enabled so that micro cells can offload more traffic.
Figure 3-7 Camping policy after dual-carrier micro base station deployment
click to enlarge
Handover policy
Blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) between inter-frequency micro cells
As shown in Figure 3-8, micro cells are deployed at three or more carriers of the macro network. In this case, measurement-based inter-frequency handovers (WRFD-020106 Load Reshuffling)
are supported between inter-frequency macro and micro cells.
Figure 3-8 Handover policy after dual-carrier micro base station deployment
click to enlarge
3.2.4.2 Load Balancing Policy (Service Steering on the Macro Network)

Figure 3-9 shows the typical macro networking for service steering when micro base stations are not deployed. After micro base station deployment, the service steering policy of the macro network must be
adjusted. The following describes the macro-micro load balancing policies when the cell is configured with different numbers of carriers.
Figure 3-9 Traffic steering on the macro network
click to enlarge

As shown in Figure 3-10, coverage at different frequencies differs after micro base station deployment. In this case, service steering-based inter-frequency DRD (WRFD-020400 DRD Introduction Package) cannot
be initiated from macro cells at f3 to macro or micro cells at f2. Only service steering-based RRC redirections (WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup Enhancement) for
HSPA services are allowed.
If WRFD-020500 Enhanced Fast Dormancy is enabled, some UEs remain in the CELL_PCH state after data transmission is complete. In this case, WRFD-150246 Service Steering and Load Sharing in
CELL_FACH State needs to be enabled to redirect these UEs to carriers that preferentially carry HSPA services.
HSDPA user quantity-based inter-frequency DRD (WRFD-020400 DRD Introduction Package) to macro cells at f1 can be triggered for HSPA services that are redirected to macro cells at f2.
Service steering-based inter-frequency DRD (WRFD-020400 DRD Introduction Package) to macro cells at f1 can be triggered for HSPA services that remain in macro cells at f3 after redirection failures.
Figure 3-10 Load balancing policy on service steering networks
click to enlarge

As shown in Figure 3-11, f1 and f2 still provide the same coverage after dual-carrier micro base station deployment. Therefore, HSDPA user quantity-based inter-frequency DRD (WRFD-020400 DRD
Introduction Package) to f1 can be triggered for HSPA services that are redirected from f3 to f2. In addition, blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) can be triggered
between f1 and f2.
Figure 3-11 Load balancing policy on service steering networks
click to enlarge
3.2.4.3 Load Balancing Policy (No Service Steering on the Macro Network)
When the Macro Network Is Configured with Two Frequencies
As shown in Figure 3-12, before micro base station deployment, blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) are used between inter-frequency macro cells.
After a micro base station is deployed at f1, macro cells at f1 and macro cells at f2 do not provide the same coverage. As a result, blind handover-based inter-frequency handovers are not allowed from macro cells
at f2 to macro cells at f1. Instead, measurement-based inter-frequency handovers (WRFD-020106 Load Reshuffling) are allowed only from macro cells at f2 to macro cells at f1 and from micro cells at f1 to macro
cells at f2.
Figure 3-12 Load balancing policy after single-carrier micro base station deployment
click to enlarge
When the Macro Network Is Configured with Three Frequencies
As shown in Figure 3-6, before micro base station deployment, blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) are used between inter-frequency macro cells when the macro
network is configured with three frequencies.
After micro base station deployment, measurement-based inter-frequency handovers are allowed from macro cells at f2 to macro cells at f1 and blind handover-based inter-frequency handovers are allowed from
macro cells at f2 to macro cells at f3. LDR from macro cells at f2 to macro cells at f1 is not allowed because a cell cannot support two LDR modes simultaneously (WRFD-020106 Load Reshuffling). In this case,
CLB (WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load Threshold) can be used between macro cells at f2 and those at f1.
Figure 3-13 Load balancing policy after single-carrier micro base station deployment
click to enlarge

When the Macro Network Is Configured with Two Frequencies
As shown in Figure 3-14, the only two frequencies still provide the same coverage after a dual-carrier micro base station is deployed and therefore no adjustment is required for load balancing policies of the macro
network. In addition, blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) can be triggered between inter-frequency micro cells.
click to enlarge
When the Macro Network Is Configured with Three Frequencies

As shown in Figure 3-15, after a dual-carrier micro base station is added to a macro network configured with three or more frequencies, recommended load balancing policies are as follows considering
coverage differences between carriers:
Bidirectional blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) between co-coverage frequencies (f1 and f2, for example)
Unidirectional blind handover-based inter-frequency handovers (WRFD-020106 Load Reshuffling) between inter-frequency macro cells (those at f2 and those at f3, for example) with different
coverage areas
CLB-triggered handovers (WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load Threshold) from micro cells at f2 to macro cells at f3 and from macro cells at f3 to
macro cells at f2
click to enlarge
Problems When Macro and Micro Cells Work on the Same Frequency
When macro and micro cells work on the same frequency, co-channel interference causes the following problems:
Downlink interference
The transmit power of a micro cell is much lower than that of a macro cell. Due to downlink interference from the macro cell, the micro cell coverage shrinks.
Uplink interference in the following two aspects:
As shown in Figure 3-16, the primary serving cell of a UE at the macro-micro SHO area is a macro cell and both the macro and micro cell are in the active set. Due to uplink unbalance, the
uplink path loss to the micro cell is less than the path loss to the macro cell. Therefore, the micro cell plays the leading role in power control and requests the UE to reduce the transmit power to
meet the uplink signal-to-interference ratio (SIR) target of the micro cell. However, this also causes the SIR in the macro cell to become lower than its own target SIR. Consequently, the macro
cell cannot demodulate the uplink control channel of the UE correctly. The incorrect demodulation of the DPCCH causes uplink out-of-synchronization of the UE in the macro cell. The incorrect
demodulation of the HS-DPCCH that carries the ACK/NACK and CQI information increases the HSDPA retransmission rate and decreases the throughput.
Figure 3-16 Interference in the macro-micro SHO area
click to enlarge
As shown in Figure 3-17, the primary serving cell of a UE at the macro-micro SHO area is a macro cell and the micro cell has not been added to the active set. When the UE moves close to the
micro cell, the uplink quality provided by the micro cell becomes better than that provided by the macro cell but the micro cell cannot perform power control on the UE. As a result, the transmit
power of the UE causes strong uplink interference to the micro cell, decreasing uplink UE throughput and capacity in the micro cell.
Figure 3-17 Interference caused by a UE in a macro cell to a micro cell
click to enlarge
Interference Suppression When Macro and Micro Cells Work on the Same Frequency
The measures for co-channel interference are as follows:
Appropriately plan simple base station sites. Keep these sites away from areas where the RSCP of a macro network is greater than -65 dBm.
Huawei provides professional services of accurate site planning (ASP) to effectively plan micro sites.
Enable the WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control feature, which includes the following sub-features:
WRFD-15020101 Macro & Micro Joint Inter-frequency Redirection
WRFD-15020102 Macro & Micro Joint Inter-frequency Handover
The preceding sub-features are mainly used to identify UEs in macro-micro problem areas and transfer these UEs to an inter-frequency macro cell that has no intra-frequency neighboring micro
cells by means of redirections (for UEs in the RRC connection setup procedure) and blind handovers (for UEs in connected mode). This prevents UEs from performing services in the macro-
micro problem areas and reduces the desensitization probability for micro cells.
WRFD-15020103 Micro Cell Dynamic Rx Sensitivity Control
Upon detecting a UE in macro-micro problem area, this sub-feature is used to reduce the receive sensitivity for the micro cell to eliminate the uplink and downlink boundary unbalance between
macro and micro cells. This mitigates the uplink interference caused by the UE in the macro cell to the micro cell and increases the HSPA throughput for the UE in the problem areas. When no
UEs are detected in the problem areas, this sub-feature restores the originally configured receive sensitivity for the micro cell to reduce uplink interference to the macro cell.
Table 4-1 List of features involved in the solution
WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control RAN15.0 Macro and Micro Co-carrier Uplink Interference Control Feature Parameter Description
WRFD-020302 Inter Frequency Hard Handover Based on Coverage RAN2.0 Handover Feature Parameter Description
WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control RAN15.0 Macro and Micro Co-carrier Uplink Interference Control Feature Parameter Description
WRFD-150246 Service Steering and Load Sharing in CELL_FACH RAN16.0 Service Steering and Load Sharing in CELL_FACH State Feature Parameter Description
State
WRFD-140217 Inter-Frequency Load Balancing Based on Configurable RAN14.0 Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature
Load Threshold Parameter Description
WRFD-020120 Service Steering and Load Sharing in RRC Connection RAN11.0 Intelligent Access Control Feature Parameter Description
Setup
AAS active antenna system
ASP accurate site planning

CQI channel quality identifier
CLB Inter-Frequency Load Balancing Based on Configurable Load Threshold
CS circuit switched
DAS distributed antenna system
DPCCH Dedicated Physical Control Channel
HCS hierarchical cell structure
HSUPA High Speed Uplink Packet Access
LAC location area code
LDR load reshuffling
MIMO multi-input multi-output
MR measurement report
PS packet switched
RAC routing area code
RNC radio network controller
SAC serving area code
SHO soft handover
SON self-organizing network
UE user equipment

2. Directed Retry Decision Feature Parameter Description
3. Macro and Micro Co-carrier Uplink Interference Control Feature Parameter Description
4. Handover Feature Parameter Description
5. Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature Parameter Description
6. Service Steering and Load Sharing in CELL_FACH State Feature Parameter Description
WCDMA RAN
UMTS Multi-Carrier Solution Guide
Issue 01
Date 2015-04-20

Notice
1.4.3 Contents
1.1 Scope
1.3 Change History
2 Overview of the Solution
2.1 Background
2.2 Application scenarios
2.3.1 Policies Involved in the Solution
2.3.2 Recommended Solution
3.1 Scenario 1: Preferentially Guaranteeing Voice Services on Intra-Band Multi-Carrier Networks
3.2 Scenario 2: Preferentially Guaranteeing Data Services on Intra-Band Multi-Carrier Networks
3.3 Scenario 3: Taking Both Voice and Data Services into Account on Intra-Band Multi-Carrier Networks
3.4 Scenario 4: Preferentially Guaranteeing Voice Services on Inter-Band Multi-Carrier Networks
3.5 Scenario 5: Preferentially Guaranteeing Data Services on Inter-Band Multi-Carrier Networks
3.6 Scenario 6: Taking Both Voice and Data Services into Account on Inter-Band Multi-Carrier Networks
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the UMTS multi-carrier solutions provided by Huawei for different application scenarios.
details, see the corresponding feature parameter description documents.
NOTE:
Capacity expansion of carriers can solve the problem of air-interface resource insufficiency, whereas it cannot solve congestion problems caused by insufficiency of other resources (RNC resources, NodeB resources, and transmission resources). For details
about how to monitor network resources, see Capacity Monitoring Guide.

Need to understand UMTS multi-carrier solutions

1.3 Change History

RAN17.1 01 (2015-04-20)
Compared with Issue 01 (2014-05-15) of RAN16.0, Issue 01 (2015-04-20) of RAN17.1 includes the following changes:
The following functions are added to scenarios 4 to 6:
Terminal capability-based RRC inter-frequency redirections of only DC-HSDPA, 3C-HSDPA, and 4C-HSDPA terminals to cells enabled with DC-HSDPA, 3C-HSDPA, or 4C-HSDPA
WRFD-171214 Inter-Band Load Balancing
2 Overview of the Solution
2.1 Background
2.1 Background
Since carriers can be added to expand UMTS network capacity, multi-carrier networks can also expand. To provide better CS and PS data services on the multi-carrier networks, proper measures need to be taken,
including proper policies of camping, service steering (access mode), load balancing (access mode), and mobility management (connected mode).

When carriers are added for capacity expansion, the carriers added to a site can belong to the same frequency band or different frequency bands. After capacity expansion, a UMTS multi-carrier network can use
either of the following networking modes:
Intra-band multi-carrier networking

Inter-band multi-carrier networking
UMTS multi-carrier networks need to provide voice services and data services, for which the following guarantee policies can be used:
Preferentially guaranteeing voice services

Preferentially guaranteeing data services
Taking both voice and data services into account
Based on these policies, UMTS multi-carrier networking solutions are provided for the following scenarios:
Scenario 1: Preferentially guaranteeing voice services on intra-band multi-carrier networks

Scenario 2: Preferentially guaranteeing data services on intra-band multi-carrier networks
Scenario 3: Taking both voice and data services into account on intra-band multi-carrier networks
Scenario 4: Preferentially guaranteeing voice services on inter-band multi-carrier networks
Scenario 5: Preferentially guaranteeing data services on inter-band multi-carrier networks
Scenario 6: Taking both voice and data services into account on inter-band multi-carrier networks
NOTE:
This document complies with the following conventions:
Band I U2100/Band II U1900 is referred to as U2100. Band VIII U900/Band V U850 is referred to as U900. For frequency bands supported by UMTS, see 3GPP TS 25.101.
On intra-band multi-carrier networks, carriers are indicated by F1, F2, and F3. On inter-band multi-carrier networks, high-band carriers are indicated by U2100 F1, U2100 F2, and U2100 F3, and low-band carriers are indicated by U900 F1 and
U900 F2.
In intra-band scenarios, it is assumed that F1 and F2 provide contiguous coverage and F3 provides discontiguous coverage.
In inter-band scenarios, it is assumed that U2100 F1, U2100 F2, and U900 F1 provide contiguous coverage, and U2100 F3 and U900 F2 provide discontiguous coverage.

2.3.1 Policies Involved in the Solution
Each solution corresponding to an application scenario involves the following policies:
Camping policies
Camping policies specify how UEs in connected mode (URA_PCH, CELL_PCH, and CELL_FACH) and UEs in idle mode (IDLE) select carriers to camp on. Camping policies can be classified into the
following types:
Random camping: A UE can camp on any carrier and select the best cell based on the Ec/N0.
Preferred camping: A UE preferentially camps on one or multiple specific carriers. When preferred camping works with the function Redirection at RRC Connection Release, UEs can quickly
return to their camping carriers. This policy is usually used with access mode policies.
Access mode polices

Access mode polices specify how UEs select carriers on different bands when setting up calls.
The access state is a temporary state in which a UE in idle mode has accessed the network before the CELL_DCH state. P2D and F2D states, which enable UEs to enter the CELL_DCH state directly, are
also called the access state. The access mode policies can be classified into the following types:
Direct access to the local cell
Layered access to another cell through DRD based on the HSPA+ technology fulfillment rate
Terminal capability-based RRC inter-frequency redirections of only DC-HSDPA, 3C-HSDPA, and 4C-HSDPA terminals to cells enabled with DC-HSDPA, 3C-HSDPA, or 4C-HSDPA
Layered access to another cell through redirection based on services
Layered access to another cell through DRD based on services
Layered access to another cell through redirection based on load
Layered access to another cell through DRD based on load
NOTE:
Redirection here refers only to redirection in the RRC connection setup stage.
DRD includes those in the RAB setup stage, F2H stage, and P2D stage.
Connected mode policies
Connected mode policies specify how UEs in CELL_DCH state perform handovers between carriers. They are divided into the following types:
Load-based inter-frequency handover
Coverage-based inter-frequency handover
The RNC implements inter-band load balancing for scenarios 4 through 6.
In the inter-band load balancing mechanism, the RNC automatically adjusts parameter settings for UEs in idle mode, access mode, and connected mode based on load differences between U900/850 cells
and U2100 cells on live networks. The adjustment is to avoid heavy load in U900/850 cells.
2.3.2 Recommended Solution

Table 2-1 lists solutions that are recommended for different scenarios. The solutions for all scenarios allow parameters for UEs in idle mode, access mode, and connected mode to be adaptively adjusted to achieve
load balancing between carriers on different frequencies. Only scenarios 4 through 6 support inter-band load balancing.
Table 2-1 Recommended multi-carrier solutions
Scenario Solution Purpose Camping Policy Access Mode Policy Connected Mode Policy
Scenario 1 Carrying voice and data services Have UEs in idle mode, Have UEs performing voice services or combined services access the Load-based inter-frequency handover
on different bearers to reduce CELL_PCH state, and local cell directly. Coverage-based inter-frequency handover
impacts of data services on KPIs URA_PCH state preferentially Data services:
of voice services camp on F1.
Layered access to another cell through DRD based on the
Have UEs in CELL_FACH HSPA+ technology fulfillment rate
state camp on their original
Layered access to another cell through DRD based on
carriers.
services
Have UEs quickly return to F1
through the function
Redirection at RRC Connection
Release.
Scenario 2 Balancing carrier resources, Have UEs camp on F1, F2, or F3 Have UEs performing voice services or combined services access the Load-based inter-frequency handover
maximizing network capacity, randomly local cell directly. Coverage-based inter-frequency handover
and providing better data Data services:
services
HSPA+ technology fulfillment rate
Scenario 3 Taking both voice and data Have UEs in idle mode, Have UEs performing voice services or combined services access the Load-based inter-frequency handover
services into account, reducing CELL_PCH state, and local cell directly. Coverage-based inter-frequency handover
inter-frequency handovers of URA_PCH state preferentially Data services:
voice services, and enabling camp on F1.
HSPA UEs to use all carrier Layered access to another cell through DRD based on the
Have UEs in CELL_FACH HSPA+ technology fulfillment rate
resources state camp on their original
carriers.
Have UEs quickly return to F1
through the function
Redirection at RRC Connection
Release.
Scenario 4 Carrying voice and Have UEs preferentially camp Have UEs performing voice services or combined services access the Load-based inter-frequency handover
data services on on U2100 F1 when selecting local cell directly. (recommended for data services)
different bearers of between U2100 carriers. Data services: Blind handover between U2100
high-band carriers to Have UEs in idle F1, U2100 F2, and U2100 F3
Between U2100 cells:
reduce impacts of data mode, CELL_PCH Layered access to another cell through DRD based on the Blind handover when the U900
services on KPIs of state, and URA_PCH HSPA+ technology fulfillment rate cell and U2100 cell share the
voice services state preferentially
Layered access to another cell through DRD based on same sector and use the same
Guaranteeing camp on F1. azimuth
contiguous coverage services
Have UEs in Measurement-based handover
with low-band carriers Layered access to another cell through DRD based on load
CELL_FACH state when the U900 cell and U2100
so that all UEs can use camp on their original When the U900 cell and U2100 cell share the same sector
cell share the same sector but use
all carriers carriers. and use the same azimuth:
different azimuths
Have UEs quickly Layered access to another cell through DRD based on the
HSPA+ technology fulfillment rate Coverage-based inter-frequency handover
return to F1 through
the function Layered access to another cell through DRD based on load This type of handover is
Redirection at RRC When the U900 cell and U2100 cell share the same sector recommended when the UE tries
Connection Release. but use different azimuths: to be handed over from a U2100
cell to a U900 cell but not
Have UEs randomly camp on Layered access to another cell through redirection based on
recommended when the UE tries
U2100 F1 or U900 F1 when services
to be handed over from a U900
selecting between them. Terminal capability-based RRC inter-frequency redirection cell to a U2100 cell.
of only DC-HSDPA, 3C-HSDPA, and 4C-HSDPA terminals
to cells enabled with this technology NOTE:
This principle considers contiguous coverage of
the U900 band to avoid ping-pong handovers
between a U2100 cell and a U900 cell.
Scenario 5 Balancing the load between Have UEs randomly camp on Have UEs performing voice services or combined services access the Load-based inter-frequency handover
high-band carriers and low-band U2100 F1, U2100 F2, or local cell directly. (recommended for data services)
carriers to avoid an excessive U2100 F3 when selecting Data services: Blind handover between U2100
load of a specific band or between them.
Between U2100 cells: F1, U2100 F2, and U2100 F3
impacts on user experience of Have UEs randomly camp on
data services Layered access to another cell through DRD based on the Blind handover when the U900
U2100 F1 or U900 F1 when cell and U2100 cell share the
selecting between them. same sector and use the same
azimuth
When the U900 cell and U2100 cell share the same sector
and use the same azimuth: Measurement-based handover
when the U900 cell and U2100
different azimuths
When the U900 cell and U2100 cell share the same sector
but use different azimuths: This type of handover is
Layered access to another cell through redirection based on recommended when the UE tries
services to be handed over from a U2100
Terminal capability-based RRC inter-frequency redirection
of only DC-HSDPA, 3C-HSDPA, and 4C-HSDPA terminals
to cells enabled with this technology
cell to a U2100 cell.
NOTE:
Scenario 6 Taking both voice and Have UEs preferentially camp Have UEs performing voice services or combined services access the Load-based inter-frequency handover
data services into on U2100 F1 when selecting local cell directly. (recommended for data services)
account for high-band between U2100 carriers. Data services: Blind handover between U2100
carriers, reducing Have UEs in idle F1, U2100 F2, and U2100 F3
inter-frequency mode, CELL_PCH Layered access to another cell through DRD based on the Blind handover when the U900
handovers of voice state, and URA_PCH HSPA+ technology fulfillment rate cell and U2100 cell share the
services, and enabling state preferentially
Layered access to another cell through DRD based on load same sector and use the same
HSPA UEs to use all camp on F1. azimuth
carrier resources When the U900 cell and U2100 cell share the same sector
Have UEs in Measurement-based handover
Guaranteeing and use the same azimuth:
CELL_FACH state when the U900 cell and U2100
contiguous coverage camp on their original Layered access to another cell through DRD based on the
with low-band carriers carriers. HSPA+ technology fulfillment rate
different azimuths
and guaranteeing that Layered access to another cell through DRD based on load
Have UEs quickly Coverage-based inter-frequency handover
all UEs can use all When the U900 cell and U2100 cell share the same sector
return to F1 through
carriers but use different azimuths: This type of handover is
the function
Redirection at RRC Layered access to another cell through redirection based on recommended when the UE tries
Connection Release. services to be handed over from a U2100
Have UEs randomly camp on Terminal capability-based RRC inter-frequency redirection
U2100 F1 or U900 F1 when of only DC-HSDPA, 3C-HSDPA, and 4C-HSDPA terminals
selecting between them. to cells enabled with this technology
cell to a U2100 cell.
NOTE:
Scenario 7 Enabling the U2100 Set parameters to guarantee that the U900 Reduce inter-operations between the U900 and U2100 networks to guarantee Reduce inter-operations between the U900, U2100
network as the UMTS network provides deep coverage. the performance of the entire GU network. and G900 networks to guarantee the performance of
capacity layer to Between U900 and G900 cells: the entire GU network.
absorb the traffic of When congestions occur on the U900 network, functions provided in Reduce coverage-based handovers.
cell center users for the GU@5 MHz solution enable UEs performing CS services to be Reduce load-based handovers.
best user experience redirected to the GSM network and UEs performing PS services to
Enabling the U900 enter the RB Parking state.
network as the UMTS Between U900 and U2100 cells:
deep-coverage layer to
No action is required.
absorb the traffic of
cell edge users to
extend UMTS
coverage and to reduce
the proportion of
UMST UEs that fall
back to the GSM
network

The following figure shows the networking of intra-band multi-carrier coverage. In this type of networking scenario, the number of carriers must be greater than or equal to 2 and even greater in hotspot areas.
Figure 3-1 Intra-band multi-carrier networking
NOTE:
In this figure, n indicates the number of carriers on the same band, which is greater than or equal to 2. There are usually more carriers in hotspot areas.

This solution aims to carry voice and data services on different bearers to reduce the impact of data services on the KPIs of voice services.

To preferentially guarantee voice services, use the preferred camping and service steering policies shown in the following figure. All carriers support R99 and HSPA services, with F1 preferentially carrying R99
services and F2, F3, F4, …, Fn preferentially carrying HSPA services. The policy for each state is as follows:
Camping policy
UEs in idle mode, CELL_PCH state, and URA_PCH state camp on F1 through preferred camping. To enable idle-mode UEs in cells served by F2, F3, F4, …, Fn to quickly reselect to F1, the
function Redirection at RRC Connection Release can be used to redirect these UEs to F1.
Have UEs in CELL_FACH state camp on their original carriers.
Access mode policy

Have UEs performing voice services or combined services access the local cell directly.
Data services:
1. Layered access to another cell through DRD based on the HSPA+ technology fulfillment rate
2. Layered access to another cell through DRD based on services
3. Layered access to another cell through DRD based on load
Connected mode policy

Figure 3-2 Preferred camping and service steering

The following table lists features involved in the solution of preferentially guaranteeing voice services on intra-band multi-carrier networks.
Table 3-1 Features involved in the solution of preferentially guaranteeing voice services on intra-band multi-carrier networks
Item Feature ID Feature Name Introduced In... Reference Document
Camping policy WRFD-010401 System Information Broadcasting RAN2.0 UE Behaviors in Idle Mode Feature Parameter Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, RAN2.0 URA-Cell Update Feature Parameter Description
WRFD-010801 Intra RNC Cell Update RAN2.0 URA-Cell Update Feature Parameter Description
WRFD-010802 Inter RNC Cell Update RAN2.0 URA-Cell Update Feature Parameter Description
WRFD-160101 System Improvement for RAN16.0 RAN 16.0 Redirection at RRC Connection Release Feature Parameter
Description
Access mode policy WRFD-020400 DRD Introduction Package RAN3.0 Directed Retry Decision Feature Parameter Description
WRFD-02040004 service steering and Load Sharing During RAN 10.0 Directed Retry Decision Feature Parameter Description
RAB Setup
Connected mode policy WRFD-020302 Inter Frequency Hard Handover Based on RAN2.0 Handover Feature Parameter Description
Coverage
WRFD-020103 Inter Frequency Load Balance RAN2.0 Load Control Feature Parameter Description

The following table lists the features involved in the solution used in this scenario.
Feature ID Feature Name Purpose of Using This Feature in the Solution
WRFD-010401 System Information Broadcasting To support cell reselection between frequency bands
WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, To support the four states of UEs in connected mode: URA_PCH,
CELL-FACH) CELL_PCH, CELL_FACH, and CELL_DCH
WRFD-010801 Intra RNC Cell Update To support intra-RNC cell updates triggered by different causes specified in
3GPP protocols
WRFD-010802 Inter RNC Cell Update To support inter-RNC cell updates triggered by different causes specified in
3GPP protocols
WRFD-160101 System Improvement for RAN16.0 To support redirection of terminals complying with 3GPP Release 6 or later
to specified frequencies through the function Redirection at RRC
Connection Release.
The frequency information is carried in the "Redirection Info" IE of the
RRC connection release message sent by the RNC.
WRFD-020400 DRD Introduction Package To support direct retry and redirection between inter-frequency co-coverage
cells
WRFD-02040004 service steering and Load Sharing During RAB Setup To support load balancing of HSDPA services through DRD and allowing
the RAN to consider cell load and the required service type during RAB
setup to implement service steering and load sharing between different
frequencies or frequency bands
WRFD-020302 Inter Frequency Hard Handover Based on Coverage To support coverage-based inter-frequency handovers
WRFD-020106 Load Reshuffling To support multiple load reshuffling policies for a cell in a basic congestion
state to decrease cell load and increase the access success rate
WRFD-020103 Inter Frequency Load Balance To enable handovers of some UEs in a cell to inter-frequency
same-coverage cells if the cell is in a basic congestion state,
reducing cell load
To support two load-based inter-frequency handover modes:
load-based inter-frequency handover based on measurement and
load-based inter-frequency blind handover
Deployment and activation of each feature will not be described in this document and will be included in the corresponding feature parameter description. This section describes basic configuration requirements
for different feature combinations.
In this scenario, the camping policy, access mode policy, and connected mode policy are independent of each other and not mutually exclusive from each other. Therefore, they can be deployed at the same time
without affecting each other.
NOTE:
This section briefs parameter configurations for each carrier according to their coverage characteristics.
F1 and F2 indicates carriers that provide contiguous coverage. In the event of multiple such carriers, the same configuration is used.
F3 indicates carriers that provide discontiguous coverage. In the event of multiple such carriers, the same configuration is used.
Camping Policy
Table 3-3 lists the recommended values of cell selection or reselection parameters according to the camping policy in this scenario. Table 3-4 lists the recommended values of the SIB11Ind(BSC6900,BSC6910)
and IdleQoffset2sn(BSC6900,BSC6910) parameters for the inter-frequency neighboring cell.
Table 3-3 Recommended values of cell selection or reselection parameters
Parameter Value Recommended for the F1 Cell Value Recommended for the F2 Cell Value Recommended for the F3 Cell
QualMeas(BSC6900,BSC6910) (ADD CPICH_ECNO CPICH_ECNO CPICH_ECNO

UCELLSELRESEL)
Qqualmin(BSC6900,BSC6910) (ADD -18 dB (-18) -18 dB (-18) -18 dB (-18)

UCELLSELRESEL)
Qrxlevmin(BSC6900,BSC6910) (ADD -115 dBm (-58) -115 dBm (-58) -115 dBm (-58)
UCELLSELRESEL)
IdleQhyst2s(BSC6900,BSC6910) (ADD 2 dB (1) 2 dB (1) 2 dB (1)

UCELLSELRESEL)
IdleSintrasearch(BSC6900,BSC6910) (ADD 10 dB (5) 127 127

UCELLSELRESEL)
IdleSintersearch(BSC6900,BSC6910) (ADD 8 dB (4) 127 127

UCELLSELRESEL)
SibCfgBitMap(BSC6900,BSC6910) (ADD SIB4-0 SIB4-0 SIB4-0

UCELLSIBSWITCH)

UCELLSIBSWITCH)
ConnSintrasearch(BSC6900,BSC6910) (ADD 10 dB (5) 10 dB (5) 10 dB (5)

UCELLSELRESEL)
ConnSintersearch(BSC6900,BSC6910) (ADD 8 dB (4) 8 dB (4) 8 dB (4)

UCELLSELRESEL)
FACHMeasInd(BSC6900,BSC6910) (ADD NOT_REQUIRE NOT_REQUIRE INTER_FREQ

UCELLMEAS)
FACHMeasOccaCycleLenCoef(BSC6900,BSC6910) 6 6 6
(ADD UCELLMEAS)
RedirSwitch(BSC6900,BSC6910) (ADD OFF ONLY_TO_INTER_FREQUENCY ONLY_TO_INTER_FREQUENCY

UCELLREDRRCREL)
ReDirUARFCNDownlink(BSC6900,BSC6910) (ADD N/A Downlink UARFCN of the F1 cell Downlink UARFCN of the F1 cell
UCELLREDRRCREL)
Table 3-4 Recommended values of SIB11Ind and IdleQoffset2sn for inter-frequency neighboring cells
Cell Neighboring Cell Relationship Between Neighboring Cells SIB11Ind(BSC6900,BSC6910) IdleQoffset2sn(BSC6900,BSC6910)
F1 F2/F3 CoSector FLASE N/A
F2/F3 F1 CoSector TRUE -20
CoSite TRUE -20
No-CoSite TRUE -20
Settings of key parameters:
IdleSintersearch(BSC6900,BSC6910)
Set this parameter to a large value (for example, 127) for F2 and F3 so that inter-frequency cell measurement can be quickly started.
SibCfgBitMap(BSC6900,BSC6910)
None of these blocks needs to be delivered in the cells. According to 3GPP TS 25.304, when SIB4 and SIB12 are not delivered, UEs in the CELL_PCH, URA_PCH, and CELL_FACH states use cell
reselection parameters in SIB3 and SIB11.
SIB11Ind(BSC6900,BSC6910) and IdleQoffset2sn(BSC6900,BSC6910)
When the F1 cell is configured as a neighboring cell of F2 and F3 cells, set SIB11Ind to TRUE for F2 and F3 cells to enable the delivering of F2 and F3 messages in the SIB11 message. Set
IdleQoffset2sn(BSC6900,BSC6910) to -20 dB for F1, F2 and F3 cells so that UEs in idle mode preferentially camp on the F1 cell.
FACHMeasInd(BSC6900,BSC6910)
Set this parameter to NOT_REQUIRE for F1 and F2 cells (providing contiguous coverage) so that UEs in the CELL_FACH state in the two cells camp on their original carriers. Set this parameter to
INTER_FREQ for the F3 cell (providing discontiguous coverage) so that UEs in the CELL_FACH state can reselect carriers that provide contiguous coverage. To reduce the probability that UEs in the
CELL_FACH state reselect other cells, set FACHMeasOccaCycleLenCoef(BSC6900,BSC6910) to 6.
RedirSwitch(BSC6900,BSC6910) and ReDirUARFCNDownlink(BSC6900,BSC6910)
Turn on the switch for Redirection at RRC Connection Release in F2 and F3 cells and set the target frequency of redirection to F1 so that UEs in the F2 and F3 cells can return to the F1 cell after the RRC
connection is released.
Access Mode Policy

Table 3-5 lists the recommended values of RNC-level parameters; Table 3-6 lists recommended values of cell-level parameters; Table 3-7 lists the recommended values of the BlindHoFlag parameter for the inter-
frequency neighboring cell.
Table 3-5 Recommended values of RNC-level parameters
Parameter Recommended Value Description
SpgId(BSC6900,BSC6910) (ADD USPG) 1 2 The SPGID needs to be set to different values for different cells.
PriorityServiceForR99RT(BSC6900,BSC6910) (ADD USPG) 1 1 R99 services are set up on carriers that are used for initiating these services, without being affected
by DRD for service steering.
PriorityServiceForR99NRT(BSC6900,BSC6910) (ADD USPG) 1 1
PriorityServiceForHSDPA(BSC6900,BSC6910) (ADD USPG) 2 1 HSDPA/HSUPA services are preferentially carried on cells whose HSDPA/HSUPA service priority
is 1.
PriorityServiceForHSUPA(BSC6900,BSC6910) (ADD USPG) 2 1
DrSwitch(BSC6900,BSC6910): DR_RAB_SING_DRD_SWITCH (SET ON DRD is enabled for services carried by a single RAB.
UCORRMALGOSWITCH)
DrSwitch(BSC6900,BSC6910): DR_RAB_COMB_DRD_SWITCH (SET OFF DRD is prohibited for combined services that are carried by multiple RABs.
UCORRMALGOSWITCH)
OptimizationSwitch(BSC6900,BSC6910): RNC_P2D_DRD_SWITCH (SET ON DRD during P2D needs to be supported.

URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for rollback after RB SETUP DRD is turned on to improve the service setup success
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH (SET URRCTRLSWITCH) rate after DRD failures.
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for DRD rollback after RB reassignment is turned on to improve the service setup
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH (SET URRCTRLSWITCH) success rate after DRD failures.
DRDROLLBACKSWITCH(BSC6900,BSC6910) (SET UDPUCFGDATA) ON The DRD rollback is enhanced so that during the DRD procedure the RNC can receive and
properly process the configuration failure messages sent by the UE after the activation time
arrives. This facilitates the subsequent DRD rollback and therefore increases the service setup
success rate.
CmpSwitch2(BSC6900,BSC6910): CMP_DRD_SRBOVERH_SWITCH (SET ON Switch for determining whether signaling radio bearers (SRBs) can be switched over from DCHs
UCORRMALGOSWITCH) to HSPA channels during directed retry. When SRB over HSPA is enabled, it is recommended that
this switch be turned on to avoid DRD rollback failures caused by channel inconsistency.
PerfEnhanceSwitch1(BSC6900,BSC6910): ON Switch for determining whether the RNC can trigger channel reconfiguration for the SRBs to
PERFENH_SRB_FAST_HRETRY_AFTER_DRD_SWITCH (SET UCORRMPARA) switch from the DCH to an HSPA channel immediately when the type of a channel for carrying
SRBs during a DRD procedure is limited. When this switch is turned on, it solves the problem of
HSUPA throughput increasing too slowly after CMP_DRD_SRBOVERH_SWITCH is selected.
Table 3-6 Recommended values of cell-level parameters

Parameter Value Recommended for the F1 Cell Value Recommended for the F2 Cell Value Recommended for the F3 Cell (Discontiguous
Coverage)
SpgId(BSC6900,BSC6910) (ADD UCELLSETUP) 1 2 2
ServiceDiffDrdSwitch(BSC6900,BSC6910) (ADD ON ON ON
UCELLDRD)
LdbDRDSwitchDCH(BSC6900,BSC6910) (ADD UCELLDRD) OFF OFF OFF
LdbDRDSwitchHSDPA(BSC6900,BSC6910) (ADD ON ON ON
UCELLDRD)
LdbDRDchoice(BSC6900,BSC6910) (ADD UCELLDRD) UserNumber UserNumber UserNumber
Table 3-7 Recommended values of BlindHoFlag for inter-frequency neighboring cells
Cell Neighboring Cell Relationship Between Neighboring Cells BlindHoFlag(BSC6900,BSC6910)
F1 F2/F3 CoSector TRUE
F2/F3 F1 CoSector TRUE
CoSite FALSE
No-CoSite FALSE
NOTE:
F1, F2, and F3 cells can be configured as blind handover neighboring cells for each other only when they share the same sector.
Connected Mode Policy

Table 3-8 lists the recommended values of parameters related to load-based inter-frequency handovers for LDR between F1, F2, and F3 cells.
Table 3-8 Recommended values of parameters for load-based LDR inter-frequency handovers
Parameter Value Recommended for the F1 Cell Value Recommended for the F2 and F3 Cells
DlLdrFirstAction(BSC6900,BSC6910) (ADD UCELLLDR) CodeAdj CodeAdj
DlLdrSecondAction(BSC6900,BSC6910) (ADD UCELLLDR) InterFreqLDHO InterFreqLDHO
DlLdrThirdAction(BSC6900,BSC6910) (ADD UCELLLDR) BERateRed BERateRed
UlLdrFirstAction(BSC6900,BSC6910) (ADD UCELLLDR) InterFreqLDHO InterFreqLDHO
UlLdrSecondAction(BSC6900,BSC6910) (ADD UCELLLDR) BERateRed BERateRed
Table 3-9 lists the recommended values of parameters for coverage-based inter-frequency handovers between F1, F2, and F3 cells.
Table 3-9 Recommended values of neighboring cell parameters related to discontiguous coverage of the F3 carrier
Cell Neighboring Cell Relationship Between Neighboring Cells HOCovPrio(BSC6900,BSC6910)
F3 F2/F1 CoSector 2
CoSite 2
No-CoSite 2
NOTE:
The F2 cell provides contiguous coverage and does not need to be configured with inter-frequency neighboring cells. The F3 cell provides discontiguous coverage and needs to be configured with the F1 or F2 cell as neighboring cells to provide contiguous
coverage. Therefore, set HOCovPrio(BSC6900,BSC6910) to 2 for the F3 cell.
NOTE:

This solution aims to preferentially guarantee data services and balance load between carriers to maximize network capacity. This solution improves user experience in data services.

To preferentially guarantee data services, use random camping and load balancing policies shown in the following figure. F1, F2, F3, F4, …, Fn carriers all support R99 and HSPA services. The priorities of R99
services carried by these carriers are the same. The same principle applies to HSPA services. The policy for each state is as follows:
Camping policy
Have UEs camp on F1, F2, F3, F4, …, Fn randomly.
Access mode policy

Data services:

Figure 3-4 Random camping and load balancing

click to enlarge

The following table lists features involved in the solution of preferentially guaranteeing data services on intra-band multi-carrier networks.
Table 3-10 Features involved in the solution of preferentially guaranteeing data services on intra-band multi-carrier networks
WRFD-02040004 service steering and Load Sharing During RAN10.0 Directed Retry Decision Feature Parameter Description
RAB Setup
Coverage

Table 3-11 Features involved in the solution of preferentially guaranteeing data services on intra-band multi-carrier networks
3GPP protocols
3GPP protocols
cells
WRFD-020103 Inter Frequency Load Balance Enabling handovers of some UEs in a cell to inter-frequency same-
coverage cells if the cell is in a basic congestion state to reduce cell load,
supporting two load-based inter-frequency handover modes: load-based
inter-frequency handover based on measurement and load-based inter-
frequency blind handover
NOTE:
The configuration of SIB11Ind(BSC6900,BSC6910) is different if there are more than three carriers. The configurations in the event of four or six carriers will be provided separately without considering the preceding rules.
Camping Policy-10 dB (-10)

To enable UEs to randomly camp on the F1, F2, or F3 cell, set cell selection or reselection parameters to the values listed in Table 3-12 and set SIB11Ind(BSC6900,BSC6910) and
IdleQoffset2sn(BSC6900,BSC6910) to the values listed in Table 3-13.

UCELLSELRESEL)

UCELLSELRESEL)
UCELLSELRESEL)
IdleQhyst2s (ADD UCELLSELRESEL) 2 dB (1) 2 dB (1) 2 dB (1)
IdleSintrasearch(BSC6900,BSC6910) (ADD 127 127 127

UCELLSELRESEL)
IdleSintersearch(BSC6900,BSC6910) (ADD 127 127 127

UCELLSELRESEL)

UCELLSIBSWITCH)

UCELLSIBSWITCH)

UCELLSELRESEL)

UCELLSELRESEL)

UCELLMEAS)
(ADD UCELLMEAS)
Cell Neighboring Relationship SIB11Ind(BSC6900,BSC6910) IdleQoffset2sn(BSC6900,BSC6910) InterNCellQualReqFlag(BSC6900,BSC6910) Qqualmin(BSC6900,BSC6910) Qrxlevmin(BSC6900,BSC6910)

Cell Between
Neighboring
Cells
F1 F2 CoSector TRUE 0 FALSE N/A N/A
F1 F3 CoSector TRUE 0 TRUE -10 dB (-10) -101dBm(-51)
F2 F3 CoSector TRUE 0 TRUE -10 dB (-10) -101dBm(-51)
CoSite TRUE 0 FALSE N/A N/A
No-CoSite TRUE 0 FALSE N/A N/A

Cell Between
Neighboring
Cells
Set this parameter to a large value (for example, 127) for all cells (F1, F2, and F3) so that inter-frequency cell measurement can be quickly started.
IdleQoffset2sn(BSC6900,BSC6910)
Set this parameter to 0 dB for inter-frequency cell measurement between the F1, F2, and F3 cells so that UEs in idle mode can randomly camp on any carrier.
None of these blocks needsthe recommended value of the BlindHoFlag parameter to be delivered in the cells. According to 3GPP TS 25.304, when SIB4 and SIB12 are not delivered, UEs in the
CELL_PCH, URA_PCH, and CELL_FACH states use cell reselection parameters in SIB3 and SIB11.
When the F1 cell is configured as a neighboring cell of F2 and F3 cells, set SIB11Ind(BSC6900,BSC6910) to TRUE to enable delivering of the SIB11 message and set
IdleQoffset2sn(BSC6900,BSC6910) to -20 dB so that UEs in idle mode preferentially camp on the F1 cell.
InterNCellQualReqFlag(BSC6900,BSC6910)
Set this parameter to TRUE for the reselection from F1 and F2 cells to the F3 cell and set Qqualmin(BSC6900,BSC6910) and Qrxlevmin(BSC6900,BSC6910) to appropriate values to
avoid reselection to the edge of the cell providing discontiguous coverage.
Set this parameter to FLASE for the reselection from F2 and F3 cells to the F1 cell.
SIB11Ind(BSC6900,BSC6910)
When there are three carriers at a site, set this parameter to TRUE for all carriers. When there are four or more carriers at a site, set this parameter to TRUE for two of the carriers according to round robin
rules. Table 3-14 describes the configurations of this parameter for each carrier when there are four carriers. Table 3-15 describes the configurations of this parameter for each carrier when there are six
carriers.
NOTE:
SIB11Ind(BSC6900,BSC6910) is used for inter-frequency cell reselection. Each cell can be configured with only a maximum of two inter-frequency reselection neighboring cells. That is, SIB11 can be set to TRUE only for a maximum of
two inter-frequency neighboring cells for each cell. As specified in 3GPP TS 25.133, a UE can only measure two frequencies besides the frequency it is camping on.
In the event of five, six, or more carriers, round robin rules apply. Details will not be provided here.
Table 3-14 Recommended values of SIB11Ind for four inter-frequency neighboring cells sharing a 4-carrier site
Neighboring Cell F1 F2 F3 F4
Original Cell
F1 / TRUE TRUE FALSE
F2 FALSE / TRUE TRUE
F3 TRUE FALSE / TRUE
F4 TRUE TRUE FALSE /
Table 3-15 Recommended values of SIB11Ind for six inter-frequency neighboring cells sharing a 6-carrier site
Neighboring Cell F1 F2 F3 F4 F5 F6
Original Cell
F1 / TRUE TRUE FALSE FALSE FALSE
F2 FALSE / TRUE TRUE FALSE FALSE
F3 FALSE FALSE / TRUE TRUE FALSE
F4 FALSE FALSE FALSE / TRUE TRUE
F5 TRUE FALSE FALSE FALSE / TRUE
F6 TRUE TRUE FALSE FALSE FALSE /
Access State Policy

Table 3-16 lists the recommended values of RNC-level parameters; Table 3-17 lists recommended values of cell-level parameters; Table 3-18 lists the recommended values of the
BlindHoFlag(BSC6900,BSC6910) parameter for the inter-frequency neighboring cell.
SpgId(BSC6900,BSC6910) (ADD USPG) 1 The SPGID needs to be set to different values for different cells.
PriorityServiceForR99RT(BSC6900,BSC6910) (ADD USPG) 1 R99 services are set up on carriers that are used for initiating these services, without being affected by DRD
for service steering.
PriorityServiceForR99NRT(BSC6900,BSC6910) (ADD USPG) 1
PriorityServiceForHSDPA(BSC6900,BSC6910) (ADD USPG) 1 The HSDPA and HSUPA service priorities are set to the same value for all cells.
PriorityServiceForHSUPA(BSC6900,BSC6910) (ADD USPG) 1
DrSwitch(BSC6900,BSC6910): DR_RAB_SING_DRD_SWITCH ON DRD is enabled for services carried by single RABs.

(SET UCORRMALGOSWITCH)
DrSwitch(BSC6900,BSC6910): DR_RAB_COMB_DRD_SWITCH OFF DRD is prohibited for combined services that are carried by multiple RABs.
OptimizationSwitch(BSC6900,BSC6910): ON DRD during P2D needs to be supported.

RNC_P2D_DRD_SWITCH (SET URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for rollback after RB Establishment DRD is turned on to improve the service setup success rate
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH (SET after DRD failures.
URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for DRD rollback after RB reassignment is turned on to improve the service setup success rate
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH (SET after DRD failures.
URRCTRLSWITCH)
DRDROLLBACKSWITCH(BSC6900,BSC6910) (SET ON The DRD rollback is enhanced so that during the DRD procedure the RNC can receive and properly process
UDPUCFGDATA) the configuration failure messages sent by the UE after the activation time arrives. This facilitates the
subsequent DRD rollback and therefore increases the service setup success rate.
CmpSwitch2(BSC6900,BSC6910): ON Switch for determining whether SRBs can be switched over from DCHs to HSPA channels during directed
CMP_DRD_SRBOVERH_SWITCH (SET UCORRMALGOSWITCH) retry. When SRB over HSPA is enabled, it is recommended that this switch be turned on to avoid DRD
rollback failures caused by channel inconsistency.
PerfEnhanceSwitch1(BSC6900,BSC6910): ON Switch for determining whether the RNC can trigger channel reconfiguration for the SRBs to switch from the
PERFENH_SRB_FAST_HRETRY_AFTER_DRD_SWITCH (SET DCH to an HSPA channel immediately when the type of a channel for carrying SRBs during a DRD
UCORRMPARA) procedure is limited. When this switch is turned on, it solves the problem of HSUPA throughput increasing
too slowly after CMP_DRD_SRBOVERH_SWITCH is selected.

Coverage)
ServiceDiffDrdSwitch(BSC6900,BSC6910) (ADD OFF OFF OFF

UCELLDRD)
LdbDRDSwitchDCH(BSC6900,BSC6910) (ADD OFF OFF OFF

UCELLDRD)
LdbDRDSwitchHSDPA(BSC6900,BSC6910) ON ON ON
(ADD UCELLDRD)
LdbDRDchoice(BSC6900,BSC6910) (ADD UserNumber UserNumber UserNumber

UCELLDRD)
CoSite FALSE
No-CoSite FALSE
NOTE:
F1, F2, and F3 cells can be configured as blind handovers neighboring cells for each other only when they share the same sector.

F3 F2/F1 CoSector 2
CoSite 2
No-CoSite 2
NOTE:
NOTE:

If the preferred camping policy for voice services needs to be preferentially guaranteed, reserve a carrier that supports contiguous coverage for voice services so that UEs performing PS services are steered
towards other carriers to avoid impact of HSPA services on KPIs of voice services.
If the random camping and load balancing policy for data services is preferentially guaranteed, voices services will be initiated on non-contiguous carriers, causing many coverage-based inter-frequency handovers
and causing both the uplink and downlink load of the cell to be affected by HSPA services.
If both voice services and data services need to be taken into account, UEs preferentially camp on carriers that provide contiguous coverage. The carriers proportionally carry HSPA UEs to minimize coverage-
based inter-frequency handovers, ensuring that HSPA UEs can use all carriers.

Use service steering and preferred camping policy to distribute HSDPA UEs proportionally, as shown in the following figure, to take both voice services and data services into account. The priorities of R99
services carried by F1, F2, F3, F4, …, Fn are the same. The same principle applies to HSPA services. The policy for each state is as follows:
Camping policy
Have UEs in idle mode, CELL_PCH state, and URA_PCH state preferentially camp on F1. To enable UEs camping on the F2, F3, F4, …, Fn cells to be redirected to the F1 cell in time, the
Redirection at RRC Connection Release function can be used.
Access mode policy

Data services:

Figure 3-6 Load balancing and service steering with preferred camping of data services
click to enlarge

The following table lists features involved in the solution of taking both voice and data services into account on intra-band multi-carrier networks.
WRFD-160101 System Improvement for RAN16.0 RAN 16.0 Redirection at RRC Connection Release Feature Parameter
Description
WRFD-02040004 service steering and Load Sharing During RAN 10.0 Directed Retry Decision Feature Parameter Description
RAB Setup
Coverage

3GPP protocols
3GPP protocols
Connection Release.
The frequency information is carried in the "Redirection Info" IE of the
RRC connection release message sent by the RNC.
cells
WRFD-020103 Inter Frequency Load Balance To enable handovers of some UEs in a cell to inter-frequency
same-coverage cells if the cell is in a basic congestion state,
reducing cell load
To support two load-based inter-frequency handover modes:
load-based inter-frequency handover based on measurement and
load-based inter-frequency blind handover
NOTE:
Camping Policy
Table 3-23 lists the recommended values of cell selection or reselection parameters according to the camping policy in this scenario. Table 3-24 lists the recommended values of the
SIB11Ind(BSC6900,BSC6910) and IdleQoffset2sn(BSC6900,BSC6910) parameters for the inter-frequency neighboring cell.

UCELLSELRESEL)

UCELLSELRESEL)
UCELLSELRESEL)
IdleQhyst2s(BSC6900,BSC6910) (ADD 2 dB (1) 2 dB (1) 2 dB (1)

UCELLSELRESEL)
IdleSintrasearch(BSC6900,BSC6910) (ADD 10 dB (5) 127 127

UCELLSELRESEL)
IdleSintersearch(BSC6900,BSC6910) (ADD 8 dB (4) 127 127

UCELLSELRESEL)

UCELLSIBSWITCH)

UCELLSIBSWITCH)

UCELLSELRESEL)

UCELLSELRESEL)

UCELLMEAS)
(ADD UCELLMEAS)
RedirSwitch(BSC6900,BSC6910) (ADD OFF ONLY_TO_INTER_FREQUENCY ONLY_TO_INTER_FREQUENCY

UCELLREDRRCREL)
ReDirUARFCNDownlink(BSC6900,BSC6910) (ADD N/A Downlink UARFCN of the F1 cell Downlink UARFCN of the F1 cell
UCELLREDRRCREL)
F1 F2/F3 CoSector FLASE N/A
F2/F3 F1 CoSector TRUE -20
CoSite TRUE -20
No-CoSite TRUE -20
Set this parameter to a large value (for example, 127) for F2 and F3 so that inter-frequency cell measurement can be quickly started.
None of these blocks needs to be delivered in the cells. According to 3GPP TS 25.304, when SIB4 and SIB12 are not delivered, UEs in the CELL_PCH, URA_PCH, and CELL_FACH states use cell
reselection parameters in SIB3 and SIB11.
When the F1 cell is configured as a neighboring cell of F2 and F3 cells, set SIB11Ind to TRUE for F2 and F3 cells to enable the delivering of F2 and F3 messages in the SIB11 message. Set
IdleQoffset2sn(BSC6900,BSC6910) to -20 dB for F1, F2 and F3 cells so that UEs in idle mode preferentially camp on the F1 cell.
Turn on the switch for Redirection at RRC Connection Release in F2 and F3 cells and set the target frequency of redirection to F1 so that UEs in the F2 and F3 cells can return to the F1 cell after the RRC
connection is released.
Access State Policy

Table 3-25 lists the recommended values of RNC-level parameters; Table 3-26 lists recommended values of cell-level parameters; Table 3-27 lists the recommended values of the BlindHoFlag parameter for the
inter-frequency neighboring cell.
PriorityServiceForR99RT(BSC6900,BSC6910) (ADD USPG) 1 R99 services are set up on carriers that are used for initiating these services, without being affected by DRD
for service steering.
PriorityServiceForHSDPA(BSC6900,BSC6910) (ADD USPG) 1 The HSDPA and HSUPA service priorities are set to the same value for all cells.
DrSwitch(BSC6900,BSC6910): DR_RAB_SING_DRD_SWITCH ON DRD is enabled for services carried by single RABs.

DrSwitch(BSC6900,BSC6910): DR_RAB_COMB_DRD_SWITCH OFF DRD is prohibited for combined services that are carried by multiple RABs.
OptimizationSwitch(BSC6900,BSC6910): ON DRD during P2D needs to be supported.

RNC_P2D_DRD_SWITCH (SET URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for rollback after RB Establishment DRD is turned on to improve the service setup success rate
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH (SET after DRD failures.
URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for DRD rollback after RB reassignment is turned on to improve the service setup success rate
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH (SET after DRD failures.
URRCTRLSWITCH)
DRDROLLBACKSWITCH(BSC6900,BSC6910) (SET ON The DRD rollback is enhanced so that during the DRD procedure the RNC can receive and properly process
UDPUCFGDATA) the configuration failure messages sent by the UE after the activation time arrives. This facilitates the
subsequent DRD rollback and therefore increases the service setup success rate.
CmpSwitch2(BSC6900,BSC6910): ON Switch for determining whether SRBs can be switched over from DCHs to HSPA channels during directed
CMP_DRD_SRBOVERH_SWITCH (SET UCORRMALGOSWITCH) retry. When SRB over HSPA is enabled, it is recommended that this switch be turned on to avoid DRD
rollback failures caused by channel inconsistency.
PerfEnhanceSwitch1(BSC6900,BSC6910): ON Switch for determining whether the RNC can trigger channel reconfiguration for the SRBs to switch from the
PERFENH_SRB_FAST_HRETRY_AFTER_DRD_SWITCH (SET DCH to an HSPA channel immediately when the type of a channel for carrying SRBs during a DRD
UCORRMPARA) procedure is limited. When this switch is turned on, it solves the problem of HSUPA throughput increasing
too slowly after CMP_DRD_SRBOVERH_SWITCH is selected.
Coverage)
ServiceDiffDrdSwitch(BSC6900,BSC6910) (ADD OFF OFF OFF

UCELLDRD)
LdbDRDSwitchDCH(BSC6900,BSC6910) (ADD OFF OFF OFF

UCELLDRD)
LdbDRDSwitchHSDPA(BSC6900,BSC6910) ON ON ON
(ADD UCELLDRD)
LdbDRDchoice(BSC6900,BSC6910) (ADD UserNumber UserNumber UserNumber

UCELLDRD)
LoadBalanceRatio(BSC6900,BSC6910) (ADD 50 100 100

UCELLCAC)
NOTE:
Configure SPGID appropriately to ensure that F1, F2, and F3 carriers have the same HSDPA and HSUPA service priority configurations. Configure LoadBalanceRatio to ensure that fewer data services are carried by the F1 cell. The value of
LoadBalanceRatio depends on the radio network plan.

CoSite FALSE
No-CoSite FALSE
NOTE:
F1, F2, and F3 cells can be configured as blind handovers neighboring cells for each other only when they share the same sector.

F3 F2/F1 CoSector 2
CoSite 2
No-CoSite 2
NOTE:

Figure 3-7 shows the coverage status of inter-band multi-carrier networks. Among high-band carriers, U2100 F1 and U2100 F2 provide comparatively contiguous coverage; U2100 F3 and other carriers of U2100
provide hot-spot coverage. Among low-band carriers, U900 F1 provides contiguous coverage and U900 F2 provides non-contiguous coverage.
Figure 3-7 Inter-band multi-carrier networking
Figure 3-8 shows the distribution of U2100 and U900 sites on existing networks. Based on the coverage direction, U2100 and U900 cells can be served by the same or different sectors. If cells working at different
bands are served by different sectors, they use different antenna lobes and patterns, and therefore their coverage is different.
Figure 3-8 Distribution of sectors supported by multiple carriers that are served by different bands at the same site
The preferred camping and service steering policy is used for multiple high-band carriers to preferentially guarantee voice services. Low-band carriers provide contiguous coverage, especially for UEs at the cell
edge, so that load carried by low-band carriers can be switched to high-band carriers to ensure light load on low-band carriers.

Use the preferred camping and service steering policy shown in Figure 3-9 for high-frequency band to preferentially guarantee voice services. All carriers support R99 and HSPA services, with U2100 F1
preferentially carrying R99 services and U2100 F2, F3, F4, …, Fn preferentially carrying HSPA services. The following policies are recommended:
Camping policy
Have UEs preferentially camp on U2100 F1 when selecting between U2100 carriers.
Have UEs in idle mode, CELL_PCH state, and URA_PCH state preferentially camp on F1.
Have UEs quickly return to U2100 F1 through the function Redirection at RRC Connection Release after they terminate services on U2100 F2, F3, F4, …, Fn.
Have UEs randomly camp on U2100 F1 or U900 F1 when selecting between them.
Access mode policy

Data services
Layered access to another cell through DRD based on services
When the U900 cell and U2100 cell share the same sector and use the same azimuth:
When the U900 cell and U2100 cell share the same sector but use different azimuths:
Terminal capability-based RRC inter-frequency redirection of only DC-HSDPA, 3C-HSDPA, and 4C-HSDPA terminals to cells enabled with this technology

Load-based inter-frequency handover (recommended for data services)
Blind handover among F1, F2, F3, F4, …, Fn of U2100
Blind handover when the U900 cell and U2100 cell share the same sector and use the same azimuth
Measurement-based handover when the U900 cell and U2100 cell share the same sector but use different azimuths

This type of handover is recommended for handovers from a U2100 cell to a U900 cell but not recommended for handovers from a U900 cell to a U2100 cell.
Inter-band load balancing policy
Figure 3-9 Preferred camping and service steering in U2100 cells

click to enlarge
NOTE:
In this figure, U900 E1 indicates U900 F1 and U900 E2 indicates U900 F2.
The following table lists features involved in the solution of preferentially guaranteeing voice services on inter-band multi-carrier networks.
Table 3-30 Features involved in the solution of preferentially guaranteeing voice services on inter-band multi-carrier networks
WRFD-160101 System Improvement for RAN16.0 RAN16.0 Redirection at RRC Connection Release Feature Parameter
Description
WRFD-02040004 service steering and Load Sharing During RAB RAN10.0 Directed Retry Decision Feature Parameter Description
Setup
WRFD-020120 Service Steering and Load Sharing in RRC RAN11.0 Load Control Feature Parameter Description
Connection Setup
WRFD-150232 Multiband Direct Retry Based on UE Location RAN15.0 Directed Retry Decision Feature Parameter Description
Coverage
Network-level WRFD-020110 Multi Frequency Band Networking Management RAN10.0 Multi-Frequency Band Networking Management Feature
management Parameter Description
WRFD-020160 Enhanced Multiband Management RAN12.0 Multi-Frequency Band Networking Management Feature
WRFD-17121 Inter-Band Load Balancing RAN17.1 Inter-Band Load Balancing Feature Parameter Description

3GPP protocols
3GPP protocols
Connection Release The frequency information is carried in the
"Redirection Info" IE of the RRC connection release message sent by the
RNC.
cells
WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup To support service redirections to other frequencies based on service types
and local cell load during RRC connection setup
WRFD-150232 Multiband Direct Retry Based on UE Location To support UE steering between high- and low-frequency bands according
to the path loss of UEs during service setup or reconfiguration in U900/850
and U2100/1900 multi-band networking scenarios so that U900/U850
carriers can provide coverage for UEs at the cell edge to ensure deep
coverage
WRFD-020110 Multi Frequency Band Networking Management To support management of UEs' mobility between inter-band co-coverage
cells Enabling DC-SHDPA, 3C-HSDPA, and 4C-HSDPA UEs to move to
cells on another band
WRFD-020160 Enhanced Multiband Management To support load-based inter-band handovers according to the measurement
results
WRFD-171214 Inter-Band Load Balancing Adaptively adjusting parameter settings for UEs in idle mode, access mode,
and connected mode to achieve load balancing between high and low bands
NOTE:
Camping Policy
Set cell selection and reselection parameters for UEs in idle mode as well as UEs in the CELL_PCH, URA_PCH, and CELL_FACH states to values listed in Table 3-32 and SIB11Ind(BSC6900,BSC6910) and
IdleQoffset2sn(BSC6900,BSC6910) for inter-frequency neighboring cells to values listed in Table 3-33.
Parameter U2100 F1 Cell U2100 F2 Cell U2100 F3 Cell (Discontiguous U900 F1 Cell/U900 F2 Cell U900 F2 Cell (Discontiguous
Coverage) (Contiguous Coverage) Coverage)
QualMeas(BSC6900,BSC6910) (ADD CPICH_ECNO CPICH_ECNO CPICH_ECNO CPICH_ECNO CPICH_ECNO

UCELLSELRESEL)
Qqualmin(BSC6900,BSC6910) (ADD -18 dB (-18) -18 dB (-18) -18 dB (-18) -18 dB (-18) -18 dB (-18)
UCELLSELRESEL)
Qrxlevmin(BSC6900,BSC6910) (ADD -115 dBm (-58) -115 dBm (-58) -115 dBm (-58) -115 dBm (-58) -115 dBm (-58)
UCELLSELRESEL)
IdleQhyst2s (ADD UCELLSELRESEL) 2 dB (1) 2 dB (1) 2 dB (1) 2 dB (1) 2 dB (1)
IdleSintrasearch(BSC6900,BSC6910) (ADD 10 dB (5) 127 127 10 dB (5) 127

UCELLSELRESEL)
IdleSintersearch(BSC6900,BSC6910) (ADD 8 dB (4) 127 127 12 dB (6) 127

UCELLSELRESEL)
SibCfgBitMap(BSC6900,BSC6910) (ADD SIB4-0 SIB4-0 SIB4-0 SIB4-0 SIB4-0

UCELLSIBSWITCH)

UCELLSIBSWITCH)
ConnSintrasearch(BSC6900,BSC6910) (ADD 10 dB (5) 10 dB (5) 10 dB (5) 10 dB (5) 10 dB (5)

UCELLSELRESEL)
ConnSintersearch(BSC6900,BSC6910) (ADD 8 dB (4) 8 dB (4) 8 dB (4) 8 dB (4) 8 dB (4)

UCELLSELRESEL)
FACHMeasInd(BSC6900,BSC6910) (ADD NOT_REQUIRE NOT_REQUIRE INTER_FREQ INTER_FREQ INTER_FREQ

UCELLMEAS)
FACHMeasOccaCycleLenCoef(BSC6900,BSC6910) 6 6 6 6 6
(ADD UCELLMEAS)
RedirSwitch(BSC6900,BSC6910) (ADD OFF Only_To_Inter_Frequency Only_To_Inter_Frequency OFF OFF

UCELLREDRRCREL)
ReDirUARFCNDownlink(BSC6900,BSC6910) (ADD N/A Downlink UARFCN of the U2100 Downlink UARFCN of the U2100 N/A N/A
UCELLREDRRCREL) F1 cell F1 cell
U2100 F1 U2100 F2/U2100 F3 CoSector FLASE N/A
U2100 F2/U2100 F3 U2100 F1 CoSector TRUE -20
CoSite TRUE -20
No-CoSite TRUE -20
U2100 F1 U900 F1/U900 F2 (contiguous coverage) CoSector TRUE 3
CoSite TRUE 3
No-CoSite TRUE 3
U900 F1 (contiguous coverage) U2100 F1 CoSector TRUE -3

CoSite TRUE -3
No-CoSite TRUE -3
U900 F2 (discontiguous coverage) U900 F1/U2100 F1 CoSector TRUE -20
CoSite TRUE -20
No-CoSite TRUE -20
Set this parameter to a large value (for example, 127) for U2100 F2, U2100 F3, and U900 F2 so that inter-frequency cell measurement can be quickly started.
Set this parameter to a large value (for example, 127) for U900 F1 so that inter-frequency cell measurement can be quickly started.
If the U2100 F1 cell is configured as a neighboring cell of the U2100 F2 and U2100 F3 cells, set this parameter to -20 dB to make UEs in idle mode preferentially camp on the U2100 F1 cell.
If the U900 F1 cell is configured as a neighboring cell of the U2100 F1 cell, set this parameter to -3 dB.
If the U2100 F1 cell is configured as a neighboring cell of the U900 F1 cell, set this parameter to +3 dB to make UEs in idle mode preferentially camp on the U2100 F1 cell and reduce the load
of the U900 F1 cell.
If the U900 F2 cell is configured as a neighboring cell of the U900 F1/U2100 F1 cell, set this parameter to -20 dB to make UEs in idle mode camp on carriers that provide contiguous coverage.
SIB3 and SIB11

Both are delivered to all cells. SIB4 and SIB12 do not need to be delivered. According to 3GPP TS 25.304, when SIB4 and SIB12 are not delivered, UEs in the CELL_PCH, URA_PCH, and
CELL_FACH states use cell reselection parameters in SIB3 and SIB11.
Set this parameter to NOT_REQUIRE for the U2100 F1 cell, U2100 F2 cell, and U900 F1 cell (providing contiguous coverage) so that UEs in the CELL_FACH state in this cell camp on their original
carriers. Set this parameter to INTER_FREQ for the U2100 F3 cell and U900 F2 cell (providing non-contiguous coverage) so that UEs in the CELL_FACH state can reselect carriers that provide
contiguous coverage. To reduce the probability that UEs in the CELL_FACH state reselect other cells, set FACHMeasInd(BSC6900,BSC6910) to 6.

Turn on the switch for Redirection at RRC Connection Release for the U2100 F2 and U2100 F3 cells and set the target frequency of redirection to U2100 F1 so that UEs in the U2100 F2 and U2100 F3
cells can return to the U2100 F1 cell after the RRC connection is released.
Access Mode Policy

SpgId(BSC6900,BSC6910) (ADD USPG) 1 2 The SPGID needs to be set to different values for different cells.
PriorityServiceForR99RT(BSC6900,BSC6910) (ADD USPG) 1 1 R99 services are set up on carriers that are used for initiating these
services, without being affected by DRD for service steering.
PriorityServiceForR99NRT(BSC6900,BSC6910) (ADD USPG) 1 1
PriorityServiceForHSDPA(BSC6900,BSC6910) (ADD USPG) 2 1 The HSDPA/HSUPA service priority is set to 1.
PriorityServiceForHSUPA(BSC6900,BSC6910) (ADD USPG) 2 1
DrSwitch(BSC6900,BSC6910): DR_RAB_SING_DRD_SWITCH (SET UCORRMALGOSWITCH) ON DRD is enabled for services carried by a single RAB.
DrSwitch(BSC6900,BSC6910): DR_RAB_COMB_DRD_SWITCH (SET UCORRMALGOSWITCH) OFF DRD is prohibited for combined services that are carried by
multiple RABs.
OptimizationSwitch(BSC6900,BSC6910): RNC_P2D_DRD_SWITCH (SET URRCTRLSWITCH) ON DRD during P2D needs to be supported.
PROCESSSWITCH2(BSC6900,BSC6910): RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH (SET ON The switch for rollback after RB SETUP DRD is turned on to
URRCTRLSWITCH) improve the service setup success rate after DRD failures.
PROCESSSWITCH2(BSC6900,BSC6910): RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH (SET ON The switch for DRD rollback after RB reassignment is turned on to
URRCTRLSWITCH) improve the service setup success rate after DRD failures.
DRDROLLBACKSWITCH(BSC6900,BSC6910) (SET UDPUCFGDATA) ON The DRD rollback is enhanced so that during the DRD procedure
the RNC can receive and properly process the configuration failure
messages sent by the UE after the activation time arrives. This
facilitates the subsequent DRD rollback and therefore increases the
service setup success rate.
CmpSwitch2(BSC6900,BSC6910): CMP_DRD_SRBOVERH_SWITCH (SET ON Switch for determining whether SRBs can be switched over from
UCORRMALGOSWITCH) DCHs to HSPA channels during directed retry. When SRB over
HSPA is enabled, it is recommended that this switch be turned on
to avoid DRD rollback failures caused by channel inconsistency.
PerfEnhanceSwitch1(BSC6900,BSC6910): ON Switch for determining whether the RNC can trigger channel
PERFENH_SRB_FAST_HRETRY_AFTER_DRD_SWITCH (SET UCORRMPARA) reconfiguration for the SRBs to switch from the DCH to an HSPA
channel immediately when the type of a channel for carrying SRBs
during a DRD procedure is limited. When this switch is turned on,
it solves the problem of HSUPA throughput increasing too slowly
after CMP_DRD_SRBOVERH_SWITCH is selected.
Parameter Value Recommended for the F1 Value Recommended for the F2 Value Recommended for the F3 U900 F1 Cell/U900 F2 Cell U900 F2 Cell (Discontiguous
Cell Cell Cell (Discontiguous Coverage) (Contiguous Coverage) Coverage)
SpgId(BSC6900,BSC6910) (ADD 1 2 2 2 2
UCELLSETUP)
ServiceDiffDrdSwitch(BSC6900,BSC6910) ON ON ON OFF OFF

(ADD UCELLDRD)
LdbDRDSwitchDCH(BSC6900,BSC6910) OFF OFF OFF OFF OFF

(ADD UCELLDRD)
LdbDRDSwitchHSDPA(BSC6900,BSC6910) ON ON ON ON ON
(ADD UCELLDRD)
LdbDRDchoice(BSC6910,BSC6900) (ADD UserNumber UserNumber UserNumber UserNumber UserNumber

UCELLDRD)
Table 3-36 Recommended values of blind handover neighboring cells
U2100 F1 U2100 F2/U2100 F3 CoSector TRUE
U2100 F2/U2100 F3 U2100 F1 CoSector TRUE
CoSite FALSE
No-CoSite FALSE
U2100 F1 U900 F1/U900 F2 (contiguous coverage) CoSector FALSE

CoSite FALSE
No-CoSite FALSE
U900 F1 U2100 F2 CoSector TRUE
CoSite FALSE
No-CoSite FALSE
U900 F1 (contiguous coverage) U900 F2 (discontiguous coverage) CoSector TRUE
U900 F2 (discontiguous coverage) U900 F1 CoSector TRUE
CoSite FALSE
No-CoSite FALSE
NOTE:
U2100 F1, F2, and F3 cells can be configured as blind handover neighboring cells for each other only when they share the same sector.
If a U900 cell and a U2100 cell share the same site and use the same azimuth, and BlindHoFlag is set to TRUE, it is recommended that inter-band direct retry based on user location be enabled and related
parameters be set to values in Table 3-37.
Table 3-37 Suggestions on setting inter-band direct retry based on user location for UEs in connected mode
Parameter U900F1
BasedUELocDRDSwitch(BSC6900,BSC6910) (SET UDRD) ON
TraffTypeForBasedUELoc(BSC6900,BSC6910) (SET UDRD) RT-0&NRT-1
BasedUELocDRDRemainThd(BSC6900,BSC6910) (SET UDRD) 60
PathlossThdForEdge(BSC6900,BSC6910) (SET UDRD) 113
PathlossThdForCenter(BSC6900,BSC6910) (SET UDRD) 133
BlindHoFlag(BSC6900,BSC6910) (ADD UINTERFREQNCELL) Collocated U2100 F2
BlindHOQualityCondition(BSC6900,BSC6910) (ADD UINTERFREQNCELL) -85
If U900 and U2100 cells share the same site and the same azimuth, an anti-DRD failure mechanism is recommended when BlindHoFlag(BSC6900,BSC6910) is set to TRUE. Suggested parameter
configurations are listed in the following table.
Table 3-38 Suggested parameter configurations for the anti-DRD failure mechanism
Parameter U900F1
CellConnAlgoSwitch1(BSC6900,BSC6910): IDLE_DRD_BASED_COVER_SWITCH ON
CellConnAlgoSwitch1(BSC6900,BSC6910): C2D_DRD_BASED_COVER_SWITCH ON
CellConnAlgoSwitch1(BSC6900,BSC6910): CONN_DRD_BASED_COVER_SWITCH ON
BlindHOQualityCondition(BSC6900,BSC6910) -86 (for neighboring U2100 cells of the serving U900 cell)
DRDTargetUlCoverLimitThd(BSC6910,BSC6900) 9 (for neighboring U2100 cells of the serving U900 cell)
NOTE:
The Multiband Direct Retry Based on UE Location feature includes an anti-DRD failure mechanism. If a cell is enabled with this feature, an anti-DRD failure mechanism is not required.
When a U900 cell and a U2100 share the same site but use different azimuths, it is recommended that service-based RRC redirection be enabled and related parameters be set to the values in Table 3-39.
Table 3-39 Recommend values of parameters related to service-based RRC redirections
Parameter U900F1/F2
TrafficType(BSC6900,BSC6910) (ADD UCELLREDIRECTION) PSHSPA
RedirSwitch(BSC6900,BSC6910) (ADD UCELLREDIRECTION) ONLY_TO_INTER_FREQUENCY
RedirFactorOfNorm(BSC6900,BSC6910) (ADD UCELLREDIRECTION) 80
PerfEnhanceSwitch(BSC6900,BSC6910) (SET UCORRMPARA) PERFENH_RRC_REDIR_PROTECT_SWITCH
NOTE:
It is recommended that PERFENH_RRC_REDIR_PROTECT_SWITCH under the PerfEnhanceSwitch(BSC6900,BSC6910) parameter in the SET UCORRMPARA command be selected so that the RNC adopts the anti-ping-pong mechanism
for redirections.
If high-band cells support DC-HSDPA, 3C-HSDPA, or 4C-HSDPA but low-band cells do not, Terminal-Capability-based Inter-Frequency RRC Redirection is recommended. In this situation, DC-HSDPA, 3C-
HSDPA, and 4C-HSDPA terminals can perform services in DC-HSDPA, 3C-HSDPA, and 4C-HSDPA cells, respectively. Suggested parameter configurations are listed in the following table.
Table 3-40 Suggested parameter configurations for Terminal-Capability-based Inter-Frequency RRC Redirection
Parameter U900F1
RedirSwitch(BSC6900,BSC6910) ON
InterFreqRedirFactorOfLDR(BSC6900,BSC6910) 50
InterFreqRedirFactorOfNorm(BSC6900,BSC6910) 50
RedirBandInd(BSC6900,BSC6910) DependOnNCell
NOTE:
In most cases, U900 frequency spectrum is limited. In U900 single-carrier scenarios, DC-HSDPA and non-inter-band 3C/4C-HSDPA are not supported.

Load-based LDR inter-frequency handovers between a U2100 cell and a U900 cell can be used. Table 3-41 lists recommended LDR configurations.
Parameter Recommended Value for the U2100 F1, U2100 F2, Recommended Value for the U900 F1 and U900 F2 Recommended Value for the U900 F1 and U900 F2
and U2100 F3 Cells Cells (with the Same Azimuth as the U2100 Cell) Cells (with an Azimuth Different from the U2100
Cell)
DlLdrFirstAction(BSC6900,BSC6910) (ADD CodeAdj CodeAdj CodeAdj

UCELLLDR)
DlLdrSecondAction(BSC6900,BSC6910) (ADD InterFreqLDHO InterFreqLDHO InterFreqLDHO

UCELLLDR)
DlLdrThirdAction(BSC6900,BSC6910) (ADD BERateRed BERateRed BERateRed

UCELLLDR)
UlLdrFirstAction(BSC6900,BSC6910) (ADD InterFreqLDHO InterFreqLDHO InterFreqLDHO

UCELLLDR)
UlLdrSecondAction(BSC6900,BSC6910) (ADD BERateRed BERateRed BERateRed

UCELLLDR)
InterFreqLDHOMethodSelection(BSC6900,BSC6910) BLINDHO BLINDHO MEASUREHO

(ADD UCELLLDR)
Table 3-42 lists the recommended values of parameters for coverage-based inter-frequency handovers between U900 F1, U900 F2, and U2100 F2 cells.
Table 3-42 Recommended values of DrdOrLdrFlag for inter-frequency neighboring cells of UEs in connected mode
Cell Neighboring Cell Relationship Between Neighboring Cells DrdOrLdrFlag(BSC6900,BSC6910)
U900 F1/U900 F2 U2100 F2 Same azimuth FALSE
U900 F1/U900 F2 U2100 F2 Different azimuths TRUE
Table 3-43 Recommended values of parameters related to inter-frequency neighboring cells
U2100 F3 (discontiguous coverage) U2100 F2/U2100 F1 CoSector 2
CoSite 2
No-CoSite 2
U2100 F3/U2100 F2/U2100 F1 U900 F1 CoSector 2
CoSite 2
No-CoSite 2
NOTE:
The U2100 F2 cell provides contiguous coverage and does not need to be configured with inter-frequency neighboring cells. The U2100 F3 cell provides non-contiguous coverage and needs to be configured with the U2100 F1 or F2 cell and U900 F1 cell
as neighboring cells to provide contiguous coverage. Therefore, set HOCovPrio(BSC6900,BSC6910) to 2 for the U2100 F3 cell.
Inter-Band Load Balancing

The Inter-Band Load Balancing feature is intended to adjust parameter settings for UEs in idle mode, in access mode, and in connected mode. Based on the recommended solution, it adaptively adjusts parameter
settings to achieve load balancing between high and low frequency bands.
NOTE:
In most cases, low-band cells easily absorb traffic. Therefore, the suggested parameter configurations assume that low-band cell absorb traffic from high-band cells and these configurations reflect the difference between high and low bands. For details, see
Inter-Band Load Balancing Feature Parameter Description.

Figure 3-11 shows the distribution of U2100 and U900 sites on existing networks. Based on the coverage direction, U2100 and U900 cells can be served by the same or different sectors. If cells working at
different bands are served by different sectors, they use different antenna lobes and patterns, and therefore their coverage is different.

The preferred camping and service steering policy is used for multiple high-band carriers to preferentially guarantee voice services. Low-band carriers provide contiguous coverage, especially for UEs at the cell
edge, so that load carried by low-band carriers can be switched to high-band carriers to ensure light load on low-band carriers.

To preferentially guarantee data services, use random camping and load balancing policies shown in Figure 3-12. The priorities of R99 services carried by F1, F2, F3, F4, …, Fn of U2100 are the same. The same
principle applies to HSPA services. The following policies are recommended:
Camping policy
Have UEs randomly camp on F1, F2, F3, F4, …, Fn of U2100 when selecting between the carriers.
Have UEs randomly camp on U2100 F1 or U900 F1 when selecting between the carriers.
Access mode policy
Data services:


Inter-band load balancing policy

Figure 3-12 Random camping in U2100/U900 cells
NOTE:
In the figure above, U900 E1 indicates U900 F1 and U900 E2 indicates U900 F2.

The following table lists features involved in the solution of preferentially guaranteeing data services on inter-band multi-carrier networks.
Table 3-44 Features involved in the solution of preferentially guaranteeing data services on inter-band multi-carrier networks
WRFD-02040004 service steering and Load Sharing During RAN10.0 Directed Retry Decision Feature Parameter Description
RAB Setup
Connection Setup
WRFD-150232 Multiband Direct Retry Based on UE RAN15.0 Directed Retry Decision Feature Parameter Description
Location
Coverage
Network-level management WRFD-020110 Multi Frequency Band Networking RAN10.0 Multi-Frequency Band Networking Management Feature
Management Parameter Description
Table 3-45 Features involved in the solution of preferentially guaranteeing data services on inter-band multi-carrier networks
3GPP protocols
3GPP protocols
cells
coverage
WRFD-020110 Multi Frequency Band Networking Management To support management of UEs' mobility between inter-band co-
coverage cells
To enable DC-SHDPA, 3C-HSDPA, and 4C-HSDPA UEs to
move to cells on another band
results
WRFD-171214 Inter-Band Load Balancing Adaptively adjusting parameter settings for UEs in idle mode, in access
mode, and in connected mode to achieve load balancing between high and
low bands
NOTE:
Camping Policy

UCELLSELRESEL)
UCELLSELRESEL)
UCELLSELRESEL)
IdleQhyst2s(BSC6900,BSC6910) (ADD 2 dB (1) 2 dB (1) 2 dB (1) 2 dB (1) 2 dB (1)

UCELLSELRESEL)
IdleSintrasearch(BSC6900,BSC6910) (ADD 127 127 127 127 127

UCELLSELRESEL)
IdleSintersearch(BSC6900,BSC6910) (ADD 127 127 127 127 127

UCELLSELRESEL)

UCELLSIBSWITCH)

UCELLSIBSWITCH)

UCELLSELRESEL)

UCELLSELRESEL)
FACHMeasInd(BSC6900,BSC6910) (ADD NOT_REQUIRE NOT_REQUIRE INTER_FREQ NOT_REQUIRE INTER_FREQ

UCELLMEAS)
(ADD UCELLMEAS)

Cell Between
Neighboring
Cells
U2100 F1 U2100 F2 CoSector TRUE 0 FALSE N/A N/A
U2100 F2 U2100 F3 CoSector TRUE 0 TRUE -10 dB (-10) -101 dBm (-51)
U900 F1 U2100 F1 CoSector TRUE -3 FALSE N/A N/A
CoSite TRUE -3 FALSE N/A N/A
No-CoSite TRUE -3 FALSE N/A N/A
U900 F1 U900 F2 CoSector TRUE 0 TRUE -10 dB (-10) -101 dBm (-51)
(discontiguous
coverage)

(discontiguous
coverage) CoSite TRUE 0 FALSE N/A N/A
Set this parameter to a large value (for example, 127) for all cells (U2100 F1, U2100 F2, U2100 F3, U900 F1, and U900 F2) so that inter-frequency cell measurement can be quickly started.
Set this parameter to 0 dB for inter-frequency cell measurement between U2100 F1, F2, and F3 cells so that UEs in idle mode can randomly camp on any carrier.
Set this parameter to 0 dB for inter-frequency cell measurement between U900 F1 and F2 cells so that UEs in idle mode can randomly camp on any carrier.
If the U900 F1 cell and U2100 F1 cell are configured as neighboring cells, set this parameter to +3 dB for inter-frequency cell measurement to make UEs in idle mode preferentially camp on the
U2100 F1 cell and reduce the load of the U900 F1 cell load.
NOTE:
IdleQoffset2sn(BSC6900,BSC6910) can be set to a value between -2 dB and -5 dB. If the U900 cell has a heavy load, it can be set to -4 dB or -5 dB. If the U900 cell has a light load, it can be set to -2 dB.
SIB3 and SIB11

If SIB3 and SIB11 are delivered to all cells, enable delivering of SIB4 and set ConnSintersearch to an appropriate value so that UEs in the CELL_PCH and CELL_FACH states start inter-frequency cell
measurement only when Ec/N0 is low so that the number of cell updates is reduced.
contiguous coverage. To reduce the probability that UEs in the CELL_FACH state reselect other cells, set FACHMeasOccaCycleLenCoef(BSC6900,BSC6910) to 6.
InterNCellQualReqFlag(BSC6900,BSC6910)
Set this parameter to TRUE for the reselection from U2100 F1 and U2100 F2 cells to the U2100 F3 cell as well as the reselection from the U900 F1 cell to the U900 F2 cell and set
Qqualmin(BSC6900,BSC6910) and Qrxlevmin(BSC6900,BSC6910) to appropriate values to avoid reselection to the edge of the cells providing non-contiguous coverage.
Set this parameter to FALSE for the reselection from U2100 F2 and U2100 F3 cells to the U2100 F1 cell as well as reselection from the U900 F2 cell to the U900 F1 cell.
Set this parameter to FALSE for reselections between U2100 F1 and U900 F1 cells.
SIB11Ind(BSC6900,BSC6910)
Set this parameter to TRUE for reselections between U2100 F1 and U900 F1 cells.
Set this parameter to TRUE for reselections between U900 F1 and U900 F2 cells.
If there are two U2100 carriers, set this parameter to TRUE for both of them. If there are more U2100 carriers, set this parameter to TRUE for two of the carriers according to round robin rules.
An example is given in the following table.
NOTE:
SIB11Ind is used for inter-frequency cell reselection. Each cell can be configured with only a maximum of two inter-frequency reselection neighboring cells. That is, SIB11 can be set to TRUE only for a maximum of two inter-
frequency neighboring cells for each cell. As specified in 3GPP TS 25.133, a UE can only measure two frequencies besides the frequency it is camping on.
Table 3-48 Suggested setting of SIB11Ind for inter-frequency neighboring cells enabled with Inter-Band Load Balancing (four carriers of U2100+two carriers of U900)
Original Cell Neighboring Cell
U2100 F1 U2100 F2 U2100 F3 U2100 F4 U900 F1 U900 F2
U2100 F1 / TRUE FALSE FALSE TRUE FALSE
U2100 F2 FALSE / TRUE TRUE FALSE FALSE
U2100 F3 TRUE FALSE / TRUE FALSE FALSE
U2100 F4 TRUE TRUE FALSE / FALSE FALSE
U900 F1 TRUE FALSE FALSE FALSE / TRUE
U900 F2 FALSE FALSE FALSE FALSE TRUE /
Access Mode Policy

Table 3-49 lists the recommended values of RNC-level parameters; Table 3-50 lists recommended values of cell-level parameters; Table 3-51 lists the recommended values of the
BlindHoFlag(BSC6900,BSC6910) parameter for the inter-frequency neighboring cell.
PriorityServiceForR99RT(BSC6900,BSC6910) (ADD USPG) 1 R99 services are set up on carriers that are used for initiating these services, without being affected by
DRD for service steering.
PriorityServiceForHSDPA(BSC6900,BSC6910) (ADD USPG) 1 The HSDPA/HSUPA service priority is set to 1.
UCORRMALGOSWITCH)
UCORRMALGOSWITCH)

URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for rollback after RB SETUP DRD is turned on to improve the service setup success rate
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH (SET URRCTRLSWITCH) after DRD failures.
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for DRD rollback after RB reassignment is turned on to improve the service setup success
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH (SET URRCTRLSWITCH) rate after DRD failures.
DRDROLLBACKSWITCH(BSC6900,BSC6910) (SET UDPUCFGDATA) ON The DRD rollback is enhanced so that during the DRD procedure the RNC can receive and properly
process the configuration failure messages sent by the UE after the activation time arrives. This
facilitates the subsequent DRD rollback and therefore increases the service setup success rate.
CmpSwitch2(BSC6900,BSC6910): CMP_DRD_SRBOVERH_SWITCH (SET ON Switch for determining whether SRBs can be switched over from DCHs to HSPA channels during
UCORRMALGOSWITCH) directed retry. When SRB over HSPA is enabled, it is recommended that this switch be turned on to
avoid DRD rollback failures caused by channel inconsistency.
PerfEnhanceSwitch1(BSC6900,BSC6910): ON Switch for determining whether the RNC can trigger channel reconfiguration for the SRBs to switch
PERFENH_SRB_FAST_HRETRY_AFTER_DRD_SWITCH (SET from the DCH to an HSPA channel immediately when the type of a channel for carrying SRBs during a
UCORRMPARA) DRD procedure is limited. When this switch is turned on, it solves the problem of HSUPA throughput
increasing too slowly after CMP_DRD_SRBOVERH_SWITCH is selected.
Parameter Value Recommended for Value Recommended Value Recommended for the F3 U900 F1 Cell/U900 F2 Cell U900 F2 Cell (Discontiguous
the F1 Cell for the F2 Cell Cell (Discontiguous Coverage) (Contiguous Coverage) Coverage)
SpgId(BSC6900,BSC6910) (ADD UCELLSETUP) 1 1 1 1 1
ServiceDiffDrdSwitch(BSC6900,BSC6910) (ADD OFF OFF OFF OFF OFF

UCELLDRD)
LdbDRDSwitchDCH(BSC6900,BSC6910) (ADD OFF OFF OFF OFF OFF

UCELLDRD)
LdbDRDSwitchHSDPA(BSC6900,BSC6910) (ADD ON ON ON ON ON
UCELLDRD)

UCELLDRD)

CoSite FALSE
No-CoSite FALSE
CoSite FALSE
No-CoSite FALSE
U900 F1/U900 F2 (contiguous coverage) U2100 F2 CoSector TRUE
CoSite FALSE
No-CoSite FALSE
U900 F1 U900 F2 (contiguous/discontiguous coverage) CoSector TRUE
CoSite FALSE
No-CoSite FALSE
NOTE:
If a U900 cell and a U2100 cell share the same site and use the same azimuth, and BlindHoFlag(BSC6900,BSC6910) is set to TRUE, it is recommended that inter-band direct retry based on user location be
enabled and related parameters be set to values in the following table.
Parameter U900 F1
The following table assumes that the Multiband Direct Retry Based on UE Location feature is not enabled. If U900 and U2100 cells share the same site and the same azimuth, an anti-DRD failure mechanism is
recommended when BlindHoFlag(BSC6900,BSC6910) is set to TRUE. Suggested parameter configurations are listed in the following table.
Parameter U900 F1
Parameter U900 F1
Parameter U900F1/F2
NOTE:
It is recommended that PERFENH_RRC_REDIR_PROTECT_SWITCH under the PerfEnhanceSwitch(BSC6900,BSC6910) parameter in the SET UCORRMPARA command be selected so that the RNC adopts the anti-ping-pong mechanism
for redirections.
If high-band cells support DC-HSDPA, 3C-HSDPA, or 4C-HSDPA but low-band cells do not, Terminal-Capability-based Inter-Frequency RRC Redirection is recommended. In this situation, terminals can perform
services with their maximum capabilities. Suggested parameter configurations are listed in the following table.
Parameter U900 F1

Cell)

UCELLLDR)

UCELLLDR)

UCELLLDR)

UCELLLDR)
Cell)

UCELLLDR)

(ADD UCELLLDR)
CoSite 2
No-CoSite 2
CoSite 2
No-CoSite 2
NOTE:

NOTE:
Figure 3-14 shows the distribution of U2100 and U900 sites on existing networks. Based on the coverage direction, U2100 and U900 cells can be served by the same or different sectors. If cells working at
different bands are served by different sectors, they use different antenna lobes and patterns, and therefore their coverage is different.

The solution of preferentially guaranteeing voice services uses the preferred camping and service steering policies. In this way, a carrier providing contiguous coverage is separately reserved for voice services so
that UEs performing PS services are steered towards other carriers to avoid impact of HSPA services on KPIs of voice services.
The solution of preferentially guaranteeing data services uses the random camping and load balancing policies. In this way, voice services are initiated on carriers providing discontiguous coverage, causing many
coverage-based inter-frequency handovers and causing both the uplink and downlink load of the cell to be affected by HSPA services.
The solution of taking both voice services and data services into account preferentially enables UEs to camp on carriers providing contiguous coverage, and enable the resident carrier and other carriers to
proportionally carry HSPA UEs. In this way, single-frequency carriers can provide contiguous coverage for UEs performing voice services, the number of inter-frequency handovers decreases, and HSPA UEs can
use all carriers.

Use the service steering and preferred camping policy to distribute HSDPA UEs proportionally, as shown in Figure 3-15, to take both voice services and data services into account. The priorities of R99 services
carried by F1, F2, F3, F4, …, Fn of U2100 are the same as those carried by F1 and F2 of U900. The same principle applies to HSPA services. The policy for each state is as follows:
Camping policy
Have UEs preferentially camp on U2100 F1 when selecting between U2100 carriers.
Have UEs in idle mode, CELL_PCH state, and URA_PCH state preferentially camp on F1.
Have UEs quickly return to U2100 F1 through the function Redirection at RRC Connection Release after they terminate services on U2100 F2, F3, F4, …, Fn.
Have UEs randomly camp on U2100 F1 or U900 F1 when selecting between them.
Access mode policy
Data services:



Figure 3-15 Random camping in U2100/U900 cells

click to enlarge
NOTE:
In the figure above, U900 E1 indicates U900 F1 and U900 E2 indicates U900 F2.

The following table lists features involved in the solution of taking both voice and data services into account on inter-band multi-carrier networks.
WRFD-160101 System Improvement for RAN16.0 RAN16.0 Redirection at RRC Connection Release Feature Parameter
Description
WRFD-02040004 service steering and Load Sharing During RAB RAN10.0 Directed Retry Decision Feature Parameter Description
Setup
Connection Setup
Coverage
Network-level WRFD-020110 Multi Frequency Band Networking Management RAN10.0 Multi-Frequency Band Networking Management Feature
management Parameter Description

3GPP protocols
3GPP protocols
Connection Release The frequency information is carried in the
"Redirection Info" IE of the RRC connection release message sent by the
RNC.
cells
coverage
WRFD-020110 Multi Frequency Band Networking Management To support management of UEs' mobility between inter-band co-coverage
cells Enabling DC-SHDPA, 3C-HSDPA, and 4C-HSDPA UEs to move to
cells on another band
results
WRFD-171214 Inter-Band Load Balancing Adaptively adjusting parameter settings for UEs in idle mode, access mode,
and connected mode to achieve load balancing between high and low bands
(ADD UCELLSELRESEL) without affecting each other.
NOTE:
Camping Policy

UCELLSELRESEL)
UCELLSELRESEL)
UCELLSELRESEL)
IdleQhyst2s(BSC6900,BSC6910) (ADD 2 dB (1) 2 dB (1) 2 dB (1) 2 dB (1) 2 dB (1)

UCELLSELRESEL)
IdleSintrasearch(BSC6900,BSC6910) (ADD 10 dB (5) 127 127 10 dB (5) 127

UCELLSELRESEL)
IdleSintersearch(BSC6900,BSC6910) (ADD 8 dB (4) 127 127 12 dB (6) 127

UCELLSELRESEL)

UCELLSIBSWITCH)

UCELLSIBSWITCH)

UCELLSELRESEL)

UCELLSELRESEL)
FACHMeasInd(BSC6900,BSC6910) (ADD NOT_REQUIRE NOT_REQUIRE INTER_FREQ INTER_FREQ INTER_FREQ

UCELLMEAS)
(ADD UCELLMEAS)
RedirSwitch(BSC6900,BSC6910) (ADD OFF Only_To_Inter_Frequency Only_To_Inter_Frequency OFF OFF

UCELLREDRRCREL)
ReDirUARFCNDownlink(BSC6900,BSC6910) (ADD N/A Downlink UARFCN of the U2100 Downlink UARFCN of the U2100 N/A N/A
UCELLREDRRCREL) F1 cell F1 cell
U2100 F1 U2100 F2/U2100 F3 CoSector FLASE N/A
U2100 F2/U2100 F3 U2100 F1 CoSector TRUE -20

CoSite TRUE -20
No-CoSite TRUE -20
U2100 F1 U900 F1/U900 F2 (contiguous coverage) CoSector TRUE 3
CoSite TRUE 3
No-CoSite TRUE 3
U900 F1 (contiguous coverage) U2100 F1 CoSector TRUE -3
CoSite TRUE -3
No-CoSite TRUE -3
U900 F2 (discontiguous coverage) U900 F1/U2100 F1 CoSector TRUE -20
CoSite TRUE -20
No-CoSite TRUE -20
Set this parameter to a large value (for example, 127) for U2100 F2, U2100 F3, and U900 F2 so that inter-frequency cell measurement can be quickly started.
Set this parameter to a large value (for example, 127) for U900 F1 so that inter-frequency cell measurement can be quickly started.
If the U2100 F1 cell is configured as a neighboring cell of the U2100 F2 and U2100 F3 cells, set this parameter to -20 dB to make UEs in idle mode preferentially camp on the U2100 F1 cell.
If the U2100 F1 cell is configured as a neighboring cell of the U900 F1 cell, set this parameter to +3 dB to make UEs in idle mode preferentially camp on the U2100 F1 cell and reduce the load
of the U900 F1 cell.
If the U900 F2 cell is configured as a neighboring cell of the U900 F1/U2100 F1 cell, set this parameter to -20 dB to make UEs in idle mode camp on carriers that provide contiguous coverage.
SIB3 and SIB11

Both are delivered to all cells. SIB4 and SIB12 do not need to be delivered. According to 3GPP TS 25.304, when SIB4 and SIB12 are not delivered, UEs in the CELL_PCH, URA_PCH, and
CELL_FACH states use cell reselection parameters in SIB3 and SIB11.
contiguous coverage. To reduce the probability that UEs in the CELL_FACH state reselect other cells, set FACHMeasInd(BSC6900,BSC6910) to 6.

Turn on the switch for Redirection at RRC Connection Release for the U2100 F2 and U2100 F3 cells and set the target frequency of redirection to U2100 F1 so that UEs in the U2100 F2 and U2100 F3
cells can return to the U2100 F1 cell after the RRC connection is released.
Access State Policy


PriorityServiceForR99RT(BSC6900,BSC6910) (ADD USPG) 1 R99 services are set up on carriers that are used for initiating these services, without being affected by
DRD for service steering.
PriorityServiceForHSDPA(BSC6900,BSC6910) (ADD USPG) 1 The HSDPA/HSUPA service priority is set to 1.
UCORRMALGOSWITCH)
UCORRMALGOSWITCH)

URRCTRLSWITCH)
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for rollback after RB SETUP DRD is turned on to improve the service setup success rate
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH (SET URRCTRLSWITCH) after DRD failures.
PROCESSSWITCH2(BSC6900,BSC6910): ON The switch for DRD rollback after RB reassignment is turned on to improve the service setup success
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH (SET URRCTRLSWITCH) rate after DRD failures.
DRDROLLBACKSWITCH(BSC6900,BSC6910) (SET UDPUCFGDATA) ON The DRD rollback is enhanced so that during the DRD procedure the RNC can receive and properly
process the configuration failure messages sent by the UE after the activation time arrives. This
facilitates the subsequent DRD rollback and therefore increases the service setup success rate.
CmpSwitch2(BSC6900,BSC6910): CMP_DRD_SRBOVERH_SWITCH (SET ON Switch for determining whether SRBs can be switched over from DCHs to HSPA channels during
UCORRMALGOSWITCH) directed retry. When SRB over HSPA is enabled, it is recommended that this switch be turned on to
avoid DRD rollback failures caused by channel inconsistency.
PerfEnhanceSwitch1(BSC6900,BSC6910): ON Switch for determining whether the RNC can trigger channel reconfiguration for the SRBs to switch
PERFENH_SRB_FAST_HRETRY_AFTER_DRD_SWITCH (SET from the DCH to an HSPA channel immediately when the type of a channel for carrying SRBs during a
UCORRMPARA) DRD procedure is limited. When this switch is turned on, it solves the problem of HSUPA throughput
increasing too slowly after CMP_DRD_SRBOVERH_SWITCH is selected.
Parameter Value Recommended for the F1 Value Recommended for the F2 Value Recommended for the F3 U900 F1 Cell/U900 F2 Cell U900 F2 Cell (Discontiguous
Cell Cell Cell (Discontiguous Coverage) (Contiguous Coverage) Coverage)
SpgId(BSC6900,BSC6910) (ADD 1 1 1 1 1
UCELLSETUP)
ServiceDiffDrdSwitch(BSC6900,BSC6910) OFF OFF OFF OFF OFF

(ADD UCELLDRD)
LdbDRDSwitchDCH(BSC6900,BSC6910) OFF OFF OFF OFF OFF

(ADD UCELLDRD)
LdbDRDSwitchHSDPA(BSC6900,BSC6910) ON ON ON ON ON
(ADD UCELLDRD)

UCELLDRD)
LoadBalanceRatio(BSC6900,BSC6910) 50 100 100 50 50

(ADD UCELLCAC)
Configure SPGID appropriately to ensure that F1, F2, and F3 carriers have the same HSDPA and HSUPA service priority configurations. Configure LoadBalanceRatio(BSC6900,BSC6910) to ensure that
fewer data services are carried by the F1 cell. The value of LoadBalanceRatio(BSC6900,BSC6910) depends on the radio network plan.
CoSite FALSE
No-CoSite FALSE
CoSite FALSE
No-CoSite FALSE
U900 F1/U900 F2 (contiguous coverage) U2100 F2 CoSector TRUE
CoSite FALSE
No-CoSite FALSE
U900 F1 U900 F2 (contiguous/discontiguous coverage) CoSector TRUE
CoSite FALSE
No-CoSite FALSE
NOTE:
If a U900 cell and a U2100 cell share the same site and use the same azimuth, and BlindHoFlag(BSC6900,BSC6910) is set to TRUE, it is recommended that inter-band direct retry based on user location be
enabled and related parameters be set to values in the following table.
Parameter U900 F1
The following table assumes that the Multiband Direct Retry Based on UE Location feature is not enabled. If U900 and U2100 cells share the same site and the same azimuth, an anti-DRD failure mechanism is
recommended when BlindHoFlag(BSC6900,BSC6910) is set to TRUE. Suggested parameter configurations are listed in the following table.
Parameter U900 F1
Parameter U900 F1
Parameter U900F1/F2
NOTE:
It is recommended that PERFENH_RRC_REDIR_PROTECT_SWITCH under the PerfEnhanceSwitch parameter in the SET UCORRMPARA command be turned on so that the RNC adopts the anti-ping-pong mechanism for redirections.
If high-band cells support DC-HSDPA, 3C-HSDPA, or 4C-HSDPA but low-band cells do not, Terminal-Capability-based Inter-Frequency RRC Redirection is recommended. In this situation, terminals can perform
services with their maximum capabilities. Suggested parameter configurations are listed in the following table.
Parameter U900 F1

Cell)

UCELLLDR)

UCELLLDR)

UCELLLDR)

UCELLLDR)
Cell)

UCELLLDR)

(ADD UCELLLDR)
CoSite 2
No-CoSite 2
CoSite 2
No-CoSite 2
NOTE:

NOTE:
WRFD-010401 System Information Broadcasting RAN2.0 UE Behaviors in Idle Mode Feature Parameter Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL- RAN2.0 URA-Cell Update Feature Parameter Description
WRFD-020110 Multi Frequency Band Networking Management RAN10.0 Multi-Frequency Band Networking Management Feature Parameter Description
WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup RAN10.0 Directed Retry Decision Feature Parameter Description
WRFD-020120 Service Steering and Load Sharing in RRC Connection RAN11.0 Load Control Feature Parameter Description
Setup
WRFD-020160 Enhanced Multiband Management RAN12.0 Multi-Frequency Band Networking Management Feature Parameter Description
BlindHO Blind Handover
DRD Directed retry decision
GSM Global system for mobile communications
IFHO Inter-Frequency Handover
KPI Key performance indicator
LDB Load Control Balancing
LDR Load reshuffling
MSC Mobile switching center
RNC Radio network controller
SGSN Serving GPRS support node

SHO Soft Handover
UE User equipment
1. UE Behaviors in Idle Mode Feature Parameter Description

2. URA-Cell Update Feature Parameter Description
6. Multi-Frequency Band Networking Management Feature Parameter Description
7. Inter-Band Load Balancing Feature Parameter Description
WCDMA RAN
UMTS Multi-Sector Solution Guide

Issue 01
Date 2016-02-29

Notice

1.4.4 Contents
1 Introduction
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
2.2 Application Scenario
3 Application Guide
3.1 Implementation Process
3.1.1 Analyzing Scenarios
3.1.2 Surveying Sites
3.1.3 Planning the Network
3.1.4 Implementing the Project
3.1.5 Optimizing the Network
3.1.6 Evaluating the Performance
3.2.1 Scenario 1: Capacity Expansion in Dense Urban and Urban Areas
3.2.2 Scenario 2: xMbps Improvement in Dense Urban and Urban Areas
3.2.3 Scenario 3: Coverage Improvement in Suburban and Rural Areas
3.2.4 Scenario 4: Capacity Expansion Using the Nine-Sector Solution
3.3.1 Special Scenario 1: Special Clutter Scenarios
3.3.2 Special Scenario 2: Special Traffic Scenarios
3.4 Key Technologies
4 Involved Features
6 References
1 Introduction
1.1 Scope
1.3 Change History
1.1 Scope
This document describes the Huawei UMTS multi-sector solution in different scenarios.
This document includes the deployment of the multi-sector solution in UMTS single-frequency and single-mode scenarios. For details about the multi-sector solution deployment in multi-frequency or multi-mode
scenarios, see Multi-Sector GUL Joint Deployment and Evolution Solution.

Need to understand multi-sector solutions

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

This is the first release of RAN18.1.
2 Solution Overview
2.1 Background
2.1 Background
Due to the increasing UMTS mobile broadband service volume, capacity expansion must be maximized with coverage ensured for the UMTS network. Carrier addition and site addition are the traditional capacity
expansion methods, which have the following disadvantages:
Some operators may have no additional spectrum resources and therefore cannot expand the capacity by carrier addition.
No proper site locations are available and site location acquisition is difficult.
Site addition is time-consuming and labor-consuming.
The multi-sector solution is an important method to solve network bottleneck problems. In scenarios where the frequencies are insufficient and site location acquisition is difficult, this solution can enable capacity
expansion without site addition, which reduces the workload and complexity of capacity expansion. The solution deployment is easy and efficient, facilitating smooth network evolution.

Based on the simulation using digital maps and live network data, the following example uses the six-sector configuration to describe the typical performance improvement of the multi-sector solution:
Coverage improvement: The improvement depends on the antennas used on the original three-sector network. For example, if the 18 dBi 65° antenna is used, the six-sector solution provides 2 dB to 3 dB
improvement on the high band.
Capacity improvement: The capacity is expanded by about 70% on the high band and about 60% on the low band. The KPIs remain stable before and after the antenna replacement.
For network establishment or swapping on high bands, the coverage can be improved by 30% to 40%, or the number of sites can be reduced by about 25% without compromising the coverage, thereby reducing the
network cost.
Based on the preceding analysis, the UMTS multi-sector solution can be used in the following scenarios:
Figure 2-1 Application scenarios of the multi-sector solution
click to enlarge
Scenario 1: Capacity expansion in dense urban and urban areas

In dense urban and urban scenarios, due to the dense population, a large number of UEs access the network, causing network congestion. Then, the traffic cannot increase as fast as the number of accessed
UEs does, adversely affecting operator's revenue as well as user experience. Therefore, the multi-sector solution needs to be deployed on these congested sites to improve the network capacity.
Scenario 2: xMbps improvement in dense urban and urban areas
In dense urban and urban areas, due to a large number of UEs, the air interface resources, including the code resources and power resources, are insufficient, and user experience may be poor. Therefore,
the multi-sector solution needs to be deployed to increase the throughput of the target area.
Scenario 3: Capacity expansion in suburban and rural areas
In suburban and rural areas, the traffic volume is small, and the inter-site distance (ISD) is large. The coverage improvement is the main concern.
Scenario 4: Capacity expansion using the nine-sector solution
The nine-sector solution can be used if further capacity expansion needs to be performed.
The following special scenarios, which need to be identified and processed in advance, may be encountered in commercial networks:
Special scenario 1: Special clutter scenarios

Complex dense urban scenario: In this scenario, the ISD is small with densely located high buildings, and the interference can hardly be controlled. Therefore, the KPI assurance using the multi-
sector solution is challenging.
Other special clutter scenarios: Other special clutter scenarios include strip areas such as the high-speed railway, highways, and urban arterial road, and areas such as elevated roads, and
overpasses. The special clutter scenarios cannot be identified using tools, and it is time-consuming to manually identify special clutter scenarios.
Special scenario 2: Special traffic scenarios

Severely imbalanced traffic
If the traffic is imbalanced after the sector split, the traffic offload provides few gains, and sector split causes more interference. Consequently, the capacity expansion improvement is not
obvious.
Traffic at the cell edge
If most traffic is required at the cell edge, the multi-sector solution will result in more handovers and severe pilot pollution. Consequently, KPIs are likely to deteriorate.
Strip-shaped traffic
If the hotspot traffic is strip-shaped along the sector direction before the sector splitting, the hotspot area will be in the overlapped area of the two split sectors after the sector splitting, adversely
affecting capacity improvement and user experience.

The multi-sector solution aims to improve the network performance using narrow-beam high-gain antennas and sector split technology. The narrow-beam high-gain antennas improve coverage, and the sector split
technology increases the number of cells to improve air interface resources, such as code resources and power resources.
Figure 2-2 shows the principle of the sector split technology.
Figure 2-2 Six-sector split and antenna pattern
3 Application Guide

Figure 3-1 shows a general deployment and verification process of the multi-sector solution.
Figure 3-1 Deployment process of the multi-sector solution
3.1.1 Analyzing Scenarios
Scenario analysis aims to spot carriers needs to be split before sector splitting.
Sector splitting is performed based on the actual situation. Hotspot sectors need to be split, and non-hotspot sectors do not need to be split. As shown in Figure 3-2, four-sector, five-sector, and six-sector sites can
exist on the network.
Figure 3-2 Sector splitting
The following describes how to identify capacity expansion scenarios, xMbps improvement scenarios, and coverage expansion scenarios:
Capacity expansion
Based on the collected live network performance data and MML configuration data, search for the traffic suppression point, where the traffic cannot increase as fast as the number of accessed UEs does.
The power utilization rate and the number of DCH UEs at this point are the capacity expansion threshold. If the power utilization rate and the number of DCH UEs of a cell are greater than this threshold,
the cell is a hotspot cell for capacity expansion.
The U-Net can be used to spot hotspots. In scenarios where the capacity expansion from a three-sector network to a six-sector network on the live network, the power utilization rate is generally between
60% to 70%. The U-Net tool is currently unavailable to customers. For details about this tool, contact Huawei technical support. The U-Net tool is currently unavailable to customers. For details about this
tool, contact Huawei technical support.
xMbps improvement
The xMbps improvement scenarios can be identified using the following method: Identify the grids of low UE rate based on the traffic map, sort the sectors based on the ratio of low rate grids, and include
the sectors with the highest ratios of low rate grids into the list of sectors to be split. This operation can be implemented using the ASP.
Coverage improvement
Obtain the RSCP distribution and prepare the traffic map based on the measurement report (MR) data. Then calculate the ratio of grids with the RSCP less than the weak coverage judgment threshold
(default value: -100 dBm). If the ratio is greater than the weak coverage ratio judgment threshold (default value: 10%), it is considered that weak coverage exists in the sector. This operation can be
implemented using the U-Net. For detailed principles, contact Huawei engineers.
If the network load is low (average load during a day lower than 30%), the sector splitting increases interference, adversely affecting network performance.
3.1.2 Surveying Sites

The site survey is the same for multi-sector sites and three-sector sites. Pay attention to the following:
The antenna installation platform must be large enough. If 1T2R RF units are used, more RF units are required.
Sector splitting brings more cells. Therefore, the baseband resources and transmission resources must be sufficient.
For details about multi-band multi-mode network deployment and hardware planning for the future evolution, see Multi-Sector GUL Joint Deployment and Evolution Solution.
3.1.3 Planning the Network

Antenna selection
The multi-sector solution requires antenna replacement. Therefore, it is vital to select antennas with outstanding performance and easy installation.
Specifications
The larger the antenna size is, the more difficult the antenna installation is. For detailed antenna size, see the antenna datasheet. Split antennas and 33° narrow beam antennas can be used for
sector splitting. Three split antennas or six 33° narrow beam antennas are used for the six sector deployment. Therefore, split antennas can be deployed more easily than 33° narrow beam
antennas.
Performance
The performance of antennas can be compared based on the antenna pattern diagram. Compare the interference levels on the horizontal plane, down side lobe filling and upper side lobe
suppression on the vertical plane, front-to-back ratio (FBR), and coverage strength. The Huawei-developed tool for antenna pattern diagram comparison can implement quick comparison for split
antennas and 33° narrow beam antennas together or separately. For details, contact Huawei engineers.
Antenna performance comparison can also be implemented through simulation. Specifically, the RSCP is used to evaluate coverage strength, and the Ec/Io is used to evaluate coverage quality.
The HSDPA throughput is used to evaluate the capacity, and the KPI is evaluated based on the Ec/Io differences between three-sector and multi-sector scenarios.
The following suggestions are for the comparison of Huawei split antennas and antennas from other mainstream vendors in terms of the coverage, capacity, and KPIs, and deployment difficulty:
High-band split scenario: The Huawei AMB4520R0 high-band split antenna is recommended.
Low-band split scenario: The Huawei AMB4519R0 low-band split antenna is recommended.
High- and low-band antenna scenario: Antennas in the industry can hardly provide good performance and easy deployment at the same time. If the antenna installation platform is large enough,
the dual-band 33° narrow-beam antenna of good performance is recommended. If the antenna installation platform is not large enough, split antennas of small sizes are recommended.
For details about antenna specification comparison results, contact Huawei engineers.
Parameter planning, RF planning, and neighboring cell scrambling code planning
The procedure of parameter planning, RF planning, and neighboring cell scrambling code planning are the same for both the multi-sector network and the three-sector network. The ASP and ACP
supports engineering parameter planning for the multi-sector network to provide engineering parameters. For details, contact Huawei engineers.
NOTE:
If the antenna installation platform is not large enough, use 2T4R RRUs, which save half space compared with 1T2R RRUs.
3.1.4 Implementing the Project

The project implementation for the multi-sector solution is similar to that for the three-sector solution, including antenna replacement, parameter configuration and activation, service verification, urgent issue
troubleshooting, and rollback.
3.1.5 Optimizing the Network

Network optimization includes common RF optimization, parameter optimization, pilot and common channel power optimization. The ACP can be used to provide RF optimization suggestions. Two beam
azimuths of the same split antenna cannot be adjusted separately. For details, contact Huawei engineers.
3.1.6 Evaluating the Performance

Evaluating the coverage improvement
In versions earlier than RAN16.0, the MR data is recommended to evaluate the coverage improvement. In RAN16.0 and later, the performance data are recommended to evaluate the coverage
improvement. The coverage improvement evaluation includes the evaluation of the RSCP and Ec/Io. The CDF, PDF, and average values of the RSCP and Ec/Io before and after sector splitting must be
provided.
Figure 3-3 RSCP and Ec/Io distribution
click to enlarge
Table 3-1 Average values of the RSCP and Ec/Io before and after sector splitting
Coverage Before Sector Splitting After Sector Splitting Difference
Average RSCP - - -
Average Ec/Io - - -
NOTE:
Cells marked in hyphen (-) need to be filled in based on site conditions.
Evaluating the system capacity improvement

The system capacity is the hard capacity, indicating the capability for traffic. The system capacity does not change with the traffic. Compare the performance data, including the load and traffic, before and
after sector splitting (collect the performance data for at least one week before and one week after sector splitting to prevent the impact of the data fluctuation). The traffic improvement is the system
capacity improvement when the load remains unchanged. Figure 3-4 shows that the high-band capacity improvement is about 70% when Huawei split antennas are used.
Figure 3-4 System capacity improvement evaluation
click to enlarge
Evaluating the traffic and load improvement
The sector splitting is implemented on congested sites, and therefore the suppressed traffic is released after the sector splitting, bringing traffic improvement. After the sector splitting, the traffic of the
original sector is shared by the two sectors. In this situation, the load of each sector should be less than that of the original sector, but the traffic increase causes the load to increase. Therefore, the traffic
and load are strongly related, and the traffic and load improvement evaluation can indicate the capacity evaluation.
Collect the performance data, including the traffic and load statistics, for at least one week before and one week after the sector splitting. It is expected that the traffic increases or the load decreases.
Evaluating the KPI Improvement
Collect the traffic statistic for at least one week before and one week after sector splitting to compare the KPIs related to the network access, call drops, and mobility. It is expected that KPIs remain stable
after the sector splitting.
Table 3-2 Common KPIs
KPI Type Counter ID Before Sector Splitting After Sector Splitting
Access VS.CS.Access.Success.Cell.Rate - -
VS.PS.Access.Success.Cell.Rate - -
Call drops VS.CS.AMR.Call.Drop.Cell.Rate - -
VS.PS.Call.Drop.Cell.Rate - -
Handover VS.SHO.Success.Cell.Rate - -

3.2.1 Scenario 1: Capacity Expansion in Dense Urban and Urban Areas
In dense urban and urban areas, due to the dense population, a large number of UEs access the network, causing network congestion. Then, the traffic cannot increase, adversely affecting operator's revenue as well
as user experience. Therefore, the multi-sector solution must be deployed on site with traffic congestion to increase the number of cells and system capacity, preventing traffic suppression caused by network
congestion.
The dense urban area has the following characteristics:
The terrain is flat.

The buildings are of 25 m to 30 m in average.
The buildings are densely located with small and irregular inter-building distances (10 m to 20 m).
Most streets (not arterial roads) are narrow.
The ISD is 300 m to 500 m.
Figure 3-5 Examples of dense urban areas

click to enlarge
The urban area has the following characteristics:
The area is in a city.

The buildings are of 20 m in average.
The inter-building distance is greater than or equal to the building height.
Open areas or green fields are in this area.
The ISD is 500 m to 700 m.
Figure 3-6 Examples of urban areas

click to enlarge
In this scenario, the capacity needs to be expanded. For details about the solution deployment, see 3.1 Implementation Process. Pay attention to the scenario identification and antenna selection. Use the live
network data to find the threshold for the capacity expansion and then identify the scenario. It is good practice to use Huawei split antennas with good side lobe suppression, controllable interference, and large
capacity improvement.
3.2.2 Scenario 2: xMbps Improvement in Dense Urban and Urban Areas

In dense urban and urban scenarios, due to a large number of UEs, the air interface resources, including the code resources and power resources, are insufficient, and user experience may be poor. Therefore, the
multi-sector solution must be implemented to bring more air interface resources, increase the UE throughput in the target area, and improve user experience.
For the definition of the dense urban and urban area scenarios, see 3.2.1 Scenario 1: Capacity Expansion in Dense Urban and Urban Areas. For the definition of the xMbps improvement scenarios, see Figure 3-7.
Figure 3-7 shows the UE rate in each grid. Deploy the multi-sector solution for sectors with most low UE rate grids.
Figure 3-7 xMbps grid diagram
click to enlarge
The multi-sector solution helps increase the throughput in this scenario. For details about the deployment procedure, see 3.1 Implementation Process. In performance evaluation, the grid-level rate is identified to
check whether the ratio of girds with UE rate greater than xMbps meets the expectation.
3.2.3 Scenario 3: Coverage Improvement in Suburban and Rural Areas

In suburban and rural areas, the traffic volume is small and the ISD is large. Therefore, large-scale attenuation occurs, resulting in weak coverage. The multi-sector solution adopts the high-gain narrow-beam
antennas. For example, if the 18 dBi 65° antenna is used on the high band, the six-sector solution brings 2 dB to 3 dB antenna gains, significantly increasing the coverage in suburban and rural areas.
The suburban area has the following characteristics:
The suburban area is usually in the rural-urban fringe.

The buildings are of 10 m in average.
Buildings are sparsely located with an average inter-building distance of 30 to 50 m.
The streets are wide with large open areas or green fields.
The ISD is 1 to 2 km.
Figure 3-8 Suburban area

click to enlarge
The rural area has the following characteristics:
Buildings are sparsely located.

Most buildings are ranch houses. The building height is about 5 m in average.
There are large pieces of open land, farmland, vegetation and road
The ISD is over 3 km.
Figure 3-9 Rural area

click to enlarge
The multi-sector solution enhances the coverage in this scenario. For details about the deployment procedure, see 3.1 Implementation Process. The selected antenna must satisfy the requirements of easy
deployment, desired coverage gains, and future capacity expansion. The Huawei split antenna, not the 33° narrow-beam antenna providing greater gains, is recommended.
3.2.4 Scenario 4: Capacity Expansion Using the Nine-Sector Solution

The nine-sector solution can be used if further capacity expansion needs to be performed.
The following lists the three scenarios for capacity expansion using the nine-sector solution:
Newly-deployed nine-sector solution: applicable to high-traffic assurance scenarios, such as concerts and football games. This scenario is rarely seen. For details, contact Huawei engineers.
Three-to-nine-sector splitting: If the six-sector solution cannot satisfy the traffic requirements, conduct sector splitting from three to nine sectors.
Six-to-nine-sector splitting: If network congestion occurs on the existing six-sector network, implement the nine-sector solution.
Figure 3-10 shows the principle of the nine-sector solution:

Figure 3-10 Nine-sector splitting and antenna pattern
The nine-sector solution can be used only on the high band. Compared with the three-sector solution, the nine-sector solution adopting Huawei triple-beam antennas brings a 120% to 170% capacity gain while the
coverage and KPIs remain stable.
The nine-sector solution deployment is basically the same as the six-sector solution deployment. The difference is as follows:
1. Analyzing scenarios
Three-to-nine-sector splitting: Check whether the traffic requirement of the three-sector network exceeds the capacity improvement (70%) provided by the six-sector solution. If yes, use the
nine-sector solution. The traffic requirement includes the suppressed traffic and the increased traffic during the capacity expansion period.
Six-to-nine-sector splitting: Collect the live network data to find the traffic suppression point of the six-sector network, where the traffic does not increase with the number of accessed UEs, to
obtain the capacity expansion threshold of the six-sector network. If the load and number of DCH UEs for the six-sector network exceeds the capacity expansion threshold on a site, the nine-
sector solution can be implemented on the site.
For detailed site selection principles, contact Huawei engineers.

2. Site survey
The three-sector and nine-sector network configurations differ significantly in terms of the sector quantity, RRU quantity, power specifications, and baseband and transmission requirements. Ensure that
you have obtained detailed current network configuration information before conducting site planning.
3. Network planning
Antenna selection
The antenna selection method is similar between the triple-beam split antenna and the dual-beam split antenna. Antenna selection must comply with the performance requirements and
deployment ease. The Huawei triple-beam split antenna is recommended.
RF module selection
If there is insufficient space for antenna installation, it is recommended three 2T4R RRUs and three 1T2R RRUs be used. Then, the three 1T2R RRUs can be reused.

3.3.1 Special Scenario 1: Special Clutter Scenarios
Complex Dense Urban Scenario
In this scenario, the ISD is small with densely located high buildings, and the interference can hardly be controlled. In this situation, the KPI assurance using the multi-sector solution is challenging.
The complex dense urban area has the following characteristics:
The buildings are of over 50 m tall.

The inter-building distance is less than 80 m in average.
The ISD is less than 300 m in average.
Example: Guangzhou, Hong Kong, Vancouver, and Tokyo

Figure 3-11 Complex dense urban scenarios
click to enlarge
The multi-sector solution can be used directly in complex dense urban scenarios, providing about 40% capacity gains. In this situation, the Ec/Io drops by about 1 dB, and the KPIs deteriorate by 25% to 30%.
After the hybrid multi-sector function is enabled, the Ec/Io and KPIs do not deteriorate with the capacity ensured.
The hybrid multi-sector function changes the overlapping area of cells on combined sectors into the cell center. Then, UEs in the idle state camp on the combined sectors. In this way, the cell edge UEs can be
eliminated to lower interference and improve KPIs and user experience.
Other Special Clutter Scenarios

In strip-shaped scenarios, such as the high-speed railways, highways, and urban arterial roads, large capacity is required. In tall buildings, if no indoor system is available, outdoor coverage cannot satisfy the
indoor traffic requirement. In elevated roads and overpasses, the radio environment is complex and the interference cannot be controlled. In such scenarios, the multi-sector solution implementation has restrictions,
and you need to identify these scenarios in advance.
Figure 3-12 shows examples of other special clutter scenarios.
Figure 3-12 Examples of strip-shaped scenarios and elevated road scenarios
click to enlarge
The following table lists the application principles of the multi-sector solution in other special clutter scenarios:
Table 3-3 Application principles of the multi-sector solution in other special clutter scenarios
Scenario Application Principle of the Multi-Sector Solution
Highway (average speed: over 80 km/h) The hotspot is on the road, and sector splitting is not recommended.
After the sector splitting, the newly formed overlapping area must not be along the road. That is, the included angle between the split
Cloverleaf interchange (open scenario)
antenna and the road must be equal to or greater than 30°.
Simple elevated roads (two layers) After sector splitting, the traffic on the two beams must be balanced.
Urban main road (usually wide) NOTE:

Handovers may fail in the highway scenarios. To ensure KPIs, reconfigure the handover parameters such as the CIO and handover thresholds.
Scenario
Tall buildings (hotspot in the building with no indoor distributed systems) Application Principle
Check whether outdooroftraffic
the Multi-Sector Solution
exists. If outdoor traffic exists, perform the sector splitting. Otherwise, do not perform sector splitting.
High-speed railway and subway The multi-sector solution is not recommended.
Complex elevated roads (three or more layers)
Bridges over the river
Spiral interchange (two or more layers)
3.3.2 Special Scenario 2: Special Traffic Scenarios

Severely imbalanced traffic
If the traffic is imbalanced after the sector split, the traffic offload provides few gains, and sector split causes more interference. Consequently, the capacity expansion improvement is not obvious. The
multi-sector solution is not recommended.
Figure 3-13 Severely imbalanced traffic
click to enlarge
Traffic at the cell edge

If most traffic is required at the cell edge, the multi-sector solution will result in more handovers and severe pilot pollution. Consequently, KPIs are likely to deteriorate. The multi-sector solution is
recommended only when site addition is unavailable at the cell edge.
Figure 3-14 Hotspot at the cell edge
click to enlarge
Strip-shaped traffic
If the hotspot traffic is strip-shaped along the sector direction before the sector splitting, the hotspot area will be in the overlapped area of the two split sectors after the sector splitting, adversely affecting
capacity improvement and user experience. The multi-sector solution is not recommended.
Figure 3-15 Strip-shaped traffic
click to enlarge

Up to 64 Neighboring Cells Allowed
If the six-sector solution is implemented on a three-sector network, the number of neighboring cells increases by about 1.4 times. If the intra-frequency neighboring cell specifications do not increase, neighboring
cell missing configuration may occur when there are more than 32 neighboring cells, adversely affecting network performance, such as the coverage quality on the edge (indicated by Ec/Io), service drop rate,
handover success rate, and the number of handovers.
If the multi-sector solution is applied, the number of supported intra-frequency neighboring cells is increased from 32 to 64 (63 neighboring cells plus the local cell), and these cells are prioritized. The 31 high-
priority intra-frequency cells are used for the SIB11 and SIB11bis system messages and Uu measurement control. The other 32 low-priority intra-frequency cells are applied only when the UE reports cells in the
detection set so that the RNC searches the desired cell ID from the intra-frequency neighboring cell list based on the scrambling code for soft handovers. This function prevents KPI deterioration due to insufficient
neighboring cells. For details, contact Huawei engineers.
Figure 3-16 Up to 64 neighboring cells allowed
click to enlarge
Efficient Improvement of Call Drop-related KPIs in Multi-Sector

Using the one-click deployment of multiple functions to improve call drop-related KPIs, this feature enhances basic network performance in multi-sector scenarios. For details, see Efficient Improvement of Call
Drop-related KPIs in Multi-Sector Feature Parameter Description.
Adaptive Soft Handover Optimization in Multi-Sector

In multi-sector scenarios, the RNC automatically adjusts the priority configurations of intra-frequency neighboring cells to ensure that information of the high-priority neighbor cells are preferentially delivered in
the measurement control messages and system messages to the source cell. Based on big data analysis, the RNC automatically adjusts the important neighbor relationships in the intra-frequency measurement
control message to reduce improper soft handovers, reducing the call drop rate. For details, see Adaptive Soft Handover Optimization in Multi-Sector Feature Parameter Description.
4 Involved Features
Feature ID Feature Name Introduced In Reference Document
N/A Up to 64 Neighboring Cells Allowed RAN14.0 Contact Huawei technical support.
N/A Hybrid Multi-Sector RAN17.1 Contact Huawei technical support.
WRFD-180107 Efficient Improvement of Call Drop-related KPIs in RAN18.1 Efficient Improvement of Call Drop-related KPIs in Multi-Sector
Multi-Sector Feature Parameter Description
WRFD-181105 Adaptive Soft Handover Optimization in Multi-Sector RAN18.1 Adaptive Soft Handover Optimization in Multi-Sector Feature
ACP Automatic Cell Planning
ASP Accurate Site Planning
CDU Complex Dense Urban
CDF Cumulative Distribution Function
DU Dense Urban
MBB Mobile Broad Band
RF Radio Frequency
RRU Remote Radio Unit
6 References
1. Multi-Sector GUL Joint Deployment and Evolution Solution
2. Efficient Improvement of Call Drop-related KPIs in Multi-Sector Feature Parameter Description
3. Adaptive Soft Handover Optimization in Multi-Sector Feature Parameter Description
WCDMA RAN
UMTS RNC in Pool Solution Guide

Issue 01
Date 2016-02-29

Notice
1.4.5 Contents
1.1 Overview
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Scenario 1: Control- and User-Plane Capacity Expansion, Load Decrease, or Burst Traffic Handling
3.2 Scenario 2: RNC Node Redundancy and Hitless Upgrade
1.1 Overview
1.3 Change History
1.1 Overview
This document describes the RNC in Pool solution for different application scenarios.

Need to understand the RNC in Pool solution

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Added descriptions of automatic NodeB control switchover to 3.2.4 Implementation.

Modified node redundancy specifications. For details, see 3.2.3 Solution Description.
2 Solution Overview
2.1 Background
2.1 Background
The rapid development of mobile networks brings not only rapid business growth but also unprecedented challenges for operators.
The smartphone penetration rate is increasing rapidly. As shown in Figure 2-1, from July 2011 to May 2013, the smartphone penetration rate increased from 15% to 40%, and the number of busy hour call attempts
(BHCA) per user increased from 1.13 to 8.21. Such an increase requires operators to expand network capacity, and in particular signaling processing capabilities. Currently, operators have requirements for
sustainable RNC capacity expansion. Traditional RNC splitting cannot meet operators' requirements and more effective capacity expansion measures are required.
Figure 2-1 Smartphone penetration rate
click to enlarge
Mobile network services may be interrupted on a large scale if an operator's equipment room encounters natural disasters such as floods and earthquakes, which may cause power failures. The RNC is a service
convergence node of the UMTS network that has high reliability requirements. Service disruptions caused by RNC failures have severe impacts.
To meet the preceding requirements, Huawei has developed the RNC in Pool solution. This solution enables interconnected RNCs to form a resource pool to provide the following benefits:
Reduces the hardware specification limitations of a single RNC

Allows for smooth RNC capacity expansion
Supports remote backup
Improves RNC reliability
Conventional RNC Capacity Expansion

With the traditional RNC capacity expansion method, expansion is achieved by adding boards, subracks, or cabinets. However, the maximum number of subracks and cabinets are six and two, respectively. When
this limit is reached, RNC splitting is required. Some base stations under the original RNC are reparented to a new RNC to reduce the load of the original RNC as shown in Figure 2-2.
Figure 2-2 Conventional RNC capacity expansion
RNC splitting involves the following operations:
1. Purchasing a new set of RNC hardware and hardware licenses

2. Purchasing a set of software license packages for the new RNC, including all the required software features
3. Planning a new set of RNC configuration parameters for the Iu, Iur, and Iub interfaces. In addition to configuring interface parameters on the new RNC, you need to configure related interface
parameters on the CN and other network elements (NEs), such as the neighboring RNCs, GSM BSCs, and LTE eNodeBs.
4. For base stations that have been reparented to the new RNC, updating the neighbor relationships of cells under the old and new RNCs as well as the neighbor relationships of cells under the neighboring
RNCs, GSM BSCs, and LTE eNodeBs
5. Reparenting base stations in batches during off-peak hours. You need to observe network KPIs and ensure integrity of configurations.
Steps 3, 4, and 5 involve network planning and implementation. Any error or omission in planning and implementation may deteriorate network KPIs. Data configurations and base station reparenting for RNC
splitting are complicated and therefore need to be optimized.
RNC Capacity Expansion Using RNC in Pool Load Sharing

RNC capacity expansion using RNC in Pool Load Sharing involves the following operations:
1. Purchasing a new set of RNC hardware and hardware licenses

2. Purchasing a license for the RNC in Pool Load Sharing feature. You may also need to purchase a license for the RNC in Pool Multiple Logical RNCs feature.
3. Planning Iur-p interface parameters and activating the feature during off-peak hours
When RNC capacity expansion is performed using the RNC in Pool feature, the following operations do not need to be performed:
Reparenting base stations

Planning a set of configuration parameters for the Iu, Iur, and Iub interfaces of the new RNC
Planning new neighbor relationship
Modifying interface and neighbor relationship configurations of the CN, neighboring RNCs, GSM BSCs, and LTE eNodeBs
Operation and maintenance costs are greatly reduced since the preceding operations are not required. RNC capacity expansion using the RNC in Pool Load Sharing feature enables smooth RNC capacity expansion
and postpones or even avoids RNC splitting.
Control- and User-Plane Capacity Expansion, Load Decrease, or Burst Traffic Handling
For a BSC6900 in an inventory network, when the maximum hardware specifications of two cabinets and six subracks are reached but the signaling processing capability cannot meet the requirements, the RNC in
Pool Load Sharing feature can be used for capacity expansion. With this feature, O&M costs arising from RNC splitting can be avoided.
If the average SPU load of an RNC is higher than 45%, the operator can implement load sharing among multiple BSC6900s and one BSC6910 to improve network reliability and prevent the impact of burst
signaling or data traffic on the RNC. The load sharing solution prevents KPI deterioration caused by a continuous increase in CPU load and improves hardware usage.
RNC Node Redundancy and Hitless Upgrade

The RNC in Pool Node Redundancy feature is suitable in the following scenarios: The operator has high RNC reliability requirements; the government has high reliability requirements for the operator's services
(for example, the service interruption duration cannot exceed 30 minutes); the operator requires that the RNC provide redundancy in the event of system failures, such as power failure, transmission interruptions,
or device failures. If there are multiple BSC6900s in an existing network, it is recommended that node redundancy be implemented among multiple BSC6900s and one BSC6910. In this case, use the BSC6910 as
the backup RNC for multiple BSC6900s.
Currently, an RNC upgrade may interrupt services provided by the RNC for several minutes. During the upgrade, idle UEs are out of service and online users experience call drops. When an operator requires a
smooth RNC upgrade and wants to mitigate upgrade impacts, the RNC in Pool Node Redundancy feature can be used. This feature ensures that idle UEs are not out of service during the upgrade and limits any
interruption of services experienced by online users to less than 20s. When the RNC in Pool Node Redundancy feature is enabled before the RNC upgrade, services are switched over to the backup RNC and are
therefore not affected during the upgrade. After the upgrade, services are switched back to the master RNC. This process is called hitless upgrade.
NOTE:
The RNC in Pool Load Sharing and RNC in Pool Node Redundancy features can be used together if the preceding scenarios co-exist.

With the RNC in Pool feature, interconnected RNCs form a resource pool over the interface Iur-p (Iur-pool), a Huawei-proprietary interface. Figure 2-3 shows the network architecture for RNC in Pool.
Figure 2-3 Network architecture for RNC in Pool
RNC in Pool consists of the following optional features:
WRFD-150211 RNC in Pool Load Sharing (control plane and user plane)
WRFD-150212 RNC in Pool Node Redundancy
WRFD-150240 RNC in Pool Multiple Logical RNCs
3GPP has defined the MSC/SGSN Pool networking function, which provides load sharing and node redundancy for CN nodes. The differences between MSC/SGSN Pool and RNC in Pool are as follows:
1. MSC Pool is defined by 3GPP, whereas RNC in Pool is a feature introduced by Huawei.
2. For MSC Pool, the NAS node selection function (NNSF) is performed by lower-layer NEs (RNC or MGW). For RNC in Pool, the RNC node selection function is performed through the communication
between RNCs in the pool (through Iur-p interface communication).
Figure 2-4 Differences between MSC Pool and RNC in Pool

click to enlarge

An operator has deployed BSC6900s/BSC6910s in UO mode on the network. The average CPU load of an RNC exceeds 45% during busy hours. In addition to adding boards to the RNC for capacity expansion,
the operator expects to expand the control-plane (CP) and user-plane (UP) capacity to reduce the average load of SPU and DPU boards. Alternatively, the operator expects to solve the insufficient SPU/DPU/GPU
board capacity problem caused by burst traffic. The planned busy hour call attempts (BHCA) and data throughput to be expanded do not exceed 90% of the original BSC6900/BSC6910 specifications.

The RNC in Pool solution reduces the average CPU load (SPU and DPU load) of existing BSC6900s, prevents service interruptions caused by burst traffic, and eliminates complex O&M after RNC splitting is
performed. As a result, this solution enables smooth capacity expansion.
With the RNC in Pool solution, next-generation large-capacity BSC6910s can be used on the inventory network for capacity expansion.
In addition, load sharing can be implemented between two BSC6910s to handle burst traffic.

WRFD-150211 RNC in Pool Load Sharing Control plane load sharing is introduced in RAN15.0, and user RNC in Pool Feature Parameter Description
plane load sharing is introduced in RAN16.0.
WRFD-150240 WRFD-150240 RNC in Pool Multiple Logical RAN15.0 RNC in Pool Feature Parameter Description
RNCs
WRFD-150211 RNC in Pool Load Sharing

The RNC in Pool Load Sharing feature enables the BSC6910 to offload traffic from other BSC6900s or BSC6910s in the same pool. Load sharing decisions are made during the RRC connection setup of
each user.
NOTE:
Load sharing has no impact on other NEs except RNCs in the pool.
Figure 3-1 Load sharing provided by a BSC6910 for a BSC6900
Figure 3-2 Load sharing between BSC6910s

When the WRFD-150240 RNC in Pool Multiple Logical RNCs feature is used together with the RNC in Pool Load Sharing, a BSC6910 can carry multiple logical RNCs (up to 7, one of which is the
logical RNC of the BSC6910 itself) and provides load sharing or Iub-Flex for n BSC6900s (n ≤ 6) or BSC6910s (n ≤ 3). Figure 3-3 and Figure 3-4 assume that the value of n is 3. The BSC6900 does not
support the WRFD-150240 RNC in Pool Multiple Logical RNCs feature.
Figure 3-3 A BSC6910 carrying multiple logical RNCs and offloading traffic for n BSC6900s (n + 1, n = 3)
Figure 3-4 A BSC6910 carrying multiple logical RNCs and offloading traffic for n BSC6910s (n + 1, n = 3)
The RNC in Pool Load Sharing features do not affect other NEs except RNCs in the pool. The CME automatically synchronizes the parameter settings of the logical RNCs in a pool from the master RNC
(BSC6900 or BSC6910) to the overflow RNC (BSC6910). You do not need to manually synchronize parameter settings on the two RNCs.
The signaling of a UE whose load is shared between RNCs is transmitted over the Iur-p interface. Therefore, transmission delay and quality of service (QoS) over the Iur-p interface must meet the specified
requirements. Otherwise, call signaling processing is affected and therefore causes potential call loss. It is recommended that RNCs in the same equipment room be configured to form a pool for load sharing.
For details about transmission requirements and feature deployment, see RNC in Pool Feature Parameter Description.
The RNC in Pool Load Sharing feature does not provide load sharing for cell signaling processing capabilities. If the cell signaling processing load of some CPU subsystems in a BSC6900 is high, the CPU load
may not decrease after the RNC in Pool Load Sharing feature is enabled. To balance the cell signaling processing load of these CPU subsystems, you need to adjust the NodeBs and cells among RNC subsystems.
The RNC in Pool Load Sharing feature is used to reduce and balance the average CPU load of RNCs. However, it cannot be used to balance the load between the subracks, boards, and CPU subsystems of a single
RNC.

The operator has a high requirement for RNC reliability and requires shorter service interruption durations to achieve fast recovery of RNC services in the event of disasters or software/hardware failures.
To use the RNC in Pool Node Redundancy feature, users must add dual-homed Iub links for base stations. It is recommended that this feature be enabled when IP transmission is used over the Iub interface.

The RNC in Pool solution improves RNC reliability.

The RNC in Pool solution uses next-generation large-capacity BSC6910s to improve the reliability of both existing and newly deployed networks. In addition, this solution shortens the service interruption time
during RNC software upgrade, achieving hitless upgrade.

WRFD-150212 RNC in Pool Node Redundancy RAN15.0 RNC in Pool Feature Parameter Description
RNCs
RNC in Pool Node Redundancy

The RNC in Pool Node Redundancy feature enables a BSC6910 to provide node redundancy for other BSC6900s or BSC6910s.
NOTE:
The RNC in Pool Node Redundancy feature does not have any impact on the neighboring cells of neighboring NEs. After services on the backup RNC are recovered, the RNC ID and neighbor relationships remain unchanged. The backup
Iu/Iur/Iub links must be configured on the backup RNC. Related interface data must also be configured on the CN and neighboring RNC.
Figure 3-5 Node redundancy provided by a BSC6910 for a BSC6900
Figure 3-6 Node redundancy between BSC6910s

When the WRFD-150240 RNC in Pool Multiple Logical RNCs feature is used together with the RNC in Pool Node Redundancy feature, a BSC6910 can carry multiple logical RNCs (up to 7, one of
which is the logical RNC of the BSC6910 itself) and provide node redundancy for n BSC6900s (n ≤ 6) or BSC6910s (n ≤ 6). In Figure 3-7 and Figure 3-8, assume that the value of n is 3. The BSC6900
does not support the WRFD-150240 RNC in Pool Multiple Logical RNCs feature.
Figure 3-7 A BSC6910 carrying multiple logical RNCs and providing node redundancy for multiple BSC6900s (n + 1, n = 3)
Figure 3-8 A BSC6910 carrying multiple logical RNCs and providing node redundancy for multiple BSC6910s (n + 1, n = 3)
For a GU dual-mode controller, the 2G and 3G controller function can be simultaneously backed up or switched over in either of the following scenarios: one BSC6900 (master RNC)+one BSC6910
(backup RNC), and one BSC6910+one BSC6910 (the two BSC6910s provide node redundancy for each other). GU dual-mode controllers support neither simultaneous 2G and 3G backup nor switchover
in other scenarios.
The CME automatically synchronizes the parameter settings of the logical RNCs in a pool from the master RNC (BSC6900 or BSC6910) to the backup RNC (BSC6910). You do not need to manually synchronize
parameter settings on the two RNCs.
After the master RNC becomes faulty and services are resumed on the backup RNC, logical RNC parameter modification on the backup RNC cannot be automatically synchronized to the master RNC. Therefore,
you need to record the modification and manually change the logical RNC parameters on the master RNC after the master RNC recovers. This ensures that the same parameter modifications are made on the
master RNC.
The node redundancy solution must be planned based on the actual networking scenarios. Generally, it is recommended that the master RNC and backup RNC be located in different places (remote disaster
recovery) to avoid simultaneous master and backup RNC failures.
If the RNC switchover mode is set to manual mode, the maintenance personnel need to first observe whether an RNC is faulty based on device alarms and then determine whether to trigger an RNC switchover. An
RNC switchover will cause call drops for all online users. Therefore, exercise caution when performing this operation.
If the RNC switchover mode is set to automatic mode, the system automatically detects whether an RNC is faulty and triggers an RNC switchover. In addition, the system can check the status of the Iu interface
according to data configurations. If the Iu interface status is abnormal, the system triggers an RNC switchover.
For details about feature deployment, see RNC in Pool Feature Parameter Description.
In the case of hitless upgrade, switch services of the master RNC to the backup RNC before upgrading the master RNC. After the upgrade is complete, switch services back to the master RNC. In this way, two
RNC switchovers are performed.
If the operator has high reliability requirements for RNCs, multiple RNCs among N+1 RNCs may require node redundancy. In this case, the sum of the capacity of N RNCs must be planned on the backup RNC.
When upgrading the R version of the RNCs in a pool, not all RNCs need to be upgraded within one day, but users must disable the automatic synchronization function before the upgrade process begins. During
the period when the RNCs in a pool have different R versions, you need to manually synchronize parameter updates between the master and backup RNCs.
WRFD-150211 RNC in Pool Load Sharing Control plane load sharing is introduced in RAN15.0. RNC in Pool Feature Parameter Description
User plane load sharing is introduced in RAN16.0.
WRFD-150212 RNC in Pool Node Redundancy RAN15.0 RNC in Pool Feature Parameter Description
RNCs

CP Control Plane
Iur-p Iur interface for Pool
UP User Plane
1. RNC in Pool Feature Parameter Description
WCDMA RAN
UMTS U900 and U850 Network Solution Guide
Issue 02
Date 2016-03-28

Notice
1.4.6 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
3.1.1 Scenario 1: Wide Suburban Coverage
3.1.1.2 Solution Purpose
3.1.2 Scenario 2: Offloading for Hotspots in Urban Areas
3.1.3 Scenario 3: Urban Intensive Coverage
3.1.4 Scenario 4: Overlay Networking
3.2 Main Challenges
3.2.1 Challenge 1: Non-standard UMTS Bandwidth
3.2.2 Challenge 2: Dual-Carrier Deployment
3.2.2.5 Impact Assessment
3.2.3 Challenge 3: External Interference
3.2.4 Challenge 4: User Throughput Improvement
4 Features Involved in the Solution
1.1 Scope

1.3 Change History
1.1 Scope
This document describes the U900 and U850 network solution, which is used to improve user experience for UMTS networks.

Need to understand the U900 and U850 network solution

1.3 Change History

RAN18.1 02 (2016-03-28)
This issue includes the following changes.
Added 3.2.2 Challenge 2: Dual-Carrier Deployment.
RAN18.1 01 (2016-02-29)
Introduced the Adaptive Interference Rejection feature. For details, see 3.2.3 Challenge 3: External Interference.
2 Solution Overview
2.1 Background
2.1 Background
The core UMTS frequency bands are UMTS 2100 MHz (band I) and UMTS 1900 MHz (band II) frequency bands, which are used in multiple commercial UMTS networks around the world. UMTS networks
require spectrums with satisfactory transmission performance because of rapid packet switched (PS) service development and the exponential growth of smartphone use in recent years. To satisfy this need, the
UMTS 900 MHz (band VIII) and UMTS 850 MHz (band V) frequency bands are put to use.
Table 2-1 lists all of the UMTS frequency bands supported by the 3GPP TS 25.101 protocol.
Table 2-1 UMTS frequency bands
Band Center Frequency Bandwidth (MHz) Uplink Frequency (MHz) Downlink Frequency (MHz) Main District
I 2100 2 x 60 1920 - 1980 2110 - 2170 -

Band Center Frequency Bandwidth (MHz) Uplink Frequency (MHz) Downlink Frequency (MHz) Main District
II 1900 2 x 60 1850 - 1910 1930 - 1990 PCS band in Americas
III 1800 2 x 75 1710 - 1785 1805 - 1880 Europe, Asia, and Brazil
IV 1700/2100 2 x 45 1710 - 1755 2110 - 2155 A new band in USA and Americas
V 850 2 x 25 824 - 849 869 - 894 USA, Americas, and Asia
VI 800 2 x 10 830 - 840 875 - 885 Japan
VII 2600 2 x 70 2500 - 2570 2620 - 2690 -
VIII 900 2 x 35 880 - 915 925 - 960 Europe and Asia
IX 1700 2 x 35 1749.9 - 1784.9 1844.9 - 1879.9 Japan
X 1700/2100 2 x 60 1710 - 1770 2110 - 2170 -
XI 1500 2 x 25 1427.9 - 1452.9 1475.9 - 1500.9 Japan
XII 700 2 x 18 698 - 716 728 - 746 -
XIII 700 2 x 10 777 - 787 746 - 756 -
XIV 700 2 x 10 788 - 798 758 - 768 -
NOTE:
In this document, the networks using either UMTS band I or UMTS band II or both are referred to as U2100 networks, the networks using UMTS band VIII are referred to as U900 networks, and the networks using UMTS band V are referred to as U850
networks.

A U900/U850 network has the following advantages over a U2100 network:
Wider coverage
A U900/U850 network, which works in low frequency bands, has less path loss and propagates signals farther than a U2100 network.
A U900/U850 network is based on the Okumura-Hata model and a U2100 network based on COST231-Hata. Theoretically, the propagation loss of a U900/U850 network is 12 dB less than that of a
U2100 network. Therefore, a U900/U850 network provides wider coverage and requires fewer sites. A U900/U850 network applies to suburban areas requiring wide coverage, where network deployment
costs can be reduced.
Intensive coverage
Test results show that both the penetration and propagation losses of a U900/U850 network are less than those of a U2100 network with the same outdoor signal level. The penetration loss of a
U900/U850 network is about 1-3 dB less than that of a U2100 network. Therefore, a U900/U850 network is also applicable to urban areas requiring deep coverage.
Overlay networking
With the development of the network, overlay networking may occur. For example, to protect existing investment, the operator can deploy a U900/U850 network in the coverage area of an existing U2100
network. Then, the two UMTS networks work together to form an overlay network.
Based on the analysis above, a U900/U850 network applies to the following scenarios:

A U900/U850 network must be commercially deployed in one of these scenarios. However, there may be several challenges.

The spectrums in the U900/U850 frequency bands specified by 3GPP are scarce. If most of these spectrums are occupied by GSM and CDMA networks, each of the spectrums available for U900/U850
networks may be less than 5 MHz. In this case, U900/U850 networks have to support non-standard frequency spacing.
Operators prefer deploying the 900/850 MHz band to meet the service requirements of increasing number of UMTS users, and therefore the U900/U850 band needs to evolve to support dual carriers.
Studies of numerous networks around the globe have shown that U900/U850 networks experience interference from many objects, such as street lights, walkie-talkies, TV amplifiers, and even electronic
billboards. The external interference negatively affects the coverage and capacity of U900/U850 networks.
A U900/U850 network may also face the following challenge in scenarios 2 and 3:

When the U900/U850 and U2100 networks cover the same area, the U900/U850 network uses a single carrier and the U2100 network uses multiple carriers in most cases. In this scenario, it is best
practice to make multi-carrier UEs to perform services on multiple carriers, so as to improve user throughput.
This document provides solutions to the challenges on a U900/U850 and U2100 dual-band network in these scenarios.
NOTE:
The terminals must support the U900/U850 band. As of 2008, mainstream terminals support the U900/U850 band.

Table 2-2 shows the major processes that are employed by the solution to improve the experience of UEs in the URA_PCH, CELL_PCH, CELL_FACH, CELL_DCH, or system access state and of UEs in idle
mode.
NOTE:
The major processes are the same for UEs in the CELL_PCH state and UEs in the URA_PCH state. Therefore, this document does not cover UEs in the URA_PCH state.
Table 2-2 Major processes
Application Scenario Major Process
UEs in Idle Mode and UEs in the CELL_PCH or UEs in Access Mode UEs in the CELL_DCH State
CELL_FACH State
Wide suburban coverage Cell reselection - Inter-frequency-band handover (IFHO)
Offloading for hotspots in urban areas Cell reselection - Blind handover (BlindHO), IFHO, load-based inter-frequency handover
based on measurement (MCLDR)
Urban intensive coverage Cell reselection BlindHO, directed retry decision (DRD), RRC inter- BlindHO, IFHO, MCLDR
frequency redirection
Overlay networking Cell reselection RRC inter-frequency redirection Inter-frequency load balancing (CLB), IFHO
This section provides guidelines about how to use features or feature combinations in each application scenario. The methods of activating these features are omitted in this document. For details about these
methods, see the corresponding feature parameter description.

3.2 Main Challenges

In this scenario, U2100 networks already provide contiguous coverage in urban and other densely populated areas. To expand UMTS coverage to rural areas, U900/U850 networks are deployed. Because U900 and
U850 networks are less costly, deploying them reduces the deployment costs in rural areas.
Figure 3-1 shows this scenario.
Figure 3-1 Scenario 1
click to enlarge

U900/U850 networks are deployed in suburban areas and they overlap the existing U2100 networks in urban areas.
In this scenario, the solution is used to ensure that UEs can be successfully handed over between cells in U900/U850 networks (referred to as U900/U850 cells) and cells in U2100 networks (referred to as U2100
cells).
In addition, this solution is also used to avoid call drops caused by coverage overlap in suburban areas, where the terrain is complex and special sites, such as mountain-top sites, may exist.

The following are the major processes that are used by the solution to hand over UEs between U2100 cells and U900/U850 cells:
For UEs in idle mode and UEs in the CELL_PCH or CELL_FACH state:
Coverage-based cell reselections
For UEs in the CELL_DCH state:
Coverage-based inter-band inter-frequency handovers
Figure 3-2 Major processes in scenario 1
click to enlarge
Features and Functions Involved in the Solution

Table 3-1 lists the features and functions involved in this solution.
Table 3-1 Features and functions involved in this solution
Feature ID Feature Name Feature Description Introduced In... Reference Document
WRFD-010401 System Information Broadcasting This feature enables UEs to perform cell reselections between RAN2.0 UE Behaviors in Idle Mode Feature Parameter
different frequency bands. Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, This feature is used to support UEs in the URA_PCH, RAN2.0 URA-Cell Update Feature Parameter Description
CELL-PCH, URA-PCH, CELL-FACH) CELL_PCH, CELL_FACH, or CELL_DCH state.
WRFD-010801 Intra RNC Cell Update This feature is used to support intra-RNC cell update triggered by RAN2.0 URA-Cell Update Feature Parameter Description
the causes specified by 3GPP.
WRFD-010802 Inter RNC Cell Update This feature is used to support inter-RNC cell update triggered by RAN2.0 URA-Cell Update Feature Parameter Description
the causes specified by 3GPP.
WRFD-020302 Inter Frequency Hard Handover Based on This feature is used to support coverage-based inter-frequency RAN2.0 Handover Feature Parameter Description
Coverage handover.
WRFD-020110 Multi Frequency Band Networking Management This feature enables inter-frequency-band mobility management. RAN10.0 Multi-Frequency Band Networking Management
WRFD-020401 Inter-RAT Redirection Based on Distance If a UE initializes a voice call with a long distance to the antenna, RAN12.0 Intelligent Access Control Feature Parameter
UMTS RAN can consider it as a call attempt in the pilot Description
contaminated area, and redirect it to GSM to avoid handover drop
in the subsequent call procedure.
WRFD-02040005 Inter-Frequency Redirection Based on Distance This feature solves the coverage overlap problem for UMTS RAN14.0 Intelligent Access Control Feature Parameter
networks. Upon receiving an RRC CONNECTION REQUEST Description
message from a UE, the RNC calculates the propagation delay for
the UE. The RNC then compares the propagation delay with the
inter-frequency redirection threshold and performs inter-frequency
redirection based on the distance between the NodeB and the UE.
The features WRFD-02040005 Inter-Frequency Redirection Based on Distance and WRFD-020401 Inter-RAT Redirection Based on Distance must be activated on a per scenario basis. Other features in Table 3-1
can be all activated in one scenario.
WRFD-02040005 Inter-Frequency Redirection Based on Distance

If coverage overlap falls into U2100 coverage areas, activate this feature only in the following scenarios:
U900/U850 ultra-high sites
Cells prone to coverage overlap
WRFD-020401 Inter-RAT Redirection Based on Distance

If coverage overlap falls into the coverage areas of a different system, activate this feature only in the following scenarios:
U900/U850 ultra-high sites
Cells prone to coverage overlap
If you cannot determine whether inter-frequency or inter-RAT coverage exists in coverage overlap areas, you can enable both Inter-Frequency Redirection Based on Distance and Inter-RAT Redirection Based on
Distance. In this situation, the RNC preferentially performs the inter-frequency redirection.
When planning and configuring data, configure U900/U850 cells as mutual neighboring cells for U2100 cells on the boarder of the U2100 networks and U900/U850 networks. In addition, set
HOCovPrio(BSC6900,BSC6910) to 1 or 3 and SIB11Ind(BSC6900,BSC6910) to TRUE, respectively.
NOTE:
The HOCovPrio(BSC6900,BSC6910) parameter indicates the priority of coverage-based inter-frequency handover in a neighboring cell. When the parameter is set to 0, the neighboring cell does not support coverage-based inter-frequency handover.
When the parameter is set to 1, coverage-based inter-frequency handover has the highest priority in the neighboring cell. When the parameter is set to 3, coverage-based inter-frequency handover has the lowest priority in the neighboring cell.
For details about parameters involved, see BSC6900 UMTS Parameter Reference or BSC6910 UMTS Parameter Reference.

U2100 networks with contiguous coverage are deployed in urban areas. To expand UMTS capacity, U900/U850 networks are deployed in some hot spots and some of the load from the U2100 networks is shifted
to the U900/U850 networks. The coverage in the U900/U850 networks is not contiguous. As a result, coverage-triggered inter-frequency handovers as well as ping-pong handovers are easily triggered.
click to enlarge

In this scenario, the objective of the solution is to ensure that U900/U850 networks can offload a certain amount of traffic from U2100 networks.
The coverage in the U900/U850 networks in this scenario is not contiguous. As a result, coverage-triggered inter-frequency handovers as well as ping-pong handovers are easily triggered. In this case, another
objective of the solution is to control coverage-triggered inter-frequency handovers and prevent ping-pong handovers.

The following are the major processes used by the solution:
click to enlarge
NOTE:
DRD is included in "BlindHO" and is not separately indicated.
Enabling UEs to randomly camp on U2100 or U900/U850 cells using cell-reselection parameters
(Recommended) Setting a threshold for camping on the target cell to reduce the number of UEs that camp on U2100 cell edges and the number of coverage-based inter-frequency handovers
When U900/U850 cells are co-sectored with U2100 cells:
Shifting PS UEs in U2100 cells in the basic congestion state to U900/U850 cells using load-triggered inter-frequency blind handover
When U900/U850 cells are not co-sectored with U2100 cells:
Shifting PS UEs in U2100 cells in the basic congestion state to U900/U850 cells using load-triggered measurement-based inter-frequency handover. This operation prevents UEs from being
blindly handed over to incorrect U900/U850 cells when U2100 cells and U900/U850 cells use different frequencies but cover the same area.
Mobility management
Perform the following operations to prevent ping-pong handovers between U2100 cells and U900/U850 cells:
Enable UEs in U900/U850 cells to be shifted to U2100 cells that do not share a site with the U900/U850 cells using coverage-based inter-frequency handovers.
Enable UEs in U2100 cells to be shifted to U900/U850 cells that share a site with U2100 cells using coverage-based inter-frequency handovers.
Parameter self-optimization
In the inter-band load balancing mechanism, the RNC automatically adjusts parameter settings for UEs in idle mode, access mode, and connected mode based on load differences between U900/U850
cells and U2100 cells on live networks. The adjustment is to avoid heavy load in U900/U850 cells.
NOTE:
In this document, "co-sector" indicates that a U2100 cell and a U900/U850 cell share the same site and azimuth, and "not co-sector" indicates that a U2100 cell and a U900/U850 cell do not share the same site or azimuth.

WRFD-010401 System Information Broadcasting This feature enables UEs to perform cell reselections between different RAN2.0 UE Behaviors in Idle Mode Feature Parameter
frequency bands. Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, This feature is used to support UEs in the URA_PCH, CELL_PCH, RAN2.0 URA-Cell Update Feature Parameter
CELL-PCH, URA-PCH, CELL-FACH) CELL_FACH, or CELL_DCH state. Description
WRFD-010801 Intra RNC Cell Update This feature is used to support intra-RNC cell update triggered by the RAN2.0 URA-Cell Update Feature Parameter
causes specified by 3GPP. Description
WRFD-010802 Inter RNC Cell Update This feature is used to support inter-RNC cell update triggered by the RAN2.0 URA-Cell Update Feature Parameter
causes specified by 3GPP. Description
WRFD-020302 Inter Frequency Hard Handover Based on This feature is used to support coverage-based inter-frequency handover. RAN2.0 Handover Feature Parameter Description
Coverage
WRFD-020106 Load Reshuffling This feature provides multiple load reshuffling policies that a cell in the RAN2.0 Load Reshuffling Feature Parameter
basic congestion state can use to decrease the cell load and increase the Description
access success rate.
WRFD-020103 Inter Frequency Load Balance This feature enables some UEs in a cell in the basic congestion state to be RAN2.0 Inter Frequency Load Balance Feature
handed over to an inter-frequency co-coverage cell to reduce the load of the Parameter Description
source cell. This feature employs load-triggered inter-frequency blind
handover and load-triggered measurement-based inter-frequency handover.
WRFD-020400 DRD Introduction Package This feature supports inter-frequency/inter-RAT DRD and redirection. RAN3.0 Directed Retry Decision Feature Parameter
Description
WRFD-020110 Multi Frequency Band Networking This feature enables inter-frequency-band mobility management on UEs in RAN10.0 Multi-Frequency Band Networking
Management co-coverage cells. Management Feature Parameter Description
WRFD-020160 Enhanced Multiband Management This feature is used to support load-triggered measurement-based inter- RAN12.0 Multi-Frequency Band Networking
frequency-band handover. Management Feature Parameter Description
WRFD-171214 Inter-Band Load Balancing This feature is used to automatically adjust parameter settings for UEs in RAN17.1 Inter-Band Load Balancing Feature Parameter
idle mode, access mode, and connected mode, so as to achieve load Description
balancing between high and low bands.
Activate all of the features listed in Table 3-2. These features can be activated simultaneously. When planning and configuring data, note the following for UEs in different states.
For UEs in idle mode:

You are advised to set the IdleSintersearch(BSC6900,BSC6910) parameter to a large value (for example 6 or 127) for U900/U850 cells to enable UEs to initiate signal quality measurement
on inter-frequency cells as early as possible.
You are also advised to set the IdleQoffset2sn(BSC6910,BSC6900) parameter to 3 to enable UEs in idle mode to preferentially camp on U2100 cells. This reduces the load of U900/U850
cells.
For UEs in the CELL_PCH or CELL_FACH state:

You are advised to set the ConnSintersearch(BSC6900,BSC6910) parameter to the recommended value for U900/U850 cells. If the FACHs in the U900/U850 cells are congested, set this parameter
to a large value (for example, 6) to enable UEs to initiate signal quality measurement on U2100 cells as early as possible. Doing so allows UEs in U900/U850 cells to be shifted to U2100 cells in time
through cell reselection.
Table 3-3 lists the cell selection/reselection parameter settings generally recommended for UEs in idle mode and UEs in the CELL_PCH or CELL_FACH state.
Table 3-3 Cell-reselection parameter settings generally recommended for UEs in idle mode and UEs in the CELL_PCH or CELL_FACH state
Parameter ID Recommended Value for U900/U850 Cell Recommended Value for U2100 Cell
Command: ADD UCELLSELRESEL
Qqualmin(BSC6900,BSC6910) -18 -18
Qrxlevmin(BSC6900,BSC6910) -58 -58
IdleQhyst2s(BSC6900,BSC6910) 1 1
IdleSintrasearch(BSC6900,BSC6910) 127 5
IdleSintersearch(BSC6900,BSC6910) 127 4
ConnSintrasearch(BSC6900,BSC6910) 5 5
ConnSintersearch(BSC6900,BSC6910) 4 4
Command: MOD UCELLSIBSWITCH
SibCfgBitMap(BSC6900,BSC6910) SIB4-1 SIB4-0
Command: ADD UINTERFREQNCELL

InterNCellQualReqFlag(BSC6910,BSC6900) TRUE N/A
Qqualmin(BSC6900,BSC6910) -12 N/A
Qrxlevmin(BSC6900,BSC6910) -51 N/A

For U2100 cells, set the BlindHoFlag(BSC6900,BSC6910) parameter to TRUE to ensure that UEs in U2100 cells can be blindly handed over to U900/U850 cells.
For U900/U850 cells, you are advised to select InterFreqLDHO under the parameters related to uplink or downlink LDR actions in the ADD UCELLLDR command.

For U900/U850 cells, select the InterFreqLDHO check box under the parameters related to uplink or downlink LDR actions in the ADD UCELLLDR command. Then, set the
InterFreqLDHOMethodSelection(BSC6900,BSC6910) and DrdOrLdrFlag(BSC6900,BSC6910) parameters to MEASUREHO and TRUE, respectively.
If the solution Offloading for Hotspots in Urban Areas is applied, pay attention to the following during planning and configuration:
Inter-frequency neighboring cell settings
Table 3-4 provides the recommended settings for parameters related to inter-cell interoperability between U900/U850 cells and U2100 cells.
Table 3-4 Recommended settings for parameters related to inter-cell interoperability between U900/U850 cells and U2100 cells
Cell Neighboring Cell SIB11Ind(BSC6900,BSC6910) IdleQoffset2sn(BSC6900,BSC6910) HOCovPrio(BSC6900,BSC6910) BlindHoFlag(BSC6900,BSC6910) DrdOrLdrFlag(BSC6900,BSC6910)

Cell Relationship
U2100 U900/U850 Co-Sector TRUE 3 2 TRUE FALSE

cells cells
CoSite TRUE 3 2 FALSE TRUE
No-CoSite TRUE 3 0 FALSE FALSE
U900/U850 U2100 cells Co-Sector TRUE -3 2 FALSE TRUE

cells
CoSite TRUE -3 2 FALSE TRUE
No-CoSite TRUE -3 0 FALSE TRUE
NOTE:
In this document, "Co-Sector" indicates that cells operating on the U2100 and U900/U850 bands are deployed on the same site with the same azimuth; "CoSite" indicates that cells operating on the U2100 and U900/U850 bands are deployed on the same
site with different azimuths; "No-CoSite" indicates that cells operating at the U2100 and U900/U850 bands are separately deployed on different sites.
Automatic parameter optimization

The Inter-Band Load Balancing feature is intended to adjust parameter settings for UEs in idle mode, in access mode, and in connected mode. Based on the recommended solution, it adaptively adjusts
parameter settings to achieve load balancing between high and low frequency bands.

U2100 networks provide contiguous coverage in urban areas. To achieve intensive coverage in these areas, U900/U850 networks providing contiguous coverage are deployed. Figure 3-5 shows this scenario.
click to enlarge

In this scenario, the objective of the solution is to ensure that U900/U850 networks can address the weak coverage issue and provide services in coverage holes. Another objective of the solution is to prevent
U900/U850 cells from being overloaded by loads from the U2100 cells.

The following are the major processes used by the solution:
click to enlarge
NOTE:
DRD is included in "BlindHO" and is not separately indicated.
(Recommended) Setting a threshold for camping on the target cell to reduce the number of UEs that camp on U2100 cell edges and the number of coverage-based inter-frequency handovers
For UEs in the system access state:
Some UEs that camp on U900/U850 cells access and perform services in U2100 cells.
Shifting HSDPA UEs in U900/U850 cells to U2100 cells through load-balancing-triggered DRD-based blind handover.
Using UE-location-based multi-frequency-band directed retry to prevent UEs on U900/U850 cell edges from being blindly handed over to U2100 cells. This operation can prevent UEs from
U2100 cell access failures.
Redirecting PS UEs in U900/U850 cells to U2100 cells

Shifting PS UEs in U900/U850 cells in the basic congestion state to U2100 cells using load-triggered inter-frequency blind handover.
Shifting PS UEs in U900/U850 cells in the basic congestion state to U2100 cells using load-triggered measurement-based inter-frequency handover. This operation can prevent UEs from being
blindly handed over to incorrect U2100 cells when U900/U850 cells and U2100 cells use different frequencies but cover the same area.
For UEs whose services are released:

After the services of UEs in U900/U850 cells are released, the UEs are redirected to U2100 cells as soon as possible.
Mobility management
To prevent ping-pong handover between U2100 cells and U900/U850 cells, you are advised to ensure that UEs in U2100 cells can be shifted to U900/U850 cells through coverage-based inter-frequency
handover. Furthermore, you are not advised to allow UEs in U900/U850 cells to be shifted to U2100 cells through coverage-based inter-frequency handover.
Parameter self-optimization
In the inter-band load balancing mechanism, the RNC automatically adjusts parameter settings for UEs in idle mode, access mode, and connected mode based on load differences between U900/U850
cells and U2100 cells on live networks. The adjustment is to avoid heavy load in U900/U850 cells.

WRFD-010401 System Information Broadcasting This feature enables UEs to perform cell reselections between different RAN2.0 UE Behaviors in Idle Mode Feature Parameter
frequency bands. Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, This feature is used to support UEs in the URA_PCH, CELL_PCH, RAN2.0 URA-Cell Update Feature Parameter Description
CELL-PCH, URA-PCH, CELL-FACH) CELL_FACH, or CELL_DCH state.
WRFD-010801 Intra RNC Cell Update This feature is used to support intra-RNC cell update triggered by the RAN2.0 URA-Cell Update Feature Parameter Description
causes specified by 3GPP.
WRFD-010802 Inter RNC Cell Update This feature is used to support inter-RNC cell update triggered by the RAN2.0 URA-Cell Update Feature Parameter Description
causes specified by 3GPP.
WRFD-020302 Inter Frequency Hard Handover Based on This feature is used to support coverage-based inter-frequency RAN2.0 Handover Feature Parameter Description
Coverage handover.
WRFD-020106 Load Reshuffling This feature provides multiple load reshuffling policies that a cell in RAN2.0 Load Reshuffling Feature Parameter Description
the basic congestion state can use to decrease the cell load and
increase the access success rate.
WRFD-020103 Inter Frequency Load Balance This feature enables some UEs in a cell in the basic congestion state to RAN2.0 Inter Frequency Load Balance Feature Parameter
be handed over to an inter-frequency co-coverage cell to reduce the Description
load of the source cell. This feature employs load-triggered inter-
frequency blind handover and load-triggered measurement-based
inter-frequency handover.
WRFD-020400 DRD Introduction Package This feature is used to ensure that UEs can perform directed retry and RAN3.0 Directed Retry Decision Feature Parameter
redirection between inter-frequency co-coverage cells. Description
WRFD-020110 Multi Frequency Band Networking This feature enables inter-frequency-band mobility management. RAN10.0 Multi-Frequency Band Networking Management
Management Feature Parameter Description
WRFD-02040004 Traffic Steering and Load Sharing During This feature provides load-balancing-based directed retry for HSDPA RAN10.0 Directed Retry Decision Feature Parameter
RAB Setup UEs. In addition, this feature allows the UTRAN to consider cell loads Description
and service types during RAB assignment to implement traffic
steering and load sharing between different frequencies or frequency
bands.
WRFD-020120 Service Steering and Load Sharing in RRC This feature allows the UTRAN to consider cell loads and service RAN11.0 Intelligent Access Control Feature Parameter
Connection Setup types during RRC connection setup to implement service steering and Description
load sharing between different frequencies through redirection.
WRFD-020160 Enhanced Multiband Management This feature is used to support load-triggered measurement-based RAN12.0 Multi-Frequency Band Networking Management
inter-frequency-band handover. Feature Parameter Description
WRFD-150232 Multiband Direct Retry Based on UE This feature allows the UTRAN to consider path loss during service RAN15.0 Directed Retry Decision Feature Parameter
Location setup or service reconfiguration when multi-band networking is Description
applied. In this way, this feature allocates UEs to different frequency
bands and U900/U850 cells can serve cell edge UEs.
WRFD-160101 System Improvement for RAN16.0 The function Redirection at RRC Connection Release enables the RAN16.0 Redirection at RRC Connection Release Feature
RRC connection release message to carry frequency information, so Parameter Description
that UEs preferentially attempt to camp on frequency specified by
operators after RRC connection is released.
WRFD-171214 Inter-Band Load Balancing This feature is used to automatically adjust parameter settings for UEs RAN17.1 Inter-Band Load Balancing Feature Parameter
in idle mode, access mode, and connected mode, so as to achieve load Description
balancing between high and low bands.
Activate the features listed in Table 3-5. These features can be activated simultaneously except the three described in the following paragraphs. The activation of these three features depends on the scenario.
WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup

You are advised to activate this feature for carriers within the same frequency band.
WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup
You are advised to activate this feature when U900/U850 cells are not co-sectored with U2100 cells.
WRFD-150232 Multiband Direct Retry Based on UE Location
You are advised to activate this feature when U900/U850 cells are co-sectored with U2100 cells.
When planning and configuring data, note the following:

cells.

Table 3-6 lists the cell-reselection parameter settings generally recommended for UEs in idle mode and UEs in the CELL_PCH or CELL_FACH state.
To enable UEs in U900/U850 cells to access and perform services in U2100 cells, you are advised to configure parameters as follows:
You are advised to set the BlindHoFlag(BSC6910,BSC6900) parameter to TRUE to enable UEs in U900/U850 cells to be blindly handed over to neighboring U2100 cells sharing
the same sector.
Set the BlindHOQualityCondition(BSC6900,BSC6910) parameter to prevent UEs on U900/U850 cell edges from failing to be blindly handed over to U2100 cells. This prevents
UE access failures.
Set the LdbDRDSwitchHSDPA(BSC6900,BSC6910) parameter to ON for U900/U850 cells to activate the load-balancing-triggered directed retry algorithm for HSDPA services.
Select RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH under the PROCESSSWITCH2(BSC6900,BSC6910) parameter to ensure that UEs can fall back to their source
cells if they fail to set up radio bearers (RBs).
Configure the following parameters related to the feature Multiband Direct Retry Based on UE Location, as listed in Table 3-7.
Table 3-7 Recommended settings for parameters related to Multiband Direct Retry Based on UE Location for UEs in the system access state
Command: SET UDRD or ADD UCELLDRD
BasedUELocDRDSwitch ON OFF
TraffTypeForBasedUELoc RT-0&NRT-1 RT-0&NRT-0
BasedUELocDRDRemainThd 30 60
PathlossThdForEdge 133 133
PathlossThdForCenter 113 113
BlindHoFlag(BSC6900,BSC6910) Collocated U2100 F2/F3/F4 Collocated U2100 F2/F3/F4
BlindHOQualityCondition(BSC6900,BSC6910) -85 -92 (default)

For U900/U850 cells, configure the following parameters related to the feature Service Steering and Load Sharing in RRC Connection Setup:
Set the TrafficType(BSC6900,BSC6910) parameter to PSHSPA.
Set the RedirSwitch(BSC6900,BSC6910) parameter to ONLY_TO_INTER_FREQUENCY.
Set the RedirFactorOfNorm(BSC6900,BSC6910) parameter based on the quantity of loads that are planned to be shifted from U2100 cells to U900/U850 cells.

For U900/U850 cells, you are advised to set the BlindHoFlag(BSC6900,BSC6910) parameter to TRUE to ensure that UEs in U900/U850 cells can be blindly handed over to U2100
cells.

Set the InterFreqLDHOMethodSelection(BSC6900,BSC6910) parameter to MEASUREHO.
Set the DrdOrLdrFlag(BSC6900,BSC6910) parameter to TRUE.
Inter-frequency neighboring cell settings

Inter-frequency neighboring cell settings apply to idle mode, access mode, connected mode, and mobility management. Table 3-8 provides the recommended settings for parameters related to inter-cell
interoperability between U900/U850 cells and U2100 cells.
Table 3-8 Recommended settings for parameters related to inter-cell interoperability between U900/U850 cells and U2100 cells

Cell Relationship
U2100 cells U900/U850 CoSector TRUE 3 2 TRUE FALSE

cells
CoSite TRUE 3 2 FALSE TRUE
No-CoSite TRUE 3 0 FALSE FALSE

Cell Relationship
U900/U850 U2100 cells CoSector TRUE -3 0 TRUE FALSE

cells
CoSite TRUE -3 0 FALSE TRUE
No-CoSite TRUE -3 0 FALSE TRUE
Automatic parameter optimization

The Inter-Band Load Balancing feature is intended to adjust parameter settings for UEs in idle mode, in access mode, and in connected mode. Based on the recommended solution, it adaptively adjusts
parameter settings to achieve load balancing between high and low frequency bands.

An operator already deploys a U2100 network using a vendor's devices in an area and wants to deploy a U900/U850 network using another vendor's devices in the same area to form an overlay network.
click to enlarge

In this scenario, the objective of the solution is to ensure the following:
Services are properly allocated between U2100 and U900/U850 networks.

The resource utilization in U2100 and U900/U850 networks is high.
The deployment of the U900/U850 networks does not cause key performance indicator (KPI) values to deteriorate or increase network reconstruction costs.
UEs can be handed over between U2100 and U900/U850 networks.
Load sharing can be achieved between U2100 and U900/U850 networks.

The following are the major processes that are used by the solution to hand over UEs that are located in weak-coverage areas or coverage holes in U2100 cells to U900/U850 cells:
click to enlarge
Redirecting PS UEs in U900/U850 cells to U2100 cells
Compatibility tests are required because UEs in the CELL_DCH state are to be handed over between U900/U850 and U2100 cells. To prevent compatibility issues, enable UEs in these cells to shift to
GSM cells through coverage-based inter-RAT handover and then fall back to UMTS cells through cell reselection.
Inter-Frequency Load Balancing Based on Configurable Load Threshold (CLB) can be performed to shift PS UEs in U900/U850 cells that are in the basic congestion state to U2100 cells.
Major processes used by the solution to prevent ping-pong handovers between U2100 and U900/U850 cells are as follows:
If U900/U850 cells provide contiguous coverage, the recommended process is coverage-based inter-frequency handover for UEs in U2100 cells to shift to U900/U850 cells. However, you are
advised to prohibit UEs in U900/U850 cells from shifting to U2100 cells through coverage-based inter-frequency handover.
If U900/U850 cells do not provide contiguous coverage, the recommended process is coverage-based inter-frequency handover for UEs in U900/U850 cells to shift to U2100 cells that do not
share sites with U900/U850 cells and for UEs in U2100 cells to shift to U900/U850 cells that share a site with U2100 cells.
WRFD-010401 System Information Broadcasting This feature enables UEs to perform cell reselections between different frequency RAN2.0 UE Behaviors in Idle Mode Feature
bands. Parameter Description
WRFD-010202 UE State in Connected Mode (CELL- This feature is used to support UEs in the URA_PCH, CELL_PCH, RAN2.0 URA-Cell Update Feature Parameter
DCH, CELL-PCH, URA-PCH, CELL- CELL_FACH, or CELL_DCH state. Description
FACH)
WRFD-010801 Intra RNC Cell Update This feature is used to support intra-RNC cell update triggered by the causes RAN2.0 URA-Cell Update Feature Parameter
specified by 3GPP. Description
WRFD-010802 Inter RNC Cell Update This feature is used to support inter-RNC cell update triggered by the causes RAN2.0 URA-Cell Update Feature Parameter
specified by 3GPP. Description
WRFD-020120 Service Steering and Load Sharing in During RRC connection setup, this feature implements inter-frequency service RAN11.0 Intelligent Access Control Feature
RRC Connection Setup steering based on connection setup causes. Based on the load and redirection Parameter Description
proportion of the target cell, this feature implements load sharing between inter-
frequency cells that cover different areas.
WRFD-140217 Inter-Frequency Load Balancing Based on On an overlay network, this feature can implement CS/PS load balancing between RAN14.0 Inter-Frequency Load Balancing Based on
Configurable Load Threshold inter-frequency cells under different RNCs. Configurable Load Threshold Feature
Activate all of the features listed in Table 3-9. These features can be activated simultaneously.
When planning and configuring data, note the following:

cells.

Table 3-10 lists the cell-reselection parameter settings generally recommended for UEs in idle mode and UEs in the CELL_PCH or CELL_FACH state.

For U900/U850 cells, configure the following parameters related to the feature Service Steering and Load Sharing in RRC Connection Setup:
Set the TrafficType(BSC6900,BSC6910) parameter to PSHSPA.
Set the RedirSwitch(BSC6910,BSC6900) parameter to ONLY_TO_INTER_FREQUENCY.
Set the RedirFactorOfNorm(BSC6900,BSC6910) parameter based on the quantity of loads that are planned to be shifted from U2100 cells to U900/U850 cells.

For U900/U850 cells, select UL_UU_CLB, DL_UU_CLB, CELL_CODE_CLB, or CELL_CREDIT_CLB under the NBMLdcAlgoSwitch(BSC6900,BSC6910) parameter.
For U2100 cells, set the CLBFlag(BSC6900,BSC6910) and CLBPrio(BSC6900,BSC6910) parameters to appropriate values.
3.2 Main Challenges

The standard bandwidth for a UMTS carrier is 5 MHz. However, the limited spectrum resources cannot meet the growing demands caused by UMTS service expansion. The conflict between resource limitation
and service expansion is especially evident in the 900 MHz and 850 MHz frequency bands. Some telecom operators cannot reserve a standard bandwidth of 5 MHz from the 900 MHz or 850 MHz frequency band.
In this case, UMTS carriers are configured with a non-standard bandwidth (for example, 3.8 MHz or 4.2 MHz). The non-standard frequency spacing is implemented between:
UMTS and UMTS (UU) carriers

The non-standard frequency spacing between UU carriers is less than 5 MHz, as shown in Figure 3-9.
Figure 3-9 Non-standard frequency spacing between UU carriers
GSM and UMTS (GU) carriers

The non-standard frequency spacing between GU carriers is less than 2.6 MHz, as shown in Figure 3-10.
Figure 3-10 Non-standard frequency spacing between GU carriers

In this scenario, the objective of the solution is to ensure that U900/U850 networks can work with a non-standard bandwidth of less than 5 MHz. The typical bandwidth is 3.8 or 4.2 MHz.

In this scenario, UMTS carriers are configured with a bandwidth of 3.8 MHz or 4.2 MHz. This bandwidth is used when a frequency spectrum of 5 MHz is unavailable for UMTS.
WRFD-021001 Flexible frequency bandwidth of This feature flexibly provides a bandwidth within the range of 4.2 to 5 MHz for RAN12.0 GU 900 MHz Non-standard Frequency
UMTS carrier UMTS carriers. Spacing Feature Parameter Description
MRFD-221804 GSM Power Control on Interference The power of the GSM center frequency that is spaced 2.0 MHz away from the SRAN7.0 GU 900 MHz Non-standard Frequency
Frequency for GU Small Frequency UMTS center frequency is lowered, thereby decreasing the downlink interference of Spacing Feature Parameter Description
gap GSM to UMTS.
MRFD-221703 2.0 MHz Central Frequency Point This feature provides the 2 MHz frequency spacing between a GSM carrier and a SRAN6.0 GU 900 MHz Non-standard Frequency
Separation Between GSM and UMTS carrier. Spacing Feature Parameter Description
UMTS Modes
WRFD-030010 CQI Adjustment Based on Dynamic This feature can increase the downlink throughput of HSDPA cells against small RAN13.0 HSDPA Feature Parameter Description
BLER Target bandwidth interference.
Activate all of the features listed in Table 3-11 according to the following instructions.
WRFD-021001 Flexible frequency bandwidth of UMTS carrier

Activate this feature when the UMTS carrier bandwidth is between 4.2 MHz and 5 MHz. You do not have to activate this feature when the UMTS carrier bandwidth is 5 MHz.
MRFD-221703 2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS)
Activate this feature when the UMTS carrier bandwidth is 3.8 MHz.
MRFD-221804 GSM Power Control on Interference Frequency for GU Small Frequency gap
Activate this feature when the UMTS carrier bandwidth is less than 5 MHz.
WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
Activate this feature when the UMTS carrier bandwidth is less than 5 MHz.
Before using the non-standard UMTS bandwidth solution, ensure that the RF modules support the WRFD-021001 Flexible frequency bandwidth of UMTS carrier and MRFD-221703 2.0MHz Central Frequency
point separation between GSM and UMTS mode(UMTS) features. For details, see GU 900 MHz Non-standard Frequency Spacing Feature Parameter Description.
To reduce the impact of non-standard frequency spacing on network KPI values, you are advised to purchase Huawei professional services.

UMTS users are growing while GSM users are shrinking. Operators prefer deploying the 900/850 MHz band to meet service requirements of the increasing UMTS users. Therefore, the U900/U850 network must
support dual-carrier deployment.
Figure 3-11 shows dual-carrier deployment on U900/U850 networks. Due to differences between spectrums available for operators, dual-carrier U900/U850 networking can be deployed with a standard bandwidth
of 5 MHz or a non-standard bandwidth less than 5 MHz.
Figure 3-11 Dual-carrier deployment on U900/U850 networks
click to enlarge

This solution provides dual-carrier deployment on the U900/U850 band. Typical scenarios are as follows:
Reconfiguration from a single-carrier U900/U850 network to a dual-carrier U900/U850 network

Dual-carrier U900/U850 network deployment

This section describes the dual-carrier U900/U850 networking policy and GU900/GU850 spectrum allocation principles.
Difference between the dual-carrier and single-carrier U900/U850 networking policies

For users in idle mode
Intra-RAT reselection policy: Only reselection to the U900/U850 F1 is allowed for users carried over the U900/U850 F2. For the F1 reselection policy, see the reselection policies
specific for various scenarios described in 3.1 Application Scenarios.
Inter-RAT reselection policy: Reselection to the G900 carrier is allowed for users carried over the U900/U850 F1 and F2.
Figure 3-12 Reselection policy for users in idle mode in dual-carrier networking
For users in connected mode

Coverage-based handover: Cell edge users carried over the U900/850 F1 and F2 can all be handed over to the U2100 F1 and the G900 carriers.
Load balancing: LDR based on blind handovers and DRD for load balancing are allowed between the U900/U850 F1 and F2. Measurement-based LDR is allowed only from the U900
F1 to the U2100 F1. The U900 F2 does not support load sharing for the U2100 carriers.
Figure 3-13 Handover and load balancing policies for users in connected mode in dual-carrier networking
click to enlarge
GU900/GU850 spectrum allocation principles
The GU900/GU850 spectrum allocation principles are as follows:

Deploying dual continuous carriers is preferred.
Most UEs support only DC-HSDPA on two continuous carriers. The spacing between the central frequencies of two continuous carriers is not greater than 5 MHz. If scattered spectral resources
are available for an operator, DC-HSDPA is not supported after dual carriers are configured on the U900/U850 network.
Both carriers use the same bandwidth.
Reconfiguration from a single-carrier network to a dual-carrier network: If the UMTS bandwidth needs to be decreased due to spectral resources, the original carrier bandwidth must
also be decreased and throughput of non-DC-HSDPA users decreases.
Deployment of a dual-carrier network: Deploy the carriers based on spectral resources available for operators.
Feature List
This solution applies to the scenarios described in section 2.2. The following table lists the feature involved in this solution.
WRFD-010696 DC-HSDPA This feature allows a UE to establish downlink connections to two RAN12.0 Multi-Carrier HSDPA Feature Parameter Description
adjacent same-coverage cells on the same frequency band. With this
feature, the UE can use the resources in both cells that work on
different carriers, increasing the peak throughput of the UE.
During the implementation, activate the features involved in related scenarios described in 3.1 Application Scenarios and pay attention to the following:
If the spacing between central frequencies of the two U900/U850 carriers is not greater than 5 MHz, activate the WRFD-010696 DC-HSPDA feature.
If the UMTS carrier needs the non-standard bandwidth less than 5 MHz after spectrum planning, activate features involved in 3.2.1 Challenge 1: Non-standard UMTS Bandwidth.
3.2.2.5 Impact Assessment

Impact assessment on the dual-carrier deployment solution is as follows:
If the U900/U850 carriers use the non-standard bandwidth or the single-carrier bandwidth is less than that before the solution deployment, then both the single-carrier throughput and KPIs will be
affected. For details, see GU 900 MHz Non-standard Frequency Spacing Feature Parameter Description.
If DC-HSDPA carriers are configured by this solution, the peak throughput of DC-HSDPA users improves on the U900/U850 network. For details, see Multi-Carrier HSDPA Feature Parameter
Description.
If carriers other than DC-HSDPA carriers are configured by this solution, the UMTS network throughput in busy hours is affected. The counters listed in the following table can be used to assess the
impact.
Counter Name Counter Description
VS.HSDPA.MeanChThroughput(BSC6900,BSC6910) Mean Downlink Throughput of single HSDPA MAC-d Flows for Cell
VS.HSUPA.MeanChThroughput(BSC6900,BSC6910) Mean Uplink Throughput of single HSUPA MAC-d Flow for Cell

Many objects cause external interference to U900/U850 networks. These objects include street lights, walkie-talkies, TV amplifiers, and even electronic billboards. In most cases, the external interference occurs in
the uplink. Figure 3-14 shows external interference on U900/U850 networks from many objects. The external interference negatively affects the coverage and capacity of U900/U850 networks.
Figure 3-14 External interference that affects U900/U850 networks
click to enlarge

If there is external interference, this solution improves user experience and network performance in the following ways:
Identifies uplink narrowband interference

Eliminates uplink strong narrowband interference
Improves coverage against uplink strong interference
Improves system capacity against uplink strong interference
Improves network performance against uplink strong interference

This solution can improve the performance of cells with external interference and reduce the impact of external interference on these cells. This solution thereby reduces the difficulty in deploying U900/U850 cells
against interference.

N/A Auto-Adaptive Background Noise This feature ensures high HSUPA throughput in the cells of sites RAN12.0 Load Measurement Feature Parameter Description
Update that experience strong uplink interference from external sources.
Under optimal conditions, applying this feature can raise the
HSUPA throughput in a cell with strong external interference to
the level of a cell with no interference.
WRFD-020136 Anti-Interference Scheduling for This function updates background noise in real time, thereby RAN13.0 HSUPA Feature Parameter Description
HSUPA improving the uplink throughput of a cell in the event of external
interference.
WRFD-140225 Narrowband Interference Suppression With this feature, the NodeB scans the frequency spectrum RAN15.0 Narrowband Interference Suppression Feature Parameter
within the receive bandwidth of a UMTS carrier to rapidly Description
identify stable narrowband interference (with millisecond-level
changes in frequency or power) and dynamically configures a
filter stopband on the receiver to suppress narrowband
interferences.
N/A Activation of the Inter-Frequency This function prevents UEs from being handed over to the edge RAN15.0 Self Optimization Under Uplink Interference Feature
Handover Algorithm Considering the of the uplink coverage of a cell with external interference, so as Parameter Description
Target RTWP to reduce the number call drops caused by handover failures.
N/A UMTS Uplink Narrowband Narrowband interference detection is performed in the time RAN16.0&GENEX Nastar Nastar professional service
Interference Detection domain and the frequency domain. V600R014C00
Narrowband interference detection in the time domain
can detect the interference signals that increase the
background noise by an average of over 6 dB in a
measurement period.
Narrowband interference detection in the frequency
domain is more precise. It can detect the interface
signals of less than 2 MHz bandwidth, increasing the
instantaneous RTWP value by over 5 dB in a
consecutive period of 15s.
Narrowband interference detection can automatically identify the
cells with interference in batches and output a narrowband
interference spectrum graph for each cell.
WRFD-160250 Interference Rejection Combining This feature mitigates strong interference in a cell that is caused RAN16.0 Interference Rejection Combining Feature Parameter
(IRC) by its neighboring cells or other external sources, thereby Description
improving the cell throughput.
WRFD-171212 Coverage Expansion Under This feature enables cells with strong interference to use the RAN17.1 Coverage Expansion Under Interference Feature
Interference resources of cells with weak or no interference, thereby Parameter Description
combining the links of multiple cells in the uplink. This enhances
the detection performance and improves the uplink coverage of
cells with strong interference.
WRFD-171213 Self Optimization Under Uplink This feature monitors the uplink received total wideband power RAN17.1 Self Optimization Under Uplink Interference Feature
Interference (RTWP) of a cell in real time and identifies scenarios in which Parameter Description
uplink interference occurs. If uplink interference occurs in a cell,
this feature automatically adjusts the settings of related
parameters to avoid imbalance between uplink and downlink
caused by uplink interference and thereby improves network
performance.
WRFD-181219 Adaptive Interference Rejection The Adaptive Interference Rejection (AIR) feature de-correlates RAN18.1 Adaptive Interference Rejection Feature Parameter
non-UMTS interference between antennas to improve the receive Description
(RX) performance, which effectively suppresses the strong
wideband non-UMTS interference and improves the uplink
coverage performance.
In Table 3-12, all features except those described in the following paragraphs can automatically identify application scenarios and can be activated on the entire U900/U850 network.
RF modules must be configured for WRFD-140225 Narrowband Interference Suppression. This feature enables the NodeB to rapidly identify stable narrowband interference that lasts for more than 40
ms, has a bandwidth of less than 400 kHz, and produces noise 7 to 35 dB louder than the background noise of the NodeB. After this feature is activated, a filter stopband is added to a remote radio unit
(RRU). This prolongs the uplink delay and slightly affects uplink demodulation performance. Therefore, it is recommended that this feature be activated only when there is external narrowband
interference.
The prolonged delay may decrease the success rate of softer handovers between cells with this feature enabled and cells without this feature. Therefore, it is recommended that this feature be enabled for
all the cells that use the same frequency and belong to the same NodeB.
For details about how to activate and use UMTS Uplink Narrowband Interference Detection, contact Huawei technical support for professional services.
The features WRFD-171212 Coverage Expansion Under Interference is recommended for cells with interference.
UBBP boards must be configured for WRFD-160250 Interference Rejection Combining (IRC) and WRFD-171212 Coverage Expansion Under Interference.
The WRFD-181219 Adaptive Interference Rejection feature significantly suppresses strong external wideband interference, reduces RTWP, and increases uplink coverage in the presence of interference.
It is recommended that this feature be activated when strong external interference occurs (interference is 12 dB to 30 dB higher than the noise floor) and the interference bandwidth of an uplink
receive carrier is greater than 400 kHz.
The improvements provided by this feature are proportional to external interference strength.
The improvements provided by this feature are also proportional to correlation of interference signals.
Only UBBPd/UBBPe boards support this feature. A UBBPd/UBBPe board working only in UMTS mode must be configured as the interface board, and the uplink resource group serving the cell
using this feature includes only UBBPd/UBBPe boards.

A typical scenario of U900/U850 network deployment is as follows: The coverage area of the U900/U850 network overlaps that of a U2100 network. The U900/U850 network uses a single carrier and the U2100
network uses multiple carriers. In addition, the U2100 network supports DC-HSDPA or 3C/4C-HSDPA. Figure 3-15 shows an example. DC-HSDPA or 3C/4C-HSDPA UEs should perform services on carriers that
support DC-HSDPA or 3C/4C-HSDPA as much as possible. DB-HSDPA UEs should use the DB-HSDPA technology as much as possible. The purpose is to improve user throughput.
Figure 3-15 U900/U850 (a single carrier) + U2100 (dual carrier)

This solution applies to scenarios where the coverage area of a U900/U850 network overlaps that of a U2100 network, so as to improve the downlink throughput of UEs served by the U900/U850 network.

This solution can increase the downlink throughput of UEs served by a U900/U850 network if the coverage area of the U900/U850 network overlaps that of a U2100 network. This solution uses the following
methods:
Migrating DC-HSDPA UEs from U900/U850 carriers to inter-band DC-HSDPA carriers

This method uses technological satisfaction-based directed retry decision (DRD) to migrate DC-HSDPA or 3C/4C-HSDPA UEs to DC-HSDPA or 3C/4C-HSDPA carriers. It also uses the
BlindHOQualityCondition(BSC6900,BSC6910) and DRDTargetUlCoverLimitThd(BSC6900,BSC6910) parameters to reduce the probability that the cell edge UEs (CEUs) of the
U900/U850 network are migrated to the weak coverage area of the U2100 network through DRD.
This method uses terminal capability-based RRC inter-frequency redirection to redirect DC-HSDPA or 3C/4C-HSDPA UEs on the U900/U850 network to the DC-HSDPA or 3C/4C-HSDPA
carriers on the U2100 network.
Making DB-HSDPA UEs on U900/U850 carriers use the DB-HSDPA technology as much as possible
Activate the DB-HSDPA feature.
In addition to DB-HSDPA, activate inter-site DB-HSDPA for more UEs to use DB-HSDPA.

WRFD-020110 Multi Frequency Band Networking This feature allows inter-band DRD and RRC redirection for DC-HSDPA or RAN10.0 Multi-Frequency Band Networking Management
Management 3C/4C-HSDPA UEs. Feature Parameter Description
WRFD-150209 DB-HSDPA Dual-band HSDPA (DB-HSDPA) allows a UE to set up a downlink RAN15.0 Multi-Carrier HSDPA Feature Parameter Description
connection in each of the two co-coverage inter-band cells so that the UE can
use the radio resources of both cells. Therefore, the UE's peak throughput is
increased.
WRFD-180212 Inter-NodeB DB-HSDPA This feature allows a UE to use the cell resources of different NodeBs to RAN18.1 Multi-Carrier HSDPA Feature Parameter Description
perform DB-HSDPA data transmission in the same coverage area of inter-
NodeB inter-band cells.
To implement this solution, the following conditions must be met:
If there are DC-HSDPA or 3C/4C-HSDPA UEs on the live network and the DC-HSDPA or 3C/4C-HSDPA feature is activated, enable DC-HSDPA or 3C/4C-HSDPA carriers to carry DC-HSDPA or
3C/4C-HSDPA UEs as much as possible, by following the method below. Otherwise, this method is not required.
For UEs in connected mode, if U2100 carriers support DC-HSDPA or 3C/4C-HSDPA but U900/U850 carriers cannot be configured to support DC-HSDPA or 3C/4C-HSDPA, DC-HSDPA and 3C/4C-
HSDPA UEs should be migrated to different carriers from SC-HSDPA UEs. The implementation method varies according to the scenario.
In addition to technological satisfaction-based DRD, the anti-DRD failure mechanism is recommended. Table 3-14 provides suggested parameter configurations.
Parameter ID U900/U850 Cell
CellConnAlgoSwitch1(BSC6900,BSC6910):IDLE_DRD_BASED_COVER_SWITCH ON
CellConnAlgoSwitch1(BSC6900,BSC6910):C2D_DRD_BASED_COVER_SWITCH ON
CellConnAlgoSwitch1(BSC6900,BSC6910):CONN_DRD_BASED_COVER_SWITCH ON
BlindHOQualityCondition(BSC6900,BSC6910) -86 (for neighboring U2100 cells of the serving U900/U850 cell)
DRDTargetUlCoverLimitThd(BSC6900,BSC6910) 9 (for neighboring U2100 cells of the serving U900/U850 cell)
Terminal capability-based inter-frequency RRC redirection is recommended. Table 3-15 provides suggested parameter configurations.
Table 3-15 Suggested parameter configurations for terminal-capability-based inter-frequency RRC redirection
Parameter ID U900/U850 Cell
RedirFactorOfLDR(BSC6900,BSC6910) 50
RedirFactorOfNorm(BSC6900,BSC6910) 50
If there are DB-HSDPA UEs on the live network, WRFD-150209 DB-HSDPA and WRFD-180212 Inter-NodeB DB-HSDPA can be activated. Otherwise, do not activate WRFD-150209 DB-HSDPA or
WRFD-180212 Inter-NodeB DB-HSDPA.
4 Features Involved in the Solution
WRFD-010401 System Information Broadcasting RAN2.0 UE Behaviors in Idle Mode Feature Parameter Description
WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL- RAN2.0 URA-Cell Update Feature Parameter Description
WRFD-020110 Multi Frequency Band Networking Management RAN10.0 Multi-Frequency Band Networking Management Feature Parameter Description
WRFD-020401 Inter-RAT Redirection Based on Distance RAN12.0 Intelligent Access Control Feature Parameter Description
WRFD-02040005 Inter-Frequency Redirection Based on Distance RAN14.0 Intelligent Access Control Feature Parameter Description
WRFD-020106 Load Reshuffling RAN2.0 Load Reshuffling Feature Parameter Description
WRFD-020103 Inter Frequency Load Balance RAN2.0 Inter Frequency Load Balance Feature Parameter Description
WRFD-020160 Enhanced Multiband Management RAN12.0 Multi-Frequency Band Networking Management Feature Parameter Description
WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup RAN10.0 Directed Retry Decision Feature Parameter Description
WRFD-020120 Service Steering and Load Sharing in RRC Connection RAN11.0 Intelligent Access Control Feature Parameter Description
Setup
WRFD-160101 System Improvement for RAN16.0 RAN16.0 Redirection at RRC Connection Release Feature Parameter Description
WRFD-140217 Inter-Frequency Load Balancing Based on Configurable RAN14.0 Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature
Load Threshold Parameter Description
N/A Auto-Adaptive Background Noise Update RAN12.0 Load Measurement Feature Parameter Description
WRFD-140225 Narrowband Interference Suppression RAN15.0 Narrowband Interference Suppression Feature Parameter Description
N/A Activation of the Inter-Frequency Handover Algorithm RAN15.0 Self Optimization Under Uplink Interference Feature Parameter Description
Considering the Target RTWP
N/A UMTS Uplink Narrowband Interference Detection GENEX Nastar V600R014C00 Nastar professional service
WRFD-160250 Interference Rejection Combining (IRC) RAN16.0 Interference Rejection Combining Feature Parameter Description
WRFD-171212 Coverage Expansion Under Interference RAN17.1 Coverage Expansion Under Interference Feature Parameter Description
WRFD-171213 Self Optimization Under Uplink Interference RAN17.1 Self Optimization Under Uplink Interference Feature Parameter Description
WRFD-021001 Flexible frequency bandwidth of UMTS carrier RAN12.0 GU 900 MHz Non-standard Frequency Spacing Feature Parameter Description
MRFD-221804 GSM Power Control on Interference Frequency for GU SRAN7.0 GU 900 MHz Non-standard Frequency Spacing Feature Parameter Description
Small Frequency gap
MRFD-221703 2.0 MHz Central Frequency Point Separation Between SRAN6.0 GU 900 MHz Non-standard Frequency Spacing Feature Parameter Description
GSM and UMTS Modes
WRFD-030010 CQI Adjustment Based on Dynamic BLER Target RAN13.0 HSDPA Feature Parameter Description
WRFD-010696 DC-HSDPA RAN12.0 Multi-Carrier HSDPA Feature Parameter Description
WRFD-150209 DB-HSDPA RAN15.0 Multi-Carrier HSDPA Feature Parameter Description
WRFD-180212 Inter-NodeB DB-HSDPA RAN18.1 Multi-Carrier HSDPA Feature Parameter Description

WRFD-181219 Adaptive Interference Rejection RAN18.1 Adaptive Interference Rejection Feature Parameter Description
Blind HO Blind Handover
DRD Directed retry decision
GSM Global system for mobile communications
IFHO Inter-Frequency Handover
KPI Key performance indicator
LDB Load Control Balancing
LDR Load Reshuffling
MSC Mobile switching center
RNC Radio network controller
SGSN Serving GPRS support node
SHO Soft Handover
UE User equipment
NBIS Narrowband Interference Suppression
IRC Interference Rejection Combining
AIR Adaptive Interference Rejection
1. UE Behaviors in Idle Mode Feature Parameter Description

2. URA-Cell Update Feature Parameter Description
4. Multi-Frequency Band Networking Management Feature Parameter Description
5. Load Reshuffling Feature Parameter Description
6. Inter Frequency Load Balance Feature Parameter Description
8. Intelligent Access Control Feature Parameter Description
9. Inter-Frequency Load Balancing Based on Configurable Load Threshold Feature Parameter Description
10. Narrowband Interference Suppression Feature Parameter Description
11. GU 900 MHz Non-standard Frequency Spacing Feature Parameter Description
14. Load Measurement Feature Parameter Description
15. Redirection at RRC Connection Release Feature Parameter Description
16. Interference Rejection Combining Feature Parameter Description
17. Coverage Expansion Under Interference Feature Parameter Description
18. Self Optimization Under Uplink Interference Feature Parameter Description
20. Multi-Carrier HSDPA Feature Parameter Description
21. Adaptive Interference Rejection Feature Parameter Description
1.5 Operation and Maintenance

UMTS SON Solution

WCDMA RAN
UMTS SON Solution Guide

Issue 01
Date 2016-02-29

Notice
1.5.1 Contents
1.1 Scope
1.3 Change History
2 Solution Overview
2.1 Background
2.3.1 Overview
2.3.2 C-SON
2.3.3 D-SON
2.3.4 Application Scenarios
3.1 Scenario 1: Wireless Networking - Single Carrier
3.2 Scenario 2: Wireless Networking - Multiple Carriers
3.3 Scenario 3: Wireless Networking - HetNet
3.4 Scenario 4: Unplanned Heavy Traffic
4 Involved Features
1.1 Scope
1.3 Change History
1.1 Scope
This document describes solutions for different application scenarios in a self-organizing network (SON).

Need to understand SONs

1.3 Change History

RAN18.1 01 (2016-02-29)
RAN18.1 Draft A (2015-12-30)

Added description of the following features:
WRFD-180102 Efficient Improvement of Handover-related KPIs

WRFD-180103 Efficient Improvement of Accessibility KPIs
WRFD-180107 Efficient Improvement of Call Drop-related KPIs in Multi-Sector
2 Solution Overview
2.1 Background

2.1 Background
The UMTS SON solution is used to reduce human involvement during network operation and maintenance (O&M), network operating costs, and operating expense (OPEX) while improving user experience and
network key performance indicators (KPIs).

The UMTS SON solution applies to all the stages of network O&M: network planning, network deployment, network optimization, and network maintenance. This solution aids a network in automatically
adapting to its own changes in order to achieve self-management. It also replaces human involvement during conventional network O&M with automatic system actions, increasing O&M efficiency and reducing
costs.
At present, the SON solution primarily plans radio frequency (RF) parameters for a newly deployed base station or newly added carriers, and optimizes RF parameters and wireless parameters during network
planning and network optimization.
RF parameter planning
RF parameter planning includes neighboring cell and scrambling code (SC) planning.
After base station deployment or carrier addition, neighbor relationships need to be adjusted during base station activation. If an offline tool is used for planning neighbor relationships, neighbor
relationships need to be planned once a base station is deployed or a carrier is added, which is time-consuming. The online planning mechanism, however, automatically plans and configures neighboring
cells and SCs without operators' manual operations, which significantly improves site deployment efficiency, simplifies related operations, and reduces network maintenance OPEX.
RF parameter optimization
RF parameter optimization includes neighboring cell optimization and SC conflict resolution.
Traditional RF parameter optimization requires a large number of human and material resources, and requires personnel to have extensive network optimization experience. As the network scale expands,
it becomes more difficult to perform RF parameter optimization based on experience. Both operators and equipment vendors expect automatic RF parameter optimization for minimizing operators' OPEX
and improving network resource utilization.
Wireless parameter optimization
Wireless parameter optimization includes capacity problem resolution and handover problem resolution.
The modes of user equipment (UE) include idle and connected modes. Corresponding features can optimize the parameters of each mode to improve network performance, increase resource utilization,
and enhance user experience.
The UMTS SON solution is mainly used in the following scenarios:
Various wireless networking scenarios

Unplanned heavy traffic scenarios
Wireless Networking Scenarios

The UMTS SON solution applies to the following wireless networking scenarios:
Single-carrier networking: There is only one UMTS carrier within the specified coverage area of the wireless network.
Multicarrier networking: There are at least two UMTS carriers within the specified coverage area of the wireless network.
HetNet networking: Micro base stations are introduced into 3900 series macro base stations networking to enhance the network capacity in hot spots.
Unplanned Heavy Traffic Scenarios

For the definition of unplanned heavy traffic scenarios, see UMTS Big Events Solution Guide.
Unplanned heavy traffic is often caused by large events of which the operator is unaware. Such events may include natural disasters or large-scale parades, where hardware expansion and parameter adjustment
cannot be performed prior to such events. In such cases, only product solutions can be deployed to prevent severe network congestion and possible network failure.
An unplanned heavy traffic scenario occurs when any of the following conditions are met for at least 30 minutes:
The value of the VS.CellDCHUEs(BSC6900,BSC6910) counter is greater than 55. This counter indicates the number of DCH UEs in a cell.
The downlink non-HSPA power load factor is greater than 80%.
The downlink non-HSPA power load factor can be calculated using the following formula:
Downlink non-HSPA power load factor = 10(VS.MeanTCP.NonHS(BSC6900,BSC6910)/10)/10(MaxTxPower/100)
The value of the VS.RRC.AttConnEstab.Sum(BSC6900,BSC6910) counter is greater than 3600. This counter indicates the number of RRC connection setups in a cell.
The value of the VS.AttCellUpdt(BSC6900,BSC6910) counter indicating the number of cell updates is greater than 5400.
The UMTS SON solution provides optimization methods that improve system stability and capacity in unplanned heavy traffic scenarios.

2.3.1 Overview
Huawei SON solution consists of Centralized SON (C-SON) and Distributed SON (D-SON). Some features involved in the D-SON are implemented on the Strategy Engine for Target Scenario. Figure 2-1
illustrates how SONs are classified.
Figure 2-1 Classification of SONs
click to enlarge
2.3.2 C-SON
C-SON is carried by the operation, administration and maintenance (OAM) system, such as the SONMaster or U2000. C-SON has two variants:
NM-Centralized SON (SON solution where SON algorithms are executed at the Network Management level, such as SONMaster)
EM-Centralized SON (SON solution where SON algorithms are executed at the Element Management level, such as U2000)
Table 2-1 lists the features involved in the C-SON in the UMTS SON solution.
Table 2-1 Features involved in the C-SON in the UMTS SON solution
Feature ID Feature Name Introduced in… RAN Version
SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency SONMaster14.0 RAN15.0
SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency SONMaster14.0 RAN15.0
SNFD-140208 Automatic Neighbor Relation - UMTS to GSM SONMaster14.0 RAN15.0
SNFD-140209 Automatic Neighbor Relation - UMTS to LTE FDD SONMaster14.0 RAN15.0
SNFD-140210 Automatic Neighbor Relation - UMTS to LTE TDD SONMaster14.0 RAN15.0
SNFD-140222 Scrambling Code Self-Optimization - UMTS SONMaster14.0 RAN15.0
SNFD-140211 Mobility Load Balancing - UMTS Inter-Band SONMaster14.0 RAN15.0
SNFD-140212 Mobility Load Balancing - UMTS Idle Mode HetNet SONMaster14.0 RAN15.0
WOFD-171300 Cell Outage Detection and Recovery M2000 V200R011 RAN13.0
SNFD-140215 Mobility Robustness Optimization - UMTS Inter-Frequency SONMaster14.0 RAN15.0
SNFD-150204 Intelligent Network Energy Saving - UMTS SONMaster15.0 RAN16.0
SNFD-151206 Initial Parameter Organizing - UMTS SONMaster15.1 RAN17.1
NOTE:
According to Huawei SingleOSS strategic plan, the name of the wireless operations support system (OSS) product M2000 is renamed U2000 since V200R014. In V200R013 and earlier versions, the M2000 name does not change.
The name change does not affect the product functions, GUIs, installation methods, or external interfaces.
2.3.3 D-SON
D-SON is carried by NEs and is a SON solution where SON algorithms are executed at the RAN level. Table 2-2 lists the features involved in the D-SON in the UMTS SON solution.
Table 2-2 Features involved in the D-SON in the UMTS SON solution
Feature ID Feature Name Introduced in...
WRFD-151201 Adaptive RACH RAN16.0
WRFD-151203 Camping Strategy Switch for Mass Event RAN16.0
WRFD-160214 Load-based Intelligent State Transition RAN16.0
WRFD-160253 Automatic Congestion Handler RAN16.0
WRFD-140104 Enhanced Combined Services RAN14.0 (enhanced in RAN17.1)
WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals RAN17.1
WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization RAN17.1
WRFD-171213 Self Optimization Under Uplink Interference RAN17.1
WRFD-171214 Inter-Band Load Balancing RAN17.1
WRFD-180102 Efficient Improvement of Handover-related KPIs RAN18.1
WRFD-180103 Efficient Improvement of Accessibility KPIs RAN18.1
WRFD-180107 Efficient Improvement of Call Drop-related KPIs in Multi-Sector RAN18.1
2.3.4 Application Scenarios

The UMTS SON solution applies primarily to the following scenarios:
Scenario 1: Wireless networking scenario - single carrier

Scenario 2: Wireless networking - multiple carriers
Scenario 3: Wireless networking - HetNet
Scenario 4: Unplanned heavy traffic
Figure 2-2 illustrates the mapping between application scenarios and SON types.
Figure 2-2 Mapping between application scenarios and SON types
click to enlarge
With the development of UMTS networks, the number of features and parameters increase. The relationships among parameters are complex. For example, traffic volume in networks fluctuates, and, as a
consequence, performance requirements can vary depending on traffic scenarios. To meet diverse performance requirements, parameter values require modification. For example, in congestion scenarios,
parameter values can be modified to relieve congestion. After congestion is relieved, parameter values can be modified to optimize user experience.
To apply optimal parameter values to different scenarios without human involvement and to solve the problem regarding slow modification of parameter values, Huawei proposed Strategy Engine for Target
Scenario.
With Strategy Engine for Target Scenario, scenarios can be automatically identified, and parameters can be set to optimum values for the scenarios to achieve optimum network performance.
For unplanned events, operators cannot adjust parameter settings in advance. To avoid network accidents and improve user experience in unplanned events, operators can define a scenario-based parameter setting
mechanism in Strategy Engine for Target Scenario, which will adapt parameter settings to different scenarios.
The scenario-based parameter setting mechanism implements adaptive parameter settings. That is, parameters are automatically set to the most appropriate values for different scenarios. Figure 2-3 illustrates the
scenario-based parameter setting mechanism in Strategy Engine for Target Scenario.
Figure 2-3 Scenario-based parameter setting mechanism in Strategy Engine for Target Scenario
click to enlarge
Table 2-3 lists D-SON features whose parameter settings are implemented in Strategy Engine for Target Scenario.
Table 2-3 D-SON features whose parameter settings are implemented in the Strategy Engine for Target Scenario
WRFD-160214 Load-based Intelligent State Transition RAN16.0

WRFD-160253 Automatic Congestion Handler RAN16.0
WRFD-140104 Enhanced Combined Services RAN14.0 (enhanced in RAN17.1)
WRFD-171213 Self Optimization Under Uplink Interference RAN17.1
WRFD-180102 Efficient Improvement of Handover-related KPIs RAN18.1
WRFD-180103 Efficient Improvement of Accessibility KPIs RAN18.1

Single-carrier scenarios are those in which there is only one UMTS carrier within the specified coverage area of the wireless network. In single-carrier scenarios, there is only one layer of coverage. All the Radio
Resource Management (RRM), including intra-cell RRM (such as access) and inter-cell RRM (such as handover and load balancing), is implemented at the same horizontal layer.

The purposes of this solution are as follows:
To plan neighboring cells and SCs during network planning

To optimize neighbor relationships and resolve SC conflicts during network optimization
To resolve capacity and congestion problems due to traffic burst
To resolve abnormal network KPIs due to combined services or faulty UEs
In addition, GSM and UMTS neighboring cell configuration or UMTS and LTE neighboring cell configuration must be complete because GSM and UMTS networks, or UMTS and LTE networks are generally
deployed together in single-carrier scenarios.
1. Neighboring cell and SC planning

During capacity expansion and replanning, only neighbor relationship and SC planning is required for newly deployed base stations. In this case, the SNFD-151206 Initial Parameter Organizing - UMTS
feature is used to automatically plan and configure SCs for neighboring cells of the newly deployed base stations, thereby improving base station deployment efficiency.
2. Neighboring cell optimization
The WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization feature resolves the following problems:
Missing intra-frequency neighboring cells in the second order
Redundant intra-frequency neighboring cell
The SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency feature resolves missing configurations, redundancy, or priority adjustment of intra-frequency neighboring cells. Compared
with the WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization feature, the SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency feature matches neighboring cell
names through engineering parameter settings and can detect missing configuration of intra-frequency neighboring cells in the second or a higher order.
Other features resolve the following network problems:
Missing or redundant inter-RAT neighboring cells for UMTS-to-GSM or UMTS-to-LTE handovers
Priority adjustment of inter-RAT neighboring cells for UMTS-to-GSM handovers
These features include the following:

SNFD-140208 Automatic Neighbor Relation - UMTS to GSM
SNFD-140209 Automatic Neighbor Relation - UMTS to LTE FDD
SNFD-140210 Automatic Neighbor Relation - UMTS to LTE TDD
3. SC conflict resolution
The SNFD-140222 Scrambling Code Self-Optimization - UMTS feature resolves call drop or cell update problems caused by SC conflicts.
4. Capacity and congestion problem resolution
The WRFD-151201 Adaptive RACH feature resolves uplink capacity problems due to traffic bursts. For example, a large number of UEs in the same cell initiate random access simultaneously, resulting
in a high received total wideband power (RTWP) in the cell.
Overload problems such as traffic burst and tide traffic in wireless networks are prone to cause access failures and power congestion, and thereby adversely impact network performance and user
experience. The SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based feature resolves these problems.
The WRFD-160214 Load-based Intelligent State Transition and WRFD-160253 Automatic Congestion Handler features resolve network congestion problems due to traffic burst. These features can
increase the uplink and downlink network capacities and relieve network congestion.
5. Abnormal network KPI resolution
The WRFD-140104 Enhanced Combined Services feature resolves the problem whereby the CS service in the CS+PS combined services has a higher call drop rate than a single CS service.
The WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals feature resolves the abnormal service setup success rate and call drop rate due to faulty UEs.
Handover-related KPIs are key indicators of user experience. Currently, several functions are used to improve handover performance. As many switches are involved and operations are complex, users
may forget to turn on some of the switches. The WRFD-180102 Efficient Improvement of Handover-related KPIs feature can efficiently enable the functions to improve handover-related KPIs and
ensure the handover performance of the network.
Accessibility KPIs are key indicators of service access experience. Currently, several functions are used to improve network access performance. As many switches are involved and operations are
complex, users may forget to turn on some of the switches. The WRFD-180103 Efficient Improvement of Accessibility KPIs feature can efficiently enable the functions to improve accessibility KPIs and
ensure the access performance of the network.
In the case of sector splitting, the radio environment becomes more complicated, and the soft handover area and intra-frequency interference increase. The WRFD-180107 Efficient Improvement of Call
Drop-related KPIs in Multi-Sector feature optimizes soft handover parameters of multiple sectors, enhances the downlink power of AMR services, and enables the cell-level call reestablishment function
to reduce co-channel interference and signal fluctuation, thereby reducing the call drop rate.

Features Involved in the Solution
Table 3-1 lists the features involved in the solution for single-carrier scenarios.
Table 3-1 Features involved in the solution for single-carrier scenarios
SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR
Feature Description
SNFD-140208 Automatic Neighbor Relation - UMTS to GSM SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR
Feature Description
SNFD-140209 Automatic Neighbor Relation - UMTS to LTE FDD SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR
Feature Description
SNFD-140210 Automatic Neighbor Relation - UMTS to LTE TDD SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR
Feature Description
SNFD-140222 Scrambling Code Self-Optimization - UMTS SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS SC Self-
Optimization Feature Description
SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS DL
Capacity Optimization RRM Based Feature Description
SNFD-151206 Initial Parameter Organizing - UMTS SONMaster V100R015C10 iManager SONMaster Product Documentation -> Initial Parameter
Organizing Feature Description
WOFD-171300 Cell Outage Detection and Recovery M2000 V200R011 U2000 Product Documentation -> RAN Management -> SON
Management -> CODR Management
WRFD-151201 Adaptive RACH RAN16.0 RAN Feature Documentation -> Adaptive RACH Feature Parameter
Description
WRFD-160214 Load-based Intelligent State Transition RAN16.0 RAN Feature Documentation -> Load-based Intelligent State
Transition Feature Parameter Description
WRFD-160253 Automatic Congestion Handler RAN16.0 RAN Feature Documentation -> Automatic Congestion Handler
WRFD-140104 Enhanced Combined Services RAN14.0 (enhanced in RAN17.1) RAN Feature Documentation -> Enhanced Combined Services
WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals RAN17.1 RAN Feature Documentation -> Terminal Black List Feature
WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization RAN17.1 RAN Feature Documentation -> Automatic Intra-Frequency
Neighbor Relation Optimization Feature Parameter Description
WRFD-180102 Efficient Improvement of Handover-related KPIs RAN18.1 RAN Feature Documentation -> Efficient Improvement of Handover-
related KPIs Feature Parameter Description
WRFD-180103 Efficient Improvement of Accessibility KPIs RAN18.1 RAN Feature Documentation -> Efficient Improvement of
Accessibility KPIs Feature Parameter Description
WRFD-180107 Efficient Improvement of Call Drop-related KPIs in Multi-Sector RAN18.1 RAN Feature Documentation -> Efficient Improvement of Call Drop-
related KPIs in Multi-Sector Feature Parameter Description

Table 3-2 lists the features involved in the solution for single-carrier scenarios.
Table 3-2 Features involved in the solution for single-carrier scenarios
SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency This feature achieves ANR between intra-frequency UMTS cells by automatically detecting and adding
missing neighboring UMTS cells, and deleting redundant neighboring UMTS cells.
It automatically adjusts priority parameters for intra-frequency neighboring UMTS cells so that optimized
neighboring cells can be preferentially selected for handovers.
SNFD-140208 Automatic Neighbor Relation - UMTS to GSM 1. This feature achieves UMTS-to-GSM ANR by automatically detecting and adding missing neighboring
GSM cells of UMTS cells, and deleting redundant neighboring GSM cells of UMTS cells.
2. It automatically adjusts priority parameters for neighboring GSM cells of UMTS cells so that optimized
SNFD-140209 Automatic Neighbor Relation - UMTS to LTE FDD This feature achieves UMTS-to-LTE FDD ANR by automatically detecting and adding missing neighboring
LTE FDD cells of UMTS cells, and deleting redundant neighboring LTE FDD cells of UMTS cells.
SNFD-140210 Automatic Neighbor Relation - UMTS to LTE TDD This feature achieves UMTS-to-LTE TDD ANR by automatically detecting and adding missing neighboring
LTE TDD cells of UMTS cells, and deleting redundant neighboring LTE TDD cells of UMTS cells.
SNFD-140222 Scrambling Code Self-Optimization - UMTS 1. With this feature, SC conflicts in the network are automatically detected based on the mobility of users.
2. In addition, the SC is replaced by the optimal SC selected from the available SC collection to automatically
resolve SC conflicts.
SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based This feature identifies overload cells and their traffic models by collecting and analyzing traffic statistics,
further analyzes the problem in aspects of neighboring cell faults, access parameter configuration, traffic load
imbalance, and traffic burst, and provides optimization advice in the following aspects:
Reporting of neighboring cell fault alarms
Access parameter configuration
Enabling of features related to load balancing and capacity improvement
Optimization of handover parameters and pilot power
By doing this, this feature resolves or relieves overload and traffic burst, and therefore improves network
performance and user experience.
SNFD-151206 Initial Parameter Organizing - UMTS This feature enables the SONMaster to automatically perform initial planning on the intra-frequency or
UMTS-to-LTE and UMTS-to-GSM neighboring cells as well as SCs of UMTS macro NodeBs when sites and
carriers are added.
WOFD-171300 Cell Outage Detection and Recovery This feature allows the U2000 to automatically detect outage cells and compensate for these cells through
RRM parameter adjustment.
WRFD-151201 Adaptive RACH In unplanned heavy traffic scenarios, a large number of UEs in the same cell initiate random access
simultaneously, resulting in a high RTWP in the cell. Based on the uplink power load and the number of
random access ACKs in the cell in a period of time, the RNC dynamically selects the most appropriate cell
random access parameters to reduce the cell's RTWP and increase network capacity.
WRFD-160214 Load-based Intelligent State Transition This feature enables the RNC to automatically select state transition parameters (including the D2F timer and
event 4A threshold) based on the cell load. In this way, if UEs in the high-load cell have no data transmission,
the RNC quickly switches them to the CELL_FACH state in order to increase cell capacity.
WRFD-160253 Automatic Congestion Handler This feature enables the RNC to automatically identify congestion scenarios and activate the corresponding
congestion relief functions. This reduces the customer's O&M workload, relieves network congestion, and
enhances system stability. Enabling this feature can relieve the following in a cell: downlink power congestion,
uplink power congestion, and FACH congestion.
WRFD-140104 Enhanced Combined Services This feature enables the RNC to determine cell congestion status based on downlink load and available codes,
and to automatically adjust the initial rate type and low activity rate threshold parameters of the BE service in
combined services. Therefore, you can flexibly configure the initial rate type and low-activity rate threshold
parameters of the BE service for different cells or for the same cell in different congestion states, thereby
reducing the number of admission failures due to insufficient resources and reducing the CS call drop rate of
combined services.
WRFD-171107 Automatic Detection and Optimization for Abnormal Terminals This feature measures the voice service setup success rate, data service setup success rate, voice service drop
rate, and data service drop rate for terminals with the same TAC on a daily basis. If the measurement results
are lower than specified thresholds, these terminals are considered abnormal. The measurement results of
several days provide a basis for generating a blacklist of terminals that may be abnormal and for putting
forward corresponding suggestions.
WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization This feature can automatically optimize UMTS intra-RAT intra-frequency neighbor relationships without
manual intervention. The automatic optimization includes automatically detecting and adding missing intra-
frequency neighboring cells as well as automatically detecting and deleting redundant intra-frequency
neighboring cells.
WRFD-180102 Efficient Improvement of Handover-related KPIs This feature uses the general improvement methods for handover-related KPIs to improve basic network
performance and reduce network optimization and O&M costs. Handover-related KPIs mainly include the
inter-frequency hard handover success rate and HSDPA serving cell change success rate.
WRFD-180103 Efficient Improvement of Accessibility KPIs This feature enables multiple accessibility KPI improvement methods through one-click deployment, thereby
improving the basic network performance and the accessibility KPI optimization efficiency.
WRFD-180107 Efficient Improvement of Call Drop-related KPIs in Multi-Sector This feature enables multiple call drop-related KPI improvement methods through one-click deployment in
multi-sector scenarios, thereby reducing network O&M difficulties, costs, and OPEX, and improving the call
drop-related KPIs.
In multi-sector cells with weak coverage or significant signal fluctuation, enabling this feature decreases the
call drop rate. If the coverage is weak when no call establishment function is enabled, this feature provides
significant benefits.
When the UMTS SON solution is used in single-carrier scenarios, all the features in Table 3-1 can be enabled.
Suggestions
If there is no GSM network, it is not necessary to enable the SNFD-140208 Automatic Neighbor Relation - UMTS to GSM feature.
If there is no LTE FDD network, it is not necessary to enable the SNFD-140209 Automatic Neighbor Relation - UMTS to LTE FDD feature.
If there is no LTE TDD network, it is not necessary to enable the SNFD-140210 Automatic Neighbor Relation - UMTS to LTE TDD feature.
Feature Relationships
It is recommended that the following features be used together to implement automatic planning and optimization of neighboring cells and SCs:
SNFD-151206 Initial Parameter Organizing - UMTS

WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization
SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency
SNFD-140222 Scrambling Code Self-Optimization - UMTS
The WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization and SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency features can be used together. The SNFD-140205
Automatic Neighbor Relation - UMTS Intra-Frequency feature matches neighboring cell names through engineering parameter settings and can detect missing configurations of intra-frequency neighboring cells in
the second or a higher order.

Multicarrier scenarios are those in which there are multiple carriers working in the same band or in different bands within the specified coverage area of the wireless network. In these scenarios, it is important to
consider not only the configuration and mobility strategies of the horizontal layer (intra-frequency) for a single carrier, but also the configuration and mobility strategies of the vertical layer (inter-frequency or
inter-band) between different carriers.

Multicarrier networking is complex. In addition to neighboring cell optimization and SC conflict resolution during network optimization, it is also important to consider the following in multicarrier scenarios:
Resolution of capacity and congestion problems due to traffic burst (including optimization of load imbalance between carriers at different layers)
Automatic optimization of mobility parameters (camping, reselection, and handover)
Resolution of abnormal network KPIs due to combined services or faulty UEs
1. Neighboring cell and SC planning

During capacity expansion and replanning, only neighbor relationship and SC planning is required for newly deployed base stations. In this case, the SNFD-151206 Initial Parameter Organizing - UMTS
feature is used to automatically plan and configure SCs for neighboring cells of the newly deployed base stations, thereby improving base station deployment efficiency.
The WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization feature resolves the following network problems:
Missing configuration of intra-frequency neighboring cells in the second order
Redundancy of intra-frequency neighboring cell
The SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency feature resolves missing configurations, redundancy, or priority adjustment of intra-frequency neighboring cells.
The SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency feature resolves missing configuration, redundancy, or priority adjustment of inter-frequency neighboring cells.
Some other features resolve the following network problems:
Missing configuration or redundancy of inter-RAT neighboring cells for UMTS-to-GSM or UMTS-to-LTE handovers
A load imbalance problem may occur between the UMTS 2100 MHz and UMTS 900 MHz networks. For example, the load on the UMTS 900 MHz network is too high and the load on the UMTS 2100
MHz network is too low, or vice versa. To balance downlink TCP load between high and low frequency bands, the SNFD-140211 Mobility Load Balancing - UMTS Inter-Band feature is used.
A load imbalance problem may occur between the UMTS 2100 MHz and UMTS 900 MHz networks. To improve user experience and system capacity in scenarios where load imbalance occurs between
high and low frequency bands, the WRFD-171214 Inter-Band Load Balancing feature is used. This feature provides low frequency bands' coverage gains during off-peak hours while ensuring capacity
sharing, and attempts to avoid cells working in low frequency bands from being in a heavy load state during peak hours.
in a high RTWP in the cell.
Overload problems such as traffic burst and tide traffic in wireless networks are prone to cause access failures and power congestion, and thereby adversely impact network performance and user
experience. The SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based feature resolves these problems.
increase the uplink and downlink network capacities and relieve network congestion. For multicarrier networks using the "Preferred Camping" strategy, the WRFD-151203 Camping Strategy Switch for
Mass Event feature is used to change the strategy to "Random Camping." This can balance the load between cells, relieve the congestion on some carriers, and increase the access success rate.
The UMTS 900 MHz or UMTS 850 MHz system is vulnerable to interference from GSM and CDMA systems as well as repeaters. As a result, the cell RTWP significantly rises and the UMTS 900 MHz
or UMTS 850 MHz cell performance deteriorates. The WRFD-171213 Self Optimization Under Uplink Interference feature resolves this problem.
5. Handover problem resolution
If inter-frequency handover parameters are inappropriately set, inter-frequency handovers may occur too early or too late, which will result in radio link failures. If the radio environment changes slowly
(for example, most users are walking), the handover parameters should be less sensitive to changes. If the radio environment changes quickly (for example, most users are driving), the handover
parameters should be more sensitive to changes. The SNFD-140215 Mobility Robustness Optimization - UMTS Inter-Frequency feature resolves this problem.
The WRFD-140104 Enhanced Combined Services feature resolves the problem whereby the CS service in the CS+PS combined services has a higher call drop rate than a single CS service.
7. Energy saving
In multicarrier networks, UE inactivity in certain periods of time (such as nights and holidays in commercial areas, nights in residential areas, periods of having no sporting events in stadiums) causes
light cell load, the light cell load periodically occurs, and operators require energy be saved and emission be reduced in single-band multicarrier networks. In this case, the SNFD-150204 Intelligent
Network Energy Saving - UMTS feature is used.

Table 3-3 lists the features involved in the solution for multicarrier scenarios.
Table 3-3 Features involved in the solution for multicarrier scenarios
Feature Description
SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR
Feature Description
Feature Description
Feature Description
Feature Description
SNFD-140211 Mobility Load Balancing - UMTS Inter-Band SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS MLB
Feature Description
SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS DL
Capacity Optimization RRM Based Feature Description
SNFD-150204 Intelligent Network Energy Saving - UMTS SONMaster15.0 iManager SONMaster Product Documentation -> Intelligent
Network Energy Saving Feature Description
SNFD-151206 Initial Parameter Organizing - UMTS SONMaster V100R015C10 iManager SONMaster Product Documentation -> Initial Parameter
Organizing Feature Description
WOFD-171300 Cell Outage Detection and Recovery M2000 V200R011 U2000 Product Documentation -> RAN Management -> SON
Management -> CODR Management
SNFD-140215 Mobility Robustness Optimization - UMTS Inter-Frequency SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS MRO
Feature Description
Description
WRFD-151203 Camping Strategy Switch for Mass Event RAN16.0 RAN Feature Documentation -> Camping Strategy Switch for Mass
Event Feature Parameter Description
WRFD-171213 Self Optimization Under Uplink Interference RAN17.1 RAN Feature Documentation -> Self Optimization Under Uplink
Interference Feature Parameter Description
WRFD-171214 Inter-Band Load Balancing RAN17.1 RAN Feature Documentation -> Inter-Band Load Balancing Feature

Table 3-4 lists the features involved in the solution for multicarrier scenarios.
Table 3-4 Features involved in the solution for multicarrier scenarios
SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency The SONMaster can automatically optimize UMTS intra-RAT intra-frequency neighbor relationships.
1. This feature achieves ANR between intra-frequency UMTS cells by automatically detecting and adding
missing neighboring UMTS cells, and deleting redundant neighboring UMTS cells.
2. It automatically adjusts priority parameters for intra-frequency neighboring UMTS cells so that optimized
SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency The SONMaster can automatically optimize UMTS intra-RAT intra-frequency neighbor relationships.
1. This feature achieves ANR between inter-frequency UMTS cells by automatically detecting and adding
missing inter-frequency neighboring UMTS cells, and deleting redundant inter-frequency neighboring UMTS
cells.
2. It automatically adjusts priority parameters for inter-frequency neighboring UMTS cells so that optimized
SNFD-140208 Automatic Neighbor Relation - UMTS to GSM The SONMaster can automatically optimize UMTS-to-GSM neighbor relationships.
1. This feature achieves UMTS-to-GSM ANR by automatically detecting and adding missing neighboring
GSM cells of UMTS cells, and deleting redundant neighboring GSM cells of UMTS cells.
2. It automatically adjusts priority parameters for neighboring GSM cells of UMTS cells so that optimized
SNFD-140222 Scrambling Code Self-Optimization - UMTS 1. With this feature, SC conflicts in the network are automatically detected based on the mobility of users.
2. In addition, the SC is replaced by the optimal SC selected from the available SC collection to automatically
resolve SC conflicts.
SNFD-140211 Mobility Load Balancing - UMTS Inter-Band This feature detects areas with load imbalance issues between cells in different frequency bands based on long-
period statistics, and automatically generates parameter optimization suggestions. This achieves load balancing
between cells in different frequency bands in these areas.
WOFD-171300 Cell Outage Detection and Recovery This feature allows the U2000 to automatically detect outage cells and compensate for these cells through
RRM parameter adjustment.
SNFD-140215 Mobility Robustness Optimization - UMTS Inter-Frequency This feature automatically identifies cells where an inter-frequency handover occurs too early or too late, and
automatically optimizes inter-frequency handover parameters to find the proper handover time for most UEs.
SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based This feature identifies overload cells and their traffic models by collecting and analyzing traffic statistics,
further analyzes the problem in aspects of neighboring cell faults, access parameter configuration, traffic load
imbalance, and traffic burst, and provides optimization advice in the following aspects:
Reporting of neighboring cell fault alarms
Access parameter configuration
Enabling of features related to load balancing and capacity improvement
Optimization of handover parameters and pilot power
By doing this, this feature resolves or relieves overload and traffic burst, and therefore improves network
performance and user experience.
SNFD-150204 Intelligent Network Energy Saving - UMTS Based on engineering parameters, performance data, and configuration data, the SONMaster analyzes network
KPIs, generates energy saving optimization advice for optimization areas periodically, and generates and
delivers configuration data to facilitate the enabling of certain green base station features, thereby gaining
energy saving benefits.
SNFD-151206 Initial Parameter Organizing - UMTS This feature enables the SONMaster to automatically perform initial planning on the intra-frequency, inter-
frequency, or UMTS-to-LTE and UMTS-to-GSM neighboring cells as well as SCs of UMTS macro NodeBs
when sites and carriers are added.
WRFD-151203 Camping Strategy Switch for Mass Event This feature periodically measures the number of RRC connection setup requests and the ratio of rejected RRC
connection setup requests due to uplink and downlink power and code resource congestion to the total RRC
connection setup requests in preferentially camped cells.
If the conditions for determining unplanned heavy traffic are met, this feature automatically changes the
network camping strategy to "Random Camping" so that the load is more balanced between cells. In addition,
this feature supports automatically resuming the original preferential camping parameters the next morning
after parameter adjustment.
This feature requires that the original multicarrier network use the "Preferred Camping" strategy.
combined services.
neighboring cells.
WRFD-171213 Self Optimization Under Uplink Interference This feature monitors the uplink RTWP of a cell in real time and identifies scenarios in which uplink
interference occurs. If uplink interference occurs in a cell, this feature automatically activates related function
algorithms or reconfigures related parameters on a live network to improve system capacity and network
performance for the cell. The automatic parameter reconfiguration includes adaptively adjusting the cell
camping threshold parameters, enabling the inter-frequency handover algorithm considering the target RTWP,
adaptively controlling algorithm switches and parameters for automatic update of background noise, and
adaptively reconfiguring compressed mode parameters.
WRFD-171214 Inter-Band Load Balancing This feature periodically monitors the average downlink load of high- and low-band cells. By adjusting
parameters for high- and low-band cells that have load differences, this feature enables UEs to travel to low-
load cells through preferred camping, redirection, and directed retry decision (DRD). This implements
downlink load balancing between high- and low-band cells. This feature provides low frequency bands'
coverage gains during off-peak hours while ensuring capacity sharing, and attempts to avoid cells working in
low frequency bands from being in the heavy load state during peak hours. Therefore, this feature improves
user experience and system capacity in scenarios where load imbalance occurs between high and low
frequency bands.
drop-related KPIs.
When the UMTS SON solution is used in multicarrier scenarios, all the features in Table 3-1 can be enabled.
Suggestions
If there is no inter-band macro base station on the network, it is not necessary to enable the SNFD-140211 Mobility Load Balancing - UMTS Inter-Band or WRFD-171214 Inter-Band Load Balancing
feature.
The WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization and SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency features can be used together. The SNFD-
140205 Automatic Neighbor Relation - UMTS Intra-Frequency feature matches neighboring cell names through engineering parameter settings and can detect missing configurations of intra-frequency
neighboring cells in the second or a higher order.
The SNFD-140211 Mobility Load Balancing - UMTS Inter-Band and WRFD-171214 Inter-Band Load Balancing features cannot be used together because of different application scenarios and different
purposes.
The SNFD-140211 Mobility Load Balancing - UMTS Inter-Band feature is used to adjust the following:
Path loss threshold during user location-based multiband DRD
Load ratio factor during load balancing-based DRD
Reselection-related parameters
Therefore, it is recommended that the SNFD-140211 Mobility Load Balancing - UMTS Inter-Band feature be used together with the following DRD-related features:
WRFD-01061112 HSDPA DRD
WRFD-150232 Multiband Direct Retry Based on UE Location
WRFD-02040001 Intra System Direct Retry
In cells that are not served by the same site but cover the same area, if user location-based multiband DRD and load balancing-based DRD are not enabled, the SNFD-140211 Mobility Load Balancing -
UMTS Inter-Band feature can be used to directly adjust cell reselection parameters.
The SNFD-140211 Mobility Load Balancing - UMTS Inter-Band feature is used to adjust the following:
RAB service steering and load sharing parameters
Parameters for cell reselection in idle mode
Parameters for inter-frequency load balancing based on the configurable load threshold
RRC service steering and load sharing parameters
Parameters for service steering and load sharing in the CELL_FACH state
Therefore, it is recommended that the SNFD-140211 Mobility Load Balancing - UMTS Inter-Band feature be used together with the following RAN features:
WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup
WRFD-150246 Service Steering and Load Sharing in CELL_FACH State
WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load Threshold
The SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based feature may adjust the pilot power of a cell. The pilot power adjustment of a cell will change the basic network structure. In
automatic optimization scenarios, to ensure that other automatic parameter optimization processes that are based on the basic network architecture can be performed concurrently, it is recommended that
this feature be enabled with the following features:
WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization
SNFD-140215 Mobility Robustness Optimization - UMTS Inter-Frequency
The optimization function provided by the SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based feature depends on the following features:
WRFD-010683 Downlink 64QAM
WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
WRFD-010610 HSDPA Introduction Package
WRFD-010685 Downlink Enhanced L2
WRFD-020103 Inter Frequency Load Balance
If the preceding features are not enabled, the SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based feature can still take effect to provide methods of optimizing power or handover
parameter settings and provide recommended values of these parameters.

HetNet scenarios are those in which 3900 series macro base stations, micro base stations, and DBS3900 LampSite base stations are deployed together in a specific coverage area.
In addition to neighboring cell optimization, SC conflict resolution, and load imbalance resolution between macro and micro base stations during network optimization, it is also important to consider the resolution
of capacity and congestion problems due to traffic burst in HetNet scenarios. Furthermore, it is important to focus on the interaction between macro and micro base stations so that the introduction of micro base
stations into the network does not affect the original network KPIs while expanding network capacity and improving user experience.

The WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization feature resolves the following network problems:
Missing configuration of intra-frequency neighboring cells in the second order
Redundancy of intra-frequency neighboring cell
The SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency feature resolves missing configuration, redundancy, or priority adjustment of intra-frequency neighboring cells.
The SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency feature resolves missing configuration, redundancy, or priority adjustment of inter-frequency neighboring cells.
Some other features resolve the following network problems:
Missing or redundant inter-RAT neighboring cells for UMTS-to-GSM or UMTS-to-LTE handovers

The SNFD-140212 Mobility Load Balancing - UMTS Idle Mode HetNet feature resolves the load imbalance problems between macro and micro base stations. The possible load imbalance problems are
as follows:
The load on the micro base station that is used for offloading traffic in hot spots is too high, which affects user experience.
The load on the micro base station that is used for offloading traffic in hot spots is too low, which does not produce the expected traffic offloading results.
in a high RTWP in the cell.
increase the uplink and downlink network capacities and relieve network congestion.
The CS service in CS+PS combined services has a higher probability of experiencing a call drop than a single CS service. The WRFD-140104 Enhanced Combined Services feature resolves this
problem.

Table 3-5 lists the features involved in the solution for HetNet scenarios.
Table 3-5 Features involved in the solution for HetNet scenarios
Feature Description
SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR
Feature Description
Feature Description
Feature Description
Feature Description
SNFD-140212 Mobility Load Balancing - UMTS Idle Mode HetNet SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS MLB
Feature Description
Description

Table 3-6 lists the features involved in the solution for HetNet scenarios.
Table 3-6 Features involved in the solution for HetNet scenarios

SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency The SONMaster can automatically optimize UMTS intra-RAT intra-frequency neighbor relationships.
This feature achieves ANR between intra-frequency UMTS cells by automatically detecting and
adding missing neighboring UMTS cells, and deleting redundant neighboring UMTS cells.
It automatically adjusts priority parameters for intra-frequency neighboring UMTS cells so that
optimized neighboring cells can be preferentially selected for handovers.
SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency The SONMaster can automatically optimize UMTS intra-RAT intra-frequency neighbor relationships.
This feature achieves ANR between inter-frequency UMTS cells by automatically detecting and
adding missing inter-frequency neighboring UMTS cells, and deleting redundant inter-frequency
neighboring UMTS cells.
It automatically adjusts priority parameters for inter-frequency neighboring UMTS cells so that
SNFD-140208 Automatic Neighbor Relation - UMTS to GSM The SONMaster can automatically optimize UMTS-to-GSM neighbor relationships.
This feature achieves UMTS-to-GSM ANR by automatically detecting and adding missing
neighboring GSM cells of UMTS cells, and deleting redundant neighboring GSM cells of UMTS
cells.
It automatically adjusts priority parameters for neighboring GSM cells of UMTS cells so that
SNFD-140222 Scrambling Code Self-Optimization - UMTS With this feature, SC conflicts in the network are automatically detected based on the mobility of
users.
In addition, the SC is replaced by the optimal SC selected from the available SC collection to
automatically resolve SC conflicts.
SNFD-140212 Mobility Load Balancing - UMTS Idle Mode HetNet This feature automatically generates optimization suggestions about mobility load balancing (MLB) for UEs in
idle mode between UMTS macro and micro cells based on historical traffic statistics. This feature also
automatically optimizes parameters related to camping on UMTS networks by adjusting parameters by step.
This feature balances load between macro and micro cells by adjusting parameters for UEs in idle mode in
these cells. This improves radio resource utilization and user experience.
combined services.
neighboring cells.
drop-related KPIs.
WRFD-190203 Automatic Inter-Frequency Neighbor Relation Optimization This feature can automatically optimize UMTS intra-RAT inter-frequency neighbor relationships without
manual intervention. Optimization includes automatically detecting and adding missing inter-frequency
neighboring cells as well as automatically detecting and deleting redundant intra-frequency neighboring cells.
When the UMTS SON solution is used in HetNet scenarios, all the features in Table 3-3 can be enabled.
Suggestions
If there is no inter-band macro base station on the network, it is not necessary to enable the SNFD-140211 Mobility Load Balancing - UMTS Inter-Band feature.
The WRFD-171108 Automatic Intra-Frequency Neighbor Relation Optimization and SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency features can be used together. The SNFD-140205
Automatic Neighbor Relation - UMTS Intra-Frequency feature matches neighboring cell names through engineering parameter settings and can detect missing configurations of intra-frequency neighboring cells in
the second or a higher order.
It is recommended that the following features be used together in scenarios where some cells cannot be configured as neighboring cells due to SC conflicts:


For details, see UMTS Big Events Solution Guide.
4 Involved Features
SNFD-140205 Automatic Neighbor Relation - UMTS Intra-Frequency SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR Feature Description
SNFD-140206 Automatic Neighbor Relation - UMTS Inter-Frequency SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR Feature Description
SNFD-140208 Automatic Neighbor Relation - UMTS to GSM SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR Feature Description
SNFD-140209 Automatic Neighbor Relation - UMTS to LTE FDD SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR Feature Description
SNFD-140210 Automatic Neighbor Relation - UMTS to LTE TDD SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS ANR Feature Description
SNFD-140222 Scrambling Code Self-Optimization - UMTS SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS SC Self-Optimization Feature
Description
SNFD-140211 Mobility Load Balancing - UMTS Inter-Band SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS MLB Feature Description
SNFD-140212 Mobility Load Balancing - UMTS Idle Mode HetNet SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS MLB Feature Description
WOFD-171300 Cell Outage Detection and Recovery M2000 V200R011 U2000 Product Documentation -> RAN Management -> SON Management -> CODR
Management
SNFD-140215 Mobility Robustness Optimization - UMTS Inter- SONMaster V100R014 iManager SONMaster Product Documentation -> UMTS MRO Feature Description
Frequency
SNFD-140219 CCO - UMTS DL Capacity Optimization RRM Based SONMaster V100R014 iManager SONMaster Product Documentation -> CCO - UMTS DL Capacity Optimization
RRM Based Feature Description
SNFD-150204 Intelligent Network Energy Saving - UMTS SONMaster15.0 iManager SONMaster Product Documentation -> Intelligent Network Energy Saving
Feature Description
SNFD-151206 Initial Parameter Organizing - UMTS SONMaster15.1 iManager SONMaster Product Documentation -> Initial Parameter Organizing Feature
Description
WRFD-151201 Adaptive RACH RAN16.0 RAN Feature Documentation -> Adaptive RACH Feature Parameter Description
WRFD-160214 Load-based Intelligent State Transition RAN16.0 RAN Feature Documentation -> Load-based Intelligent State Transition Feature
WRFD-160253 Automatic Congestion Handler RAN16.0 RAN Feature Documentation -> Automatic Congestion Handler Feature Parameter
Description
WRFD-151203 Camping Strategy Switch for Mass Event RAN16.0 RAN Feature Documentation -> Camping Strategy Switch for Mass Event Feature
WRFD-140104 Enhanced Combined Services RAN14.0 (enhanced in RAN Feature Documentation -> Enhanced Combined Services Feature Parameter
RAN17.1) Description
WRFD-171107 Automatic Detection and Optimization for Abnormal RAN17.1 RAN Feature Documentation -> Terminal Black List Feature Parameter Description
Terminals
WRFD-171108 Automatic Intra-Frequency Neighbor Relation RAN17.1 RAN Feature Documentation -> Automatic Intra-Frequency Neighbor Relation
Optimization Optimization Feature Parameter Description
WRFD-171213 Self Optimization Under Uplink Interference RAN17.1 RAN Feature Documentation -> Self Optimization Under Uplink Interference Feature
WRFD-171214 Inter-Band Load Balancing RAN17.1 RAN Feature Documentation -> Inter-Band Load Balancing Feature Parameter
Description
WRFD-180102 Efficient Improvement of Handover-related KPIs RAN18.1 RAN Feature Documentation -> Efficient Improvement of Handover-related KPIs Feature
WRFD-180103 Efficient Improvement of Accessibility KPIs RAN18.1 RAN Feature Documentation -> Efficient Improvement of Accessibility KPIs Feature
WRFD-180107 Efficient Improvement of Call Drop-related KPIs in RAN18.1 RAN Feature Documentation -> Efficient Improvement of Call Drop-related KPIs in Multi-
Multi-Sector Sector Feature Parameter Description
ACH Automatically Congestion Handler
ANR Automatic Neighbor Relationship
C-SON Centralized SON
DRD Directed Retry Decision
D-SON Distributed SON
GSM Global System for Mobile Communications
LTE Long Term Evolution
MLB Mobility Load Balancing
MRO Mobility Robustness Optimization
OPEX OPerating EXpense
PSC Primary scrambling code
RACH Random Access CHannel
RAN Radio Access Network
RF Radio Frequency
RLF Radio Link Failure
RNC Radio Network Controller
RRM Radio Resource Management

SON Self Organization Network
UE User Equipment
WCDMA Wideband Code Division Multiple Access
1. Adaptive RACH Feature Parameter Description

2. Camping Strategy Switch for Mass Event Feature Parameter Description
3. Automatic Congestion Handler Feature Parameter Description
4. Load-based Intelligent State Transition Feature Parameter Description
5. RAN KPI Reference
6. iManager SONMaster Product Documentation -> UMTS ANR Feature Description
7. iManager SONMaster Product Documentation -> UMTS SC Self-Optimization Feature Description
8. iManager SONMaster Product Documentation -> UMTS MLB Feature Description
9. iManager SONMaster Product Documentation -> UMTS MRO Feature Description
10. U2000 Product Documentation -> RAN Management
11. iManager SONMaster Product Documentation -> CCO - UMTS DL Capacity Optimization RRM Based Feature Description
12. iManager SONMaster Product Documentation -> Intelligent Network Energy Saving Feature Description
13. iManager SONMaster Product Documentation -> Initial Parameter Organizing Feature Description
15. Terminal Black List Feature Parameter Description
16. Automatic Intra-Frequency Neighbor Relation Optimization Feature Parameter Description
17. Self Optimization Under Uplink Interference Feature Parameter Description
19. Efficient Improvement of Handover-related KPIs Feature Parameter Description
20. Efficient Improvement of Accessibility KPIs Feature Parameter Description
21. Efficient Improvement of Call Drop-related KPIs in Multi-Sector Feature Parameter Description
1.6 Network Evaluation and Planning

UMTS MBB Visibility Solution
WCDMA RAN
UMTS MBB Visibility Solution Guide
Issue 02
Date 2016-06-23

Notice
1.6.1 Contents
1.1 Overview
1.3 Change History
2 Solution Overview
2.1 Background
3.1 Overview
3.2 Scenario 1: RAN Capacity Visibility
3.3 Scenario 2: RAN KPI Insight
3.4 Scenario 3: Management of Customized Counters
3.5 Scenario 4: xMbps Anytime Anywhere Visibility
3.6 Scenario 5: MBB Subscriber Migration Visibility
3.7 Scenario 6: Coverage Visibility
3.8 Scenario 7: Traffic Volume Visibility
1.1 Overview
1.3 Change History
1.1 Overview
This document describes the UMTS MBB visibility solution for different application scenarios.

Need to understand the MBB visibility solution

1.3 Change History

This section provides the changes in different versions of this document.
RAN18.1 02 (2016-06-23)
This is the forth commercial release of RAN18.1.
Optimized the grid-level coverage visibility solution. For details, see 3.7 Scenario 6: Coverage Visibility.
Revised descriptions in this document.
RAN18.1 01 (2016-02-29)
RAN18.1 Draft B (2016-02-03)

This is the second commercial release of RAN18.1.
Compared with Draft A (2015-12-30) of RAN18.1, Draft B (2016-02-03) of RAN18.1 optimized the description in 3.7 Scenario 6: Coverage Visibility and 3.8 Scenario 7: Traffic Volume Visibility.
RAN18.1 Draft A (2015-12-30)

Compared with Issue 01 (2015-04-20) of RAN17.1, Draft A (2015-12-30) of RAN18.1 adds the traffic volume visibility solution. For details, see 3.8 Scenario 7: Traffic Volume Visibility.
2 Solution Overview
2.1 Background
2.1 Background
With the prevalence of smartphones and a sharp increase in PS signaling and traffic, the MBB network bears an increasingly heavy traffic load and its architecture becomes more and more complex and difficult to
maintain while terminal users are pursuing better service quality and experience. To meet the challenge, telecom operators must learn about whether the network capacity needs to be expanded and whether the
KPIs, coverage, and quality of experience (QoE) counters are normal.
The conventional methods of obtaining QoE counters require manual operations, which is inefficient and costly. Some QoE counters cannot even be collected using the conventional method. Therefore, telecom
operators are eager for an efficient and comprehensive solution. To meet this requirement, Huawei provides a UMTS MBB visibility solution.
The UMTS MBB visibility solution provides the following benefits:
Decreasing the OPEX of network maintenance for telecom operators

Providing a method of evaluating and presenting MBB service quality
Providing data base for accurate network planning and evolution

The MBB visibility solution is a "health check form" for UMTS networks. Based on the iManager Performance Surveillance (PRS) developed by Huawei, the MBB visibility solution enables network capacity and
KPIs to be visible. This helps telecom operators analyze network capacity bottlenecks and network performance problems. In addition, this solution helps to implement accurate network expansion and intelligent
optimization by analyzing traffic distribution and user behavior distribution at the grid level.
MBB Visibility Solution

Figure 2-1 shows how the MBB visibility solution is implemented.
Figure 2-1 Architecture of the MBB visibility solution
Based on NE configuration data, performance data, and license files collected by the U2000, the statistical performance visibility function supports capacity visibility, KPI insight, management of customized
counters, xMbps visibility (cell-level), and fallback analysis (cell-level).
The statistical performance visibility function supports EBC-based management of customized counters by using the TS to collect the EBC counters of NEs.
MBB RAN service visibility supports the following based on the CHR/MR data collected by the TS:
xMbps visibility (grid-level)

Coverage visibility (grid-level)
Traffic volume visibility (grid-level)
Fallback analysis (grid-level)

Figure 2-2 shows the scenarios supported by the MBB visibility solution.
Figure 2-2 Scenarios supported by the MBB visibility solution
click to enlarge
Figure 2-3 shows the mapping between scenarios supported by the MBB visibility solution and RAN versions.
Figure 2-3 Roadmap for the MBB visibility solution
click to enlarge
The features involved in the MBB visibility solution do not affect each other. It is recommended that these features be used together.
Table 2-1 lists the features supported by the MBB visibility solution.
Table 2-1 Functions supported by the MBB visibility solution
MBB Visibility Scenario Related Feature
Management of customized counters WOFD-097700 PRS Basic Service
WOFD-090300 Custom Report System
WOFD-093400 GIS Support
WOFD-192300 Event-based Counter
WOFD-100220 Performance File Interface
Real-time KPI monitoring WOFD-097700 PRS Basic Service
WOFD-093011 UMTS RAN Real-time KPI Monitoring
Capacity visibility WOFD-097700 PRS Basic Service
WOFD-093900 UMTS RAN Capacity Visibility
KPI insight WOFD-097700 PRS Basic Service
WOFD-092900 UMTS RAN KPI Insight
xMbps anytime anywhere visibility (grid-level) WOFD-097700 PRS Basic Service
WOFD-094620 UMTS xMbps Visibility - Grid Level
WOFD-093903 UMTS MBB Grid-level Basic Package
MBB subscriber migration visibility (cell-level) WOFD-097700 PRS Basic Service
WOFD-094500 User Fallback (GSM-UMTS) – Cell Level

MBB Visibility Scenario Related Feature
MBB subscriber migration visibility (grid-level) WOFD-097700 PRS Basic Service
WOFD-094512 UMTS User Migration – Fallback Analysis – Grid level
Indoor MBB (grid-level) WOFD-097700 PRS Basic Service
WOFD-094620 UMTS xMbps Visibility - Grid Level
3.1 Overview
3.1 Overview
Solution Function Scenario
KPI KP report 3.4 Scenario 3: Management of Customized Counters
KPI insight 3.3 Scenario 2: RAN KPI Insight
Infrastructure network construction Capacity visibility 3.2 Scenario 1: RAN Capacity Visibility
Coverage visibility 3.7 Scenario 6: Coverage Visibility
Traffic volume visibility 3.8 Scenario 7: Traffic Volume Visibility
Experience-based network construction xMbps anytime anywhere visibility 3.5 Scenario 4: xMbps Anytime Anywhere Visibility
GU user fallback 3.6 Scenario 5: MBB Subscriber Migration Visibility
Indoor MBB 3.7 Scenario 6: Coverage Visibility

The capacity visibility solution is applicable for all networks that require capacity visibility. It can quickly display network risks when one of the following scenarios exists:
The network capacity is insufficient and may be overloaded.

The number of subscribers grows fast and the traffic model changes frequently, which causes the risk of network capacity bottleneck.

This solution enables telecom operators to quickly view the capacity status of the RAN system, find the capacity bottleneck, and provide guidance to capacity expansion of sites, RAN hardware, and licenses.

Based on Huawei's rich OM experience on wireless networks, the capacity visibility solution predefines a method of calculating the capacity resource usage of RAN devices, transmission resources, and air
interface resources, and also predefines alarm thresholds. By using the capacity status overview, device capacity panel, capacity geographic display, and traffic trend display functions, the capacity visibility
solution enables users to detect and analyze capacity bottlenecks and view the traffic trend.
Capacity Visibility
The PRS collects traffic statistics, license data, and configuration data of RNCs and NodeBs from the RAN over the U2000.
The PRS presents the capacity resource usage of the RAN on the graphic user interface (GUI). The capacity monitoring items include network equipment, air interfaces, transmission resources, and licenses.
The following resources are visible in the capacity visibility solution.
Category Visible Resource
BSC6900 SPU, MPU, DPU, SCU, and interface boards

Average CPU usage of the SPU, MPU, and DPU at the RNC level
BSC6910 CP, UP, RMP, SCU, and interface boards
NodeB Board CPU

CNBAP
CE
Air interface Code resources

Downlink power
Uplink load
Common channels
Transmission resource Transmission resource usage on the Iu, Iur, and Iub interfaces when transmission resource pools are not configured
Transmission resource usage on the Iu, Iur, and Iub interfaces
License CS Erl license, PS traffic license, HSUPA traffic license, and HSDPA traffic license
Hardware license, NIU board license, active user number license, and cell-level HSPA user number license
Figure 3-1 shows the main interface of the capacity visibility feature.
Figure 3-1 Main interface of capacity visibility
click to enlarge
Users can determine the overall status of the network capacity by viewing the colors and numbers under each legend. The red color indicates the critical severity, orange indicates warning, green indicates normal,
while gray indicates not involving in evaluation or other activities. The number under each legend indicates the number of NE instances.
Network Capacity Bottleneck Detection

The network capacity bottleneck can be detected through visual alarm indications. In addition to the overview of the entire network capacity status, the capacity visibility solution supports the RNC device panel
and the short-term capacity trend chart.
Figure 3-2 Capacity bottleneck detection
click to enlarge
Capacity Bottleneck Assistant Analysis
1. Correlated analysis of the SPU and NodeB: guides the NodeB re-homing between SPU subsystems.
2. Load breakdown function: provides the SPU load, cell uplink power, and cell downlink power as a reference for optimization.
3. Capacity map: geographically presents the correlation of capacity problems.
Figure 3-3 Capacity bottleneck assistant analysis

click to enlarge
Visible Traffic Trend and Model

The capacity visibility solution allows users to plan the network in the long term and extract feature data for capacity prediction as a reference.
1. List of features involved in the capacity visibility solution
Capacity analysis and WOFD-097700 PRS Basic Service PRS V100R002 PRS Statistics Performance Visibility User Guide
visibility
WOFD-093900 UMTS RAN Capacity Visibility PRS V100R008 PRS Statistics Performance Visibility User Guide
WOFD-093400 GIS Support PRS V100R007 PRS Statistics Performance Visibility User Guide
2. Descriptions of features involved in the capacity visibility solution
WOFD-097700 PRS Basic Service This feature is a basic feature and provides user management and system backup.
WOFD-093900 UMTS RAN Capacity Visibility This feature supports network capacity bottleneck detection, capacity bottleneck assistant analysis, and traffic trend visibility.
WOFD-093400 GIS Support This feature provides geographical display for users.

The KPI insight solution is applicable to all networks that require KPI insight. This solution is specially aimed at networks with poor KPIs or networks that are under the risk of KPI deterioration in the future due
to the fast growth in the number of subscribers and rapid change in the traffic model.
KPI insight allows users to view the current KPI status, and assists users to complete daily KPI reports and network problem analysis, for example, KPI improvement.

KPIs are of telecom operators' prior concern. The KPI insight feature provided by the PRS helps telecom operators view and learn about the network KPI status on the GUI, and instructs them to detect KPI
problems and perform cause analysis.

There are a large number of counters for the wireless network, and therefore it will take a long time to define key KPIs to monitor the network performance and define associated KPIs and reports to analyze
different types of KPI problems.
To ease performance analysis, KPI insight provides a KPI monitoring and analysis system that can drill down to the root causes of KPI problems. One-click query allows users to monitor the performance of an
object dimension on the network. The KPI alarm indication table, chart, and report show the network performance in a visible way. KPI insight also incorporates mature network optimization experience into the
PRS for network quality correlated analysis.
The application scenarios of KPI insight include KPI monitoring and KPI cause analysis.
KPI Monitoring
In the KPI monitoring scenario, users should focus on KPIs, collect KPIs from different dimensions such as entire network, RNC, and cell group, and view the change trend. Once an abnormal KPI is detected,
users need to further locate the cause.
KPI insight integrates Huawei's rich OM experience of many years. Users can select major KPIs and specify their alarming thresholds. Then, the PRS will provide alarm indications on the GUI and export results
as expected.
Users can select to query data by report type, time range, or NE range. After users click Query, the PRS presents users the KPI monitoring data and the trend chart of each object dimension. The KPI monitoring
data supports GIS geographic display.
This section uses the UMTS PS services as an example. KPI monitoring can monitor five categories of KPIs:
Accessibility
Mobility
Network availability
Retainability
Service integrity
Figure 3-4 Main interface of KPI insight

click to enlarge
KPI Cause Analysis

In the KPI cause analysis scenario, users must locate the cause of a KPI problem by analyzing the characteristics of abnormal KPIs from different dimensions such as time, cell distribution, and failure cause.
A typical way of analyzing KPI causes is as follows:
Trend analysis: analyzes the problem occurrence time and checks whether the problem always exists.
Top N cell analysis: focuses on the worst cells.
Failure cause analysis: analyzes the causes of a failure and the proportion.
Trend and failure cause combined analysis: analyzes the change of the failure cause proportion at different times.
Based on the OM and optimization expertise for different network types, KPI insight filters some typical KPIs and predefines the network performance analysis service model associated with these KPIs. If users
perform service-associated drill operation on an abnormal KPI, the PRS analyzes the associated cause according to the KPI-related service report predefined in the service model. This method is different from the
traditional manual analysis, which requires the concurrent analysis of multiple KPIs. It directly performs associated analysis on problematic KPIs and makes problem locating more efficient.
Figure 3-5 Comprehensive analysis of KPI insight
click to enlarge
1. List of features involved in the KPI insight solution
KPI analysis and WOFD-092900 UMTS RAN KPI Insight PRS V100R009 N/A
visibility
WOFD-097700 PRS Basic Service PRS V100R002 PRS Statistics Performance Visibility User Guide
WOFD-093400 GIS Support PRS V100R007 PRS Statistics Performance Visibility User Guide
2. Descriptions of features involved in the KPI insight solution
WOFD-092900 UMTS RAN KPI Insight This feature provides a system for monitoring and analyzing KPIs, facilitating the location of KPI problems.
EBC is applicable to the scenario where telecom operators focus on the KPIs at the service layer and the user layer to implement lean network operation.

There are more than 100 KPIs at the service and user layers under the KPIs of the network layer. If the traditional method is adopted, massive counters must be available for lean performance monitoring. Massive
counters will cause the problems such as the increase of northbound management cost, long delivery period, and heavy NMS load.
The EBC provides a mechanism of generating counters based on events. It also provides a platform for telecom operators to flexibly customize and generate event-based counters.

The EBC solution requires the deployment of the U2000 and the PRS or NMS, and the SAU board must be installed in the RNC. The SAU provides NE data collection and counter measurement. The U2000
provides EBC counter management and northbound services. The PRS or NMS system stores counter data for a long time and shows counters on the GUI.
NOTE:
The EBC solution in this section refers to management of customized counters.
Application Scenarios and Advantages

The core of the EBC is the counter template (Base Counter). A counter template can generate hundreds of counters.
As a supplement to traditional performance data analysis, the EBC extends the failure cause analysis for more detailed services and bearers, such as the deep analysis of different failure scenarios for CS/PS
services and bearers. Base Counter includes detailed filter criteria for basic service types and bearers, and may include other filter criteria such as failure cause, quality, distance, and operator.
Table 3-1 Examples of EBC application scenarios
Scenario Description Example
Deep analysis of network performance By associating Base Counter with a failure cause (setting the filter Example 1: For the Base Counter that specifies RRC connection failures, you can perform deep analysis
problems criterion to a failure cause value), you can define detailed EBC of different causes of RRC connection failures by correlating connection setup causes with connection
counters for deep analysis of network performance problems. failure causes. In addition, Base Counter has abundant failure cause values and therefore you can define
more failure scenarios in Base Counter such as connection failure.
Example 2: For the Base Counter that specifies handover failures between two cells, you can analyze the
failure scenarios based on the failure cause criteria.
Multi-dimensional analysis of network You can perform multi-dimensional network performance analysis Example 1: You can analyze the connection failure distribution proportion for different qualities based
performance problems and collect statistics by correlating Base Counter with quality, on the RSCP or Ec/No during RRC connection.
distance, and operator (for example, setting the filter criterion to Example 2: You can analyze the KPIs of different operators by combining the operator's filter criteria
quality, distance, or operator.) and other filter criteria.
Table 3-2 lists the EBC's advantages over the traditional solution.
Table 3-2 EBC's advantages over the traditional solution
Comparison Item Traditional Solution EBC
Delivery time One year 15 minutes
System load Heavy Light
NE load Heavy Light
Implementation Process
1. On the GUI of the U2000 EBC management, users can customize counters based on the Base Counter (which is provided in the EBC reference documentation) and activate these counters.
2. The U2000 issues commands to the RNC to turn on the CHR switch of these counters and deliver these counters to the SAU. According to the definition rules of the counters, the SAU starts to
preprocess CHRs.
3. The RNC reports the preprocessed results to the U2000. The U2000 aggregates the results into a periodical result file. After converting the file into a desired format, the U2000 reports the file to the PRS
or NMS to show the results of the user-defined counters.
1. List of features involved in the EBC solution
Management of customized WOFD-192300 Event-Based Counter - WRAN M2000 V200R013 N/A

counters
WOFD-100220 Performance File Interface M2000 V200R002 N/A
WOFD-097400 KPI Management PRS V100R005 N/A
2. Description of features involved in the EBC solution
WOFD-192300 Event-Based Counter - WRAN This feature provides a mechanism of generating counters based on events. It also provides a platform for telecom operators to flexibly
customize and generate event-based counters.
WOFD-100220 Performance File Interface This feature is required when users want to query the EBC counters over the NMS on the U2000.
WOFD-097400 KPI Management This feature is required when users want to query EBC counters on the PRS.
The features involved in the EBC solution do not affect each other. They can be used together.
For details, see U2000 EBC Management User Guide and U2000 EBC Feature Description.

This solution applies to scenarios where the experience of xMbps Anytime Anywhere is a concern of telecom operators and is used as a criterion in network planning. The value of x depends on network
characteristics. In most cases, xMbps Anytime Anywhere refers to 2 to 3 Mbit/s Anytime Anywhere.

As an important index for the radio access network, rate directly affects user experience.
The xMbps anytime anywhere visibility solution aims at achieving x Mbit/s at anytime and anywhere. When the rates in some areas on the network do not reach x Mbit/s, capacity expansion or site addition is
required. The multi-screen comparison function can also be used to present coverage and traffic distribution so that operators can perform precise capacity expansion and site addition in valuable areas.

In RAN17.1, the xMbps anytime anywhere visibility solution is enhanced by enabling the rate capability and actual rate to be visible at the grid level. A target rate is generated based on the service characteristics
on the live network. With this target rate, the grids with insufficient rate capability are accurately detected. Capacity expansion or site addition can be performed in these grids.
Visibility of Grid-Level Rate Capability

The rate capability of the air interface reflects the average air interface capability provided by the RAN to a single user.
The rate capability of the air interface is related to the number of concurrent users, grid-level CQI, cell power, number of available code resources in a cell, and UE capability. The grid-level rate capability is
calculated based on the rate capability of the air interface and the measurement report (MR) positioning results and is displayed on the GIS. Generally, the display granularity of grids is 50 m x 50 m.
Visibility of the Grid-Level Rate Capability Fulfillment Rate

The fulfillment rate of the rate capability equals the ratio of the rate capability to the target rate. This fulfillment rate indicates the probability that the rate capability reaches the target rate and serves as an
important reference for capacity expansion or site addition. For the grids with a low fulfillment rate, a visual alarm (red) is displayed on the GIS.
Visibility of the Actual Grid-Level Rate

The actual grid-level rate equals the average service rate in a grid.
The actual rate is affected by the bandwidth capability in the RAN network as well as by many other factors, such as the actual service requirement, UE capability, PS gateway, and SP server. A low actual rate may
be caused by insufficient amount of data to transmit or problems on the CN side.
The actual rate is used only as a reference. If the amount of data to be transmitted is insufficient, the low rate problem does not need to be handled.
Grid-Level Coverage Multi-Screen Comparison

This function is used to analyze causes for the low rate. The PRS supports geographical display of grid-level RSCP, Ec/Io, RSCP proportion, Ec/Io proportion, pilot coverage scope, and UE transmit power.
Grid-Level Traffic Multi-Screen Comparison

This function is used to identify low-rate areas. The PRS supports geographical display of grid-level AMR traffic, HSDPA traffic, HSUPA traffic, downlink PS R99 traffic, uplink PS R99 traffic, number of voice
users, and number of PS users.
1. List of features involved in the xMbps anytime anywhere visibility solution
xMbps anytime anywhere WOFD-094620 UMTS xMbps Visibility - Grid PRS V100R015 RAN Service Visibility
visibility Level
WOFD-097700 PRS Basic Service PRS V100R012 N/A
WOFD-093903 UMTS MBB Grid-level Basic PRS V100R015 N/A

Package
WOFD-093400 GIS Support PRS V100R007 N/A
2. Description of features involved in the xMbps anytime anywhere visibility solution
WOFD-094620 UMTS xMbps Visibility - Grid This feature provides the following functions: visibility of grid-level rate capability, visibility of the grid-level rate capability fulfillment rate, and
Level visibility of the actual grid-level rate.
WOFD-093903 UMTS MBB Grid-level Basic This feature provides CHR/MR data collection and preprocessing.
Package
The features involved in the xMbps anytime anywhere visibility solution do not affect each other. They can be used together.
For details, see PRS Statistics Performance Visibility User Guide.

This solution applies to multimode networks where UEs migrate between different networks in consideration of the marketing strategy and spectral efficiency. With this solution, UEs are gradually migrated from a
low RAN to a high RAT, for example, from GSM to UMTS.

The MBB subscriber migration visibility solution identifies fallback UEs as well as the number of fallbacks, traffic, fallback causes, and geographical areas where fallback occurs. With this solution, telecom
operators can clearly evaluate the network coordination status, the number of fallback UEs, and the amount of traffic loss. Telecom operators can then formulate more effective solutions to address these problems
based on the evaluation results.
This solution enables the UE fallback from UMTS to GSM to be visible and identifies fallback UEs. If UE fallback occurs, telecom operators can quickly locate the cell with fallback and the fallback causes,
thereby facilitating fallback troubleshooting.
RAN16.0 implements the visibility of cell-level UE fallback from UMTS to GSM. This solution determines whether UE fallback from UMTS to GSM occurs based on counters related to inter-RAT handovers,
such as the proportion of CS inter-RAT handovers, PS inter-RAT handovers, and total inter-RAT handovers, the number of inter-RAT handovers, and handover causes.
In RAN17.1, this solution is enhanced by supporting the identification of UEs experiencing fallback from UMTS to GSM, identification of the grid where UE fallback occurs, and visibility of inter-RAT handovers
on the GIS.
Measurement of UMTS-to-GSM Handovers

Table 3-3 lists the items that are available on the PRS for measuring the number and proportion of CS inter-RAT handovers. The measurement results can be viewed on the GIS of the PRS. If the proportion of CS
inter-RAT handovers exceeds a predefined threshold, a visual alarm indication is displayed, facilitating the location of the corresponding geographical areas.
Table 3-3 Numbers and proportion of CS inter-RAT handovers
Item
CS Inter-RAT Handover Out Ratio
CS Inter-RAT Handover Times
CS Release Times
Cause Classification of UMTS-to-GSM Handovers

Figure 3-6 shows an example of the cause classification of UMTS-to-GSM handovers. Based on the major causes, telecom operators can effectively optimize the network performance.
Figure 3-6 Cause classification of UMTS-to-GSM handovers
click to enlarge
Display of the Inter-RAT Handover Trend

In addition to cause classification, the PRS also displays the trend in inter-RAT handovers. Telecom operators can compare the trend before and after optimization measures are taken.
User Type Identification and Visibility

This solution classifies PS users into five types by analyzing user behavior and traffic characteristics based on UFDR data reported by the GGSN. This solution also calculates the proportion of users of each type
to the total number of users, and proportion of the total uplink and downlink throughput of each user type to the overall throughput on the network.
The user type identification can be performed on a per cell basis, and the user type identification results are displayed on the GIS at the cell level.
Table 3-4 Definitions of PS user types
User Type Definition User Type ID
Users stay in 3G with 3G terminals Defines the users who access the UMTS network during a measurement period. TypeA
Users inter-working in 2G3G with 3G terminals Defines the users who access both the UMTS and GSM networks during a measurement period, that is, the users who fall back from TypeB
UMTS to GSM during a measurement period.
Users stay in 2G with 3G terminals Defines the users who support UMTS but access the GSM network during a measurement period. The possible reason is that these TypeC
users are locked to the GSM network.
Users stay in 2G with 2G terminals & high PS traffic Defines the users who support only GSM and access the GSM network during a measurement period. In addition, these users have a TypeD
high PS throughput and are considered as highly active PS users. This type of users has no interaction with TypeC users because
TypeC users have already been sorted out.
Users stay in 2G with 2G terminals & low PS traffic Defines the users who support only GSM and access the GSM network during a measurement period. In addition, these users are TypeE
not highly active PS users. This type of users has no interaction with TypeC users because TypeC users have already been sorted
out.
Identification and Visibility of Grids With UE Fallback

The PRS identifies the grids with UE fallback, which can be caused by all types of reasons, such as inter-RAT handovers, blind coverage, and weak coverage. The PRS then displays these grids on the GIS.
With this function, operators can take specific measures to solve the UE fallback problem in specific grids. These measures include adjusting handover parameters, improving coverage, and increasing capacity.
Visibility of Inter-RAT Handovers on the GIS
The occurrences of inter-RAT handovers are displayed at the grid level on the GIS. In this way, operators can directly locate the geographical areas with inter-RAT handovers.
Figure 3-7 shows the main interface of MBB subscriber migration visibility.
Figure 3-7 Main interface of MBB subscriber migration visibility
click to enlarge
1. List of features involved in the MBB subscriber migration visibility solution
MBB subscriber migration WOFD-094500 User Fallback (GSM-UMTS) – Cell Level PRS V100R014 N/A
visibility
WOFD-094512 UMTS User Migration – Fallback Analysis – Grid PRS V100R015 N/A
level
2. Description of features involved in the MBB subscriber migration visibility solution
WOFD-094500 User Fallback (GSM-UMTS) – Cell This feature identifies cells where a larger number of UEs fall back from UMTS networks to GSM networks, and obtains the time when UE
Level fallback occurs and the causes of UE fallback.
WOFD-094512 UMTS User Migration – Fallback This feature displays the specific grids (50 m x 50 m) where UEs fall back from UMTS networks to GSM networks and where UEs camping on
Analysis – Grid level GSM cells reselect UMTS cells.
The features involved in the MBB visibility solution do not affect each other. These features can be used together.

This solution applies to scenarios where telecom operators focus on network coverage and want to know the status of their network coverage in real time.

This solution helps evaluate the network coverage quality. Based on the evaluation results, telecom operators can quickly and efficiently find network coverage problems, thereby facilitating the improvement of
network quality.

In RAN16.0, the coverage visibility solution can be implemented only at the cell level to detect weak coverage/coverage holes and interference.
In RAN17.1, the coverage visibility solution can be implemented at the grid level.
The coverage visibility solution evaluates the cell coverage quality based on related counters and sends the evaluation results to the PRS. The PRS then displays the results in reports and sorts top cells. The
counters that indicate the cell coverage quality include RSCP, Ec/No, Transport Propagation Delay (TP), cell power, and cell load.
Weak coverage or coverage holes

Weak coverage or coverage holes can be identified based on the downlink RSCP, uplink UE transmit power, and TP from the UE to the NodeB.
Indoor weak coverage
Indoor weak coverage can be identified based on the grid-level indoor RSCP and Ec/Io.
Interference
Interference can be identified based on the downlink Ec/No, downlink transmitted carrier power (TCP), and uplink RTWP.
The PRS provides an independent menu for cell-level coverage quality evaluation. The reports display counter measurement results on multiple pages. The PRS also supports the display of the evaluation
results on the GIS and supports calculation of the proportion of objects with poor counter values.
Figure 3-8 PRS coverage quality evaluation reports
click to enlarge
1. Feature involved in the coverage visibility solution
UMTS MBB Grid-level Basic Package WOFD-093903 UMTS MBB Grid-level Basic PRS V100R015 N/A
Package
2. Description of the feature involved in the coverage visibility solution
WOFD-093903 UMTS MBB Grid-level Basic Package As a basic feature, this feature helps operators quickly find network coverage problems.

The traffic volume visibility solution is intended for operators who desire to know the geographic distribution of traffic.

Earlier, when analyzing network hotspots or problems, operators assumed that UEs and traffic are evenly distributed in cells. Operators then corrected analysis results based on cell performance files and their
knowledge of the live network.
Actually, UEs and traffic are unevenly distributed in cells on the live network. Some areas may do not have the expected large amount of traffic, whereas others may have an amount of traffic greater than expected.
Free from the restrictions of traditional methods, the traffic visibility solution analyzes traffic distribution and user service behavior distribution by grid and identifies differences between hotspot areas. This allows
operators to intuitively and efficiently know the status of the live network.

This solution introduces a traffic map, on which voice traffic, HSDPA traffic, HSUPA traffic, downlink PS R99 traffic, uplink PS R99 traffic, voice user number, and PS user number are displayed. The voice user
number and PS user number can be displayed only at the grid level, whereas other items can be displayed at the grid and cell levels.
Voice traffic
Voice traffic can be displayed by day, hour, or week in the unit of Erlang at the grid or cell level.
HSDPA traffic
HSDPA traffic can be displayed by day, hour, or week in the unit of Kbyte at the grid or cell level.
HSUPA traffic
HSUPA traffic can be displayed by day, hour, or week in the unit of Kbyte at the grid or cell level.
Downlink PS R99 traffic
Downlink PS R99 traffic can be displayed by day, hour, or week in the unit of Kbyte at the grid or cell level.
Uplink PS R99 traffic
Uplink PS R99 traffic can be displayed by day, hour, or week in the unit of Kbyte at the grid or cell level.
Voice user number
The voice user number can be displayed by day, hour, or week at the grid level.
PS user number
The PS user number can be displayed by day, hour, or week at the grid level.
Figure 3-9 Main interface of MBB traffic visibility

click to enlarge
1. Feature involved in the traffic volume visibility solution
UMTS MBB Grid-level Basic WOFD-093903 UMTS MBB Grid-level Basic Package PRS V100R015 N/A
Package
2. Description of the feature involved in the traffic volume visibility solution
WOFD-093903 UMTS MBB Grid-level Basic Package As a basic feature, this feature displays geographical traffic distribution on networks.
WOFD-093900 UMTS RAN Capacity Visibility PRS V100R008 PRS ATAE Cluster System Commissioning Guide
PRS Statistics Performance Visibility User Guide
WOFD-093400 GIS Support PRS V100R007 PRS ATAE Cluster System Commissioning Guide
WOFD-093020 Performance Threshold Alarm PRS V100R014 PRS ATAE Cluster System Commissioning Guide
WOFD-093011 UMTS RAN Real-time KPI Monitoring PRS V100R014 PRS ATAE Cluster System Commissioning Guide
WOFD-092900 UMTS RAN KPI Insight PRS V100R009 PRS ATAE Cluster System Commissioning Guide
WOFD-192300 Event-Based Counter - WRAN M2000 V200R013 U2000 EBC Management User Guide
WOFD-100220 Performance File Interface M2000 V200R002 U2000 Northbound Performance File Interface Developer Guide (NE-Based)
U2000 Northbound Performance File Interface Developer Guide(Measurement
Unit-Based)
WOFD-097400 KPI Management PRS V100R005 PRS ATAE Cluster System Commissioning Guide
WOFD-094600 UMTS xMbps Visibility - Cell Level PRS V100R014 PRS ATAE Cluster System Commissioning Guide
WOFD-094620 UMTS xMbps Visibility - Grid Level PRS V100R015 PRS ATAE Cluster System Commissioning Guide
WOFD-094500 User Fallback (GSM-UMTS) – Cell Level PRS V100R014 PRS ATAE Cluster System Commissioning Guide
WOFD-094512 UMTS User Migration – Fallback Analysis – Grid PRS V100R015 PRS ATAE Cluster System Commissioning Guide
level PRS Statistics Performance Visibility User Guide
WOFD-093903 UMTS MBB Grid-level Basic Package PRS V100R015 PRS ATAE Cluster System Commissioning Guide
KQI Key Quality Indicator
PRS Performance Surveillance
EBC Event-Based Counter
1. U2000 EBC Management User Guide

2. U2000 EBC Feature Description
3. U2000 Northbound Performance File Interface Developer Guide (NE-Based)
4. U2000 Northbound Performance File Interface Developer Guide (Measurement Unit-Based)
5. PRS Statistics Performance Visibility User Guide
6. PRS ATAE Cluster System Commissioning Guide

Huawei Solutions 3G

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Huawei Solutions 3G

Загружено:

Авторское право:

Доступные форматы

RAN Feature Documentation

Product Version: RAN18.1

For any question, please contact us.

Radio and Performance

Operation and Maintenance

Network Evaluation and Planning

1.1 Voice Services

Parent topic: Solution Description

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.

Huawei Technologies Co., Ltd.

1 About This Document

1.2 Disclaimer for Trial Features

1.3 Intended Audience

1.4 Change History

1.2 Disclaimer for Trial Features

1.3 Intended Audience

Need to understand voice quality improvement solutions

1.4 Change History

Change Type Change Description

Feature change None

Editorial change Optimized the structure and descriptions.

RAN18.1 Draft A (2015-12-30)

Change Type Change Description

Editorial change None

2.2 Application Scenarios

2.3 Overall Solution

Figure 2-1 Frequency bands of AMR-WB and AMR-NB services

2.2 Application Scenarios

The fastest access solution

2.3 Overall Solution

Use the best experience solution to improve the MOS.

Figure 2-2 HD voice solution

3.2 The Best Experience

3.3 The Fastest Access

3.4 The Widest Coverage

3.5 Speech Quality Assessment and Maintenance

3.1.1 Scenario Description

12.2 kbit/s - (1) - - - - - 1 - - - - - - 1 1

3.1.2 Solution Purpose

3.1.3 Solution Description

Feature ID Feature Name Introduced in... Reference Document

WRFD-011600 TFO/TrFO RAN3.0 AMR Feature Parameter Description

WRFD-020701 AMR/WB-AMR Speech Rates RAN2.0 AMR Feature Parameter Description

Description of Features Involved in the Solution

Feature ID Feature Name Feature Description

It is recommended that rate set 4 be configured for end-to-end HD voice services.

When to Use This Solution

Scenario CN RAN UE Remarks

3.2 The Best Experience

3.2.2 Solution Purpose

3.2.3 Solution Description

List of Features Involved in the Solution

Feature ID Feature Name Introduced in... Reference Document

Description of Features Involved in the Solution

Feature ID Feature Name Feature Description

Scenario CN RAN UE Remarks

3.3.2 Solution Purpose

3.3.3 Solution Description

List of Features Involved in the Solution

Feature ID Feature Name Introduced in... Reference Document

Description of Features Involved in the Solution

Feature ID Feature Name Feature Description

The following is an example of solution implementation.

3.4 The Widest Coverage