Professional Documents
Culture Documents
VF Germanychapter 9: Technical Requirements "Network Performance & Optimisation Aspects"
VF Germanychapter 9: Technical Requirements "Network Performance & Optimisation Aspects"
VF Germanychapter 9: Technical Requirements "Network Performance & Optimisation Aspects"
VF GermanyChapter 9
Technical Requirements
“Network Performance &
Optimisation Aspects”
V 1.1
INDEX OF CHAPTER
0 INTRODUCTION......................................................................................................................................3
0 Introduction
This document contains Local Technical Requirements defined from Vodafone D2 GmbH (herein
after called VF D2) for the SGC technical assessment
In case of not compliance, SGC can propose an alternative (technical or/and commercial) proposal
that will have implication in the Total Cost of Ownership. VF D2 reserve the right to approve or not
the alternative proposal
Q&P-01 KPIs
As the new deployed UTRAN System is further developed (e.g. improved UL sensitivity, higher DL
power) in comparison to the swapped network, VF D2 expect better overall network KPIs and
improved user perceived quality.
The fulfilment of the requested Network KPIs and End-to-End KPIs has to be shown by SGC
for each cluster.
The exact figures which have to be fulfilled for the main network KPIs (PM-Counter) / E2E-KPIs
(drive test) and the “cluster-performance-acceptance-procedure” can be found in chapter 2, “Cluster
Performance Acceptance”.
SGC shall explain in detail how they ensure the fulfilment of the requested KPIs.
The parameterisation service should ensure that the already implemented “parameterisation
strategy” is transferred to the SGC-system. This should be done by setting up a common
parameterisation team, which develops a “default-parameter-setting”. SGC is responsible to
implement the aligned “default-parameter-setting”.
SGC shall explain in detail how they ensure that the “UMR6.5 parameterisation strategy” is
transferred to a most similar “SGC parameterisation strategy”.
1. The performance comparison of each cluster shall be done based on the “Cluster
Acceptance Network-KPIs” list:
Network-KPIs_Targe
ts_v3.doc
3. SGC will have one week for optimization activities after swap (common optimisation team)
to reach the absolute target values mentioned in the “Cluster Acceptance Network-KPIs”
list.
4. SGC will have three weeks for optimization activities after swap (common optimisation
team) to reach the relative target values mentioned in the “Cluster Acceptance Network-
KPIs” list. If the relative values worse than the absolute values, absolute values have to be
reached.
5. The performance comparison will be done based on one week aggregated performance
before the beginning of the swap and one week after SGC finishes the optimization
activities. The exact time period will be agreed by VF-D2 together with SGC.
6. For each cluster SGC has to deliver a formal “Network KPI acceptance-report”.
7. During the time period between the cluster is on air and is accepted, SGC shall deliver daily
performance reports for all the counter based KPIs from the “Cluster Acceptance KPIs”
until 12p.m for the previous performance day. The reports shall present cell and cluster
performance. For not fulfilling KPIs, SGC has to deliver a description of the failure cause
and the planned activities for elimination.
1. For each cluster, the E2E performance has to be verified based on the “Cluster
Acceptance E2E-KPIs” list:
RFQ UTRAN
Systemtechnik 02_04_...
2. The methodology for the end-to-end measurements is also found in the file above. For
each cluster the requested number of measurement samples has to be fulfilled.
Furthermore at least 95% of the cells in the cluster have to be covered by the drive test
route.
4. SGC will have one week after swap to perform E2E measurement.
5. SGC (and common optimisation team) will have one week after E2E measurement to
analyse the measurements (beside UE-traces, also IMSI-traces from network side should
be activated).
7. For not fulfilling KPIs, SGC has to deliver a description of the failure cause and the planed
activities for elimination.
8. In case of not fulfilling E2E-KPIs, VF-D2 can request a repetition of E2E measurements by
SGC.
The aim of Optimisation Service is to improve and maintain the overall performance of the
UMTS Network, as well as the interoperability with the existing 2G/3G Network, in order to
optimise the above listed KPIs at cluster level. Furthermore VF-D2 optimisation engineers have
to be trained in all optimisation tasks.
Reporting daily all of the Optimisation Services performed by SGC and the
resulting effect on the UTRAN performance, including but not limited to an
analysis of each drive test and an analysis of each site in relation to its
neighbouring sites. The reporting actions shall be performed in accordance to
VF-D2 Requirements.
SGC shall use VF-D2 approved radio propagation planning tool to simulate
change proposals before presenting these change proposals to VF-D2.
SGC shall identify the problematic areas in the UMTS network, quantify its
impact on the local network performance and propose changes that can lead to
a solution, or at least, to a significant improvement in quality and/ or
performance. The optimisation actions must target the performance of the 3G
Network itself and the interoperability with the 2G/3G existing Network, as well.
Due to higher DL-power, retuning of the neighbour relations (intra- and inter
frequency, inter-system) will be necessary. SGC shall identify and add missing
neighbour relations. Also detection and deletion of unnecessary neighbour
relations is requested. Automatic procedure (RNC measurements) is
recommended.
1. VF-D2 has the right to participate in the Optimisation Services and to provide
suggestions or comments to SGC, which SGC must take into account in performing the
Optimization Services. If SGC does not or proposes not to take into account VF-D2
suggestions and comments, SGC must prove to VF-D2 that the performance objectives
cannot be met considering VF-D2 suggestions.
2. VF-D2 has the right to specify and approve the Tools, Equipment, Data formats and
Methods, involved in the Optimisation Services.
3. VF-D2 has the right to specify and approve Performance indicators or any kind of
statistical analysis to be used for evaluating the performance of the UMTS Network,
interoperability 3G-2G and 3G-3G existing network and efficiency of the optimisation
actions. Any performance indicator, statistical expression or method proposed by SGC
must be approved by VGC.
4. Drive routes must be agreed between SGC and VF-D2 before drive test performing
5. All the raw and processed data obtained during drive or walk testing, or any other sort
of measurement actions, shall be owned by VF-D2.
6. SGC shall be able to replace all sorts of faulty equipment and tools to be used during
the overall optimisation process, in a period short enough to avoid any negative impact
in the Ongoing Optimisation Services schedule.
1. SGC has to record the actual parameter setting of the swapped network and to
understand the strategy behind them.
2. SGC has to develop a “VF-D2 specific default parameter set” which shows similar
behaviour to the actual parameter set (deviations have to be pointed out clearly).
3. SGC has to present the feature behaviour using the “VF-D2 specific default parameter
set” to VF-D2 beforehand to the swap, special interest on:
HSXPA Mobility
Intrafrequency (HSXPA Cell Change, HSXPA Inward-/Outward-Mobility)
Interfrequency (IF HO for HSXPA with Compressed Mode, Blind IF HO)
Inter-RAT (CTS to R99 ?/CM for HS? / Cell Change Order)
2nd frequency allocation at HS call setup (UE differentiation)
HSXPA Power/Code allocation strategy
Dynamic Code Allocation
Power Reservation for HSXPA
CQI adjustment/BLER consideration in NodeB
HSXPA Scheduler (Proportional Fair Scheduler, … etc.)
HSXPA Admission/Congestion Control
# HSXPA user per cell
Interworking with R99 traffic
dependencies considering UL R99 Bearer
HSXPA RABs
Different UL R99 Bearer for HSXPA (initial rate/ bit rate adaptation)
Multi-RABs / State Model
Channel Model
HSXPA Flow Conrtol on Iub
RLC PDU size
Buffer/queue management
Congestion control on Iub
R99
Mobility
Cell specific Handover
4. “VF-D2 specific default parameter set” must be agreed between SGC and VF-D2
before swap starts.
5. SGC has to implement “VF-D2 specific default parameter set” plus cell specific
settings, such as all neighbour relations (intra- and inter frequency, inter-system), #
HSDSCH-Codes, power settings, …
6. VF-D2 has the right to provide suggestions for changes of the “VF-D2 specific default
parameter set”. If SGC does not or proposes not to take into account VF-D2
suggestions and comments, SGC must prove to VF-D2 that the performance objectives
cannot be met considering VF-D2 suggestions.