Security Level:

UMTS Precautions and Emerge

ncy Measures for Large Traffic

2013.10.14

www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.

Content

1 Key Event Assurance Service

2 Parameter Adjusting

3 Emergency Measures

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

 Typical Scenarios & Scope
 Key sports events
Cyber Security Promoting
National Image
Leaders of over 80 countries
participated in Beijing Olympics
that went live in over 200
countries and regions.
Subscribers at the venue
doubled ; BHCA increased by
40%; traffic per line increased
by 120%; traffic increased by
170%.
KEA services to assurance the global planned major event, such as sports games, exhibition, summit,

festivals, and other events ,etc.
HUAWEI TECHNOLOGIES
Focus on HuaweiCO.,
 Key religious events
Unexpected Traffic Peaks
In HAJJ, over 2 million mobile
subscribers gathered in Mecca,
an area of 10 square kilometers.
There were 5 worships every
day, and over one million
subscribers were using services
at the same time after each
worship. At peak hours, the
standard BHCA of a single EO
increased by 37 times and the
number of SMs reached 4 million
per hour, increased by 31 times.
LTD.
wireless, Huawei
core network, network Confidential
 Key traditional festivals
Challenges and
Opportunities Promoting
Brand Image and
Increasing Revenue
In German beer festival,
approximately 7 million tourists
gathered around each year and
the voice or data services
increase by 2–3 times.
Successful assurance services
bring not only profits but also
good reputation and brand
value to operators.
equipment protection.
Key special events Key expositions
Great Pressure and Heavy Traffic, High Cyber
Security Requirements
Impact, High Cyber
Security Requirements In word-class expos, many
enterprises and a large
On national days,
audience gather around.
independence days,
Therefore, heavy traffic
presidential election days, or
threatens network stability. To
summits of national leaders,
increase profits and
operators are under great
consolidate brand image,
pressure due to extremely
operators have to ensure the
high requirements on cyber
cyber security and stability in
security and stability for VIP
the specific heavy-traffic areas.
customers, specific areas,
and specific technologies.
 Solution of Key Event Assurance Service

E2E Key Event Assurance Service

Before Event In Event After Event

Resource Capacity Equipment Network Adjust Emergency Spare Parts Event On-duty Adjustment and
Assessment Support Summary
Health Check & Optimization Scheme Design Assurance

• Spare parts • Provide expert • Restore the

• Forecast traffic • Carry out health • Develop • Design emergency
assessment and technical support on temporarily
model. check. adjustment plan hand book
• Assess the • Implement the • Develop planning site modified network
network adjustment contingency plan • Order management • Real-time network parameters
• Spare parts supply alarm and KPI • Summarize.
resources solution. • Perform drill if it is
• Warehousing monitoring and
necessary.
• Logistics analyzing on duty

Value Value Value Value Value Value Value

• Accurately • Inspect • Adjust the • Prepare • ensure timely • Real-time monitoring • Experience
predict the future equipment network contingency supply and the on site to ensure sharing to
traffic • find the problem, configuration to plans to reduce lowest cost. efficiently problems enhance the
• Reasonably • Clear network improve the the risk of handling. operation and
allocate the risks current network accidents. maintenance skill
network performance level
resources.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

Content

1 Key Event Assurance Service

2 Parameter Adjusting

3 Emergency Measures

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Solution Overview of Precautions
RAN12&Pre RAN13 RAN14 RAN15
1. CS RRC Preemption
CS 1. PS BE RRC
2. RRC Power CAC based on call type
preempted CE preemption
Service 3. CS RAB CAC Optimization P2D CS preemption
2. CS Paging Prior enhancement
Priority 4. PS RAB unconditionally preempted
to PS
5. CS prioritizing in FACH congestion

1. E2E flow control based on NodeB CPU load

1. E2E flow control based on
phase1
Equipment 2. RNC IU & RRC flow control
NodeB CPU load phase2 1. SPU subsystem
related 2. Wait-time based on call type CAPS FC
3. SPU CPU load sharing function
3. Cell-level PS domain barring
4. Adjusting DPU sharing thresholds

1. Replacing RB
CCH 1. CCCH congestion control
1. DCCH congestion control reconfiguration
2. CELL_DCH to Idle
congestion 3. Replacing IMSI with TMSI
2. FACH subscriber message with
control specification PhyCH
4. Adding another SCCPCH for FACH
reconfiguration

Timer 1. Adjusting N300/T300/T381 timers

parameter 2. Adjusting periodic LAC/RAC update 1. CQI feedback period
s 3. Adjusting DPB measurement report period

3. Multicarrier network policy

1. RRC CONN
4. Dynamic HSDPA Codes
Others 5. Disabling the Uplink Access Control
SETUP message
optimization
Function

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 6

Solution Overview: CS Service Priority
 RRC Connection Setup  RAB Setup signaling control procedure
signaling control procedure

UE NodeB RNC UE NodeB RNC CN

Paging
1. Paging Control
RRC Connection Request Initial DT 1. RNC Iu Flow
Control
2. RNC RRC Flow Downlink DT
Control
RAB assignment Request
3. RRC Admission
Control
Radio link Setup Request
2. RAB Admission
Control
Radio Link Reconfigure Prepare
4. NodeB Flow
Control 3. NodeB CE
Admission Control
Radio link Setup Response
Radio link Reconfigure Ready
5. FACH Control
RRC Connection Setup Radio Bearer Setup Request

RRC Connection setup complete

Radio Bearer Setup Complete

RAB assignment Complete

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 7

 RRC Admission Control
 RRC Connection Setup signaling control procedure
 1. Paging Control: CS paging prior to PS;
UE NodeB RNC  2. RNC RRC flow control: CS service with higher
Paging priority than PS in flow control;
1. Paging Control
RRC Connection Request
 3. RRC Admission Control: CS RRC Preemption a
2. RNC RRC Flow
nd RRC power CAC based on call type;
Control  4. NodeB Flow Control: E2E flow control can acce
3. RRC Admission
Control
ss CS service prior to PS based on NodeB CPU load
Radio link Setup Request and power congestion;
 5. FACH control: when CCCH congestion happen
4. NodeB Flow
Control
s, CS signaling will use FACH prior to PS signalin
g;
Radio link Setup Response
 Other solutions for high loading scenarios:
RRC Connection Setup
5. FACH Control  Dynamic wait-time based on call type;
 Cell-level PS domain barring;
RRC Connection setup complete  Intelligent Access Class Control;

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 8

RRC Admission Control
2. RRC Power CAC based on call
1. CS RRC Preemption type(RAN12)
(RAN12)
【 Introduction 】 【 Scenarios 】
 When CS RRC admission failed because In some congestion scenarios, rejecting PS requests in a
of resource limitation, CS can preempt massive way produces RRC storm. In current RRC
PS RAB BE services. admission algorithm, CS and PS service use the same
loose admission threshold that is OLC threshold. That
numerous PS RRC consumes much power resource leads
to more CS service admission rejection.
【 Introduction 】
 Different type service can be configured with different
3. PS BE RRC power load threshold.
preempted(RAN14)  PS service threshold usually is lower than CS ,thus CS
RRC setup success rate will be higher.
【 Scenarios 】
 In some scenarios, too many PS RRC links
Load （ %
exist. These services have setup RRC ）
Loose Admission
successfully and haven’t setup RAB. These CS/PS/Other Threshold
links consume much resource and CS can not
access the RAN network.
【 Introduction 】 t/s
 When CS RRC or RAB setup failures happen
because of congestion, PS BE RRC can be Load （ %
Strict Admission
preempted besides PS RABs. ）
Other Threshold
Configurable CS Threshold
PS Threshold

t/s

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 9

RAB Admission Control
 RAB Setup signaling control procedure

UE NodeB RNC CN

Initial DT 1. RNC Iu Flow  1. RNC Iu Flow Control: CS service with

Control
Downlink DT higher priority than PS in flow control;
RAB assignment Request  2. RAB Admission Control:
2. RAB Admission  CS RAB CAC Optimization;
Control  PS RAB unconditionally preempted;
Radio Link Reconfigure Prepare  P2D CS preemption;
3. NodeB CE
Admission Control
 3. NodeB CE admission Control: NodeB
Radio link Reconfigure Ready CS CE preemption
Radio Bearer Setup Request
Radio Bearer Setup Complete

RAB assignment Complete

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 10

RAB Admission Control
1. CS RAB CAC Optimization (RAN12) 2.PS RAB unconditionally
preempted(RAN12)
【 Scenarios 】 【 Scenarios 】
In some congestion scenarios ， CS RRC setup succeed but
Due to improper ARP planning of operators, Pre-emption
CS RAB setup failed since in RAB CAC resource is reserved
Vulnerability IE in PS RAB setup request message is set
for hand over. In order to improve the success rate of CS
“not pre-emptable” and this will lead to unsuccessful CS
RAB, optimization is necessary.
preemption.
【 Introduction 】 【 Introduction 】
 Power RAB CAC
CS AMR RAB threshold is set with OLC threshold when the OLC
 In the case of unconditional preemption, the RNC does
algorithm switch is turned on or 100% when the OLC algorithm switch not compare the priority of CS conversational services
is turned off. In previous algorithm, CS threshold must be lower than with that of PS BE services.
handover threshold and reserved resources for handover.  Preemption does not consider the Pre-emption
Capability or Pre-emption Vulnerability IE delivered by
the CN.
AMR RAB threshold : OLC or 
100%
In this case, PS BE services can be preempted by any
Handover threshold Handover threshold CS conversational services and only PS BE services
AMR RAB threshold can be preempted. Preempted PS BE services are
Other service threshold Other service threshold
ranked by priority.

3. P2D CS Preemption (RAN13)

 Credit &Code RAB CAC
The credit &code resource-based admission is successful if the
current available credit resources are sufficient for the AMR
service. In previous algorithm, CS can not use all the left
resource and some credit resources are reserved for handover.
【 Introduction 】
 When UE initiates CS call in Cell_PCH/ URA_PCH
state and need to do in Cell_PCH/ URA_PCH to
Cell_DCH state transition, preemption can be triggered
and PS BE RAB will be preempted.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 11

RAB Admission Control
4. CE preemption enhancement(RAN15)
【 Scenarios 】 ：
CE is hardware resource in NodeB, RNC do the CE admission
and preemption, NodeB only do the CE dynamic scheduling
among admitted UEs.
CS service is rejected in RNC by CE resource, the preemption
triggered in RNC has been implemented;
CS service is admitted in RNC, and reject in NodeB by CE
resource, the preemption need to be implemented.
【 Introduction 】 ：
When NodeB CE admission of CS service is failed, CE
Preemption can be triggered in NodeB and CS service will be
setup successfully.
5. CS Paging Prior to PS (RAN14)
【 Scenarios 】
As PS services increases so rapidly, paging
messages consume a large amount of paging
resources. As a result, the paging success rate of
CS services may be affected.
【 Introduction 】
 When the number of transmitted paging
messages in a transmission time interval (TTI)
reaches the maximum (known as PCH
congestion), push to talk (PTT) services and
conversational services can start preempting
the paging resources of other services.

UE
RRC Connection request CS PS PS CS PS
The maximum
RNC CE
paging Number
Admission in a TTI
RL Setup Request Success
Preemption
NodeB CE
Admission
Failed PS CS PS CS PS
NodeB CE Preemption The maximum
paging Number
RL Setup Response
in a TTI
RRC Connection Setup

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 12

Solution Overview: Equipment related

 1. Flow Control:
 E2E flow control;
CN
 SPU subsystem CAPS FC;
UE
 Cell-level dynamic CAPS FC;
 2. Load Sharing:
SPU CPU load sharing RNC Iu flow control
 SPU CPU load sharing;
DPU load sharing  DPU load sharing;
E2E flow control
SPU subsystem CAPS FC
Cell-level dynamic CASP FC

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 13

 Equipment related
1. E2E flow control based on NodeB CPU load phase1
（ RAN12 ）
【 Scenarios 】
Without E2E flow control, when the CPU of the baseband board
or WMPT is congested or overloaded, NodeB will reject or
discard the RADIO LINK SETUP REQUEST messages
regardless of CS or PS service.
【 Introduction 】
 In E2E Flow Control Phase 1, RADIO LINK SETUP
REQUEST messages sent by the RNC to the NodeB are
categorized by service priority.
 The NodeB performs flow control based on service priorities
to reduce the NodeB CPU load and ensures preferential
access of high-priority services such as CS services. PS BE
service is with the lower priority and will be rejected firstly.
HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散
2. E2E Flow Control Based on Power Congestion （ RAN12 ）
【 Scenarios 】
Since RNC can not acquire the downlink transmitted power
timely ， in some scenarios too many users are admitted and
cause the power increase sharply, which affects CS RRC setup
success rate.
【 Introduction 】
 E2E flow control based on power congestion in NodeB is
intended to reduce the probability of downlink power
congestion. In addition, it ensures that high-priority real-time
services (including conversational and streaming services) are
processed preferentially.
 Congestion will be determined when downlink power or RRC
online users exceed the thresholds, which are different for real-
time and non real-time service.
Page 14
 Equipment related
3. E2E flow control based on NodeB CPU load phase2 (RAN13) 4. RNC Iu&RRC flow control ( RAN12 ）

【 Scenarios 】
Without E2E flow control, when the CPU of the baseband board or
WMPT is congested or overloaded, NodeB will reject or discard the
RADIO LINK SETUP REQUEST messages.
【 Introduction 】 UE CN
 In E2E Flow Control Phase 2, the RNC performs flow control on
RRC CONNECTION REQUEST messages of new services
(excluding emergency calls) based on the CPU congestion level
reported by the NodeB and service priorities.
RNC RRC flow control RNC Iu flow control
 The RRC CONNECTION REQUEST messages of low-priority
services are preferentially rejected. E2E Flow Control Phase 2
serves as a supplement to E2E Flow Control Phase 1. The former
reduces the NBAP signaling traffic on the Iub interface and saves 【 Introduction 】
RAN resources. (1) RNC RRC flow control: When problems happen caused
by limited RNC hardware resources in congestion
scenarios , for example , higher CPU load of RNC
boards, RNC may performs RRC flow control, that will
reject PS RRC connection request firstly with the lowest
priority while CS service is with the highest priority
except emergency call, CS prioritizing is only part of
functions in RNC RRC flow control.

(2) RNC Iu flow control: When problems happen

caused by limited signaling bandwidth over the Iu,
the RNC works with the core network to perform
flow control on initial UE messages. CS service
with the highest priority and be discarded with the
least probability.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 15

 Equipment related
5. Enabling the SPU CPU Load Sharing Function 6. Adjusting DPU Load Sharing Threshold

【 Scenarios 】 【 Scenarios 】
By enabling the SPU CPU load sharing function and setting the When a DSP alarm is generated on the live network,
threshold of SPU CPU load sharing, you can ensure the balance of the
you can adjust the DSP load sharing thresholds.
CPU load between the subsystems of each SPU.
There are two scenes of DPU load sharing, one is in
【 Notes 】 MPU, one is between MPU.
The load generated by resource management cannot be shared among
CPUS subsystems.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 16

Equipment related
7. Wait-time based on call type (RAN13) 8. Cell-level PS domain barring(RAN13)
【 Scenarios 】 【 Scenarios 】
 In most scenarios, a number of PS service request In some special scenarios, very severe PS
and retransmission retry lead to more severe congestion happen and CS is hard to access the
congestion. Using the same configured wait-time RAN network. At this time , temporary PS domain
parameter for CS and PS service is not appropriate barring for some cells can be applied.
any more.
【 Introduction 】
【 Introduction 】
UE RNC

RRC conn. req SYS1 SYS1

RRC conn.
congestion

reject （ Wait-time ）
CS PS CS
× PS

Wait-time

RRC conn.
Req （ Resend ）
 PS domain information in SIB1 will not be
sent when a certain cell is barred through
 RRC Connection Reject message includes wai-time
the MML command. And then UEs in the
IE. When UE received the message, it will wait for
the wait-time and then resend the service request. cell will not initiate any new PS services.
 Wait-time for CS and PS service can be configured
independently. For example, wait-time is usually
configured 4s for CS service and 15s for PS. This
will alleviate the congestion.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 17

 Solution Overview: CCH Congestion
 RRC Connection Setup related entity

RRC_CONN_SETUP

RRC  1. Controlling CCCH Congestion:

SRB 0 SRB 1 SRB 2 SRB 3 SRB 4 Disable T381 and stop the retransmitted R
RC Setup REQ;
RLC RLC RLC RLC RLC
 2. Controlling DCCH Congestion: Restric
t the P2F and F2D process;
CCCH DCCH
 3. Controlling PCH Congestion:
MAC C MAC D
Set the quantity of paging retransmissions
RACH at the RNC side to 0;
FACH
PCH  4. Controlling FACH Congestion:
FP FP
 Add S-CCPCH;
 FACH Subscriber Specification;
 CELL_DCH to Idle;
RRC_CONN_REQ
 Physical channel reconfiguration for F2P

UE

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 18

 CCH congestion
1. Controlling CCCH Congestion 2. Controlling DCCH Congestion
【 Scenarios 】 【 Scenarios 】
CCCH congestion will lead to FACH congestion and RRC
During DCCH congestion, retransmission of the
CONNECTION SETUP and CELL/URA UPDATE CONFIRM may not RB_RFG message for P2D, F2D, or D2F switching
be sent. It is necessary to guarantee CS service is sent preferentially. in UM mode further aggravates DCCH congestion,
increases the power consumption of UEs, and
【 Introduction 】 affects the experience of PS subscribers during
The CCCH congestion level is determined by comparing the CCCH buffer data transmission.
size and preset thresholds, minor congestion and major congestion are
defined.
【 Introduction 】
 Minor CCCH congestion processing: When DCCH is congested,
− For CS service requests, retransmission of RRC CONNECTION SETUP 1. CS service trigger P2D.
and CELL/URA UPDATE CONFIRM is stopped.
− For PS service requests, retransmission of RRC CONNECTION SETUP 2. The Cell Update Confirm message for RL re-
and CELL/URA UPDATE CONFIRM is stopped, and the retransmitted RRC setup is transmitted through the CCCH.
connection requests and cell update messages will be discarded. 3. Restricting the P2F, and F2D phase which is
 Major CCCH congestion processing:
trigged by PS traffic.
− For CS service requests, retransmission of RRC CONNECTION SETUP
and CELL/URA UPDATE CONFIRM is stopped. 4. D2Idle to substitute D2F.
− RNC will reject new PS BE services, discards the cell update messages.

Minor Stop message retransmission of CS/PS BE

3. Controlling PCH Congestion
Congestion services
【 Introduction 】
Discards retransmitted messages of PS BE When PCH is congested, we can disable global paging
CCCH services and prolong the retransmission interval of paging
buffer Major
Reject new PS services
messages on the CN side.
Congestion At the RNC side, we can set the quantity of paging
Stop message retransmission of CS services
retransmissions at the RNC side to 0 to relieve PCH
congestion.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 19

CCH congestion
4. Controlling FACH Congestion
Add S-CCPCH
Adding another S-CCPCH and allocate the PCH and FACH to different S-CCPCHs can relieve the FACH congestion.

PCH FACH PCH FACH

SCCPCH SCCPCH 1 SCCPCH 2

FACH Subscriber Specification

When the FACH is congested, adjusting the restricted quantity of FACH subscribers is increased from 30 to 60.
Cell_DCH to Idle state
When the FACH is congested, the CELL_DCH subscribers can release the dedicated resource by perform D2Idle state
transition.
Physical channel reconfiguration for F2P
Using physical channel reconfiguration message to substitute RB reconfiguration message can optimize the state transition from
CELL_FACH to CELL_PCH or URA_PCH by reducing the number of packets required for instructing UEs to perform the state
transition.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 20

 Solution Overview: Timer parameters
 Timer parameters optimization signaling control prcedure  1. Controlling RRC Connection Request message:
 T300&N300 optimization

UE NodeB RNC
 Periodic LA update optimization
 UE wait time optimization
T300 RRC Connection Request  2. Controlling RNC Connection Setup message:
Periodic LA update RRC Connection Request
T381 optimization
Wait time when RRC reject RRC Connection Request
 3. Controlling NBAP message:
RRC Connection Setup T381
DPB measure report message optimization
DPB report Measure Report
 4. Controlling UL Load:
HS-DPCCH CQI Feedback
CQI feedback period optimization

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 21

 Timer parameters
1. N300 & T300 Timer 2. T381 Timer
【 Introduction 】 【 Introduction 】
N300 specifies the maximum quantity of retransmissions of T381 timer begins when RNC send the RRC CONN SETUP
RRC setup requests. message, and it stops when receive RRC CONN SETUP COM
T300 timer begins when UE send the RRC CONN REQ message.
message, and it stops when receive RRC CONN SETUP
message. 【 advice 】
Set T381 to 0s.
【 advice 】
Set N300 to 1 and T300 to 2s
4. Periodic Location Area Update Timer
3. DPB report period 【 Introduction 】
T3212 specifies the interval at which a UE initiates the
【 Introduction 】
update of the location area (LA).
This parameter specifies the period of the measure report of
DL code transmit power for the DPB(Downlink Power Balance) 【 Introduction 】
algorithm. It’s advised to set this parameter from 10(one hour) to
40(four hour).
【 advice 】
Set this parameter to 2s.

5. CQI feedback period

【 Introduction 】
This parameter specifies the CQI feedback of HSDPA user’s
uplink HS-DPCCH.
【 advice 】
Set this parameter to 8s.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 22

Content

1 Key Event Assurance Service

2 Parameter Adjusting

3 Emergency Measures

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Solution Overview of Emergency Measures

Implement Scene Remarks

1. NodeB CPU is continually over 90%

2G/3G Traffic Load 2. Airface resource is congested
There are 3 steps MML script to
Sharing 3. 2G traffic load is low
do this measure.

1. NodeB CPU is continually over 90% The ratio of pilot power and cell
Decrease Pilot Power 2. Airface resource is congested maximum TR power cannot be
3. Neighbor cell traffic load is low lower than 5%.

1. This feature is license-

1. SPU CPU is continually over 90% controlled.
Intelligent AC Control 2. AC distribution is evenly distributed 2. It doesn’t work to
CELL_PCH state UEs.

The number of allowed RRC

Cell Dynamic CAPS 1. SPU CPU is continually over 90%
connection requests per second
Flow Control 2. The RRC SUCC Rate is low
in the cell decreases.

Block Cell PS Domain 1. Above actions don’t work PS service will be blocked

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 24

 Emergence Measures
1. 2G/3G Traffic Load Sharing
【 Scenarios 】
We do the 2G/3G traffic load sharing when the following scenes happen:
1. NodeB CPU is continually over 90%
2. Airface resource is congested
3. 2G traffic load is low
【 NOTEs 】
There are three steps to do this measure.
2G&3G reselection and HO parameters
Huawei Parameter name Now 1st step 2nd step 3nd step
3G QQUALMIN -18 　 　 　
3G QRXLEVMIN -58 -54 -50 　
3G CS 2D ECN0 -16 -14 -12 　
3G CS 2F ECN0 -14 -12 -10 　
3G CS 2D RSCP -108 -103 -98 -94
3G CS 2F RSCP -105 -100 -95 -91
2G FDD Qmin -14 -11 -9 -7
2G FDDRSCPMIN -114 -104 -96 -90
3G SsearchRat 1 2 3 4
2G fast return feature activated deactivated deactivated deactivated
3G HSPA 2D ECN0 -24 -18 -16 　
3G HSPA 2F ECN0 -22 -16 -14 　
3G HSPA 2D RSCP -115 -110 -100 　
3G HSPA 2F RSCP -112 -107 -97 　
3G R99 2D ECN0 -18 -16 -14 　
3G R99 2F ECN0 -16 -14 -12 　
3G R99 2D RSCP -114 -110 -100 　
3G R99 2F RSCP -111 -107 -97 　

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 25

Emergence Measures
2. Decrease Pilot Power
【 Scenarios 】
We decrease the pilot power of the TOP cell when
the following scenes happen:
 NodeB CPU is continually over 90%
UMTS cell edge changes
 Airface resource is congested
 Neighbor cell traffic load is low

【 Impact 】
1) Easier Camp on GSM or neighbor cells.
2) Easier Reselection to GSM or neighbor cells.
3) UMTS Coverage shrinks.
4) Handover earlier from 3G to 2G.
5) User experience worse due to lower data throughput in
GSM network after handover.
6) More traffic stay in 2G, heavy loading on GSM network
and not maximizing the value of UMTS network.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 26

 Emergence Measures
3. Intelligent Access Class Control
【 Scenarios 】
 Intelligent Access Class Control applies to scenarios
where there is a surge in the number of network access
requests, for example, during mass gathering events.
 When cell congestion occurs, the RNC rejects a large
number of RRC connection setup requests, which
consumes much air interface resources, and
reconnections from UEs further aggravates network
congestion, and affects system stability.
An Example: The barred ACs are broadcast by polling to reduce the access attempts in heavy loading scenarios
HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散
【 Introduction 】
 All UEs have an AC that ranges from 0 to 9. The AC of a UE is
defined by the operator and is stored in the subscriber identity
module (SIM).
 If a cell is more congested, more ACs should be barred. ACs
will be barred by polling, the barred ACs are broadcast in the
SIB 3 message. When the cell congestion is relieved, less
ACs should be barred. This feature prevents network storms
and relieves cell congestion.
 Pre R5 UE can not support CS and PS AC control separately.
1. Based on congestion conditions to Judge cel
l congestion for every 20 seconds:
 RRC setup rejection rate
 RAB setup rejection rate
 Uplink power load
 CPU usage of the RNC SPU subsystem
2. AC Restriction Range: AC0-AC9, some ACs w
ill be barred by polling for every 10 seconds;
3. Service restriction priority from high to low:
 1. R6/R7/R8 PS;
 2. R99/R4/R5 CS+PS;
 3. R6/R7/R8 CS
Page 27
Emergence Measures
4. Cell Dynamic CAPS Flow Control
【 Scenarios 】
We do the cell dynamic CAPS flow control when the following scenes happen:
 SPU CPU is continually over 90%
 Numerous RRC REQ come from cell and RRC SUCC rate is low.
【 Principle 】
The cell compares the current RRC connection failure rate with RejectKPICTHD (threshold for triggering
flow control) every 6s. If the threshold is reached, cell-level dynamic CAPS control starts. This function
dynamically controls the number of admitted services in a cell. The specific policy is as follows:
 If the RRC connection failure rate in the current period is greater than RejectKPIRTHD, the cell lowers
the number of RRC connection requests allowed for the cell in the next period, reducing the impact of
invalid service access on the CPU load of the cell.
 If the RRC connection failure rate in the current period is less than RejectKPIRTHD, the cell raises the
number of RRC connection requests allowed for the cell in the next period, enabling more services to
access the cell.
 If the RRC connection failure rate is less than RejectKPIRTHD for 10 consecutive periods, the cell stops
cell-level dynamic CAPS control.

【 Benefits 】
 To limit the numerous sudden cell RRC REQ, assure other cells work normally.
 To relieve the load of SPU subsystem.
 Enhance the stability of RNC in case of key event scene.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 28

Emergence Measures
5. Block Cell PS Domain
【 Scenarios 】
In some special scenarios, very severe PS congestion happen
and CS is hard to access the RAN network. At this time ,
temporary PS domain barring for some cells can be applied.
【 Introduction 】

SYS1 SYS1

CS PS CS ×
PS

 PS domain information in SIB1 will not be sent when a

certain cell is barred through the MML command. And
then UEs in the cell will not initiate any new PS
services.

HUAWEI TECHNOLOGIES CO., LTD. 华为保密信息，未经授权禁止扩散 Page 29

 Thank you
www.huawei.com

Copyright©2011 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.