Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Enigma 2006
V2.0
18.08.2006
Authority
Name
O2
Nokia
Patricia Rdiger
Hatem Mokhtari
Signature
2 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
Table of Contents
1
2
3 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
1
The city of Rostock is subdivided into two clusters. This report refers to the cluster in the centre of
Rostock. The second Rostock cluster includes the northern part of the city including the Baltic Sea
harbour. The O2 network in Rostock is lightly loaded and appears to be in good condition. During the
Pre and Post Drive tests all the sites were operational and no significant network issues were
encountered.
Cluster Name
Drive date
Number of Drives Conducted
Number of Planned Sites
Number of Integrated Sites
Number of OTSR Sites
Number of STSR Sites
Table 1: Cluster Information
Pre-Swap
Post Swap
TOC0506_P1 (Rostock 1)
CS and PS: 22.06.2006
CS and PS: 10.08.2006
1
1
24
24
24
24
24
24
0
0
4 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
2
EXECUTIVE SUMMARY
This report summarizes the DT performance of O2 network in Rostock (cluster 1) before
and after the Node B swap. As Rostock is subdivided into two separate clusters, this analysis
concerns only the centre of Rostock since the northern part of Rostock has yet to be swapped.
The Rostock 1 cluster demonstrates that the performance of the Nokia network exceeds that of
the previous equipment. For both CS and PS calls the post swap performance generally exceeds
the pre swap performance. However due to the lack of intervendor Iur and the fact that some of
the drive testing for this cluster was carried out in the vicinity of the cluster border there is some
impact on the performance. This is due to the rf emissions from the sites in the unswapped
cluster being experienced by the users (and drive test UEs) in the swapped cluster and causing
an increased noise environment. This effect will be experienced in all clusters where there are
boundaries between swapped and unswapped clusters. The effect is not severe in this case but
slightly adversely affects the throughput and probably contributes to some dropped calls in the
boundary region. The DL BLER performance is significantly better with the Nokia equipment and
this should provide enhanced voice quality and data throughput performance.
2.1
2.1.1
KPI Comparison
PS KPIs
PS KPIs
Attach Attempts
Attach Failures
Attach Success Rate
Attach Delivery Time <= 10 sec
PDP Context Activation Attempts
PDP Context Activation Failures
PDP Context Activation Success Rate
PDP Context Delivery Time <= 8 sec
HTTP Download Attempts
HTTP Download Failures
HTTP Download Success Rate
HTTP DL Throughput (384 kbps bearer)
PS Call Dropped
Average Active Set Size
Overall PS Session Success Rate
Pre DT
22.06.2006
Post DT
10.08.2006
304
0
100.0%
99.3%
304
0
100%
100%
304
1
99.67%
278.7
2
1.27
99.34%
273
0
100.0%
99.6%
273
0
100.0%
100.0%
273
1
99.63%
271.3
2
1.30
99.27%
Table 2: PS Comparison
2.1.2
CS KPIs
CS KPIs
Call Attempts
Call Setup Failures
Call Drops
Successful Calls
Overall Call Success
Average Active Set Size
Average Downlink BLER
Pre DT
22.06.2006
225
1
0
224
99.56%
1.24
2.27%
Table 3: CS Comparison
Post DT
10.08.2006
212
0
1
211
99.53%
1.27
0.21%
Delta
-1
1
-0.03
0.03
2.07
Delta
0
0
0.3
0
0
0
0
-0.04
-7.4
0
0.03
-0.07
5 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
2.2
2.2.1
RF Performance
EcNo Distribution
Ec/Io Distribution
80.00%
70.00%
60.00%
50.00%
40.00%
PRE Ec/Io
30.00%
POST Ec/Io
20.00%
10.00%
0.00%
-5.0 to -0.1
dB
-13.0 to 11.0 dB
-15.0 to 13.0 dB
-17.0 to 15.0 dB
-20.0 to 17.0 dB
More samples of Ec/Io in the highest range in the POST than in the PRE period !
2.2.2
Rscp Distribution
RSCP Level Distributions
35.00%
30.00%
25.00%
20.00%
PRE RSCP
15.00%
POST RSCP
10.00%
5.00%
0.00%
-60 to +20
-70 to -60
-80 to -70
-90 to -80
-100 to -90
-115 to -100
-130 to -115
RSCP Values have higher occurrence in the high ranges (dBm) under Nokia
equipment than the previous vendor. The tendency is inverse in the lower ranges.
6 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
3
KPI DETAILS
3.1.1
Pre DT KPIs
Rostock Pre DT
22.06.2006
Cluster Name:
PS KPIs
Attach Attempts
Attach Failures
Attach Success Rate
Attach Delivery Time <= 10 sec
PDP Context Activation Attempts
PDP Context Activation Failures
PDP Context Activation Success Rate
PDP Context Delivery Time <= 8 sec
HTTP Download Attempts
HTTP Download Failures
HTTP Download Success Rate
HTTP DL Throughput (384 kbps bearer)
PS Call Dropped
Average Active Set Size
Overall PS Session Success Rate
Table 4: Pre DT PS KPIs
Cluster Name:
Rostock Pre DT
22.06.2006
CS KPIs
Call Attempts
Call Setup Failures
Call Drops
Successful Calls
Overall Call Success
Average Active Set Size
Average Downlink BLER
Result
225
1
0
224
99.48%
1.24
2.27%
Result
304
0
100.00%
99.30%
304
0
100%
100%
304
1
99.67%
278.7
2
1.27
99.34%
7 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
3.1.2
Post DT KPIs
Rostock Post DT
Cluster Name:
PS KPIs
Attach Attempts
Attach Failures
Attach Success Rate
Attach Delivery Time <= 10 sec
PDP Context Activation Attempts
PDP Context Activation Failures
PDP Context Activation Success Rate
PDP Context Delivery Time <= 8 sec
HTTP Download Attempts
HTTP Download Failures
HTTP Download Success Rate
HTTP DL Throughput (384 kbps bearer)
PS Call Dropped
Average Active Set Size
Overall PS Session Success Rate
Table 6: Post DT PS KPIs
Cluster Name:
Rostock Post DT
CS KPIs
Call Attempts
Call Setup Failures
Call Drops
Successful Calls
Overall Call Success
Average Active Set Size
Average Downlink BLER
Result
212
0
1
211
99.53%
1.27
0.21%
Result
304
0
100.00%
99.30%
304
0
100%
100%
304
1
99.67%
278.7
2
1.30
99.34%
8 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
4
PLOTS
9 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
4.1
SC Dominance Plot
10 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
11 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
4.2
RSCP Plots
12 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
13 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
4.3
Ec/Io Plots
14 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
15 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
4.4
16 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
17 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
APPENDIX
5
5.1
Cluster Name:
Rostcok Post DT
PS KPIs
Attach Attempts
Attach Failures
Attach Success Rate
Attach Delivery Time <= 10 sec
PDP Context Activation Attempts
PDP Context Activation Failures
PDP Context Activation Success Rate
PDP Context Delivery Time <= 8 sec
HTTP Download Attempts
HTTP Download Failures
HTTP Download Success Rate
HTTP DL Throughput (384 kbps
bearer)
PS Call Dropped
Average Active Set Size
Overall PS Session Success Rate
Table 8: Post DT PS KPI summary
Result
304
0
100.00%
99.30%
304
0
100%
100%
304
1
99.67%
278.7
2
1.30
99.34%
Issues
Issue #1
Issue #2, #3
18 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
5.1.1
A normal Download of the predefined 700kB HTTP file consists of 715616 Bytes. According to TEMS
logfiles (Actix Post-processed) only 712931 Bytes are downloaded. The event is flagged by Transfer
Error. Before the fail occurred we see a RRCConnectionReleaseComplete. The connection is thus
terminated normally, which we can also see in the data below that Ec/Io values are quite acceptable
(blue color). As in region South, we already seen this tool error. We consider this event as void.
Normally if the HTTP Failure occurred in a highly interfered location we could say that this is a typical
radio issue. HTTP Failure can also occur when the UMTS Network area is highly loaded or a drop in
the receive power (diffraction, sudden RF loss, tunnel, etc..), which is not the case here. We can also
see that the subsequent messages are all normal. RRCConnectionRequest then Setup and setup
Complete. This issue will continue to be reported as a fault in future reports and it is expected that
future releases of TEMS may cure this problem.
19 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
20 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
5.1.2
The figure below clearly shows the rapid degradation of the rf environment. We can see that at the
time and location of the drop the Ec/No is very bad. Here the mobile is very close to the site, which
means that the DL receive power is sufficient but the increase in noise (probably due to the
interference coming from the non-swapped sites in the adjacent cluster) rapidly reduces the Ec/No.
We see also that aggregated BLER has increased to 100% on this location.
21 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
22 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
5.1.3
The figures below clearly show the degradation of the radio interference environment. This is a
repeat of the problem detailed above.
23 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
5.1.4
DL throughput reduction
As discussed previously the DL throughput is affected by the radio conditions. In the Rostock data
there are some PS sessions that appear to be affected by interference due to the missing intervendor
Iur. Although it is occurring in a irregular fashion (due to local clutter and propagation environment)
this example clearly demonstrates the cause (poor Ec/Io) and effect (reduced throughput). Referring
to plot 15, showing the throughput versus the time of call, the reduction of average throughput is clear
to see, particularly around 06:23. Plots 16 and 17 present the throughput and Ec/Io data for this time
and clearly demonstrate the correlation. Although it is not possible to pin point the source of the
interference to the unswapped sites in the north of Rostock, it is clear that this example of reduced
throughput is in the north of the Rostock cluster and in close vicinity to those unswapped sites.
Without detailed clutter and terrain information we can only assume that those areas where the
throughput is reduced have low loss radio paths in the direction of the interfers.
DL Troughput vs Time
400
350
300
200
150
100
50
0
02
:5
03 2:1
:0 2:5
03 2:2 40
:1 3:2
03 1:2 90
:2 7:7
03 2:4 10
:3 9:3
03 2:0 10
:4 0:0
03 3:0 90
:5 4:5
04 8:4 70
:0 5:6
04 7:3 20
:1 1:8
04 6:3 00
:2 0:1
04 5:2 50
:3 6:3
04 4:3 10
:4 6:5
04 4:4 50
:5 1:2
05 5:1 90
:0 6:2
05 9:4 90
:1 4:1
05 8:4 20
:2 8:9
05 7:5 40
:4 6:3
05 4:5 60
:5 1:8
06 3:5 30
:0 7:3
06 3:5 60
:1 6:5
06 3:0 40
:2 2:9
06 3:5 00
:3 4:7
06 3:5 30
:4 1:4
06 5:2 20
:5 1:4
07 4:3 40
:0 8:5
07 5:0 00
:1 9:0
07 4:0 40
:2 6:5
07 7:0 80
:3 0:4
07 6:2 00
:5 8:5
08 0:5 30
:0 2:8
08 1:2 40
:1 0:8
08 1:4 60
:2 2:9
08 0:3 80
:3 8:7
08 0:5 50
:3 4:2
9: 3
48 0
:3
50
kbps
250
Time
24 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
Plot 16: DL Throughput Degradation in the north of the Rostock 1 cluster close to the river
25 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
Plot 16: DL Throughput degradation correlated with Ec/Io (here -17 dB)
26 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
27 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
5.2
CS Calls
Cluster Name:
CS KPIs
Call Attempts
Call Setup Failures
Call Drops
Successful Calls
Overall Call Success
Average Active Set Size
Average Downlink BLER
Table 9: Post DT CS KPI summary
Rostock Post DT
10.08.2006.
Issues
Result
212
0
1
211
99.53%
1.27
0.21%
Issue #4
28 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
5.2.1
29 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
30 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
31 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
EXPLANATION OF DATA AND PLOTS
5.3
Legend
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
APPLIED OFFSETS
No OTSR->STSR Upgrades were done in this cluster, thus no offsets were applied.
32 (32)
Cluster Swap Report Rostock 1
Hatem Mokhtari
Issue: V2.0
7
This section details the test equipment used for each swap event and includes changes to equipment
between pre and post swap events.
7.1
Equipment List
Equipment Description
Pre-Swap
355677007885912
356657006119918
01150005
PNA411076369
2005100109
Post Swap
355677007885912
356657006119918
01150005
PNA411076369
2005100109
7.2
Call mix
7.2.2
PS-Call:
APN (Zugangspunkt):
Einwahlnummer:
Every download has to start with a new RRC Connection Request followed by a new
Attach and PDP Activation.
surfo2
*99#
CS-Call: