Professional Documents
Culture Documents
10/7/16
Smartphone Signaling
Storm Solution Training
www.huawei.com
Huawei Confidential
HSDPA
Solution Introduction
Smartphone Signaling Storm Assessment
Smart phone Signaling Storm Optimization
Case Study
Page 2
Page 3
Page 4
Fast dormancy was introduced to save UE power but lead to more signaling
Time
Without
Fast dormancy:
1 time data connection, few signaling
Short
battery life
Long
battery life
With
Fast Dormancy:
HISILICON SEMICONDUCTOR
Page 5
1
2
3
iPhone
No Service
MSN
iPhone
5- 6s
Every 55 - 60
seconds
Every 50 seconds,
interaction with
twitter.com
HTC
Android
No heart beat
40-60s
HISILICON SEMICONDUCTOR
Page 6
Operator
RNC ID (measure in BH)
Smart phone penetration rate
User Number
3021
8%
47786
PS
0.9322
PS Call times per User
2.4567
Total PS Throughput (kbps) per User
PS RAB Number
PS Call Duration (s)
AMR Traffic (Erl) per User
AMR Call Times per User
AMR Holding Time (s)
329
20%
49979
1.6139
5.9095
1789.692
1200.6320
4
82.3071 80.0488
CS
0.0053
0.0217
0.2128
0.7758
76.3465 78.026
3511
95%
168510
2303
>100%
23538
5.2965
0.9975
5.3452
58.18
19139.12 9449.6254
78.2447 270.3761
0.0322
0.0045
0.6487
0.02
134.8078 653.143
HISILICON SEMICONDUCTOR
Page 7
Smartphone Evaluation
Transmission Resource
Adjustment
Network Traffic Model
Evaluation
Analysis &
Prediction
Smartphone Historical
Trend Analysis
Capacity Enhancement
(Products)
Capacity Enhancement
(Features)
Smartphone penetration
Forecast
Stability Enhancement
Network resource
Prediction with
Smartphone development
HISILICON SEMICONDUCTOR
Network
Development Plan
Page 8
Content
RNC SPU/PIU
NODEB CNBAP
FACH/PCH Utility Audit
Resource & Capability URA Feature Gain Audit
RNC SPU/PIU Forecast(Consider Smartphone Penetration
Evaluation
Growth)
NODEB CNBAP Forecast(Consider Smartphone Penetration
Growth)
FACH/PCH Utility Forecast(Consider Smartphone
Penetration Growth)
Multi-Carrier Strategy Audit
Performance
Multi-RAB Service Audit(After CELLPCH/FACH Activation)
Evaluation
Result verification
Signaling Storm Optimization
EFD Feature
FD/EFD Feature Introduction
Introduction
Multi-RAB CS Service Quality Improvement
Smart Phone Feature
Smartphone Fast State Transition
Introduction
URA Planning
HISILICON SEMICONDUCTOR
RNC Version
Solution
Version
ALL
Later
Later
Later
Later
Later
Later
ALL
ALL
ALL
Later
V1R1
V1R1
V1R1
V1R1
V1R1
V1R2
V1R2
V1R1
V1R1
V1R1
V1R2
than
than
than
than
than
than
R11
R12
R11
R12
R12
R12
than R12
ALL
V1R2
ALL
V1R2
ALL
V1R2
ALL
Later than
R12SPC518
V1R1
V1R1
V1R2
V1R2
V1R2
Page 9
V1R2
HSDPA
Solution Introduction
Smartphone Signaling Storm Assessment
Smart Phone Signaling Storm Optimization
Case Study
HISILICON SEMICONDUCTOR
Page 10
Page 10
Tools
OMSTARV5R6
Smartphone Penetration
Apple, RIM and Nokia are the TOP 3
Smartphone.
Smartphone Definition
9%
9%
RIM
Nokia
HTC
Samsung Korea
Others
SmartPhone
Behavior
2%
28%
SmartPhone
Behavior
1% 5%
General UE
General UE
Dongle
Dongle
70%
94%
SmartPhone
Behavior
41%
51%
7%
General UE
SmartPhone
Behavior
51%
49%
Dongle
General UE
Dongle
28% Smartphone Behavior UEs generate 94% of total PS Access, 51% of total PS Traffic. 2% Datacard
generate 41% of the total PS traffic .
RIM
1.17
HTC
0.88
Motorola
0.92
IPhone4
Sony Ericsson
IPhone
Nokia
0.00
16.47
16.69
5.01
11.89
Sony Ericsson
11.17
1.18
14.82
15.00
20.00
0.00
64.80
24.36
73.49
16.91
68.18
24.08
73.14
21.57
Nokia
10.00
63.43
20.44
IPhone
2.43
0.94
68.39
15.27
IPhone4
3.34
5.00
HTC
Motorola
1.36
0.66
RIM
20.00
68.91
40.00
60.00
times
CS RAB ACCESS per user
RIM, HTC and Iphone have the most PS RAB Access per user, and HTC and RIM have
relative low penetration rate in the Network (RNC3501).
80.00
second
UE Device
Total RRC
CS RAB
Total User
Access
ACCESS
Number
(Times)
per user
PS RAB
SHO
HHO
CS Call
PS
DL PS
UL PS
DCCC
ACCESS ATTEMPT ATTEMPT
Duration Duration Traffic per Traffic per
REQUEST
per user
S
S
per CS Call per PS Call user(KB) user(KB)
Nokia
158381
24966
0.94
2.43
201839
1141
46974
68.91
21.57
1499.37
129.47
IPhone
165787
11283
1.18
11.17
295007
3939
83629
73.14
24.08
5362.29
663.79
Sony
Ericsson
62353
7217
0.66
3.34
61357
498
10481
68.18
16.91
1044.06
84.47
IPhone4
99328
6480
1.36
11.89
103840
20056
73.49
24.36
5942.60
752.12
Motorola
56088
6232
0.92
5.01
74464
707
21067
64.80
20.44
1692.83
472.42
HTC
90421
4282
0.88
16.69
105429
1970
21070
63.43
15.27
3656.53
486.69
RIM
42868
2107
1.17
16.47
46243
802
13521
68.39
14.82
743.13
102.87
Dongle
45127
2511
15.90
58049
1198
116185
68.56
85478.20
9003.39
96.38%
86.27%
71.35%
28.65%
17.14%
13.39%
PIU
Smartphone
3901
13.02%
3.52%
SPU
RNCID
86.85%
81.86%
ULPower DLPower
Cong
Cong
Times
Times
5122
91
DPU
CNBAP
General UE
ULCE
Cong
Times
DLCE
Cong
Times
CODE
Cong
Times
1093
11
DLIUBBa ULIUBBa
nd Cong nd Cong
Times
Times
Penetration
12
R11
R12_A
R12_B
SMS
0.90000%
1.02700%
1.07500%
CS_RAB_TIMES
1.97000%
2.18300%
2.55900%
PS Call (R99)
3.20000%
2.18300%
2.55900%
PS_RAB_TIMES*{(RAB.AttEstabPS.Conv+RAB.AttEstabPS.Bgrd+RAB. 3.20000%
2.32700%
2.84600%
0.52000%
0.64400%
0.79100%
0.26000%
0.32200%
0.32400%
(RAB.AttEstabPS.Conv+RAB.AttEstabPS.Bgrd+RAB.AttEstabPS.Intv+R
AB.AttEstabPS.Strm)
PS Call (HSPA)
AttEstabPS.Intv+RAB.AttEstabPS.Strm-VS.RAB.AttEstab.PSR99))/
(RAB.AttEstabPS.Conv+RAB.AttEstabPS.Bgrd+RAB.AttEstabPS.Intv+R
AB.AttEstabPS.Strm)
Soft Handover Addition
ucStatShoAttTimes* {(VS.SHO.AttRLAdd-VS.SoHO.AttRLAdd)/
(VS.SHO.AttRLAdd-VS.SoHO.AttRLAdd +VS.SHO.AttRlDelVS.SoHO.AttRlDel)
ucStatShoAttTimes* (VS.SHO.AttRlDel-VS.SoHO.AttRlDel)/
(VS.SHO.AttRLAdd-VS.SoHO.AttRLAdd +VS.SHO.AttRlDelVS.SoHO.AttRlDel)
0.35000%
0.45700%
0.60800%
+VS.SoHO.AttRlDel))
ucStatShoerAttTimes* (VS.SoHO.AttRlDel/(VS.SoHO.AttRLAdd
0.17000%
0.24000%
0.24800%
DCCC
+VS.SoHO.AttRlDel))
ucDcccUpRateReqTimes ucDcccDownRateReqTimes
0.80000%
0.85600%
1.01600%
Hard Handover
ucStatIntraFreqHhoReqTimes ucStatInterFreqHhoReqTimes
0.66000%
0.66000%
0.85700%
CS_RAB_TIMES
PS Call (R99)
PS_RAB_TIMES
PS Call (HSPA)
Same as PS R99
ucStatShoAttTimes* {(VS.SHO.AttRLAdd-VS.SoHO.AttRLAdd )/
((VS.SHO.AttRLAdd-VS.SoHO.AttRLAdd )+(VS.SHO.AttRlDelVS.SoHO.AttRlDel))}
Soft Handover Deletion
ucStatShoAttTimes* {(VS.SHO.AttRlDel-VS.SoHO.AttRlDel)/
((VS.SHO.AttRLAdd-VS.SoHO.AttRLAdd )+(VS.SHO.AttRlDelVS.SoHO.AttRlDel))}
Softer Handover Addition
DCCC
ucDcccUpRateReqTimes+ucDcccDownRateReqTimes
Hard Handover
Counter:
Counter:
PCHR
VS.IUB.AttRLSetup
VS.IUB.AttRLAdd
VS.IUB.AttRLRecfg
CNBAP= ((VS.IUB.AttRLSetup +
VS.IUB.AttRLAdd + VS.IUB.AttRLRecfg
*{2})/{3600})
UE Handover times
PS RAB Attempts
CS RAB Attempts
UE DCCC Times
PCHR
UE consumed CNBAP= UE Handover
times + PS RAB Attempts *3 + CS RAB
Attempts *3+ UE DCCC Times *2 /3600
According to the penetration assessment result, provide the conclusion if the signaling
solution can be applied to the current network.
Smartphone behavior Analysis
HSDPA
Solution Introduction
Smartphone Signaling Storm Assessment
Smart Phone Signaling Storm Optimization
-PCH/FD/EFD
Case Study
Page 25
UEs complying with 3GPP Release 8 support the fast dormancy function, as defined in 3GPP
TS 25.331 CR3483.
R8 fast dormancy: This mechanism is standardized by 3GPP Release 8. UE sends a
SIGNALLING CONNECTION RELEASE INDICATION (SCRI) message to the network with the IE
Signaling Connection Release Indication Cause set to UE Requested PS Data session
end.
--The RNC can identify this type of UE by the SCRI message with IE UE Requested PS Data
session end.
Pre-R8 fast dormancy: This mechanism, which is not standardized, is the early proprietary
implementations of fast dormancy prior to Release 8. UE sends SCRI without the IE Signaling
Connection Release Indication Cause for fast dormancy.
-- The RNC can identify this type of UE by its IMEI.
Page 27
IDLE
Cell_PC
Cell_P
H
CH
Low
loa
d
high
load
Cell_DCH
Cell_FACH
Medium
load
IDL
E
HUAWEI TECHNOLOGIES CO., LTD.
Page 28
1. White List
2. Black List
Cons:
Cons:
Higher risks of UE
compatibility
White list and black list only apply to Pre-R8 fast dormancy UE
29
P2F2D2F2P
D2IDLE2D
P2F2P
Page 31
Page 32
D2F2PTvmThd
D2FTvmTimeToTrig
Explanation
Purpose:
This parameter is the threshold to decide whether 4B event should be reported.
How it works:
When the UE is on CELL_DCH and its traffic volume is lower than this parameter, D2FTvmTimeToTrig timer starts.
Purpose:
This parameter is designed to prevent unnecessary 4B event report when UE is on DCH, caused by traffic volume
variation.
How it works:
This timer starts immediately when the UE traffic volume is below the D2F2PTvmThd.
During the period it sets, there are two scenarios according to the traffic volume of the UE:
UE traffic volume is always below D2F2PTvmThd until it expires, 4B event is reported immediately when it
expires.
When UE traffic volume is higher D2F2PTvmThd at some time before it expires, this timer will reset and
UE is still on CELL_DCH.
Purpose:
This timer is designed to monitor whether the UE traffic volume is always lower than D2F2PTvmThd before UE
transfer from CELL_DCH to CELL_FACH
How it works:
This timer starts immediately when D2FTvmTimeToTrig expires.
During the period it sets, there are two scenarios according to the traffic volume of the UE:
BeD2FStateTransTimer
UE traffic volume is always below D2F2PTvmThd until it expires, UE is transferred from Cell_DCH to
Cell_FACH.
UE traffic volume is higher D2F2PTvmThd before it expires, this timer will reset and UE is still on
CELL_DCH.
Page 33
Parameter ID
Explanation
Purpose:
This parameter is designed to prevent unnecessary 4B event report when UE is on Cell_FACH, caused by traffic volume
variation.
How it works:
F2PTvmTimeToTrig
When the traffic volume is 0, this timer starts.
During the period before it expires, there are two scenarios according to the traffic volume of the UE:
UE traffic volume is always below 0, 4B event is reported immediately when it expires.
UE traffic volume is higher 0 at some time before it expires, this timer will reset and UE is still on Cell_FACH.
Purpose:
This parameter is designed to monitor whether the UE traffic volume is always 0 before UE transfer from Cell_FACH to
Cell_PCH
How it works:
BeF2PStateTransTimer
This timer starts immediately when F2PTvmTimeToTrig expires.
During the period it sets, there are two scenarios according to the traffic volume of the UE:
UE traffic volume is always below 0 until it expires, UE is transferred from Cell_FACH to Cell_PCH.
UE traffic volume is higher 0 before it expires, this timer will reset and UE is still on Cell_FACH
PsInactTmrForInt/
PsInactTmrForBac
Purpose:
This parameter is designed to monitor whether the UE traffic volume is always 0 before UE transfer to idle.
How it works:
When UE that has interactive class data service/ background class data service stops data transfer, this timer starts.
During the period before it expires, there are two scenarios according to the traffic volume of the UE:
UE traffic volume is always below 0, UE is transferred to idle status when it expires.
UE traffic volume is higher 0 at some time before it expires, this timer will reset and UE is still on its original status
(CELL_DCH or Cell_FACH).
Page 34
For simplicity, in this document, we use D2F Timer and F2P Timer
(defined as below)to describe the principles Cell_PCH works. Pleased be
noticed that there are no timer named D2F Timer or F2P Timer in our
system.
If the D2F Timer or F2P Timer is too low, it may misjudge whether the UE
traffic volume meets the condition for state transition. If the D2F Timer
or F2P Timer is too high, more UE stay at Cell_DCH or Cell_FACH state.
The timers should be set according to actual BE service model.
HUAWEI TECHNOLOGIES CO., LTD.
Page 36
PS_RAB_TIMES(all)
SCRI_TIMES(Smartphone) : SCRI_TIMES@BH of Smartphone; (which will not change after launching Cell_PCH)
Smartphone here means UEs PS_RAB_TIMES@BH is more than 10 times. Actual definition could vary in UEs
PS_RAB_TIMES@ BH.
If we define PS_RAB_TIMES@BH lower than 10 times as Smartphone, the estimated
gain will increase,
PS_RAB_TIMES Reduced
Smartphone Penetration
SCRI Penetration
Actual PS RAB Times @BH
Timer(all)
Long timer will increase risk of Cell_FACH / Cell_DCH Congestion, which
influence KPIs such as access success ratio, etc.
Page 39
SPU LoadPS
9.27%
RAB
56.01
%
SPU Load PS
RAB
3%
SPU Load
PS RAB
4.09%
20.45%
19%
Node B
Node B RNCSGSN/GGSN
RNCSGSN/GGSN
Node B RNCSGSN/GGSN
Cell_FACH is not activated on original network
Ratio of PS RAB
from Smartphone
@BH
Smartphone
Penetration
Cell_FACH Lauched
SCRI Ratio
PS RAB Gain
SPU Load
Gain
Telenor
75%
19%
40%
20.45%
4.09%
Operator A
82.07%
12.73%
26%
56.01%
9.27%
Operator B
35%
9%
63%
19%
-3%
The PS_RAB_TIMES GAIN and SPU GAIN for Operator A&B are tested value on the networks. The PS RAB GAIN & SPU
GAIN for Telenor is estimated value using the method described in page 37~page39, and is based on the data from RNC512
from Aug 31,2011~ Sep. 7, 2011.
HUAWEI TECHNOLOGIES CO., LTD.
PCH/FD/EFD Solution-EFD
Scenario
1 Applicable to R8 UE and UEs in White List
2 Applicable to RNC version later than V9R12
When fast dormancy enhancement is not applied, the RRC connection of the UE is released
when the RNC receives the SCRI.
When fast dormancy enhancement is applied, the RNC can change the UE status to the
CELL_PCH /CELL-FACH state instead of idle mode.
Procedure
Procedure Comparison
Comparison
State
State Transition
Transition of
of Fast
Fast
Dormancy
Dormancy Enhancement
Enhancement
Page 43
44
Explanation
Meaning: This parameter specifies the value of the CELL-DCH inactivity timer for UEs
enabled with the Fast Domancy feature. When detecting that the Fast Domancy User in
PsInactTmrFo PS domain had no data to transfer in CELL-DCH for a long time which longer than this
rFstDrmDch timer, the state transition from CELL-DCH to CELL-FACH or CELL-PCH is triggered. To
enable this timer, set this timer to a value other than 0.
Recommended Value: 5s
Meaning: This parameter specifies the value of the CELL-FACH inactivity timer for
UEs enabled with the Fast Dormancy feature. When detecting that the Fast Dormancy
PsInactTmrFo User in PS domain had no data to transfer in CELL-FACH for a long time which longer
rFstDrmFach than this timer, the state transition from CELL-FACH to CELL-PCH is triggered. To enable
this timer, set this timer to a value other than 0
Recommended Value: 5s
Meaning: This parameter specifies the value of the CELL-PCH inactivity timer for UEs
enabled with the Fast Dormancy feature. When detecting that the Fast Dormancy User in
PsInactTmrFo
PS domain had no data to transfer in CELL-PCH for a long time which longer than this
rPreFstDrm timer, the UE is released. To enable this timer, set this timer to a value other than 0.
Recommended Value: 1800s
FastDormanc Meaning: This parameter specifies the threshold of the traffic volume of 4A event for
yF2DHTvmTh triggering the transition of fast dormancy user from FACH/E_FACH to DCH/HSPA.
Recommended Value: D1024
d
Page 45
PS_RAB_TIMES(Apple, after
PS_RAB_TIMES(all)
PS_RAB_TIMES( Apple, before EFD) : PS_RAB_TIMES@BH of Apply IPhone before launching EFD
PS_RAB_TIMES Reduced
Apple Penetration
R8 UE Penetration
Actual PS RAB Times of Apple &
R8 UE @BH
Page 48
Node
B
RNC
Times of PS
Access
43.9
%
SGSNGGSN
R8 UE Penetration
Apple Penetration (Apple Excluded)
Operator C
15%
0%
Telenor
24%
0%
Node
B
Ratio of PS RAB
TIMES
of Apple & R8 UE
@BH
44%
58%
Times of PS
Access
9.29%
46.44%
RNC
SGSN GGS
N
PS RAB Gain
43.9%
iPhone
46.44%
SPU Gain
8.56%
9.29%
The PS_RAB_TIMES GAIN and SPU GAIN for Operator C are tested value on the network.
The PS RAB GAIN & SPU GAIN for Telenor is estimated value using the method described in page 45~page47, and is based on the data from
RNC512 from Aug 31,2011~ Sep. 7, 2011 , where the network does not have CELL_PCH.
KPI/Counter
Remark
VS.RRC.AttConnEstab.Sum
RRC.SuccConnEstab.sum
RRC Access
PS RAB
CS RAB
CellUpdt
Common Channel
CPU
State Transit
Radio Link
(CNBAP)
(RNC)
PS Call Drop Ratio with PCH
(RNC)
(VS.RAB.AttEstabPS.Conv.
RNC+VS.RAB.AttEstabPS.Bk
VS.RAB.AttEstabPS.RNC
g.RNC+VS.RAB.AttEstabPS.I
nt.RNC+VS.RAB.AttEstabPS.
Str.RNC)
VS.RAB.AbnormRel.PS
(RNC)
CS Service Drop Ratio (RNC)
VS.RAB.AbnormRel.AMR.RN
C
VS.AttCellUpdt
VS.FACH.DCCH.CONG.TIME
Congestion duration
VS.FACH.DTCH.CONG.TIME
VS.XPU.CPULOAD.MEAN
SPU UTILITY
VS.INT.CPULOAD.MEAN
PIU Utility
VS.DCCC.Succ.F2D
VS.DCCC.Succ.D2F
VS.DCCC.Att.F2P
VS.DCCC.Succ.F2P
VS.DCCC.P2F.Att
VS.DCCC.P2F.Succ
VS.IUB.SuccRLAdd
VS.IUB.SuccRLDel
VS.IUB.SuccRLRecfg
VS.IUB.SuccRLSetup
VS.LC.ULCreditUsed.Mean
Credit
VS.LC.DLCreditUsed.Mean
VS.MultiRAB.CSAbnormRel.C
SPS
VS.MultiRAB.CSNormRel.CS
PS
Multirab
VS.MultiRAB.AttEstab.CSPS
VS.MultiRAB.CSAbnormRel.P
HUAWEI TECHNOLOGIES
CO., LTD.
SAtt
HSDPA
Solution introduction
Smartphone signaling storm assessment
Smartphone signaling storm Optimization
- URA_PCH solution
Case study
Page 51
Page 53
Page 55
URA Re-planning
Planning design rules:
Specification
The product supports that the max URA number is 65535, the whole
network can be configured up to 65535
RNC supports the max cell number is 5100, and the max NodeB number
is 3060.
Rules
The protocol defines single cell can be configured up to 8 URA .
Only one URA can not be configured in one RNC, it may result in
waste of paging channel resource
URA can not cross the RNC, or it may result in paging failure
It should ensure cells with continuous coverage allocate the same
URA.
Control the number of URA updates.
Page 56
URA Re-planning
URA planning principle Every cell can be configured up to 8 URA ID , one
configures Primary URA ID seven configures Secondary URA ID
Page 57
URA Re-planning
URA planning principal Every cell can be configured up to 8 URA ID , one
configures Primary URA ID seven configures Secondary URA ID
Page 58
HSDPA
Solution introduction
Smartphone signaling storm assessment
Smartphone signaling storm optimization
- Fast state transition and Smart P2D
Case study
Page 59
60
Design strategy
The DRA_SMART_FAST_STATE_TRANSFER_SWITCH
switch under DraSwitch
controls whether fast state transition is enabled. If this switch is turned on:
When the state of a Smartphone performing BE services changes from
CELL_DCH to CELL_FACH, the RNC records the time stamp as T1.
When the Smartphone state changes from CELL_PCH, URA_PCH, or CELL_FACH
back to
CELL_DCH, the RNC records the time stamp as T2.
The RNC then calculates the interval between T1 and T2. If this time interval is
greater than the value of TthdForSFSTUserIdentify, the RNC determines that the
Smartphone is capable of fast state transition during the subsequent procedure S2.
HUAWEI TECHNOLOGIES CO., LTD.
Design strategy
The DRA_PCH_UE_SMART_P2D_SWITCH
switch under DraSwitch
controls whether smart P2D is enabled.
If the amount of data transmitted by a UE four consecutive times
exceeds the value of TvmThdForSmartP2D, the RNC predicts that
the amount of data the UE will transmit subsequently will remain
above the value of TvmThdForSmartP2D. The RNC directly transit
the UE state to DCH.
If the amount of data transmitted by a UE four consecutive times is
less than or equal to the value of TvmThdForSmartP2D, the RNC
predicts
that the UE
HUAWEI
TECHNOLOGIES
CO.,has
LTD. a
small amount
of data to transmit
Counter
Description
67199617
VS.MeanRTWP
67199618
VS.MeanTCP
67202902
67202567
67202570
73410510
VS.CellDCHUEs
73410511
VS.CellFACHUEs
73439971
73421934
Focus on monitoring
Whether Non-HSDPA power
, CE consumption is
decrease ,
P2D transition success
number change
CELL PCH
URA PCH
R8FD
Dependence
none
none
none
The introduction of
version
V9R012SPH226and after
Applicable
terminal
Negative influence
All terminal
All terminal
decrease PS RAB
attempts( decrease SPU
load , CNBAP,CE
utilization and air
interface resource
utilization), decrease
paging channel utilization
Increase RB
reconfigure
decrease PS RAB
attempts( decrease SPU
load , CNBAP,CE
Increase RB reconfigure
utilization and air
and cell reselection
interface resource
utilization), decrease
paging channel utilization
decrease PS RAB
attempts( decrease SPU
load , CNBAP,CE
Increase RB reconfigure
utilization and air
and cell reselection
interface resource
utilization), decrease
paging channel utilization
EFD
none
V9R012SPH226and after
need to enable
CELL PCH or
URA PCH
Main gain
No impact
Remark
Two solutions
URA PCH + layered paging
URA replanning
Two solutions:
Fast state solution
Smart P2D solution
HSDPA
Solution introduction
Smartphone Signaling Storm Assessment
Smart Phone Signaling Storm Optimization
-Risk Analysis
Case Study
Page 66
SCCPCH SCCPCH
High
Priority
TF
PCH TB
Low
SIG FACH
Traffic
TB
FACH TB
Case1
Case2
Case3
Case4
Case5
Case6
67
HUAWEI TECHNOLOGIES CO., LTD.
SCCPCH8
FACH USER
Plane
PCH
0*240,
1*240
TFCS
1:{0*240,
2:{1*240,
3:{0*240,
4:{1*240,
5:{0*240,
6:{0*240,
0*168,
0*168,
1*168,
1*168,
2*168,
0*168,
0*360}
0*360}
0*360}
0*360}
0*360}
1*360}
68
SCCPCH8
LOG CH
PCH
TFS
0*240,
1*240
TFCS
1:{0*240}
2:{1*240}
SCCPCH9
FACH USER
FACH SIG Plane
Plane
0*168, 1*168,
0*360, 1*360
2*168
1:{0*168,
2:{1*168,
3:{2*168,
4:{0*168,
0*360}
0*360}
0*360}
1*360}
For every TTI 10ms, there are two TB (Transport Block) for
FACH
If there is RRC message, one or two TB can be used by SRB FACH
Otherwise (No SRB FACH), TRB FACH can be transferred
69
HUAWEI TECHNOLOGIES CO., LTD.
70
HUAWEI TECHNOLOGIES CO., LTD.
71
HUAWEI TECHNOLOGIES CO., LTD.
72
HUAWEI TECHNOLOGIES CO., LTD.
73
HUAWEI TECHNOLOGIES CO., LTD.
HSDPA
Solution Introduction
Smartphone Signaling Storm Assessment
Smartphone Signaling Storm Optimization
Study Case
Page 81
Test Case
RRC times
PS RAB
times
Paging
times
SPU Utility
CE Num.
CELL-PCH
-30%
-30%
-26%
-4%
19%
URA<LAC
-30%
-30%
-27%
-6%
27%
URA=LAC
-33%
-33%
-27%
-7%
28%
-56%
-56%
-47%
-13%
34%
T2=2S
-33%
-33%
-31%
-5%
29%
T2=10S
-33%
-32%
-29%
-7%
28%
T2=15S
-28%
-27%
-25%
-4%
24%
URAPCH
FD
RRC State
Transfer
PCH
URA
FD
RRC
RNC08
4000
3500
3500
3000
3000
2500
2500
2000
2000
1500
1500
1000
1000
500
500
PCH
URA
FD
RRC
CELL_DCH UE
CELL_FACH UE
CELL_DCH UE
CELL_FACH UE
CELL_PCH UE
URA_PCH UE
CELL_PCH UE
URA_PCH UE
SPU Load
40.0
39.0
38.0
before
PCH
URA
37.0
FD
RRC state
transition timer
test
36.0
35.0
Weekend
weekend
Weekend
34.0
33.0
32.0
31.0
30.0
CE Utility Ratio
14000
before
PCH
URA
13000
12000
FD
RRC state
transition timer
test
Weekend
11000
10000
9000
8000
Weekend
Weekend
7000
6000
before
180000
PCH
URA
FD
RRC state
transition timer
test
160000
140000
120000
Weekend
100000
weekend
Weekend
80000
60000
40000
20000
0
before
PCH
URA
140000
FD
RRC state
transition timer
test
120000
100000
Weekend
weekend
Weekend
80000
60000
40000
20000
0
CS Traffic Volume
300
before
PCH
URA
250
200
Weekend
weekend
FD
RRC state
transition timer
test
Weekend
150
100
50
PS Traffic Volume
30000
PCH
25000
20000
URA
Weekend
15000
Weekend
FD
RRC state
transition timer
test
Weekend
10000
5000
0
Accessibility
100.00
before
PCH
URA
FD
99.50
RRC state
transition timer
test
99.00
98.50
98.00
97.50
RRC service
PS RAB
Retainability CS CDR
CS CDR
0.800
before
0.700
PCH
URA
FD
RRC state
transition timer
test
0.600
0.500
0.400
0.300
0.200
0.100
0.000
Retainablity PS CDR
*PS CDR formula is modified.
before
PCH
URA
0.450
0.400
0.350
0.300
Weekend
weekend
FD
RRC state
transition timer
test
Weekend
0.250
0.200
0.150
0.100
0.050
0.000
Thank you
www.huawei.com