Classification : Interne

RNO Training on the Job

State transition 3G

September 2019
Classification : Interne

Agenda

RRC State Transition

Cell_DCH/Cell_FACH/Cell_PCH

State Transition and channel type switch :

Functionnal Description

summary
Classification : Interne

RRC State
Transition
Classification : Interne

CELL_DCH state 4

CELL_DCH state (carried

over the DCH)
A UE in this state occupies
dedicated channel resources and
consumes a large amount of radio
CELL_DCH state for HSDPA
resources.
services (carried over the HS-
DSCH)
This state is suitable for high-speed
data transmission
CELL_DCH state for HSUPA services
 After HSPA is introduced, the (carried over the E-DCH)
CELL_DCH state is categorized
as follows :
Classification : Interne

CELL_FACH state 5

 Monitor a FACH to receive signalling

messages or user data addressed to
 A UE in this state uses the common
the UE or any broadcast messages
channel to send or receive data,
which occupies only a small amount
 By default, use RACH for transfer of
of resources.
signalling messages or user data in
the uplink according to the random
 Because of resource limitations on
access procedure
the RACH and FACH, the
CELL_FACH state is suitable for low-
 Perform cell reselection and upon
speed data transmission.
selecting a new UTRA cell, initiate a
cell update procedure
 The UE is known on cell level
according to the cell where the UE
 Perform measurements and transmit
last made a cell update.
measurement reports according to the
measurement control information
Classification : Interne

CELL_PCH 6

In the uplink, a UE in this state cannot transmit signaling

messages. If the UE has data to transmit on the uplink, it needs to
1 go through the cell update procedure to transit to the CELL_FACH
or CELL_DCH state.

In the downlink, the UE uses discontinuous reception (DRX) to

2 monitor messages on the PCH at a given moment. The purpose is
to receive paging messages,

The UTRAN can obtain the serving cell of the UE and page the UE
3 within the serving cell. After moving to another cell, the UE needs
to send a CELL UPDATE message to perform cell reselection.
Classification : Interne

Functionnal
Description
Classification : Interne

PS Connection Establishment 8

 In the RRC connection setup procedure

the UE is always transferred directly to
CELL_DCH state in Nokia RAN

 After the UE has completed a RRC Connection setup procedure with

the RNC, dedicated channel resources are allocated to the UE (a DCH
for the signalling link is setup).

 The UE performs a NAS connection establishment to the PS CN.

 After the service negotiation has been carried out between the UE and
PS CN, the PS CN sends a RAB assignment to the RNC.

 The RNC’s RRC signalling entity performs a radio bearer setup with a
RRC:Radio Bearer Setup procedure.

 The RNC’s RRC signalling entity starts a supervision timers UL_DLcapacityReqWait (5s) and SignallingLinkInactivityTimer (2s)

 If the capacity request is received from the UE or from the RNC’s within the UL_DLcapacityReqWait, the DCH for NRT RB(s) is allocated.

 If there is no activity in RB(s) within the UL_DLcapacityReqWait and the inactivity of signalling link is detected ‘SignallingLinkInactivityTimer’ has also
expired, the state transition from CELL_DCH to CELL_FACH is initiated
Classification : Interne

Transition: Cell_DCH to CELL_FACH 9

 In case the RNC detects inactivity (nothing sent or received), it will indicate this to the RRM and RRC signaling entities of the RNC.

 After receiving the inactivity indication, the RRC signalling entity defines and starts an inactivity timer (InactivityTimerUplinkDCH or
InactivityTimerDownlinkDCH).

 SmartInactivityTimerDCH : This parameter is also used for the identified Legacy Fast Dormancy Smartphone, instead of the
InactivityTimerDownlinkDCH and InactivityTimerUplinkDCH parameters.

 After the inactivity timer expires the RRC radio bearer reconfiguration–procedure is performed. RRC sends an RRC: RADIO BEARER
RECONFIGURATION message to the UE. UE acknowledges by sending the RRC: RADIO BEARER RECONFIGURATION COMPLETE –message
to the RRC signaling entity of the RNC

 In case the UE is having RT RB which has become inactive and at the same time it is having inactive NRT RB then RADIO BEARER RELEASE
procedure is used (instead of RADIO BEARER RECONFIGURATION).
Classification : Interne

Switching from HS-DSCH to FACH(1/2) 10

HS-DSCH released and channel type switching to Cell_FACH in one of the following
cases

Low
utilization

Channel Low
type throughput
switching in
cell FACH

multi-RAB with AMR:

Transition to Cell_DCH
with AMR +
NRT DCH 0/0
Classification : Interne

11
Switching from HS-DSCH to FACH(2/2)

 Low Throughput indicated when

 Low Utilisation indicated when :
 MAC-d flow throughput below MACdflowthroughputRelThr (0
 MAC-d flow throughput below MACdflowutilRelThr (256 bps) during time to trigger MACdflowthroughputTimetoTrigger
bps) during time to trigger MACdflowutilTimetoTrigger (5s)
(0s)
 AND there is still data in the BTS buffer (abnormal release)
 AND RLC does not have any data to send
 After MAC-d flow release HS-DSCH not allowed until guard timer
 AND there is no more data in the BTS buffer (normal HsdschGuardTimerLowThroughput (30s)expires
release)

Throughput calculated by counting all transmitted bits during configurable

sliding measurement window MACdflowthroughputAveWin (2s/3s)
Classification : Interne

12
Switching from E-DCH to FACH

Transition from E-DCH to CELL_FACH is applicable when the uplink E-DCH NRT
MAC-d flow is released due to low throughput.

Conditions:

 MAC-d flow throughput below EDCHMACdFlowThroughputRelThr (256

bps)
 EDCHMACdFlowThroughputTimetoTrigger (0s)
 EDCHMACdFlowThroughputAveWin (2s/3s)
 SmartHSPATputAveWin (1s)
 SmartHSPATimeToTrigger (0.2 s)
 EDCHMACdflowtputStrTtT (5s)
Classification : Interne

13
Transition: CELL_FACH to CELL_DCH (1/2)

 TrafVolThresholdULLow (128 bytes)

 TrafVolThresholdDLLow (128 bytes)

 SmartTrafVolThrDL 1 kB (1024)

 TrafVolPendingTimeUL (2000ms)
Classification : Interne

14
Switching from HS-DSCH to DCH

 Trigger

 Last HSDPA capable cell dropped (removed from AS)

 Event 1F (for all active cells) : Serving cell CPICH becomes worse than an absolute threshold
(HHoEcNoThreshold ; HHoRscpThreshold; HHoEcNoTimeHysteresis)

 Event 6A (too high UE Tx power)

 Too high DL RL power

 UL quality deterioration

Nb : Only if ISHO process triggered. In case of IFHO process switch not required

 DCH allocation

 attempted in next scheduling period with initial bit rates defined by InitialBitRateUL (16 kbps ) and
InitialBitRateDL (16 kbps)

 If initial bit rates can not be allocated, DCH 0/0 is offered

Classification : Interne

15
Switching from DCH to HS-DSCH

 General Conditions

1. UE has RAB combination supporting HSDPA

Not more than three NRT RABs (if multi RAB NRT support
enabled)
No R99 streaming or NRT RAB (if multi RAB NRT support
disabled) Cause : Capacity

2. UE and at least one active cell HSDPA capable  UL: TVM > TrafVolThresholdULHigh (1024 bytes)
If HSDPAMobility = disabled, active set size must be 1  DL: TVM > TrafVolThresholdDLHigh (1024 bytes)
 TrafVolTimetoTriggerDL(UL) (0s)
3. No inactivity or low utilization detected on DCH (DL/UL)  Conditions for HSDPA allocation fulfilled
HSDSCHGuardTimerLowThroughput (30s)
4. No guard timers running to prevent HS-DSCH selection

HsdschGuardTimerHO (5s)
HSDSCHGuardTimerLowThroughput (30s)
HSDSCHCTSwitchGuardTimer (5s)

5. RAB attribute “Maximum bit rate” does not prevent use of HSDPA prevent use
of HSDPA

HsdschGuardTimerHO : The parameter determines a period of

time during which the HS-DSCH allocation is denied after successful
channel type switching from HS-DSCH to DCH 0/0 kbps due to
handover reasons.

HSDSCHGuardTimerLowThroughput : It is started after a release

of the MAC-d flow, which was triggered by low throughput. The timer is
HSDSCHCTSwitchGuardTimer : This parameter
started just if DCH 0/0 is allocated. When the timer is running HS-DSCH
determines the time that must be waited after an HS-
allocation is not allowed to the UE.
DSCH to DCH channel type switching before an
DCH to HS-DSCH channel type switching can be
done.
Classification : Interne

16
Transition from CELL_DCH to CELL_PCH
CELL_DCH
CELL_PCH
Classification : Interne

17
Transition from CELL_FACH to CELL_PCH

 Since the MS performs continuous reception of FACH in CELL_FACH state, it should be moved to
the CELL_PCH state if the data service has not been active for a while.

 This state transition is done when the RNC’s RRC timer “FACH activation timer” expires.

 This timer is started when the RNC's MAC entity for MS indicates observed inactivity in UL and DL
direction.

 Also, the state transition from CELL_FACH to CELL_PCH is done immediately after successful Cell
Update procedure due to 'cell reselection' or 'periodic cell update' in case the UE was in CELL_FACH
before executing Cell Update procedure.

• “FACH activation timer” = UL_DL_activation_timer

(2s/5s) for UEs supporting CELL_PCH

• “FACH activation timer” for UEs recognized as

Smartphone's = SmartInactivityTimerFACH
Classification : Interne

Returning from Cell_PCH to Cell_DCH 18

After transition:
 UE stays in Cell_PCH until new data UL/DL in L2 buffers.

 Direct return / reconfiguration to Cell_DCH possible, if traffic volume threshold TrafVolThrDLLowGTP (non-
configurable parameter) exceeded & CUCforPCHtoDCHallowed = true.

 RNC must send a paging notification to get in touch with UE.

 UE answer with RRC: Cell Update (cause: paging response)

Classification : Interne

Returning from Cell_PCH to Cell_DCH 19

 On reception on Cell Update message from UE, RNC checks if CUCforPCHtoDCHallowed = 1 and
EcNo > CUCEcNoThreshold (default = – 9 dB)  RNC sends Cell Update Confirm message.

 Else RNC moves UE to Cell_FACH.

Classification : Interne

Transition from CELL_PCH to CELL_FACH 20

 cell update or data in the buffer

Classification : Interne

Transition from CELL_PCH to idle 21

(15 min)
Classification : Interne

22

summary
Classification : Interne

Summary 23

Inactivity

DCH FACH
 InactivityTimerUplinkDCH
 InactivityTimerDownlinkDCH
 SmartInactivityTimerDCH

Low Throughput/Low utilisation

HS-DSCH FACH
 MACdflowutilRelThr (256 bps)
 MACdflowutilTimetoTrigger (0s)
 MACdflowthroughputTimetoTrigger (5s)
 After MAC-d flow release HS-DSCH not
allowed until guard timer
HsdschGuardTimerLowThroughput (30s)
expires
 MACdflowthroughputAveWin (2s/3s)
 SmartHSPATimeToTrigger

Low Throughput

E-DCH FACH
 EDCHMACdFlowThroughputRelThr (256
bps)
 EDCHMACdFlowThroughputTimetoTrigger
(0s)
 EDCHMACdFlowThroughputAveWin (2s/3s)
 SmartHSPATputAveWin (1s)
 SmartHSPATimeToTrigger (0.2 s)
 EDCHMACdflowtputStrTtT (5s)
Classification : Interne

Summary 24

Inactivity

Cell_FACH Cell_PCH
 UL_DL_activation_timer (2s/5s)
 SmartInactivityTimerFACH

Capacity

Cell_PCH Cell_DCH
 CUCforPCHtoDCHallowed = true
 TrafVolThrDLLowGTP (128 Byte) exceeded
 EcNo > CUCEcNoThreshold (-9dB)

Inactivity

Cell_PCH Idle
 MS Connectivity supervision >15min
Classification : Interne

Summary 25
Capacity Request

Cell_FACH Cell_DCH
 TrafVolThresholdULLow (128 bytes)
 TrafVolThresholdDLLow (128 bytes)
 SmartTrafVolThrDL 1 kB (1024)
 TrafVolPendingTimeUL (2000ms)

HS-DSCH DCH

Capacity

DCH HS-DSCH
 UL: TVM > TrafVolThresholdULHigh (1024 bytes)
 DL: TVM > TrafVolThresholdDLHigh (1024 bytes)
 TrafVolTimetoTriggerDL(UL) (0s)
 Conditions for HSDPA allocation fulfilled
HSDSCHGuardTimerLowThroughput (30s)
Classification : Interne

KPIs 26
Classification : Interne

KPIs 27
Classification : Interne

28

Thank You
For Your
Attention