Nemo L3 PS Intro v1

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

PS Data Call Analysis Intro
Nokia RNWP
2 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.
PMM-DETACHED
PMM-CONNECTED PMM-IDLE
GPRS Detach
GPRS Attach Reject
RAU Reject
GPRS Attach
Implicit GPRS Detach
(SGSN: MS Reachable
Timer expires)
PS Signalling Connection
Release
PS Signalling Connection
Establishment
3G-SGSN only:
S-RNC Relocation
(adopted from TS 23.060 V3.13.0)
State of Attached
PDP Context
RAB
INACTIVE ACTIVE
(adopted from TS 23.060 V3.13.0)
Activate PDP Context
Deactivate PDP Context
or
MM context change to PMM-DETACHED
UE
3G-SGSN GGSN
Packet Data Protocol (PDP) States
Location Area
Routing Area
Service Area
LA1
LA2
MCC MNC LAC LAI =
MCC MNC LAC RAI = RAC
LA2
RA1
RA2
RA3
RA4
MCC MNC LAC SAI = SAC
LA1
LA2 SA1
SA2
SA3
SA4
SA5
SA7
SA8
SA6
Location Area Concepts
10701,11701, The only rule is
LAC must smaller than MSC.
For the time being, LAC
update only happens during
idle mode.
All "1", RAC is not supposed to
be equivalent to RNC, The only
rule is RAC must be smaller
than LAC.
RAC update can be seen during
connected mode.
Same with cell ID, It's
not functioning for the
time being.
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
RB 0/0 kbps
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
Traffic Volume
Measurement Report
(e4a).
UL data: FTP log in request
This RAB Reconfig is not requested by UE
(No MR E4a found prior to this RAB_Reconfig.
spreadingFactorAndPilot : sfd32 --> 64K
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
PS DATA CALL
MS BTS PS_CN RNC
RRC:RRC CONNECTION REQUEST
NBAP:RADIO LINK SETUP REQUEST
NBAP:RADIO LINK SETUP RESPONSE
RRC:RRC CONNECTION SETUP
NBAP:SYNCHRONIZATION INDICATION
RRC:CONNECTION SETUP COMPLETE
RRC:INITIAL DIRECT TRANSFER (Attach Request)
RANAP:INITIAL UE MESSAGE
(Attach Request)
RANAP:RAB ASSIGNMENT REQUEST
Uplink and downlink data transfer
L1 synchronisation
AAL2SIG: ERQ
AAL2SIG: ECF
RANAP: DIRECT TRANSFER
(Attach Accept)
RRC: DOWNLINK DIRECT TRANSFER (Attach Accept)
RRC: UPLINK DIRECT TRANSFER (SM:Activate PDP Context request)
(SM: Activate PDP Context request)
(SM: Activate PDP Context accept)
RRC: DOWNLINK DIRECT TRANSFER (SM: Activate PDP Context Accept)
NBAP:RADIO LINK RECONFIGURATION PREPARE
NBAP:RADIO LINK RECONFIGURATION READY
AAL2SIG: ERQ
AAL2SIG: ECF
NBAP:RADIO LINK RECONFIGURATION COMMIT
RRC: RADIO BEARER SETUP
RRC: RADIO BEARER SETUP COMPLETE
RANAP:RAB ASSIGNMENT RESPONSE
RRC: TRANSPORT CHANNEL RECONFIGURATION
RRC: MEASUREMENT REPORT
RRC: TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RRC: DOWNLINK DIRECT TRANSFER (Attach Complete)
(Attach Complete)
BTS CS_CN RNC
PDP Context is active
NBAP:RL DELETION REQUEST
AAL2SIG: RLC
AAL2SIG: REL
MS
RRC: DT (Deactivate PDP context request)
RANAP: DT (Deactivate PDP context request)
RANAP: DT (Deactivate PDP context accept)
(Release)
RRC: DT (Deactivate PDP context accept)
RRC: RADIO BEARER RELEASE
RANAP: RAB ASSIGNMENT REQUEST
RRC:RADIO BEARER RELEASE COMPLETE
NBAP:RL DELETION RESPONSE
AAL2SIG: REL
AAL2SIG: RLC
NBAP:RL RECONFIGURATION PREPARE
NBAP:RL RECONFIGURATION READY
RANAP: RAB ASSIGNMENT RESPONSE
NBAP:RL RECONFIGURATION COMMIT
RRC: DT(Detach request)
RANAP: DT(Detach request)
RANAP: DT(Detach accept)
RRC: DT(Detach accept)
RANAP: Iu Release Command
RANAP: Iu Release Complete
RRC: RRC CONNECTION RELEASE
RRC: RRC CONNECTION RELEASE COMPLETE
Multi RAB (Simultaneous AMR+PS)
AMR
PS
PS
Disconnect
AMR
Disconnect
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
Power
/ Load
time
non-controllable load
i.e. RT Traffic
controllable load
i.e. non RT Traffic
PtxTotal (variable) PrxTotal
PtxNrt PrxNrt
PtxTarget PrxTarget
PtxOffset PrxOffset
PtxTargetBTS PrxTargetBTS
overload
Desired
Prx/Ptx
Values
PtxRt PrxRt
PS Data Call State Transition
RRC Modes and Packet Scheduling
URA_PCH
CELL_DCH
CELL_PCH
Establish RRC
Connection
UTRA RRC Connected Mode
Idle Mode
(UE camps on UTRAN cell)
UL/DL Activation timer
(10s)
Cell_Update, UL_Tx
DCH_Inactivity Timer
(10s)
Traffic_volume
CELL_FACH
Release RRC
Connection
1. MS Activity
Supervision
timer (30min):
when still
having
RB_connected.
or
2. PS CN Inactive
signaling time
supervision: 30s
:when RB is
disconnected.(re
moved in
RAN04)
If this is not enact, then the Cell_PCH & URA_PCH is not allowed.
1. PS Connection Establishment
RNC UE
SGSN
RRC Connection Establishment (SRB)
PMM & CM (e.g. PDP Context Activation)
RAB Assignment Request
Traffic Volume
Parameters
determination
Measurement Control [Traffic Volume Measurements]
CELL_
DCH
Start
UL_DLcapacityReqWait
(RB_InactivityTimer)
SignallingLinkInactivityTimer
expiry
Capacity Request?
DCH for NRT RB(s) allocation
no
yes
yes
SignallingLinkInactivityTime
expiry
CELL_
FACH
Signaling Radio Bearer
1-a PS Connection Establishment
Parameter
Name
Description Range Default Current
Setting
Remark
UL_DLcapacity
ReqWait
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
the MS. The timer stops when any DL/UL activity is detected (i.e.
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.
0 ... 20 s,
step 0.5 s
5s 10s
2s
SignaillingLink
Inactivity
Timer
The timer is used for inactivity detection of the
signalling link in CELL_DCH state. The timer is
detected and reset when any activity detected.
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.
0 ... 20 s,
step 0.5 s
2s
2. Transition from CELL_DCH to CELL_FACH
RNC
UE
CELL_
DCH
Node B
PDU Transport on the DCH/DPCH
All data is sent and
RLC-U buffer is empty
Inactivity detected
Start
InactivityTimerUplinkDCH
InactivityTimerDownlinkDCH
Radio Bearer Reconfiguration Complete
Expiry
CELL_
FACH
L2 configuration
Radio Link Deletion
Start
MAC: Inactivity detected
UL/DL activation timer
2-a. Transition from CELL_DCH to CELL_FACH
Parameter
Name
Setting
Remark
Inactivity
Timer for
UL(DL) DCH
The time indicating how long the radio and
transmission resources are reserved after silence
detection on downlink/uplink DCH before release
procedures.
0~20s,
step:1s
255 s
(infinity)
:Parameter value
255 (infinity)
means that NRT
DCH inactivity
supervision is not
used.
8 kbps: 5 s
16 kbps: 5 s
32 kbps: 5 s
64 kbps: 3 s
128 kbps: 2 s
256 kbps: 2 s
320 kbps: 2 s
384 kbps: 2 s
20S In order to avoid
too frequent state
transition between
Cell_DCH and
Cell_FACH. (20s)
3. Transition from CELL_FACH to Cell_PCH/URA_PCH
Start
MAC: Inactivity detected
UL/DL activation timer (10s)
UE
CELL_
FACH
CELL_
FACH
Cell Update
Cell Update
Cell Update Confirm
URA_
PCH
MaxCellReselections
CellReselectionObservingTime
and
MaxPeriodicalCellUpdates
Start
Expiry
Expiry
RNC
analog in
CELL_PCH
URA Update
URA Update
URA Update Confirm
Inactivity detected
Transition to URA_PCH
MSActivitySupervision (30min)
URA_
PCH
RRC-
IDLE
CELL_
PCH
3-a. Transition from CELL_FACH to Cell_PCH
Parameter
Name
Setting
Remark
UL/DL
activation timer
This timer is used on MAC -c to detect idle periods
on data transmission (NRT RBs and SRBs) for the
UE, which is in Cell_FACH state.
Based on this timer the MAC -c shall give the
No_Data indication to the RRC, which further can
change the state of the RRC from Cell_FACH
state to the Cell_PCH state (or URA_PCH state).
50 ... 10000
ms, step 50
ms
2000 ms 10000ms
MS activity
supervision
timer
MSActivitySupervision timer is used in RRC states
CELL_PCH and URA_PCH for supervising the
inactivity of NRT RAB(s). Timer is started when a
state transition to either of these states is
executed.
In expiry of the MSActivitySupervision timer when
the first 'inactive state indication(I.e. cell/URA
update, which does not cause the (re)initiation o
fthe signalling or data flow) is received from the
MS, the RNC asks SGSN to release the Iu
connection.
0 ... 1440
min, step 1
min
30 min 30 min Note: If the
parameter value is
set to zero:
- state transition to
Cell_PCH/URA_PC
H is not allowed
when inactivity is
detected in
Cell_FACH state,
the MS will be
switched to the Idle
Mode
In order to avoid
too frequent state
transition between
Cell_FACH and
Cell_PCH. (10s)
4. Transition from CELL_FACH to CELL_DCH
RNC
UE
CELL_
FACH
Node B
UL & DL packet scheduling
Measurement Report (Traffic Volume Event)
CELL_
DCH
Radio Link Setup
UE initiated
It will assign 384K directly if there is data throughput..
4-1. Transition from CELL_FACH to CELL_DCH
RNC
UE
CELL_
FACH
Node B
DL capacity need is
detected by MAC
CELL_
DCH
Radio Link Setup
RNC initiated
Channel type selection
-> DCH
UL & DL
packet scheduling
Cell_PCH
WAP (Always on mode)
WAP
Cell DCH
-DCH inactivity timer:
20s
Cell FACH
- UL/DL activation timer:
10s
Cell PCH
-MS activity supervision
timer: 30min
(hardcoded).
* RRC_Release was after
30 min.
RRC_Released (PMM_Idle)
04J un09 Always_on4.dt1
Cell_DCH
Cell_FACH
Cell_FACH
Cell_PCH
Idle
After ~20s
After ~10s
Cell_FACH
After
~30min
Inactivity timer for DCH (UL/DL): 20 sec
Inactivty timer in NRT RB setup: 10s
Signalling link inactivity timer: 2s
UL/DL activation timer: 10s
MS activity supervision timer: 30 min
Now it's 10S
Dynamic Link Optimization in PS
Triggering of Dynamic Link Optimisation
time
Ptx, RL
distance
Ptx, ave
Triggering of DyLO
Ptx, max
Offset
Ptx, ave is averaged radio
link power, measured and
reported to RNC by BTS
Ptx, max is determined by
admission control
The value of the Offset is
fixed, 2 dB
Dynamic link optimisation
is triggered if
Ptx, ave > Ptx, max - Offset
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)
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)
Nokia b QiP Sex-b N P , Ss64JKBps.
Example DLO : PtxDLabsMax 50 dBm, PtxTotalMax 43dBm
D
L

p
w
r
(
d
B
m
)
PtxTotalMax 43dBm
PtxPrimaryCPICH 33dBm
PtxPrimaryCPICH CPICHtoRefRABoffset = 31 dBm
PtxDLabsMax 50 dBm
Calculated max RL pwr
Calculated max RL pwr - DLOptimisationPwrOffset
This is where DLO triggers. (If PtxDLabsMax is set high)
384kbps:38dBm
128kbps:37.387dBm
Default hidden
value is 2dB
ref tx
P
,
max , tx
P
Ptx, threshold
384kbps:40dBm
128kbps:39.387dBm
PS NRT & MultiRAB:
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
2 s
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)
64 -> 32 (1 SF step)
32 -> 16 (1 SF step)
16 -> 8 (1 SF step)
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
128K-->384K
64K -->128K
??-->64K
Bitrate Upgrade Possibilities in Nokia RAN
SF32(64k) SF8(384k) SF16(128k) CELL-FACH SF32(64k) SF8(384k)

Example: Max Bitrate 384kbps, Initial Bitrate 64kbps
Inactivity timers trigger release of resources
Bitrate
[kbps]
time
RB setup
32
64
128
384
CapacityRequest DyLO triggered
Lightweight Flexible Upgrade feature active
-Bitrate upgrade if sufficient resources available
Maximum Bitrate > Allocated bitrate > InitialandMinAllowedBitrate
CapacityRequest triggered fromLFU feature
After RN2.0 CD3.0
Bitrate downgrade
Due to DyLo
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.
Crucial Parameters
RRM Control Parameter 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).
Signalling link inactivity timer 2 s
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
corresponding RB inactivity timer(s) expired.
5 s
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
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.
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
TrafVolThresholdDLHigh 4 KB
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
than 16 kbps is allocated for the radio bearer.
TrafVolThresholdULHigh 4 KB
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
the radio bearer.
TrafVolPendingTimeUL 2000 ms
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
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
not triggered
R
L
C

b
u
f
f
e
r

p
a
y
l
o
a
d
R
L
C

b
u
f
f
e
r

p
a
y
l
o
a
d
(
t
r
a
n
s
p
o
r
t

c
h
a
n
n
e
l

t
r
a
f
f
i
c

v
o
l
u
m
e
)
(
t
r
a
n
s
p
o
r
t

c
h
a
n
n
e
l

t
r
a
f
f
i
c

v
o
l
u
m
e
)
UL data transmission
on RACH in
CELL_FACH state
UL data transmission
on DCH in CELL_DCH
state
TrafVolThresholdULLow (Cell parameter)
4A
TrafVolThresholdULHigh (RNC parameter)
triggered, request for high bit rate
4A
Downlink traffic volume measurements
R
L
C

b
u
f
f
e
r

p
a
y
l
o
a
d
R
L
C

b
u
f
f
e
r

p
a
y
l
o
a
d
(
t
r
a
n
s
p
o
r
t

c
h
a
n
n
e
l

t
r
a
f
f
i
c

v
o
l
u
m
e
)
(
t
r
a
n
s
p
o
r
t

c
h
a
n
n
e
l

t
r
a
f
f
i
c

v
o
l
u
m
e
)
TrafVolThresholdDLLow (Cell parameter)
TrafVolThresholdDLHigh (RNC parameter)
DL data transmission
on FACH in
CELL_FACH state
DL data transmission
on DCH in CELL_DCH
state
not triggered
triggered, request for low bit rate
triggered, request for high bit rate
UL Traffic Volume Based RRC State Transition
Reporting event:
4A: Transport Channel Traffic Volume becomes larger than an absolute threshold
time
Transport Channel
Traffic Volume
(= UE Buffer Load)
Thresholds
4A
4A
4A
RNC
UE
UE in CELL_FACH: TrafVolThresholdULLow (128 Bytes)
UE in CELL_DCH: TrafVolThresholdULHigh (4096 Bytes)
TrafVolPendingTimeUL (2s)
4A
4A
Measurement
report has
information about
current
UE buffer load
MR e4alSa ,{I 2SecQ N k!
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
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
DL Traffic Volume Based RRC State Transition
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
Ec/No Monitored Set
Carrier RSSI
DL BLER
UL Interference
TX Power
Application DL Throughput
Scanner CPICH Ec/No
Scanner Carrier RSSI
Nemo Event (PS)
Successful Call Case
5MB FTP DL
2nd RB_Reconfig:
UL:64kbps (sf16)
DL:384kbps (sf8)
1st RB_Reconfig:
UL:64kbps (sf16)
DL:64kbps (sf32)
RB_Setup:
UL:0kbps
DL:0kbps
MR(e4a)
Traffic Volume Measurement.
Possible UL: FTP log in request
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
Doesnt 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)
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
cell update is under Cell_FACH,
just like cell reselection under idle
mode)
Case1
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
requested for upgrade.
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
environment problem.
DL
Throughput
Case2
PS Call Drop 2
1st RB_Reconfig
: Initial and Min bit rate:64/64
2nd RB_Reconfig
: UL:64kbps / DL 384kbps
Ec/No degradation
caused drop call.
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.
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)
Case3
LAU/RAU during PS Call
ASU;
rl_removal
SRNS relocation;
New SRNTI allocated
from new RNC
After Location Area
Update, releasing
signaling link for Iu_CS,
since it only requires
Iu_PS for PS call.
LAU/RAU
PS
Throughput
during
LAU/RAU
Case4
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.
Case5
This case was before
changing Prx_Target to
30dB..
Sf8 -> Cell FACH (due to UL interference)
Cell_FACH; CID: 32325
sf8
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..
Case5
Low Throughput due to Poor Ec/No
Low
Throughput
Poor Ec/No
Case6
One example of
having low
throughput due to
poor Ec/NO (RF
issue).
Sf128
Due to increasing
in DL link power,
RNC did not
upgrade PS bit
rate. (DyLO issue
caused by poor RF
condition.)
Solution;
Try to create
dominant server.
In this case, Inter
SGSN handover
was introduced.
Try to reduce RAU
pingpong issue
which will cause
low throughput
also.
sf16, Bit rate 128KPS

Nemo L3 PS Intro v1

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Nemo L3 PS Intro v1

Încărcat de

Drepturi de autor:

Formate disponibile

1 NOKIA PS Intro.

PPT / Aug 2006 / MHL Company Confidential

S-ar putea să vă placă și