Professional Documents
Culture Documents
TABLE OF CONTENTS
1 Overview
1.1 Procedure of Monitoring Wireless Network Resources
1.1 Overview of Wireless Network Resources
1 Overview
Wireless network resource monitoring is an important job in the network maintenance phase. With the increase in the number of users and service applications,
especially with the rapid development of wireless broadband data services, the network load will continue to rise. When the network load reaches a certain level,
congestion occurs in network resources and network performance deteriorates, which ultimately affect users service experience. To satisfy service development
requirements, it is required to monitor the load and performance of the entire network in real time, and optimize or expand the capacity for any NE whose load exceeds
the threshold. Thus, the network carrier achieves good user experience and keeps a competitive advantage of the network.
Discover indicators to be handled through network monitoring, and adjust loads first through resource balancing and function commissioning. If you fail to satisfy
requirements after resource balancing and optimization, expand the corresponding resources.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 2 of 27
Using counters of the UR13 network management system as a reference, this document describes load indicators and suggestions for expansion thresholds in ZTEs
GSM wireless network.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 3 of 27
Monitoring
Indicator Formula Threshold
Yellow Red
Wireless Pre- Pre-
Resource Indicator alarm alarm
Erl per SDCCH C901080005/Gr/C901080001 0.7 0.9
channel
SDCCH SDCCH C901250003/ C901250001 1% 2%
channel congestion ratio
((C901280040+C901280066+C901280099)*0.2354/Gr+(C901640007+2* 55% 70%
CCCH channel (C901640008+C901640009+C901640010+C901640011))*0.2354/Gr/4)/9*Number of
utilization rate CCCH channels
Percentage of C901640005 50% 70%
PCH block
resources used
CCCH Paging message (C901640001+C901640002)/C901640007 1% 5%
channel congestion ratio
Erl per TCH (C901080015+C901080023)/Gr/(C901080009+C901080028+C901080019) 0.7 0.9
channel
TCH congestion (C901260022+C901260071+C901270022+C901270071)/ 2% 5%
TCH channel ratio (C901260020+C901260069+C901270020+C901270069)
PDCH channel C901040017/ C901040003 80% 95%
utilization rate
Uplink PDCH (C901190016+C901190039+C901190065+C901200016+C901200039+C901200065)/ 1% 3%
congestion ratio (C901190001+C901190036+C901190062+C901200001+C901200036+C901200062)
PDCH Downlink PDCH (C901170008+C901170024+C901170037+C901180008+C901180024+C901180037)/ 1% 3%
channel congestion ratio (C901170001+C901170021+C901170034+C901180001+C901180021+C901180034)
The SDCCH channel is a dedicated channel used to set up the connection between an MS and the network. For example, before the TCH channel is allocated, the
SDCCH channel is used to transfer system signaling messages, receive and send short messages, and perform location updates during the call setup process. Since
service traffic on the SDCCH channel is low, the TCH channel is not required. Service traffic on the SDCCH channel is 1/8 of the traffic on the TCH channel. The
SDCCH channel is divided as follows:
2. SDCCH/4: Stand-Alone dedicated control channel combined with the CCCH channel.
To monitor the utilization rate of SDCCH channel resources in the network, observe the following two indicators:
Counter ID Description
C901080005 SDCCH busy time
C901080001 Average number of available SDCCH
C901250001 Number of SDCCH seizure attempts for assignment
C901250003 Number of SDCCH seizure failure for assignment
Granularity of collecting statistics on the background OMM. Unit:
Gr seconds.
Table 2-3 Monitoring Thresholds for the SDCCH Channel Utilization Rate
When the yellow pre-alarm threshold is exceeded, you need to enable SDCCH dynamic conversion feature ZGB-03-02-003 Dynamic Configuration of SDCCH to
increase SDCCH channels. When the red pre-alarm threshold is exceeded, you need to expand SDCCH channels immediately.
The Common Control Channel(CCCH) serves all mobile stations in the cell. On its downlink direction, PCH and AGCH channels broadcast paging requests and assign
dedicated channels. On its uplink direction, RACH channels transmit request messages for dedicated channels. AGCH channels are used for immediate assignment
in the CS domain and the PS domain. When a user acts as the calling party or the called party, performs a location update, receives or sends a short message, one
immediate assignment in the CS domain will be triggered. One immediate assignment in the PS domain means one TBF setup process. AGCH channels and PCH
channels share CCCH channel resources. In one cell, the capacity of one CCCH channel is fixed. If CCCH channel resources inside the cell are fixed, the rapid
increase of data services will result in congestion of AGCH channels or PCH channels. When AGCH channels are congested, even if traffic channels (TCH and
PDCH) are idle, user access still fail, so network access performance will be affected. If PCH channels are congested, network paging performance will decrease.
Since data services are real-time, online and interactive, they occupy more AGCH channel resources. The more interactive a data service is, the greater impact and
requirements it will impose upon the AGCH channel. Therefore, with the continuous increase of traffic, higher requirements are imposed upon the capacity of CCCH
channels. If the load of CCCH channels still exceeds the configured channel number after optimization, CCCH channels should be expanded.
Downlink CCCH channels are shared by PCH channels and AGCH channels. PCH channels are used for message paging, while AGCH channels are used for
immediate assignment of messages in voice and data services. Suppose that one CCCH channel is configured on the cell level with the granularity of 15 minutes,
traffic of the CCCH channel is calculated as follows:
Number of occupied AGCH channels = (CS Immediate assignment messages + PS Immediate assignment messages) * 0.2354/900
Number of occupied PCH channels = (One-time paging times * (1 + 2 * Multi-retransmission ratio ) + (PS paging times) *0.2354/900/4
Load of cell-level CCCH channels = (Number of occupied PCH channels + Number of occupied AGCH channels)/9
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 4 of 27
(Note: The number of paging-occupied channels includes PS paging messages when the paging queue is full and there is no retransmission for the second time.
Before calculating the number of paging-occupied channels, make sure that in system settings the TMSI is used in the first paging, the IMSI is used in retransmission,
and paging messages are not automatically retransmitted on the air interface. )
Therefore, the monitoring indicator for CCCH channel resources is calculated as follows:
((C901280040+C901280066+C901280099)*0.2354/Gr+(C901640007+2*(C901640008+C901640009+C901640010+C901640011))*0.2354/Gr/4)/9*Number of CCCH
channels
Counter ID Description
C901280040 Number of IMMEDIATE ASSIGN COMMAND messages
C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages
C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages
C901640007 Number of paging messages retransmitted zero times
C901640008 Number of paging messages retransmitted one times
C901640009 Number of paging messages retransmitted two times
C901640010 Number of paging messages retransmitted three times
C901640011 Numbers of paging messages retransmitted four times
Granularity of collecting statistics on the background OMM. Unit:
Gr seconds.
PCH channels are used to send paging messages on the downlink. To monitor PCH channel resources separately, check the following two indicators:
Counter ID Description
C901640005 The percentage of PCH Blocks validly used
C901640001 Number of PS paging message discarded due to full of the queue
C901640002 Number of CS paging message discarded due to full of the queue
C901640007 Number of paging messages retransmitted zero times
For pre-alarm thresholds for the cell-level CCCH channel load, refer to Table 2-6.
When the yellow pre-alarm threshold is exceeded, you need to expand CCCH channels. When the red pre-alarm threshold is exceeded, you should expand CCCH
channels immediately.
When the paging channel utilization rate is analyzed separately, its monitoring thresholds are described in Table 2-7.
Table 2-7 Monitoring Thresholds for the PCH Channel Utilization Rate
Yellow Pre-
Pre-alarm Level Red Pre-alarm
alarm
Percentage of PCH block resources 50% 70%
used
Paging message congestion ratio 1% 5%
When the yellow pre-alarm threshold is exceeded, you need to expand PCH channels (by increasing the number of CCCH channels). When the red pre-alarm
threshold is exceeded, you should expand PCH channels immediately.
The TCH channel bears encoded voice or user data. It is divided into a full-rate traffic channel (TCH/F) and a half-rate traffic channel (TCH/H).
1. A full rate traffic channel (TCH/F): Its total rate is 22.8 kbit/s.
2. A half rate traffic channel (TCH/H): Its total rate is 11.4 kbit/s.
According to carried services, the TCH channel is divided into a voice service channel and data service channel.
The following two indicators are monitored for the TCH channel utilization rate:
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 5 of 27
Counter ID Description
C901080015 TCH/H busy time
C901080023 TCH/F busy time
C901080009 Average number of available dynamic radio channel
C901080028 Number of available defined TCH/F
C901080019 Number of available defined TCH/H
C901260022 Number of voice TCH/F seizure failure for assignment
C901260071 Number of data TCH/F seizure failure for assignment
C901270022 Number of voice TCH/H seizure failure for assignment
C901270071 Number of data TCH/H seizure failure for assignment
C901260020 Number of voice TCH/F seizure attempts for assignment
C901260069 Number of data TCH/F seizure attempts for assignment
C901270020 Number of voice TCH/H seizure attempts for assignment
C901270069 Number of data TCH/H seizure attempts for assignment
Granularity of collecting statistics on the background OMM. Unit:
Gr seconds.
Table 2-9 describes monitoring thresholds for the TCH channel utilization rate.
Table 2-9 Monitoring Thresholds for the TCH Channel Utilization Rate
Yellow Pre-
Pre-alarm Level Red Pre-alarm
alarm
Erl per TCH channel 0.7 0.9
TCH congestion ratio 2% 5%
When the yellow pre-alarm threshold is exceeded, you need to lower the TCH half-rate conversion threshold, increasing the TCH half-rate ratio, and expanding TCH
channels. When the red pre-alarm threshold is exceeded, you need to expand TCH channels immediately.
The PDCH channel (Packet Data Channel) is a transmission channel for the packet data service. It bears control signaling messages (RLCMAC signaling) and user
data in data service transmitting and receiving flow.
The PDCH channel is divided into the following two types according to its configuration mode:
2. Dynamic PDCH: This channel is converted between the TCH and the PDCH as needed, which are used in the voice service and packet service respectively.
The following three indicators are monitored for the PDCH channel utilization rate:
C901040017/C901040003
Counter ID Description
C901040017 Average number of used PDCH
C901040003 Average number of available PDCH
C901190016 Number of GPRS UL TBF establishment failure due to RR
congestion
C901190039 Number of GPRS UL TBF resource reallocation failure due to RR
congestion for DL TBF establishment
C901190065 Number of GPRS UL TBF resource reallocation failure due to RR
congestion for resource request
C901200016 Number of EGPRS UL TBF establishment failure due to RR
congestion
C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR
congestion for DL TBF establishment
C901200065 Number of EGPRS UL TBF resource reallocation failure due to RR
congestion for resource request
C901190001 Number of GPRS UL TBF establishment requests
C901190036 Number of GPRS UL TBF resource reallocation requests due to DL
TBF establishment
C901190062 Number of GPRS UL TBF resource reallocation requests for
resource request
C901200001 Number of EGPRS UL TBF establishment requests
C901200036 Number of EGPRS UL TBF resource reallocation requests due to DL
TBF establishment
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 6 of 27
Counter ID Description
C901200062 Number of EGPRS UL TBF resource reallocation requests for
resource request
C901170008 Number of GPRS DL TBF establishment failure due to RR
congestion
C901170024 Number of GPRS DL TBF resource reallocation failure due to RR
congestion for UL TBF establishment
C901170037 Number of GPRS DL TBF resource reallocation failure due to RR
congestion for LLC transmission
C901180008 Number of EGPRS DL TBF establishment failure due to RR
congestion
C901180024 Number of EGPRS DL TBF resource reallocation failure due to RR
congestion for UL TBF establishment
C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR
congestion for LLC transmission
C901170001 Number of GPRS DL TBF establishment requests
C901170021 Number of GPRS DL TBF resource reallocation requests due to UL
TBF establishment
C901170034 Number of GPRS DL TBF resource reallocation requests due to LLC
transmission
C901180001 Number of EGPRS DL TBF establishment requests
C901180021 Number of EGPRS DL TBF resource reallocation requests due to UL
TBF establishment
C901180034 Number of EGPRS DL TBF resource reallocation requests due to
LLC transmission
Table 2-11 describes recommended monitoring thresholds for the PDCH channel utilization rate.
Table 2-11 Monitoring Thresholds for the PDCH Channel Utilization Rate
Yellow Pre-
Pre-alarm Level Red Pre-alarm
alarm
PDCH channel utilization rate 80% 95%
Uplink PDCH congestion ratio 1% 3%
Uplink PDCH congestion ratio 1% 3%
When the yellow pre-alarm threshold is exceeded, you need to increase the channel multiplexing ratio, reducing the number of channels allocated to each user,
increasing the number of static channels, and expanding PDCH channels. When the red pre-alarm threshold is exceeded, you should expand PDCH channels
immediately.
The CC board is used as the base station main-control board. The CC board provides the following functions for a BS: clock function, data switching function,
operation and maintenance management, network interface function, and signaling processing.
Functions of the CC board are fulfilled by both the hardware and software of the CC board. Functions fulfilled by the hardware are determined directly by the board
type, and do not need to be measured. This section describes how to measure the functions fulfilled by the software or by the hardware and software together.
According to the design, networking planning, and maintenance situation of the CC board, the following indicators need to be monitored for the CC board load:
Counter ID Description
C370010000 Maximum CPU utilization rate
C370010001 Average CPU utilization rate
When both the average CPU utilization rate and the maximum CPU utilization rate exceed the yellow pre-alarm threshold, you need to monitor CPU load closely.
When both counters exceed the red pre-alarm threshold, it indicates that the CPU of the CC board is has a high load, so you need to split the site or expand the CC
board (by replacing it with a main-control board with greater processing capacity).
During operation of the ZXG10 iBSC, users need to pay attention to the transmission capacity load of each external interface and the capacity load of each board. The
corresponding indicators are defined by counters, which have two-level monitoring, the yellow pre-alarm threshold (low threshold) and red pre-alarm threshold (high
threshold).
In addition, the extreme point is defined for the situation when the peak-hour load indicator exceeds the monitoring threshold for three days in one week. When the
load in the existing network exceeds the yellow pre-alarm threshold, consider optimization measures such as load balancing, and load reduction or expansion. When
the load in the existing network exceeds the red pre-alarm threshold, handle it immediately to ensure that the system load is kept under the yellow pre-alarm threshold.
Table 2-14 describes detailed monitoring indicators.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 7 of 27
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 8 of 27
The Abis interface is an interface between the BSC and the BTS. According to different access modes, it is divided into three types: TDM E1 Abis, IP Abis-FE, and IP
Abis-IPOE. Abis link resource monitoring results indicate whether transmission resources under these three access modes are sufficient. This section describes these
indicators in detail.
Definition: When the TDM E1 Abis interface is used, this indicator indicates the occupancy of transmission time slot resources on the Abis interface.
Formula:
Abis link resource utilization rate (TDM E1 Abis) = C901040002/Number of Abis timeslots
Table 2-15 Counters Related to the Abis Link Resource Utilization Rate (TDM E1 Abis)
Counter ID Description
C901040002 Number of used Abis TS
Note:
1. Number of used Abis TS is taken from the Abis time-slot pool configured on each site.
2. The C901040002 counter value is counted by cell. After the counter values of all cells are added up, the total value may exceed the configured total number of
timeslots.
Table 2-16 Monitoring Thresholds for the Abis Link Resource Utilization Rate (TDM E1 Abis)
Definition: When the IP Abis interface in FE mode is used, this indicator indicates the occupancy of bandwidth on the Abis interface.
Formula:
Table 2-17 Counters Related to the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-FE)
Counter ID Description
C370020009 Radio of Send Bandwidth
C370020008 Radio of Receive Bandwidth
Note: none.
Table 2-18 Monitoring Thresholds for the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-FE)
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 9 of 27
Definition: When the IP Abis interface in IPOE mode is used, this indicator indicates the occupancy of bandwidth on the Abis interface.
Formula:
Abis uplink bandwidth utilization rate (IP Abis-IPOE) = (C901840001 * 8/1000/Gr)/ C901840015
Abis downlink bandwidth utilization rate (IP Abis-IPOE) = (C901840011 * 8/1000/Gr)/ C901840015
Table 2-19 Counters Related to the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-IPOE)
Counter ID Description
Number of received bytes. That is, number of bytes sent by the SDR
C901840001 on the uplink PPP channel (Byte).
Number of sent bytes. That is, number of bytes received by the SDR
C901840011 on the downlink PPP channel (Byte).
C901840015 Bandwidth of PPP link(bps)
Note:
Table 2-20 Monitoring Thresholds for the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-IPOE)
The Gb interface is an interface between the BSC and the SGSN. According to different access modes, it is divided into two types: E1 and IP. Gb-interface link
resource monitoring results indicate whether transmission resources under these two access modes are sufficient. This section describes these indicators in detail.
Definition: When the Gb interface in FR mode is used, this indicator indicates the occupancy of links on the Gb interface.
Formula:
Gb-interface uplink utilization rate (E1) = (C901460005 * 8/1000/Gr)/(Number of timeslots in BRCH links on the Gb interface * 64)
Gb-interface downlink utilization rate (E1) = (C901460004 * 8/1000/Gr)/(Number of timeslots in BRCH links on the Gb interface * 64)
Table 2-21 Counters Related to the Gb-Interface Uplink/Downlink Link Utilization Rate (E1)
Counter ID Description
C901460005 Number of bytes sent on FR link (Byte)
C901460004 Number of bytes received on FR link (Byte)
Note:
1. The number of timeslots of BRCH links on the Gb interface is acquired from the configuration.
Table 2-22 Monitoring Thresholds for the Gb-Interface Uplink/Downlink Link Utilization Rate (E1)
Definition: This indicator indicates the occupancy of bandwidth on the uplink and downlink of the IPGb interface.
Formula:
(8* )/ (Gr*1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
(8* )/ (Gr*1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 10 of 27
Table 2-23 Counters Related to the Gb-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
Counter ID Description
C901850057 send packets bytes high 32bits
C901850056 send packets bytes low 32bits
C901850006 receive packets bytes high 32bits
C901850005 receive packets bytes low 32bits
Note:
1. If the interface board is the GIPI, n=1. If the interface board is the GIPI4, n=2.
3. The number 1000000000 is used to convert the unit of the rate indicator from bps to Gbps.
4. On the IPGb interface, the interface board may be the GIPI or the GIPI4. Because the capacities of these two boards are different, they need to be distinguished.
5. The physical bandwidth of the Gb-interface is allocated by the data bearer network, so it is acquired from the data bearer network. If the physical bandwidth
allocated by the bearer network is greater than the maximum capacity of the board, the maximum capacity MaxOuter_GIPI or MaxOuter_GIPI4 is selected
according to the interface board type.
6. The board bandwidth capacity (MaxOuter) indicates the capacity after the maximum signaling traffic and non-service traffic such as OMCB and PTP have been
reserved. The IP interface rate does not distinguish the interface type (Gb, IPA, or IPAbis), so you need to manually confirm the type of each IP interface.
Table 2-25 Monitoring Thresholds for the Gb-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
The A-interface is an interface between the BSC and the MSC. According to different access modes, it is divided into two types: E1 and IP. A-interface link resource
monitoring results indicate whether transmission resources under these two access modes are sufficient. This section describes these indicators in detail.
Definition: When the A interface in TDM mode is used, this indicator indicates the occupancy of trunk circuits on the A interface.
Formula:
Table 2-26 Counters Related to the A-Interface Trunk Utilization Rate (E1/STM-1)
Counter ID Description
C901380019 Mean number of busy trunk circuits
C901380001 Mean number of available trunk circuits
Note: none.
Table 2-27 Monitoring Thresholds for the A-Interface Trunk Utilization Rate (E1/STM-1)
Definition: When the A-interface in IP mode is used, this indicator indicates the occupancy of transmission bandwidth on the A-interface.
Formula:
(8* )/ (Gr*1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
(8* )/ (Gr*1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
Table 2-28 Counters Related to the A-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
Counter ID Description
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 11 of 27
Counter ID Description
C901850057 send packets bytes high 32bits
C901850056 send packets bytes low 32bits
C901850006 receive packets bytes high 32bits
C901850005 receive packets bytes low 32bits
Note:
1. If the interface board is the GIPI, n=1. If the interface board is the GIPI4, n=2.
3. The number 1000000000 is used to convert the unit of the rate indicator from bps to Gbps.
4. On the IP A interface, the interface board may be the GIPI or the GIPI4. Because the capacities of these two boards are different, they need to be distinguished.
Table 2-29 Maximum Capacity of Physical Bandwidth on the GIPI and the GIPI4
5. The physical bandwidth of the A interface is allocated by the data bearer network, so it is acquired the data bearer network. If the physical bandwidth allocated by
the bearer network is greater than the maximum capacity of the board, the maximum capacity MaxOuter_GIPI or MaxOuter_GIPI4 is selected according to the
interface board type.
6. The board bandwidth capacity (MaxOuter) indicates the capacity after the maximum signaling traffic and non-service traffic such as OMCB and PTP have been
reserved. The IP interface rate does not distinguish the interface type (Gb, IPA, or IPAbis), so you need to manually confirm the type of each IP interface.
Table 2-30 Monitoring Thresholds for the A-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
Definition: When the Ater-interface (with external TC) is used, this indicator indicates the occupancy of trunk circuits on the Ater interface.
Formula:
Counter ID Description
C901600005 Maximum number of busy 8K relay circuits of Ater interface
C901600004 Maximum number of busy 16K relay circuits of Ater interface
C901600003 Average number of available 16K relay circuits of Ater interface
Note:
8K relay circuits are used in the HR service, while 16 relay circuits are used in FR circuits. Two 8K relay circuits are multiplexed in one 16K sub-time slot.
Table 2-32 Monitoring Thresholds for the Ater-Interface Trunk Utilization Rate
Under E1 transmission mode, the No.7 signaling link is used to exchange control-plane messages between the BSC and the MSC (or the iTC). Its bandwidth can be
configured as 64 K or 2 M. This section describes the utilization rate indicator in detail.
Formula:
Table 2-33 Counters Related to the No.7 Signaling Link Uplink/Downlink Utilization Rate
Counter ID Description
C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing
signalling link
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 12 of 27
Counter ID Description
Ten thousand multiple bandwidth occupancy rate on incoming
C901670047 signalling link
Note:
At most 16 No.7 signaling links can be configured for one single adjacent office.
Table 2-34 Monitoring Thresholds for the No.7 Signaling Link Uplink/Downlink Utilization Rate
Under IP transmission mode, the SCTP link is used to exchange signaling messages between the BSC and the core network. You can monitor the traffic on one SCTP
link to ensure that the actual traffic falls within the scope of system processing capacity.
Definition: This indicator indicates the traffic of each SCTP link on the iBSC, to ensure that SCTP congestion does not exist.
Formula:
Counter ID Description
C901420005 Bytes of packets sent to ip(Bytes)
C901420003 Bytes of packets received from ip(Bytes)
Note:
1. On the ZXG10 iBSC, the buffer size of SCTP links is fixed in the version, and the bandwidth is mainly restricted by the size of the receiving buffer. If the bandwidth
is restricted, SCTP links need to be expanded. Usually two SCTP links are added each time.
2. On the ZXUR 9000 GSM controller, the receiving and sending buffers are managed in a new way, so the throughput of a single SCTP is no longer the bottleneck
and does not need to be monitored any longer.
The CMP board is in charge of call control for wireless services in the PS or CS domain, protocol processing on BSSAP, BSSGP, and SCTP sub-layers, and
management of distributed resources in the system itself. CPU load of the CMP board is the key indicator measuring the board processing capacity.
Definition: This indicator indicates the CPU load of the CMP unit on the iBSC.
Formula:
Counter ID Description
C901410004 Mean ratio of the CPU usage
Note:
The statistics of the CPU load is calculated using the CPU load of all boards. While monitoring the counter C901410004, you need to select the load of the
corresponding unit on the CMP board.
Table 2-38 Monitoring Thresholds for the CMP CPU Utilization Rate
The planning of BSC paging capacity is affected by the paging capacity of the air interface and the load of the CMP. If the paging traffic in one location area is too
high, some paging messages may not be sent in time from the BTS side due to insufficient CCCH channel resources. In addition, if the paging traffic on the CMP
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 13 of 27
board is too high, its load will increase. Under scenarios with high service traffic and high load, the paging needs to be controlled. It is recommended that the incoming
paging traffic in one location area does not exceed 250000 per hour. The paging capacity should better be configured for each module and each location area. The
following indicator is monitored for the BSC paging capacity.
Definition: This indicator indicates whether the paging traffic on the iBSC has exceeded the threshold.
Formula:
Table 2-39 Counters Related to the Number of Times that Paging Traffic Exceeds the Threshold
Counter ID Description
C902110002 Times of pagings larger than the low threshold
Note:
1. Paging messages are sent to each CMP module, so traffic control measurement is completed by CMP. There are two thresholds for paging traffic control: number
of paging messages processed by the system per second, and maximum number of paging messages that can be processed by the system per second, which
are set to 300/s and 400/s respectively by default.
2. When the first traffic control threshold is reached, the system starts to discard PS paging messages. When the second traffic control threshold is reached, the
system discards both PS and CS paging messages. In addition, the system also counts the number of paging messages discarded beyond the threshold and the
maximum number of paging messages discarded per second, so that onsite engineers can monitor the situation when the paging traffic is extremely high.
Table 2-40 Monitoring Thresholds for the Number of Times that Paging Traffic Exceeds the Threshold
DSP timeslots on the UPPB board are used to process PS services, which process user-plane protocols under A/Gb mode and Iu mode, such as the BSSGP, the
PDCP, the GTP_U, and the Iu_UP. One Gigabit UPPB (GUP2) includes 15 DSPs, each of which handles 400 16K channels. One 100M UPPB (GUP) includes 14
DSPs, each of which handles 160 16K channels.
Definition: This indicator indicates the usage of DSP resources on the UPPB board.
Utilization rate of DSP timeslots on the UPPB board = (C902470002/C902470003)/Number of timeslots on a single DSP
Maximum utilization rate of DSP MAC instances on the UPBB board: C902470036
Table 2-41 Counters Related to the DSP Resource Utilization Rate on the UPPB Board
Counter ID Description
C902470002 Amount of used DSP TS
C902470003 Number of regular scanning and sampling
C902470036 Peak value of MAC process usage
C902470041 Mean vaule of DSP usage
Note:
1. The number of timeslots on one DSP differs according to the board type. There are 160 timeslots on a single DSP of the 100M board, and 400 timeslots on a
single DSP of the Gigabit board.
2. Measurement of Slave timeslots is taken of the DSPs of all boards. While checking the statistics, you need to units of the UPPB type according to the physical
configuration.
Table 2-42 Monitoring Thresholds for the DSP Resource Utilization Rate on the UPPB Board
DSP timeslots on the AIPB board are used to process CS services. On the A interface, DSP timeslots process and package the RTP protocol, transform code types,
and fulfill code type transformation and rate adaptation for TRAU frames. One Gigabit AIPB (GUP2) includes 15 DSPs, each of which handles 406 A-interface voice
timeslots. One 100 M AIPB (GUP) includes 14 DSPs, each of which handles 125 A-interface voice timeslots.
Definition: When the IPA interface is used, this indicator indicates the occupancy of DSP timeslots on the A-interface user-plane processing board AIPB.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 14 of 27
Table 2-43 Counters Related to the DSP Resource Utilization Rate on the AIPB Board
Counter ID Description
C902470030 Number of active voice channel
Note:
1. The number of timeslots on one DSP differs according to the board type. There are 125 timeslots on a single DSP of the 100M board, and 406 timeslots on a
single DSP of the Gigabit board.
2. Measurement of Slave timeslots is taken of the DSPs of all boards. While checking the statistics, you need to units of the AIPB type according to the physical
configuration.
Table 2-44 Monitoring Thresholds for the DSP Resource Utilization Rate on the AIPB Board
The IP interface board provides the IP access function for external interfaces on the BSC. The packet forwarding capacity of one board can be indicated by the
equivalent PPS, which equally reflects the contribution to the media core CPU made by packet forwarding in different service flows.
Definition: This indicator indicates whether the equivalent PPS capacity of forwarding packets on the IP interface board is restricted.
Formula:
( + 1* )/ Gr/(1080 * 1000)
Table 2-45 Counters Related to the Transmitting and receiving Utilization Rate of IP Interface Board
Counter ID Description
C901850060 send packets high 32bits
C901850059 send packets low 32bits
C901850009 receive packets high 32bits
C901850008 receive packets low 32bits
Note:
2. The interface board may be the GIPI or the GIPI4. Because the capacities of these two boards are different, they need to be distinguished.
Table 2-46 Maximum PPS Capacity of the GIPI and the GIPI4
3. The one-way PPS capacity of the board (MaxPPS_GIPI_UNI) indicates the capacity after the maximum signaling traffic and non-service traffic such as OMCB
and PTP have been reserved.
Table 2-47 Monitoring Thresholds for the Transmitting and Receiving Utilization Rate of IP Interface Board
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 15 of 27
Similar to the ZXG10 iBSC, interface capacity and board load indicators of the ZXUR 9000 GSM are also defined through counters, so that users can determine the
yellow pre-alarm threshold (low threshold) and red pre-alarm threshold (high threshold).
In addition, the extreme point is defined for the situation when the peak-hour load indicator exceeds the monitoring threshold for three days in one week. When the
load in the existing network exceeds the yellow pre-alarm threshold, consider optimization measures such as load balancing, load reduction or expansion. When the
load in the existing network exceeds the red pre-alarm threshold, handle it immediately to ensure that the system load is kept under the yellow pre-alarm threshold.
Table 2-48 describes detailed monitoring indicators.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 16 of 27
The Abis interface is an interface between the BSC and the BTS. According to different access modes, it is divided into three types: TDM E1 Abis, IP Abis-FE, and IP
Abis-IPOE. Abis link resource monitoring results indicate whether transmission resources under these three access modes are sufficient. This section describes these
indicators in detail.
Definition: When the TDM E1 Abis interface is used, this indicator indicates the occupancy of transmission time slot resources on the Abis interface.
Formula:
Abis link resource utilization rate (TDM E1 Abis) = C901040002/Number of Abis time slots
Table 2-49 Counters Related to the Abis Link Resource Utilization Rate (TDM E1 Abis)
Counter ID Description
C901040002 Number of used Abis TS
Note:
1. Number of used Abis TS is taken from the Abis timeslot pool configured on each site.
2. The C901040002 counter is counted by cell. After the counter values of all cells are added up, the total value may exceed the configured total number of time
slots.
Table 2-50 Monitoring Thresholds for the Abis Link Resource Utilization Rate (TDM E1 Abis)
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 17 of 27
Definition: When the IP Abis interface in FE mode is used, this indicator indicates the occupancy of bandwidth on the Abis interface.
Formula:
Table 2-51 Counters Related to the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-FE)
Counter ID Description
C370020009 Radio of Send Bandwidth
C370020008 Radio of Receive Bandwidth
Note: none.
Table 2-52 Monitoring Thresholds for the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-FE)
Definition: When the IP Abis interface in IPOE mode is used, this indicator indicates the occupancy of bandwidth on the Abis interface.
Formula:
Abis uplink bandwidth utilization rate (IP Abis-IPOE) = (C380250002 * 8/1000/Gr)/ C380250005
Abis downlink bandwidth utilization rate (IP Abis-IPOE) = (C380250004 * 8/1000/Gr)/ C380250005
Table 2-53 Counters Related to the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-IPOE)
Counter ID Description
Number of Received Bytes. That is, number of bytes sent by the
C380250002 SDR on the uplink PPP channel (byte).
Number of Transmitted Bytes. That is, number of bytes received by
C380250004 the SDR on the downlink PPP channel (byte).
C380250005 PPP band width(bps)
Note:
Table 2-54 Monitoring Thresholds for the Abis Uplink/Downlink Bandwidth Utilization Rate (IP Abis-IPOE)
The Gb interface is an interface between the BSC and the SGSN. According to different access modes, it is divided into two types: E1 and IP. Gb-interface link
resource monitoring results indicate whether transmission resources under these two access modes are sufficient. This section describes these indicators in detail.
Definition: When the Gb interface in FR mode is used, this indicator indicates the occupancy of links on the Gb interface.
Formula:
Gb-interface uplink utilization rate (E1) = (C901460005 * 8/1000/Gr)/(Number of time slots in BRCH links on the Gb interface * 64)
Gb-interface downlink utilization rate (E1) = (C901460004 * 8/1000/Gr)/(Number of time slots in BRCH links on the Gb interface * 64)
Table 2-55 Counters Related to the Gb-Interface Uplink/Downlink Link Utilization Rate (E1)
Counter ID Description
C901460005 Number of bytes sent on FR link (Byte)
C901460004 Number of bytes received on FR link (Byte)
Note:
1. The number of timeslots in BRCH links on the Gb interface is acquired from the configuration.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 18 of 27
Table 2-56 Monitoring Thresholds for the Gb-Interface Uplink/Downlink Link Utilization Rate (E1)
Definition: This indicator indicates the occupancy of bandwidth on the uplink and downlink of the IPGb interface.
Formula:
(8* )/(Gr * 1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
(8* )/(Gr * 1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
Table 2-57 Counters Related to the Gb-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
Counter ID Description
C380260003 Number of bytes sent (high 4 bytes)
C380260004 Number of bytes sent (low 4 bytes)
C380260001 Number of bytes received (high 4 bytes)
C380260002 Number of bytes received (low 4 bytes)
Note:
2. The number 1000000000 is used to convert the unit of the rate indicator from bps to Gbps.
3. When the IPGb interface is used, the interface board can be EGPBEXGB1aEXGB1bEGPB2c or EGPB2a. Their maximum bandwidth processing
capacities are described as follows:
4. The physical bandwidth of the Gb-interface is allocated by the data bearer network, so it is acquired the data bearer network. If the physical bandwidth allocated
by the bearer network is greater than the maximum capacity of the board, the maximum capacity MaxOuter is taken.
5. The board bandwidth capacity (MaxOuter) indicates the capacity after the maximum signaling traffic and non-service traffic such as OMCB and PTP have been
reserved. The IP interface rate does not distinguish the interface type (Gb, IPA, or IPAbis), so you need to manually confirm the type of each IP interface.
6. The vaule n was according to the number of external port used on the board.
Table 2-59 Monitoring Thresholds for the Gb-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
The A-interface is an interface between the BSC and the MSC. According to different access modes, it is divided into two types: E1 and IP. A-interface link resource
monitoring results indicate whether transmission resources under these two access modes are sufficient. This section describes these indicators in detail.
Definition: When the A interface in TDM mode is used, this indicator indicates the occupancy of trunk circuits on the A interface.
Formula:
Table 2-60 Counters Related to the A-Interface Trunk Utilization Rate (E1/STM-1)
Counter ID Description
C901380019 Mean number of busy trunk circuits
C901380001 Mean number of available trunk circuits
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 19 of 27
Note: none.
Table 2-61 Monitoring Thresholds for the A-Interface Trunk Utilization Rate (E1/STM-1)
Counter ID Description
C901380019 Average number of busy trunk circuits on the A interface
C901380001 Average number of available trunk circuits
Definition: When the A-interface in IP mode is used, this indicator indicates the occupancy of transmission bandwidth on the A-interface.
Formula:
(8* )/(Gr * 1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
(8* )/(Gr * 1000000000)/ min(Bandwidth allocated by the bearer network (Gbps),Maximum throughput of the board)
Table 2-62 Counters Related to the A-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
Counter ID Description
C380260003 Number of bytes sent (high 4 bytes)
C380260004 Number of bytes sent (low 4 bytes)
C380260001 Number of bytes received (high 4 bytes)
C380260002 Number of bytes received (low 4 bytes)
Note:
2. The number 1000000000 is used to convert the unit of the rate indicator from bps to Gbps.
3. When the IPGb interface is used, the interface board can be EGPBEXGB1aEXGB1bEGPB2c or EGPB2a. Their maximum bandwidth processing
capacities are described as follows:
4. The physical bandwidth of the A-interface is allocated by the data bearer network, so it is acquired from the data bearer network. If the physical bandwidth
allocated by the bearer network is greater than the maximum capacity of the board, the maximum capacity MaxOuter is taken.
5. The board bandwidth capacity (MaxOuter) indicates the capacity after the maximum signaling traffic and non-service traffic such as OMCB and PTP have been
reserved. The IP interface rate does not distinguish the interface type (Gb, IPA, or IPAbis), so you need to manually confirm the type of each IP interface.
6. The vaule n was according to the number of external port used on the board.
Table 2-64 Monitoring Thresholds for the A-Interface Uplink/Downlink Bandwidth Utilization Rate (IP)
Definition: When the Ater-interface (with external TC) is used, this indicator indicates the occupancy of trunk circuits on the Ater interface.
Formula:
Counter ID Description
C901600005 Maximum number of busy 8K relay circuits of Ater interface
C901600004 Maximum number of busy 16K relay circuits of Ater interface
C901600003 Average number of available 16K relay circuits of Ater interface
Note:
8K relay circuits are used in the HR service, while 16 relay circuits are used in FR circuits. Two 8K relay circuits are multiplexed in one 16K sub-time slot.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 20 of 27
Table 2-66 Monitoring Thresholds for the Ater-Interface Trunk Utilization Rate
Under E1 transmission mode, the No.7 signaling link is used to exchange control-plane messages between the BSC and the MSC (or the iTC). Its bandwidth can be
configured as 64 K or 2 M. This section describes the utilization rate indicator in detail.
Formula:
Table 2-67 Counters Related to the No.7 Signaling Link Uplink/Downlink Utilization Rate
Counter ID Description
Ten thousand multiple bandwidth occupancy rate on outgoing
C380120019 signalling link
Ten thousand multiple bandwidth occupancy rate on incoming
C380120020 signalling link
Note:
At most 16 No.7 signaling links can be configured for one single adjacent office.
Table 2-68 Monitoring Thresholds for the No.7 Signaling Link Uplink/Downlink Utilization Rate
The control plan CPU on CRP board (such as CMP module before) is in charge of call control for wireless services in the PS or CS domain, protocol processing on
BSSAP, BSSGP, and SCTP sub-layers, and management of distributed resources in the system itself. The CPU load of CRP board is the key indicator measuring the
board processing capacity.
Definition: This indicator indicates the CPU load of the CRP board on the BSC.
Formula:
Counter ID Description
C380360004 Mean ratio of the CPU usage
Note:
CPU load of the ZXUR 9000 GSM is counted for board. These statistics include the total CPU load of all modules under this CRP board. During the monitoring
process, it is better to centralize primary modules on one board, so that you only need to monitor the load of the primary CRP board.
Table 2-70 Monitoring Thresholds for Average CPU load of control plan
The planned BSC paging capacity is affected by the paging capacity of the air interface and the load of the CMP module. If the paging traffic in one location area is too
high, some paging messages may not be sent in time on the BTS side due to insufficient CCCH channel resources. In addition, if the paging traffic on the CRP board
is too high, its load will increase. Under scenarios with high service traffic and high load, the paging needs to be controlled. It is recommended that the incoming
paging traffic in one location area does not exceed 250000 per hour. The paging capacity should better be configured for each module and each location area. The
following indicator is monitored for the BSC paging capacity.
Definition: This indicator indicates whether the paging traffic on the BSC has exceeded the threshold.
Formula:
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 21 of 27
Table 2-71 Counters Related to the Number of Times that Paging Traffic Exceeds the Threshold
Counter ID Description
C902110002 Times of pagings larger than the low threshold
Note:
1. Paging messages are sent to each CMP module, so traffic control measurement is made by CMP. There are two thresholds for paging traffic control: number of
paging messages processed by the system per second, and maximum number of paging messages that can be processed by the system per second, which are
set to 300/s and 400/s respectively by default.
2. When the first traffic control threshold is reached, the system starts to discard PS paging messages. When the second traffic control threshold is reached, the
system discards both PS and CS paging messages. In addition, the system also counts the number of paging messages discarded beyond the threshold and the
maximum number of paging messages discarded per second, so that onsite engineers can monitor the situation when the paging traffic is extremely high
transiently.
Table 2-72 Monitoring Thresholds for the Number of Times that Paging Traffic Exceeds the Threshold
Each slave unit on CRP board is configured to handle CS service and PS service both. The load of CS services is shared by every slave, and the load of PS services
is shared by balanced cells configured on every slave automatically.
Definition: This indicator indicates the usage of slave resources on the CRP board.
Counter ID Description
C902470002 Amount of used DSP TS
C902470003 Number of regular scanning and sampling
C902470041 Mean vaule of DSP usage
C902470030 Number of active voice channel
Note:
3 5376 is a maximum point value when CS is occupied on the slave, and 7 is a ratio between this point value and active voice channel
Yellow Pre-
Indicator Red Pre-alarm
alarm
Utilization rate of slave timeslots for 80% 90%
PS services
Occupancy of slave timeslots for 70% 75%
CS services
Average load of Slave 70% 80%
On the ZXUR 9000 GSM, you need to pay attention to the packet processing capacity of interface boards under IP mode and IPOE mode. Board types include: EGPE,
EXGB1a, EXGB1b, EGPB2c, EGPB2a, EDTI, EDTI2a, ESDTI and ESDTI2a. The EGPB, EXGB1a, EXGB1b, EGPB2c, EGPB2a boards provide Ethernet-based IP
access, the EDTI, EDTI2a boards provide E1-based IP access, and the ESDTI, ESDTI2a boards provide CSTM-1 interface-based IP access. Compared with the
EGPB, EXGB1a, EXGB1b, EGPB2c, EGPB2a boards, the EDTI, EDTI2a, ESDTI, ESDTI2a boards need to perform HDLC or PPP/ML/MC-PPP protocol processing
upon TDM data before recovering IP data packets. The utilization rate indicator is monitored for the following boards.
Definition: This indicator indicates whether the equivalent PPS capacity of forwarding packets on the EGPB board is restricted.
Formula:
Counter ID Description
C380450009 Number of received packets (high 32 bit)
C380450010 Number of received packets (low 32 bit)
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 22 of 27
Counter ID Description
C380450011 Number of sent packets (high 32 bit)
C380450012 Number of sent packets (low 32 bit)
Note:
3. The EGPB board has four external GE ports, so the number of packets forwarded on the four ports is added up to get the number of forwarded packets on the
board level.
Table 2-77 Monitoring Thresholds for the EGPB Board Utilization Rate
Definition: This indicator indicates whether the equivalent PPS capacity of forwarding packets on the EXGB1a\EXGB1b\EGPB2c\EGPB2a board is restricted.
Formula:
Counter ID Description
C380460001 Total Received IPv4 Packet Count
C380460004 Total Transmitted IPv4 Packet Count
C380460007 Total Received IPv6 Packet Count
C380460010 Total Transmitted IPv6 Packet Count
C380450012 Number of sent packets (low 32 bit)
Note:
2. The vaule n was according to the number of external port used on the board.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 23 of 27
Table 2-80 Monitoring Thresholds for the EXGB1a\EXGB1b\EGPB2c\EGPB2a Board Utilization Rate
2.4.8.3 Utilization Rate of the Transmitting and Receiving Bandwidth of EDTI/EDTI2a/ESDTI/ESDTI2a Boards
Definition: This indicator indicates whether the transmitting and receiving bandwidth of EDTI/EDTI2a/ESDTI/ESDTI2a boards is restricted.
Formula:
Occupancy of the transmitting bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards (Abis interface) = (8* )/(Gr*1000000)/ Maximum throughput of the board
Occupancy of the receiving bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards (Abis interface) = (8* )/(Gr*1000000) /Maximum throughput of the board
Occupancy of the transmitting bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards (Gb interface) =(8* )/(Gr*1000000) /Maximum throughput of the board
Occupancy of the receiving bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards (Gb interface) =(8* )/(Gr*1000000) /Maximum throughput of the board
Table 2-81 Counters Related to the Transceiving Bandwidth Utilization Rate of EDTI/ESDTI Board
Counter ID Description
C380250002 Number of Received Bytes
C380250004 Number of Transmitted Bytes
C901460004 Number of bytes received on FR link
C901460005 Number of bytes sent on FR link
Note:
2. The maximum bandwidth processing capacities of EDTI/EDTI2a/ESDTI/ESDTI2a boards are different, and the ESDTI/ESDTI2a board is also configured
differently on the Abis interface and the Gb interface. The processing capacities of EDTI/EDTI2a/ESDTI/ESDTI2a boards are described as follows:
3. The PPS capacity of the EDTI/EDTI2a board is far higher than its bandwidth, so you only need to monitor the bandwidth of the EDTI/EDTI2a board. But for the
ESDTI/ESDTI2a, you need to consider both its PPS capacity and its traffic.
4. The bandwidth capacity (MaxOuter_EDTI/MaxOuter_ESDTI) of a board indicates the capacity after OMCB channel processing and PTP traffic are excluded.
5. The vaule n was according to the number of PPP or FR link used on the board.
Table 2-83 Monitoring Thresholds for the Transmitting and Receiving Bandwidth Utilization Rate of EDTI/EDTI2a/ESDTI/ESDTI2a Board
Yellow Pre-
Indicator Red Pre-alarm
alarm
Occupancy of the transmitting 70% 80%
bandwidth on
EDTI/EDTI2a/ESDTI/ESDTI2a
board (Abis interface)
Occupancy of the receiving 70% 80%
bandwidth on
EDTI/EDTI2a/ESDTI/ESDTI2a
board (Abis interface)
Occupancy of the transmitting 70% 80%
bandwidth on
EDTI/EDTI2a/ESDTI/ESDTI2a
board (Gb interface)
Occupancy of the receiving 70% 80%
bandwidth on
EDTI/EDTI2a/ESDTI/ESDTI2a
board (Gb interface)
Definition: This indicator indicates whether the equivalent PPS capacity of forwarding packets on the ESDTI/ESDTI2a board is restricted.
Formula:
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 24 of 27
Table 2-84 Counters Related to the PPS Utilization Rate of the ESDTI/ESDTI2a
Counter ID Description
C380250001 Number of Received Frames
C380250003 Number of Transmitted Frames
Note:
3. For ESDTI/ESDTI2a board, you need to consider both its PPS capacity and its traffic.
4. The PPS capacity of the board indicates the capacity after OMCB channel processing and PTP traffic are excluded. In addition, only the Abis interface needs to
be monitored for the ESDTI/ESDTI2a board.
5. The vaule n was according to the number of PPP used on the board.
Table 2-86 Monitoring Thresholds for the PPS Utilization Rate of the ESDTI/ESDTI2a
1. The MSC sends a paging message to the BSC. For the abnormal situation, see point #1.
2. The BSC sends the paging message to the MS. The MS returns a paging response that contains the connection request. For the abnormal situation, see point #2.
3. The BTS assigns a signaling channel. The MS establishes the connection with the BTS, and sends the paging response to the MSC. For abnormal situations, see
points #3, #4, and #5.
4. The MSC carries out the DTAP (authentication/encryption) procedure. For abnormal situations, see points #6 and #7.
5. The MSC initiates the channel assignment flow and assigns a channel. For abnormal situations, see points #8, #9, #10, #11, and #12.
6. The MSC carries out the call setup procedure. The call is set up successfully.
Figure 3-1 Impacts of Wireless Network Resources upon the Basic Called Flow
When the MS initiates a channel request to the network side, the BSS needs to allocate a SDCCH channel to the MS. As the number of connected users increases,
SDCCH channels may be congested. In this case, other users cannot be connected.
Figure 3-2 shows the analysis and processing flow for the SDCCH utilization rate.
Figure 3-2 Analysis and Processing Flow for the SDCCH Utilization Rate
Based on on-site experience, the paging congestion ratio starts to increase when the CCCH load reaches 55%, and it increases dramatically when the CCCH load
reaches 70%. Congestion of AGCH channels and PCH channels is not only related to the channel occupation times, but also related to the concurrency degree. The
cell concurrency degree under different traffic models is different.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 25 of 27
Figure 3-3 shows the analysis and processing flow for the CCCH utilization rate.
Figure 3-3 Analysis and Processing Flow for the CCCH Utilization Rate
As paging messages increase, the PCH channel utilization rate also increases. If the PCH channel utilization rate is too high or paging messages are congested, the
transmission of paging messages will be affected and therefore the called user cannot be paged.
Figure 3-4 shows the analysis and processing flow for the PCH utilization rate.
Figure 3-4 Analysis and Processing Flow for the PCH Utilization Rate
When the Erl per TCH channel and the TCH congestion ratio increase, users may not be allocated with TCH channels.
Figure 3-5 shows the analysis and processing flow for the TCH utilization rate.
Figure 3-5 Analysis and Processing Flow for the TCH Utilization Rate
When the PDCH utilization rate and the uplink/downlink congestion ratio increase, users may not be allocated with PDCH channels.
Figure 3-6 shows the analysis and processing flow for the PDCH utilization rate.
Figure 3-6 Analysis and Processing Flow for the PDCH Utilization Rate
The following functions occupy CPU load: operation and maintenance management, network interface function and signaling processing. Usually operation and
maintenance functions occasionally occupy CPU load, and do not occupy CPU load on a long term. Thus, during network monitoring, you need consider both the
average CPU usage and the maximum CPU usage.
1. The average CPU usage and the maximum CPU usage are counted with the granularity of an hour, so there are 7*24=168 sampling points in one week. The
indicators are monitored for one week continuously.
2. When the situation that the average CPU usage (%) >=75% and the maximum CPU usage (%) >=85% occurs twice or more in one week, this site will be listed as
a key site for monitoring.
3. When the situation that the average CPU usage (%) >=80% and the maximum CPU usage (%) >=90% occurs twice or more in one week, you need to consider
site splitting or expansion.
4. For functions that are less used, such as version downloading, if CPU load is too high during busy hours, it is suggested to carry out these operations during idle
hours in the midnight.
Figure 3-7 shows the analysis and processing flow for the CC board load.
When the TDM Abis-interface link utilization rate exceeds the threshold, first verify that no fault exists with any E1 link, and then expand Abis links. For IPOE IP Abis
links, first verify that no fault exists with any E1 link, and then enable the IP head compression and DTX function to save bandwidth on Abis-interface links. If the Abis
link utilization rate still exceeds the threshold after the IP head compression and DTX function has been enabled, expand E1 links. For IP Abis links on the FE
interface, usually no bandwidth bottleneck exists. However, if bandwidth restriction is configured on the bearer network, the bearer network side needs to allocate
greater bandwidth.
Figure 3-8 Analysis and Processing Flow for the Abis-Interface Link Utilization Rate
For the FR GB (E1) interface, if the Gb-interface link utilization rate exceeds the threshold, first verify that no link fault exists. Otherwise, handle the link fault first. If
multiple BRCH channels are configured, verify that the load on each BRCH is balanced. In case of load unbalance between BRCH channels, adjust the number of
timeslots to be the same for all BRCH channels.
For the IPGB interface, if the Gb-interface link utilization rate exceeds the threshold, verify that the link load between transmission paths is balanced. In case of link
load unbalance, make analysis upon the uplink and the downlink respectively. Check networking schemes of the iBSC, the data bearer network, and the SGSN, and
check the routing policy on each node, to identify the cause for link load unbalance. Adjust link load accordingly. When necessary, the bearer network needs to
increase the bandwidth allocated to the Gb interface.
Figure 3-9 Analysis and Processing Flow for the Gb-Interface Link Utilization Rate
For the TDM A interface, when the circuit trunk usage exceeds the threshold, first verify that no fault exists with circuits. If the usage still exceeds the threshold after
circuit faults are eliminated, expand A-interface trunk circuits.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 26 of 27
For the IP A interface, if the bandwidth usage exceeds the threshold, verify that the link load between several transmission paths is balanced. In case of link load
unbalance, make analysis upon the uplink and the downlink respectively. Check networking schemes of the iBSC, the data bearer network, and the CN, and check the
routing policy on each node, to identify the cause for link load unbalance. Adjust link load accordingly.
The Ater interface only exists in TDM mode. When its circuit trunk usage exceeds the threshold, expand trunk circuits on the Ater interface.
Figure 3-10 Analysis and Processing Flow for the A/Ater-Interface Link Utilization Rate
When the No.7 signaling link load exceeds the threshold, first verify that the load between signaling links is balanced. In case of any link load unbalance, verify that no
signaling link is out of service and the number of signaling links is n power of 2 (2, 4, 8, 16). Under this situation, the load between signaling links can be basically
balanced. If signaling link load is already balanced, you can make expansion by increasing the number of signaling links or transforming 64K signaling links into 2M
signaling links.
Figure 3-11 Analysis and Processing Flow for the No.7 Signaling Link Uplink/Downlink Utilization Rate
On the ZXG10 iBSC, the buffer size of SCTP links is fixed in the version, and the bandwidth is mainly restricted by the size of receiving buffer. In case of bandwidth
restriction, make expansion by increasing two SCTP links each time. In this case, the SCTP links should be balanced on CMP boards.
Figure 3-12 Analysis and Processing Flow for the SCTP Traffic Indicator
The CMP board is in charge of service call control management in PS/CS domains and management of resources on BSSAP and BSSGP layers and in the system
itself. It handles a large number of control-plane messages. If the CMP load is high, it is usually directly related to the high service traffic of this module, or it may be
caused by unreasonable configurations. You can make analysis according to the following procedure:
Figure 3-13 Analysis and Processing Flow for the CMP Load
In LAIs with extremely high paging traffic, you can split LAIs to reduce paging traffic on the A interface. Under the normal situation that the BSC system is attacked by
transient outburst paging traffic (for example, group sending of short messages), the CMP load will be increased transiently and normal service access will be affected.
To avoid impacts of transient attack, the paging flow-control function is configured on the BSC for the sudden increase of paging traffic. With this function, the paging
traffic in a unit time is restricted, so the paging traffic is controlled from the beginning when paging traffic is received. Thus, the problem of high CPU load caused by
high outburst paging traffic can be avoided. When the paging traffic exceeds the threshold, make analysis according to the following flow:
Note: The transient paging attack does not necessarily occur in busy hours, so you need to monitor this indicator all day.
Figure 3-14 Analysis and Processing Flow for BSC Paging Traffic
3.4.8 Analysis and Processing of DSP Resource Utilization Rate on the UPPB Board
Three indicators are monitored for DSP resources on the UPPB board: DSP timeslot usage on the UPBB board, maximum usage of DSP MAC instances on the UPBB
board, and average DSP load on the UPPB board. They all indicate whether resource usage on this DSP has exceeded the threshold and whether you need to
balance services to other DSPs. The analysis and processing flow for DSP resources on the UPPB board is shown as follows:
Figure 3-15 Analysis and Processing Flow for DSP Resources on the UPPB Board
3.4.9 Analysis and Processing of Utilization Rate of DSP Resource on the AIPB Board
When the DSP resource usage on the AIPB board exceeds the threshold, possibly the DSP timeslot resources on the AIPB are insufficient, and you need to expand
the AIPB board to increase timeslots. The analysis and processing flow is shown as follows:
Figure 3-16 Analysis and Processing Flow for DSP Resources on the AIPB Board
The GIPI or the GIPI4 is used as the IP interface board. The following indicators are monitored for the IP interface board: GIPI transmitting utilization rate, GIPI
receiving utilization rate, and comprehensive GIPI4 transmitting and receiving utilization rate. They indicate whether the transmitting and receiving capacity of the IP
interface board has exceeded the threshold. If yes, usually you need to expand the board. The analysis and processing flow is shown as follows:
Figure 3-17 Analysis and Processing Flow for the IP Interface Board Link Utilization Rate
When the TDM Abis-interface link utilization rate exceeds the threshold, first verify that no fault exists with any E1 link, and then expand Abis links. For IPOE IP Abis
links, first verify that no fault exists with any E1 link, and then enable the IP head compression and DTX function to save bandwidth on Abis-interface links. If the Abis
link utilization rate still exceeds the threshold after the IP head compression and DTX function has been enabled, expand E1 links. For IP Abis links on the FE
interface, usually no bandwidth bottleneck exists. However, if bandwidth restriction is configured on the bearer network, the bearer network side needs to allocate
greater bandwidth.
Figure 3-18 Analysis and Processing Flow for the Abis-Interface Link Utilization Rate
For the FR GB (E1) interface, if the Gb-interface link utilization rate exceeds the threshold, first verify that no link fault exists. Otherwise, handle the link fault first. If
multiple BRCH channels are configured, verify that the load on each BRCH is balanced. In case of load unbalance between BRCH channels, adjust the number of
timeslots to be the same for all BRCH channels.
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015
Capacity Monitoring and Expansion Guide Page 27 of 27
For the IPGB interface, if the Gb-interface link utilization rate exceeds the threshold, verify that the link load between transmission paths is balanced. In case of link
load unbalance, make analysis upon the uplink and the downlink respectively. Check networking schemes of the iBSC, the data bearer network, and the SGSN, and
check the routing policy on each node, to identify the cause for link load unbalance. Adjust link load accordingly. When necessary, the bearer network needs to
increase the bandwidth allocated to the Gb interface.
Figure 3-19 Analysis and Processing Flow for the Gb-Interface Link Utilization Rate
For the TDM A interface, when the circuit trunk usage exceeds the threshold, first verify that no fault exists with circuits. If the usage still exceeds the threshold after
circuit faults are eliminated, expand A-interface trunk circuits.
For the IP A interface, if the bandwidth usage exceeds the threshold, verify that the link load between several transmission paths is balanced. In case of link load
unbalance, make analysis upon the uplink and the downlink respectively. Check networking schemes of the iBSC, the data bearer network, and the CN, and check the
routing policy on each node, to identify the cause for link load unbalance. Adjust link load accordingly.
The Ater interface only exists in TDM mode. When its circuit trunk usage exceeds the threshold, expand trunk circuits on the Ater interface.
Figure 3-20 Analysis and Processing Flow for the A/Ater-Interface Link Utilization Rate
When the No.7 signaling link load exceeds the threshold, first verify that the load between signaling links is balanced. In case of any link load unbalance, verify that no
signaling link is out of service and the number of signaling links is n power of 2 (2, 4, 8, 16). Under this situation, the load between signaling links can be basically
balanced. If signaling link load is already balanced, you can make expansion by increasing the number of signaling links or transforming 64K signaling links into 2M
signaling links.
Figure 3-21 Analysis and Processing Flow for the No.7 Signaling Link Uplink/Downlink Utilization Rate
3.5.5 Analysis and Processing of the load of control plan on CRP board
The control plan CPU on CRP board (CMP) is in charge of service call control management in PS/CS domains and management of resources on BSSAP and BSSGP
layers and in the system itself. It handles a large number of control-plane messages. If the CMP load is high, it is usually directly related to the high service traffic of
this module, or it may be caused by unreasonable configurations. You can make analysis according to the following procedure:
In LAIs with extremely high paging traffic, you can split LAIs to reduce paging traffic on the A interface. Under the normal situation that the BSC system is attacked by
transient outburst paging traffic (for example, group sending of short messages), the CMP load will be increased transiently and normal service access will be affected.
To avoid impacts of transient attach, the paging flow-control function is configured on the BSC for the sudden increase of paging traffic. With this function, the paging
traffic in a unit time is restricted, so the paging traffic is controlled from the beginning when paging traffic is received. Thus, the problem of high CPU load caused by
high outburst paging traffic can be avoided. When the paging traffic exceeds the threshold, make analysis according to the following flow:
Note: The transient paging attack does not necessarily occur in busy hours, so you need to monitor this indicator all day.
Figure 3-23 Analysis and Processing Flow for BSC Paging Traffic
3.5.7 Analysis and Processing of Utilization rate of Slave resources on the CRP board
In UR13 version, each Slave unit on CRP board is configured to handle CS service and PS service both. Only if the CS service load for all of the systen is high, you
need to expand the CRP board, because the load of CS services can be balanced automatically on each Slave. When utilization rate of slave timeslots for PS services
or Average load of Slave has exceeded the threshold, you can try to adjust some cells to some low utilization rate or load Slaves (less than 60%) firstly. The analysis
and processing flow is shown as follows:
Figure 3-24 Analysis and Processing Flow for Utilization rate of Slave resources
In this section, the board refers to the EGPB, EXGB1a, EXGB1b, EGPB2c, EGPB2a, EDTI, EDTI2a, ESDTI and ESDTI2a boars on the ZXUR9000 platform. The
following indicators are monitored for them: utilization rate of the EGPB board, utilization rate of the EXGB1a\EXGB1b\EGPB2c\EGPB2a board, occupancy of the
transmitting bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards (Abis interface), occupancy of the receiving bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards
(Abis interface), occupancy of the transmitting bandwidth on EDTI/EDTI2a/ESDTI/ESDTI2a boards (Gb interface), occupancy of the receiving bandwidth on
EDTI/EDTI2a/ESDTI/ESDTI2a boards (Gb interface), and PPS utilization rate of the ESDTI/ESDTI2a. These indicators indicate whether the transmitting and receiving
capacity of the corresponding board has exceeded the threshold. If yes, you need to expand the board. The analysis and processing flows for these indicators are
basically the same, as shown below:
Figure 3-25 Analysis and Processing Flow for the Board Utilization Rate
http://127.0.0.1:8890/go_outfiles/Lib20140527134643_R1_1/documents/OK/Capacity%... 2/3/2015