Академический Документы
Профессиональный Документы
Культура Документы
Issue
02
Date
2013-03-30
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.
Website:
http://www.huawei.com
Email:
support@huawei.com
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
For definitions of the man-machine language (MML) commands, parameters, alarms, and performance
counters mentioned in this document, see the "Operation and Maintenance" part in 3900 Series LTE
eNodeB Product Documentation.
Intended Audience
This document is intended for:
Field engineers
Organization
This document describes the principles and methods of capacity monitoring.
02 (2013-03-30)
Chapter
Description
1 "Overview"
2 "General Capacity
Monitoring"
3 "Resource Allocation
Problem Identification"
ii
eRAN3.0
Capacity Monitoring Guide
Chapter
Description
A "Appendix"
Change History
This section describes changes in each issue of this document.
02 (2013-03-30)
This is the second official release.
The document name has been changed from Capacity Monitoring Guidelines to Capacity
Monitoring Guide.
Compared with 01 (2012-12-30), this issue includes an appendix and the changes described in
the following table.
Section
Change Description
1 "Overview"
01 (2012-12-30)
This is the first official release.
02 (2013-03-30)
iii
eRAN3.0
Capacity Monitoring Guide
Contents
Contents
About This Document .................................................................................................................... ii
1 Overview......................................................................................................................................... 1
1.1 Capacity Monitoring Methods.......................................................................................................................... 1
1.2 Network Resources .......................................................................................................................................... 1
1.2.1 eNodeB Resources .................................................................................................................................. 2
1.2.2 Cell Resources ........................................................................................................................................ 2
1.3 General Process ................................................................................................................................................ 3
02 (2013-03-30)
iv
eRAN3.0
Capacity Monitoring Guide
Contents
A Appendix ..................................................................................................................................... 19
A.1 Querying the Maximum Number of UEs Supported by the PUCCH ............................................................ 19
A.2 Querying the Maximum Number of UEs Supported by SRS Resources....................................................... 20
A.3 Querying the Maximum Number of CCEs .................................................................................................... 23
A.4 Querying Ethernet Port Traffic ...................................................................................................................... 24
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
1 Overview
Overview
This chapter provides an introduction to capacity monitoring methods, network resources, and
a general process of capacity monitoring and handling.
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
1 Overview
Paging resources
If the actual number of paging messages exceeds the paging capacity, the eNodeB will
be unable to process all the paging messages and user experience will be affected.
Control-board CPU
If the load on the main control board exceeds the CPU capacity, severe problems may
occur, for example, the deterioration of key performance indicators (KPIs).
LBBP CPU
If the load on an LTE baseband process unit (LBBP) exceeds the CPU capacity, severe
problems may occur, for example, the deterioration of KPIs.
Ethernet ports
If the load on an Ethernet port exceeds the bandwidth configured for the port, exceptions
may occur (for example, packets may be lost), affecting user experience.
PRBs
The usage of physical resource blocks (PRBs) reflects the uplink and downlink
bandwidth consumed on the air interface.
PUCCH resources
Insufficient physical uplink control channel (PUCCH) resources have negative impacts
on the following:
SRS resources
Sounding reference signal (SRS) resources are allocated to UEs for network access. If an
LBBPd is used, UEs can access the network even when SRS resources are not allocated
to them.
If SRS resources are insufficient, the eNodeB cannot obtain accurate measurement
information, which then affects efficient use of radio resources.
PRACH resources
Physical random access channel (PRACH) resources are random access preambles
carried on the PRACH.
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
1 Overview
If PRACH resources are insufficient for handling all access attempts, access delays are
prolonged or even access attempts fail.
PDCCH resources
If physical downlink control channel (PDCCH) resources are limited, scheduling delays
are long and user experience is affected.
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
1 Overview
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
1 Overview
Some indicators need to be used with others in order to locate resource bottlenecks. For
example, the connected user license usage must be used with the control-board CPU usage;
the PDCCH resource usage must be used with the uplink or downlink PRB usage.
For details about capacity monitoring, see chapter 2 "General Capacity Monitoring" or contact
Huawei technical support.
The process shown in Figure 1-2 is applicable in most cases. If the resource overload is not
due to increased traffic but due to other factors, identify resource allocation problems by
referring to chapter 3 "Resource Allocation Problem Identification."
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
2.1 Introduction
For monitoring resource consumption on the network, counters and corresponding limits are
defined in the eNodeB. For better monitoring, busy hours should be defined; it is
recommended that the period with maximum resource consumption be defined as busy hours.
Table 2-1, Table 2-2, Table 2-3, and Table 2-4 describe the counters related to radio resources,
device resources, transport resources, and reactive KPIs, respectively.
Table 2-1 Counters related to radio resources
02 (2013-03-30)
Performance Counter
Description
L.Traffic.User.Avg
L.Traffic.User.Max
L.Traffic.User.Ulsync.Avg
L.ChMeas.PRB.UL.Used.Avg
L.ChMeas.
PRB.DL.Used.Avg
L.ChMeas.PRB.PUCCH.Avg
L.RA.GrpA.Att
L.RA.GrpB.Att
L.RA.Dedicate.Att
L.ChMeas.CCE.CommUsed
L.ChMeas.CCE.ULUsed
eRAN3.0
Capacity Monitoring Guide
Performance Counter
Description
L.ChMeas.CCE.DLUsed
L.Paging.S1.Rx
L.Paging.Dis.Num
Description
VS.Board.CPUload.Max
VS.Board.CPUload.Mean
VS.Board.CPULoad.Cumulati
veHighloadCount
Description
VS.FEGE.TxMaxSpeed
VS.FEGE.TxMeanSpeed
VS.FEGE.RxMaxSpeed
VS.FEGE.RxMeanSpeed
VS.RscGroup.TxPkts
VS.RscGroup.TxDropPkts
VS.RscGroup.TxMaxSpeed
VS.RscGroup.TxMeanSpeed
02 (2013-03-30)
Performance Counter
Description
L.RRC.ConnReq.Att
eRAN3.0
Capacity Monitoring Guide
Performance Counter
Description
L.RRC.ConnReq.Succ
L.E-RAB.AttEst
L.E-RAB.SuccEst
L.E-RAB.AbnormRel
L.E-RAB.NormRel
If the LMPT CPU usage is lower than 60%, you are advised to increase the licensed
limit.
If the LMPT CPU usage is greater than or equal to 60%, adding more users will result in
LMPT CPU overload, and you are advised to add an eNodeB.
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
Uplink PRB usage = Average number of used uplink PRBs during busy hours (indicated
by L.ChMeas.PRB.UL.Used.Avg)/Total number of uplink PRBs x 100%
Downlink PRB usage = Average number of used downlink PRBs during busy hours
(indicated by L.ChMeas.PRB.DL.Used.Avg)/Total number of downlink PRBs x 100%
Decrease in cell and UE throughput: If CQI resources are insufficient or limited, the
eNodeB selects a CQI reporting period of 40 ms for UEs, which results in less accurate
CQIs and lower spectral efficiency. In addition, these UEs cannot be chosen to perform
frequency selective scheduling.
Increase in uplink scheduling delay: If SRI resources are insufficient or limited, the
eNodeB selects an SRI period of 20 ms for UEs, which results in longer uplink
scheduling delays for these UEs.
02 (2013-03-30)
eRAN3.0
Capacity Monitoring Guide
Prolong the SRS period until it reaches the maximum SRS subframe configuration by
running the following command:
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=OFF, UserSrsPeriodCfg=ms40;
Turn on the SRS period adaptation switch by running the following command:
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=ON;
02 (2013-03-30)
10
eRAN3.0
Capacity Monitoring Guide
Random preamble usage = [Number of times that random preambles in group A are
received during a busy hour (indicated by L.RA.GrpA.Att) + Number of times that
random preambles in group B are received during this hour (indicated by
L.RA.GrpB.Att)]/3600/100 x 100%
Dedicated preamble usage = Number of times that dedicated preambles are received
during busy hours (indicated by L.RA.Dedicate.Att)/3600/100 x 100%
If the percentage of the number of times that dedicated preambles are received exceeds 75%
during busy hours, you are advised to enable reuse of dedicated preambles between UEs by
running the following command:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch=MaksIdxSwitch-1;
This helps reduce the probability of UEs initiating contention-based random access in the case
of dedicated preamble insufficiencies and therefore helps reduce the access delay.
If PDCCH symbols are excessive, which indicates that the usage of PDCCH CCEs is low,
the resources that can be used by the PDSCH decreases. This will also result in low
spectral efficiency.
02 (2013-03-30)
11
eRAN3.0
Capacity Monitoring Guide
Number of paging messages discarded over the Uu interface during busy hours
(indicated by L.Paging.Dis.Num)
02 (2013-03-30)
In an eNodeB, the percentage of the number of paging messages received by the eNodeB
over the S1 interface exceeds 60% of the eNodeB paging capacity.
In an eNodeB, more than 1500 paging messages from the mobility management entity
(MME) to UEs are discarded during busy hours.
12
eRAN3.0
Capacity Monitoring Guide
Measurement Unit
Description
Signaling-related
Measurement related to
RRC setup
Measurement related to
E-RAB establish
Measurement related to
E-RAB release
Measurement related to
Intra eRan HOIN
Measurement related to
MCS
Measurement related to
MAC
Service-related
Operators can use the information described in Table 2-5 to determine whether KPI
deterioration is caused by insufficient control-board CPU processing capability or poor radio
conditions. The evaluation is as follows:
If the MCS measurement and initial-transmission failure measurement indicate that the
channel quality is poor, KPI deterioration may not be caused by control-board CPU
overload but by deterioration in channel quality.
If the KPIs deteriorate and the control-board CPU usage exceeds the expansion threshold,
you are advised to perform capacity expansion according to section 2.9.3 "Suggested
Measures."
02 (2013-03-30)
Number of times that the control-board CPU usage exceeds the threshold during busy
hours (indicated by VS.Board.CPULoad.CumulativeHighloadCount)
13
eRAN3.0
Capacity Monitoring Guide
The percentage of the number of times that the control-board CPU usage exceeds 85%
(VS.Board.CPULoad.CumulativeHighloadCount/3600) exceeds 20% in one busy hour
for x consecutive days (x is configurable).
If the control-board CPU is overloaded, you are advised to perform capacity expansion on the
eNodeB control plane as follows:
1.
2.
If the main control board is an LMPT, replace with the LMPT with a UMPT.
3.
Add an eNodeB, and connect it to the evolved packet core (EPC) through a new S1
interface.
Number of times that the LBBP CPU usage exceeds the threshold during busy hours
(indicated by VS.Board.CPULoad.CumulativeHighloadCount)
The average LBBP CPU usage (VS.Board.CPUload.Mean) exceeds 75% in one busy
hour for x consecutive days (x is configurable).
The percentage of the number of times that the LBBP CPU usage exceeds 85%
(VS.Board.CPULoad.CumulativeHighloadCount/3600) is more than 20% in one busy
hour for x consecutive days (x is configurable).
If the LBBP CPU is overloaded, you are advised to perform capacity expansion on the
eNodeB user plane as follows:
02 (2013-03-30)
Add an LBBP to share the network load, and then determine whether to move the
existing cells or add new cells based on the number of UEs. The capacity expansion
methods are as follows:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14
eRAN3.0
Capacity Monitoring Guide
If the radio resources are sufficient, move a cell from the existing LBBP to the new
LBBP.
If the radio resources are insufficient, set up new cells on the new LBBP.
If the eNodeB has multiple LBBPs and one of them is overloaded, move cells from the
overloaded LBBP to an LBBP with a lighter load.
NOTE
If the eNodeB already has a maximum of six LBBPs and more LBBPs are required, add
an eNodeB.
The proportion of the average transmission rate to the configured bandwidth during busy
hours exceeds 4/5 in 80% of monitoring periods throughout an entire week.
The proportion of the maximum transmission rate to the configured bandwidth during
busy hours exceeds 9/10 in 10% of monitoring periods throughout an entire week.
The packet loss rate exceeds 0.05% during busy hours for a whole week. The packet loss
rate is the ratio of VS.RscGroup.TxDropPkts to RscGroup.TxPkts in a specific period.
When a transport resource group is congested, you are advised to adjust the bandwidth
configuration for the transport resource group on the eNodeB. The following is an example
command:
MOD RSCGRP: CN=0, SRN=0, SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=0,
RU=KBPS, TXBW=15000, RXBW=20000;
02 (2013-03-30)
15
eRAN3.0
Capacity Monitoring Guide
If the problem persists after the bandwidth adjustment, you are advised to perform capacity
expansion on the transport resource group.
02 (2013-03-30)
16
eRAN3.0
Capacity Monitoring Guide
02 (2013-03-30)
17
eRAN3.0
Capacity Monitoring Guide
The fault location procedure begins with the identification of abnormal KPIs, followed up by
selecting and performing a KPI analysis on the top N cells.
Cell congestion mainly results from insufficient system resources. Bottlenecks can be
detected by analyzing the access KPIs.
02 (2013-03-30)
18
eRAN3.0
Capacity Monitoring Guide
Appendix
If the value is PucchSwitch:On, query the maximum number of UEs supported by CQI
resources in Table A-1.
Step 2 Run the LST CQIADAPTIVECFG command to query the value of the CQI period
adaptive switch parameter.
If the value is On, query the maximum number of UEs supported by CQI resources in
Table A-1.
02 (2013-03-30)
The Delta shift parameter specifies the interval between cyclic shifts used for the
PUCCH. Its value can be queried by running the LST PUCCHCFG command.
The CQI RB number parameter specifies the number of PRBs allocated for CQIs. Its
value can be queried by running the LST PUCCHCFG command.
The User CQI period config parameter specifies the CQI reporting period. Its value can
be queried by running the LST CQIADAPTIVECFG command.
19
eRAN3.0
Capacity Monitoring Guide
5 MHz
200
10 MHz
400
15 MHz
400
20 MHz
400
----End
Step 2 Run the LST SRSCFG command to query the value of the SRS subframe configuration
parameter, and then query the maximum number of UEs supported by SRS resources based
on Table A-3.
Table A-2 Maximum number of UEs supported by SRS resources (SrsSubframeRecfSwitch set
to On)
02 (2013-03-30)
Channel Bandwidth
(Configurable)
Number of SRS
Subframes per Frame
5 MHz
Automatically adjusted
in the range of 1 to 10
200
10 MHz
Automatically adjusted
in the range of 1 to 10
15 MHz
Automatically adjusted
in the range of 1 to 10
400
20 MHz
Automatically adjusted
in the range of 1 to 10
400
20
eRAN3.0
Capacity Monitoring Guide
Table A-3 Maximum number of UEs supported by SRS resources (SrsSubframeRecfSwitch set
to Off)
CP Length
(Configurable)
Channel
Bandwidth
(Configurable)
SRS Subframe
Position
(Configurable)
Number of SRS
Subframes per
Frame
Maximum
Number of
UEs
Normal CP
5 MHz
9, 10, 11, 12
3, 4, 5, 6
16
7, 8
40
1, 2
56
13
120
14
152
10
200
9, 10, 11, 12
12
3, 4, 5, 6
24
7, 8
120
1, 2
168
13
264
14
312
10
400
9, 10, 11, 12
15
3, 4, 5, 6
30
7, 8
60
1, 2
120
13
240
14
300
10
400
9, 10, 11, 12
15
3, 4, 5, 6
30
7, 8
90
1, 2
120
13
240
14
300
10
400
10 MHz
15 MHz
20 MHz
02 (2013-03-30)
21
eRAN3.0
Capacity Monitoring Guide
CP Length
(Configurable)
Channel
Bandwidth
(Configurable)
SRS Subframe
Position
(Configurable)
Number of SRS
Subframes per
Frame
Maximum
Number of
UEs
Extended CP
5 MHz
9, 10, 11, 12
3, 4, 5, 6
30
7, 8
78
1, 2
102
13
150
14
174
10
200
9, 10, 11, 12
10
3, 4, 5, 6
50
7, 8
130
1, 2
170
13
250
14
290
10
370
9, 10, 11, 12
20
3, 4, 5, 6
40
7, 8
120
1, 2
160
13
280
14
360
10
400
9, 10, 11, 12
22
3, 4, 5, 6
67
7, 8
157
1, 2
202
13
292
14
337
10
400
10 MHz
15 MHz
20 MHz
----End
02 (2013-03-30)
22
eRAN3.0
Capacity Monitoring Guide
If the value is On, query the maximum number of CCEs based on Table A-4.
Step 2 Run the LST PHICHCFG command to the query the value of the PHICH resource
parameter.
The value can be ONE_SIXTH, HALF, and ONE, TWO, which are the same as the values
of Ng in Table A-4. The maximum number of CCEs can be queried based on Ng in Table A-4.
Table A-4 Maximum number of CCEs
Channel
Bandwidth
Ng
(Configurable)
(Configurable)
5 MHz
10 MHz
15 MHz
20 MHz
1/6
13
21
1/2
12
21
12
20
11
19
1/6
10
26
43
1/2
26
42
25
41
23
39
1/6
15
40
65
1/2
14
39
64
12
37
62
34
59
1/6
20
54
87
1/2
19
52
86
17
50
84
13
46
80
PDCCH
Symbol
Number
Adjust
Switch = On
21
43
65
87
----End
02 (2013-03-30)
23
eRAN3.0
Capacity Monitoring Guide
If LR Switch is set to Disable, set the denominator (S1 allocated bandwidth) in the
following formulas to 1 GHz for the UMPT or 360 MHz for the LMPT:
If LR Switch is set to Disable, set the denominator (S1 allocated bandwidth) in the
following formulas to 1 GHz for the UMPT or 540 MHz for the LMPT:
If LR Switch is set to Enable, set the denominator (S1 allocated bandwidth) in the
following formulas to the value of UL Committed Information Rate:
If LR Switch is set to Enable, set the denominator (S1 allocated bandwidth) in the
following formulas to the value of DL Committed Information Rate:
NOTE
The main control board type (UMPT or LMPT) is specified by the Board Type parameter and can be
queried by running the DSP BRD command. Because many types of boards exist in the baseband unit
(BBU), you must search all boards for the main control board.
02 (2013-03-30)
24