Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Hi all
Please could you provide your input to the following drive test KPI's that will be
measured during initial tuning.
The network will be using P6 and there will be in total 20 sites. Some areas will have
only 1/2 sites providing coverage.
There will be 10 codes available per sector and IP will be used for transmission.
Target
98%
2%
5s
98%
2.50%
8s
98%
2%
Test
240kbps
98%
2%
10Mb file DL
2500kbps
50Mb file DL
600kbps
20Mb file UL
97%
View
Properties
Repl
y
Hi,
I think most of the KPIs that you have provided are quite allright for a trial and is quite similar to
the ones i had proposed previously to another operator. Probably, just something to highlight the
CST where it is very dependent on several factors like the Core and whether is that A-B party or
just to the call test number then a 5 sec for speech CST maybe a little low.
Show Quoted Messages
View
Properties
Repl
Hi Ciara..
I think a few things you need to clarify:
As you those are my general recomendations, and how to approach is quite dependant on how
the aggrement is done with the custommer... The PM should be aware of those detailes.
BR
Carlos
View
Repl
Properties
Hi Ciara
I have involved on FOA P6FP for an italian customer. we have tested P6 on live network. We have
monitored 10 KPIs. In the next table you can find the P5 reference values and the P6 values.
KPI
View
Properties
Repl
y
Hi Ciara,
1. For your Speech CS12.2kbps, since there is no particular requirement on MOC (Mobile
Originating Call) & MTC (Mobile Terminating Call), and there is requirement of 5s, I would suggest
you need to call a fixed line.
2. You may need to look into no. of calls or sample in your drive test data as well. For example, if
DCR is 2%, means in you only have 100 calls, you can only drop 2 calls. So if you have less
sample, you can only afford drop less calls.
3. Regarding your IRAT, you can optimise your criteria accordingly to match the IRAT boundary
level and noise floor level. Do not set too low as it will cause high failure; do not see too high else
it will be too obvious less effort is done in optimising the network.
4. For CS64 call setup time, it is advisable to put the MTC UE at stationary spots with good
coverage to minimise the risk.
5. For all the IP test, it's advisable for to test there is no Transmission bottleneck as well as 100%
Transmission Availability. I assume Single Site Verification Test have been carried out on each
sites, since it's only 20 sites.
6. Look at the parameters as well, as there are many useful features to help you get high
throughput, e.g. flexible-code etc
Good Luck.
BR//Lum
Show Quoted Messages
View
Properties
Repl
y
Hi Ciara,
here are the KPIs we used in Nigeria for one of the operators:
CLASSES
Coverage
INDICATORS
CPICH RSCP > -95 and CPICH Ec/No > -11
Pilot Pollution
Access
Speech Call Set up Time
Call Set up Success rate (CSSR) (Speech)
Call Set up Success rate (CSSR) (Packet)
Call Set up Success rate (CSSR) (Video)
Throughput PS 64 RAB
PS 128 RAB
PS 384 RAB
HSDPA
Mobility
Soft / Softer Handover Factor overhead
Soft Handover Success Rate (Speech)
Soft Handover Success Rate (Packet)
Soft Handover Success Rate (Video)
CS IRAT Handover Success Rate(3G to 2G)
PS IRAT Handover Success Rate(3G to 2G)
Retainability DCR (Speech)
DCR (Packet)
DCR (Video)
Threshold
> 95%
< 4%
< 5s
> 97%
> 97%
> 97%
> 48
> 96
> 300
> 2.25M
< 30%
> 97%
> 97%
> 97%
> 97%
> 95%
< 3%
< 10%
< 3.5%
View
Properties
Repl
y
Hi Ciara,
Judging from your Initial Tuning KPI, it does not differ much from what we do here in Maxis
Malaysia. I believe you can achieve this KPI easily.
From my experience, FA is much more difficult than Initial Tuning. Good luck.
BR,
-afiq-
View
Properties
Repl
y
Hi
I would like to share some other useful information about this topic which I received through mails from the
N&TC Global Technical Focused Network.
The following website contains really good guidelines and a database for handling KPI commitments within
projects:
http://internal.ericsson.com/page/hub_globalservices/unit/units/advise/kpi/kpi_guidelines.jsp
Some other questions that should be considered when dicsussing KPI's are:
- Are the KPI's based on a "golden cluster"?
- Are you driving with exclusion criteria so only where you have good coverage will you drive?
- How many samples will you need to verify any of these KPI's? You should be aware of the fact that you might
not be able to get enough samples for the KPI fulfillment since you have a very small cluster.
- Are all to be met in the one cluster, or per cell?
- Is the cluster empty or any other traffic?
- Is there any payment terms related to this?
Normally you should counter propose something to the customer that is good enough (few KPIs, few drives) so
that you can pass acceptance in a short time period - and spend the rest of your time improving the network
for you customer, not re-measuring kPIs day in and day out.
The KPIs themselves are not impossible under the right conditions and criteria but under the wrong ones they
must be rejected.
Rgds
Ciara