You are on page 1of 61

RG20(BSS) Pilot Report

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

1 (61)

RG20(BSS) Pilot Report

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The document has been prepared to be used by professional and properly trained
personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability
arising in connection with such hardware or software products shall be defined conclusively in
a separate agreement between Nokia Siemens Networks and the customer. However, Nokia
Siemens Networks has made all reasonable efforts to ensure that the instructions contained in
the document are adequate and free of material errors and omissions. Nokia Siemens
Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may
not be covered by the document.
Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY
LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT
This document and the product it describes are considered protected by copyrights and other
intellectual property rights according to the applicable laws.
Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2011. All rights reserved.

2 (61)

Nokia Siemens Networks

Contents

Contents

DN0757383
Issue 5-0
14/04/2011

1
1.1
1.2

Introduction ............................................................................................4
Purpose and Scope of this Document......................................................4
Achievement of Piloting Objectives ..........................................................4

2
2.1
2.2
2.3

System Piloting ......................................................................................6


Introduction ..............................................................................................6
System Stability and Service Availability..................................................9
System Performance................................................................................9

3
3.1
3.2
3.3
3.4

BSC Entity Piloting...............................................................................18


Introduction ............................................................................................19
BSC Stability and Performance..............................................................19
S15 Maintenance Packet 0.0 (S15 MP0.0) ............................................20
S15 Problem Reports Raised During Pilot .............................................20

4
4.1
4.2
4.2.1
4.3
4.3.1
4.3.2
4.4
4.5
4.6
4.7
4.7.1
4.8
4.8.1
4.8.2
4.9
4.10

BTS Entity Piloting ...............................................................................21


CX(M)8 Pilot Details ...............................................................................21
CX(M)8 Pilot Schedule & Features ........................................................22
BTS configurations .................................................................................22
CX(M)8 KPI analysis ..............................................................................22
UltraSite BTS KPIs .................................................................................23
MetroSite BTS KPIs ...............................................................................27
CX(M)8 Alarms.......................................................................................31
CX(M)8 Problem reports raised during pilot ...........................................31
EX4 Pilot Details.....................................................................................31
EX4 Pilot Schedule & Features ..............................................................32
BTS configurations .................................................................................32
EX4 KPI analysis....................................................................................33
EX4 BTS Cluster 1 KPIs.........................................................................33
EX4 BTS Cluster 2 KPIs.........................................................................37
EX4 Alarms ............................................................................................41
EX4 Problem reports raised during pilot.................................................41

5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8

New Features ........................................................................................42


OSC Piloting...........................................................................................42
Packet Abis Piloting................................................................................48
AoIP Piloting...........................................................................................55
BSC Capacity Evolution Piloting ............................................................56
Fast BSS Restart....................................................................................59
PCU Restart Handling ............................................................................59
Automatic EDAP Reallocation PCU .......................................................60
New Measurements ...............................................................................60

Conclusions..........................................................................................61

Nokia Siemens Networks

3 (61)

RG20(BSS) Pilot Report

Introduction

1.1

Purpose and Scope of this Document


This report summarizes the results and experiences of piloting activities for
RG20(BSS) release.

1.2

Achievement of Piloting Objectives


Main objective for the pilot was to ensure RG20(BSS)release readiness for world
markets. Stability and performance of both the existing and most critical new
functionality was expected to be verified during the pilot. From configuration point
of view pilot was planned to cover BSC2i, BSC3i and Flexi BSC with Talk BTS,
MetroSite BTS, UltraSite BTS and Flexi EDGE BTSs.
Minimum one month live time was required for RG20(BSS)SW and HW. In
addition to system performance the readiness of delivery pipeline and related
product services were planned to be ensured during the pilot.
The general pilot objectives were met. Release proved to be stabile in live
network and one month live time requirement was met for RG20(BSS) SW and
HW.
All required configurations were covered in the pilots. Performance of the release
proved to be at least on the same level as the previous release. Normal delivery
pipeline was used during the pilot.
In the pilot planning phase a list of requirements for the pilot network were
defined (features and configurations). These requirements were fulfilled in the
pilots.
In planning phase two pilot customers were selected to ensure that enough
configuration variants were covered in the pilots and if one pilot would face
schedule problems and could not be completed in time the other pilot would be
enough for ensuring the readiness for commercial release.

4 (61)

Nokia Siemens Networks

Introduction

In addition, there was third pilot (pre-pilot) that was conducted in advance
of the other two main pilots to get early experiences on OSC performance.
In planning phase the feature coverage of the pilots were agreed to cover
the following new RG20(BSS)features:
BSS21309
BSS30385
BSS30380
BSS21454
BSS21440
BSS21445
BSS21439
BSS20045
BSS21232
BSS21362
BSS21368
BSS101583
BSS101584
BSS101585
BSS101586

OSC Half Rate with SAIC MS


Circuit Switched Dynamic Abis Pool
A over IP, Transcoder in MGW
Packet Abis over IP/Ethernet
Packet Abis over TDM
Packet Abis Congestion reaction
Packet Abis Sync. ToP IEEE1588v2
PCU Restart Handling
Automatic EDAP Reallocation in PCU
Fast BSS Restart
Flexi BSC Capacity Evolution
Precise RX Level Measurement
Precise Timing Advance Measurement
Precise Power Level Measurement
Adjacent Cell RX Level Measurement

The combination of the three pilots covered these required features. The
expected gain and impact of these features was verified in live customer
environment as planned. Live network verification was completed as
planned for the old functionality and selected new functionality
The piloting was expected to take maximum three months, but it took even
few weeks longer to get all major issues solved and verified properly.
Commercial S15 MP0.0 was build in the end of the project including all the
corrections from pre-MPs. S15 MP0.0 was then piloted in the last week of
the pilot period in four live BSCs.
The outcome of RG20(BSS) piloting was good in general. Stability and
KPIs of release was good for the basic functionality and also for new
features piloted.
OSC and Packet Abis features fulfilled the targets. The average OSC traffic
was around 15% from total traffic with 50% average SAIC penetration. With
most active OSC cells the carried OSC traffic share was up to 32%.
Significant bandwidth savings were achieved with Packet Abis compared to
the allocated legacy Abis mapping bandwidth. Savings of 60% were
achieved at the TDM sites and 50% at the Ethernet sites were obtained.
The key exception was AoIP (Transcoder in MGW), which requires further
investigation and network verification before the commercial launch. In
addition, the Packet Abis Congestion reaction function requires an
enhancement in order to improve the feature operation.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

5 (61)

RG20(BSS) Pilot Report

System Piloting
RG20(BSS) system pilot includes

BSC: S15 SW

BTS: EX4 SW for Flexi EDGE BTS and CX(M)8 SW for Ultra/MetroSite

In addition there is set of new RG20(BSS) SW/HW features included as listed in


the next section.
In this chapter the pilot results are dealt from RG20(BSS) point of view, more
precisely with S15 and EX4/CX8 combination excluding new features. New
RG20(BSS) features and entity level analysis is done in the dedicated chapters.

2.1

Introduction
The following table summarise three pilots done for RG20(BSS). Customer
names are not mentioned due to confidentiality reasons.

Customer

Type of Activity

Schedule of
Activity

Customer A

Pre-pilot

Live network

- Focus in OSC feature

29.11- 9.12.2010

Pilot

Live network

- Focus in release

5.1 - 13.4.2011

Pilot

Live network

- Focus in release and major features

10.1 - 13.4.2011

Customer B

Customer C

6 (61)

Nokia Siemens Networks

System Piloting

Pilots with Customer B and C were system level pilots fulfilling system pilot
requirements, whereas pilot with Customer A was limited pre-pilot with
focus in OSC only. The results of Customer A pilot are summarised in OSC
chapter.
The focus in Customer B pilot was in basic release with legacy features and
interfaces. From new RG20(BSS) features only new measurement types
(BSS101583-101586) were piloted.
Customer C pilot included basic release and a subset of new features
introduced in RG20(BSS).
The following table summarise pilot configuration and features in system
pilots done with Customer B and Customer C
Customer B
BSC1
BSC2
BSC3

BSC type
BSC3i 660
BSC3i 2000
FlexiBSC

FlexiBTS
10
63
82
155

UltraSite
52
135
75
262

MetroSite
1
6
40
47

TalkBTS
0
0
0
0

Total BCF
63
204
197
464

Total TRX
490
1166
1619
3275

Area
Rural Area
Rural Area
Urban Area

Customer C
BSC1
BSC2
BSC3
BSC4

BSC type
Flexi BSC
BSC3i 2000
Flexi BSC
BSC2i

FlexiBTS
19 (16)*
29 (29)*
20
8 (7)*
76

UltraSite
58 (5)*
60
98
28 (24)*
244

MetroSite
29 (5)*
31
39
9 (9)*
108

TalkBTS
6
11
12
5
34

Total BCF
112 (26)*
131 (29)*
169
50 (41)*
462 (96)*

Total TRX
902
1081
1276
392
3651

Area
Urban
Urban
Urban
Urban

FlexiBTS
231

UltraSite
506

MetroSite
155

TalkBTS
34

Total BCF
926

Total TRX
6926

Total

In Customer B pilot, all BTSs were upgraded to RG20 SW level. In


Customer C pilot, a part of BTSs were upgraded to RG20 level, and others
were left running with original RG10 SW level. The amount of BTSs
upgraded to RG20 level are marked with *) in the previous table.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

7 (61)

RG20(BSS) Pilot Report

In the following table the new RG20(BSS) features are listed per pilot:

Feature ID
BSS21309
BSS30385
BSS30380
BSS21454
BSS21440
BSS21445
BSS21439
BSS20045
BSS21232
BSS21362
BSS21368
BSS101583
BSS101584
BSS101585
BSS101586

Feature Name
OSC Half Rate with SAIC MS
Circuit Switched Dynamic Abis Pool
A over IP, Transcoder in MGW
Packet Abis over IP/Ethernet
Packet Abis over TDM
Packet Abis Congestion reaction
Packet Abis Sync. ToP IEEE1588v2
PCU Restart Handling
Automatic EDAP Reallocation in PCU
Fast BSS Restart
Flexi BSC Capacity Evolution
Precise RX Level Measurement
Precise Timing Advance Measurement
Precise Power Level Measurement
Adjacent Cell RX Level Measurement

Customer A
x
x

Customer B

Customer C
x
x
x
x
x
x
x
x
x
x
x

x
x
x
x

Main legacy RG10 features used by customers were:

Customer B: EGPRS, BB hopping

Customer C: AMR, EGPRS, BB hopping

RG20(BSS) SW used in pilots:


Customer B:

BSC: Pre_MP 0.01, Pre_MP 0.05

Flexi EDGE BTS: EX4.0 BL97, BL110

Ultra/MetroSite BTS: CX(M)8 Pre12

Customer C:

BSC: Pre_MP 0.01 - Pre_MP 0.07, MP0.0 (commercial SW)

Flexi EDGE BTS: EX4.0 BL97, BL107, BL110, BL114 (commercial


SW)

Ultra/MetroSite BTS: CX(M)8 Pre12, Pre13

Core Network SW levels used in pilot

Customer B: MSS - MEN971P1, MGW - U4N976P2

Customer C: MSS - MEGU9200, MGW - U4GUA400

Details of Customer A pilot can found from OSC feature pilot chapter.

8 (61)

Nokia Siemens Networks

System Piloting

2.2

System Stability and Service Availability


All seven RG20(BSS) pilot clusters have worked with good stability for
whole pilot period.
There were couple of incidents affecting CS and PS traffic. In both cases
the impact was temporal and occurred only in the limited area of pilot. Both
issues were fixed and the required corrections included in MP0.0.

2.3

System Performance
System Performance was monitored and analysed by using network KPIs
(Key Performance Indicators). KPIs were derived from BSC counter data
separately for each pilot BSC by using NSN KPI Reporter tool.
RG20(BSS) KPIs were compared to KPIs from the time before RG20(BSS)
upgrade to detect any changes in the performance. KPI analysis included
173 KPIs in total and was done daily basis over pilot period.
RG20(BSS)performance was in good level over the whole pilot period.
There were a few issues in the beginning which caused some deviation in
certain KPIs, but where then fixed in the course of pilot.
In addition pilot customers monitored the pilot clusters with their own
network maintenance tools and methods.
It is worth to mention that there was no risk of SW fallback in any stage of
pilots due to stability or performance.
The most essential KPIs are presented in the following pages. To save
space and readers time, the KPIs from two central clusters are only
presented here (note that all clusters have same trend anyway). The
selected BSCs are BSC2 (BSC3i 2000) from Customer B and BSC1
(FlexiBSC) from Customer C. The scales are hidden due to confidentially
reasons.
First red marker indicates when BSC SW was upgrade to RG20(BSS) level
and second for BTS SW respectively. Third marker indicates when MP0.0
was taken in use with Customer C.
As a conclusion, the KPIs have no constant deviation; only normal
seasonal variations can be seen.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

9 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

trf_202/Average CS Traffic (Erl)

Figure 1 CS Traffic Customer B

trf_202/Average CS Traffic (Erl)

Figure 2 CS Traffic Customer C

10 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

System Piloting

cssr_3b/CSSR, voice

Figure 3 Call Setup Success Rate Customer B

cssr_3b/CSSR, voice

Figure 4 Call Setup Success Rate Customer C

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

11 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

sdr_1a/SDCCH Drop rate

Figure 5 SDCCH Drop Rate Customer B

sdr_1a/SDCCH Drop rate

Figure 6 SDCCH Drop Rate Customer C

12 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

System Piloting

dcr_3i/TCH drop call ratio, before re-establisment

Figure 7 TCH Drop Call Rate Customer B

dcr_3i/TCH drop call ratio, before re-establisment

Figure 8 TCH Drop Call Rate Customer C

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

13 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

blck_8i/TCH call blocking

Figure 9 TCH Call Blocking Customer B

blck_8i/TCH call blocking

Figure 10 TCH Call Blocking Customer C

14 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

System Piloting

hsr_6a/BSC controlled outgoing TCH-TCH HO success


ratio

Figure 11 BSC Controlled Hanover Success Rate Customer B

hsr_6a/BSC controlled outgoing TCH-TCH HO success


ratio

Figure 12 BSC Controlled Hanover Success Rate Customer C

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

15 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 13 GPRS/EGPRS Overall TBF Success Rate Customer B

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 14 GPRS/EGPRS Overall TBF Success Rate Customer C

16 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
08.01.2 011
12.01.2 011
16.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

System Piloting

trf_215a/EGPRS DL payload data

Figure 15 DL EGPRS Payload Customer B

trf_215a/EGPRS DL payload data

Figure 16 DL EGPRS Payload Customer C

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

17 (61)

RG20(BSS) Pilot Report

BSC Entity Piloting


This chapter describes RG20(BSS) BSC entity level pilot with basic S15
SW. S15 SW new feature piloting is described in Chapter 4.
The following picture shows the principle of BSC SW piloting:

Figure 17 BSC SW pilot phases

18 (61)

Nokia Siemens Networks

BSC Entity Piloting

3.1

Introduction
In RG20(BSS) pilot, all BSCs were upgraded and running with S15 SW
from one to three weeks before new RG20 feature activation started.
Customer A had one pilot BSC running with S15 pre-pilot SW. Customer B
and C had all pilot BSCs running with S15 pilot SW (S15 1.25-0).
In the course of the piloting, there were seven S15 SW pre-maintenance
packets (S15 Pre_MP0.01 PRE_MP0.07) published and piloted.
Pre_MPs included corrections for the faults found during the piloting and
also some other improvements.

3.2

BSC Stability and Performance


Alarms, computer logs and performance were monitored daily throughout
S15 pilot. The results during basic S15 SW pilot period were good.
Customer A:
After S15 upgrade, there were no new alarms, no alarming computer logs,
no difference with basic performance compared to S14 SW.
Even there was early pre-pilot S15 SW used, there were no major issues
with basic SW stability or performance.
Customer B and C:
With S15 pilot SW the situation was the same - no major alarms, no
alarming log writings. Also basic performance stayed at least in the same
level compared to original S14 SW baseline.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

19 (61)

RG20(BSS) Pilot Report

3.3

S15 Maintenance Packet 0.0 (S15 MP0.0)


S15 MP0.0 was published for piloting on 4th of April. The MP0.0 includes all
the corrections from Pre_MPs and some additional corrections and
changes. S15 P8 level SW is S15 1.25-0 SW package + S15 MP0.0.
The MP0.0 was installed in customer C pilot BSC 4 (BSC2i) on 6-7.April
night and on the following night it was installed in three other pilot BSCs.
Installation went without any notable problems. After the MP0.0 installation
no changes were observed in BSC stability or performance.
The MP0.0 SW ran in live network (Customer C 4 pilot BSC) one week
without problems before S15 general availability.

3.4

S15 Problem Reports Raised During Pilot


All open S15 product faults found during piloting are listed in S15 1.25-0
Open Problem Reports document.

20 (61)

Nokia Siemens Networks

BTS Entity Piloting

BTS Entity Piloting


The Piloting of BTS software in a live network is a mandatory requirement
before the commercial release of a new version of software by Nokia
Siemens Networks.
The pilots for UltraSite CX8 BTS, MetroSite CXM8 BTS and Flexi EDGE
BTS software were carried out as part of the overall RG20(BSS) software
pilot activities.
The results from the pilot demonstrate comparable performance and
functionality as compared with the baseline and therefore Nokia Siemens
Networks concludes that the software fully meets the P8 criteria and
recommends full deployment to live customer networks.
RG20(BSS) BTS SW was used in both Customer B and C pilots.
RG20(BSS) BTS SW pilot analysis in this chapter is based on the results
achieved from Customer C.
Main Features Active in pilot clusters:
AMR FR & HR
(E)GPRS
Baseband Hopping

4.1

CX(M)8 Pilot Details


The pilot cluster comprised 24 UltraSite BTS and 9 MetroSite BTS
connected to a BSC2i.
During the pilot, daily analysis of BTS active alarms, alarm history and KPIs
was performed to verify correct operation of the BTS software updates.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

21 (61)

RG20(BSS) Pilot Report

4.2

CX(M)8 Pilot Schedule & Features


Schedule

20th Dec 2010 baseline CX(M)7 MP3.0

13th Jan 2011 CX(M)8 Pre1 activation

17th Jan 2011 S15 upgrade and activation

27th Jan 2011 CX(M)8 Pre2 activation

Features

4.2.1

No new features tested

BTS configurations
A variety of BTS configurations were used in order to increase the test
coverage. Typical configurations were:

4.3

Dual band E-GSM / GSM1800

2 TRX Omni up to 12 TRX 5 Sector

EDGE only hardware

EDGE + Non EDGE hardware in the same configuration

RTC and Dual Duplexer is the same configuration

CX(M)8 KPI analysis


The CX(M)8 pilot was conducted with concurrent activities such as RG20(BSS) and
Flexi EDGE EX4 BTS software validation. This report will only highlight activities that
were related to CX(M)8 activities.
The KPIs were monitored from the baseline and throughout the pilot period. The
example KPIs shown here are taken from the more detailed KPI reports.

22 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

4.3.1 UltraSite BTS KPIs


trf_202/Average CS Traffic (Erl)

Figure 18 CS Traffic

cssr_3b/CSSR, voice

Figure 19 Call Setup Success Rate

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

23 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

sdr_1a/SDCCH Drop rate

Figure 20 SDCCH Drop Rate

dcr_3i/TCH drop call ratio, before re-establisment

Figure 21 TCH Call Drop Rate

24 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

blck_8i/TCH call blocking

Figure 22 TCH Call Blocking

hsr_6a/BSC controlled outgoing TCH-TCH HO success


ratio

Figure 23 BSC Controlled Hanover Success Rate

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

25 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 24 GPRS/EGPRS Overall TBF Success Rate

trf_215a/EGPRS DL payload data

Figure 25 DL EGPRS Payload

26 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

4.3.2 MetroSite BTS KPIs


trf_202/Average CS Traffic (Erl)

Figure 26 CS Traffic

cssr_3b/CSSR, voice

Figure 27 Call Setup Success Rate

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

27 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

sdr_1a/SDCCH Drop rate

Figure 28 SDCCH Drop Rate

dcr_3i/TCH drop call ratio, before re-establisment

Figure 29 TCH Call Drop Rate

28 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

blck_8i/TCH call blocking

Figure 30 TCH Call Blocking

hsr_6a/BSC controlled outgoing TCH-TCH HO success


ratio

Figure 31 BSC Controlled Hanover Success Rate

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

29 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 32 GPRS/EGPRS Overall TBF Success Rate

trf_215a/EGPRS DL payload data

Figure 33 DL EGPRS Payload

30 (61)

Nokia Siemens Networks

BTS Entity Piloting

4.4

CX(M)8 Alarms
Active alarms and alarm histories were collected in the pilot cluster on a daily
basis. All BTS generated alarms were checked to see whether they are genuine
and if they were as a result of the piloted feature
All observed alarms during the pilot period were checked against the baseline
period. There were no other alarms seen as a result of the activation of the new
BTS SW.

4.5

CX(M)8 Problem reports raised during pilot


There were no problems raised against CX(M)8 SW during the course of the
pilot.

4.6

EX4 Pilot Details


EX4 pilot was done in the three clusters are follows:

Cluster 1 / BSC2: 29 BCFs in urban areas

Cluster 2 / BSC1: 16 BCFs in urban areas

Cluster 4 / BSC3: 7 BCFs in urban areas

During the pilot, daily analysis of BTS active alarms, alarm history and KPIs
was performed to verify correct operation of the BTS software.
EP3 MP3.2 SW was used as comparison baseline for the analysis (i.e.
existing BTS SW before pilot).

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

31 (61)

RG20(BSS) Pilot Report

4.7

EX4 Pilot Schedule & Features


Schedule

10th Jan 2011 EX4 Pre1 SW activation in cluster 1

13th Jan 2011 EX4 Pre1 SW activation in cluster 3

17th Jan 2011 EX4 Pre1 SW activation in cluster 2

1st Feb 2011 EX4 Pre2 SW activation in cluster 2 and 3

3rd Feb 2011 EX4 Pre2 SW activation in cluster 1

22nd Feb 2011 EX4 Pre3 SW activation in cluster 1

24th Feb 2011 EX4 Pre3 SW activation in cluster 2 and 3

Features:
The following new features were active in the part of sites (See more details in
OSC and Packet Abis feature pilot chapters):

4.7.1

BSS21309, OSC Half Rate with SAIC MS

BSS21454, Packet Abis over Ethernet feature

BSS21440, Packet Abis over TDM feature

BTS configurations
A variety of BTS configurations were used in order to increase the test
coverage. Typical configurations were:

32 (61)

From 4 TRX omni up to 18 TRX configurations (6+6+6) with System


Extension Module (ESEA)

Flexi EDGE BTS Dual Duplexer Module (ERxA) and Flexi EDGE
Remote Tune Combiner (ECxA) Module with System Extension
Module (ESEA)

Both 900 MHz and 1800 MHz Flexi EDGE Dual TRX Modules
(EVxx)

Nokia Siemens Networks

BTS Entity Piloting

4.8

EX4 KPI analysis


KPIs were monitored throughout the pilot period. KPIs remained at the same level
than during baseline period with EX4 SW. The following chapters show the main
KPIs for two biggest EX4 BTS clusters 1 and 2.

4.8.1

EX4 BTS Cluster 1 KPIs

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

trf_202/Average CS Traffic (Erl)

Figure 34 CS Traffic

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

33 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

cssr_3b/CSSR, voice

Figure 35 Call Setup Success Rate

sdr_1a/SDCCH Drop rate

Figure 36 SDCCH Drop Rate

34 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

dcr_3i/TCH drop call ratio, before re-establisment

Figure 37 TCH Call Drop Rate

blck_8i/TCH call blocking

Figure 38 TCH Call Blocking

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

35 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

hsr_6a/BSC controlled outgoing TCH-TCH HO success


ratio

Figure 39 BSC Controlled Hanover Success Rate

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 40 GPRS/EGPRS Overall TBF Success Rate

36 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

trf_215a/EGPRS DL payload data

Figure 41 DL EGPRS Payload

4.8.2

DN0757383

Issue 5-0

14/04/2011

EX4 BTS Cluster 2 KPIs

trf_202/Average CS Traffic (Erl)

Figure 42 CS Traffic

Nokia Siemens Networks

37 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

cssr_3b/CSSR, voice

Figure 43 Call Setup Success Rate

sdr_1a/SDCCH Drop rate

Figure 44 SDCCH Drop Rate

38 (61)

Nokia Siemens Networks

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

BTS Entity Piloting

dcr_3i/TCH drop call ratio, before re-establisment

Figure 45 TCH Call Drop Rate

blck_8i/TCH call blocking

Figure 46 TCH Call Blocking

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

39 (61)

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

RG20(BSS) Pilot Report

hsr_6a/BSC controlled outgoing TCH-TCH HO success


ratio

Figure 47 BSC Controlled Hanover Success Rate

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 48 GPRS/EGPRS Overall TBF Success Rate

40 (61)

Nokia Siemens Networks

BTS Entity Piloting

20.12.2 010
24.12.2 010
28.12.2 010
01.01.2 011
05.01.2 011
09.01.2 011
13.01.2 011
17.01.2 011
21.01.2 011
25.01.2 011
29.01.2 011
02.02.2 011
06.02.2 011
10.02.2 011
14.02.2 011
18.02.2 011
22.02.2 011
26.02.2 011
02.03.2 011
06.03.2 011
10.03.2 011
14.03.2 011
18.03.2 011
22.03.2 011
26.03.2 011
30.03.2 011
03.04.2 011
07.04.2 011
11.04.2 011

trf_215a/EGPRS DL payload data

Figure 49 DL EGPRS Payload

4.9

EX4 Alarms
No unexpected alarms were seen during the pilot.

4.10

EX4 Problem reports raised during pilot


All the product faults found during piloting are listed and regularly updated in List
of Generic Failures document: LGF-2GBTSf-2011-w15.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

41 (61)

RG20(BSS) Pilot Report

New Features
This chapter presents results of new features piloted in RG20(BSS) system
pilot.

5.1

OSC Piloting
The objective for the first pilot was to verify OSC in live network. The main
target was to get first experiences from real live environment and start the
parameter optimisation study. First OSC pilot was conducted with early
RG20(BSS) SW which was not as extensively tested as normal by R&D.
Therefore the assumption was that there could be some faults in
functionality.
Performance results of the first OSC pre-pilot were encouraging and mostly
in line with the expectations, although there were functional faults found
affecting the results occasionally.
Faults found from the first OSC pilot were fixed in course of second OSC
pilot. The parameter optimisation was completed providing good
understanding on OSC dynamics.

42 (61)

Nokia Siemens Networks

New Features

In table below are OSC configurations used in pilots:


Customer
st

1 OSC
Pilot

nd

OSC
Pilot

Cluster
/ BSC

Feature id

Feature

OSC
Cells

TRX
amount

Live duration
(days)

Cluster 1
/ BSC1

BSS21309

OSC Half Rate


with SAIC MS

20

121

13

BSS30385

CS Dynamic Abis
Pool

20

121

13

BSS21309

OSC Half Rate


with SAIC MS

22

114

80

BSS30385

CS Dynamic Abis
Pool

22

114

80

BSS21309

OSC Half Rate


with SAIC MS

44

166

56

BSS30385

CS Dynamic Abis
Pool

14

53

56

BSS21231

PacketABis over
TDM

16

50

53

BSS21231

Packet Abis over


Eth

14

63

53

Cluster 2
/ BSC2

Cluster 3
/ BSC1

OSC Half rate with SAIC MS feature was verified in pilots in three different
BSCs. OSC was used in both Circuit Switched dynamic Abis pool and
Packet Abis configurations.
Average carried traffic in 1st OSC cluster (20 cells with 121 TRXs) was 950
Erl during busy hour. OSC traffic was about 93 Erl (10% of total traffic)
while SAIC mobile penetration was about 40%. In most active OSC cells
the OSC traffic share of total traffic was over 25%. On most active OSC
cells where offered traffic was not limiting the cells carried traffic OSC
increased carried traffic up to 16%. Even with increased traffic in the cluster
the DCR improved slightly. The quality remained at the same level.
Average carried traffic in 2nd OSC cluster was about 870 Erl and OSC traffic
was 118 Erl (about 14% of total traffic).
In 3rd OSC cluster total traffic was about 530 Erl and OSC traffic 80 Erl
(about 15% of total carried traffic). The SAIC penetration was on average
50%. In the best cells, average OSC traffic share was up to 32%.
Parameter optimization was performed on the cell level to increase OSC
gain from the initial values (OSC vs OSC aggressive in the plots). Even
with aggressive parameterization the network quality remained on
acceptable level.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

43 (61)

RG20(BSS) Pilot Report

During the trial the average traffic on the best 10 cells has been increasing
slightly after OSC activation. This is due to fact that cells had initially
blocking and OSC helped to serve more traffic.

Figure 50 Busy Hour Average Traffic - Snapshot of 10 most active OSC cells

Figure 51 Blocking vs Traffic - Snapshot of 10 most active OSC cells

44 (61)

Nokia Siemens Networks

New Features

Figure 52 Drop Call Rate vs Traffic - Snapshot of 10 most active OSC cells

Figure 53 Blocking vs Traffic - Snapshot of an OSC cell with blocking

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

45 (61)

RG20(BSS) Pilot Report

Initial OSC Parameters:


In total there have been 3 parameter updates done for different parameters.
Majority of the parameter changes lead into increase in traffic.
The area where OSC is working has been seen to work until -95dBm and
RX Quality 5 (de-multiplexing).
Only parameter which leads into degradation of the quality was the demultiplexing window on 20dB, this increase the bad quality by about 10%.
The bad quality (RX Quality 5, 6, and 7) for UL did remain the same after
OSC implementation and with aggressive OSC parameters. In more detail,
the bellow graph shows that the baseline UL quality was around 8 to12 %
and with OSC activated between 10% and 13%. The quality for the
aggressive OSC has a maximum of 15%.

Figure 54 Bad UL Quality


The next figure shows that the Bad UL quality has increased slightly after
OSC implementation. Baseline quality is between 8% and 12%, with OSC
activated between 10% and 13%, and with the aggressive OSC parameters
have a bad quality of 12% to 15%. This is due to the location of the MS
which are attracted to OSC.

46 (61)

Nokia Siemens Networks

New Features

Figure 55 Bad DL Quality


From the pilots also can be concluded that the initial parameter set
attached below can be as the starting point for each project (different than
the current default values).

parameter name
DHRLIM
OMLT
ODMQT
OMLW
ODMRG
ODDQT
TDRQD
TURQD
LDDHR
LUHDR
UDDHR
UUDHR

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

value
10
-85 dBm
1
10 dB
14 dB
5
6
6
3
3
1
1

47 (61)

RG20(BSS) Pilot Report

5.2

Packet Abis Piloting


Purpose
The main objective of the Packet Abis piloting was to verify the feature set
of packet Abis, compare its performance with the previous legacy Abis
network performance level and measure the bandwidth savings achieved
with Packet Abis.
Summary
Packet Abis deploys native IP for transport of Abis information, allowing for
backhaul bandwidth savings. In legacy Abis TRX, TRXSIG and OMU
signals are allocated statically to fixed PCM timeslots. This is removed in
Packet Abis.
Packet Abis was piloted with Customer C in two clusters in the same BSC
area for more than 10 weeks. One cluster deployed Packet Abis over
Ethernet and consisted of 6 BCFs, while the other cluster consisted of 5
BCFs and implemented Packet Abis over TDM (E1).
Significant bandwidth savings were achieved with Packet Abis compared to
the allocated legacy Abis mapping bandwidth. Savings of 60% were
achieved at the TDM sites and 50% at the Ethernet sites were obtained.
Depending on the traffic profile of the single sites, the savings can be even
higher.
The voice quality was not affected by the deployment of packet Abis, nor
the subscribers perceived any increase of the speech delay. There was no
impact to the relevant BSS KPIs due to Packet Abis.
Description of field environment

Site

Configuration

# PCM TSL (legacy Abis)

BCF A

4+4+5

34

BCF B

5+5

30

BCF C

17

BCF D

6+6+4

41

BCF E

4+3+4

29

BCF F

4+4

21

Configuration of Packet Abis over Ethernet cluster

48 (61)

Nokia Siemens Networks

New Features

Max RT delay

Min RT delay

Max 1minwindow RT
average

Max 5minwindow RT
average

13,3 ms

1,2 ms

2,4 ms

1,9 ms

Round-Trip Delay Statistics of Packet Abis over Ethernet cluster

Site

Configuration

# PCM TSL (legacy Abis)

BCF G

4+2+2+3

29

BCF H

4+4+3

29

BCF I

4+4+4

31

BCF J

4+2+2+2

26

BCF K

3+3

17

Configuration of Packet Abis over TDM cluster

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

49 (61)

RG20(BSS) Pilot Report

Max RT delay

Min RT delay

Max 1minwindow RT
average

Max 5minwindow RT
average

13,2 ms

5,3 ms

6,9 ms

6,2 ms

Round-Trip Delay Statistics of Packet Abis over TDM cluster


Throughput KPIs

Busy Hour Throughput Comparison for BCF D


DL Eth Throughput

UL Eth Throughput

Legacy Abis Bandwidth

3000
2500

kbits/s

2000
1500
1000
500

Figure 56 Throughput of a Packet Abis over Ethernet site

50 (61)

Nokia Siemens Networks

15.03.11

13.03.11

11.03.11

09.03.11

07.03.11

05.03.11

03.03.11

01.03.11

27.02.11

25.02.11

23.02.11

21.02.11

19.02.11

17.02.11

15.02.11

13.02.11

11.02.11

09.02.11

07.02.11

New Features

Busy Hour Throughput Comparison for BCF J


UL HDLC Throughput

DL HDLC Throughput

Legacy Abis Bandwidth

1800
1600
1400
kbits/s

1200
1000
800
600
400
200
15.03.2011

13.03.2011

11.03.2011

09.03.2011

07.03.2011

05.03.2011

03.03.2011

01.03.2011

27.02.2011

25.02.2011

23.02.2011

21.02.2011

19.02.2011

17.02.2011

15.02.2011

13.02.2011

11.02.2011

09.02.2011

07.02.2011

Figure 57 Throughput of a Packet Abis over TDM site


The above charts show the bandwidth usage of sample packet Abis sites
for both clusters. The savings due to packet Abis compared to the legacy
Abis bandwidth are above 50%. The throughput values apply for the peak
15 minute interval of the daily busy hour and are average values for this
interval.
These charts are representative for all the sites in the clusters. The actual
chart of each site depends on the local traffic profile. Nevertheless the
savings are in the same range as the ones shown above.
BSS KPIs at the packet Abis clusters
There was no relevant impact to the BSS KPIs due to Packet Abis, nor was
there a performance difference between the Ethernet and the TDM
clusters. The following charts show representative BSS KPIs alternating for
the Ethernet and the TDM clusters.
The first marker in the charts denotes the start of the activation of the
Packet Abis feature in the cluster. The second marker shows the day of
completion of the feature activation. The third marker indicates the SW
upgrade of the BSC to the final S15 version.
Single peaks on specific days are due to maintenance or test activities.
Differing from the default BTS values for the SCTP signalling protocol, the
Selective Acknowledgement period has to be configured to 120ms.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

51 (61)

12.01.2 011
15.01.2 011
18.01.2 011
21.01.2 011
24.01.2 011
27.01.2 011
30.01.2 011
02.02.2 011
05.02.2 011
08.02.2 011
11.02.2 011
14.02.2 011
17.02.2 011
20.02.2 011
23.02.2 011
26.02.2 011
01.03.2 011
04.03.2 011
07.03.2 011
10.03.2 011
13.03.2 011
16.03.2 011
19.03.2 011
22.03.2 011
25.03.2 011
28.03.2 011
31.03.2 011
03.04.2 011
07.04.2 011
10.04.2 011

12.01.2 011
15.01.2 011
18.01.2 011
21.01.2 011
24.01.2 011
27.01.2 011
30.01.2 011
02.02.2 011
05.02.2 011
08.02.2 011
11.02.2 011
14.02.2 011
17.02.2 011
20.02.2 011
23.02.2 011
26.02.2 011
01.03.2 011
04.03.2 011
07.03.2 011
10.03.2 011
13.03.2 011
16.03.2 011
19.03.2 011
22.03.2 011
25.03.2 011
28.03.2 011
31.03.2 011
03.04.2 011
06.04.2 011
09.04.2 011

RG20(BSS) Pilot Report

cssr_3b/CSSR, voice

Figure 58 Call Setup Success Rate, Packet Abis over TDM cluster

sdr_1a/SDCCH Drop rate

Figure 59 SDCCH Drop Rate, Packet Abis over Ethernet cluster

52 (61)

Nokia Siemens Networks

12.01.2 011
15.01.2 011
18.01.2 011
21.01.2 011
24.01.2 011
27.01.2 011
30.01.2 011
02.02.2 011
05.02.2 011
08.02.2 011
11.02.2 011
14.02.2 011
17.02.2 011
20.02.2 011
23.02.2 011
26.02.2 011
01.03.2 011
04.03.2 011
07.03.2 011
10.03.2 011
13.03.2 011
16.03.2 011
19.03.2 011
22.03.2 011
25.03.2 011
28.03.2 011
31.03.2 011
03.04.2 011
07.04.2 011
10.04.2 011

12.01.2 011
15.01.2 011
18.01.2 011
21.01.2 011
24.01.2 011
27.01.2 011
30.01.2 011
02.02.2 011
05.02.2 011
08.02.2 011
11.02.2 011
14.02.2 011
17.02.2 011
20.02.2 011
23.02.2 011
26.02.2 011
01.03.2 011
04.03.2 011
07.03.2 011
10.03.2 011
13.03.2 011
16.03.2 011
19.03.2 011
22.03.2 011
25.03.2 011
28.03.2 011
31.03.2 011
03.04.2 011
06.04.2 011
09.04.2 011

New Features

During the first days of packet Abis activation, an increase of the SDCCH
drop rate was observed when SCTP bundling was deployed. In this case,
the BTS level parameter SLO (number of timeslots to spread
retransmissions) must be changed from 10 to SLO=32.

dcr_3i/TCH drop call ratio, before re-establisment

Figure 60 TCH Drop Call Ratio, Packet Abis over TDM cluster

hfr_2b/Total HO failure ratio, area level

Figure 61 Total HO Failure Ratio, Packet Abis over Ethernet cluster

DN0757383

Issue 5-0

14/04/2011

Nokia Siemens Networks

53 (61)

12.01.2 011
15.01.2 011
18.01.2 011
21.01.2 011
24.01.2 011
27.01.2 011
30.01.2 011
02.02.2 011
05.02.2 011
08.02.2 011
11.02.2 011
14.02.2 011
17.02.2 011
20.02.2 011
23.02.2 011
26.02.2 011
01.03.2 011
04.03.2 011
07.03.2 011
10.03.2 011
13.03.2 011
16.03.2 011
19.03.2 011
22.03.2 011
25.03.2 011
28.03.2 011
31.03.2 011
03.04.2 011
07.04.2 011
10.04.2 011

12.01.2 011
15.01.2 011
18.01.2 011
21.01.2 011
24.01.2 011
27.01.2 011
30.01.2 011
02.02.2 011
05.02.2 011
08.02.2 011
11.02.2 011
14.02.2 011
17.02.2 011
20.02.2 011
23.02.2 011
26.02.2 011
01.03.2 011
04.03.2 011
07.03.2 011
10.03.2 011
13.03.2 011
16.03.2 011
19.03.2 011
22.03.2 011
25.03.2 011
28.03.2 011
31.03.2 011
03.04.2 011
06.04.2 011
09.04.2 011

RG20(BSS) Pilot Report

tbf_34b/Overall TBF success rate, UL and DL together


(% )

Figure 62 Overall TBF Success Rate, Packet Abis over TDM cluster

trf_162f/DL EGPRS traffic (erl)

Figure 63 DL EGPRS Traffic, Packet Abis over Ethernet cluster

54 (61)

Nokia Siemens Networks

New Features

Packet Abis Features


The following BSS features were verified during the pilot.
BSS21445 Packet Abis Congestion reaction
During normal operation no congestion was observed. The actual traffic is
much lower than the allocated backhaul capacity due to the savings
provided by packet Abis (see above throughput charts). During specific
congestion control tests, the system behaved as expected. However an
explicit break test under non-realistic conditions caused a traffic break at
the site under test. During this test the committed information rate (CIR)
was modified online to a value far below the current traffic. This caused
an artificial congestion situation. Please refer to the S15 1.25-0 Open
Problem Reports document.
BSS21439 Packet Abis Sync. ToP IEEE1588v2
All sites belonging to the Packet Abis over Ethernet cluster deployed this
synchronization scheme. Synchronization was very stable throughout the
pilot and no alarms were observed.

5.3

AoIP Piloting
Objective of AoIP piloting was to verify its functionality in live network.
Before pilot BSC used in AoIP piloting was using S14 SW with L2 IP
topology and TDM in A interface signalling. For this kind of BSC different
kind of changes are required in order to take AoIP into use. In addition to
S15 sw upgrade and AoIP licence activation in BSC and MSS those include

DN0757383
Issue 5-0
14/04/2011

modification of configuration of BSC site switches/multilayer switches

modification of SWU-0 SWU-5 configuration in BSC

addition of SWU-6 and SWU-7 to BSC (same switches are used also
for Packet Abis)

enabling LAN device integration to BSC

changing BSC to use L3 IP topology (this is a pre-requisite for Packet


Abis and AoIP)

ETPA unit integration to BSC

MSS/MGW configuration changes

SIGTRAN needs to be taken into use in A interface

Nokia Siemens Networks

55 (61)

RG20(BSS) Pilot Report

SIGTRAN and AoIP are independent features and SIGTRAN can be used
without AoIP but not the other way around. S15 BSC supports AoIP only
for BTSs that are using packet abis. If both AoIP and legacy A are used in
parallel legacy A is used by all non-packet abis BTSs and AoIP only by
packet abis BTSs.
Following MSS BSSAP parameter needs to be checked if AoIP is wanted to
be taken into use:
8: AOIP TRANSPORT TYPE PERCENTAGE
By default this parameter is 0. This is load sharing parameter, value 0
meaning 0% of CS calls are primarily allocated to use AoIP even if BSC
and MSS both are AoIP capable. Value 100% means that all calls are
primarily allocated to use AoIP if that is supported.
Note also that the RTCP supervision of the u-plane has to be off in MGW,
since this feature is not supported by the BSC at the S15 level.
AoIP solution requires further investigation and network verification before
the commercial launch. See S15 Release Note for more information about
AoIP availability.

5.4

BSC Capacity Evolution Piloting


BSC Capacity Evolution feature functionality was verified in BSC 3
(FlexiBSc S14 HW) of Customer C.
BSC configuration was 3+1 BCSU with 1276 TRXs. New dual core CP1D-A
unit was installed for all computer units during the maintenance window.
TRX capacity pilot was done so that TRXs from BCSU-1 and BCSU-2 were
reallocated to BSCU-3 to increase traffic of BCSU-3. After reallocation
there was 697 TRXs under BCSU-3 (max. capacity is 700 TRX/BCSU with
CP1D-A PIU)

56 (61)

Nokia Siemens Networks

New Features

Below is ZTOP:D=100MS:N Service Terminal printout from computer units


with CP1D-A in high traffic period showing normal load situtaion in CPUs
BCSU-3
17:20:37

WOEX

Mem usage:

SF 1.25-0

11.04.2011

878983Kb/ 1047871Kb, header usage count 19274 / 249984

Load

History -1

-2

-3

-4

-5

Average 10s

20s

30s

60s

CPU1

23%

( 22%

0%

0%

0%

0%

22%

22%

22%

21%

CPU2

16%

( 16%

0%

0%

0%

0%

15%

15%

15%

15%

TOTAL

19%

( 19%

0%

0%

0%

0%

18%

18%

18%

18%

During same hour the BSC carried traffic 3200 Erl meaning around 1750
Erl (3200 Erl x 697/1276) in high loaded BCSU-3.
Performance and stability remained good after reallocation of TRXs. Some
of main KPIs are shown in the following figures:

11.04.2 011

07.04.2 011

03.04.2 011

30.03.2 011

26.03.2 011

22.03.2 011

18.03.2 011

14.03.2 011

10.03.2 011

06.03.2 011

02.03.2 011

29.01.2 011

25.01.2 011

21.01.2 011

17.01.2 011

13.01.2 011

09.01.2 011

05.01.2 011

01.01.2 011

28.12.2 010

24.12.2 010

20.12.2 010

trf_202/Average CS Traffic (Erl)

Figure 64 CS Traffic

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

57 (61)

58 (61)

Nokia Siemens Networks

Figure 66 TCH Drop Call Rate


07.04.2 011
11.04.2 011

11.04.2 011

30.03.2 011

26.03.2 011

22.03.2 011

18.03.2 011

14.03.2 011

10.03.2 011

06.03.2 011

02.03.2 011

29.01.2 011

25.01.2 011

21.01.2 011

17.01.2 011

13.01.2 011

09.01.2 011

05.01.2 011

01.01.2 011

28.12.2 010

24.12.2 010

20.12.2 010

07.04.2 011

dcr_3i/TCH drop call ratio, before re-establisment


03.04.2 011

Figure 65 Call Setup Success Rate

03.04.2 011

30.03.2 011

26.03.2 011

22.03.2 011

18.03.2 011

14.03.2 011

10.03.2 011

06.03.2 011

02.03.2 011

29.01.2 011

25.01.2 011

21.01.2 011

17.01.2 011

13.01.2 011

09.01.2 011

05.01.2 011

01.01.2 011

28.12.2 010

24.12.2 010

20.12.2 010

RG20(BSS) Pilot Report

cssr_3b/CSSR, voice

New Features

5.5

Fast BSS Restart


The Fast BSS Restart feature functionality was verified in BSC4 (BSC2) of
Customer C. There were used 31 BCFs (Flexi EDGE BTS and UltraSite
BTS) which SW support the feature and 14 BCFs (MetroSite BTS and
TalkFamily BTS) which SW did not support the feature in the BSC.
Fast BSS restart was triggered in the maintenance window. Total unblocking time of the 31 BCFs and their TRXs was 24 seconds.
Performance of the Fast BSS Restart was in line with the expectations.
For the reference: when system restart with RNW restart command was
given in the same BSC, 31 first BCFs restart and unblocking time was 3
minutes and 26 seconds.

5.6

PCU Restart Handling


The PCU Restart Handling feature functionality was verified in BSC4
(BSC2) of Customer C.
PCU Hot restart:
PCU Hot restart was executed successfully by giving UJR:BCSU,<bcsuid>:<pcu_id>:HOT:;-MML command for the PCU2_U (with 16 BTSs):

Alarm 3483 PCU RESTARTED was set active

PCU object was set to configuring state

PCU object was set back to WO state

Alarm 3483 PCU RESTARTED was cancelled and after that the
PCU was able to transfer data traffic

The PCU Hot restart time was 31 seconds.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

59 (61)

RG20(BSS) Pilot Report

PCU Cold restart:


PCU Cold restart was executed successfully by giving
UJR:BCSU,<bcsu_id>:<pcu_id>:COLD;-MML command for the PCU2_U
(with 16 BTSs):
1. Alarm 3483 PCU RESTARTED was set active at start of the
restart
2. PCU object was changed to restarting state
3. NSVCs and BVCIs were set to BL-SY state
4. PCU object was set to configuring state
5. PCU object, NSVCs and BVCIs were changed back to WO state
6. the 3483 PCU RESTARTED alarm was cancelled and the PCU
was able to transfer data traffic.
The PCU Cold restart time was 2 min 5 seconds.

5.7

Automatic EDAP Reallocation PCU


The automatic EDAP Reallocation features functionality was verified in
BSC4 (BSC2) of Customer C.
The feature was verified by modifying ETPCM-TSLS of the DAP by using
ESM-command.
After the command was given the PCU Hot restart was executed
successfully and the PCU was able to transfer data traffic.

5.8

New Measurements
RG20(BSS) included four new measurement features:

BSS101583

Precise RX Level Measurement (M135)

BSS101584

Precise Timing Advance Measurement (M136)

BSS101585

Precise Power Level Measurement (M137)

BSS101586

Adjacent Cell RX Level Measurement (M138)

These new measurement were piloted in customer B network in all three


BSCs. Measurement were enabled and tested as a part of customer's
acceptance testing process. Measurements were successfully activated,
collected and forwarded to NetAct.

60 (61)

Nokia Siemens Networks

Conclusions

Conclusions
RG20(BSS)release includes several new major features such as OSC,
Packet Abis, AoIP, DualCore CPUs in BSC) requiring fundamental changes
in the system design. Although the release was tested comprehensively by
Nokia Siemens Networks, there were several issues which became visible
in pilot. All major issues found in pilot were fixed and verified in the course
of the piloting. From this reason piloting took longer than earlier less
extensive releases.
Live piloting was conducted with three different customers all together in
seven different BSCs (BSC2i, BSC3i and FlexiBSC types including new
DualCore PCUs) and with around 1000 Base Stations (Flexi EDGE,
UltraSite, MetroSite and TalkFamily BTSs types). Peak traffic was up to
4500 Erl during the busy hour. Large diversity of different features and
configurations were covered in pilot providing good understanding on
RG20(BSS)release maturity.
Based on the pilot results achieved, it can be concluded that RG20(BSS)is
ready for the commercial use (excluding AoIP which requires further live
network testing).
The issues which remained open after pilot completed will be fixed as soon
as possible in the future SW Maintenance Packets.

DN0757383
Issue 5-0
14/04/2011

Nokia Siemens Networks

61 (61)

You might also like