1.

Hi anh Tuan, Hng,

TMC just have a drive test around Da Nang. There are many places that HS switch to R99 with very low
throughput. Mainly are at project new sites.

Request:
VNPT-T redrive test around these area (as attached file) immediately. Service: Data (do not lock
HS). Nokia Propose other request for test case (if any).
Nokia check parameters.
Nokia have Report before 31/12/2016. Today got first report for 1 District (drive test result).

2. Hi Mr. SK, Mr. Tuan,

It seems that this is the broadly issue. About more than 50% new sites in Binh Dinh province encounter
the same problem in channel type selection.
I leads to low throughput (<384kbps) in both DL and UL because of DCH channel assignment instead of
HS-DSCH.

What is Nokias mechanism in HSPA channel type selection and switching and how to control it?
Could you please send us some related docs so that we can understand it deeper?
3. Hi,

There are a number of reasons for the transitions between DCH and HS-DSCH. 2 things we need
to consider: why transition from HS-DSCH/E-DCH to DCH happened, and why DCH to HS-
DSCH/E-DCH didnt happen.

The following situations may trigger DCH to HS-DSCH/E-DCH reconfiguration:

1/ The first cell which supports the used RAB combinations with HSDPA is added to the active
set;
2/ Inter-frequency and inter-system handover measurements did not cause the respective
handovers;
3/ RAB combination of the UE changes so that it supports use of HS-DSCH;
4/ Initial HS-DSCH reservation did not succeed for temporary reasons (no HSDPA capacity in
the RNC);
5/ CS voice/PS RAB establishment;
6/ Active set update, so that full HSPA configuration is possible (F-DPCH conditions);
7/ RAB combination change to combination where CS voice over HSPA is supported.

Before the actual DCH to HS-DSCH transition is started, all the following preconditions must be
fulfilled:
1/ At least one interactive/background or streaming RB which is mapped to DCH exists, having a
bit rate different from 0/0kbit/s or CS voice RAB mapped to DCH;
2/ The UE and at least one cell in the active set are HSDPA capable;
3/ UE has a RAB combination that is supported with HSDPA;
4/ Selected serving cell is good enough compared to the other cells in the active set (CPICH
Ec/No);
5/ No guard timers are running, preventing the selection of the HS-DSCH;
6/ If HSDPAMobility is disabled, the active set size must be 1;
7/ RAB attribute Maximum bit rate does not prevent use of HSDPA (by preventing reservation
of needed UL bit rate);
8/ No active inter-frequency or inter-system handover causes exist.

The following situations may cause HS-DSCH to DCH reconfiguration:

1/ Serving cell cannot be found (quality reasons, needed feature not supported);
2/ A new RAB combination is not supported with HSDPA or HSPA (but supported with DCH);
3/ Full HSPA configuration cannot be kept anymore, for example:
Unsuccessful HSUPA TTI switch from 2ms to 10ms.
For quality reasons (F-DPCH).
Initiation of compressed mode.
When a cell not supporting CS voice on HSPA or F-DPCH is added to active set.
When a cell under the DRNC is added to an active set.
A new RAB combination is not supported with full HSPA configuration (but
supported with DCH).
4/ A UE with PS RABs mapped to HS-DSCH moves to another cell although HSDPA mobility
is disabled.
Under normal conditions, HS-DSCH and E-DCH should only be released due to low throughput
or low utilization. Below are some parameters related to releases of HS-DSCH:
1/ Parameters for detecting low throughput on HS-DSCH
MACdflowthroughputRelThr (default 0kbps)
MACdflowutilRelThr (default 256bps)
2/ Parameters for release timing of the MAC-d flow
MACdflowthroughputTimetoTrigger (default 5s)
MACdflowutilTimetoTrigger (default 0s)
3/ Parameters that prevent a new HS-DSCH setup
HSDSCHGuardTimerLowThroughput (default 30s)
4/ Parameters for detecting low throughput on E-DCH
EDCHMACdFlowThroughputAveWin (default 3s)
EDCHMACdFlowThroughputRelThr (default 256bps)
EDCHMACdFlowThroughputTimetoTrigger (default 0s)
5/ Parameter that prevents a new E-DCH setup
EDCHCTSwitchGuardTimer (default 2s)

The following 2 plots show UE throughput, but didnt show channel types. Could it be possible
that the problem was HS-DSCH allocated with low throughput instead of HS-DSCH to DCH
transitions?

@ Tuan, please help to fish the following counters at the BTS we are interested in:

PS_SWI_HS_E_TO_D_D_INT
PS_SWI_HS_D_TO_D_D_INT

Br,
Say Kiat
4.
Hi Tuan,

If DC-HSDPA is involved, please verify the following settings:

FRLCEnabled=Enable
HSDPA14MbpsPerUser=Enable
HSDPA64QAMallowed=Enable
HSDPAEnabled=Enable
HSUPAEnabled=Enable
HSPDSCHCodeSet=54560d
HSPAQoSEnabled set to the same value in both cells of the DC HSDPA cell pair
Tcell set to the same value in both cells of the DC HSDPA cell pair
SectorID set to the same value in both cells of the DC HSDPA cell pair
DCellHSDPAFmcsId=
DCellHSDPAEnabled=Enable
You can check the HSPA mobility performance (serving cell change) with the following KPIs in
RSRAN001:
RNC_927a HSDPA SCC Att
RNC_733b HSDPA SCC SR
RNC_929a HSUPA SCC att
RNC_918b HSUPA SCC SR

Br,
Say Kiat
5. Hi Tuan,

Please check the current setting of PRFILE RN40_MAINT_014. Below are the functionalities of
this PRFILE:

1/ SIR error to trigger CTS

During poor UL SIR error conditions HSDPA calls which have only one cell in active set are
switched from HSDPA to DCH. Also HSDPA calls in soft handover might be switched to DCH
if other active set cells are not suitable HSDPA serving cell candidates. Problem can be detected
by HSDPA retainability decreasing and channel type switches due to UL SIR error might occur
frequently. As a correction, new PRFILE controlled change prevents channel type switch to
DCH due UL SIR error measurement without preventing the possibility to use UL SIR error
measurement to trigger HSDPA serving cell change.

2/ HSPA reconfiguration to DCH after SCC

HSDPA retainability is decreased due to channel type switches from HSDPA/HSPA to DCH.
This occurs when serving cell is deleted from the active set and suitable serving cell candidate is
not found due to low UL SIR error measurement in the target cell. With this workaround, if the
serving cell change (SCC) is triggered by such an event or measurement report, where the
serving cell is to be deleted from the active set, RNC will not use UL SIR error measurement of
the target cell as criterion.

Serving cell can be deleted from the active set due to following reasons:
Measurement Event 1B reported by the UE
Measurement Event 1C reported by the UE
RL failure (loss of UL synchronisation) reported by the BTS
RL removal due to Rx-Tx time difference reported by the UE

Allowed
value (s) Effect
0000H All workarounds are disabled (default value)
0001H Enables SIR error to trigger CTS workaround
0003H Enables SIR error to trigger CTS workaround and HSPA reconfiguration to DCH after SCC
Br,
Say Kiat

7. Hi Mr. SK,
HSPA channel type selection and switching is an interesting topic which involves in end-user throughput.
Therefore, in my point of view, controlling this part is very needed.
Right now, I just understand how to manipulate the release of HS-DSCH and E-DCH under normal
condition to improve the performance of radio resource utilization, other parts that you mentioned is still
a mystic box.
Could you please share me some detail docs about this topic?
Thanks,
Thanh Pham.
TMC, Mobifone Corporation.
M: +84905674369.
8. Hi,

You can refer to the document for details. This is part of customers documentation and
Mobifone can request a copy from Nokia counterpart.

Br,
Say Kiat

9. Dear cc anh,
Em gi li mt s thng tin v channel switching v R99 trc y em c lm.
By gi yu cu Nokia bt bn tin trn RNC l bit nguyn nhn chuyn v R99 c phi trigger
do UL SirError hay khng?
Tuy nhin, nu ch tp trung vo cc trm mi ln, th em ngh nguyn nhn do vic comission
c vn .

Theo ti liu ca Vendor Nokia, hin tng chuyn t HSDPA v R99 khi thc hin download
data c th xy ra do mt trong cc nguyn nhn sau:
Last HSDPA capable cell dropped
Event 1F (too low Ec/I0 or RSCP for all active cells)
Event 6A (too high UE Tx power)
Too high DL RL power
UL quality deterioration
Trng hp gp phi: UL quality deterioration
- Khi cht lng tn hiu ng ln (UL SIRerror) suy gim di ngng th RNC s trigger
vic chuyn trng thi t HSDPA sang R99 v Serving Cell Change.
- Vn pht hin khi t pha RNC bt c bn tin trigger:
- Tham s khai bo lin quan:
HSDPASIRErrorReportPeriod: Chu k o c v bo co gi tr UL-SIR-Error ln RNC.
Nu Set = 0 th s khng s dng gi tr UL-SIR-Error trigger nn s loi b c channel
switching do trng hp ny.
PRFILE (007:0284 RN40_MAINT_014): Gi tr khai bo ca Parameter File. Nu thit
lp gi tr tham s bng 00FH th s loi b c channel switching do UL-SIR-Error, chi tit
nh x nh bng sau: