11/05/2012
UKRE/11/089
Project Team:
Ed Christian: [email protected]
Sanjay Peshion: [email protected]
Sasi Sasitharan: [email protected]
Wong Yook-Loon: [email protected]
Lotfi Kehal: [email protected]
Fractional DPCH (RAN1201) Live Network Trial Report
Introduction
This slide pack presents the result of “Fractional DPCH” feature trial
conducted in the O2UK live network environment.
This document is delivered by NSN as a part of the 3G Feature Trials and
Deployment project.
This feature was introduced in RU20 On-Top and belongs to application
software.
The “Fractional DPCH” feature introduces resolutions to the problem of DL
spreading code space limitation.
This feature is based on 3GPP Enhanced F-DPCH in Rel7.
The following sites in RNC37 were idenfied as the candidate sites for the trial.
1
Site Name RNC ID WBTS ID
W046257_CANAL_H 37 48
W042943_WESTFIL 37 49
W042942_CLAYHIL 37 52
W042944_SPEENHA 37 78
W036940_UPPER_B 37 91
2
The feature trial was conducted in 3 phases as presented below (feature
rolled back on 09/05/2012):
Introduction
Trial Phases Trial Description Date of Activation
Phase 1Enable F-DPCH allocation along with user plane allocation
(FDPCHSetup=2) 16/04/2012
Phase 2 Enable immediate F-DPCH allocation (FDPCHSetup=0) 23/04/2012
Phase 3ATOSRBsOnHSPA parameter modified from 300ms to 500ms
while immediate F-DPCH allocation is enabled 30/04/2012
Objectives
3
To verify that the Fractional DPCH feature activation is successful without
causing any alarms.
To verify that the Fractional DPCH feature behaved as expected in the O2 UK
live network environment.
To verify that no service degradation occurred for interaction between FDPCH
supported cell to non-FDPCH supported cell.
To assess positive and negative impacts on Business Critical KPIs (voice and
data) due to the activation of the feature.
Ensure that M1002C664 to M1002C667 counters are incremented with the
activation of Fractional DPCH feature.
Summary Results
4
Performance Measure Pass /
FailResults
Expected
ResultsIssues/Comments
Feature Activation Pass Successful Yes No issues
Alarms Pass Successful Yes None
Feature Verification:
1. Enable F-DPCH allocation along with user
plane allocation (FDPCHSetup=2).
2. Enable immediate F-DPCH allocation
(FDPCHSetup=0)
Pass Successful YesThe FDPCH information has been observed in the
Layer 3 messages.
Coverage Dependency (Field testing) Pass Successful Yes
Softer and soft handovers (Field testing) Pass Successful Yes
HSDPA Accessibility (Network data) Fail0.2%
degradationNo
HSDPA Accessibility degraded by 0.2% due to
increase in SETUP_FAIL_UE_HS_DSCH_INT.
Resolve Case:NA05188968
HSUPA Accessibility (Network data) Fail0.1%
degradationNo
HSUPA Accessibility degraded by 0.1% due to
increase in SETUP_FAIL_EDCH_UE_INT. Resolve
Case:NA05188975
HSDPA Retainability (Network data) Fail0.4%
degradationNo
HSDPA Retainability degraded by 0.4% due to
increase in REL_ALLO_RL_FAIL_HS_DSCH_INT.
Resolve Case:NA05188978
HSUPA Retainability (Network data) Fail0.1%
degradationNo
HSUPA Retainability degraded by 0.4% due to
increase in REL_EDCH_RL_FAIL_INT. Resolve
Case:NA05188979
CELL_UPDATE_ATT_R_LINK_FAIL
(Network data)Fail
On average
increased from
1283 to 3113
No
Significant increase in
CELL_UPDATE_ATT_R_LINK_FAIL failures.
Resolve Case:NA05188980
F-DPCH Feature Trial on 5 Sites
Summary Results...cont
5
Performance Measure Pass /
FailResults
Expected
ResultsIssues/Comments
PS_REL_RL_FAIL_HS_E_INT
(Network data)Fail
On average
increased from
671 to 1513
NoSignificant increase in PS_REL_RL_FAIL_HS_E_INT
failures. Resolve Case:NA05188981
SCC_FAILED_DUE_TO_OTHER
(Network data)Fail
On average
increased from
7 to 262
No
Significant increase in
SCC_FAILED_DUE_TO_OTHER failures. Resolve
Case:NA05188982
FAIL_RB_SETUP_HSDPA_UE
(Network data)Fail
On average
increased from
144 to 487
NoIncrease in FAIL_RB_SETUP_HSDPA_UE. Resolve
Case:: NA05188987
Increment of F-DPCH feature related counters
ALLO_EDCH_SRB_SRNC and
ALLO_HS_DSCH_SRB_SRNC
Pass Incremented Yes F-DPCH feature related counters incremented
HSDPA/HSUPA Throughput and
HSDPA/HSUPA ErlangsPass No impact Yes
Soft Handover performance Pass No impact Yes
Inter-System Handover performance Pass No impact Yes
RRC performance Pass No impact Yes
Voice related performance including voice
MPDPass No impact Yes
F-DPCH Feature Trial on 5 Sites
Conclusions and Recommendations
6
Feature Activation: The FDPCH feature activations for candidate trial sites have
been successful without causing any alarms.
Feature Verification: The F-DPCH feature functionality has been verified in the
live network environment using a Release 8 device. It has been verified that F-
DPCH information observed in the Layer 3 messages for the following scenarios
of the F-DPCH allocations:
F-DPCH allocation along with the user plane allocation.
F-DPCH with immediate allocation.
Coverage Dependency: The Coverage Dependency verification test showed
that, when the UE coverage reaches the threshold of
CPICHRSCPThreSRBHSDPA, F-DPCH was not allocated, and when the UE
coverage is reached above the threshold F-DPCH is re-allocated.
Conclusions and Recommendations
7
Soft/Softer Handover: Field testing has revealed that softer and soft handovers
were successful in the following scenarios:
F-DPCH Feature Related Counters: The ALLO_EDCH_SRB_SRNC and
ALLO_HS_DSCH_SRB_SRNC counters were observed to be incremented.
Impact on Business Critical KPIs:
HSDPA Accessibility performance degraded by ~0.2% due to UE failures
HSUPA Accessibility performance degraded by ~0.1% due to UE failures
HSDPA Retainability performance degraded by ~0.4% due to RL failures
HSUPA Retainability performance degraded by ~0.1% due to RL failures
Call Setup
Success
Soft
Handover
Softer
Handover
Call Setup
Success
Soft
Handover
Softer
Handover
N/A N/A
N/A N/A
FDPCH Immediate allocation (Phase2)
Scenario
s
FDPCH to FDPCH
FDPCH to Non FDPCH
Non FDPCH to FDPCH
FDPCH allocation along user plane
allocation (Phase1)
Conclusions and Recommendations
8
ATOSRBsOnHSPA parameter change: Changing ATO parameter value from
300ms to 500ms has not impacted UE failures.
Other failure counter increase:
Increase in CELL_UPDATE_ATT_R_LINK_FAIL counter
Increase in PS_REL_RL_FAIL_HS_E_INT counter
Increase in SCC_FAILED_DUE_TO_OTHER counter
Increase in FAIL_RB_SETUP_HSDPA_UE counter
SHO and ISHO performance: SHO and ISHO performance remained at pre-trial
levels
HSDPA Data Volume: There were no noticeable impact on HSDPA data volume
In light of the customer impacting issues observed with the F-DPCH feature, it is
recommended that this feature should not be rolled out across the network at
present. A further detailed trial should be conducted once the highlighted issues
are resolved.
Parameter Setting for Phase 1 Trial
9
The parameter setting for Phase 1 trial is presented below. In this phase
FDPCHSetup parameter is set to 2 to enable F-DPCH allocation along with
user plane allocation.
10
Parameter Setting for Phase 2 Trial
The parameter setting for Phase 2 trial is presented below. In this phase
FDPCHSetup parameter is changed to 0 to enable immediate F-DPCH
allocation.
11
Parameter Setting for Phase 3 Trial
The parameter setting for Phase 3 trial is presented below. In this phase
ATOSRBsOnHSPA parameter value was modified from 300ms to 500ms
while Immediate F-DPCH allocation is enabled.
F-DPCH Feature Related Measurement Counters
12
The following F-DPCH feature related measurement counters are available:
Counter ID Counter Name
M1002C664 ALLO_EDCH_SRB_SRNC
M1002C665 ALLO_EDCH_SRB_DRNC
M1002C666 ALLO_HS_DSCH_SRB_SRNC
M1002C667 ALLO_HS_DSCH_SRB_DRNC
Performance Analysis: HSDPA Accessibility
13
End user HSDPA Accessibility degraded by ~0.2% with the activation of FDPCH
feature on 16/04/2012.
As shown in the next slide, HSDPA Accessibility degradation is caused due to
increase in SETUP_FAIL_UE_HS_DSCH_INT failures.
This failure was observed across all the candidate trial cells.
Increasing ATOSRBsOnHSPA parameter from 300ms to 500ms does not show
any noticeable reduction in SETUP_FAIL_UE_HS_DSCH_INT failures.
A Resolve Case has been raised to investigate this particular UE related failure.
(Case Reference:NA05188968)
0
200
400
600
800
1000
1200
99.6%
99.6%
99.7%
99.7%
99.8%
99.8%
99.9%
99.9%
100.0%
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
HSDPA Accessibility (Aggregated - 30 cells)
Sum of SETUP_FAIL_UE_HS_DSCH_INT Average of % End User HSDPA Accessibility
14
Performance Analysis: HSDPA Accessibility.. Cont..
0
20
40
60
80
100
120
140
160
180
200
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
SETUP_FAIL_UE_HS_DSCH_INT 1/1/0369401/1/0429421/1/0429431/1/0429441/1/0462571/2/0369401/2/0429421/2/0429431/2/0429441/2/0462572/1/0369402/1/0429422/1/0429432/1/0429442/1/0462572/2/0369402/2/0429422/2/0429432/2/0429442/2/0462573/1/0369403/1/042942
15
Performance Analysis: HSUPA Accessibility
End user HSUPA Accessibility degraded by ~0.1% with the activation of FDPCH
feature on 16/04/2012.
As shown in the next slide, HSUPA Accessibility degradation is caused due to
increase in SETUP_FAIL_EDCH_UE_INT failures.
This failure was observed across most of the candidate trial cells.
Increasing ATOSRBsOnHSPA parameter from 300ms to 500ms does not show
any noticeable reduction in SETUP_FAIL_EDCH_UE_INT failures.
A Resolve Case has been raised to investigate this particular UE related failure.
(Case Reference:NA05188975)
0
20
40
60
80
100
120
140
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
SETUP_FAIL_EDCH_UE_INT1/1/0369401/1/0429421/1/0429431/1/0429441/1/0462571/2/0369401/2/0429421/2/0429431/2/0429441/2/0462572/1/0369402/1/0429422/1/0429432/1/0429442/1/0462572/2/0369402/2/0429422/2/0429432/2/0429442/2/046257
Performance Analysis: HSUPA Accessibility...Cont..
16
0
100
200
300
400
500
600
99.74%
99.76%
99.78%
99.80%
99.82%
99.84%
99.86%
99.88%
99.90%
99.92%
99.94%
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
HSUPA Accessibility (Aggregated - 30 cells)
Sum of SETUP_FAIL_EDCH_UE_INT Average of % End User HSUPA Accessibility
Performance Analysis: HSDPA Retainability
17
End user HSDPA Retainability degraded by ~0.4% with the activation of FDPCH
feature on 16/04/2012.
As shown in the next slide, HSDPA Retainability degradation is caused due to
increase in REL_ALLO_RL_FAIL_HS_DSCH_INT failures.
This failure was observed across most of the candidate trial cells.
A Resolve Case has been raised to investigate this particular failure. (Case
Reference: NA05188978)
Performance Analysis: HSDPA Retainability...cont...
18
0
500
1000
1500
2000
2500
3000
3500
4000
98.6%
98.8%
99.0%
99.2%
99.4%
99.6%
99.8%
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
HSDPA Retainability (Aggregated - 30 cells)
Sum of REL_ALLO_RL_FAIL_HS_DSCH_INT Average of % HSDPA Retainability
0
100
200
300
400
500
600
700
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
REL_ALLO_RL_FAIL_HS_DSCH_INT 1/1/0369401/1/0429421/1/0429431/1/0429441/1/0462571/2/0369401/2/0429421/2/0429431/2/0429441/2/0462572/1/0369402/1/0429422/1/0429432/1/0429442/1/0462572/2/0369402/2/0429422/2/0429432/2/0429442/2/0462573/1/0369403/1/042942
Performance Analysis: HSUPA Retainability
19
End user HSUPA Retainability degraded by ~0.1% with the activation of FDPCH
feature on 16/04/2012.
As shown in the next slide, HSUPA Retainability degradation is caused due to
increase in REL_EDCH_RL_FAIL_INT failures.
This failure was observed across most of the candidate trial cells.
A Resolve Case has been raised to investigate this particular failure. (Case
Reference: NA05188979)
Performance Analysis: HSUPA Retainability.. Cont..
20
0
100
200
300
400
500
600
97.5%
98.0%
98.5%
99.0%
99.5%
100.0%
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
HSUPA Retainability (Aggregated - 30 cells)
Sum of SETUP_FAIL_EDCH_UE_INT Average of % HSUPA Retainability
0
200
400
600
800
1000
1200
1400
1600
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
REL_EDCH_RL_FAIL_INT
1/1/036940
1/1/042942
1/1/042943
1/1/042944
1/1/046257
1/2/036940
1/2/042942
1/2/042943
1/2/042944
1/2/046257
Performance Analysis: Cell Update due to RL Failures
21
0
500
1000
1500
2000
2500
3000
3500
4000
4500
5000
01/0
4/20
12
02/0
4/20
12
03/0
4/20
12
04/0
4/20
12
05/0
4/20
12
06/0
4/20
12
07/0
4/20
12
08/0
4/20
12
09/0
4/20
12
10/0
4/20
12
11/0
4/20
12
12/0
4/20
12
13/0
4/20
12
14/0
4/20
12
15/0
4/20
12
16/0
4/20
12
17/0
4/20
12
18/0
4/20
12
19/0
4/20
12
20/0
4/20
12
21/0
4/20
12
22/0
4/20
12
23/0
4/20
12
24/0
4/20
12
25/0
4/20
12
26/0
4/20
12
27/0
4/20
12
28/0
4/20
12
29/0
4/20
12
30/0
4/20
12
01/0
5/20
12
02/0
5/20
12
03/0
5/20
12
04/0
5/20
12
05/0
5/20
12
CELL_UPDATE_ATT_R_LINK_FAIL
0
100
200
300
400
500
600
700
800
900
1000
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
CELL_UPDATE_ATT_R_LINK_FAIL
1/1/036940
1/1/042942
1/1/042943
1/1/042944
1/1/046257
1/2/036940
1/2/042942
1/2/042943
1/2/042944
1/2/046257
Cell Update attempts due to RL failures increased with the activation of FDPCH
feature. A Resolve Case has been raised (Case Reference:NA05188980)
22
Performance Analysis: PS_REL_RL_FAIL_HS_E_INT
0
500
1000
1500
2000
2500
01/0
4/20
12
02/0
4/20
12
03/0
4/20
12
04/0
4/20
12
05/0
4/20
12
06/0
4/20
12
07/0
4/20
12
08/0
4/20
12
09/0
4/20
12
10/0
4/20
12
11/0
4/20
12
12/0
4/20
12
13/0
4/20
12
14/0
4/20
12
15/0
4/20
12
16/0
4/20
12
17/0
4/20
12
18/0
4/20
12
19/0
4/20
12
20/0
4/20
12
21/0
4/20
12
22/0
4/20
12
23/0
4/20
12
24/0
4/20
12
25/0
4/20
12
26/0
4/20
12
27/0
4/20
12
28/0
4/20
12
29/0
4/20
12
30/0
4/20
12
01/0
5/20
12
02/0
5/20
12
03/0
5/20
12
04/0
5/20
12
05/0
5/20
12
PS_REL_RL_FAIL_HS_E_INT
0
100
200
300
400
500
600
01/0
4/20
12
02/0
4/20
12
03/0
4/20
12
04/0
4/20
12
05/0
4/20
12
06/0
4/20
12
07/0
4/20
12
08/0
4/20
12
09/0
4/20
12
10/0
4/20
12
11/0
4/20
12
12/0
4/20
12
13/0
4/20
12
14/0
4/20
12
15/0
4/20
12
16/0
4/20
12
17/0
4/20
12
18/0
4/20
12
19/0
4/20
12
20/0
4/20
12
21/0
4/20
12
22/0
4/20
12
23/0
4/20
12
24/0
4/20
12
25/0
4/20
12
26/0
4/20
12
27/0
4/20
12
28/0
4/20
12
29/0
4/20
12
30/0
4/20
12
01/0
5/20
12
02/0
5/20
12
03/0
5/20
12
04/0
5/20
12
05/0
5/20
12
PS_REL_RL_FAIL_HS_E_INT 1/1/0369401/1/0429421/1/0429431/1/0429441/1/0462571/2/0369401/2/0429421/2/0429431/2/0429441/2/0462572/1/0369402/1/0429422/1/0429432/1/0429442/1/0462572/2/0369402/2/0429422/2/0429432/2/0429442/2/046257
PS_REL_RL_FAIL_HS_E_INT failures increased with the activation of FDPCH
feature. A Resolve Case has been raised (Case Reference: NA05188981)
0
10
20
30
40
50
60
70
80
01/0
4/20
12
02/0
4/20
12
03/0
4/20
12
04/0
4/20
12
05/0
4/20
12
06/0
4/20
12
07/0
4/20
12
08/0
4/20
12
09/0
4/20
12
10/0
4/20
12
11/0
4/20
12
12/0
4/20
12
13/0
4/20
12
14/0
4/20
12
15/0
4/20
12
16/0
4/20
12
17/0
4/20
12
18/0
4/20
12
19/0
4/20
12
20/0
4/20
12
21/0
4/20
12
22/0
4/20
12
23/0
4/20
12
24/0
4/20
12
25/0
4/20
12
26/0
4/20
12
27/0
4/20
12
28/0
4/20
12
29/0
4/20
12
30/0
4/20
12
01/0
5/20
12
02/0
5/20
12
03/0
5/20
12
04/0
5/20
12
05/0
5/20
12
SCC_FAILED_DUE_TO_OTHER
1/1/036940
1/1/042942
1/1/042943
1/1/042944
1/1/046257
1/2/036940
1/2/042942
1/2/042943
1/2/042944
1/2/046257
2/1/036940
0
50
100
150
200
250
300
350
400
450
500
01/0
4/20
12
02/0
4/20
12
03/0
4/20
12
04/0
4/20
12
05/0
4/20
12
06/0
4/20
12
07/0
4/20
12
08/0
4/20
12
09/0
4/20
12
10/0
4/20
12
11/0
4/20
12
12/0
4/20
12
13/0
4/20
12
14/0
4/20
12
15/0
4/20
12
16/0
4/20
12
17/0
4/20
12
18/0
4/20
12
19/0
4/20
12
20/0
4/20
12
21/0
4/20
12
22/0
4/20
12
23/0
4/20
12
24/0
4/20
12
25/0
4/20
12
26/0
4/20
12
27/0
4/20
12
28/0
4/20
12
29/0
4/20
12
30/0
4/20
12
01/0
5/20
12
02/0
5/20
12
03/0
5/20
12
04/0
5/20
12
05/0
5/20
12
SCC_FAILED_DUE_TO_OTHER
Performance Analysis: SCC_FAILED_DUE_TO_OTHER
23
SCC_FAILED_DUE_TO_OTHER increased with the activation of FDPCH feature.
A Resolve Case has been raised (Case Reference: NA05188982)
Performance Analysis: FAIL_RB_SETUP_HSDPA_UE
24
0
100
200
300
400
500
600
700
800
01/0
4/20
12
02/0
4/20
12
03/0
4/20
12
04/0
4/20
12
05/0
4/20
12
06/0
4/20
12
07/0
4/20
12
08/0
4/20
12
09/0
4/20
12
10/0
4/20
12
11/0
4/20
12
12/0
4/20
12
13/0
4/20
12
14/0
4/20
12
15/0
4/20
12
16/0
4/20
12
17/0
4/20
12
18/0
4/20
12
19/0
4/20
12
20/0
4/20
12
21/0
4/20
12
22/0
4/20
12
23/0
4/20
12
24/0
4/20
12
25/0
4/20
12
26/0
4/20
12
27/0
4/20
12
28/0
4/20
12
29/0
4/20
12
30/0
4/20
12
01/0
5/20
12
02/0
5/20
12
03/0
5/20
12
04/0
5/20
12
05/0
5/20
12
FAIL_RB_SETUP_HSDPA_UE
0
50
100
150
200
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
FAIL_RB_SETUP_HSDPA_UE1/1/0369401/1/0429421/1/0429431/1/0429441/1/0462571/2/0369401/2/0429421/2/0429431/2/0429441/2/0462572/1/0369402/1/0429422/1/0429432/1/0429442/1/0462572/2/0369402/2/0429422/2/0429432/2/042944
FAIL_RB_SETUP_HSDPA_UE increased with the activation of FDPCH feature. A
Resolve Case has been raised (Case Reference: NA05188987)
Performance Analysis: Feature Related Counters
25
The FDPCH feature related traffic counters ALLO_EDCH_SRB_SRNC and
ALLO_HS_DSCH_SRB_SRNC have incremented with the FDPCH feature activation.
The ALLO_EDCH_SRB_SRNC counter provides the number of successful E-DCH
allocations for Signalling Radio Bearer in the SRNC.
The ALLO_HS_DSCH_SRB_SRNC counter provides the number of successful HS-DSCH
allocations for Signalling Radio Bearer in the SRNC.
As presented in the next slide most of the trial sites are reporting FDPCH feature related
counters incrementing.
0
20000
40000
60000
80000
100000
120000
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
06
/05
/20
12
07
/05
/20
12
ALLO_EDCH_SRB_SRNC & ALLO_HS_DSCH_SRB_SRNC (Aggregated - 30 cells)
Sum of ALLO_EDCH_SRB_SRNC Sum of ALLO_HS_DSCH_SRB_SRNC
Performance Analysis: Feature Related Counters
26
0
2000
4000
6000
8000
10000
12000
14000
16000
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
06
/05
/20
12
07
/05
/20
12
ALLO_EDCH_SRB_SRNC - Cell Level
1/1/036940 1/1/042942 1/1/042943 1/1/042944 1/1/046257 1/2/036940 1/2/042942 1/2/042943
1/2/042944 1/2/046257 2/1/036940 2/1/042942 2/1/042943 2/1/042944 2/1/046257 2/2/036940
2/2/042942 2/2/042943 2/2/042944 2/2/046257 3/1/036940 3/1/042942 3/1/042943 3/1/042944
3/1/046257 3/2/036940 3/2/042942 3/2/042943 3/2/042944 3/2/046257
0
500
1000
1500
2000
2500
3000
3500
4000
01
/04
/20
12
02
/04
/20
12
03
/04
/20
12
04
/04
/20
12
05
/04
/20
12
06
/04
/20
12
07
/04
/20
12
08
/04
/20
12
09
/04
/20
12
10
/04
/20
12
11
/04
/20
12
12
/04
/20
12
13
/04
/20
12
14
/04
/20
12
15
/04
/20
12
16
/04
/20
12
17
/04
/20
12
18
/04
/20
12
19
/04
/20
12
20
/04
/20
12
21
/04
/20
12
22
/04
/20
12
23
/04
/20
12
24
/04
/20
12
25
/04
/20
12
26
/04
/20
12
27
/04
/20
12
28
/04
/20
12
29
/04
/20
12
30
/04
/20
12
01
/05
/20
12
02
/05
/20
12
03
/05
/20
12
04
/05
/20
12
05
/05
/20
12
06
/05
/20
12
07
/05
/20
12
ALLO_HS_DSCH_SRB_SRNC - Cell Level
1/1/036940 1/1/042942 1/1/042943 1/1/042944 1/1/046257 1/2/036940 1/2/042942 1/2/042943
1/2/042944 1/2/046257 2/1/036940 2/1/042942 2/1/042943 2/1/042944 2/1/046257 2/2/036940
2/2/042942 2/2/042943 2/2/042944 2/2/046257 3/1/036940 3/1/042942 3/1/042943 3/1/042944
3/1/046257 3/2/036940 3/2/042942 3/2/042943 3/2/042944 3/2/046257
Charts show that FDPCH feature related counters are incrementing across the
cells under trial
0
1,000
2,000
3,000
4,000
5,000
23-M
ar-1
224
-Mar
-12
25-M
ar-1
226
-Mar
-12
27-M
ar-1
228
-Mar
-12
29-M
ar-1
230
-Mar
-12
31-M
ar-1
201
-Apr
-12
02-A
pr-1
203
-Apr
-12
04-A
pr-1
205
-Apr
-12
06-A
pr-1
207
-Apr
-12
08-A
pr-1
209
-Apr
-12
10-A
pr-1
211
-Apr
-12
12-A
pr-1
213
-Apr
-12
14-A
pr-1
215
-Apr
-12
16-A
pr-1
217
-Apr
-12
18-A
pr-1
219
-Apr
-12
20-A
pr-1
221
-Apr
-12
22-A
pr-1
223
-Apr
-12
24-A
pr-1
225
-Apr
-12
26-A
pr-1
227
-Apr
-12
28-A
pr-1
229
-Apr
-12
30-A
pr-1
201
-May
-12
HSUPA Data Volume (Mbytes)
HSUPA Data Volume Mbytes
Performance Analysis: HSDPA/HSUPA Throughput
27
0
200
400
600
800
1000
1200
1400
22
-Mar
-12
23
-Mar
-12
24
-Mar
-12
25
-Mar
-12
26
-Mar
-12
27
-Mar
-12
28
-Mar
-12
29
-Mar
-12
30
-Mar
-12
31
-Mar
-12
01
-Ap
r-1
2
02
-Ap
r-1
2
03
-Ap
r-1
2
04
-Ap
r-1
2
05
-Ap
r-1
2
06
-Ap
r-1
2
07
-Ap
r-1
2
08
-Ap
r-1
2
09
-Ap
r-1
2
10
-Ap
r-1
2
11
-Ap
r-1
2
12
-Ap
r-1
2
13
-Ap
r-1
2
14
-Ap
r-1
2
15
-Ap
r-1
2
16
-Ap
r-1
2
17
-Ap
r-1
2
18
-Ap
r-1
2
19
-Ap
r-1
2
20
-Ap
r-1
2
21
-Ap
r-1
2
22
-Ap
r-1
2
23
-Ap
r-1
2
24
-Ap
r-1
2
25
-Ap
r-1
2
26
-Ap
r-1
2
27
-Ap
r-1
2
28
-Ap
r-1
2
29
-Ap
r-1
2
30
-Ap
r-1
2
01
-May
-12
02
-May
-12
03
-May
-12
HSDPA Interactive Erlangs
HSDPA Interactive Erlangs
0
200
400
600
800
1000
1200
22
-Mar
-12
23
-Mar
-12
24
-Mar
-12
25
-Mar
-12
26
-Mar
-12
27
-Mar
-12
28
-Mar
-12
29
-Mar
-12
30
-Mar
-12
31
-Mar
-12
01
-Ap
r-1
2
02
-Ap
r-1
2
03
-Ap
r-1
2
04
-Ap
r-1
2
05
-Ap
r-1
2
06
-Ap
r-1
2
07
-Ap
r-1
2
08
-Ap
r-1
2
09
-Ap
r-1
2
10
-Ap
r-1
2
11
-Ap
r-1
2
12
-Ap
r-1
2
13
-Ap
r-1
2
14
-Ap
r-1
2
15
-Ap
r-1
2
16
-Ap
r-1
2
17
-Ap
r-1
2
18
-Ap
r-1
2
19
-Ap
r-1
2
20
-Ap
r-1
2
21
-Ap
r-1
2
22
-Ap
r-1
2
23
-Ap
r-1
2
24
-Ap
r-1
2
25
-Ap
r-1
2
26
-Ap
r-1
2
27
-Ap
r-1
2
28
-Ap
r-1
2
29
-Ap
r-1
2
30
-Ap
r-1
2
01
-May
-12
02
-May
-12
03
-May
-12
HSPA Interactive Erlangs
HSPA Interactive Erlangs
0.6
10.6
20.6
30.6
40.6
50.6
60.6
22-M
ar-1
223
-Mar
-12
24-M
ar-1
225
-Mar
-12
26-M
ar-1
227
-Mar
-12
28-M
ar-1
229
-Mar
-12
30-M
ar-1
231
-Mar
-12
01-A
pr-1
202
-Apr
-12
03-A
pr-1
204
-Apr
-12
05-A
pr-1
206
-Apr
-12
07-A
pr-1
208
-Apr
-12
09-A
pr-1
210
-Apr
-12
11-A
pr-1
212
-Apr
-12
13-A
pr-1
214
-Apr
-12
15-A
pr-1
216
-Apr
-12
17-A
pr-1
218
-Apr
-12
19-A
pr-1
220
-Apr
-12
21-A
pr-1
222
-Apr
-12
23-A
pr-1
224
-Apr
-12
25-A
pr-1
226
-Apr
-12
27-A
pr-1
228
-Apr
-12
29-A
pr-1
230
-Apr
-12
01-M
ay-1
202
-May
-12
HSDPA Data Volume (Mbps)
HSDPA Data Volume Mbps
HSDPA throughput performance remained at pre-trial levels.
Performance Analysis: RRC Performance
28
0.0
0.0
0.0
0.1
0.1
0.1
0.1
0.1
0.2
95
96
97
98
99
1000
3.2
2.2
01
2
03
.23
.20
12
03
.24
.20
12
03
.25
.20
12
03
.26
.20
12
03
.27
.20
12
03
.28
.20
12
03
.29
.20
12
03
.30
.20
12
03
.31
.20
12
04
.01
.20
12
04
.02
.20
12
04
.03
.20
12
04
.04
.20
12
04
.05
.20
12
04
.06
.20
12
04
.07
.20
12
04
.08
.20
12
04
.09
.20
12
04
.10
.20
12
04
.11
.20
12
04
.12
.20
12
04
.13
.20
12
04
.14
.20
12
04
.15
.20
12
04
.16
.20
12
04
.17
.20
12
04
.18
.20
12
04
.19
.20
12
04
.20
.20
12
04
.21
.20
12
04
.22
.20
12
04
.23
.20
12
04
.24
.20
12
04
.25
.20
12
04
.26
.20
12
04
.27
.20
12
04
.28
.20
12
04
.29
.20
12
04
.30
.20
12
05
.01
.20
12
05
.02
.20
12
05
.03
.20
12
#M
illio
ns
%RRC Performance (Aggregated Performance - 30 cells)
RNC_214a RRC Setup attempts (#)
RNC_94e RRC Setup and Access Complete Ratio from the network point of view (%)
RNC_154d RRC Setup and Access Complete Ratio from end user perspective (%)
RNC_20b RRC Connection setup success ratio (%)
RNC_217f RRC Connection Succ Ratio (%)
Performance Analysis: Voice MPD
29
0
2000
4000
6000
8000
10000
12000
14000
16000
18000
20000
0
100
200
300
400
500
600
700
800
900
1000
22
-Mar
-12
23
-Mar
-12
24
-Mar
-12
25
-Mar
-12
26
-Mar
-12
27
-Mar
-12
28
-Mar
-12
29
-Mar
-12
30
-Mar
-12
31
-Mar
-12
01
-Ap
r-1
2
02
-Ap
r-1
2
03
-Ap
r-1
2
04
-Ap
r-1
2
05
-Ap
r-1
2
06
-Ap
r-1
2
07
-Ap
r-1
2
08
-Ap
r-1
2
09
-Ap
r-1
2
10
-Ap
r-1
2
11
-Ap
r-1
2
12
-Ap
r-1
2
13
-Ap
r-1
2
14
-Ap
r-1
2
15
-Ap
r-1
2
16
-Ap
r-1
2
17
-Ap
r-1
2
18
-Ap
r-1
2
19
-Ap
r-1
2
20
-Ap
r-1
2
21
-Ap
r-1
2
22
-Ap
r-1
2
23
-Ap
r-1
2
24
-Ap
r-1
2
25
-Ap
r-1
2
26
-Ap
r-1
2
27
-Ap
r-1
2
28
-Ap
r-1
2
29
-Ap
r-1
2
30
-Ap
r-1
2
01
-May
-12
02
-May
-12
Voice MPD
NOK RAB Attempts CS Voice VOICE_MPD
0
10
20
30
40
50
60
22-M
ar-1
2
23-M
ar-1
2
24-M
ar-1
2
25-M
ar-1
2
26-M
ar-1
2
27-M
ar-1
2
28-M
ar-1
2
29-M
ar-1
2
30-M
ar-1
2
31-M
ar-1
2
01-A
pr-1
2
02-A
pr-1
2
03-A
pr-1
2
04-A
pr-1
2
05-A
pr-1
2
06-A
pr-1
2
07-A
pr-1
2
08-A
pr-1
2
09-A
pr-1
2
10-A
pr-1
2
11-A
pr-1
2
12-A
pr-1
2
13-A
pr-1
2
14-A
pr-1
2
15-A
pr-1
2
16-A
pr-1
2
17-A
pr-1
2
18-A
pr-1
2
19-A
pr-1
2
20-A
pr-1
2
21-A
pr-1
2
22-A
pr-1
2
23-A
pr-1
2
24-A
pr-1
2
25-A
pr-1
2
26-A
pr-1
2
27-A
pr-1
2
28-A
pr-1
2
29-A
pr-1
2
30-A
pr-1
2
01-M
ay-1
2
02-M
ay-1
2
RAB_ACT_FAIL_CS_VOICE Failures
RAB_ACT_FAIL_CS_VOICE_TRANS RAB_ACT_FAIL_CS_VOICE_RADIO RAB_ACT_FAIL_CS_VOICE_BTS
RAB_ACT_FAIL_CS_VOICE_IUR RAB_ACT_FAIL_CS_VOICE_UE RAB_ACT_FAIL_CS_VOICE_RNC
Voice MPD performance has not impacted due to the activation of FDPCH
feature.
0.0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
97.0
97.5
98.0
98.5
99.0
99.5
100.00
3.2
2.2
01
2
03
.23
.20
12
03
.24
.20
12
03
.25
.20
12
03
.26
.20
12
03
.27
.20
12
03
.28
.20
12
03
.29
.20
12
03
.30
.20
12
03
.31
.20
12
04
.01
.20
12
04
.02
.20
12
04
.03
.20
12
04
.04
.20
12
04
.05
.20
12
04
.06
.20
12
04
.07
.20
12
04
.08
.20
12
04
.09
.20
12
04
.10
.20
12
04
.11
.20
12
04
.12
.20
12
04
.13
.20
12
04
.14
.20
12
04
.15
.20
12
04
.16
.20
12
04
.17
.20
12
04
.18
.20
12
04
.19
.20
12
04
.20
.20
12
04
.21
.20
12
04
.22
.20
12
04
.23
.20
12
04
.24
.20
12
04
.25
.20
12
04
.26
.20
12
04
.27
.20
12
04
.28
.20
12
04
.29
.20
12
04
.30
.20
12
05
.01
.20
12
05
.02
.20
12
05
.03
.20
12
#M
illio
ns
%
Soft Handover Performance (Aggregated Performance - 30 cells)
RNC_193b SHO Update Attempts RT (#) RNC_194b SHO Update Attempts NRT (#)
RNC_153b SHO Success Rate RT (%) RNC_191b SHO Success Rate NRT (%)
Performance Analysis: Soft Handover
30
0.0
0.5
1.0
1.5
2.0
2.5
3.0
3.5
4.0
4.5
5.0
70.0
75.0
80.0
85.0
90.0
95.0
100.00
3.2
2.2
01
2
03
.23
.20
12
03
.24
.20
12
03
.25
.20
12
03
.26
.20
12
03
.27
.20
12
03
.28
.20
12
03
.29
.20
12
03
.30
.20
12
03
.31
.20
12
04
.01
.20
12
04
.02
.20
12
04
.03
.20
12
04
.04
.20
12
04
.05
.20
12
04
.06
.20
12
04
.07
.20
12
04
.08
.20
12
04
.09
.20
12
04
.10
.20
12
04
.11
.20
12
04
.12
.20
12
04
.13
.20
12
04
.14
.20
12
04
.15
.20
12
04
.16
.20
12
04
.17
.20
12
04
.18
.20
12
04
.19
.20
12
04
.20
.20
12
04
.21
.20
12
04
.22
.20
12
04
.23
.20
12
04
.24
.20
12
04
.25
.20
12
04
.26
.20
12
04
.27
.20
12
04
.28
.20
12
04
.29
.20
12
04
.30
.20
12
05
.01
.20
12
05
.02
.20
12
05
.03
.20
12
#T
ho
usan
ds
%
ISHO Performance (Aggregated Performance - 30 cells)
RNC_298e ISHO Attempts RT (#) RNC_299d ISHO Attempts NRT (#)
RNC_300g ISHO Success Rate RT (%) RNC_301e ISHO Success Rate NRT (%)
Performance Analysis: ISHO
31
Field Testing: Trial Sites
32
The following sites on RNC37 were identified as candidates for the trial.
Field testing was performed to verify F-DPCH feature functionality.
Site Name RNC ID WBTS ID
W046257_CANAL_H 37 48
W042943_WESTFIL 37 49
W042942_CLAYHIL 37 52
W042944_SPEENHA 37 78
W036940_UPPER_B 37 91
Drive Route
33
Field Testing: Feature Verification Methodology Test Case Test Case Description Test Procedure
Test Case 1 Fractional DPCH Setup Verification Test
Step 1: Establish a HSDPA Data Call using Rel-7 or later release UE
Step 2: Ensure that F-DPCH information is observed in Radio Bearer Reconfiguration Message.
Step 3: Ensure that there were no call setup failures and call drops observed during the test.
Test Case 2Fractional DPCH Coverage
Dependency Verification Test
Step 1: Establish a HSDPA Data Call using Rel-7 or later release UE.
Step 2: Ensure that F-DPCH information is observed in RB Reconfiguration Message.
Step 3: Move UE towards cell coverage edge until the CPICH RSCP falls below the threshold
(-103dBm) value of RNC Parameter CPICHRSCPThreSRBHSDPA .
Step 4: Ensure that RB Reconfiguration Message is sent to show that Fractional DPCH is
removed.
Step 5: Move UE back to the cell until the CPICH RSCP falls above the threshold value of RNC
Parameter CPICHRSCPThreSRBHSDPA .
Step 6: Ensure that RB Reconfiguration Message is sent to show that Fractional DPCH is
allocated.
Step 7: Ensure that no call setup failures, call drops and SHO failures observed during the test.
Test Case 3Fractional DPCH Mobility
Verification Test (F-DPCH cell -> F-
DPCH cell)
Step 1: Establish a HSDPA Data Call using Rel-7 or later release UE.
Step 2: Ensure that F-DPCH information is observed in RB Reconfiguration Message.
Step 3: Move UE to another cell so that Soft Handover is achieved.
Step 4: Ensure that F-DPCH information for target cell is observed in Active Set Update Message
Step 5: Ensure that no call setup failures, call drops and SHO failures observed during the test.
Test Case 4
Fractional DPCH Mobility
Verification Test (F-DPCH cell ->
non F-DPCH cell)
Step 1: Establish a HSDPA Data Call using Rel-7 or later release UE.
Step 2: Ensure that F-DPCH information is observed in RB Reconfiguration Message.
Step 3: Move UE to another cell so that Soft Handover is achieved.
Step 4: Ensure that RB Reconfiguration Message is received and F-DPCH is removed.
Step 5: Ensure that no call setup failures, call drops and SHO failures observed during the test.
Test Case 5 Fractional DPCH Mobility
Verification Test (non F-DPCH cell -
> F-DPCH cell)
Step 1: Establish a HSDPA Data Call using Rel-7 or later release UE.
Step 2: Move UE to another cell which supports FDPCH so that Soft Handover is achieved.
Step 3: Further move the UE towards target cell until source cell is removed from active set list.
Step 4: Ensure that RB Reconfiguration Message contains FDPCH information is received after
Active Set Update Message (RL deletion).
Step 5: Ensure that no call setup failures, call drops and SHO failures observed during the test.
34
1. F-DPCH Setup Verification Test
HSDPA Data Call using Rel-8 UE, established.
F-DPCH allocation along with user plane allocation
enabled for cell PSC18.
F-DPCH information observed within in RB
Reconfiguration Message.
There were no call setup failures or drops observed
during the test.
Field Testing: Phase 1 Analysis
F-DPCH Enabled Cell
R8 UE
SC18
35
2. FDPCH Coverage Dependency Verification Test
FDPCH enabled for cell with PSC18, with the
allocation along with user plane allocation.
FDPCH is not allocated when the RSCP reach the
threshold value of CPICHRSCPThreSRBHSDPA,
which is -103dBm.
FDPCH has been reallocated when the RSCP
become higher then the threshold value of
CPICHRSCPThreSRBHSDPA.
There were no call setup failures or drops
observed during the test.
Field Testing: Phase 1 Analysis
F-DPCH Enabled Cell
R8 UE
SC18
UE Moving towards cell edge
36
3. Fractional DPCH Mobility Verification Test (F-DPCH cell -> F-DPCH cell)
FDPCH enabled for cell PSC18 & PSC392, with
the allocation along with user plane allocation.
Soft handover is completed successfully.
F-DPCH is remained during soft handover
process between Cell PSC18 & PSC392.
FDPCH information is observed in the Active Set
Update message.
There were no call setup failures or drops
observed during this test.
Field Testing: Phase 1 Analysis
F-DPCH Enabled Cell F-DPCH Enabled Cell
Mobility
SC18 SC392
37
4. Fractional DPCH Mobility Verification Test (F-DPCH cell -> Non F-DPCH cell)
FDPACH is not enabled for the cell with PSC108.
FDPCH enabled for cells PSC331 & PSC392, with
the allocation along with user plane allocation.
Soft handover is completed successfully. The non-
FDPCH cell (SC108) added to the Active set.
Fractional DPCH is not allocated for FDPCH enabled
cells (PSC=392 & 331) even before adding non
FDPCH cell (PSC=108) to the active set, due to
received RSCP level was below the threshold of
CPICHRSCPThreSRBHSDPA, which is -103dBm.
There were no call setup failures or drops observed
during the test.
Field Testing: Phase 1 Analysis
F-DPCH Enabled Cells
Non F-DPCH cell
Mobility
SC331 SC108
SC392
38
5. Fractional DPCH Mobility Verification Test (Non F-DPCH cell -> F-DPCH cell)
FDPACH is not enabled for the cell with PSC400.
FDPCH enabled for cells with PSC392 & PSC331,
with the allocation along with user plane allocation.
Soft Handover is completed successfully.
FDPCH should be allocated when the non FDPCH
Cell (SC400) is removed from the active set, but due
to received RSCP was below the threshold of
CPICHRSCPThreSRBHSDPA, which is -103dBm, the
FDPCH has not been allocated.
There were no call setup failures or drops observed
during this test.
Field Testing: Phase 1 Analysis
Non F-DPCH Cells
Mobility
SC400 SC331
SC392
F-DPCH Enabled Cells
39
1. Fractional DPCH Setup Verification Test
HSDPA Data Call using Rel-8 UE, established.
F-DPCH allocation along with immediate allocation
enabled for the cell PSC18.
F-DPCH information is observed in RB
Reconfiguration Message.
There were no call setup failures or drops
observed during the test.
Field Testing: Phase 2 Analysis
F-DPCH Enabled Cell
R8 UE
SC18
40
2. FDPCH Coverage Dependency Verification Test
FDPCH enabled for cell with PSC18, with the
Immediate allocation.
FDPCH is not allocated when the RSCP reach the
threshold of CPICHRSCPThreSRBHSDPA, which is
set to -103dBm.
FDPCH has been reallocated when the RSCP
become higher then the threshold of
CPICHRSCPThreSRBHSDPA, which is -103dBm.
There were no call setup failures or drops observed
during this test.
Field Testing: Phase 2 Analysis
F-DPCH Enabled Cell
R8 UE
SC18
UE moving toward the cell edge
41
3. Fractional DPCH Mobility Verification Test (F-DPCH cell -> F-DPCH cell)
FDPCH enabled for cell PSC18 & PSC331, with
the immediate allocation.
Soft handover is completed successfully.
F-DPCH is remained during soft handover
process between Cell PSC18 & PSC331.
FDPCH info observed in the Active Set Update
message.
There were no call setup failures or drops
observed during the test.
Field Testing: Phase 2 Analysis
F-DPCH Enabled Cell F-DPCH Enabled Cell
Mobility
SC18 SC331
42
4. Fractional DPCH Mobility Verification Test (F-DPCH cell -> Non F-DPCH cell)
FDPACH is not enabled for the cell with PSC400.
FDPCH enabled for cells PSC331 & PSC392, with
immediate allocation.
Soft handover is completed successfully. The non
FDPCH cell (SC400) added to the Active set.
Fractional DPCH is not allocated for FDPCH enabled
cells (PSC=392 & 331) even before adding non
FDPCH cell (PSC=400) to the active set, due to
received RSCP is below the threshold of
CPICHRSCPThreSRBHSDPA, which is -103dBm.
There were no call setup failures or drops observed
during the test.
Field Testing: Phase 2 Analysis
F-DPCH Enabled Cells
Non F-DPCH cell
Mobility
SC331 SC400
SC392
43
5. Fractional DPCH Mobility Verification Test (Non F-DPCH cell -> F-DPCH cell)
FDPACH is not enabled for the cell with PSC256.
FDPCH enabled for cell with PSC331, with the
Immediate allocation.
Soft Handover is completed successfully.
FDPCH should be allocated when the non FDPCH
Cell (SC256) is removed from the active set, but
due to received RSCP is below the threshold of
CPICHRSCPThreSRBHSDPA, which is -103dBm,
the FDPCH has not been allocated.
There were no call setup failures or drops
observed during the test.
Field Testing: Phase 2 Analysis
Non F-DPCH Cell F-DPCH Enabled Cell
Mobility
SC256 SC331
44
The F-DPCH feature functionality has been verified in the live network
environment using a Release 8 device, where the FDPCH information has been
observed in the Layer 3 messages.
The following scenarios of the F-DPCH allocations are verified:
F-DPCH allocation along with the user plane allocation.
F-DPCH with immediate allocation.
The Coverage Dependency verification test showed that, when the UE coverage
reaches the threshold of CPICHRSCPThreSRBHSDPA, F-DPCH was not
allocated. When coverage reaches above the threshold F-DPCH was re-
allocated.
Field testing has revealed that softer and soft handovers were successful.
Soft handovers were successful when the source and target cells both had F-
DPCH enabled.
Softer handovers were successful between sectors of the same sites for
which all the cells are F-DPCH enabled
Field Testing: Phase 1 and Phase 2 Summary
45
Soft and softer handover test summary:
There were no call setup failures or call drops reported during field testing with
the activation of F-DPCH feature.
Field Testing: Phase 1 and Phase 2 Summary
Call Setup
Success
Soft
Handover
Softer
Handover
Call Setup
Success
Soft
Handover
Softer
Handover
N/A N/A
N/A N/A
FDPCH Immediate allocation (Phase2)
Scenario
s
FDPCH to FDPCH
FDPCH to Non FDPCH
Non FDPCH to FDPCH
FDPCH allocation along user plane
allocation (Phase1)
Top Related