Nemo L3 PS Intro v1 PDF

PS Data Call Analysis Intro
Nokia RNWP
1 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

Contents
• PS Mobility Management States
• PS Call Signaling
• PS State Transition
• Dynamic Link Optimization (DyLO)
• Essential PS Parameters
• PS Call Analysis Method and Case study.

PS Mobility Management States

PS Mobility Management States
State of Attached
3G-SGSN only: RAB
S-RNC Relocation
PS Signalling Connection
Establishment
PMM-CONNECTED PMM-IDLE
PS Signalling Connection
Release
PDP Context
GPRS Attach
GPRS Detach Implicit GPRS Detach

GPRS Attach Reject PMM-DETACHED
(SGSN: MS Reachable
RAU Reject Timer expires)
(adopted from TS 23.060 V3.13.0)

Packet Data Protocol (PDP) States
UE 3G-SGSN GGSN
Activate PDP Context
INACTIVE ACTIVE
Deactivate PDP Context

or
MM context change to PMM-DETACHED
(adopted from TS 23.060 V3.13.0)
Location Area Concepts 10701,11701, The only rule is
LAC must smaller than MSC.
For the time being, LAC
update only happens during
Location Area LAI = MCC MNC LAC idle mode.
LA2
LA1
All "1", RAC is not supposed to

Routing Area RAI = MCC MNC LAC RAC
be equivalent to RNC, The only
rule is RAC must be smaller
than LAC.
RA3 RAC update can be seen during
connected mode.
RA2 LA2
RA1
RA4
Same with cell ID, It's
not functioning for the
time being.
Service Area SAI = MCC MNC LAC SAC

SA7
SA1 SA4 LA2 SA8
SA3
LA1
SA2 SA5 SA6

PS Call Signalling

PS DATA CALL
RRC Connection Setup
Attach & Authentication Procedure
PDP Context Activation & Radio Bearer

Setup Procedure
Radio Bearer Reconfiguration
PDP Context Deactivation Procedure
Detach & Radio Bearer Release Procedure
RRC Connection Release

spreadingFactorAndPilot : sfd32 --> 64K
This RAB Reconfig is not requested by UE
(No MR E4a found prior to this RAB_Reconfig.
RB 0/0 kbps
Traffic Volume
Measurement Report
(e4a).
UL data: FTP log in request
1st Radio Bearer

Reconfiguration with
“Initial & Minimum Bit
Rate” 64/64 kbps
2nd Radio Bearer

Reconfiguration with
possible maximum bit rate (
based on resource status)
64/384 kbps

PS DATA CALL
UE BTS RNC PS_CN
RRC_Connection_Request
RRC_Connection_Setup
RRC_Connection_Setup_Complete
Attach_Request
Authentication_n_Ciphering Request
Authentication_n_Ciphering Response
Security_Mode_Command
Security_Mode_Complete
Attach_Accept
Attach_Complete
Activate_PDP_Context_Request
Radio_Bearer_Setup
Radio_Bearer_Setup_Complete
Activate_PDP_Context_Accept
Radio_Bearer_Reconfiguration
Radio_Bearer_Reconfiguration_Complete

MS BTS RNC PS_CN
RRC:RRC CONNECTION REQUEST
PS DATA CALL
NBAP:RADIO LINK SETUP REQUEST
NBAP:RADIO LINK SETUP RESPONSE
AAL2SIG: ERQ
AAL2SIG: ECF
RRC:RRC CONNECTION SETUP
L1 synchronisation
MS BTS RNC CS_CN
NBAP:SYNCHRONIZATION INDICATION
PDP Context is active

RRC:CONNECTION SETUP COM PLETE
RRC:INITIAL DIRECT TRANSFER (Attach Request) RRC: DT (Deactivate PDP context request)
RANAP: DT (Deactivate PDP context request)
RANAP:INITIAL UE M ESSAGE
RANAP: RAB ASSIG NM ENT REQ UEST
(Attach Request)
(Release)
RANAP: DIRECT TRANSFER RANAP: RAB ASSIG NM ENT RESPONSE
RRC: DOW NLINK DIRECT TRANSFER (Attach Accept) NBAP:RL RECONFIG URATIO N PREPARE
(Attach Accept)
NBAP:RL RECONFIG URATIO N READY

RRC: DOW NLINK DIRECT TRANSFER (Attach Com plete)
RANAP: DT (Deactivate PDP context accept)
RANAP: DIRECT TRANSFER
RRC: UPLINK DIRECT TRANSFER (SM :Activate PDP Context request) (Attach Com plete) RRC: DT (Deactivate PDP context accept)

NBAP:RL RECONFIGURATION COM M IT
(SM : Activate PDP Context request)
RRC: RADIO BEARER RELEASE
RANAP:RAB ASSIGNM ENT REQUEST

RRC:RADIO BEARER RELEASE CO M PLETE
RRC: RADIO BEARER SETUP RRC: DT(Detach request)
RANAP: DT(Detach request)

RRC: RADIO BEARER SETUP COM PLETE
RANAP: DT(Detach accept)
RRC: DT(Detach accept)
RANAP:RAB ASSIGNM ENT RESPONSE
NBAP:RL DELETION REQ UEST

(SM : Activate PDP Context accept) AAL2SIG: REL
RRC: DOWNLINK DIRECT TRANSFER (SM : Activate PDP Context Accept) NBAP:RL DELETIO N RESPONSE
AAL2SIG: RLC
RRC: M EASUREM ENT REPORT
AAL2SIG : REL
NBAP:RADIO LINK RECONFIGURATION PREPARE AAL2SIG : RLC

RANAP: Iu Release Comm and
NBAP:RADIO LINK RECONFIGURATION READY
RRC: RRC CO NNECTION RELEASE RANAP: Iu Release Com plete
AAL2SIG: ERQ
RRC: RRC CO NNECTIO N RELEASE CO MPLETE
AAL2SIG: ECF
NBAP:RADIO LINK RECONFIGURATION COM M IT
RRC: TRANSPORT CHANNEL RECONFIGURATION
RRC: TRANSPORT CHANNEL RECONFIGURATION COM PLETE
Uplink and downlink data transfer

Multi RAB (Simultaneous AMR+PS)
PS
Disconnect
AMR
AMR
Disconnect
12 © NOKIA PS Intro.PPT / Aug 2006 / MHL

PSCompany Confidential
Packet Scheduling Principles
• Packet Scheduler switches between common channels (FACH/RACH = low
capacity) and dedicated channels (DCH = higher bit rates)
• Packet Scheduler allocates to RABs temporarily dedicated channels with a
set of maximum bit rates
• For instance within an allocation for 384kbit/s, the instantaneous bit
rate can be {0, 8, 16, 32, 64, 128, 384} kbit/s
• Packet Scheduler allocates DCH based on Capacity Requests
• A Capacity Request (Nokia term) is triggered based on traffic volume
measurement info: the sender (UE or RNC) has data in buffer and no
sufficient dedicated channel
• Packet Scheduler releases DCH upon inactivity
• Packet Scheduler re-schedules continuously DCH to serve all requests
equally, and take into account changes in non-controllable load

Packet Scheduling
overload
Power PtxTargetBTS PrxTargetBTS
/ Load
PtxOffset PrxOffset
PtxTarget PrxTarget
PtxTotal (variable) PrxTotal

PtxNrt PrxNrt
Desired
Prx/Ptx
Values
PtxRt PrxRt
controllable load
i.e. non RT Traffic
non-controllable load
i.e. RT Traffic
time
PS Data Call State Transition

RRC Modes and Packet Scheduling
UTRA RRC Connected Mode
URA_PCH CELL_PCH
Cell_Update, UL_Tx
Traffic_volume
UL/DL Activation timer
(10s)
CELL_DCH CELL_FACH
1. MS Activity
Supervision
timer (30min):
Release RRC when still
Establish RRC DCH_Inactivity Timer having
Connection (10s) Connection RB_connected.
or
2. PS CN Inactive
signaling time
supervision: 30s
(UE camps on UTRAN cell) :when RB is
disconnected.(re
If this is not enact, then the Cell_PCH & URA_PCH is not all
moved in
Idle Mode RAN04)

1. PS Connection Establishment
CELL_
DCH UE RNC SGSN
RRC Connection Establishment (SRB)
Signaling Radio Bearer
PMM & CM (e.g. PDP Context Activation)
Traffic Volume RAB Assignment Request

Parameters
determination
Start
Measurement Control [Traffic Volume Measurements] • UL_DLcapacityReqWait
• (RB_InactivityTimer)
• SignallingLinkInactivityTimer
UL_DLcapacityReqWait
expiry
yes
no
SignallingLinkInactivityTime
Capacity Request? expiry
yes
DCH for NRT RB(s) allocation CELL_
17 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential FACH
1-a PS Connection Establishment
Parameter Description Range Default Current Remark
Name Setting
UL_DLcapacity The timer is set after a DCH for a signaling link is allocated in the
RRC connection setup phase and a U-plane RB has been setup in
0 ... 20 s, 5s 10s
ReqWait the MS. The timer stops when any DL/UL activity is detected (i.e. step 0.5 s
capacity request received from the MS or MAC entity of the RNC)
and a DCH for the U plane RB(s) is allocated. If the MS is in
CELL_FACH state, a state transition to CELL_DCH is initiated.
The timer is also used in the following signaling cases:
- when the MS is in CELL_DCH state and a RAB assignment request
is received from the PS CN,
- after the MS has detected a radio link failure in CELL_DCH state,
has been transferred to CELL_FACH state and sent a cell update to
the RNC, and
- when the MS is in CELL_FACH state and a RAB assignment request
is received from the PS CN. In the expiry of the timer (no capacity
request id received from the MS or MAC-d entity of the RNC), the
state transition from CELL_DCH to CELL_FACH is initiated when also
the SignallingLinkInactivityTimer has expired (and no RT RB(s),
nor another active NRT RB(s) exists at the moment). If the MS is in
CELL_FACH state, the state transition to CELL_PCH is initiated when
the next inactivity indication is received from the MAC-c entity.
SignaillingLink The timer is used for inactivity detection of the 0 ... 20 s, 2s 2s

Inactivity signalling link in CELL_DCH state. The timer is step 0.5 s
detected and reset when any activity detected.
Timer
In expiry of the set after inactivity of the
signalling link is timer, a state transition from
CELL_DCH to CELL_FACH state is initiated when
also the corresponding RB inactivity timer(s)
expired.

2. Transition from CELL_DCH to CELL_FACH
CELL_
DCH UE Node B RNC
PDU Transport on the DCH/DPCH

All data is sent and
RLC-U buffer is empty
Inactivity detected Start
InactivityTimerUplinkDCH
InactivityTimerDownlinkDCH
Radio Bearer Reconfiguration Expiry
CELL_
FACH Radio Bearer Reconfiguration Complete
L2 configuration
Radio Link Deletion

Start
MAC: Inactivity detected
UL/DL activation timer

2-a. Transition from CELL_DCH to CELL_FACH
Name Setting
Inactivity The time indicating how long the radio and 0~20s, 8 kbps: 5 s 20S In order to avoid
Timer for transmission resources are reserved after silence step:1s 16 kbps: 5 s too frequent state
UL(DL) DCH detection on downlink/uplink DCH before release 255 s transition between
procedures. (infinity)
32 kbps: 5 s Cell_DCH and
:Parameter value 64 kbps: 3 s Cell_FACH. (20s)
255 (infinity)
means that NRT 128 kbps: 2 s
DCH inactivity
supervision is not 256 kbps: 2 s
used.
320 kbps: 2 s
384 kbps: 2 s

3. Transition from CELL_FACH to Cell_PCH/URA_PCH
CELL_
FACH UE RNC
Start
MAC: Inactivity detected
UL/DL activation timer (10s)
CELL_ Expiry
PCH Radio Bearer Reconfiguration
CELL_ Inactivity detected Start

FACH Cell Update
MaxCellReselections
URA_ CellReselectionObservingTime
PCH Cell Update and
MaxPeriodicalCellUpdates
Cell Update Confirm
Expiry
analog in
URA_ CELL_PCH
PCH Transition to URA_PCH
URA Update
MSActivitySupervision (30min)
RRC- URA Update
IDLE URA Update Confirm
3-a. Transition from CELL_FACH to Cell_PCH
Name Setting
UL/DL This timer is used on MAC -c to detect idle periods 50 ... 10000 2000 ms 10000ms In order to avoid
activation timer on data transmission (NRT RBs and SRBs) for the ms, step 50 too frequent state
UE, which is in Cell_FACH state. ms transition between
Based on this timer the MAC -c shall give the Cell_FACH and
No_Data indication to the RRC, which further can Cell_PCH. (10s)
change the state of the RRC from Cell_FACH
state to the Cell_PCH state (or URA_PCH state).
MS activity MSActivitySupervision timer is used in RRC states 0 ... 1440 30 min 30 min Note: If the
supervision CELL_PCH and URA_PCH for supervising the min, step 1 parameter value is
timer inactivity of NRT RAB(s). Timer is started when a min set to zero:
state transition to either of these states is - state transition to
executed. Cell_PCH/URA_PC
In expiry of the MSActivitySupervision timer when H is not allowed
the first 'inactive state indication‘(I.e. cell/URA when inactivity is
update, which does not cause the (re)initiation o detected in
fthe signalling or data flow) is received from the Cell_FACH state,
MS, the RNC asks SGSN to release the Iu the MS will be
connection. switched to the Idle
Mode

4. Transition from CELL_FACH to CELL_DCH
UE initiated
CELL_
FACH UE Node B RNC
Measurement Report (Traffic Volume Event)
UL & DL packet scheduling
Radio Link Setup

CELL_
DCH Radio Bearer Reconfiguration Complete It will assign 384K directly if there is data through

4-1. Transition from CELL_FACH to CELL_DCH
RNC initiated
CELL_
FACH UE Node B RNC
DL capacity need is
detected by MAC
Channel type selection
-> DCH
UL & DL
packet scheduling
Radio Link Setup

CELL_ Radio Bearer Reconfiguration Complete
DCH

WAP (Always on mode)
Now it's 10S
Cell_DCH
After ~20s WAP

Inactivity timer for DCH (UL/DL): 20 sec
Inactivty timer in NRT RB setup: 10s Cell DCH
Signalling link inactivity timer: 2s
UL/DL activation timer: 10s -DCH inactivity timer:
MS activity supervision timer: 30 min
20s
Cell FACH
- UL/DL activation timer:
Cell_FACH
After ~10s
10s
Cell_PCH
Cell PCH
-MS activity supervision
Cell_FACH timer: 30min
(hardcoded).
Cell_PCH * RRC_Release was after
After
~30min 30 min.
RRC_Released (PMM_Idle)
Cell_FACH
Idle
04Jun09 Always_on4.dt1

Dynamic Link Optimization in PS

Triggering of Dynamic Link Optimisation
Ptx, ave is averaged radio

link power, measured and
reported to RNC by BTS
distance
Ptx, RL Ptx, max is determined by
Ptx, max admission control
Offset The value of the Offset is
fixed, 2 dB
Dynamic link optimisation
Triggering of DyLO is triggered if
Ptx, ave Ptx, ave > Ptx, max - Offset
time

Decision algorithm
Triggering of DyLO
DyLO is not possible during compressed mode
DyLO is possible for NRT DCH allocations that have

lasted at least 2 seconds (fixed guard time)
Not applicable in RAN1.5 (only 1 NRT DCH possible

per UE)
• SF is doubled (physical channel bit rate reduced

to half of the original)
• Additional puncturing is not allowed
• DyLO cannot reduce bit rate below the Initial and
minimum allowed bit rate in downlink
(RAN1.5.2ED CD19) Nokia 把這兩個參數設成一個, 即64JKBps.
• DyLO can be started only if the current bit rate is

higher than Maximum Allowed DL User Bitrate in
HHO (enable compressed mode due to DL power)

Example DLO : PtxDLabsMax 50 dBm, PtxTotalMax 43dBm
PtxDLabsMax 50 dBm
PtxTotalMax 43dBm 384kbps:40dBm
Calculated max RL pwr

Ptx,max 128kbps:39.387dBm
Calculated max RL pwr - DLOptimisationPwrOffset
Ptx, threshold
DL pwr (dBm)
Default hidden
value is 2dB
PtxPrimaryCPICH 33dBm
Ptx ,ref
PtxPrimaryCPICH – CPICHtoRefRABoffset = 31 dBm
PS NRT & MultiRAB:

• This is where DLO triggers. (If PtxDLabsMax is set high)
•384kbps:38dBm
•128kbps:37.387dBm

Related Parameters – operator controllable
• WCEL: PtxDLAbsMax - Planned maximum downlink transmission power of a radio
link
• The planned maximum downlink transmission power of radio link. This parameter is used in the downlink power
allocation when CCTrCH includes one or more DCH's of interactive or background traffic class RAB's. The allocated
power of a radio link cannot exceed the value of this parameter. The parameter is set separately for each cell. This
parameter is the planned maximum, not the physical limit.
• -10...50 dBm, step 0.1 dBm, default 50 dBm
• WBTS: PtxDPCHmax - DPCH downlink transmission power maximum value

• Parameter defines the maximum code channel output power for the power control dynamic range of BTS. The power
control dynamic range of BTS is the difference between the maximum and the minimum transmit output power of a
code channel. The maximum transmission power is calculated by adding the value of the parameter to the BTS
maximum output power (Pmax in dBm).
• -3...0 dB, step 0.1 dB, default –3 dBm
• WCEL: MinAllowedBitRateDL - Initial and minimum allowed bit rate in downlink

• This parameter defines the minimum allowed bit rate in downlink that can be allocated by the PS. The allocated bit
rate corresponds to the highest bit rate in the TFS from which the TFCS is constructed.
• 64, 128, 384 kbps, default 64 kbps (RAN1.5)
• 8, 16, 32, 64, 128, 384 kbps, default 32 kbps (RAN04)
• 8, 16, 32, 64, 128, 256, 384 kbps, default 32 kbps (RAN05)
• WCEL: HHoMaxAllowedBitrateDL - Maximum Allowed DL User Bitrate in HHO

• This parameter determines the bitrate threshold which the maximum allocated user bitrate on the downlink DPCH
may not exceed in order for the inter-frequency or inter-RAT (GSM) handover to be possible due to high downlink
DPCH power level.
• 64, 128, 384 kbps, default 64 kbps (RAN1.5)
• 32, 64, 128, 384 kbps, default 64 kbps (RAN04)
• 32, 64, 128, 256, 384 kbps, default 64 kbps (RAN05)

Related Parameters – fixed
• Dynamic link optimisation usage
• Always used
• Downlink transmission power offset for dynamic link optimisation
• 2 dB
• Guard time for dynamic link optimisation
• 2s

Restrictions
• Radio link under DRNC
• Radio link under DRNC cannot trigger DyLO
• Transmission resources
• The reconfiguration of Iub AAL2 transmission resources is not
performed due to DyLO
• Compressed mode
• DyLO is not allowed during the compressed mode measurements

RAN04/RAN05 Additions to Dynamic Link Optimisation
• Possible downgrade steps (if not restricted by parameters *)
• RAN1.5
• 384 -> 128 (1 SF step)
• 128 -> 64 (1 SF step)
• RAN04 (in addition to RAN1.5) ??-->64K
• 64 -> 32 (1 SF step)
• 32 -> 16 (1 SF step) 64K -->128K
• 16 -> 8 (1 SF step) 128K-->384K
• RAN05 (in addition to RAN04)

• 256 -> 128 (1 SF step)
• 384 -> 64 (2 SF steps)
• 256 -> 64 (2 SF steps)
• 128 -> 32 (2 SF steps)
• 64 -> 16 (2 SF steps)
• 32 -> 8 (2 SF steps)
* Initial and minimum allowed bit rate in downlink

* Maximum Allowed DL User Bitrate in HHO

Bitrate Upgrade Possibilities in Nokia RAN
Example: Max Bitrate 384kbps, Initial Bitrate 64kbps
SF32(64k) SF8(384k) SF16(128k) CELL-FACH SF32(64k) SF8(384k) ○
Inactivity timers trigger release of resources
Bitrate
Capacity Request triggered from LFU feature
[kbps]
384
After RN2.0 CD3.0
128
64 Lightweight Flexible Upgrade feature active

Bitrate downgrade
-Bitrate upgrade if sufficient resources available –
Due to DyLo
32 Maximum Bitrate > Allocated bitrate > InitialandMinAllowedBitrate
RB setup
Capacity Request DyLO triggered time

Bit Rate Upgrade
For deliveries earlier than RN2.0 GCD3.0 the bit rate upgrade is possible only if the
currently allocated dedicated channel bit rate is lower or equal to the initial bit rate,
which is defined by initial and minimum allowed bit rate in uplink
(MinAllowedBitRateUL) and initial and minimum allowed bit rate in downlink
(MinAllowedBitRateDL).
In other words, if the currently allocated dedicated channel bit rate exceeds the initial
bit rate, then it is not possible to upgrade it.
From delivery RN2.0 GCD3.0 onwards it is possible to upgrade the NRT DCH bit rate
from any bit rate up to the maximum allowed bit rate.This upgrade is also based on
downlink and uplink traffic volume measurements. In this case the thresholds for the
upgrade are specified as follows:
. For bit rates 8 kbps and 16 kbps the threshold is a fixed value (512 bytes).
. For bit rates higher than 16 kbps TrafVolThresholdDLHigh and
TrafVolThresholdULHigh are used for downlink and uplink respectively.
When the upgrade of the NRT DCH bit rate is performed (from RN2.0 GCD3.0
onwards), packet scheduler uses the average downlink radio link power in the
estimation of the power increase instead of only the last received measurement
result which is used otherwise in power increase estimation. This is done to avoid a
ping-pong effect as the downlink radio link power varies a lot.

RRM Control Parameter
Crucial Parameters
Used Value Unit Description
Telecom Parameters
T315 180 s The RRC connection re-establishment timer for AM bearers (UE timer).
T302 4000 ms The CELL UPDATE/URA UPDATE retransmission timer(MS timer).
N302 3 times CELL UPDATE/URA UPDATE retransmission counter(MS counter).
The timer is used for inactivity detection of the signalling link in CELL_DCH state. The timer is set after inactivity
of the signalling link is detected and reset when any activity detected.
In expiry of the timer, a state transition from CELL_DCH to CELL_FACH state is initiated when also the
Signalling link inactivity timer 2s corresponding RB inactivity timer(s) expired.
The timer is set after a DCH for a signalling link is allocated in the RRC connection setup phase and a U-plane
RB has been setup in the MS. The timer stops when any DL/UL activity is detected (i.e. capacity request received
from the MS or MAC entity of
UL_DLcapacityReqWait the RNC) and a DCH for the U-plane RB(s) is allocated. If the MS is in CELL_FACH state, a state transition to
5s CELL_DCH is initiated.
Admission Control / Load Control Parameters
PrxNoise -101.9 dBm
PrxOffset 1 dB
PrxTarget 30 dB Due to severe UL interference.
PtxOffset 1 dB
PtxTarget 42 dBm in case of 20Watt (43dBm) WPA
Packet Scheduler Parameters
Initial & MinAllowedBitRateDL 64 kbps This parameter defines the minimum allowed bit rate in downlink that can be allocated by the PS.
Initial & MinAllowedBitRateUL 64 kbps This parameter defines the minimum allowed bit rate in uplink that can be allocated by the PS.
Max Bitrate UL 384 kbps This parameter defines the maximum uplink user bit rate allowed in a cell for an NRT PS domain RAB.
Max Bitrate DL 384 kbps This parameter defines the maximum downlink user bit rate allowed in a cell for an NRT PS domain RAB.
Inactivity timer UL 10 s Initiating Cell_FACH from Cell_DCH in case no UL activity during specified period
Inactivity timer DL 10 s Initiating Cell_FACH from Cell_DCH in case no DL activity during specified period
UL/DL Activation Timer 10 s Initiating Cell_PCH from Cell_FACH in case no activity during specified period
MS Activity Super Vision Timer 30 min Transfer to Idle from Cell_PCH
This parameter defines the threshold of data in the RLC buffer of RB in bytes which triggers downlink traffic
volume measurement report (capacity request) on MAC, when the UE is in a Cell_DCH state and bit rate higher
TrafVolThresholdDLHigh 4 KB than 16 kbps is allocated for the radio bearer.
The parameter defines the threshold of data in RLC buffer of RB in bytes. This threshold triggers the uplink traffic
volume measurement report when the UE is in a Cell_DCH state and bit rate higher than 16 kbps is allocated for
TrafVolThresholdULHigh 4 KB the radio bearer.
This parameter indicates the period of time, in seconds, during which it is forbidden to send any new traffic
volume measurement reports with the same measurement ID, even if the triggering condition is fulfilled again.
This parameter also indicates the period during which the UE blocks DTCH transmissions on the RACH after a
TrafVolPendingTimeUL 2000 ms measurement report is triggered.
T315
• The initial value for supervision timer RRC_ConnRe-estabTmr is defined as
follows:
• RRC_ConnRe-establTmr = T315 + (T302*N302)
• Constant N302 (Cell/URA Update Retransmission Count) and timers T302

(Cell/URA Update Retransmission Time) and T315 are management
parameters.
• In expiry of the RRC_ConnRe-estabTmr (no RRC:CELL UPDATE message is
received from the MS), the Iu release request with a cause value ‘Radio
Connection With UE Lost’ is sent to the PS-CN

T315

Uplink traffic volume measurements
Traffic volume measurement
(transport channel traffic volume)

4A
triggered, request for high bit rate
TrafVolThresholdULHigh (RNC parameter)
RLC buffer payload

UL data transmission
on DCH in CELL_DCH
state
4A
TrafVolThresholdULLow (Cell parameter)
UL data transmission
on RACH in Traffic volume measurement
CELL_FACH state not triggered

Downlink traffic volume measurements
Traffic volume measurement
(transport channel traffic volume)

triggered, request for high bit rate
TrafVolThresholdDLHigh (RNC parameter)
RLC buffer payload

DL data transmission
on DCH in CELL_DCH
state Traffic volume measurement
triggered, request for low bit rate
TrafVolThresholdDLLow (Cell parameter)

DL data transmission
on FACH in Traffic volume measurement
CELL_FACH state not triggered

UL Traffic Volume Based RRC State Transition
Reporting event:
4A: Transport Channel Traffic Volume becomes larger than an absolute threshold
UE in CELL_DCH: TrafVolThresholdULHigh (4096 Bytes)
Transport Channel
Traffic Volume UE in CELL_FACH: TrafVolThresholdULLow (128 Bytes)
(= UE Buffer Load)
4A 4A 4A
Measurement
report has
information about Thresholds
current
UE buffer load
time
UE
Measurement Report (Traffic Volume Event) RNC
TrafVolPendingTimeUL (2s)
Measurement Report (Traffic Volume Event)
MR e4a沒反應,等2Sec再送一次
• TrafVolThresholdULLow
• This parameter defines, in bytes, the threshold of data in the RLC buffer of RB that
triggers the uplink traffic volume measurement report, when the UE is in Cell_FACH
state.
• Otherwise, UE sends data on RACH.
• This parameter is sent to the UE using an RRC: MEASUREMENT CONTROL message.
• default value: 128 bytes; range: 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128 bytes,
256 bytes, 512 bytes, 1024 bytes (1 KB)
• TrafVolThresholdULHigh
• The parameter defines the threshold of data in RLC buffer of RB in bytes.
• The parameter is sent to the UE using the RRC: MEASUREMENT CONTROL message.
• default value: 4096 bytes; range: 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128 bytes,
256 bytes, 512 bytes, 1024 bytes (1 KB), 2048 bytes (2 KB), 3072 bytes (3 KB), 4096
bytes (4 KB)

• TrafVolPendingTimeUL
• This parameter indicates the period of time, in seconds, during which it is forbidden
to send any new traffic volume measurement reports with the same measurement
ID, even if the triggering condition is fulfilled again
• Parameter is sent to UE using an RRC: MEASUREMENT CONTROL message.
• default value: 2000 ms; range: 250 ms, 500 ms, 1000 ms, 2000 ms, 4000 ms,
8000 ms, 16000 ms
• Note: The same value should be set in all cells within a Node B
• TrafVolTimeToTriggerUL
• This parameter defines, in ms, the period of time between the timing of event
detection and the timing of sending a traffic volume measurement report.
• This parameter is sent to the UE using an RRC: MEASUREMENT CONTROL message.
• default value: 0 ms; range: 0 ms, 10 ms, 20 ms, 40 ms, 60 ms, 80 ms, 100 ms, 120
ms, 160 ms, 200 ms, 240 ms, 320 ms, 640 ms, 1280 ms, 2560 ms, 5000 ms

DL Traffic Volume Based RRC State Transition
• TrafVolThresholdDLLow
• This parameter defines, in bytes, the threshold of data in the RLC buffer of RB that
triggers the downlink traffic volume measurement report (capacity request) on MAC,
when UE is in Cell_FACH state. Otherwise, RNC sends data on FACH
• default value: 128 bytes; range: 0 bytes, 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128
bytes, 256 bytes, 512 bytes, 1024 bytes (1 KB)
• TrafVolThresholdDLHigh
• This parameter defines the threshold of data in the RLC buffer of RB in bytes which
triggers downlink traffic volume measurement report (capacity request) on MAC,
when UE is in a Cell_DCH state and the initial bit rate DCH is allocated for the radio
bearer
• default value: 4096 bytes; range: 0 bytes, 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128
bytes, 256 bytes, 512 bytes, 1024 bytes (1 KB), 2048 bytes (2 KB), 3072 bytes (3 KB),
4096 bytes (4 KB)

DL Traffic Volume Based RRC State Transition
• TrafVolTimeToTriggerDL
• This parameter defines, in ms, the period of time between the timing of event
detection and the timing of sending a downlink capacity request
• default value: 0 ms; range: 0 ms, 10 ms, 20 ms, 40 ms, 60 ms, 80 ms, 100 ms, 120
ms, 160 ms, 200 ms, 240 ms, 320 ms, 640 ms, 1280 ms, 2560 ms, 5000 ms
• TrafVolPendingTimeDL
• This parameter indicates the period of time, in ms, during which it is forbidden to
send any new downlink capacity requests with the same RB id, even if the triggering
condition is fulfilled again
• default value: 2000 ms; range: 250 ms, 500 ms, 1000 ms, 2000 ms, 4000 ms, 8000
ms, 16000 ms

PS Call Analysis

PS Call Analysis Method
• Once the crucial parameters are set properly, PS throughput will be
depending more on RF condition (Ec/No).
• Items to be analyzed for PS call
• PS Call Events
• Attach / PDP_Context_Activation Failure cases
• PS Call Drop cases
• LAU/RAU can be happened during PS call.
– Creating Iu_CS for LAU, after LAU signaling connection release
(Iu_CS).
– For RAU during PS call requires SRNS relocation.
• Poor Throughput area

• RF Performance (Ec/No, Non-dominance issue)
• UL Interference (SIB7)
• DyLO (DL link power issue)

Analysis Screen Layout
Ec/No Active Set
Nemo Event (PS)
Ec/No Monitored Set
Carrier RSSI
Scanner CPICH Ec/No
Scanner Carrier RSSI
DL BLER
UL Interference
TX Power
Application DL Throughput
Successful Call Case
5MB FTP DL
RB_Setup:
UL:0kbps
DL:0kbps
MR(e4a)
Traffic Volume Measurement.
Possible UL: FTP log in request
1st RB_Reconfig:
UL:64kbps (sf16)
DL:64kbps (sf32)
2nd RB_Reconfig:
UL:64kbps (sf16)
DL:384kbps (sf8)

Case1
PS Call Drop 1
PS Call (RRC) Drop.
Before RRC drop, high

DL BLER observed
under SC306 (CID
28044), single active
set situation with fair
Ec/No.
Possible Site related

issue.
SIB7
UL_Int: -103
Doesn’t seem to be UL
interference causing
drop call situation

Case1 PS Call Drop 1-1
-RRC_Re-establishment after RRC Drop (based on T315 setting)
cell update is under Cell_FACH,

just like cell reselection under idle
mode)
cellUpdateCause:
radiolink Failure
cellUpdateConfirm
r3
cellUpdateConfirm-r3
rrc-TransactionIdentifier :2
new-C-RNTI
Bin : 00 03 (= 3)
rrc-StateIndicator : cell-FACH
failureCause :
invalidConfiguration
Successful RB_Reconfig to
UL:64kbps (sf16)
DL:384kbps (sf8)
New Neighbor List and SHO

criteria

Case1

Case2
Down Grade due to DyLO Case
PS Bitrate downgraded
(RB_Reconfig, DL sf 16,
128kbps).
This is due to a radio link pwr

reached to a threshold level to
trigger DyLO.
Based on DyLO procedure, RNC
is downgrading DL bitrate to
next lower level.
PS Bitrate back to DL sf8 (384kbps).
The situation is that after lowering

down bit rate (radio link power),
RLC buffer exceeds
“TrafVolThresholdDLHigh” and
DL requested for upgrade.
Throughput After checking resource status of
target cells, RNC decided to upgrade
to 384bkps DL based on Packet
Scheduling
This is a normal case.
Problem comes when it does not

upgrade back to sf8 after DyLO.
Then it is possible poor RF
53 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential environment problem.
Case3
PS Call Drop 2
1st RB_Reconfig
: Initial and Min bit rate:64/64
2nd RB_Reconfig
: UL:64kbps / DL 384kbps
Multiple Measurement Report with

No ASU.
Cause.
During RB set up or
RB_Reconfiguration, parallel
procedures are not allowed in RNC,
meaning that RNC will first perform
RB setup, or RB Reconfig then SHO.
However, by the time RB Reconfig

completed, UE Ec/No got already
poorer, loosing synch with BTS
which caused drop call situation.
Ec/No degradation
caused drop call.

Case3
PS Call Drop 2-2
RRC_Re-establishment
Procedure after PS call drop.
(Depending on T315 para
setting).

Case3
PS Call Drop 2-3
Cell_Update caused by
Cell_Reselection

Case3
PS Call Drop 2-4
RB_Reconfig
DL:64kbps (sf32)
RB_Reconfig
DL:384kbps (sf8)

Case4
LAU/RAU during PS Call
ASU;
rl_removal
SRNS relocation;
New SRNTI allocated
from new RNC
LAU/RAU
After Location Area
Update, releasing
signaling link for Iu_CS,
PS since it only requires
Iu_PS for PS call.
Throughput
during
LAU/RAU

Case5 Going to Cell FACH from sf8 while downloading
- due to High UL interference peak
Under good rf condition it

went to Cell_FACH while
downloading with sf8.
Probably due to UL int?

since it is having
UL_nrt_load_modify reqeust
to 0bps ??
RN23 Prx_target: 4dB at that
moment.
More test required after
changing prx_target to
30dB.
This case was before

changing Prx_Target to
30dB..

Case5
Sf8 -> Cell FACH (due to UL interference)
sf8
Cell_FACH; CID: 32325
RN23
July 22, 2004
Prx_Target: 30dB
Prx_offset: 1dB
Prx_nosie: -101.9dBm
After changing
Prx_Target to 30dB, no
more case found
except one very
obvious UL
interference case;
having higher than our
plan..

Case6
Low Throughput due to Poor Ec/No
One example of
having low
throughput due to
poor Ec/NO (RF
issue).
Sf128
sf16, Bit rate 128KPS
Due to increasing
in DL link power,
RNC did not
upgrade PS bit
rate. (DyLO issue
caused by poor RF
Poor Ec/No condition.)
Solution;
Try to create
dominant server.
Low In this case, Inter
Throughput SGSN handover
was introduced.
Try to reduce RAU
pingpong issue
which will cause
low throughput
also.

Nemo L3 PS Intro v1 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nemo L3 PS Intro v1 PDF

Uploaded by

Copyright:

Available Formats

PS Data Call Analysis Intro

1 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

2 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

3 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

3G-SGSN only: RAB

GPRS Detach Implicit GPRS Detach

(adopted from TS 23.060 V3.13.0)

Activate PDP Context

Deactivate PDP Context

All "1", RAC is not supposed to

Service Area SAI = MCC MNC LAC SAC

6 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

7 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

Attach & Authentication Procedure

PDP Context Activation & Radio Bearer

Radio Bearer Reconfiguration

PDP Context Deactivation Procedure

Detach & Radio Bearer Release Procedure

RRC Connection Release

8 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

1st Radio Bearer

2nd Radio Bearer

9 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

10 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RRC:RRC CONNECTION SETUP

PDP Context is active

NBAP:RL RECONFIG URATIO N READY

RANAP: DIRECT TRANSFER

RANAP:RAB ASSIGNM ENT REQUEST

RRC: RADIO BEARER SETUP RRC: DT(Detach request)

RANAP: DT(Detach request)

NBAP:RL DELETION REQ UEST

NBAP:RADIO LINK RECONFIGURATION PREPARE AAL2SIG : RLC

RRC: RRC CO NNECTION RELEASE RANAP: Iu Release Com plete

NBAP:RADIO LINK RECONFIGURATION COM M IT

RRC: TRANSPORT CHANNEL RECONFIGURATION

RRC: TRANSPORT CHANNEL RECONFIGURATION COM PLETE

Uplink and downlink data transfer

11 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

12 © NOKIA PS Intro.PPT / Aug 2006 / MHL

13 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

PtxTotal (variable) PrxTotal

15 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

16 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

PMM & CM (e.g. PDP Context Activation)

Traffic Volume RAB Assignment Request

SignaillingLink The timer is used for inactivity detection of the 0 ... 20 s, 2s 2s

18 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

PDU Transport on the DCH/DPCH

Radio Link Deletion

UL/DL activation timer

20 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

CELL_ Inactivity detected Start

22 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

Radio Link Setup

Radio Bearer Reconfiguration

23 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

Radio Link Setup

Radio Bearer Reconfiguration

24 © NOKIA PS Intro.PPT / Aug 2006 / MHL Company Confidential

After ~20s WAP