Professional Documents
Culture Documents
Zte Umts Load Monitoring and Expansionguide 141112012330 Conversion Gate02
Zte Umts Load Monitoring and Expansionguide 141112012330 Conversion Gate02
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright 2013 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
and
are registered trademarks of ZTE CORPORATION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyones access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided as is and as available. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATIONs
products and technologies.
ZTE CORPORATION
Address:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website:
http://support.zte.com.cn
Email:
800@zte.com.cn
Revision History
Product Version
Document Version
RNC V3.09
Serial Number
R1.0
Author
Date
2011-3-15
Document
Version
R1.0
Prepared by
Qiao Bin, Jin
Zhengtuan, and
Xu Yi
Reviewed by
Ma Wei
Approved by
Wang Zhenhai
II
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ
1
Reference material
Null
2
3
Follow-up document: After reading this document, you may need the following information.
SEQ
1
Reference material
Null
Information
Null
2
3
III
Description
Overview
IV
TABLE OF CONTENTS
1
1.1
1.2
Overview ......................................................................................................... 1
Background ...................................................................................................... 1
Main Contents .................................................................................................. 2
2
2.1
2.2
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
3
3.1
3.2
4
4.1
4.1.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
FIGURES
Figure 1-1 High-Load Network Monitoring and Optimization ................................................ 3
Figure 1-2 High-Load Network Monitoring Process .............................................................. 4
Figure 1-3 High-Load Network Optimization Process ........................................................... 5
Figure 2-1 Relationship Between the Uplink Capacity and Noise ....................................... 10
Figure 3-1 Flowchart of Network Load Optimization ........................................................... 13
Figure 3-2 High-Load Network Optimization Process ......................................................... 15
Figure 4-1 Expansion Analysis Process ............................................................................. 17
Figure 4-2 Cell Expansion Decision Process ...................................................................... 18
Figure 4-3 Combination Chart of Cell Expansion Decision Formula ................................... 21
Figure 4-4 Relationship Between the Code Resource Utilization and Traffic ...................... 23
Figure 4-5 Relationship Between the Cell Carrier Transmit Power Utilization and TCP
Limited Proportion ................................................................................................................ 24
Figure 4-6 Average Utilization Rates of Uplink and Downlink NodeB CE Resources in
Shapingba, Chongqing, China .............................................................................................. 28
Figure 4-7 Maximum Utilization Rates of Uplink and Downlink NodeB CE Resources in
Shapingba, Chongqing, China .............................................................................................. 29
TABLES
Table 2-1 Code Resource Distribution of Code Channel ...................................................... 8
Table 4-1 Cell Expansion Thresholds ................................................................................. 19
Table 4-2 Cell Expansion Implementation Rules ................................................................ 25
Table 4-3 Node B CE Expansion Thresholds and Expansion Methods .............................. 27
Table 4-4 Cell Expansion Implementation Rules ................................................................ 29
Table 4-5 Iub Transmission Expansion Thresholds ............................................................ 31
Table 4-6 Cell Expansion Implementation Rules ................................................................ 32
Table 4-7 Monitoring Indicators of RNC Hardware Expansion ............................................ 36
Table 4-8 Observation Indicators of RNC Hardware Expansion ......................................... 37
Table 4-9 Observation Indicators of RNC Hardware Expansion ......................................... 39
Table 4-10 RNC Expansion Implementation Rules............................................................. 41
VI
Overview
1.1
Background
To monitor and optimize the high load and performance of UMTS network is one of the
key tasks in the network operation and maintenance stage. With the increase of the
subscriber number and service application, especially with the rapid development of the
wireless broadband service, the network load will keep increasing. When the network
load reaches a certain level, the network resources will be congested and the network
performance will deteriorate, affecting the end users service experience.
To provide the users with high-speed access experience and keep the competitiveness
of the UMTS network, the operators should perform real-time monitoring to the load and
performance of the whole network, alarm the network element (NE) exceeding the load
threshold, take timely measures of optimization and expansion to meet the requirement
of service development.
In the narrow sense, the load refers to the traffic loaded by the network or channel. In the
broad sense, except for the network traffic, the operators need to consider the resource
utilization of the software and hardware of each NE in the network. The higher the
utilization rate is, the heavier the load will be.
Compared with the 2G network, the monitoring and management of the UMTS network is
more complex. The reasons are as follows:
The UMTS is a soft capacity system. Its capacity is not only constrained by the hard
resources such as the CE and Iub configuration bandwidth, but also constrained by the
soft resources such as the OVSF code, uplink interference, and downlink power. Subject
to the requirements for the network coverage and service quality, the system capacity is
not a fixed value.
UMTS is a hybrid multi-service system. The system capacity is different due to different
service structure and different service model, so we cannot simply use the traffic of a
certain service to monitor the system capacity.
The UMTS may use the hybrid carrier strategy of R99+HSPA. R99 and HSPA share the
system resources, making it more complex to monitor the capacity of R99 and HSPA.
The UMTS is a network focusing on the data service. To judge the data network
congestion, we cannot simply follow the processing of the traditional voice-centric
network, that is, we cannot judge the network congestion according to whether there is a
admission rejection, but should judge the network congestion by combining the HSPA
1.2
Main Contents
The high-load network monitoring and optimization guide shall apply to the
communication network in the UMTS commercial operation and maintenance phase.
As shown in Figure 1-1, the high-load network monitoring and optimization transversely
aim at three levels of NEs: the cell of radio access network (RAN), Node B and RNC.
Longitudinally, there are three phases: high-load network monitoring, high-load network
optimization and high-load network expansion, respectively corresponding to the three
parts of this guide.
Figure 1-1
Part 1 corresponds to Chapter 2 of this guide, mainly describing the indicators needed to
be monitored for the network load. As shown in Figure 1-2, the network load monitoring of
WCDMA system mainly aim to three levels of NEs: the cell of wireless access network,
NodeB and RNC. Each NE corresponds to different RAN. Mainly involving the air
interface resources such as the code resource and power resource, the cell NE closely
relates to the users experience rate and focuses on the users feeling. The Node B NE
mainly involves the transmission resource and CE resource. According to the RNC
configuration, the RNC NE mainly involves the indicators such as the occupation of RCP
and CPU as well as the use of RUP and CE resources.
Figure 1-2
Yes
Cell-level monitoring,
analysis, and alarm
High-load network
performance
monitoring and
evaluation
NodeB-level
monitoring, analysis,
and alarm
RNC-level monitoring,
analysis, and alarm
Perform
optimization to
solve the problem
of high load
No
Yes
Cell expansion
Add carriers or power
amplifiers
Yes
NodeB expansion
Add BPC boards or
transmission resources
Yes
RNC expansion
Software: Add licenses
Hardware: Add RUB or
RCB boards
No
Part 2 corresponds to Chapter 3 of this guide, mainly describing the optimization of the
high-load network performance. There are mainly 2 aspects: the high-load network
optimization process and common optimization methods. As shown in Figure 1-3, in the
optimization process of high-load network, you should optimize the RF and wireless
parameters according to the actual network situation. The wireless parameters
optimization mainly includes the parameters such as the handoff, congestion control,
load equalization, DRBC, power control and HSPA, so as to reduce the consumption of
various resources.
Figure 1-3
High-load NE
Cell-level NEs involve false load rises and
real load rises.
Vertical
RF optimization
Neighbor optimization, only for cell-level NEs
RF neighbor optimization
Parameter optimization
Congestion control
Load balancing
DRBC
Part 3 corresponds to Chapter 4 of this guide, mainly introducing the high-load network
expansion. As shown in Figure 1-2, the high-load WCDMA network will be respectively
expanded in the three levels of cell, Node B and RNC. The content contains the
expansion analysis process, expansion criteria, expansion methods and implementation
details.
Reading guide: If you want to understand the high-load network optimization measures
given in this guide, please directly go to Chapter 3. If you want to understand the
expansion criteria and methods, please directly go to Chapter 4. Any question about the
counter or indicators, you can directly refer to Chapter 2 or understand by other means.
2.1
WCDMA NE Classification
The NE level of WCDMA system can be classified into the RAN cell, Node B, RNC and
CN. We mainly focus on the load monitoring and evaluation of the three NE levels of the
RAN cell, Node B and RNC. For all NEs, we need to consider various scenarios of
service behaviors, find the reasonable monitoring indicators and set the monitoring
threshold, so as to perform the monitoring, alarm and load control.
For the same service behavior, different NE has different monitoring parameters. As to
the air interface, we mainly study the factors such as the cell throughput, single-user
throughput, downlink power, uplink interference and downlink code resource. As to the
NodeB, we mainly consider the utilization of hardware resources.
1.
Cell level
The monitoring parameters of the NE in cell level mainly aim at the air interface,
such as the cell throughput, average throughput of HSDPA users, average
utilization of non-HSDPA carrier transmission power, average utilization of
non-HSDPA code resources and the uplink noise rise.
2.
Node B level
The NE in Node B level mainly monitors the utilization of Node B hardware
resources, such as the utilization of uplink/downlink Node B CE resources, and the
utilization of Iub interface uplink/downlink bandwidth.
3.
RNC level
The NE in RNC level mainly monitors the utilization of hardware resources,
including the CPU load (control plane), CE resource utilization (user plane) and
bandwidth utilization (interface board).
The RNC will also observe the traffic operation indicators of the existing network,
including the Erl, traffic, BHCA and the quantity of online users.
2.2
Expansion
Monitoring Indicator System 20110315.xls
Unlike the non-flexible resource and load of Node B and RNC, the cell-level load
monitoring indicators are the most complex, so following we will mainly introduce the
cell-level load monitoring indicators.
2.3
Key Indicators
2.3.1
Table 2-1
Channel
Spreading Code
HS-PDSCH
16
8 at least
HS-SCCH
128
E-AGCH
256
E-RGCH
128
CPICH
256
PCCPCH
256
SCCPCH
64
PICH
256
AICH
256
We can see that the maximum of available code resources of R99 service = 256 8 8
16 4 1 2 = 113. Because the quantity of code resources occupied by common
channel is fixed and small, usually we can ignore it for calculation.
So, when the utilization of cell code resources is very high, and even a congestion of
code resource occurs, we suggest you reduce the minimum of HSDPA code channel to
be 1.
2.3.2
acceptance threshold. When the predictive power is bigger than the acceptance
threshold, the system will reject all the requests of establishing connection. If there are
many requests of establishing connection, the predictive power deltaP will be large and it
is easy to refuse to accept.
2.3.3
Figure 2-1
10
From the figure you can see that, there is a non-linear relationship between the NodeB
uplink noise rise and uplink capacity (load). When the uplink capacity (load) reaches a
certain threshold, the noise rise will increase sharply. Therefore, the UMTS radio network
planning is based on certain uplink load planning. Generally the uplink load is designed to
be 50%, corresponding to 3db of noise rise. When the uplink load is too large, both the
system uplink coverage and performance will obviously deteriorate due to the sharp
noise rise
The indicator of cell uplink noise rise cannot be calculated directly from the network
management. It formula is defined as follows:
Cell uplink noise rise = Average value of cell carrier received power System noise floor
2.3.4
2.3.5
11
user experience, that is, user average download rate. When the user experience rate of
the HSDPA users is below expectations, we need to optimize and expand the network.
When the average experience rate of the HSDPA users cannot meet expectations,
except for the possible causes mentioned above that the network coverage is poor or the
transmission bandwidth is insufficient, there is another cause that too many users initiate
the data transmission at the same time. If the low HSDPA user rate is caused by too
many users initiating the data transmission at the same time, we need to optimize and
expand the network. HS-PDSCH is a shared physical channel, and the transmission
bandwidth is shared by all the HSDPA users. If too many users initiate the data
transmission at the same time, the real-time transmission rate of each HSDPA user will
reduce. Therefore, except for the indicator of HSDPA user real-time experience rate, the
system should also provide the indicator of real-time transmission HSDPA user quantity,
which is used to judge whether the low real-time transmission rate of each HSDPA user
is caused by too many HSDPA users initiating the data transmission at the same time.
The Average Throughput of HSDPA Single User is defined as follows:
Average throughput of HSDPA single user (Kbps) = Amount of user data confirmed by
HSDPA MAC/Data transmission time of HSDPA users
12
3.1
Figure 3-1
13
3.2
14
Figure 3-2
High-load NE
Cell-level NEs involve false load rises and
real load rises.
Vertical
RF optimization
Neighbor optimization, only for cell-level NEs
RF neighbor optimization
Parameter optimization
Congestion control
Load balancing
DRBC
15
4.1
Expansion Process
4.1.1
16
Figure 4-1
Yes
Cell-level monitoring,
analysis, and alarm
High-load network
performance
monitoring and
evaluation
NodeB-level
monitoring, analysis,
and alarm
Perform
optimization to
solve the problem
of high load
RNC-level monitoring,
analysis, and alarm
No
Yes
Cell expansion
Add carriers or power
amplifiers
Yes
NodeB expansion
Add BPC boards or
transmission resources
Yes
RNC expansion
Software: Add licenses
Hardware: Add RUB or
RCB boards
No
4.2
4.2.1
Cell Expansion
Among the three NEs, the WCDMA system cell is the NE closest to the actual users and
the minimum unit used to assess the network load. The cell load and performance level
directly affects the user experience, so the cell load monitoring and assessment will be
the key point in our daily monitoring and assessment, and the cell expansion is also the
core content of the WCDMA network expansion.
17
4.2.1.1
Figure 4-2
No
Low transmission
rate and
congestion
Yes
Resource utilization
evaluation: code resources
and power resources
No
Optimization
High-load decision
Yes
Expansion
The indicators of assessing the user experience are mainly the data user experience rate
and cell resource congestion level. The network resources mainly refer to the air interface
code resource and power resource. For details please refer to the cell indicators
mentioned in Section 2.2.
4.2.1.2
18
bigger. Therefore, the user experience of data service will also become the most
important factor to measure the 3G network load, and the best indicator to assess the
user experience of data service is the user download experience rate of data service.
According to the expansion principle of Focus on the user experience, we will regard
the HSDPA user average experience rate (throughput) as the core to assess the cell load,
and try to accurately assess the cell load by combining the air interface.
Each monitoring indicator of the cell load assessment has been set an expansion
indicator number. The expansion indicator SPI is a logical indicator, and the value can
only be 0 or 1. When the expansion indicator SPI reaches the threshold, the value will be
1, or else 0. We also provide corresponding expansion methods when each indicator
reaches the expansion threshold, for your reference.
Table 4-1
Expansion
Indicator
Indicator Name
No.
Alarm
Expansion
Threshold
Threshold
1 Mbps
512 Kbps
Expansion Method
Average
SPI1
Throughput of
HSDPA Single
HSPA+/Multi-carrier/add
User
NodeB
HSDPA cell
SPI2
average
100 MB
150 MB
60%
70%
60%
70%
6 dB
8 dB
throughput
Non-HSDPA code
SPI4
resource average
Multi-carrier/add NodeB
occupancy
Average
utilization of
SPI5
non-HSDPA
carrier transmit
Expand power
amplifier/add NodeB
power
SPI6
Multi-carrier/add NodeB
19
Admission
SPI8
rejection
Set to be a
proportion due to
fixed
limited downlink
value: 1
2%
Multi-carrier/add NodeB
code resources
Admission
SPI9
rejection
Set to be a
proportion duo to
fixed
limited downlink
value: 1
2%
Expand power
amplifier/add NodeB
power TCP
According to the threshold setting of the cell load monitoring indicator SPI and the cell
expansion assessment process, we can get the combination chart of the cell expansion
decision formula, as shown in Figure 4-3.
20
Figure 4-3
SPI8 SPI9 = 1
The cell has severe congestion
and user perception is bad; the
cell may be a high-load cell.
SPI SPI2 = 1
Yes
Yes
No
False load rise
Optimization
From above we can get the general formula of the high-load cell decision:
S_cell = SPI1 SPI2 + SPI4 SPI8 + SPI5 SPI9 + SPI6 (SPI4 + SPI5)
Formula description:
1.
2.
SPI1 SPI2 is mainly used to filter the high-load cell focusing on the data service,
that is, need to meet the requirements of low user rate and high cell throughput.
21
3.
SPI4 SPI8 + SPI5 SPI9 + SPI6 (SPI4 + SPI5) is mainly used to filter the
high-load cell focusing on the non-HSDPA service. The purpose of SPI1 SPI2 is to
perform mutual correction of two counters. Two SPIs meeting the criteria can
basically determine that the cell is in a high-load state.
SPI4 SPI8 means the average utilization of non-HSDPA code resources is
relatively high and the situation of refusing to accept is serious. If the average
utilization of non-HSDPA code resources is relatively high but there is no situation of
refusing to accept, it means that, although the load is high, it does not meet the
expansion criteria. If the situation of refusing to accept is serious but the average
utilization of non-HSDPA code resources is not high, it may be caused by the virtual
load rise due to improper resource allocation.
SPI5 SPI9 means the same as SPI4 SPI8.
SPI6 (SPI4 + SPI5) means at least two indicators meet the criteria. There are two
causes, one is that the uplink may be interfered, and the other is that the automatic
noise floor update is false. So we use the two indicators of the code resource and
power resource to correct, so as to ensure the cells we filtered are really the cells
with relatively high load.
4.
When S_cell > 0, it means that the cell enters a high-load state and needs to be
expanded, and we need to perform monitoring optimization and load assessment.
5.
The bigger value of S_cell means the heavier load of the current cell. The minimum
of S_cell is 0 and the maximum is 5.
4.2.1.3
4.2.1.3.1
22
the cell load assessment, when the indicator of average occupancy of non-HSDPA code
resources is used, it means the indicator of CS traffic is indirectly used too. The average
occupancy of non-HSDPA code resources not only reflects the occupancy of cell R99
code resources and the situation of refusing to accept, but also reflects the cell CS traffic
load level.
Figure 4-4
4.2.1.3.2
23
Figure 4-5
Relationship Between the Cell Carrier Transmit Power Utilization and TCP
Limited Proportion
4.2.1.3.3
4.2.1.3.4
24
need to monitor the HSDPA cell average throughput, and use the two indicators to
determine whether the network capacity needs to be expanded.
When the Average Throughput of HSDPA Single User is less than 512 Kbps, we need to
make the next-step decision of the capacity monitoring.
The HSDPA cell average throughput indicates the service volume of cell data
transmission. The HSDPA cell average throughput is too low may be because the
application layer flow is not enough or the cell coverage is poor. In this situation, we
should not perform the expansion. Therefore, we suggest considering the expansion
when the HSDPA cell average throughput > 150 MB.
In general, when the Average Throughput of HSDPA Single User is less than 512 Kbps
and the HSDPA cell average throughput is greater than 150 MB, the cell capacity should
be expanded.
4.2.1.3.5
4.2.1.4
Table 4-2
Monitoring
Monitoring Mode 1
Mode
Monitoring
Object
Monitoring
Granularity
Monitoring Mode 2
Hour
Hour
25
A week (7 24)
Monitoring
assessment.
Trigger
Condition
Expansion
Trigger
Condition
4.2.2
Sn = S_cell_1 + S_cell_2
+ S_cell_n (n = 7 24).
+ S_cell_n (n = 7 24).
expansion demand.
expansion demand.
4.2.2.1
26
The Node B CE resource load assessment is as shown in the table. An indicator number
SPI is set for each monitoring indicator. The expansion indicator SPI is a logical indicator
and its value can only be 0 or 1. When the indicator reaches the expansion threshold, the
value will be 1, or else 0. Meanwhile, we provide the expansion method corresponding to
each indicator reaching the expansion threshold. The expansion threshold and method
are as shown in Table 4-3.
Table 4-3
Expansion
Indicator
Indicator Name
No.
SPI11
Average utilization of
uplink NodeB CE resource
Alarm
Expansion
Expansion
Threshold
Threshold
Method
60%
70%
BPC board
Average utilization of
SPI12
downlink NodeB CE
60%
70%
80%
90%
80%%
90%
resource
SPI13
Maximum utilization of
uplink NodeB CE resource
Maximum utilization of
SPI14
downlink NodeB CE
resource
SPI15
SPI16
Expand the
Set as a
fixed
2%
value: 1
Set as a
fixed
2%
value: 1
Expand the
BPC board
Expand the
BPC board
Expand the
BPC board
Expand the
BPC board
Expand the
BPC board
According to the expansion threshold setting shown in Table 4-3, we use the expansion
decision formula to assess the Node B load and expansion demand.
S_nodeb_CE = (SPI11 + SPI3) SPI15 + (SPI12 + SPI4) SPI16
Formula description:
1.
27
2.
(SPI11+SPI3) SPI15 is mainly used to filter the uplink CE high-load cell, indicating
that the uplink average or maximum utilization is relatively high, and meanwhile the
uplink CE refuses to accept. If there is only high utilization but no CE admission
rejection, it means the indicator does not reach the expansion threshold. If there is
only admission rejection but no high utilization, it may be caused by uneven
distribution of resources.
3.
When S_nodeb_CE > 0, it means the NodeB enters a high-load state and falls into our
monitoring scope for monitoring optimization and expansion assessment.
Greater value of S_nodeb_CE means greater Node B expansion demand. The minimum
of S_node_CE is 0 and the maximum can be 2.
4.2.2.2
Figure 4-6
28
Figure 4-7
4.2.2.3
Table 4-4
Monitoring
Monitoring Mode 1
Mode
Monitoring
Object
Monitoring
Granularity
Monitoring Mode 2
Hour
Hour
A week (7 N: N refers to the fixed
Monitoring
Cycle
A week (7 24)
29
Monitoring
Monitoring Mode 1
Mode
Monitoring
assessment.
Trigger
Condition
Expansion
Trigger
Condition
4.2.3
Monitoring Mode 2
4.2.3.1
30
your reference when each indicator reaches the expansion threshold. The expansion
threshold and methods are as shown in Table 4-5.
Table 4-5
Expansion
Indicator
Indicator Name
No.
Alarm
Expansion
Expansion
Threshold
Threshold
Method
80%
90%
Maximum forward
SPI17
SPI18
accepted bandwidth
proportion of IP
Expand the
Maximum backward
transmission.
accepted bandwidth
80%
90%
60%
70%
60%
70%
80%
90%
80%
90%
60%
70%
60%
70%
proportion of IP
SPI19
SPI20
accepted bandwidth
proportion of IP
Maximum forward
SPI21
accepted bandwidth
proportion of ATM
Maximum backward
SPI22
accepted bandwidth
proportion of ATM
Average forward accepted
SPI23
bandwidth proportion of
ATM
Average backward
SPI24
accepted bandwidth
proportion of ATM
Expand the
transmission.
Expand the
transmission.
Expand the
transmission.
Expand the
transmission.
Expand the
transmission.
Expand the
transmission.
For SPI1724 in the above table, we need to start the measurement on the OMCB for at
least 1 week, and then close.
According to the expansion threshold setting in the above table, we can use the
expansion decision formula to assess the IUB transmission load and the expansion
demand, as shown below:
31
4.2.3.2
4.2.3.3
Table 4-6
Monitoring
Monitoring Mode 1
Mode
Monitoring
Object
Monitoring
Granularity
Monitoring Mode 2
Hour
Hour
A week (7 N: N refers to the fixed
Monitoring
Cycle
A week (7 24)
32
Monitoring
Monitoring Mode 1
Mode
Monitoring
assessment.
Trigger
Condition
Sn = S_trans_1 +
S_trans_2 + S_trans_n (n =
Expansion
7 24 hrs).
Trigger
Condition
4.2.4
Monitoring Mode 2
RNC Expansion
The RNC is at the highest level of the radio network, responsible for the work scheduling
and processing of NodeBs and cells in its charge.
In the perspective of software and hardware constraints, the RNC expansion can be
divided into RNC hardware expansion and RNC software expansion.
RNC hardware expansion refers to the expansion triggered by the constraint of RNC
hardware processing capability. The expansion can be performed by increasing the
hardware boards.
33
RNC software expansion means that the software license is close to or reaches the
committed capacity and thus the expansion is triggered. The expansion can be
performed by increasing the software licenses.
The RNC hardware expansion and software expansion may occur at the same time or
occur respectively. Their association depends on the project hardware configuration
mode and the software quotation mode. We need to monitor each project respectively
according to related parameters of the RNC hardware expansion and RNC software
expansion.
In the perspective of modeling configuration, the RNC expansion can be divided into
modeling expansion and non-modeling expansion.
The modeling expansion means that the RNC hardware and software use the modeling
configuration quotation. The expansion will be performed in the unit of model.
The non-modeling expansion means that the RNC hardware and software do not use the
modeling configuration quotation. The expansion will be performed in the unit of board.
4.2.4.1
4.2.4.1.1
Rack: The rack expansion depends on the quantity of frame. Each 4 frames need 1
rack.
Frame: including the control frame, resource frame and exchange frame
The expansion of control frame depends on the increase amount of the control
plane processing board RCB. When there is the exchange frame, the main
control frame can be inserted 6 RCBs, and the rest can be inserted 14. When
34
there is no exchange frame, the main control frame can be inserted 2 RCBs
and the rest can be inserted 14.
The expansion of resource frame depends on the increase amount of the user
plane processing board RUB and the interface board. Each resource frame
can be inserted 15 RUBs and interface boards.
For the exchange frame, the system configures 1 exchange frame at most.
When there are more than 2 resource frames, the exchange frame must be
configured. When there are 2 or less resource frames, it is defaulted and
recommended to configure the exchange frame.
Common board: including the global processing board and system exchange board
Global processing boards: including ROMB, CLKG and SBCX. The quantity is
a fixed configuration and has nothing to do with the capacity, so usually there is
no issue of expansion. If no active and standby boards are divided at the
beginning, later we need to expand them to be active and standby according to
the operations requirement.
System exchange boards: including THUB, GUIM, UIMC, PSN and GLI.
Configuring a pair of THUB for the whole RNC is a fixed configuration. A pair of
GUIM is configured for each resource frame. A pair of UIMC is configured for
each control frame or exchange frame. A pair of PSN is configured for each
exchange frame. A pair of GLI is configured for every 2 resource frames.
ii.
NodeB quantity
35
iii.
Cell quantity
The monitoring indicators of the hardware expansion of RNC capacity hardware resource
are as shown in Table 4-7.
Table 4-7
Indicator
Indicator Name
No.
SPI31
SPI32
Average utilization of
RUP CE resources
Maximum utilization of
RUP CE resources
Monitoring
Expansion
Expansion
Threshold
Threshold
Method
60%
70%
80%
90%
SPI33
60%
70%
SPI34
80%
90%
NodeB quantity
140/pair of RCB
Cell quantity
420/pair of RCB
Expand the
RUB board.
Expand the
RUB board.
Expand the
RCB board.
Expand the
RCB board.
Expand the
RCB board.
Expand the
RCB board.
For the NodeB quantity and cell quantity, we do not set the monitoring counter. When
expand the NodeB, we need to assess whether the RCB needs to be expanded.
For the utilization of RUB CE resources and the load of RCB CPU, we need to set the
monitoring indicators.
An expansion indicator number (SPI3134) is set for each monitoring indicator, and the
value can only be 0 or 1. When the indicator reaches the expansion threshold, the value
will be 1, or else 0.
36
According to the expansion threshold setting in the table, we can assess the RNC load
and expansion demand by the expansion decision formula, as shown below:
S_hard_Ctrl = SPI31 (1 + SPI32)
S_hard_User = SPI33 (1 + SPI34)
Formula description:
S_hard is the RNC expansion index, and the value can be 0, 1 and 2.
When S_hard = 0, it means neither the peak nor average value meets the criteria. So we
do not need to expand.
When S_hard = 1, it means the average value meets the criteria but the peak does not,
and the RNC enters a high-load state. So we need to expand the control plane or the
user plane.
When S_hard = 2, it means both the peak and average value meet the criteria, and the
expansion is urgent.
Except for the monitoring indicators mentioned above, we can also set some observation
indicators to observe the actual network service state when the hardware is close to or
reaches the expansion threshold, as shown in Table 4-8.
Table 4-8
Observation Indicator
Related Monitoring
Name
Indicator
Affected Board
BHCA
SPI33/SPI34
RCB board
CS traffic
SPI31/SPI32
RUB board
PS flow
SPI31/SPI32
RUB board
SPI31/SPI32/SPI33/SPI34
Capacity
37
2.
3.
For example, in a Unicom project, the Iu/Iub interfaces in many provinces share the
IP interface board in the beginning, later it is required that the interface boards of
Iu/Iub interfaces should be separated. Therefore, we need to separately expand the
interface boards without changing the capacity hardware. This kind of expansion is
resulted from the operators requirement and does not need any expansion
foundation. We just need to re-calculate the flow of each interface after separation.
4.
5.
For example, the ATM interface boards are used previously, now we need to
increase the IP interface boards because the network develops to the all-IP
technology. This kind of expansion is resulted from the operators requirement and
does not need any expansion foundation. We just need to re-calculate according to
the new interface board algorithm.
6.
7.
Many kinds of interface boards are related to the quantity of NEs and ports. For
example, the interface boards will be increased by increasing the NodeB quantity,
increasing the E1 quantity for each NodeB, increasing the Iur quantity, or increasing
the Iu-flex function. In this case, we need to re-calculate the quantity of interface
boards according to the new NodeB/port demands.
8.
9.
For Case 2 to Case 5 mentioned above, we do not need to set the monitoring indicators,
and perform the expansion correspondingly when it is necessary. For Case 1, we need to
monitor the bandwidth usage of the interface boards. The monitoring parameters are as
shown in Table 4-9.
38
Table 4-9
4.2.4.1.2
Monitoring
Expansion
Expansion
Threshold
Threshold
Method
Expand the
70%
80%
ATM interface
board
Expand the
70%
80%
ATM interface
board
70%
80%
70%
80%
70%
90%
50%
90%
Expand the IP
interface board
Expand the IP
interface board
Expand the IP
interface board
Expand the IP
interface board
39
In some projects, some features are quoted in the unit of NodeBs CE. So we need to
monitor the CE operating indicators of all the NodeBs, and should trigger the software
expansion when the indicators exceed the quotation unit. (For the monitoring indicators
please refer to CE Monitoring Indicators of NodeB)
Software expansion in the dimensions of Erl and flow:
In some projects, some features are quoted in the unit of Erl and flow. So we need to
monitor the indicators of Erl and flow, and should trigger the software expansion when
the indicators exceed the quotation unit. (For the monitoring indicators, please refer to
RNC Hardware Expansion Observation Indicators.)
For example, in one project, the RNC hardware configuration is 250 Mbps and software
is quoted 100 Mbps. When the flow indicator of existing network exceeds 100 Mbps, we
need to expand the software license, that is, to quote the software feature for the
increased flow. When the flow is almost 250 Mbps, we need to perform the hardware
expansion.
4.2.4.1.3
40
interface board are monitored to be load-rising, we can also expand the RUB or interface
board separately.
If the modeling method is used, the control plane and user plane boards need to be
linked according to the model. In some projects, the interface board is also contained in
the model, so we need to link the control plane, user plane and interface board. For
example, in one project, if the RCP CPU is monitored to be a little bit high-load but other
indicators are normal, we need to expand the whole model to the upper capacity level but
not only to expand the RCB.
4.2.4.2
4.2.4.3
Table 4-10
Monitoring
Object
Monitoring
Granularity
Monitoring
Cycle
Monitoring
Trigger
Condition
Implementation Rule 2
Hour
Hour
A week (7 24)
If in 1 week, S_hard 1, N 3,
assessment.
assessment.
41
Expansion
Trigger
Condition
If in 1 week, S_hard 1, N 3,
42