You are on page 1of 5

B country M project HSUPA 5.

74Mbps
per
user
feature
abnormal
low
performance analysis report
Author
Region
Date
Approver
Case
Name
Proble
m
Descrip
tion

Alarm
Informa
tion
Proble
m
Ananlys
is

a00190510
WEU
2014/02/27

ID
Product
Version

00190510
WCDMA RNC
BSC6900 V900R014ENGC00SPH532

B country M project HSUPA 5.74Mbps per user feature abnormal


low performance analysis report
In B country M project, We activated the feature HSUPA 5.74Mbps
per user, but when we analyse the DT logs of UMTS FTP upload, we
notice that some points the UL throughput are blocked at 2.6Mbps
and can not reach a higher level.

But when we analysed the details of DT logs and trace logs, we


noticed that this blocking period was taking 2ms instead of 10ms,
and from the feature we think it should goes to higher throughput
like around 4Mbps.
So here its abnormal to have 2ms blocked at 2.6Mbps when we
have SRBoE.
No related alarms

We noticed a lot of 2ms have upload throughput limited bellow


2.8Mbps like one case below shows.

From the DT statistics we noticed a lot of 2ms allocated 2SF2


instead of 2SF2+2SF4.

Upon the 2SF2 2ms issue, they were not E-DCH, in fact the E-DCH
is TRB type instead of SRB type. Here we checked Log
of
Probe_20131129185628.gen as below and confirmed this 2SF2
2ms is 2ms SRBoD instead of SRBoE:
1. When checking RB set up message, first find RB Information
Reconfig List and check the UL Transport Channel Type for
RB in the list whose ID=2, then you can notice its 2ms
SRBoD with 2SF2 instead E-DCH with 2SF2+2SF4.
18:57:06.070 RB setup

2. When checking RB Re-CFG, if notice it contains UL DPCH


information, then it is SRBoD. When re-CFG to SRBoE there
is no UL DPCH information which could only find in SRBoD.
18:57:21.549 RB Re-CFG (first time Re-CFG after 18:57:06.070
RB setup)

And also we noticed that the RLC throughput during this session is
limited below 2.6Mbps.

Root
Cause
summar
y
Optimiz
ation
Plan
Results

These 2ms with low max throughput 2.6Mbps are 2ms with 2SF2,
they are with SRB over DCH, so they can not be higher than
2.88Mbps.
If we want to these 2ms have more gain form feature 5.74Mbps per
user, we need to bring these 2ms 2SF2 to 2ms 2SF2+2SF4 which
means SRB need to HO to E-DCH.
We enabled SRBoE retry(retry per 5s) to reduce the 2ms DCH and
increase 2ms E-DCH;
From the result we noticed this throughput limit disappeared and

of
Optimiz
ation

we
have
a
very
good
throughput
average/median/bandwidth allocated:

Attach
ment
Referen
ce

None
Feature HSUPA 5.74Mbps per user.

both

from

You might also like