Академический Документы
Профессиональный Документы
Культура Документы
Level:
www.huawei.com
Content
1
Parameter Adjusting
Emergency Measures
Huawei Confidential
Page 2
Before Event
Resource
Capacity
Assessment
Forecast traffic
model.
Assess the
network
resources
Accurately
predict the future
traffic
Reasonably
allocate the
network
resources.
Equipment
Health Check
Carry out health
check.
Inspect
equipment
find the problem,
Clear network
risks
After
Event
Network
Adjust &
Optimization
Develop
adjustment plan
Implement the
adjustment
solution.
Emergency
Spare Parts
Assurance
Adjustment
Event Onand
Summary
duty
Scheme
Support
Design
Provide expert
Restore the
Design emergency Spare parts
technical support on temporarily
assessment and
hand book
site
modified network
Develop
planning
parameters
Order management Real-time network
contingency plan
Summarize.
Perform drill if it is Spare parts supply alarm and KPI
monitoring and
Warehousing
necessary.
analyzing on duty
Logistics
Adjust the
network
configuration to
improve the
current network
performance
Prepare
contingency
plans to reduce
the risk of
accidents.
ensure timely
supply and the
lowest cost.
Huawei Confidential
Real-time monitoring
on site to ensure
efficiently problems
handling.
Page 3
Experience
sharing to
enhance the
operation and
maintenance skill
level
Content
1
Parameter Adjusting
Emergency Measures
Huawei Confidential
Page 4
Item
Descriptions
Parameter
Descriptions
RNC Equipment
Resource
Congestion
Parameter Adjusting
FACH Congestion
Service Related
RTWP Optimization
IUB Transmission
Networking Policy
Multicarrier Networking
RRC DRD Switch
Expand Frequency
Others
Guarantee CS Services
Follow On Function
IU Signaling Link
Huawei Confidential
Page 5
1. RNC equipment
Enabling the SPU CPU Load Sharing Function
By enabling the SPU CPU load sharing function and setting the threshold of SPU CPU load sharing, you can
ensure the balance of the CPU load between the subsystems of each SPU.
Impact: This function has no negative impact.
To enable SPU CPU load sharing function, run the following command:
SET URRCTRLSWITCH: PROCESSSWITCH=RNC_SHARE_SWITCH-1
SET UCTRLPLNSHAREPARA: CtrlPlnSharingOutThd=50, CtrlPlnSharingOutOffset=5, SharingOutCAPSMidLoad=0;
Huawei Confidential
Page 6
1. RNC equipment
Enabling E2E flow control
When congestion or overload occurs on a NodeB, the NBAP RADIO LINK SETUP message must be restricted.
As the NodeB cannot identify the service type corresponding to each NBAP RADIO LINK SETUP message, the
NodeB cannot restrict the message based on the priorities of service types.
On the RNC, flow control is classified into three levels (absolute assurance, flow control allowed, and flow control
first) according to the service types initiated by UEs.
E2E flow control phase I refers to restricting the RADIO LINK SETUP REQUEST message sent from the RNC to a
NodeB. This can alleviate the CPU load of the NodeB to ensure service access. E2E flow control phase II is a
supplementary of phase I. In phase II, the RRC CONNECTION REQUEST message sent from a UE to the RNC is
restricted. This can reduce the signaling traffic over the IUB interface to prevent the CPU overload of the NodeB.
Impact: The access success rate of PS services is affected, but the access success rate of CS services is
boosted.
Huawei Confidential
Page 7
2. Resource Congestion
FACH Congestion1. Controlling DCCH Congestion
During DCCH congestion, retransmission of the RB_RFG message for P2D, F2D, or D2F switching in UM mode
further aggravates DCCH congestion, increases the power consumption of UEs, and affects the experience of PS
subscribers during data transmission.
During DCCH congestion, CS subscribers perform P2D switching instead of P2F.
During DCCH congestion, the Cell Update Confirm message for RL re-setup is transmitted through the CCCH.
During serious DCCH congestion, the traffic-volume-based P2F switching triggered by the non-real-time PS
service is restricted.
During serious DCCH congestion, the DRD upon the failure of F2D switching is restricted and the fallback upon
the failure of F2H switching is restricted.
During serious DCCH congestion, D2Idle instead of D2F switching is performed for non-real-time PS services.
Impact: This function has no negative impact.
To enable the function of controlling DCCH congestion, run the following command:
SET URRCTRLSWITCH: PROCESSSWITCH3=FACH_DCCH_CONG_CTRL_SWITCH-1;
To set the thresholds of DCCH/DTCH congestion, recovery, and congestion relief, run the following command:
SET UDPUCFGDATA: FachCongThd=60, FachCongRecoverThd=30, FachCongClearThd=10;
Huawei Confidential
Page 8
2. Resource Congestion
Huawei Confidential
Page 9
2. Resource Congestion
FACH Congestion3. Controlling CCCH Congestion
To increase the probability in which a UE receives the RRC CONNECTION SETUP message, the RNC sends the
RRC CONNECTION SETUP message repeatedly to the UE at specified intervals. In this way, the access success
rate of UE can be increased. When the CCCH is congested, however, retransmission of RRC setup requests
aggravates CCCH congestion. As a result, the first RRC CONNECTION SETUP message sent to the UE is
discarded due to congestion. If the UE fails to receive the RRC CONNECTION SETUP message, the UE sends
the RRC CONNECTION REQUEST message repeatedly, which further aggravates CCCH congestion.
When the CCCH is congested, T381 is automatically disabled, and the active retransmission of RRC setup
requests for non-CS and emergency call services is stopped. In the case of serious CCCH congestion, the RRC
setup requests for other non-CS/emergency call services will be rejected.
The CCCH congestion of cells is relieved and the success rate of RRC setup is improved.
Impact: When a large number of subscribers access a cell, the RRC CONNCTION SETUP messages sent from
the PS subscribers may be discarded.
To enable the function of controlling CCCH congestion, run the following command:
MOD UCELLALGOSWITCH: CellId=0, RsvdPara1=RSVDBIT5-1;
Huawei Confidential
Page 10
2. Resource Congestion
FACH Congestion4. Adding Another S-CCPCH for FACH
By default, the PCH and FACH are multiplexed on one SCCPCH, and the PCH is of higher priority. Within one
transmission timing interval (TTI), the FACH can transmit only one transmission block (TB) when there is data on
the PCH. About eight TBs need to be transmitted when an RRC is set up on the DCH. When the PCH is 100%
occupied, the quantity of RRC connections set up for one cell is about 12.5 per second; when the PCH is 100%
idle, the quantity of RRC connections set up for one cell is about 25 per second. To reduce the impacts of the PCH
on the FACH, you can add another S-CCPCH and allocate the PCH and FACH to different S-CCPCHs. In this way,
25 RRC connections per second can be ensured.
The capacity of public channels is expanded, and RRC Noreply and CCH call drop due to congestion of public
channels are significantly reduced.
Impact: The success rate of RRC setup takes six hours to recover after the SCCPCH parameters are adjusted.
Therefore, the operations must be performed in the idle hours of early morning before the festival. When the latest
IPhone 4 reselects a cell with two SCCPCHs from a cell with one SCCPCH, RRC connection cannot be set up due
to a certain bug. Therefore, the parameters must be modified network-wide.
Use the following script to modify the parameters. Replace the cell IDs in the scripts with the actual ones.
Adding another
S-CCPCH
Huawei Confidential
Page 11
2. Resource Congestion
Service Related1. Setting N300 and T300
N300 specifies the maximum quantity of retransmissions of RRC setup requests. When a UMTS network is
congested, the RNC rejects the RRC setup request sent by a UE, and the UE retransmits the RRC setup request
according to the values of N300 and T300. Frequent retransmissions of the RRC setup request affect the
elimination of network congestion.
The default value of T300 is 2s. If the value of T300 on the live network is too small (for example, 600 ms),
frequent retransmissions of RRC setup requests may occur during network congestion, which affects the
elimination of network congestion. If the value of T300 is less than 2s, set T300 to 2s. The recommended value is
1.
Frequent retransmissions of RRC setup requests by one UE during network congestion can be reduced, which
facilitates the elimination of network congestion.
Impact: When retransmissions of RRC setup requests are reduced, the success rate of RRC setup in non-hotspot
areas may decrease.
To set the N300 and T300 parameters, run the following command:
SET UIDLEMODETIMER: T300=D2000, N300=1;
Huawei Confidential
Page 12
2. Resource Congestion
Service Related3. Setting Periodic Location Area Update
T3212 specifies the interval at which a UE initiates the update of the location area (LA). The default value is 10
(one hour).
The RNC resources during traffic burst are limited. You are advised to adjust T3212 to 40.
Set the timer of periodic route area update on the Serving GPRS Support Node (SGSN). The maximum value of
the timer is 186 minutes. You are advised to set the timer on SGSN to 186 minutes.
The quantity of RRC setup requests due to periodic LA update is reduced.
Impact: This function has no negative impact.
To set the periodic location area update parameters, run the following command:
MOD UCNDOMAIN: CNDOMAINID=CS_DOMAIN, T3212=40;
Huawei Confidential
Page 13
2. Resource Congestion
RTWP Optimization1. When Release the Channel Resource
If the RNC successfully receives the first RRC CONNECTION RELEASE COMPLETE message sent by an UE,
the NodeB starts releasing radio channel resources immediately, but the UE does not release the channel
resources until T308 times out. If the power control command issued by the NodeB cannot be received, some UEs
will increase the power by default. As a result, the RTWP of the cell increases. The quantity of RRC setup requests
due to periodic LA update is reduced.
The RTWP increase can be prevented when a UE releases channel resources.
On V900R012 versions, run the following command:
SET UCORRMALGOSWITCH: ReservedSwitch0=RESERVED_SWITCH_0_BIT27-1;
Huawei Confidential
Page 14
2. Resource Congestion
Huawei Confidential
Page 15
3. Networking Policy
Adjusting the Multicarrier Networking Policy
When a major sports event is coming up, the multicarrier policy and mobility policy on the live network may not be
appropriate. In this case, modify the policies as required.
By adjusting the networking policy and handover parameters (such as pilot regulation and 1A/1B threshold
adjustment), the traffic load among multiple carriers is more balanced and the network congestion due to
imbalanced load can be avoided.
The field network planning engineers are responsible for developing the policy optimization schemes, and the
Headquarters will provide necessary support.
Use the random camp-on policy for carrier reselection. If four carriers are configured, configure every three
carriers as neighboring carriers.
Impact: This function has no negative impact.
To keep the cell reselection function enabled, run the following MML command:
MOD UCELLSELRESEL: CellId=XXX, IdleSintersearch=127, SsearchRat=127;
Huawei Confidential
Page 16
4. Others
Configuring Signaling Links on the Iu Interface: ATM-based networking
Assess the usage of IU signaling links during busy hours before the festival or event, and forecast the usage of IU
signaling links during traffic burst when the festival or event comes. In this case, perform the forecast on CS and
PS services respectively. For example, if the usage of IU-CS signaling links is 30% in busy hours before the
festival or event and the traffic volume of CS services will increase by 50% during traffic burst when the festival or
event comes, the usage of IU-CS signaling links is about 30% x (1 + 50%) = 45%. If the forecast usage of IU
signaling links during traffic burst when the festival or event comes exceeds 60%, IU signaling links must be
expanded.
Two methods are provided:
Add more links.
Increase the bandwidth of each link.
Huawei Confidential
Page 17
No.
Item
Descriptions
Parameter
Descriptions
RNC Equipment
Resource
Congestion
Parameter Adjusting
FACH Congestion
Service Related
RTWP Optimization
IUB Transmission
Networking Policy
Multicarrier Networking
RRC DRD Switch
Expand Frequency
Others
Guarantee CS Services
Follow On Function
IU Signaling Link
Huawei Confidential
Page 18
Content
1
Parameter Adjusting
Emergency Measures
Huawei Confidential
Page 19
MML Order
SET
UKPIALMTHD
Parameter Adjust
KPIALARMSWITCH=ON, KPIALARMCHKTIMES=D1,
RRCCONNESTABSUCCRATIOTHD=90, RRCCONNESTABATTMINNUM=200,
AMRRABESTABSUCCRATIOTHD=90, AMRRABESTABATTMINNUM=100,
VPRABESTSUCCRATIOTHD=90, VPRABESTATTMINNUM=100,
HSDPARABESTSUCCRATIOTHD=90, HSDPARABESTATTMINNUM=100,
HSUPARABESTSUCCRATIOTHD=90, HSUPARABESTATTMINNUM=100,
PSRABESTSUCCRATIOTHD=90, PSRABESTATTMINNUM=100,
AMRRABABNORMRELRATIOTHD=5, AMRRABRELMINNUM=100,
VPRABABNORMRELRATIOTHD=10, VPRABRELMINNUM=100,
PSRABABNORMRELRATIOTHD=10, PSRABRELMINNUM=100;
Huawei Confidential
Page 20
counter
V912/V913
(VS.RAB.AbnormRel.CS.RF.RNC+VS.RAB.AbnormRel.CS.RNC)/
(VS.RAB.AbnormRel.CS.RF.RNC+VS.RAB.AbnormRel.CS.RNC+VS.R
AB.NormRel.CS.RNC)
(VS.RAB.AbnormRel.PS.RF.RNC+VS.RAB.AbnormRel.PS.RNC)/
(VS.RAB.AbnormRel.PS.RF.RNC+VS.RAB.AbnormRel.PS.RNC+VS.R
AB.NormRel.PS.RNC)
VS.RANAP.CsPaging.Loss/ VS.RANAP.CsPaging.Att
VS.RANAP.PsPaging.Loss/ VS.RANAP.PsPaging.Att
CS ERLANG
RNC(NON MOCN)
PS DL THROUGHPUT
or
CN OPERATOR(MOCN)
VS.CSLoad.Erlang.Equiv.RNC
VS.CSLoad.Erlang.Equiv.PLMN.RNC
VS.R99PSLoad.DLThruput.RNC+VS.HSDPAPSLoad.DLThruput.RNC
VS.R99PSLoad.DLThruput.PLMN.RNC+VS.HSDPAPSLoad.DLThrupu
t.PLMN.RNC
VS.R99PSLoad.ULThruput.RNC+ VS.HSUPAPSLoad.ULThruput.RNC
PS UL THROUGHPUT
VS.R99PSLoad.ULThruput.PLMN.RNC+VS.HSUPAPSLoad.ULThrupu
t.PLMN.RNC
Huawei Confidential
Page 21
Alarm Name
Alarm ID
Cause
ALM-20256
ALM-22501
Flow Control
ALM-22835
Number of Resources
Used Reaching Alarm
Threshold Specified by
License
ALM-20258
ALM-20259
ALM-22301
CPU overload
CPU overload
Flow Control
Insufficient
license capacity
CN congestion
Number of Resources
Used Exceeding Alarm
Threshold Specified by
License
UMTS CN Overload
Huawei Confidential
Page 22
Alarm Name
Alarm ID
Cause
Abnormal KPIs
ALM-22302
ALM-22201
ALM-21542
ALM-21582
Cell congestion
Transmission
congestion
Path Congestion
Huawei Confidential
Page 23
Calls Are Restricted After the Resource Usage Exceeds the Licensed Volume
10
11
12
Huawei Confidential
Page 24
Emergency Measures
1. If the UEs on the live network are allocated evenly to ACs, enable the AC control function.
2. The RRC requests are classified into three priorities (high, medium, and low) based on the causes of RRC
access. When users access and the current SPU CPU usage is higher than the flow control threshold of the
corresponding priority, the RRC request is rejected.
To enable the function of performing RRC flow control of SPU CPU usage based on RRCs with different priorities
SET UNBMPARA:ReservedSwitch0=RESERVED_SWITCH_0_BIT6-1, ReservedU32Para1=90, ReservedU8Para0=85,
ReservedU8Para1=80;
To disable the function of performing RRC flow control of SPU CPU usage based on RRCs with different priorities, run
the following command:
SET UNBMPARA:ReservedSwitch0=RESERVED_SWITCH_0_BIT6-0;
3. Try to limit the number of access times of cells by using the CALLSHOCK function.
Huawei Confidential
Page 25
Emergency Measures
If only a few links are congested and the load on other links is low, run the DEA M3LNK or DEA MTP3LNK
command to deactivate the congested links. Alternatively, remove the congested links and add them again.
If PS node signaling congestion occurs, block cell PS domains in batches until the counters return back to normal
(in V913SPH529 and later versions) by running the following command:
MOD UCELLALGOSWITCH: CellID = xxxx,RsvdPara1= RSVDBIT14-1;
When this switch is turned on, add PS domain blocking in the SIB1. When this switch is turned off, cancel PS
domain blocking in the SIB1.
Expand the signaling links.
Deactivate the cells in batches, and activate them in batches three minutes after the IU signaling overload alarm is
cleared
Huawei Confidential
Page 26
Emergency Measures
Disable global paging and prolong the retransmission interval of paging messages on the CN. The domain (CS or
PS) of a paging can be determined based on the quantities of CS paging and PS paging and their tendencies.
Run the following command to set the quantity of paging retransmissions at the RNC side to 0:
SET UDPUCFGDATA: MaccPageRepeatTimes=0;
Enable the CS paging preemption on the PS.
In case of a congestion paging, the conversation paging takes priority over other paging to ensure the CS paging
success rate.
To enable this function, run the following command:
SET UDPUCFGDATA: PagingSwitch=ON;
Huawei Confidential
Page 27
Emergency Measures
If the PS RRC usage is greater than 40%, activate the cell PS domains configured by the SPU managed by the
MPU until the counters are normal. When the ALM-20256 CPU Overload of the MPU is cleared, activate the cells
in batches 3 minutes later. Observe the CPU usage of MPU activated and perform the next step when the CPU
usage is relatively stable.
To block cell PS domains in batches (available in V913SPH529 and later versions, run the following command:
MOD UCELLALGOSWITCH: CellID = xxxx,RsvdPara1= RSVDBIT14-1;
Deactivate the cells of the SPU subsystems managed by the MPU in batches, and activate them three minutes
after ALM-20256 CPU Overload is cleared. Check the CPU usage of the MPU. Perform the follow-up operations
when the CPU usage of the MPU becomes stable.
Huawei Confidential
Page 28
Emergency Measures
If the uplink access control function is not disabled before the festival, run the following command to disable the
uplink access control function:
MOD UCELLALGOSWITCH: CellId=xxx, NBMUlCacAlgoSelSwitch=ALGORITHM_OFF;
Huawei Confidential
Page 29
5.2 UL CE Congestion
Problem Symptom
The success rate of RRC setup decreases due to access rejection caused by UL CE congestion.
Emergency Measures
Run the following command to disable the 2 ms HSUPA function to reduce the usage of CE resources:
SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0;
Emergency Measures
If T381 is not adjusted before the festival and FACH congestion occurs during traffic burst, run the following
command to set T381 to 0 to relieve the FACH congestion:
SET UCONNMODETIMER: T381=D0;
Huawei Confidential
Page 30
Emergency Measures
1. Take the following measures if they are not taken before the festival to reduce the IUB signaling load:
Adjusting N300/T300
Adjusting T381
2. Adjust the pilot power of the cells of the NodeB to reduce the cell coverage, and allocate some subscribers to
the cells of other NodeBs. Pilot power can be adjusted by 2 dB each time for no more than twice. After each
adjustment, check the 5-minute measurement results for 15 minutes.
Huawei Confidential
Page 31
Thank you
www.huawei.com
Copyright2011 Huawei Technologies Co., Ltd. All Rights Reserved.
The information in this document may contain predictive statements including, without
limitation, statements regarding the future financial and operating results, future product
portfolio, new technology, etc. There are a number of factors that could cause actual results
and developments to differ materially from those expressed or implied in the predictive
statements. Therefore, such information is provided for reference purpose only and
constitutes neither an offer nor an acceptance. Huawei may change the information at any
time without notice.