Heavy Traffic During Holidays Emergency Solution: Huawei Technologies Co., LTD

GSM BSC Precautions and Emergency Measures for Large Traffic
Heavy Traffic During Holidays Emergency Solution
Huawei Technologies Co., Ltd.

All rights reserved
2010-12-29
Huawei Technologies Proprietary
Page 1 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic Contents
1 Introduction.................................................................................................................................... 7 2 Optimizing System and Data Configuration Before Festival .............................................. 8

2.1 Overview .......................................................................................................................................................... 8 2.2 Analyzing and Adjusting BSC Performance Before Festival ........................................................................... 8 2.2.1 Important Performance Counters ............................................................................................................ 8 2.3 Adjusting BSC Parameters Before a Festival ................................................................................................. 12 2.3.1 Backing Up Configuration Data............................................................................................................ 12 2.3.2 Adjusting Data Configuration and Availability of the SS7 Signaling Link ........................................... 12 2.3.3 Adjusting Data Configuration of the LAPD Signaling Link ................................................................. 12 2.3.4 Adjusting Data Configuration of the GDPUP ....................................................................................... 13 2.3.5 Adjusting Data Configuration of the GEIUB/GEHUB ......................................................................... 13 2.3.6 Adjusting Paging Parameters ................................................................................................................ 13 2.3.7 Adjusting Random Access Parameters .................................................................................................. 15 2.3.8 SDCCH Dynamic Adjustment .............................................................................................................. 15 2.3.9 Adjusting TCHH Dynamic Adjustment Threshold ............................................................................... 16 2.3.10 Adjusting PDCH Configuration in External PCU Configuration Mode ............................................. 16 2.3.11 Splitting Location Area ....................................................................................................................... 16 2.3.12 Adjusting Parameters About PS Resource Allocation ......................................................................... 17 2.3.13 Adjusting Parameters About PS Cells ................................................................................................. 17 2.3.14 Adjusting Parameters About PS TRXs ................................................................................................ 18 2.3.15 Enabling or Adjusting Paging Message Optimization ........................................................................ 18 2.3.16 Adjusting Parameters About CCCH Load Threshold .......................................................................... 19 2.3.17 Expanding the Capacity of Cells with TCH Congestion ..................................................................... 19
3 Emergency Measures for Traffic Peak .................................................................................... 20

3.1 Final Preparations........................................................................................................................................... 20 3.1.1 Backing Up Configuration Data............................................................................................................ 20 3.1.2 Obtaining Onsite Information ............................................................................................................... 20 3.1.3 Preparing Operation Records ................................................................................................................ 20 3.1.4 Registering Traffic Statistic for 15 Minutes .......................................................................................... 20 3.2 Emergency Measures ..................................................................................................................................... 22 3.3 CPU or LAPD Overload in the GXPUM/GXPUT ......................................................................................... 23 3.3.1 Symptom ............................................................................................................................................... 23 3.3.2 Emergency Measures ............................................................................................................................ 24 3.4 CPU Usage of GSCU in the Configuration of Multiple BM Subracks and One Remote TC Subrack........... 27 3.4.1 Symptom ............................................................................................................................................... 27 3.4.2 Emergency Measures ............................................................................................................................ 28 3.5 DSPP CPU Usage of GDPUP ........................................................................................................................ 28 3.5.1 Symptom ............................................................................................................................................... 28 3.5.2 Emergency Measures ............................................................................................................................ 28
2010-12-29
Page 2 of 29

3.6 Abnormal Decrease of Traffic Volume ........................................................................................................... 29 3.6.1 Symptom ............................................................................................................................................... 29 3.6.2 Emergency Measures ............................................................................................................................ 29
2010-12-29
Page 3 of 29
Tables
Table 3-1 Pre-warning value of each counter ...................................................................................................... 22
2010-12-29
Page 5 of 29
1
This document describes the following aspects:
z z z
Introduction
The drastic increase of traffic volume during a festival or a large gathering greatly impacts normal operation of the BSC6000. For example, the related KPIs such as the paging success rate, assignment success rate, and traffic volume deteriorate and the subscribers face difficulty in making calls. This document is intended for the field engineers to manage the increase in traffic volume to ensure the stable operation of the network.
Optimization of system and configuration data before a festival to prepare for the traffic peak Key performance indicators to check the network for exceptions Emergency measures to handle exceptions to ensure the system safety during the high-traffic-volume period
2010-12-29
Page 7 of 29
2
2.1 Overview
Optimizing System and Data Configuration Before Festival
Before a festival, the field engineers should determine the performance-related defects in the system based on the traffic models, KPIs, alarms, and traffic statistics. The engineers should rectify these defects to maximize the system processing capacity. This chapter provides guidelines for performing these operations.
It may not be possible to have large system capacity and good system quality at the same time. Sometimes it is necessary to compromise on the system quality for a large system capacity. This chapter describes the adjustments to be made for maximizing the system capacity. Therefore, the optimization of system and configuration data before a festival is different from the network optimization. After the traffic peak ends, all the configuration data should be restored. The adjustments affecting the network quality are described in the following.
2.2 Analyzing and Adjusting BSC Performance Before Festival

2.2.1 Important Performance Counters
Traffic Model
All the system specifications of the BSC6000 CS services are based on the following traffic model. Traffic Model for General Subscribers Traffic volume per user in busy hours 2010-12-29 Huawei Technologies Proprietary Value Range 0.02 ERL Page 8 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic Traffic Model for General Subscribers Mean time of a call Ratio of originated calls Ratio of terminated calls Number of location updates in busy hours Number of originated calls in busy hours Number of terminated calls in busy hours Number of sent short messages Number of received short messages Average retransmission of paging Number of times of intra-BSC switching in a busy time Number of times of inter-BSC switching in a busy time Value Range 45s 35% 65% 1.5 0.56 1.04 1 1 0.714 0.9 0.1
In the previous traffic model, the BSC6000 performance can meet the nominal specifications. On the existing network, the actual performance of the BSC6000 may be lower than the nominal specifications. The reason for the low performance is that there are some differences between the onsite traffic model and the standard traffic model. Therefore, it is necessary to determine the differences and the adverse effect of the differences so that appropriate adjustments can be made to the BSC6000 in advance.
KPIs
The field engineers should check the following KPI information. Step 1 Obtain the traffic volume of each subrack and the CPU usage of all boards in each subrack. Each subrack of the BSC6000 supports a traffic volume of 3,000 Erl. The mean CPU usage of the boards should be about 60%. If this ratio is not met, do as follows. Cause of the Problem The traffic load is unbalanced. The traffic model is inconsistent with the standard model. Troubleshooting Method See section 2.3.5 . Expand the capacity
Step 2 Obtain the number of paging messages on the A interface. If the number of paging messages on the A interface is greater than 110,000/location area for 15 minutes, see sections 2.3.6 and 2.3.15 . Step 3 Obtain the number of channel requests of every GEIUB. If the number is greater than 150/s, see section 2.3.7 . 2010-12-29 Huawei Technologies Proprietary Page 9 of 29
The traffic statistics contain only the number of channel requests by cells. Therefore, to obtain the number of channel requests of one GEIUB, you should specify the cells served by each GEIUB, and then add the channel requests of these cells together.
Step 4 Obtain the SDCCH congestion rate of each cell. If the SDCCH congestion rate of one cell is greater than 2%, see section 2.3.8 . Step 5 Obtain the TCH congestion rate of each cell. If the TCH congestion rate is greater than 10%, see sections 2.3.9 and 2.3.10 . Step 6 Calculate the number of cells in each location area. See section 2.3.11 . ----End
Traffic Statistics and Alarms Related to the Performance and Flow Control
The system starts the flow control when the alarms or traffic statistics listed in the following table are generated on site. The segment where the flow control occurs is the bottleneck of the system performance. This section provides guidelines on how to adjust the system based on these alarms and traffic statistics to reduce the severity of the flow control. Step 1 Check whether the LAPD flow control occurs. If the alarms listed in the following table are generated and if the values of the counters are not 0, you can infer that the LAPD flow control occurs. See section 2.3.3 . Short Name of Counter A530 Type Traffic measureme nt Description Paging Measurement/ Measurement of Discarded Paging Messages due to Overload per LAPD/ SM Pagings Discarded on LAPD Link A531 Traffic measureme nt Paging Measurement/ Measurement of Discarded Paging Messages due to Overload per LAPD/ CS Pagings Discarded on LAPD Link A532 Traffic measureme nt Paging Measurement/ Measurement of Discarded Paging Messages due to Overload per LAPD/ PS Pagings Discarded on LAPD Link L5012 Traffic measureme nt Alarm LAPD Measurement/ LAPD Link Measurement/ I Frames Discarded by LAPD Link LAPD Link Congestion
21001
Step 2 In A over TDM mode, check whether the MTP3 flow control occurs. If the alarms listed in the following table are generated and if the value of the counter is not 0, you can infer that the MTP3 flow control occurs. See section 2.3.2 . 2010-12-29 Huawei Technologies Proprietary Page 10 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic Short Name of Counter L6016 Type Traffic measurement Description MTP3 Measurement/ MTP3 Link Measurement/ Discarded MSUs during Link Congestion 21502 21504 21518 Alarm Alarm Alarm MTP3 Layer 3 Congestion MTP3 Layer 2 Congestion MTP3 Link Layer 3 Congestion Released
Step 3 Check whether the paging channel is overloaded. If the values of L3188L and L3188C are not 0 or if L3188M is greater than 95%, you can infer that the PCH is overloaded. See sections 2.3.6 and 2.3.16 . Short Name of Counter L3188L Type Traffic measureme nt Traffic measureme nt Description Call Measurement/ Flow Control Measurement per Cell/ Paging Messages Discarded from the PCH Queue Call Measurement/ Flow Control Measurement per Cell/ MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface Call Measurement/ Flow Control Measurement per Cell/ Maximum Seizure Ratio of PCH Paging Queue
L3188C
L3188M
Traffic measureme nt
Step 4 Check whether the RACH is overloaded. If the value of L3188B is not 0, you can infer that the RACH is overloaded. See sections 2.3.7 and 2.3.16 . Short Name of Counter L3188B Type Traffic measureme nt Description Call Measurement/ Flow Control Measurement per Cell/ MSG CCCH LOAD IND (RACH) Messages Sent on Abis Interface
Step 5 Check whether the DSP overload alarm is generated. If the DSP overload alarm is generated, see sections 2.3.12 , 2.3.13 , and 2.3.14 . ----End 2010-12-29 Huawei Technologies Proprietary Page 11 of 29
2.3 Adjusting BSC Parameters Before a Festival

2.3.1 Backing Up Configuration Data
To ensure that the adjusted data can be restored after the traffic peak comes to an end, you should back up the configuration data. Alternatively, you can keep a record of the parameter adjustment for the convenience of data recovery after festival.
2.3.2 Adjusting Data Configuration and Availability of the SS7 Signaling Link
Requirements
1. You can calculate the number of SS7 signaling links required on site by using the calculation tool. For details on the calculation tool, see section 2.2.1 . If the number of SS7 signaling links on site is smaller than the number calculated by the tool, increase SS7 signaling links. Two methods can be used to increase SS7 signaling links: change 64 kbit/s links into 2 Mbit/s links and adopt multiple signaling points. Set the priorities of all the links to the same if the signaling link priority can be configured at the MSC. In each BM subrack, the 64 kbit/s low-speed signaling links should be evenly distributed over the XPUMs or XPUTs. The 2 Mbit/s high-speed signaling links should be distributed in multiple BM subracks. In a BM subrack, the 2 Mbit/s high-speed signaling links should be configured on the XPUM or XPUT with the minimum load. In the case of R8C01, you are advised to configure the 2 Mbit/s links to the XPUM CPU0. In the case of R8C12, you are advised to configure the 2 Mbit/s links to the XPUM CPUP. The 2 Mbit/s signaling links and 64 kbit/s signaling links should not be configured in the same linkset.
2. 3. 4.
5.
Description
Prevent the overload of the SS7 signaling links while ensuring the maximum load capacity. 1. When the traffic volume of PS services is large, the SS7 signaling links must not be configured on CPU0 of the GXPUM.
2.3.3 Adjusting Data Configuration of the LAPD Signaling Link

Procedure
The principles of configuring the LAPD links over the Abis interface in non-IP transmission mode are as follows: 1. 2. Avoid multiplexing multiple primary BCCH links on the same timeslot. Do not use the 4:1 networking mode when the transmission resources are sufficient.
2010-12-29
Page 12 of 29
Description
This modification prevents the LAPD link congestion, but decreases the utilization of the resources over the Abis interface.
2.3.4 Adjusting Data Configuration of the GDPUP

Procedure
1. 2. Adjust the BTS configuration. Ensure that the traffic volumes of PS services are evenly distributed over CPU0 of each GXPUM in all the subracks. Based on the number of GPRS cells to be served, configure sufficient GDPUPs. Ensure that the services in the cells that are configured on the subrack are processed by the GDPUPs in the subrack.
Description
1. 2. After cells are distributed over subracks, PDCHs may not be able to be activated because of insufficient GDPUPs. If the services in a cell are processed by multiple subracks, extra inter-subrack resources are required. Many cross-subrack cells may affect the number of activated Abis sublinks.
2.3.5 Adjusting Data Configuration of the GEIUB/GEHUB

Procedure
1. 2. Adjust the distribution of BTSs over the GEIUBs/GEHUBs. Ensure that the traffic volume of each GEIUB/GEHUB is basically the same. More than two ports on each GEHUB should be used. This prevents the failure of LAPD links due to broken Ethernet cables.
Description
Prevent the overload of the GEIUBs/GEHUBs.
2.3.6 Adjusting Paging Parameters

Procedure
1. 2. Set the number of paging message retransmissions to one at the MSC. At the MSC, set the interval between the first paging and second paging to 8 seconds. (For the Ericsson MSC, the parameter that determines the interval is Time supervision for the first page in one LA.)
In the case of G6 MSC, you are advised to set the interval to 5 seconds (maximum value). Huawei G3 and G9 MSC support the interval of greater than 5 seconds. At the G9 MSC, run MOD PGCTRL to modify the interval. At the G3 and G6 MSC, set the corresponding software parameter to modify the interval.
3.
At the MSC, set the parameters and ensure the following conditions: the first paging message uses the TMSI and the second paging message uses the IMSI; neither of the two paging messages carries the Channel Needed IE; the paging messages are sent according to location areas; the paging of the entire network can be disabled if necessary. Huawei Technologies Proprietary Page 13 of 29
2010-12-29
GSM BSC Precautions and Emergency Measures for Large Traffic 4. 5. 6. 7. Use non-BCCHs if radio resources are sufficient. Choose Cell Attribute Parameter > Idle Mode > Basic Idle Parameters > BS_AG_BLKS_RES. Set BS_AG_BLKS_RES to 1. Choose Cell Attribute Parameter > Idle Mode > Basic Idle Parameters > BS-PA-MFRARMS. Set BS-PA-MFRARMS to 2. Choose Cell Attribute Parameter > Other Property Parameters > Advanced Parameters> Public Channel Control > CCCH Load Threshold. Set CCCH Load Threshold to 100. Choose Cell Attribute Parameter > Call Control Parameters > Basic Call Control Parameters > MS MAX Retrans. Set MS MAX Retrans to 1. Choose Cell Attribute Parameter > Call Control Parameters > Basic Call Control Parameters > Paging Times. Set Paging Times to 1.
8. 9.
10. Choose Configure BSC Attributes > Software Parameters > A Interface Collaboration Paging Switch. Set A Interface Collaboration Paging Switch to Close.
Description
1. 2. 3. Observe the result after each step is performed. If the problem is solved, you need not perform the subsequent steps Steps 1 through 3 are performed at the MSC. After these steps are performed, the paging load on the GEIUBs decreases. The paging success ratio, however, decreases. If the interval between the first paging and second paging at the MSC is less than 5 seconds and cannot be modified, you are advised to set the BTS lifetime (software parameter 29) to 1 for each cell in step 2. To set the BTS lifetime, log in as the super user and choose Cell Attribute Parameter > Other Property Parameters > Advanced Parameters > BTS Soft Parameters > Software Parameter 29.
Software Parameter 2010-12-29
Paging lifetime
Default value: 255, indicating 5
Effective range [8, 80] with the
Paging message processing period at the Page 14 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic 29 seconds unit 250 ms BTS
The relation between the paging interval at the MSC and the software parameter 29 is as follows: Paging Interval at the MSC (s) Software parameter 29 (250ms) <=3 8 4 12 >=5 255
4. 5.
Steps 4 through 9 are performed at the BSC. After these steps are performed, the paging capabilities of all the cells are maximized. You can perform step 10 if the BSC does not require the A interface paging coordination function. This prevents the sending of the CS paging messages to CPU0 of the GXPUM.
2.3.7 Adjusting Random Access Parameters

Procedure
Choose Cell Attribute Parameter > Other Property Parameters > Advanced Parameters > T3122(s). Set T3122(s) to 30 s. When you choose Cell Attribute Parameter > Idle Mode > Period of Periodic Location Update(6 minutes), check the value on the CN side. You are advised to set this value 10 minutes less than the value on the CN side.
Description
This adjustment prevents the frequent reporting of invalid access requests, but prolongs the MS access time.
2.3.8 SDCCH Dynamic Adjustment

Procedure
1. 2. 3. Choose Cell Attribute Parameter > Basic Attribute Parameters > SD Dynamic Allocation Allowed. Set SD Dynamic Allocation Allowed to Yes. Choose Cell Attribute Parameter > Channel Parameters > Basic Parameters > TCH Minimum Recovery Time (s). Set TCH Minimum Recovery Time (s) to 600. If SD Dynamic Allocation Allowed has been set to Yes, you are advised to add one static SDCCH in the cell.
Description
This adjustment can prevent high SDCCH congestion rates, but decreases the number of available TCHs. Thus, the TCH congestion rate and the CPU usage of the GXPUM/GEIUB may increase. When enabling or disabling the SDCCH dynamic adjustment function, you should take all the factors into consideration. 2010-12-29 Huawei Technologies Proprietary Page 15 of 29
2.3.9 Adjusting TCHH Dynamic Adjustment Threshold

Procedure
Choose Cell Attribute Parameter > Channel Parameters > Advanced Parameters > HWII Channel Allocation and Radio Channel Control > TCH Traffic Busy Threshold. Set TCH Traffic Busy Threshold to 60.
Description
This adjustment increases the number of available TCHs, thus preventing high TCH congestion rates. It, however, leads to the increase in the CPU usage of the GXPUM/GEIUB. Therefore, when adjusting the TCH traffic busy threshold, you should take all the factors into consideration.
2.3.10 Adjusting PDCH Configuration in External PCU Configuration Mode

Procedure
1. 2. For a GPRS-enabled cell, configure one static PDCH. Configure the same cells for the RPPU and the corresponding GMPS/GEPS. Ensure that the GMPS/GEPS is connected to the subrack where the RPPU is located.
Description
Through the adjustment, CS and PS resources are reasonably assigned. This prevents the waste of resources due to unreasonable configurations.
2.3.11 Splitting Location Area

Requirements
1. 2. 3. The maximum number of cells configured in one location area should not exceed 300. Ensure that the number of cells in one location area is not greater than 256. The maximum number of TRXs configured in one location area should not exceed 1,024. The principle of splitting a location area is as follows: One location area must be served by only one BSC, one interface board, and one subrack.
Description
1. 2. Many cells in one location area cause high traffic volumes to the GEIUB. Many TRXs in one location area may incur paging overload. Thus, calls cannot be made and the traffic volume decreases.
2010-12-29
Page 16 of 29
2.3.12 Adjusting Parameters About PS Resource Allocation

Requirements
1. 2. 3. Choose Configure BSC Attributes > Software Parameters > Allow E Down G Up Switch. Set Allow E Down G Up Switch to Open. Choose Configure BSC Attributes > Software Parameters > Reassignment TBF for Different Trx. Set Reassignment TBF for Different Trx to Not Allow if required. Choose Configure BSC Attributes > Software Parameters > Force MS to Phase2 Function Switch. Set Reassignment TBF for Different Trx to Not Force if required.
Description
1. When Allow E Down G Up Switch is set to Close, a channel cannot be configured with uplink GPRS TBF if the channel is configured with downlink EDGE TBF. The search overhead increases during the resource allocation. Therefore, unless otherwise specified, Allow E Down G Up Switch should be set to Close. When Reassignment TBF for Different Trx is set to Allow, the search overhead during PS channel assignment increases. Therefore, Reassignment TBF for Different Trx should be set to Not Allow if required. If Reassignment TBF for Different Trx is set to Not Allow, a TBF over another TRX cannot be assigned. In the internal procedure, the system needs to process more messages between the GXPUM and the GDPUP during two-phase access than those during one-phase access.
2.
3.
2.3.13 Adjusting Parameters About PS Cells

Requirements
1. Setting the following parameters for network optimization Choose GPRS Attributes > PS Network Optimization Parameters > Release Delay of Non-extended Uplink TFB(ms). If the value of Release Delay of Non-extended Uplink TFB(ms) is less than 120, set it to 120. If the value is greater than or equal to 120, retain the original value. Choose GPRS Attributes > PS Network Optimization Parameters > Inactive Delay of Extended Uplink TFB(ms). If the value of Inactive Delay of Extended Uplink TFB(ms) is less than 2000, set it to 2000. If the value is greater than or equal to 2000, retain the original value. Choose GPRS Attributes > PS Network Optimization Parameters > Release Delay of Downlink TFB(ms). If the value of Release Delay of Downlink TFB(ms) is less than 2000, set it to 2000. If the value is greater than or equal to 2000, retain the original value. 2. Checking and setting the following PS channel management parameters Based on the number of TRXs and historical traffic statistics, ensure the following settings: Choose GPRS Attributes > PS Channel Management Parameters > Timer of Releasing Idle Dynamic Channel. Set Timer of Releasing Idle Dynamic Channel to a value greater than or equal to 20. Choose GPRS Attributes > PS Channel Management Parameters > Timer of Releasing Abis Timeslot. Set Timer of Releasing Abis Timeslot to a value greater than or equal to 10. 2010-12-29 Huawei Technologies Proprietary Page 17 of 29
Description
1. To test the throughput of PS services, you must set both Uplink Fixed CS Type and Downlink Fixed CS Type to CS4 for GPRS cells, and set both Uplink Fixed MCS Type and Downlink Fixed MCS Type to MCS9 for EDGE cells. When the coding scheme is fixed, the DSPP of the GDPUP requests the GXPUM for channels even if the transmission quality on the Um interface cannot meet the requirements (for example, MCS9). The application requires extra overhead. Therefore, the coding scheme should be set to UNFIXED. For the PS signaling plane, the system performance depends on the capability of the CPU0 in the GXPUM, which processes the channel requests triggered by the uplink and downlink TBF establishments. Therefore, you can adjust the parameters about network optimization to ensure that the uplink and downlink TBFs are not released. Thus, the load of the CPU0 in the GXPUM decreases. The parameter Maximum Ratio Threshold of PDCHs in a Cell correlates with the PS cell distribution algorithm and maximum number (set to 48 at present) of PDCHs activated on DSP. If more than six TRXs are configured for a cell, Maximum Ratio Threshold of PDCHs in a Cell should not be set to a great value because the cell may not be normally distributed or channels cannot be activated.
2.
2.3.14 Adjusting Parameters About PS TRXs

Requirements
Choose Configure TRX Attributes > Base Attribute Setting > MaxAbisTSOccupied. Set MaxAbisTSOccupied to 32.
Description
When MaxAbisTSOccupied for EDGE TRXs is less than 32 and that for GPRS TRXs is less than 16, the channel sublinks may be unevenly distributed even if sufficient idle timeslots are configured. If an MS occupies multiple PDCHs and sublinks are unevenly distributed, the corresponding DSPP may request the GXPUM for sublinks. Thus, extra signaling overhead is required.
2.3.15 Enabling or Adjusting Paging Message Optimization

Requirements
1. Choose Configure Cell Attributes > Other Attributes > Cell Soft Parameters > Paging Messages Optimize at Abis Interface. Set Paging Messages Optimize at Abis Interface to Forced turn on (default value). Choose Configure Cell Attributes > Other Attributes > Cell Soft Parameters > Paging Numbers of one Optimizing Msgs. Set Paging Numbers of one Optimizing Msgs to a large value.
2.
Description
1. The BTS should support the Paging Messages Optimize at Abis Interface function. After the function is enabled, check whether the Abis Cell Pack Page Command is sent over the Abis interface. If the extended BCCH is configured, the pre-warning is generated as follows: Huawei Technologies Proprietary Page 18 of 29
2. 2010-12-29
GSM BSC Precautions and Emergency Measures for Large Traffic Pre-Warning Name Abnormal Paging Messages Optimize at Abis Interface function on the extended BCCH due to software bugs Pre-Warning Description Version Involved Resolving Avoidance Measures Version Set Paging Messages Optimize at Abis Interface of the cell to Forced turn-off.
The Paging Messages BTS3000V100R0 To be Optimize at Abis Interface 08C01&C11, and specified later versions function is abnormal. In the case of the extended BCCH, the paging message is delivered to the incorrect channel. Thus, the paging success rate severely drops.
3.
When the Paging Messages Optimize at Abis Interface function is enabled, the CPU usage of the GXPUM/GEIUB may increase. Therefore, when enabling or disabling this function, you should take all the related factors into consideration.
2.3.16 Adjusting Parameters About CCCH Load Threshold

Requirements
Choose Configure Cell Attributes > Other Attributes > CCCH Load Threshold. Set CCCH Load Threshold to 100.
Description
The CCCH load threshold is used when the BTS notifies the BSC of the load on the CCCH timeslot. If the value of the CCCH Load Threshold increases, the number of CCCH load indication messages sent by the BTS to the BSC decreases. Thus, the traffic flow on the Abis interface decreases.
2.3.17 Expanding the Capacity of Cells with TCH Congestion

Requirements
You should expand the capacity of the cell in which the TCH congestion rate exceeds 20%.
Description
You should expand the capacity of the cells that have high congestion rates, so that the congestion on the Um interface in these cells during festival decreases.
2010-12-29
Page 19 of 29
Emergency Measures for Traffic Peak
3.1 Final Preparations

3.1.1 Backing Up Configuration Data
Back up the configuration data to ensure that the adjusted data can be restored after the traffic peak.
3.1.2 Obtaining Onsite Information

Obtain onsite information, including the mapping between the BSC and LAC and the existing VIP BTSs.
3.1.3 Preparing Operation Records

Print an operating record sheet to record the operating time and the operating content.
3.1.4 Registering Traffic Statistic for 15 Minutes

The traffic statistics about the counters (in the following table) in the latest 15 minutes should be taken before the traffic peak. Short Name of Counter ZK3014 Description BSC Measurement/ Access measurement per BSC/ Traffic Volume on TCH per BSC (Traffic Channel) A0300 Paging Measurement/ A Interface Paging Measurement/ MSC-Initiated Paging Requests for CS Service AR9702 System Load Measurement/ CPU Usage Measurement/ Average CPU Usage
2010-12-29
Page 20 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic Short Name of Counter RL6021 Description MTP3 Measurement/ MTP3 Link Measurement Ratio of Transmit Bandwidth to Total Bandwidth ZCA300J BSC Measurement/ Access measurement per BSC/ Immediate Assignment Requests per BSC A0301/A31 Paging Measurement/ SGSN-Initiated Paging Requests for CS Service SGSN-Initiated Paging Requests for PS Service A9001 /A9101 /A9201 /A9301 PS Call Measurement /Uplink GPRS TBF Establish and Release Capability Measurement per Cell /Number of Uplink GPRS TBF Establishment Attempts PS Call Measurement /Downlink GPRS TBF Establish and Release Capability Measurement per Cell /Number of Downlink GPRS TBF Establishment Attempts PS Call Measurement /Uplink EGPRS TBF Establish and Release Capability Measurement per Cell /Number of Uplink EGPRS TBF Establishment Attempts PS Call Measurement /Downlink EGPRS TBF Establish and Release Capability Measurement per Cell /Number of Downlink EGPRS TBF Establishment Attempts A9401 /A9404 PS Call Measurement /Packet Access Capability Measurement /Number of 8-Bit Packet Channel Requests Received on CCCH Number of 11-Bit Packet Channel Requests Received on CCCH R94 DSP Measurement /DSP CPU Performance Measurement /Average DSP CPU Usage (%)
2010-12-29
Page 21 of 29
3.2 Emergency Measures

Table 3-1 Pre-warning value of each counter Traffic Measurement Counter Traffic Volume on TCH per BSC (Traffic Channel) MSC-Initiated Paging Requests for CS Service or SGSN-Initiated Paging Requests for CS Service (GS Interface) Average CPU Usage 70% or 80% Pre-Warning Value 2500 Erl/subrack 110,000/locati on area Remarks The pre-warning value of the traffic volume in each subrack is 2500 Erl every 15 minutes. The BSC6000 paging processing capability is 120/s, that is, 108,000 every 15 minutes. If the BSC serves n location areas, the number of MSC Paging Requests per location area is approximately equal to the total number of MSC-Initiated Paging Requests for CS Service or SGSN-Initiated Paging Requests for CS Service (GS Interface) divided by n. If the average usage of CPU0 in the GXPUM exceeds 70% or if the average CPU usage of any other board exceeds 80%, you should take emergency measures. None.
Ratio of Transmit Bandwidth to Total Bandwidth Immediate Assignment Requests per BSC Number of TBF Establishment Requests (including uplink and downlink GPRS TBFs and uplink and downlink EDGE TBFs by subrack) Under PS Call Measurement Number of Packet Channel Requests (including Number of 8-Bit Packet Channel Requests Received on CCCH and Number of 11-Bit Packet Channel Requests Received on CCCH by subrack)
55%
145000/subrac k 1260000/subra ck
Equivalent to BHCA. The specification for the BSC6000 is 2340K, that is, 145,000 every 15 minutes for a single subrack. 1400/s for a single subrack, that is, 1260000 for 15 minutes in a single subrack
360000/subrac k
400/s for a single subrack, that is, 360,000 for 15 minutes in a single subrack
2010-12-29
Page 22 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic Traffic Measurement Counter Average CPU Usage of DSPP Pre-Warning Value 80% Remarks Check the counter "Average DSP CPU Usage" of all DSPPs for all GDPUPs under the BSC. Any board whose counter "Average DSP CPU Usage" exceeds the pre-warning value should be processed.
When one counter in Table 3-1 exceeds the pre-warning value, you can infer that the system load is heavy. Take emergency measures immediately. Start the intra-net MS originated and MS terminated call test in the BSC immediately (at least 20 times). If it is difficult to make calls (10 failed calls out of 20 calls), take emergency measures immediately. If calls can be made temporarily, make a test call once a minute until the previous counters are less than the per-warning values. If you acknowledge that the call failure occurs, perform the emergency measures at once. The emergency measures are as follows: 1. 2. Determine the symptom of system overload. Based on the phenomenon, troubleshoot the fault accordingly.
The following sections in this chapter provide guidelines for you to take these emergency measures.
3.3 CPU or LAPD Overload in the GXPUM/GXPUT

3.3.1 Symptom
1. The traffic statistics in the latest 15 minutes show that the average usage of CPU0 in the GXPUM exceeds 70%, or that the average usage of any one of CPU1, CPU2, and CPU3 in the GXPUM exceeds 80%, or that the average usage of any one of CPU0, CPU1, CPU2, and CPU3 in the GXPUT exceeds 80%. A query of active alarms shows that the LAPD overload alarm is generated and is not cleared for a long time (more than five minutes). A query of history alarms shows that the CPU overload alarm or LAPD overload alarm is reported several times in the latest five minutes.
The CPU overload alarm that is based on the CPU transient usage is generated and cleared randomly. Therefore, no specific number of alarms can be used to determine whether there is the overload problem. You can calculate the duration of every alarm (the interval between the clearing of an alarm and the generation of the alarm). Add all the duration of all the alarms in 5 minutes. If the duration exceeds two minutes, you can infer that the GXPUM is overloaded.
2. 3.
4.
Check the traffic statistics of MSC-Initiated Paging Requests for CS Service and Immediate Assignment Requests per BSC in the latest 15 minutes. Compared with the normal values of MSC-Initiated Paging Requests for CS Service and of Immediate Assignment Requests per BSC, the measured values may incur a sharp increase. In this case, take emergency measures.
2010-12-29
Page 23 of 29
3.3.2 Emergency Measures

Step 1 Use the CPU usage monitoring function on the LMT to monitor the CPU (CPU0 through CPU3) usage of the GXPUM/GXPUT. In this way, you can easily observe the effect of emergency measures. Step 2 The configurable measurement object NCELL has a great impact on the CPU usage of the GXPUM. When taking emergency measures to solve high-traffic problems, you are advised to delete all the configurable measurement objects registered with each BSC connected to the M2000. To delete the configurable measurement objects, do as follows: Log in to the M2000 client. Choose, Performance > Measure Management > Measurement Settings.
Delete all the measurement objects from GSM cell-GSM cell and Neighbor cell under each BSC.
2010-12-29
Page 24 of 29
Wait for 15 minutes. Then, check whether the CPU usage of the GXPUM is within the normal range. That is, the usage of CPU0 is less than 70%, and the usage of CPU1 through CPU3 is less than 80%. If the usage of all the four CPUs is within the normal range, terminate the processing. If the usage is not within the normal range, go to the next step. Step 3 If the CPU of the GXPUM/GXPUT is overloaded, choose Configure Cell Attributes > Handover Data > Advanced. Set MR.Preprocessing to Yes and Sent Freq. of preprocessed MR to Once every two second. Then, check whether the LAPD overload alarm is cleared or whether the CPU usage is lower than 80%. If the result is normal, terminate the processing. If the result is not normal, go to the next step.
In the case of the BTS version earlier than BTS3000V100R001C07, disable the HW III power control function before you enable the MR preprocessing.
Step 4 Check the traffic statistics about MSC Paging Requests (Circuit Service) in the latest 15 minutes. If the number is greater than twice the normal value, choose Configure Cell Attributes > Call Control > Basic Call Control Parameters, and then set Paging Times to 1 to reduce the number of paging messages sent. Disable the MSC second paging. Configure the MSC to initiate paging by TMSI. Set the MSC paging response timer to 10 seconds. After the previous modification, check whether the CPU usage of the XPUM/XPUT drops to be in the normal range. That is, the usage of XPUM CPU0 is less than 70%, the usage of XPUM CPU1 through CPU3 is less than 80%, or the usage of XPUT CPU0 through CPU3 is less than 80%. If the usage of all the four CPUs is within the normal range, the fault is rectified. Otherwise, go to the next step.
2010-12-29
Page 25 of 29
These parameters are set on the MSC.
Step 5 Check the traffic statistics about Immediate Assignment Requests per BSC in the latest 15 minutes. If the value is greater than three times the normal value, choose Configure Cell Attributes > Call Control > Basic Call Control Parameters, and then set Paging Times to 1 to reduce the number of requests retransmitted by MSs. After the previous modification, check whether the CPU usage of the XPUM/XPUT drops to be in the normal range. That is, the usage of XPUM CPU0 is less than 70%, the usage of XPUM CPU1 through CPU3 is less than 80%, or the usage of XPUT CPU0 through CPU3 is less than 80%. If the usage of all the four CPUs is within the normal range, the fault is rectified. Otherwise, go to the next step. Step 6 Check the traffic statistics about Immediate Assignment Requests per BSC in the latest 15 minutes. If the value is greater than three times the normal value, you should increase the length of timers T3122 and T3212. Timer T3122 determines the interval between the time the MS receives the immediate assignment reject message and the time the MS retransmits an access request message. To increase the length of timer T3122, choose Configure Cell Attributes > Other Attributes > Cell Timers, and then set T3122(s) to 30. To increase the length of timer T3212, choose Configure Cell Attributes > Idle Mode, and then set Period of Periodic Location Update(6 minutes) to 40.After the previous modification, check whether the CPU usage of the XPUM/XPUT drops to be in the normal range. That is, the usage of XPUM CPU0 is less than 70%, the usage of XPUM CPU1 through CPU3 is less than 80%, or the usage of XPUT CPU0 through CPU3 is less than 80%. If the usage of all the four CPUs is within the normal range, the fault is rectified. Otherwise, go to the next step. Step 7 Check the total number of Immediate Assignment Requests per BSC in the latest 15 minutes. If the number is greater than three times the normal value, adjust the ratio of TCHFs to TCHHs. Choose Cell Attribute Parameter > Channel Parameters > Advanced Parameters > HWII Channel Allocation and Radio Channel Control > TCH Traffic Busy Threshold. Set TCH Traffic Busy Threshold to 30. Then, check whether the LAPD overload alarm is cleared or whether the CPU usage is lower than 80%. If the result is normal, terminate the processing. If the result is not normal, go to the next step. Step 8 Choose Cell Attribute Parameter > Basic Attribute Parameters > SD Dynamic Allocation Allowed. Set SD Dynamic Allocation Allowed to No. Step 9 Choose Configure BSC Attributes > Flow Control Data > Channel Request Max Message Number In Period. Set Channel Request Max Message Number In Period against 300/subrack on the basis of the configuration. Step 10 Choose BSC Attributes > Flow Control Data > Pg Max Message Number In Period. Set Pg Max Message Number In Period to 100 for a BSC that controls a single location area and to 140 for a BSC that controls multiple location areas. Step 11 If Number of TBF Establishment Requests Under PS Call Measurement or Number of Packet Channel Requests in a certain subrack exceeds the pre-warning value, perform the following operations: Choose GPRS Attributes > PS CS Parameters. Set both Uplink Fixed CS Type and Downlink Fixed CS Type to CS2, and set both Uplink Fixed MCS Type and Downlink Fixed MCS Type to MCS2. You should batch modify the coding schemes of 10% of the total cells served by a subrack each time. For example, if the subrack serves 200 cells, you should batch modify the coding schemes of 20 cells at a time. Ensure that the Abis sublink application is not triggered. In this way, the load of CPU0 in the GXPUM is in the normal range (below 70%) at the expense of the single-user bandwidth. Step 12 If Number of TBF Establishment Requests Under PS Call Measurement exceeds the pre-warning value, choose BSC Attributes > Inner Software parameters, and then set 2010-12-29 Huawei Technologies Proprietary Page 26 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic PsResReqMsgNumInPeriod to a proper value. When setting PsResReqMsgNumInPeriod, adhere to the following principle: reduce the number of PsResReqMsgNumInPeriod by 10% each time and ensure that PsResReqMsgNumInPeriod per subrack is at most 1,400. In this way, the load of CPU0 in the GXPUM drops to be in the normal range (below 70%) at the expense of part network capacity. Step 13 If Number of Packet Channel Requests of a single subrack exceeds the pre-warning value, choose Configure BSC Attributes > Flow Control Data, and then set Channel Request PS Domain Average Message Number of CPU0 In Period to a proper value. When setting Average Message Number of CPU0 In Period, adhere to the following principle: reduce the number by 10% each time and ensure that the Channel Request PS Domain Average Message Number of CPU0 In Period per subrack is at most 400. In this way, the load of CPU0 in the GXPUM drops to be in the normal range (below 70%) at the expense of part network capacity. Step 14 Block some cells and recover these cells according to the recovery of traffic volume.
During the traffic peak, if the transmission network is faulty, many BTS links are broken. When the fault is rectified, the BTS service recovers at the same time. Many subscribers update their location at this moment, which leads to the overload of GXPUM/GXPUT and frequent reset. Block some cells first. After some subscribers complete the location update, unblock the blocked cells. Perform the same operations until the services of all the cells are restored. Step 15 Shut down the authentication and encryption.(modified on the MSC) Step 16 Remove the half-rate speech from the APCOOL at the MSC to disable the half-rate function. Step 17 If the CPU usage of the GXPUM is still beyond the normal range after you perform all the previous operations, block the cells under the non-VIP BTSs controlled by the BSC one by one until the CPU usage of the GXPUM falls in the normal range. ----End
3.4 CPU Usage of GSCU in the Configuration of Multiple BM Subracks and One Remote TC Subrack
3.4.1 Symptom
1. 2. The traffic statistics in the latest 15 minutes show that the average CPU usage of the GSCU exceeds 80%. A query of history alarms shows that the CPU overload alarm is reported several times in the latest five minutes.
2010-12-29
Page 27 of 29
The CPU overload alarm that is based on the CPU transient usage is generated and cleared randomly. Therefore, no specific number of alarms can be used to determine whether there is the overload problem. We can calculate the duration of every alarm (the interval between the clearing of an alarm and the generation of a new alarm). Add all the duration of all the alarms in 5 minutes. If the duration exceeds two minutes, you can infer that the GSCU is overloaded.

Step 1 Use the CPU usage monitoring function of the LMT to monitor the CPU usage of the GSCU in real time. In this way, you can easily observe the effect of emergency measures. Step 2 Choose Cell Attribute Parameter > Basic Attribute Parameters > SD Dynamic Allocation Allowed. Set SD Dynamic Allocation Allowed to No. Step 3 Choose Configure Cell Attributes > Other Attributes > Cell Timers > T3122(s). Set T3122(s) to 30. Choose Cell Attribute Parameter > Idle Mode > Period of Periodic Location Update(6 minutes). Set Period of Periodic Location Update(6 minutes) to 40. Step 4 Choose Configure BSC Attributes > Flow Control Data > Channel Request Max Message Number In Period. Set Channel Request Max Message Number In Period against 200/subrack on the basis of the configuration. Step 5 Choose Cell Attribute Parameter > Idle Mode > Basic Idle Parameters > Tx-integer. Increase the value of Tx-integer. ----End
3.5 DSPP CPU Usage of GDPUP

3.5.1 Symptom
The traffic statistics in the latest 15 minutes show that the average DSP CPU usage per DSPP exceeds 80%.

Step 1 Use the CPU usage monitoring function of the LMT to monitor in real time the CPU usage of the DSPP whose CPU usage is too high. In this way, you can easily observe the effect of emergency measures. Step 2 Run the DSP PSCELL command to obtain the information about the cell distribution. Then, record the information (subrack number, slot number, and DSP number) about the idle DSP. Step 3 Run the DSP PSRES command to obtain the information about the activated PDCHs and cells on the DSPs. Then, record the information (subrack number, slot number, and DSP number) about the light-loaded DSPs. Step 4 Run the SET PSCELLTODSP command to transfer the cells on the heavy-loaded DSPs to the idle DSPs or light-loaded DSPs. Step 5 Observe the DSPs involved in the adjustment and ensure that the average CPU usage of all the DSPs is smaller than 80%. Step 6 Add GDPUPs if idle DSPs or light-loaded DSPs are not obtained. 2010-12-29 Huawei Technologies Proprietary Page 28 of 29
GSM BSC Precautions and Emergency Measures for Large Traffic ----End
3.6 Abnormal Decrease of Traffic Volume

3.6.1 Symptom
Observe the traffic statistics of the Traffic Volume on TCH per BSC (Traffic Channel) counter described in chapter 2. Compare the current traffic volume with that in the previous normal period. If the traffic volume decreases drastically (at least 20%), you should take emergency measures.

Step 1 Shut down MSC secondary paging. Initiate paging by TMSI. Set the MSC paging response timer to 10s. Check whether the traffic volume is normal after the modification. If the traffic volume is normal, terminate the processing. If the traffic volume is not normal, go to the next step.
These parameters are set on the MSC.
Step 2 Choose Cell Attributes > GPRS Attributes > PS Channel Management Parameters > Maximum Ratio Threshold of PDCHs in a Cell. Reduce the value of Maximum Ratio Threshold of PDCHs in a Cell by 10% each time (the maximum value 50). Check whether the traffic volume is normal after the modification. If the traffic volume is normal, terminate the processing. If the traffic volume is not normal, go to the next step. Step 3 Choose Configure Cell Attributes > Set Cell Properties > GPRS Support. Then, disable the GPRS Support function. Check whether the traffic volume is normal after the modification. If the traffic volume is normal, terminate the processing. If the traffic volume is not normal, go to the next step. Step 4 Based on the traffic status, block the cells of some non-VIP BTSs by 10% of the total number of cells each time. ----End
2010-12-29
Page 29 of 29

Heavy Traffic During Holidays Emergency Solution: Huawei Technologies Co., LTD

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Heavy Traffic During Holidays Emergency Solution: Huawei Technologies Co., LTD

Hochgeladen von

Copyright:

Verfügbare Formate

GSM BSC Precautions and Emergency Measures for Large Traffic