RAN Capacity Management Guide

Contents
4.7 RAN Capacity Management Guide
 RAN18.1

Capacity Management Guide

Issue 01

Date 2016-02-29

HUAWEI TECHNOLOGIES CO., LTD.

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

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

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any
kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: support@huawei.com
Contents

1 About This Document

1.1 Overview

1.2 Intended Audience

1.3 Change History

2 Overview of Capacity Management

3 Capacity Management Activities

3.1 Capacity Planning

3.1.1 Basic Capacity Planning

3.1.2 xMbps Capacity Planning

3.2 Dimensioning

3.3 Product Configuration

3.4 Capacity Monitoring

3.5 Capacity Optimization

3.6 Capacity Expansion

3.6.1 Capacity Expansion of the Air Interface

3.6.2 Capacity Expansion of Devices

4 Reference Documents
1
1.1 Overview
About This Document

This document describes the six capacity management activities throughout network lifecycle, which are, capacity
planning, dimensioning, product configuration, capacity monitoring, capacity optimization, and capacity expansion.

1.2 Intended Audience

This document is intended for personnel who:

Need to understand this solution

Maintain Huawei products

1.3 Change History

01 (2016-02-29)

This issue does not include any changes.

Draft A (2015-12-31)

This is a draft.
2 Overview of Capacity Management

New network construction and inventory network operation involve different capacity management activities, as
shown in Figure 2-1.

Figure 2-1 Capacity management process

Each management activity consists of some key actions, as shown in Table 2-1.

Table 2-1 Key actions of each management activity

Management Key Action

Activity

Capacity planning As to new network construction, confirm the network construction objective, su
as the network capacity and requirements for user experience.

As to inventory network operation, confirm the capacity expansion object, such

the resource types to be expanded and load increase factors.
Management Key Action
Activity

Dimensioning Compute resources that require special attentions, including air interface
resources, CE resources, Iub resources, and RNC resources (load sharing).

Product configuration Compute the requirements for base stations, cells, boards, and transport devices

Capacity monitoring Monitor the major resources that affect system capacity. Network status is
monitored in real time.

Capacity optimization Enable features/functions to improve throughput.

Capacity expansion Add air interface and device resources to expand system capacity.
3 Capacity Management Activities

3.1 Capacity Planning

Every network undergoes a cyclical process that includes developing users, light load, heavy load, and capacity
expansion. Based on years of network maintenance and service experience, Huawei works out two capacity planning
solutions: basic capacity planning and xMbps planning. Resources required in the two solutions are shown in Figure
3-1.

Figure 3-1 Capacity planning solutions

3.1.1 Basic Capacity Planning

The network capacity is planned based on the current and future capacity demands to ensure basic network KPIs
(such as KPIs related to accessibility and service drops).

3.1.1.1 Prerequisites

Before basic capacity planning, predict network capacity requirements based on the current capacity status and
future service planning. To know about the current capacity status, evaluate loads of the devices and the air interface
on the network.

3.1.1.2 Planning Procedure

The following figure shows the procedure of basic capacity planning.

Figure 3-2 Basic capacity planning procedure

 The steps of planning capacity for a new network and an inventory network are different.

New network

Step 1 Learn demands of the operator.

Operator demands include traffic demands and user experience assurance solutions.

Step 2 Set network construction objective.

The network construction objective will be regarded as the acceptance standards of the new network after being
established. Capacity and user experience are the most important factors.

Step 3 Reach an agreement with the operator.

Reach an agreement with the operator in terms of network construction objectives. The objectives are the service
demands of the new network.

----End

Inventory network

Step 1 Assess the capacity bottleneck.

Assess the capacity bottleneck based on the capacity monitoring result.

Step 2 Plan the capacity expansion objective.

 If the usage of a resource exceeds the corresponding capacity expansion threshold, perform capacity expansion for
this resource and decrease the target load to 10 percentage points lower than the capacity expansion threshold. For
example, if the SPU capacity expansion threshold is 60%, then the target load should be less than 50%.

Step 3 Predict the future capacity demands.

If the usage of a resource type does not exceed the corresponding capacity expansion threshold, the future capacity
demands are predicted based on the current traffic model and service loads.

Step 4 Define factors causing load growth.

There are various factors causing an increase in loads. The following factors are defined for future capacity demand
prediction:

l SubscriberFactor: total subscriber quantity increase factor

l CSSigFactor: single-subscriber CS signaling plane increase factor

l PSSigFactor: single-subscriber PS signaling plane increase factor

l CSTrafficFactor: single-subscriber CS user plane increase factor

l PSTrafficDLFactor: single-subscriber PS downlink user plane increase factor

l PSTrafficULFactor: single-subscriber PS uplink user plane increase factor

During future capacity demand prediction, you can specify several load subitems for each kind of resource based on
consumption factors, and then sum up all load subitems after each of them times its corresponding increase factor to
calculate the total loads.

----End

3.1.2 xMbps Capacity Planning

xMbps planning aims to meet the data rate required by end users. It evaluates the data rates supported by the air
interface on a grid level to decide the difference between the current and target data rates, and then provides carrier
capacity expansion and site planning advice or a multi-sector solution by means of simulation.

3.1.2.1 Background

Basic KPI can no longer reflect user experience of web browsing and video services in the Mobile Broadband (MBB)
era. The xMbps assesses the current grid-level capacity of the network and provides capacity planning suggestions.

Mobile networks have entered the MBB era leaving the 2G voice era behind. Videos are evolving from high
definition (HD) to ultra HD (UHD). The performance of mobile networks is limited by the air interface. Therefore,
providing a high bearer bandwidth ensures good user experience.

Figure 3-3 Impact of speed on services

Before building an MBB network, set the target xMbps based on the user experience requirement of the target
service. Consider the following factors when setting the target xMbps.

xMbps for different types of services

The bearer rate varies with the service type, as shown in Figure 3-4.

Figure 3-4 xMbps for different types of MBB services

User experience of a service needs to be evaluated from various aspects. The bearer rates to ensure good user
experience from various aspects may also be different, as shown in table Table 3-1. The highest bearer rate is
selected as the bearer rate for the service.

Table 3-1 Bearer rates for different types of services

 Format Resolution Code Bit Rate User Experience Bearer Network
(Mbit/s) Rate Requiremen
(Mbit/s) (Mbit/s)

360p 480x360 H.264 0.5-0.8 Startup Time < 4s 1 1

Interruption-free Share > 0.8

95%

480p 640x480 H.264 1.2-2.3 Startup Time < 4s 3 3

Interruption-free Share > 2.3

95%

720p 1280x720 H.264 2.1-3.8 Startup Time < 4s 5 5

Interruption-free Share > 3.8

95%

1080p 1920x1080 H.264 5-7.7 Startup Time < 4s 10 10

Interruption-free Share > 7.7

95%

The bit rates of video services with different definitions are obviously different. Although the definitions are the
same, actual bit rates are different because of different dynamic picture proportions and video coding levels. The
preceding table is for reference only.

xMbps in different areas

The distribution of MBB services is unbalanced. The proportion of high data rate services in urban areas is large
while the proportion of low data rate services in rural areas is large. Therefore, xMbps should be planned based the
area of the network.

For example, the target areas can be classified into major areas, valued areas, and common areas based on HD
services, valued users, and terminal distribution.
 Table 3-2 Area classification

Area Proportion of HD Proportion of valued Proportion of

services users intelligent terminal

Major areas 50% 60% 45%

Valued area 30% 35% 50%

Common area 20% 5% 5%

The values of xMbps for different areas should be specified separately based on the mainstream valued services. In
areas where web services and low definition video services are dominant, the target bearer rate is set to 1 Mbit/s. In
areas where HD or UHD video services are leading, the bearer rate is set to 5 Mbit/s or 10 Mbit/s. This can reduce
CAPEX.

xMbps engineering planning

A specific xMbps anywhere and anytime is not an absolute requirement. It can be defined as follows from the
perspective of engineering planning: The xMbps is reached in a specified percentage (typical value: 95%) of places
within a specified percentage (typical value: 90%) of time to ensure user experience of the good level or above.

3.1.2.2 xMbps Planning Procedure

The xMbps planning procedure is as follows:

Step 1 Decide the target rate.

A proper target rate is calculated based on the typical rate required by services through analyzing service types and
the ratio of each type of service. 1 Mbit/s can meet 90% of service requirements for networks with non-video service
requirements. Therefore, 1 Mbit/s is used as the target rate during xMbps planning

Step 2 Evaluate grid-level rate capability.

To evaluate the grid-level rate capability, calculate the theoretical rate of each grid based on the channel quality
indicator (CQI), number of UEs, and available power in this grid, and then geographically display the rates in the
form of grids.

Step 3 Provide advice on planning.

You can provide reasonable advice on carrier capacity expansion and site planning through simulation and
positioning based on the difference between the current grid-level rate capability and the target rate. This method is
also applicable to multi-sector planning.
----End

3.2 Dimensioning

At the dimensioning stage, the service demands of capacity planning are used to predict the critical resource
demands for network construction, such as the air interface, CE, IUB, and RNC resources. These resources required
at the dimensioning stage are abstract and irrelevant to the network topology and hardware type.

For details, see RAN18.1 Dimensioning Rules.

3.3 Product Configuration

At the product configuration stage, the abstract resource demands of dimensioning are used to configure base
stations, cells, boards, and transport devices based on product specifications, capability, and other related
parameters.

For details about how to configure RNC, see SRAN11.1&GBSS18.1&RAN18.1 BSC6910 Configuration Principles
(Global) and SRAN11.1&GBSS18.1&RAN18.1 BSC6900 Configuration Principles (Global).

For details about how to configure NodeB, see SRAN11.1&GBSS18.1&RAN18.1&eRAN11.1 3900 Series Base
Station Configuration Principles and SRAN11.1&RAN18.1 BTS3911E Series Base Station Configuration Principles.

3.4 Capacity Monitoring

It is required to monitor major resources affecting network capacity to learn real-time network status after the
network operates steadily, thereby enabling the network to stay in optimal status and meeting carriers' service
requirements. The resources whose capacity needs to be monitored can be classified into air interface and device
resources.

If air interface resources are found to be insufficient, decide whether capacity optimization can be conducted to
relieve the congestion situation first. If the problem persists, perform capacity expansion.

If device resources are found to be insufficient, add devices accordingly.

For details, see RAN18.1 Capacity Monitoring Guide (BSC6910-Based) and RAN18.1 Capacity Monitoring Guide
(BSC6900-Based).

3.5 Capacity Optimization

Capacity optimization in this section indicates capacity optimization over the air interface by enabling features or
functions to increase network capacity. If network capacity needs to be improved to meet increasing service
demands, you are advised to perform network optimization.

For details, see UMTS Uplink Throughput Improvement Solution, UMTS Downlink Throughput Improvement Solution,
and UMTS Small Data Packet Storm Solution.

3.6 Capacity Expansion

Network capacity needs to be expanded when it cannot meet the capacity standard for network construction
currently or in the foreseeable future. The rules for capacity expansion are as follows:

The air interface capacity needs to meet traffic demands.

 The device capability needs to match the air interface capacity.

Compared with new network construction, inventory networks provide more information for reference. You can
decide whether to add resources or authorization based on the resource utilization on the network from all resource
dimensions and under the selected network construction solution.

3.6.1 Capacity Expansion of the Air Interface

When the maximum system capability cannot meet service demands with the current network configurations, you
have to modify the network configurations to increase the network capacity.

3.6.1.1 Capacity Expansion Principles

Expansion points are decided based on basic capacity and xMbps.

Capacity expansion for networks planned based on basic

capacity

You are advised to use this capacity expansion solution if the network adopts basic capacity planning.

In typical smartphone traffic scenarios, the relationships between system capacity demands/system capacity
capability/actual system capacity/lower limit of system capacity and the number of users are shown in the following
figure.

Figure 3-5 Relationships between system capacity demands/system capacity capability/actual system capacity/lower
limit of system capacity and the number of users

A: point at which the actual system capacity starts to decrease

B: target minimum system capacity demand designed by the operator

In a statistical sense, the traffic demand of each user is steady, and the capacity demand increases as the number of
users increases. Users interfere with each other due to self-interfering characteristics of the CMDA scheme. As the
number of users increases, the actual system capacity capability decreases.
The actual system capacity increases as the number of users increases and then decreases until the number of users
almost reaches the maximum number that the system capacity can support. Generally, when the actual system
capacity has a turning point or cannot meet the minimum system capacity demand, capacity expansion needs to be
performed.

Capacity expansion for networks planned based on xMbps

You are advised to use this capacity expansion solution if the network adopts xMbps capacity planning.

In typical smartphone traffic scenarios, the relationships between user-required throughput/user-perceived

throughput/xMbps and the number of users are shown in the following figure.

Figure 3-6 Relationships between user-required throughput/user-perceived throughput/xMbps and the number of
users

C: target xMbps for the area where the network is planned based on xMbps

In a statistical sense, the user-required throughput is basically steady in the specified traffic scenarios (relevant to
user types, service types, and charging policies). The throughput demand is not affected by the number of users.

The user-perceived throughput is steady and then decreases after the number of users gradually reaches the
maximum number that the system capacity can support. When the xMbps cannot meet requirements, capacity
expansion needs to be performed.

3.6.1.2 Capacity Expansion Methods

The standards for expand the capacity of the air interface are described in Table 3-3.

Table 3-3 Air interface capacity expansion standards

Capacity Planning Capacity Planning Standard

Solution
 Capacity Planning Capacity Planning Standard
Solution

xMbps capacity planning Expand the capacity of point C in Figure 3-6.

Combination of basic capacity and Expand the capacity of point A/B in Figure 3-5, and consider the C
xMbps planning capacity expansion point in Figure 3-6.

Air interface resources include the downlink power, CE resource, and uplink load. Air interface capacity expansion
focuses on the downlink power and uplink load. The lower capacity expansion point is used as the capacity
expansion point of the air interface.

Downlink power
Indexes of downlink power mainly include Transmitted Carrier Power (TCP) and non-HSDPA power (Non-HS TCP
and Non-HSPA TCP). So the capacity expansion of downlink power needs to find out the relationship between basic
capacity and downlink power (TCP and Non-HS TCP) and between user-perceived throughput and downlink power
(TCP and Non-HS TCP).

Figure 3-7 shows the dimension reference of downlink power and describes the capacity expansion method based on
downlink power.

Figure 3-7 Relationship between system capacity/user throughput and Non-HS TCP

The following is the specific procedure of the method:

Step 1 Collect data.

Collect the measured values of system capacity, user-perceived throughput, and downlink power.
Step 2 Make a relationship diagram.

Make a scatter chart with horizontal coordinate as downlink power. For example, Figure 3-7 shows the system
capacity (HSDPA traffic, unit MB), user-perceived throughput (unit kpbs), and Non-HS TCP of a site. (The capacity
and throughput are average values.)

Step 3 Decide capacity expansion points.

Decide capacity expansion points based on the relationship diagram such as Figure 3-7.

For networks built based on basic capacity planning and concerning the traffic turning point, perform capacity
expansion when Non-HS TCP reaches 50%.

l For networks built based on basic capacity planning and concerning minimum expected traffic (such as 300 MB),
perform capacity expansion when Non-HS TCP reaches 75%.

For networks built based on xMbps planning and the target is set to 1000 kbps, perform capacity expansion when
Non-HS TCP reaches 36%.

----End

Uplink load
Uplink load refers to the received total wideband power (RTWP) of a cell. The RTWP decides the uplink coverage
and system stability. Therefore, the capacity expansion based on the RTWP needs to consider uplink coverage and
system stability.

Figure 3-8 shows the relationship between system capacity/user-perceived throughput and RTWP.

Figure 3-8 Relationship between system capacity/user-perceived throughput and RTWP

When the system capacity increases gradually, RTWP increases and cell coverage decreases to below the target
(such as 64 kbps edge rate) at a moment. At this moment, you are advised to perform capacity expansion.

RTWP increases with the system capacity. Perform capacity expansion when the corresponding load factor
(Accurate background noise needs to be identified because background noise will not lead to mutual increase.)
enters the non-linear area (not exceeding 95% normally).

When the uplink coverage and system stability are satisfied, you can find out the cross point between network
capacity and RTWP (as shown in Figure 3-8) and decide whether to perform capacity expansion.

3.6.1.3 Capacity Expansion Solutions

Capacity expansion for the air interface can be implemented by adding carriers, adding NodeBs, or splitting sectors.

Adding carriers

In hotspot valued areas, good user experience needs to be ensured. Adding carriers to increase spectrum resources is
the first choice to alleviate the pressure of network capacity.

In multi-carrier deployment, carriers usually adopt high-and-low frequency mixed networking.

Low-frequency band is used as the coverage layer to achieve wide coverage nationwide.

High-frequency band is used as the capacity layer for traffic absorption in hot spots.

Adding NodeBs

Encrypted macro NodeBs

As the number of users or traffic volume increases, the required capacity will exceed the maximum capacity
provided by a NodeB. Under this circumstance, new NodeBs need to be added to avoid user experience
deterioration.

In densely populated urban areas, NodeBs carry multi-frequency multi-mode devices. Antenna and cabinet space is
insufficient, and rent and installation and maintenance fees are expensive. To solve this problem, Huawei provides
the Easy Macro solution. Easy Macro is small and light and can be installed flexibly, such as on street light poles,
stadiums, roofs and walls, and independent poles, without occupying any ground space.

Easy Macro uses the Active Antenna System (AAS) and outdoor BBU:

AAS

The AAS is a new type of radio frequency (RF) module following the Remote Frequency Unit (RFU) and Remote
Radio Unit (RRU). The AAS integrates functions of RF modules and antennas and therefore saves antenna and site
resources.

Outdoor BBU

The outdoor BBU integrates the functions of main control, transmission, and baseband processing all into one
module. It is characterized by small size and easy deployment.

Figure 3-9 shows how Easy Macro is deployed.

Figure 3-9 Easy Macro deployment

 Micro NodeBs

Smart phones become more and more popular and user behaviors always change, leading to continuous upgrade of
traffic modes and challenging user experience demands. In densely populated urban areas and indoor hot spots
where adding macro NodeBs or adding spectrum resources cannot meet requirements, add micro NodeBs.

Micro NodeBs are advantageous in terms of site acquisition and flexible deployment. They can absorb traffic
accurately in densely populated urban areas and hot spots, improving user experience. Huawei provides the
AtomCell and LampSite solutions:

Outdoor AtomCell solution

AtomCells is small and easy to camouflage, and so it can be deployed on light poles, bus stations, and telephone
booths. Microwave, WiFi, and e-Relay solutions that are developed for micro NodeBs make backhaul easier.
Therefore, AtomCell can help carriers deploy micro NodeBs in densely populated areas and hot spots.

Indoor LampSite solution

LampSite features large capacity, small size, and easy deployment. It can improve capacity indoor quickly to meet
the service requirements of indoor users.

Splitting sectors

When new NodeB and spectrum resources are unavailable, Huawei provides the multi-sector solution.

This solution can increase site capacity by 50% to 90% and improve coverage by 3 dB without adding NodeB or
spectrum resources. This effectively addresses the concerns of carriers and improves user experience. Figure 3-10
shows the comparison between normal and multi-sector solutions.

Figure 3-10 Comparison between normal and multi-sector solutions

3.6.2 Capacity Expansion of Devices
3.6.2.1 Capacity Expansion Standards

Spectrum resources of the air interface are the most precious. Device capacity must support the full utilization of the
air interface capability and match the demands for air interface capacity.

The average and peak resource usage on the live network and the peak-to-average ratio (PAR) coefficient can be
used for determining the capacity expansion threshold.

RNC resources
The types, monitoring indexes, and capacity expansion thresholds of RNC resources are listed in Table 3-4.

Table 3-4 RNC resources and their capacity expansion thresholds

Resource Type Monitoring Index Capacity Expansio

Threshold

SPU CPU load VS.XPU.CPULOAD.MEAN 50%

MPU CPU load VS.XPU.CPULOAD.MEAN 50%

DPU DSP load VS.DSP.UsageAvg 60%

SCU CPU load VS.SCU.CPULOAD.MEAN 60%

CPU load on an interface board VS.INT.CPULOAD.MEAN 50%

Forwarding load of the transport VS.INT.TRANSLOAD.RATIO.MEAN 70%

interface board
NodeB resources
The types, indexes, and capacity expansion thresholds of NodeB resources are listed in 0.

Table 3-5 NodeB resources and their capacity expansion thresholds

Resource Type Monitoring Index Capacity Expansion

Threshold

CE usage VS.NodeB.ULCreditUsed.Mean 70%

VS.LC.ULCreditUsed.Mean

VS.LC.DLCreditUsed.Mean

VS.HW.DLCreditAvailable

VS.HW.ULCreditAvailable

CNBAP load VS.RadioLink.Recv.Mean 60%

VS.DedicMeaRpt.MEAN

VS.BTS.CnbapCap.UseRate

HSPA user number VS.BOARD.UsedHsdpaUserRatio.Mean 60%

capacity utility ratio on
the baseband board VS.BOARD.UsedHsupaUserRatio.Mean

Iub transmission resources

The types, indexes, and capacity expansion thresholds of Iub resources are listed in Table 3-6 and Table 3-7.

Table 3-6 ATM transmission resources and their capacity expansion thresholds
 Resource Type Monitoring Index Capacity Expansion
Threshold

Success rate of VS.AAL2.CAC.Succ/VS.AAL2.CAC.Att 99%

bandwidth-based
admission

Physical bandwidth Signaling plane 70%

utilization
DL Iub Usage on Control Plane =
VS.SAALLNK.PVCLAYER.TXBYTES *
8/1000/<SP>/TX BW_CFG

UL Iub Usage on Control Plane =

VS.SAALLNK.PVCLAYER.RXBYTES
*8/1000/<SP>/RX BW_CFG

User plane

DL Iub Usage on User Plane = Sum

(VS.AAL2PATH.PVCLAYER.TXBYTES) *
8/<SP>/1000/TX BW_CFG

UL Iub Usage on User Plane = Sum

(VS.AAL2PATH.PVCLAYER.RXBYTES) *
8/<SP>/1000/RX BW_CFG

Table 3-7 IP transmission resources and their capacity expansion thresholds

Resource Type Monitoring Index Capacity Expansion

Threshold

Success rate of IP connection setup success rate = 99%

bandwidth-based VS.ANI.IP.Conn.Estab.Succ/VS.ANI.IP.Conn.Estab.Att
admission
 Resource Type Monitoring Index Capacity Expansion
Threshold

Physical bandwidth Signaling plane 70%

utilization
SCTP DL KBPS = VS.SCTP.TX.BYTES *
8/<SP>/1000

SCTP UL KBPS = VS.SCTP.RX.BYTES

*8/<SP>/1000

User plane

DL Iub Usage on User Plane =

VS.IPPOOL.ANI.IPLAYER.TXBYTES *
8/<SP>/1000/TX BW_CFG

UL Iub Usage on User Plane =

VS.IPPOOL.ANI.IPLAYER.RXBYTES *
8/<SP>/1000/RX BW_CFG

3.6.2.2 Capacity Expansion Solutions

Device capability includes hardware and licenses which need to be considered when capacity expansion is
performed for devices as required by air interface capacity expansion.
4 Reference Documents

Reference documents about capacity management activities are listed in Table 4-1.

Table 4-1 Reference documents

Capacity Reference Document How to Obtain

Management
Activities

Dimensioning RAN18.1 Dimensioning Rules Contact Huawei enginee

Product SRAN11.1&GBSS18.1&RAN18.1 BSC6910 Configuration Contact Huawei enginee

configuration Principle (Global)

SRAN11.1&GBSS18.1&RAN18.1 BSC6900 Configuration

Principle (Global)

SRAN11.1&GBSS18.1&RAN18.1&eRAN11.1 3900 Series

Base Station Configuration Principles

SRAN11.1&RAN18.1 BTS3911E Base Station Configuration

Principles

Capacity RAN18.1 Capacity Monitoring Guide (BSC6910-Based) Product Documentation

monitoring Operation and
RAN18.1 Capacity Monitoring Guide (BSC6900-Based) Maintenance >
Performance Manageme

Capacity UMTS Uplink Throughput Improvement Solution RAN Feature

optimization Documentation > Soluti
UMTS Downlink Throughput Improvement Solution Description > Radio and
Performance
UMTS Small Data Packet Storm Solution