Implementation “3G Network Controlled

Fast Dormancy” as one alternative

solution for High penetration Smartphone

Nokia global NPO sharing session

Jun/2016
1 05/05/2020 © Nokia 2016
Confidential
 Why we need Fast Dormancy ?
Number of Signaling

s
From idle Large packet from PCH Small packet from PCH
PS Call setup PCH to DCH
s
PCH to FACH
0 . 2
0. 5 d
1. Cell update with TVM (RRC) 1. Cell update (RRC)

e
2. Radio Link Setup (NBAP) 2. Cell update confirm (RRC)

e
1. RRC Connection Request (RRC)
3. Radio Link Setup Response (NBAP) 3. UMI confirm (RRC)

d N
2. Radio Link Setup (NBAP)
4.

e
3. Radio Link Setup Response (NBAP) Establish Requests (ALCAP)
5.

e
4. Establish Requests (ALCAP) Establish Confirm (ALCAP)
6. Establish Requests (ALCAP)

N
5. Establish Confirm (ALCAP)
6. RRC Connection Setup (RRC) 7. Establish Confirm (ALCAP)
7. NBAP Synchronization (NBAP) 8. CU confirm with RB reconfig (RRC)
8. RRC Connection Setup Complete (RRC) 9. NBAP Synchronization (NBAP)
10.

s
9. Initial Direct Transfer (GPRS) (RRC) RB reconfiguration complete (RRC)

2
10. Initial UE Message (RANAP) 11. Measurement Control (HO) (RRC)
12. Measurement Control (TVM) (RRC)

d
11. Common Id (RANAP)

e
12. Security Mode Command (RANAP)

e
13. Security Mode Command (RRC)
14. Security Mode Complete (RRC)

N
15. Security Mode Complete (RANAP) Number of messages
16. Downlink Direct Transfer (P-TMSI) (RRC)
RRC NBAP RANAP ALCAP
17. Uplink Direct Transfer (P-TMSI) (RRC)
18. RAB Assignment Req (RANAP) From Idle_mode to Cell_DCH 12 5 7 6
19. GTP Tunnel Setup (RANAP) From Cell_PCH to Cell_DCH 5 3 0 4
20. RB Setup (RRC)
21. Radio Link Setup (NBAP)
22.
23.
Radio Link Setup Response (NBAP)
Establish Requests (ALCAP)
Repeat session establishment from idle will clearly increase
24.
25.
Establish Confirm (ALCAP)
Establish Requests (ALCAP)
signalling load. However in high-mobility environments this will, to
26. Establish Confirm (ALCAP) some extent, be offset by the reduced cell/URA update activity.
27. RB Setup Complete (RRC)
28. RANAP:RAB Assignment Resp (RANP)
29. 2 Measurement Control (HO) (RRC)
30. Measurement Control (TVM) (RRC)
PS NPO Radio CC / June 2013
How to Implement Fast Dormancy ?
License and Activation Aspects
Licensing:
• RAN2136 Fast Dormancy is a BSW type of feature
• RAN2451 Fast Dormancy Profiling is an ASW type of feature (optional feature)
• RAN2451 is controlled by a long term On/Off feature license key
• Feature Code = 0000002284
• Feature Name = Fast Dormancy Profiling
Activation
• RAN2136 Fast Dormancy
• Operator activates Fast Dormancy in RNC by setting FastDormancyEnabled parameter
(0=Disabled, 1=Enabled)
• MSActivitySupervision value have to be >0 (>0 means that PCH states are supported in RNC)
before Fast Dormancy feature can be activated
• RNC updates System Information Block type 1 parameters by adding T323 timer
• Value of timer T323 is set by PRFILE and cannot be modified on-line
• RNC creates System Information Update Request message and send it to BTS’s
• BTS acknowledges successful operation with System Information Update Response
• The inclusion of T323 within SIB1 allows a UE to detect that the network supports Fast
Dormancy
• RAN2451 Fast Dormancy Profiling
• Fast Dormancy Profiling is activated by setting LFDProfEnabled parameter to „Enabled”
3
• LFDProfEnabled can be modified on-line and does not required object locking
 How to Implement Fast Dormancy ?
Parameter Aspects (RRC States & Transition)
The idea behind:
- Mandatory to activate 2nd
SCCPCH as FACH utilized
more.
- Try to push UE more into
Cell_PCH States instead of
IDLE MODE.
- Try to balance Transition
attempts from Cell_DCH to
Cell_FACH & Cell_FACH to
Cell_PCH
- For Small Packet Services1,
try to push UE more into
Cell_FACH instead of
Cell_DCH (or HSPA Chn.)
- If FACH congest, try to
utilize Fast Call Setup from
Cell_PCH to Cell_DCH
4
1. Packet Size < 500 byte
Phys. Reconfiguration
Frequent cell updates
Phys. Reconfiguration
URA Update, UL data, Paging
Fast call setup from
URA_PCH
CUCforPCHtoDCHallowed
After RT call with inactive
PS RABs & high mobility in
CELL_DCH
RRC Setup / Release
After RT call with
inactive PS RABs
Fast call setup from
UTRA RRC Connected Mode CELL_PCH
CUCforPCHtoDCHallowed
URA_PCH CELL_PCH
Phys. Reconfiguration UL/DL
activation timer
CELL_FACH Phys. Reconfiguration
CELL_DCH Cell Update, UL data, paging
RB. Reconfiguration
Traffic Volume, RACH load
RB. Reconfiguration
Inactivity Timer, Overload
IDLE Mode
How to Implement Fast Dormancy ?
Parameter Aspects (Traffic Volume Thresholds Setting)

• Higher traffic volume thresholds should be used for moving smartphones and
LFD Phones to Cell_DCH state
• It gives possibility to avoid unnecessary movement to Cell_DCH – only for
sending keep-alive message
• Stored IMSI gives possibility to faster usage of higher traffic volume thresholds

New higher traffic volume thresholds Legacy traffic volume thresholds

Default Default
Name Name
Value Value
Rel-99 FACH
SmartTrafVolThrUL 256 bytes TrafVolThresholdULLow 128 bytes
& RACH UL
Rel-99 FACH
SmartTrafVolThrDL 256 bytes TrafVolThresholdDLLow 128bytes
& RACH DL
HS-FACH &
SmartTrafVolThrUL 256 bytes TrafVolThresholdULLow 128 bytes
Rel-99 RACH

5
How to Implement Fast Dormancy ?
Parameter Aspects (Inactivity Timers Thresholds Setting)

• Shorter inactivity timers should be used for moving LFD Phones to Cell_PCH
state - saving UE battery
• It gives possibility to avoid unnecessary movement to IDLE_mode – less
signalling load

New shorter inactivity timers Legacy inactivity timers

Default Default
Name Name
Value Value
HS-DSCH SmartHSPATputAveWin 1s MACdflowthroughputAveWin 3s
Inactivity SmartHSPATimeToTrigger 0.2s MACdflowutilTimetoTrigger 0s
E-DCH SmartHSPATputAveWin 1s EDCHMACdFlowThroughputAveWin 3s
Inactivity SmartHSPATimeToTrigger 0.2s EDCHMACdFlowThroughputTimetoTrigger 5s
DCH InactivityTimerDownlinkDCH 5s
SmartInactivityTimerDCH 0.2s
Inactivity InactivityTimerUplinkDCH 5s
Rel-99 FACH
SmartInactivityTimerFACH 1s UL_DL_activation_timer 2s
inactivity

6
Impact to Network Performance (1 of 2)

• Following benefits are observed if UE has been recognized as LFD Phone:

• is faster moved from Cell_DCH to Cell_PCH state – lower utilization of cell
resources and lower UE power consumption (i.e. SmartHSPATimeToTrigger,
SmartInactivityTimerDCH)
• is kept in Cell_PCH instead of goes to IDLE_mode – less signalling is required for
moving to Cell_FACH or Cell_DCH
• higher amount of data could be sent in Cell_FACH/HS-Cell_FACH state (i.e.
SmartTrafVolThrUL threshold)
• Value of timers and thresholds could be used for network performance optimisation
• Shorter values of timers could be applied if we would like to release cell resources
faster - it will be useful in case with many smartphones application in network. In
other cases it could caused higher number of RRC States transitions
• Value of traffic volume thresholds should allow to send small pieces of data via
Cell_FACH (i.e. Keep-alive messages)

7
Impact to Network Performance (2 of 2)

• Changes of timers and thresholds values have impact on number of RRC State transitions
• Counters introduced by RAN2167 State Transitions Counters feature could be used for
monitoring those changes.

Parameter Name Counters for verification

M1006C228 CELL_DCH TO PCH ATTEMPTS
SmartInactivityTimerDCH M1006C225 CELL_DCH TO CELL_FACH ATTEMPTS
M1006C223 CELL_FACH TO IDLE
M1006C226 CELL_FACH TO PCH ATTEMPTS
SmartInactivityTimerFACH
M1006C223 CELL_FACH TO IDLE
SmartHSPATputAveWin M1006C228 CELL_DCH TO PCH ATTEMPTS
M1006C225 CELL_DCH TO CELL_FACH ATTEMPTS
SmartHSPATimeToTrigger M1006C223 CELL_FACH TO IDLE
M1006C232 FACH TO HS-DSCH/E-DCH
SmartTrafVolThrUL
SUCCESSFUL
M1006C232 FACH TO HS-DSCH/E-DCH
SmartTrafVolThrDL
SUCCESSFUL
8
Impact to KPI Formula & Solution
CSSR PS (1 of 3)

- CSSR PS will significant degraded after implement this feature (but not
affecting end user perception) due to significant reduction PS RRC & RAB
Attempts as impact to very less Idle_State.
in t us
m pla ation
il l co rad to
r w d e g in g
to me KPI affect !!
Cus to this h no ption
u e o u g rce
d n th r p e
Eve nd use
E

- Solution for this is to suggest operator to modify the formula as impact

from Fast dormancy activation. Meaning, it needs to included attempt from
9 Cell_PCH state as call started from Cell_PCH.
Impact to KPI Formula & Solution
CSSR PS Modification after Fast Dormancy (2 of 3)
KPI Name CSSR PS (RRC Part)
KPI Definition Call Setup Success Rate for PS service (RRC Part) [%] over the reporting period
System Nokia Huawei
(MOC_INTER_CALL_ATTS - MOC_INTER_CALL_FAILS + MOC_BACKG_CALL_ATTS - MOC_BACKG_CALL_FAILS +
MTC_INTER_CALL_ATTS - MTC_INTER_CALL_FAILS + MTC_BACKG_CALL_ATTS - MTC_BACKG_CALL_FAILS +
MOC_HIGH_PRIOR_SIGN_ATTS - MOC_HIGH_PRIOR_SIGN_FAILS + MTC_HIGH_PRIOR_SIGN_ATTS -
(RRC.SuccConnEstab.OrgInterCall + RRC.SuccConnEstab.OrgBkgCall
MTC_HIGH_PRIOR_SIGN_FAILS - RRC_ACC_REL_INTERACTIVE - RRC_ACC_REL_MO_BACKGROUND -
+ RRC.SuccConnEstab.TmItrCall + RRC.SuccConnEstab.TmBkgCall +
RRC_ACC_REL_MO_HIGH_PR_SIGN - RRC_ACC_REL_MO_INTERACTIVE - RRC_ACC_REL_MT_BACKGROUND -
VS.DCCC.P2D.Succ+
RRC_ACC_REL_MT_HIGH_PR_SIGN) / (MOC_INTER_CALL_ATTS + MOC_BACKG_CALL_ATTS +
Existing Formula VS.DCCC.P2F.Succ)/(RRC.AttConnEstab.OrgInterCall +
MOC_HIGH_PRIOR_SIGN_ATTS + MTC_INTER_CALL_ATTS + MTC_BACKG_CALL_ATTS +
RRC.AttConnEstab.OrgBkgCall + RRC.AttConnEstab.TmInterCall +
MTC_HIGH_PRIOR_SIGN_ATTS - RRC_ATT_REP_INTERACTIVE - RRC_ATT_REP_MO_INTERACTIVE -
RRC.AttConnEstab.TmBkgCall + VS.DCCC.P2D.Att+
RRC_ATT_REP_MO_HIGH_PR_SIGN - RRC_ATT_REP_MO_BACKGROUND - RRC_ATT_REP_MT_BACKGROUND -
VS.DCCC.P2F.Att)
RRC_ATT_REP_MT_HIGH_PR_SIGN - RRC_ACC_REL_INTERACTIVE - RRC_ACC_REL_MO_BACKGROUND -
RRC_ACC_REL_MO_HIGH_PR_SIGN - RRC_ACC_REL_MO_INTERACTIVE - RRC_ACC_REL_MT_BACKGROUND -
RRC_ACC_REL_MT_HIGH_PR_SIGN )

(MOC_INTER_CALL_ATTS - MOC_INTER_CALL_FAILS + MOC_BACKG_CALL_ATTS - MOC_BACKG_CALL_FAILS +

MTC_INTER_CALL_ATTS - MTC_INTER_CALL_FAILS + MTC_BACKG_CALL_ATTS - MTC_BACKG_CALL_FAILS +
MOC_HIGH_PRIOR_SIGN_ATTS - MOC_HIGH_PRIOR_SIGN_FAILS + MTC_HIGH_PRIOR_SIGN_ATTS -
MTC_HIGH_PRIOR_SIGN_FAILS - RRC_ACC_REL_INTERACTIVE - RRC_ACC_REL_MO_BACKGROUND -
RRC_ACC_REL_MO_HIGH_PR_SIGN - RRC_ACC_REL_MO_INTERACTIVE - RRC_ACC_REL_MT_BACKGROUND -
RRC_ACC_REL_MT_HIGH_PR_SIGN+ DENOM_ST_TRANS_TIME_PCH_DCH
Proposed
+DENOM_ST_TRANS_TIME_PCH_FACH) / (MOC_INTER_CALL_ATTS + MOC_BACKG_CALL_ATTS + SAME WITH ABOVE
Formula
MOC_HIGH_PRIOR_SIGN_ATTS + MTC_INTER_CALL_ATTS + MTC_BACKG_CALL_ATTS +
MTC_HIGH_PRIOR_SIGN_ATTS - RRC_ATT_REP_INTERACTIVE - RRC_ATT_REP_MO_INTERACTIVE -
RRC_ATT_REP_MO_HIGH_PR_SIGN - RRC_ATT_REP_MO_BACKGROUND - RRC_ATT_REP_MT_BACKGROUND -
RRC_ATT_REP_MT_HIGH_PR_SIGN - RRC_ACC_REL_INTERACTIVE - RRC_ACC_REL_MO_BACKGROUND -
RRC_ACC_REL_MO_HIGH_PR_SIGN - RRC_ACC_REL_MO_INTERACTIVE - RRC_ACC_REL_MT_BACKGROUND -
RRC_ACC_REL_MT_HIGH_PR_SIGN + ATT_PCH_TO_FACH + ATT_PCH_TO_DCH)

Recently Huawei includes P2D & P2F attempt and success into the formula to compensate losses of attempt due to FAST DORMANCY.
Remarks
After Fast Dormancy, UE will mostly stay at CELL_PCH.

Noted:
10 Found Total Success for these counter (DENOM_ST_TRANS_TIME_PCH_DCH + DENOM_ST_TRANS_TIME_PCH_FACH) > Total attempt of counter
(ATT_PCH_TO_FACH + ATT_PCH_TO_DCH), so there is RRC SR > 100% for some cells (still need to verify whether correction already applied after RU50).
Impact to KPI Formula & Solution
CSSR CS Modification after Fast Dormancy(3 of 3)
KPI Name CSSR CS (RRC Part)

KPI Definition Call Setup Success Rate for CS service (RRC Part) [%] over the reporting period

System Nokia Huawei

(MOC_CONV_CALL_ATTS - MOC_CONV_CALL_FAILS + MTC_CONV_CALL_ATTS -

((RRC.SuccConnEstab.OrgConvCall + RRC.SuccConnEstab.TmConvCall +
MTC_CONV_CALL_FAILS + EMERGENCY_CALL_ATTS -
RRC.SuccConnEstab.EmgCall)/(RRC.AttConnEstab.OrgConvCall +
EMERGENCY_CALL_FAILS) / ( MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS
Existing RRC.AttConnEstab.TmConvCall + RRC.AttConnEstab.EmgCall)) *
+ EMERGENCY_CALL_ATTS - RRC_ATT_REP_MO_CONV -
Formula ((VS.RAB.SuccEstabCS.AMR.12.2 +
RRC_ATT_REP_MT_CONV - RRC_ATT_REP_EMERGENCY)) *
VS.RAB.SuccEstCS.Conv.64)/(VS.RAB.AttEstabCS.AMR.12.2 +
(RAB_ACC_COMP_CS_VOICE + RAB_ACC_COMP_CS_CONV) /
VS.RAB.AttEstCS.Conv.64)) * 100
(RAB_STP_ATT_CS_VOICE + RAB_STP_ATT_CS_CONV)) * 100

(MOC_CONV_CALL_ATTS - MOC_CONV_CALL_FAILS + MTC_CONV_CALL_ATTS -

MTC_CONV_CALL_FAILS + EMERGENCY_CALL_ATTS -
EMERGENCY_CALL_FAILS+CELL_UPDATE_SUCC_CS_CALL) /
Proposed ( MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS + EMERGENCY_CALL_ATTS - Huawei to provide the matching formula with NOKIA to accommodate attempt at
Formula RRC_ATT_REP_MO_CONV - RRC_ATT_REP_MT_CONV - CELL_PCH state
RRC_ATT_REP_EMERGENCY+CELL_UPDATE_ATT_CS_CALL)) *
(RAB_ACC_COMP_CS_VOICE + RAB_ACC_COMP_CS_CONV) /
(RAB_STP_ATT_CS_VOICE + RAB_STP_ATT_CS_CONV)) * 100

Since CELL_PCH activation need to include attempt from CELL_PCH state, as

Remarks
calls started from Cell_PCH are not using RRC procedure but Cell Update procedure

11
Impact to Other Feature and etc.
Interoperation with Continuous Packet Connectivity - prioritization

If Continuous Packet Connectivity and Fast Dormancy

features are activated and UE is requesting FD then:
• If Fast Dormancy has higher priority then UE state is changed to PCH state
• If CPC has higher priority then UE state is not changed

Prioritization between Continuous Packet Connectivity and Fast Dormancy

is set via FastDormOverCpcPri parameter.
• FastDormOverCpcPri = false then Fast Dormancy has higher priority
• FastDormOverCpcPri = true then CPC has higher priority

In RU20OnTop parameter FastDormOverCpcPri is not available.

If Fast Dormancy and CPC features are activated then system behaviour is the same as
when FastDormOverCpcPri = 0.
12
Impact to Other Feature and etc.
Behavior with RAB and Multi RAB‘s

The following procedures are performed when UE sends message SCRI with “UE
Request PS data session end” or empty SCRI* and have following RAB(s):

UE RAB’s PS RAB or multiple PS RAB or multiple PS CS RAB

PS RABs and CS RABs
RAB

State after SCRI with • PS resources are •PS resources are • Fast Dormancy
“UE Request PS released released not supported
data session end” • UE stays in • UE goes to cell_PCH
message or empty cell_DCH or URA_PCH
SCRI*
* - only if RAN2451 Fast Dormancy Profiling is activated

13
Some Trial Result (1)

de in ta in
ra in ta a in
D eg M a M
PS CS R99
R R S
CS
S
CS
S RP
DC

ove se d
pr e a
Im ve In cr
lig htly mp ro
g htly
R s R I s li
DC PS d
A Loa
DP H
HS FAC

14
Some Trial Result (2)

PROs CONs Remark

XPU Load increase 3-5% Inline with traffic increase
Less UE mean cells, traffic
DPU Load decreased by 2-3%
increase
UE Mean Cell decreased by 25% Less UE mean cells
RTWP Improve 1-2 dB Less UE mean cells
CS Traffic increase by 30% Indicating EcNo improvement
HSDPA Traffic is maintained
HSDPA+HSUPA+Rel99 traffic increase
HSDPA means user throughput is maintained
CSSR failure is less and
Absolute number of CSSR PS Failure CSSR attempt is also less, but
CSSR PS Degraded
decrease overall % CSSR PS is
decreased
CSSR CS maintained
DCR PS improve -
DCR CS improve Better EcNO
15