Você está na página 1de 47

Fractional DPCH (RAN1201) Live

Network Trial Report


11/05/2012

Project Team:
Ed Christian: ed.christian@nsn.com
Sanjay Peshion: sanjay.peshion.ext@nsn.com
Sasi Sasitharan: sasi.sasitharan@nsn.com
Wong Yook-Loon: yook-loon.wong@nsn.com
Lotfi Kehal: lotfi.kehal@nsn.com

UKRE/11/089

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.
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

Introduction
The feature trial was conducted in 3 phases as presented below (feature
rolled back on 09/05/2012):
Trial Phases
Phase 1
Phase 2
Phase 3

Trial Description
Enable F-DPCH allocation along with user plane allocation
(FDPCHSetup=2)
Enable immediate F-DPCH allocation (FDPCHSetup=0)
ATOSRBsOnHSPA parameter modified from 300ms to 500ms
while immediate F-DPCH allocation is enabled

Date of Activation
16/04/2012
23/04/2012
30/04/2012

Objectives
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
Performance Measure
Feature Activation
Alarms
Feature Verification:
1. Enable F-DPCH allocation along with user
plane allocation (FDPCHSetup=2).
2. Enable immediate F-DPCH allocation
(FDPCHSetup=0)
Coverage Dependency (Field testing)
Softer and soft handovers (Field testing)

F-DPCH Feature Trial on 5 Sites


Pass /
Expected
Results
Fail
Results
Pass
Successful
Yes
No issues
Pass
Successful
Yes
None

Pass

Successful

Yes

Pass
Pass

Successful
Successful

Yes
Yes

HSDPA Accessibility (Network data)

Fail

0.2%
degradation

No

HSUPA Accessibility (Network data)

Fail

0.1%
degradation

No

HSDPA Retainability (Network data)

Fail

0.4%
degradation

No

HSUPA Retainability (Network data)

Fail

0.1%
degradation

No

Fail

On average
increased from
1283 to 3113

No

CELL_UPDATE_ATT_R_LINK_FAIL
(Network data)

Issues/Comments

The FDPCH information has been observed in the


Layer 3 messages.

HSDPA Accessibility degraded by 0.2% due to


increase in SETUP_FAIL_UE_HS_DSCH_INT.
Resolve Case:NA05188968
HSUPA Accessibility degraded by 0.1% due to
increase in SETUP_FAIL_EDCH_UE_INT. Resolve
Case:NA05188975
HSDPA Retainability degraded by 0.4% due to
increase in REL_ALLO_RL_FAIL_HS_DSCH_INT.
Resolve Case:NA05188978
HSUPA Retainability degraded by 0.4% due to
increase in REL_EDCH_RL_FAIL_INT. Resolve
Case:NA05188979
Significant increase in
CELL_UPDATE_ATT_R_LINK_FAIL failures.
Resolve Case:NA05188980

Summary Results...cont
Performance Measure
PS_REL_RL_FAIL_HS_E_INT
(Network data)
SCC_FAILED_DUE_TO_OTHER
(Network data)
FAIL_RB_SETUP_HSDPA_UE
(Network data)
Increment of F-DPCH feature related counters
ALLO_EDCH_SRB_SRNC and
ALLO_HS_DSCH_SRB_SRNC
HSDPA/HSUPA Throughput and
HSDPA/HSUPA Erlangs
Soft Handover performance
Inter-System Handover performance
RRC performance
Voice related performance including voice
MPD

F-DPCH Feature Trial on 5 Sites


Pass /
Expected
Results
Issues/Comments
Fail
Results
On average
Significant increase in PS_REL_RL_FAIL_HS_E_INT
Fail
increased from
No
failures. Resolve Case:NA05188981
671 to 1513
On average
Significant increase in
Fail
increased from
No
SCC_FAILED_DUE_TO_OTHER failures. Resolve
7 to 262
Case:NA05188982
On average
Increase in FAIL_RB_SETUP_HSDPA_UE. Resolve
Fail
increased from
No
Case:: NA05188987
144 to 487
Pass

Incremented

Yes

Pass

No impact

Yes

Pass
Pass
Pass

No impact
No impact
No impact

Yes
Yes
Yes

Pass

No impact

Yes

F-DPCH feature related counters incremented

Conclusions and Recommendations


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 FDPCH 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


Soft/Softer Handover: Field testing has revealed that softer and soft handovers
were successful in the following scenarios:
io
ar
n
ce

S
FDPCH to FDPCH
FDPCH to Non FDPCH
Non FDPCH to FDPCH

FDPCH allocation along user plane


allocation (Phase1)
Call Setup
Soft
Softer
Success
Handover
Handover

N/A

N/A

FDPCH Immediate allocation (Phase2)


Call Setup
Success

Soft
Handover

Softer
Handover

N/A
N/A

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

Conclusions and Recommendations


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.
8

Parameter Setting for Phase 1 Trial


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.

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.

10

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.

11

F-DPCH Feature Related Measurement Counters


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

12

Performance Analysis: HSDPA Accessibility


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)

13

14
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

Sum of SETUP_FAIL_UE_HS_DSCH_INT

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

SETUP_FAIL_UE_HS_DSCH_INT

200
180
160
140
120
100
80
60
40
20
0
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: HSDPA Accessibility.. Cont..


100.0%
99.9%
99.9%
99.8%
99.8%
99.7%
99.7%
99.6%
99.6%

HSDPA Accessibility (Aggregated - 30 cells)


1200

1000
800

600

400

200
0

Average of % End User HSDPA Accessibility


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

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)

15

16
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

Sum of SETUP_FAIL_EDCH_UE_INT

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

140

120

100

80

60

40

20

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

99.94%
99.92%
99.90%
99.88%
99.86%
99.84%
99.82%
99.80%
99.78%
99.76%
99.74%

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: HSUPA Accessibility...Cont..


HSUPA Accessibility (Aggregated - 30 cells)
600

500

400

300

200

100
0

Average of % End User HSUPA Accessibility

SETUP_FAIL_EDCH_UE_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
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

Performance Analysis: HSDPA Retainability


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)

17

18
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

Sum of REL_ALLO_RL_FAIL_HS_DSCH_INT

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

700

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

REL_ALLO_RL_FAIL_HS_DSCH_INT

600

500

400

300

200

100

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: HSDPA Retainability...cont...


HSDPA Retainability (Aggregated - 30 cells)

99.8%
4000

99.6%
3500

99.4%
3000

2500

99.2%
2000

99.0%

1500

98.8%
1000
500

98.6%
0

Average of % HSDPA Retainability

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

Performance Analysis: HSUPA Retainability


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)

19

20
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

Sum of SETUP_FAIL_EDCH_UE_INT

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

400

200

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: HSUPA Retainability.. Cont..


100.0%

HSUPA Retainability (Aggregated - 30 cells)


600

99.5%

500

99.0%

400

98.5%

300

98.0%

200

100

97.5%
0

Average of % HSUPA Retainability

1600

REL_EDCH_RL_FAIL_INT

1400

1/1/036940

1200
1/1/042942

1000

1/1/042943

800
1/1/042944

600

1/1/046257

1/2/036940

1/2/042942

1/2/042943

1/2/042944

1/2/046257

21
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

1000

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

900

800

400

300

200

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: Cell Update due to RL Failures


Cell Update attempts due to RL failures increased with the activation of FDPCH
feature. A Resolve Case has been raised (Case Reference:NA05188980)
5000

CELL_UPDATE_ATT_R_LINK_FAIL

4500

4000

3500

3000

2500

2000

1500

1000

500

CELL_UPDATE_ATT_R_LINK_FAIL
1/1/036940

700
1/1/042942

600

1/1/042943

500
1/1/042944

1/1/046257

1/2/036940

100
1/2/042942

0
1/2/042943

1/2/042944

1/2/046257

22
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

600

PS_REL_RL_FAIL_HS_E_INT

500

400

300

200

100

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: PS_REL_RL_FAIL_HS_E_INT


PS_REL_RL_FAIL_HS_E_INT failures increased with the activation of FDPCH
feature. A Resolve Case has been raised (Case Reference: NA05188981)
PS_REL_RL_FAIL_HS_E_INT

2500

2000

1500

1000

500

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

23
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

70

60

50

40

30

20

10

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: SCC_FAILED_DUE_TO_OTHER


SCC_FAILED_DUE_TO_OTHER increased with the activation of FDPCH feature.
A Resolve Case has been raised (Case Reference: NA05188982)
500

SCC_FAILED_DUE_TO_OTHER

450

400

350

300

250

200

150

100

50

80

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

24
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

FAIL_RB_SETUP_HSDPA_UE

200

150

100

50

0
05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: FAIL_RB_SETUP_HSDPA_UE


FAIL_RB_SETUP_HSDPA_UE increased with the activation of FDPCH feature. A
Resolve Case has been raised (Case Reference: NA05188987)
800

FAIL_RB_SETUP_HSDPA_UE

700

600

500

400

300

200

100

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

Performance Analysis: Feature Related Counters


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.
ALLO_EDCH_SRB_SRNC & ALLO_HS_DSCH_SRB_SRNC (Aggregated - 30 cells)
120000
100000
80000
60000
40000
20000

Sum of ALLO_EDCH_SRB_SRNC

25

Sum of ALLO_HS_DSCH_SRB_SRNC

07/05/2012

06/05/2012

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

Performance Analysis: Feature Related Counters


Charts show that FDPCH feature related counters are incrementing across the
cells under trial
ALLO_EDCH_SRB_SRNC - Cell Level
16000
14000
12000
10000
8000
6000
4000
2000

1/1/036940
1/2/042944
2/2/042942
3/1/046257

1/1/042942
1/2/046257
2/2/042943
3/2/036940

1/1/042943
2/1/036940
2/2/042944
3/2/042942

1/1/042944
2/1/042942
2/2/046257
3/2/042943

1/1/046257
2/1/042943
3/1/036940
3/2/042944

1/2/036940
2/1/042944
3/1/042942
3/2/046257

1/2/042942
2/1/046257
3/1/042943

07/05/2012

06/05/2012

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

1/2/042943
2/2/036940
3/1/042944

ALLO_HS_DSCH_SRB_SRNC - Cell Level


4000
3500
3000
2500
2000
1500
1000
500

1/1/036940
1/2/042944
2/2/042942
3/1/046257

1/1/042942
1/2/046257
2/2/042943
3/2/036940

1/1/042943
2/1/036940
2/2/042944
3/2/042942

1/1/042944
2/1/042942
2/2/046257
3/2/042943

26

1/1/046257
2/1/042943
3/1/036940
3/2/042944

1/2/036940
2/1/042944
3/1/042942
3/2/046257

1/2/042942
2/1/046257
3/1/042943

07/05/2012

06/05/2012

05/05/2012

04/05/2012

03/05/2012

02/05/2012

01/05/2012

30/04/2012

29/04/2012

28/04/2012

27/04/2012

26/04/2012

25/04/2012

24/04/2012

23/04/2012

22/04/2012

21/04/2012

20/04/2012

19/04/2012

18/04/2012

17/04/2012

16/04/2012

15/04/2012

14/04/2012

13/04/2012

12/04/2012

11/04/2012

10/04/2012

09/04/2012

08/04/2012

07/04/2012

06/04/2012

05/04/2012

04/04/2012

03/04/2012

02/04/2012

01/04/2012

1/2/042943
2/2/036940
3/1/042944

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-Apr-12
02-Apr-12
03-Apr-12
04-Apr-12
05-Apr-12
06-Apr-12
07-Apr-12
08-Apr-12
09-Apr-12
10-Apr-12
11-Apr-12
12-Apr-12
13-Apr-12
14-Apr-12
15-Apr-12
16-Apr-12
17-Apr-12
18-Apr-12
19-Apr-12
20-Apr-12
21-Apr-12
22-Apr-12
23-Apr-12
24-Apr-12
25-Apr-12
26-Apr-12
27-Apr-12
28-Apr-12
29-Apr-12
30-Apr-12
01-May-12

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-Apr-12
02-Apr-12
03-Apr-12
04-Apr-12
05-Apr-12
06-Apr-12
07-Apr-12
08-Apr-12
09-Apr-12
10-Apr-12
11-Apr-12
12-Apr-12
13-Apr-12
14-Apr-12
15-Apr-12
16-Apr-12
17-Apr-12
18-Apr-12
19-Apr-12
20-Apr-12
21-Apr-12
22-Apr-12
23-Apr-12
24-Apr-12
25-Apr-12
26-Apr-12
27-Apr-12
28-Apr-12
29-Apr-12
30-Apr-12
01-May-12
02-May-12

0
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-Apr-12
02-Apr-12
03-Apr-12
04-Apr-12
05-Apr-12
06-Apr-12
07-Apr-12
08-Apr-12
09-Apr-12
10-Apr-12
11-Apr-12
12-Apr-12
13-Apr-12
14-Apr-12
15-Apr-12
16-Apr-12
17-Apr-12
18-Apr-12
19-Apr-12
20-Apr-12
21-Apr-12
22-Apr-12
23-Apr-12
24-Apr-12
25-Apr-12
26-Apr-12
27-Apr-12
28-Apr-12
29-Apr-12
30-Apr-12
01-May-12
02-May-12
03-May-12

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-Apr-12
02-Apr-12
03-Apr-12
04-Apr-12
05-Apr-12
06-Apr-12
07-Apr-12
08-Apr-12
09-Apr-12
10-Apr-12
11-Apr-12
12-Apr-12
13-Apr-12
14-Apr-12
15-Apr-12
16-Apr-12
17-Apr-12
18-Apr-12
19-Apr-12
20-Apr-12
21-Apr-12
22-Apr-12
23-Apr-12
24-Apr-12
25-Apr-12
26-Apr-12
27-Apr-12
28-Apr-12
29-Apr-12
30-Apr-12
01-May-12
02-May-12
03-May-12

Performance Analysis: HSDPA/HSUPA Throughput

HSDPA throughput performance remained at pre-trial levels.


1400

HSDPA Interactive Erlangs


1200

HSPA Interactive Erlangs

1200

1000

1000

800
800

600
600

400
400

200
200

HSDPA Interactive Erlangs


HSPA Interactive Erlangs

60.6

HSDPA Data Volume (Mbps)


HSUPA Data Volume (Mbytes)

50.6
5,000

40.6
4,000

30.6
3,000

20.6
2,000

10.6

0.6
1,000
0

HSDPA Data Volume Mbps


HSUPA Data Volume Mbytes

27

03.22.2012
03.23.2012
03.24.2012
03.25.2012
03.26.2012
03.27.2012
03.28.2012
03.29.2012
03.30.2012
03.31.2012
04.01.2012
04.02.2012
04.03.2012
04.04.2012
04.05.2012
04.06.2012
04.07.2012
04.08.2012
04.09.2012
04.10.2012
04.11.2012
04.12.2012
04.13.2012
04.14.2012
04.15.2012
04.16.2012
04.17.2012
04.18.2012
04.19.2012
04.20.2012
04.21.2012
04.22.2012
04.23.2012
04.24.2012
04.25.2012
04.26.2012
04.27.2012
04.28.2012
04.29.2012
04.30.2012
05.01.2012
05.02.2012
05.03.2012

98

97

95

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 (%)

28

0.1

Millions

99

0.1

Performance Analysis: RRC Performance


RRC Performance (Aggregated Performance - 30 cells)
0.2

100
0.1

0.1

0.1

0.0

96
0.0

0.0

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-Apr-12
02-Apr-12
03-Apr-12
04-Apr-12
05-Apr-12
06-Apr-12
07-Apr-12
08-Apr-12
09-Apr-12
10-Apr-12
11-Apr-12
12-Apr-12
13-Apr-12
14-Apr-12
15-Apr-12
16-Apr-12
17-Apr-12
18-Apr-12
19-Apr-12
20-Apr-12
21-Apr-12
22-Apr-12
23-Apr-12
24-Apr-12
25-Apr-12
26-Apr-12
27-Apr-12
28-Apr-12
29-Apr-12
30-Apr-12
01-May-12
02-May-12

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-Apr-12
02-Apr-12
03-Apr-12
04-Apr-12
05-Apr-12
06-Apr-12
07-Apr-12
08-Apr-12
09-Apr-12
10-Apr-12
11-Apr-12
12-Apr-12
13-Apr-12
14-Apr-12
15-Apr-12
16-Apr-12
17-Apr-12
18-Apr-12
19-Apr-12
20-Apr-12
21-Apr-12
22-Apr-12
23-Apr-12
24-Apr-12
25-Apr-12
26-Apr-12
27-Apr-12
28-Apr-12
29-Apr-12
30-Apr-12
01-May-12
02-May-12

Performance Analysis: Voice MPD

Voice MPD performance has not impacted due to the activation of FDPCH
feature.
1000
900
800
700
600
500
400
300
200
100
0

Voice MPD
20000
18000
16000
14000
12000
10000
8000
6000
4000
2000
0

NOK RAB Attempts CS Voice

29

VOICE_MPD

60

RAB_ACT_FAIL_CS_VOICE Failures

50

40

30

20

10

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

97.0

03.22.2012
03.23.2012
03.24.2012
03.25.2012
03.26.2012
03.27.2012
03.28.2012
03.29.2012
03.30.2012
03.31.2012
04.01.2012
04.02.2012
04.03.2012
04.04.2012
04.05.2012
04.06.2012
04.07.2012
04.08.2012
04.09.2012
04.10.2012
04.11.2012
04.12.2012
04.13.2012
04.14.2012
04.15.2012
04.16.2012
04.17.2012
04.18.2012
04.19.2012
04.20.2012
04.21.2012
04.22.2012
04.23.2012
04.24.2012
04.25.2012
04.26.2012
04.27.2012
04.28.2012
04.29.2012
04.30.2012
05.01.2012
05.02.2012
05.03.2012

100.0

99.0
0.6

98.5
0.4

98.0
0.3

0.2

97.5
0.1

RNC_193b SHO Update Attempts RT (#)


RNC_194b SHO Update Attempts NRT (#)

RNC_153b SHO Success Rate RT (%)


RNC_191b SHO Success Rate NRT (%)

30
0.0

Millions

Performance Analysis: Soft Handover


Soft Handover Performance (Aggregated Performance - 30 cells)
0.9

0.8

99.5
0.7

0.5

70.0

31

RNC_298e ISHO Attempts RT (#)


RNC_299d ISHO Attempts NRT (#)

RNC_300g ISHO Success Rate RT (%)


RNC_301e ISHO Success Rate NRT (%)

05.03.2012

05.02.2012

05.01.2012

04.30.2012

04.29.2012

04.28.2012

04.27.2012

04.26.2012

04.25.2012

04.24.2012

04.23.2012

04.22.2012

04.21.2012

04.20.2012

04.19.2012

04.18.2012

04.17.2012

04.16.2012

04.15.2012

04.14.2012

04.13.2012

04.12.2012

04.11.2012

04.10.2012

04.09.2012

04.08.2012

04.07.2012

04.06.2012

04.05.2012

04.04.2012

04.03.2012

04.02.2012

04.01.2012

03.31.2012

03.30.2012

03.29.2012

03.28.2012

03.27.2012

03.26.2012

03.25.2012

03.24.2012

03.23.2012

03.22.2012

90.0
3.5

3.0

85.0
2.5

2.0

80.0
1.5

75.0

1.0

0.5

0.0

Thousands

100.0

Performance Analysis: ISHO


ISHO Performance (Aggregated Performance - 30 cells)
5.0

4.5

95.0

4.0

Field Testing: Trial Sites


The following sites on RNC37 were identified as candidates for the trial.
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

Field testing was performed to verify F-DPCH feature functionality.


Drive Route

32

Field Testing: Feature Verification Methodology


Test Case

Test Case Description

Test Procedure
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.
Test Case 1 Fractional DPCH Setup Verification Test
Step 3: Ensure that there were no call setup failures and call drops observed during the 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
Fractional DPCH Coverage
Test Case 2
removed.
Dependency Verification Test
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.
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.
Fractional DPCH Mobility
Test Case 3 Verification Test (F-DPCH cell -> F- 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
DPCH cell)
Step 5: Ensure that no call setup failures, call drops and SHO failures observed during the test.
Step 1: Establish a HSDPA Data Call using Rel-7 or later release UE.
Fractional DPCH Mobility
Step 2: Ensure that F-DPCH information is observed in RB Reconfiguration Message.
Test Case 4 Verification Test (F-DPCH cell ->
Step 3: Move UE to another cell so that Soft Handover is achieved.
non F-DPCH cell)
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.
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.
Test Case 5 Fractional DPCH Mobility
Verification Test (non F-DPCH cell - Step 4: Ensure that RB Reconfiguration Message contains FDPCH information is received after
Active Set Update Message (RL deletion).
> F-DPCH cell)
Step 5: Ensure that no call setup failures, call drops and SHO failures observed during the test.

33

Field Testing: Phase 1 Analysis


1. F-DPCH Setup Verification Test
F-DPCH Enabled Cell

SC18

R8 UE

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.

34

Field Testing: Phase 1 Analysis


2. FDPCH Coverage Dependency Verification Test
F-DPCH Enabled Cell

SC18

R8 UE
UE Moving towards cell edge

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.
35

Field Testing: Phase 1 Analysis


3. Fractional DPCH Mobility Verification Test (F-DPCH cell -> F-DPCH cell)
F-DPCH Enabled Cell

F-DPCH Enabled Cell

SC18

SC392

Mobility

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.
36

Field Testing: Phase 1 Analysis

4. Fractional DPCH Mobility Verification Test (F-DPCH cell -> Non F-DPCH cell)
F-DPCH Enabled Cells
Non F-DPCH cell

SC392
SC331

SC108

Mobility

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 nonFDPCH 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.
37

Field Testing: Phase 1 Analysis

5. Fractional DPCH Mobility Verification Test (Non F-DPCH cell -> F-DPCH cell)
Non F-DPCH Cells

F-DPCH Enabled Cells

SC392
SC400

SC331

Mobility

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.
38

Field Testing: Phase 2 Analysis


1. Fractional DPCH Setup Verification Test
F-DPCH Enabled Cell

SC18

R8 UE

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.

39

Field Testing: Phase 2 Analysis


2. FDPCH Coverage Dependency Verification Test
F-DPCH Enabled Cell

SC18

R8 UE
UE moving toward the cell edge

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.
40

Field Testing: Phase 2 Analysis


3. Fractional DPCH Mobility Verification Test (F-DPCH cell -> F-DPCH cell)
F-DPCH Enabled Cell

F-DPCH Enabled Cell

SC18

SC331

Mobility

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.

41

Field Testing: Phase 2 Analysis

4. Fractional DPCH Mobility Verification Test (F-DPCH cell -> Non F-DPCH cell)
F-DPCH Enabled Cells
Non F-DPCH cell

SC392
SC331

SC400

Mobility

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.
42

Field Testing: Phase 2 Analysis

5. Fractional DPCH Mobility Verification Test (Non F-DPCH cell -> F-DPCH cell)
Non F-DPCH Cell

F-DPCH Enabled Cell

SC256

SC331

Mobility

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.
43

Field Testing: Phase 1 and Phase 2 Summary


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 reallocated.
Field testing has revealed that softer and soft handovers were successful.
Soft handovers were successful when the source and target cells both had FDPCH enabled.
Softer handovers were successful between sectors of the same sites for
which all the cells are F-DPCH enabled

44

Field Testing: Phase 1 and Phase 2 Summary


Soft and softer handover test summary:

en
Sc

s
io
r
a

FDPCH to FDPCH
FDPCH to Non FDPCH
Non FDPCH to FDPCH

FDPCH allocation along user plane


allocation (Phase1)
Call Setup
Soft
Softer
Success
Handover
Handover

N/A

N/A

FDPCH Immediate allocation (Phase2)


Call Setup
Success

Soft
Handover

Softer
Handover

N/A
N/A

There were no call setup failures or call drops reported during field testing with
the activation of F-DPCH feature.

45

Você também pode gostar