umts_kpi

Test

ID

Test

Typ

e

Mile

ston

e 1

Mile

ston

e 2

Mile

ston

e 3

Test Case

DT

UE

Loca

tion

Valid

Driv

erou

te S

ampl

es

UL/

DL

Load

ing

Con

ditio

ns

mt1

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt2

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt3

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt4

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt5

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt6

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt7

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt8

mob

ile te

sts

yes

yes

yes

outd

oor

yes

yes n/a

mt9

mob

ile te

sts

yes

yes

yes HSUPA

outd

oor

yes

yes n/a

The Drivetest Data Validation Rules - Each raw shows the rules and the specific filters to be applied for the collected Cluster Acceptance drive test files depending of the Drivetest type (see the comments in the header cells for addtl. details) ---> to be used in the XPLORE UMTS Cluster Validation Engine

Entir

e D

river

oute

C

ompl

eted

Min

imum

# o

f site

s to

te

st/c

lust

er Validation KPI Collected (Mandatory for Validation Decision)

->see the "Validation KPI Tab for details)

Voice Calls (90 seconds) UE to PSTN

Load

ed (a

nd

Unl

oade

d?) ~CSV Access Failure Ratio

~CSV Call Setup Time ~CSV Drop Ratio~Cell Capacity~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

Voice Call Indefinite UE to PSTN

Load

ed (a

nd

Unl

oade

d?) ~CSV Quality (BLER)

~Voice MOS~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

FTP DL 2 MB file using any of the following PS RB (PS DL/UL) PS 384/64, PS 128/64, PS 64/64 Lo

aded

(and

U

nloa

ded?

) ~PSD Access Failure Rate~PSD Drop Rate~PSD Call Setup Time~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

FTP DL 10 MB file using any of the following PS RB (PS DL/UL) PS 384/64, PS 128/64, PS 64/64[Please clarify: No forced use of values? The terminal used in testing is free to perform Channel Switching. TMO yes]

Load

ed (a

nd

Unl

oade

d?) ~PSD Average DL Throughput

~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

FTP UL 2 MB file using any of the following PS RB (PS DL/UL) PS 384/64, PS 128/64, PS 64/64 Lo

aded

(and

U

nloa

ded?

) ~PSD Average UL Throughput~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

HSDPA Call 5 code (and 15 code when available)

Load

ed (a

nd

Unl

oade

d?) ~PSD HSDPA Access Failure Rate

~PSD HSDPA Drop Rate~PSD HSDPA Peak and Average Throughput ~PSD HSDPA Call Setup Time~*Soft/Softer HO Failure Rate~*Soft/Softer HO OverheadVoice Call (90

seconds) UE to 3G

Load

ed (a

nd

Unl

oade

d?) ~CSV Call Setup Time (3G

to 3G)~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

Voice Calls (90 seconds) with other than 12.2 kbit/s codec.

Load

ed (a

nd

Unl

oade



Load

ed (a

nd

Unl

oade

d?) ~PSD HSUPA Throughput


st1

yes

yes

yes

n/a

n/a

st2

yes

yes

yes

n/a

n/a

st4

yes

yes

yes

n/a

n/a

st5

yes

yes

yes

n/a

n/a

st6

yes

yes

yes

n/a

n/a

st7

yes

yes

yes

n/a

n/a

st8

yes

yes

yes HSUPA n/a

n/a

mob

ile te

sts no yes

yes

outd

oor

n/a

n/a ?

mob

ile te

sts no yes

yes Video Call Indefinite

outd

oor

n/a

n/a ?

mob

ile te

sts no yes

yes Voice IRAT KPI

mob

ile te

sts no yes

yes Packet IRAT KPI

stat

iona

ry

test

s Voice Calls (90 seconds) UE to PSTN

outd

oor/i

ndoo r? >=10

%(=#of sites/cluster)/10)

Load

ed (a

nd

Unl

oade



stat

iona

ry

test

s FTP DL 2 MB file using any of the following PS RB (PS DL/UL) PS 384/64, PS 128/64, PS 64/64

outd

oor/i

ndoo r? >=10


Load

ed (a

nd

Unl

oade

d?) ~PSD Access Failure Rate

~PSD Drop Rate~PSD Call Setup Time~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

stat

iona

ry

test

s FTP UL 2 MB file using any of the following PS RB (PS DL/UL) PS 384/64, PS 128/64, PS 64/64

outd

oor/i

ndoo r? >=10


Load

ed (a

nd

Unl

oade

d?) ~PSD Average UL Throughput


stat

iona

ry

test

s Ping Test of 32 byte packets using DCH channels

outd

oor/i

ndoo r? >=10


Load

ed (a

nd

Unl

oade

d?) ~PSD Latency


stat

iona

ry

test

s HSDPA Call 5 code (and 15 code when available)

outd

oor/i

ndoo r? >=10


Load

ed (a

nd

Unl

oade

d?) ~PSD HSDPA Access Failure Rate

~PSD HSDPA Drop Rate~PSD HSDPA Peak and Average Throughput ~PSD HSDPA Call Setup Time~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

stat

iona

ry

test

s Voice Calls (90 seconds) with other than 12.2 kbit/s codec.

outd

oor/i

ndoo r? >=10


Load

ed (a

nd

Unl

oade


~CSV Call Setup Time ~CSV Drop Ratio~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

stat

iona

ry

test

s

outd

oor/i

ndoo r? >=10


Load

ed (a

nd

Unl

oade

d?) ~PSD HSUPA Throughput


Video Calls (90 Seconds)

~CSD Access Failure Ratio~CSD Call Setup Time~CSD Drop Ratio~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

~CSV Quality (BLER)~Video MOS~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

~Voice IRAT Failure Rate~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

~PSD IRAT Failure Rate~PSD Packet Interruption Time~*Soft/Softer HO Failure Rate~*Soft/Softer HO Overhead

Cal

l Ini

tiate

d by

Cal

l Ter

min

ated

by

Con

nect

ion

Type

Voic

e C

odec

FTP

Dire

ctio

n

PIN

G T

est

Stat

ic P

ING

test

PSTN A A CSV any(?) n/a n/a n/a n/a n/a

PSTN A CSV any(?) n/a n/a n/a n/a n/a

n/a A A manual PSD n/a 2MB DL n/a n/a n/a

n/a A A manual PSD n/a 10MB DL n/a n/a n/a

n/a A A manual PSD n/a 2MB UL n/a n/a n/a

n/a A A manual HSDPA n/a 10MB DL n/a n/a n/a

3G M

obile A A CSV any(?) n/a n/a n/a n/a n/a

PSTN ? A A ? CSV n/a n/a n/a n/a n/a

n/a A A manual HSUPA n/a 10MB UL n/a n/a n/a

- Each raw shows the rules and the specific filters to be applied for the collected Cluster Acceptance drive test files depending of the Drivetest type (see the comments in the header cells for addtl. details) ---> to be used in the XPLORE UMTS Cluster Validation Engine

KPI Collected (to be collected/reported only)

->see the "Validation KPI Tab for details)

Cal

l Sou

rce

"A P

arty

"

Cal

l Des

tinat

ion

"B P

arty

"

Cal

l Dur

atio

n/S

essi

on D

urat

ion

Tim

e in

terv

al b

etw

een

Cal

ls

/ Ses

sion

s

FTP

Volu

me

Size

(Arc

hive

-type

file

s us

ed)

# of

loca

tions

req.

for t

he

PIN

G te

st

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route Te

st V

ehic

le

UE+

Scan

ner? 90

seconds/call15 seconds


st V

ehic

le

UE+

Scan

ner? indefinite (till

Call Drop)Call Drop

30 seconds

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route~PSD Average DL Throughput

Test

Veh

icle

U

E+Sc

anne

r?

Net

/FTP

Se

rver

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route~PSD Access Failure Rate~PSD Drop Rate~PSD Call Setup Time

Test

Veh

icle

U

E+Sc

anne

r?

Net

/FTP

Se

rver

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route~PSD Access Failure Rate~PSD Drop Rate~PSD Call Setup Time

Test

Veh

icle

U

E+Sc

anne

r?

Net

/FTP

Se

rver


st V

ehic

le

UE+

Scan

ner?

Net

/FTP

Se

rver

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route

Test

Veh

icle

U

E+Sc

anne

r? 90 seconds/call

15 seconds


st V

ehic

le

UE+

Scan

ner? AMR12.2kbps

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route~PSD HSUPA Access Failure Rate~PSD HSUPA Drop Rate~PSD HSUPA Call Setup Time

Test

Veh

icle

U

E+Sc

anne

r?

Net

/FTP

Se

rver

UE+

Scan

ner?

PSTN A A CSV any(?) n/a n/a n/a n/a n/a

~PSD Average DL Throughput

UE+

Scan

ner? n/a A A manual PSD n/a 2MB DL n/a n/a n/a

UE+

Scan

ner? n/a A A manual PSD n/a 2MB UL n/a n/a n/a

UE+

Scan

ner? n/a A A manual PSD n/a n/a n/a yes 10

UE+

Scan

ner? n/a A A manual HSDPA n/a 10MB DL n/a n/a n/a

~Cell Capacity

UE+

Scan

ner?

PSTN ? A A ? CSV n/a n/a n/a n/a n/a

UE+

Scan

ner? n/a A A manual HSUPA n/a 10MB UL n/a n/a n/a

UE+

Scan

ner?

3G M

obile A A CSD n/a n/a n/a n/a n/a n/a

UE+

Scan

ner?

3G M

obile A CSD n/a n/a n/a n/a n/a n/a

90 seconds/call

15 seconds

Net

/FTP

Se

rver

~PSD Access Failure Rate~PSD Drop Rate~PSD Call Setup Time N

et/F

TP

Serv

erN

et/F

TP

Serv

er 1000PINGS [32B]/sector

Net

/FTP

Se

rver

AMR12.2kbps

~PSD HSUPA Access Failure Rate~PSD HSUPA Drop Rate~PSD HSUPA Call Setup Time N

et/F

TP

Serv

er

90 seconds/call

15 seconds

indefinite (till Call Drop)

Call Drop

30 seconds

~PSD Packet User Interruption Time

n/a 350 n/a n/a n/a

12 n/a n/a n/a n/a

n/a 350 n/a n/a n/a

12 n/a n/a n/a n/a

12 n/a n/a n/a n/a

12 n/a n/a n/a n/a

n/a 350 n/a n/a n/a

n/a 350 n/a n/a n/a

12 n/a n/a n/a n/a

- Each raw shows the rules and the specific filters to be applied for the collected Cluster Acceptance drive test files depending of the

Min

imum

sta

ted

num

ber o

f ho

urs

wor

th o

f (va

lid

colle

cted

) dat

a/cl

uste

rM

inim

um #

of C

all S

etup

At

tem

pts/

Clu

ster

Min

imum

sta

ted

num

ber o

f ho

urs

wor

th o

f (va

lid

colle

cted

) dat

a/se

ctor

(for

st

atic

test

s on

ly)

Min

imum

# o

f Cal

l Set

up

Atte

mpt

s/Se

ctor

(for

sta

tic

test

s on

ly)

Min

imum

val

id D

T sa

mpl

es/s

ecto

r

Min

imum

val

id D

T sa

mpl

es/d

rive

rout

e10% samples more than the # of samples required for a 95% Statistical Confidence

10% samples more than the # of samples required for a 95% Statistical Confidence








n/a n/a n/a 60 n/a

n/a n/a n/a 60 n/a

n/a n/a n/a 60 n/a

n/a n/a n/a n/a n/a

n/a n/a 2 n/a n/a

n/a n/a n/a 60 n/a

n/a n/a 2 n/a n/a

n/a n/a n/a n/a n/a ?

n/a n/a n/a n/a n/a ?








Des

crip

tion

Mobile-to-PSTN voice callOriginating side located in the vehicleA Party calls B Party and call held for 90 seconds.A Party Terminates.Time between calls = 15 seconds

Mobile- to-PSTN voice callOriginating-side located in the vehicleA Party calls B Party and call held indefinitely.If call drops, re-establish call immediately within 30 seconds.

Mobile-in-Car in idle state, requests PDP context activation, connect to FTP server and initiate FTP DL of 2 MB file using allocated radio bearer.Purpose is to use whatever radio bearer allocated, and to try and achieve a mix of data radio bearers between 384,128, and 64 in DL.At end of DL, wait some time (depends on parameters for inactivity) for DCH to be released, then deactivate the PDP context activation. Repeat the cycle.Mobile-in-Car in idle state, requests PDP context activation, connect to FTP server and initiate FTP DL of 10 MB file using allocated radio bearer.Purpose is to use whatever radio bearer allocated and to try and achieve a mix of data radio bearers between 384,128, and 64 in DL.At end of DL, wait some time (depends of parameters for inactivity) for DCH to be released, then deactivate the PDP context activation. Repeat the cycle.Mobile-in-Car in idle state, requests PDP context activation, connect to FTP server and initiate FTP UL of 2 MB file. At end of UL, wait 15 seconds for DCH to be released and PDP context is deactivated. Repeat Cycle.

HSDPA tests will be done with a single UE doing HSDPA call in the Cell under test with a 384 Kbps associated DCH on the UL (capable of downgrading to 64 Kbps) FTP DL of minimum 10 MB zipped file.

mobile-to-3G mobile callOriginating side located in the vehicle, terminating side located in office.A party calls B party and call held for 90 seconds.A Party TerminatesTime between calls = 15 seconds

Mobile to PSTN using AMR rate other than 12.2kbit/sNB That this test is only applicable when rates other than 12.2kbit.s are supported in Ericsson release.Details of test to be mutually defined.

HSUPA tests will be done with a single UE doing HSUPA call in the Cell under test .FTP UL of minimum 10 MB zipped file. NB That this test is only applicable when HSUPA is supported in Ericsson release.Details of test to be mutually defined.

Voice inter-system handovers and Cell re-selections to be obtained on IRAT-Specific Drive Route

Mobile-to-PSTN voice callOriginating side located in the vehicleA party calls B party and call held for 90 seconds.A Party Terminates.Time between calls = 15 seconds

The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be done for every sector of Node chosen. The test locations shall either be indoor locations, subject to the indoor coverage requirements contained in Section 5.3 or shall be outdoor locations to be specified by the validator entity(Purchaser/Ericsson).He reserves the right to relax or waive the need to conduct these stationary tests or to reduce the number of stationary test locations within a Cluster.

Mobile-in-Car in idle state, requests PDP context activation, connect to FTP server and initiate FTP DL of 2 MB file using allocated radio bearer.Purpose is to use whatever radio bearer allocated, and to try and achieve a mix of data radio bearers between 384,128, and 64 in DL.At end of DL, wait some time (depends on parameters for inactivity) for DCH to be released, then deactivate the PDP context activation. Repeat the cycle.


Mobile-in-Car in idle state, requests PDP context activation, connect to FTP server and initiate FTP UL of 2 MB file. At end of UL, wait 15 seconds for DCH to be released and PDP context is deactivated. Repeat Cycle.


Mobile is Idle and requests PDP context activation, then large ping to force DCH channel pings specific IP address with 32 byte packet, set 1000 pings, repeat cycle.

The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be done for every sector of Node chosen. The test locations shall either be indoor locations, subject to the indoor coverage requirements contained in Section 5.3 or shall be outdoor locations to be specified by the validator entity(Purchaser/Ericsson).He reserves the right to relax or waive the need to conduct these stationary tests or to reduce the number of stationary test locations within a Cluster.HSDPA tests will be done with a single UE doing HSDPA call in the Cell under test with a 384 Kbps associated DCH on the UL (capable of downgrading to 64 Kbps) FTP DL of minimum 10 MB zipped file.


Mobile to PSTN using AMR rate other than 12.2kbit/sNB That this test is only applicable when rates other than 12.2kbit.s are supported in Ericsson release.Details of test to be mutually defined.


HSUPA tests will be done with a single UE doing HSUPA call in the Cell under test .FTP UL of minimum 10 MB zipped file. NB That this test is only applicable when HSUPA is supported in Ericsson release.Details of test to be mutually defined.


3G-to-3G video callOriginating-side located in the vehicle, terminating-side located in office.A Party calls B Party and call held for 90 secondsA Party TerminatesTime between calls = 15 seconds

3G-to-3G Video callOriginating-side located in the vehicle, terminating-side located in office.A Party calls B Party and call held indefinitelyif call drops re-establish call immediately within 30 seconds

Packet inter-system handovers (Cell change orders) and Cell re-selections to be obtained on IRAT-specific Drive Route

Rep

ort -

Det

ails

Rep

ort -

Clu

ster

Driv

etes

t R

esul

ts M

appi

ng

Rep

ort -

Map

ping

(the

In-

Bui

ldin

g W

alkt

ests

m

appi

ng)

*Show Cluster Driveroute*Show Failure Events (Lat/Lon, Explain)*Show the Voice Coverage Map (show the "Service Area"=areas where the serv. is expected to be reliably-offered to customers)*Show the Video Coverage Map (show the "Service Area")*Show the Packet Coverage Map (show the "Service Area")*Show the HSDPA Coverage Map (show the "Service Area")*Show the Scanner RSCP measurements (Vs. Lat/Lon) along the Drive route *Show the Average value of the Scanner RSCP measurements (Vs. Lat/Lon) along the Drivetest*Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drive route*Scanner Average value of the Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest*Show the Coverage Prediction Maps (TMO/Prediction Tool)

*for InBuilding Tests Only: Show the Scanner RSCP measurements (Vs. floor plan) along the in-building walk-test route *for InBuilding Tests Only: Scanner Ec/Io mesurements (Vs. floor plan) along the in-building walk-test route

all raw results ,measurements and KPI achieved before application of allowable exemptions, all processed results ,measurements and KPI achieved after application of allowable exemptions, All applicable exclusions and exemptions. Network element alarm history during the Cluster Acceptance, and Network event history during the drives. OSS Statistics covering all Level 1 KPI as stated below for all cells within the Cluster, for the duration of the drives. This information shall be provided in a format provided by Seller and approved by Purchaser TMO OK Maps and Floor Plans will be provided by Purchaser. TMO OK

























n/a

n/a

n/a

n/a

n/a

n/a

n/a















UMTS KPI, Thresholds and the Imput Data Sources---> used for Milestones 1 - 3

yes ~CSV Access Failure Ratioyes ~CSV Drop Ratioyes ~CSV Quality (BLER)yes ~CSV Quality (BLER)yes yes ~Cell Capacityyes

yes ~CSV Call Setup Time (Mobile to PSTN)yes ~CSV Call Setup Time (Mobile to Mobile)

(not mentioned here) (not mentioned here) (not mentioned here) (not mentioned here)

yes ~CSV Call Setup Time yes yes ~PSD Access Failure Rateyes yes ~PSD Drop Rateyes ~PSD Latency

yes ~PSD Average DL Throughput yes ~PSD Average DL Throughput

yes ~PSD Average UL Throughputyes ~PSD Average UL Throughputyes yes ~PSD Call Setup Time

(not mentioned here) (not mentioned here) (not mentioned here)

yes ~PSD HSDPA Access Failure Rateyes ~PSD HSDPA Drop Rate


yes ~PSD HSDPA Average Throughput yes ~PSD HSDPA Average Throughput yes ~PSD HSUPA Throughput yes ~PSD HSUPA Throughput yes ~PSD HSDPA Call Setup Time


yes ~PSD HSUPA Access Failure Rateyes ~PSD HSUPA Drop Rateyes ~PSD HSUPA Call Setup Timeyesyesyesyes

yes ~Voice MOSyes ~PSD HSDPA Peak Throughput yes ~Soft/Softer HO Failure Rate (cluster level)yes ~Video MOSyes ~Voice IRAT Failure Rateyes ~PSD IRAT Failure Rate

Milestone 1 Mandatory KPI

("Cl. Acceptance Decision KPI"):

Milestone 1 Report Only

KPI ("FYI KPI"):

KPI Parameter (per Annex E Table from "U16 UMTS System Acceptance Procedures v7.12.doc")

~Soft/Softer Handover Overhead (cluster level)

*Scanner RSCP Measurements (Vs. Lat/Lon) along the Drivetest route *Scanner Ec/Io mesurements (Vs. Lat/Lon) along the Drivetest route*for InBuilding Tests Only: Show the Scanner RSCP measurements (Vs. floor plan) along the in-building walk-test route *for InBuilding Tests Only: Scanner Ec/Io mesurements (Vs. floor plan) along the in-building walk-test route

yes ~PSD Packet Interruption Timeyes ~PSD Packet User Interruption Time

UMTS KPI, Thresholds and the Imput Data Sources---> used for Milestones 1 - 3

CSV Access Failure Rate 2.0 % 2.0 % 2.0 % >CSV Drop Rate 2.0 % 1.5 (2) % 1.5 (2) % >CSV Quality (DL) >CSV Quality (UL) >Cell Capacity >Soft/Softer Handover Overhead 1.6 1.6 1.7 >CSV IRAT Failure Rate N.A. 5.0 % 5.0 % >*Voice Call Setup time (Mobile to PSTN) >*Voice Call Setup time (Mobile to Mobile) >CSD Access Failure Rate 3.0 % 2.0 % 2.0 % >CSD Drop Rate 2.5 % 2.5 % >CSD Quality (DL) >CSD Quality (UL) >*CSD Call Setup time N.A. N.A. >PSD Access Failure Rate 2.0 % 2.0 % 2.0 % >PSD Drop Rate 2.5 % 2.0 % 2.0 % >*PSD Latency (any R99 RAB) N.A. N.A. >

240 240 > 210 210 > 200 200 > 180 180 >

*PSD Call Setup time N.A. N.A. >PSD IRAT Failure Rate N.A. 5.0 % 5.0 % >PSD IRAT Interruption time N.A. N.A. >PSD IRAT User Data Interruption time N.A. N.A. >HSDPA Access Failure Rate 2.0 % 2.0 % 2.0 % >HSDPA Drop Rate 3.0 % 2.0 % 2.0 % >*HSDPA Latency N.A. N.A. >

1300 1300 > 1100 1100 N.A. > 700 700 > 600 600 N.A. >

1100 1100 > 500 500 >

*HSDPA Session Activation time N.A. N.A. >*Average Cell Availability KPI N.A. N.A. N.A.** >*Average Cell Non-Maintenance Availability KPI N.A. N.A. N.A.** >

10 % 10 % 10 % > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) > (not mentioned here) N.A. > (not mentioned here) N.A. > (not mentioned here) N.A. >

KPI Parameter (from "U12 UMTS Network KPI v6.10.doc")

Pre-Launch KPI Thresholds

(Milestone 1) -U12-

Launch KPI Thresholds(Milestone 2)

-U12-

Post Launch KPI Thresholds(Milestone 3)

-U12-

95th percentile of samples 2.0 %

BLER


BLER


BLER 95th percentile of samples 2.0 %

BLER


BLER


BLER 40 UE AMR

12.2k (provided it is achieved in RF

design)

40 UE AMR 12.2k (provided it is achieved in RF

design)

Measure and report

95th percentile 6 seconds

95th percentile 6 seconds

95th percentile 6 seconds 95th percentile

9 seconds 95th percentile

9 seconds 95th percentile

9 seconds 3.0 %

(Counter), 2.5 % (Drive Test)


BLER


BLER


BLER 95th percentile of samples 1.0 %

BLER


BLER

95th percentile of samples 1.0

%BLER 95th percentile 9

seconds

95th percentile 200msPSD R99 Average DL throughput (kbps)

(Unloaded) 150 (Counter), 240 (Drive Test)PSD R99 Average DL throughput (kbps)

(Loaded) 150 (Counter), 210 (Drive Test)PSD R99 Average UL throughput (kbps)

(Unloaded) 150 (Counter), 200 (Drive Test)PSD R99 Average UL throughput (kbps)

(Loaded) 150 (Counter), 180 (Drive Test)95th percentile

sessions 5 seconds95th percentile ,

12 secondsMeasure and Report

95th percentile sessions 100

msStationary Maximum DL HSDPA Bit Rate (kbps) under no load (UE Category 12)

1300 (at RLC Layer using

counter)Stationary Maximum DL HSDPA Bit Rate (kbps) with 50% DL loading (UE Category 12)HSDPA Average DL Throughput (kbps) for UE category 12 under no load

700 (at off peak) HSDPA Average DL Throughput (kbps) for UE

category 12 under 50% DL loadingHSUPA Stationary Peak throughput (kbps) for UE Category 3 (1.45 Mbps)

Measure and ReportHSUPA Stationary Average throughput (kbps) for

UE Category 3 (1.45 Mbps)Measure and

Report95th percentile sessions 5

secondsGSM Performance Degradation due to Introduction of UMTS

(not mentioned here) N.A. > (not mentioned here) N.A. >

CSV Access Failure RateCSV Drop RateCSV Quality (DL)CSV Quality (UL)Cell CapacitySoft/Softer Handover OverheadCSV IRAT Failure Rate*Voice Call Setup time (Mobile to PSTN)*Voice Call Setup time (Mobile to Mobile)CSD Access Failure RateCSD Drop RateCSD Quality (DL)CSD Quality (UL)*CSD Call Setup timePSD Access Failure RatePSD Drop Rate*PSD Latency (any R99 RAB) RTT (Round Trip Time)

*PSD Call Setup timePSD IRAT Failure RatePSD IRAT Interruption time PSD IRAT User Data Interruption time HSDPA Access Failure Rate Table 41HSDPA Drop Rate*HSDPA Latency

*HSDPA Session Activation time Table 51*Average Cell Availability KPI Table 53*Average Cell Non-Maintenance Availability KPI Table 55

?

KPI Parameter (from "U12 UMTS Network KPI v6.10.doc") KPI Parameter

Reference/Definition

XPLORE Validation Module Input data for the Milestone 1:[Drivetest Data only]

Access failure is the product of the RRC Connection Failure, NAS Setup Failure and the RAB Establishment Failure. RRC Connection Success is counted when the RNC receives a RRC Setup Complete from the UE. NAS Setup is considered successful when the signaling messages in the call flow during call setup flow is successfully completed by relevant Network Elements. A RAB is considered successfully established when the RAB Assignment Response is sent by RNC to the CN. # of RRC Connections

Requests (UL L3 Messages)# of Connect CC_Alerting /Connect (DL L3 Messages)

Circuit Switched Voice Drop measures the Networks inability to maintain a call. CSV Drop is defined as the ratio of abnormal speech disconnects, relative to all speech disconnects (both normal and abnormal). A normal disconnect is initiated by a RAB Disconnect RANAP message from the MSC at the completion of the call. An abnormal RAB disconnect includes Radio Link Failures, UL or DL interference or other reason and can be initiated by either UTRAN or CN.

# of Call_Dropped# of Call Setup SuccessVoice quality shall be

measured by BLER# of samples below BLER Target (BLER_DL 2%)# of all BLER DL Samples

Voice quality shall be measured by BLER

# of samples below BLER Target (BLER_UL 2%)# of all BLER DL Samples

Average number of Voice Calls (AMR 12.2) that can be supported by cell

CellTrafficPower AvgRL PerCall AvgPowerPerRL

Soft/Softer Handover Overhead KPI provides an indication of how many Cells or Sectors were in the active set during the call on an average basis.

AS (list of used AS, 1, 2.M)M = Maximum Active Set size usedDuration(AS)

CSV Inter-Radio Access Technology Handover Failure = Hard Handover Failure rate from UMTS and GSM System for voice calls. = ratio between # of HO UTRAN Failures received by UE and # of HO UTRAN commands sent by UE

# of HO UTRAN Failures received by UE# of HO UTRAN commands sent by UE

Voice call set up time indicates Network response time to a user request for a voice service. This KPI is applicable only for drive test.

CC_Alerting(MOC)RRC Connection Request(MOC)



Access failure is the product of the RRC Connection Failure, NAS setup failure and the RAB Establishment Failure. RRC Connection Success is counted when the RNC receives a RRC Setup Complete from the UE. NAS Setup is considered successful when the signaling messages in the call flow during call setup flow is successfully completed by relevant Network elements. A RAB is considered successfully established when the RAB Assignment Response is sent by RNC to the CN.

# of RRC Connections Requests (UL L3 Messages)# of Connect CC_Alerting /Connect (DL L3 Messages)

# of Call_Dropped# of Call Setup SuccessCSD Data quality shall be

measured by BLER# of samples below BLER Target (BLER_DL 2%)# of all BLER DL Samples

CSD Data quality shall be measured by BLER


Circuit Switched Data call set up time indicates Network response time to a user request for a video service.


TSwitch Data access failure from a user perspective

# of Activate PDP Context Accept# of RRC Connections Requests

Packet session is considered as dropped when associated RAB has been released abnormally by either UTRAN or CN. Any drop after RANAP: RAB Assignment Response is considered as PS drop call.

# of FTP Downloads Success# of Call Setup SuccesRound trip time for a 32 Bytes

ping for any R99 PS RABIndicates maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP.

PSD R99 Average DL throughput (kbps) (Unloaded)

DL Packet Switched Data average throughput using R99 RAB measured at application layer(Total number of RLC blocks sent over the observation window including re-transmission per transport type)

DL User Data Transferred [kb] (FTP)Session duration [s] (FTP)

PSD R99 Average DL throughput (kbps) (Loaded)



PSD R99 Average UL throughput (kbps) (Unloaded)

UL Packet Switched Data average throughput using R99 RAB measured at application layer(Total number of RLC blocks sent over the observation window including re-transmission per transport type)

UL User Data Transferred [kb] (FTP)Session duration [s] (FTP)

PSD R99 Average UL throughput (kbps) (Loaded)



PSD call setup time indicates Network response time to a user request for a packet data service. In case of multiple RRC connection requests the first RRC connection request will be considered for KPI calculation.

PDP Context Activation accept (MOC)RRC Connection Request (MOC)

Inter-Radio Access Technology (IRAT) is a hard handover failure rate between UMTS and GSM = Hard Handover failure rate when a PS Data call (R99) fail to handover from UMTS network to GSM network

#CellChangeOrderFromUTRAN Failure(PS)#CellChangeOrderFromUTRAN Command(PS)

Duration of interruption to Packet data service during Hard Handover (is an indicator of interruption time for the packet switch data during Inter-Radio Access Technology hard handover.)

TimeRAUpdateComplete_UETimeCellChangeOrder_RNCDuration in seconds to

interruption of Packet data service from User perspective during IRAT Hard Handover from 3G to 2G

TimeFirstPacketDataReceivedIn2GTimeLastPacketDataReceivedIn3G

# of Activate PDP Context Accept Messages# of RRC Connection Requests Messages

HSDPA session is considered as dropped when associated HS-DSCH has been released abnormally by either UTRAN or CN. This test will be done with a single UE performing HSDPA call in the Cell under test with 384/64 Kbps associated DCH on the uplink and HS-DSCH in the DL with downgrade/upgrade to/from R99 RAB.

# of HS-DSCH_ReleaseDueToFailure ( = HS-DSCH_Drop)# of HS-DSCH_AllocationSuccess

Round trip time for a 32 Bytes ping for HSDPA NRT RABStationary Maximum DL HSDPA Bit Rate (kbps)

under no load (UE Category 12)Highest RLC blocks throughput over the observation window including re-transmission

Peak DL User data RLC throughput [Kb] Stationary Maximum DL HSDPA Bit Rate (kbps)

with 50% DL loading (UE Category 12)Highest RLC blocks throughput over the observation window including re-transmission

Peak DL User data RLC throughput [Kb] HSDPA Average DL Throughput (kbps) for UE

category 12 under no loadTotal number of RLC blocks sent over the observation window including re-transmission

Sum of all DL User data transferred [Kb]Sum of Sessions duration [s]

HSDPA Average DL Throughput (kbps) for UE category 12 under 50% DL loading

Total number of RLC blocks sent over the observation window including re-transmission


HSUPA Stationary Peak throughput (kbps) for UE Category 3 (1.45 Mbps)

Highest RLC blocks throughput over the observation window including re-transmission

Peak UL User data RLC throughput [Kb] HSUPA Stationary Average throughput (kbps) for

UE Category 3 (1.45 Mbps)Total number of RLC blocks sent over the observation window including re-transmission

Sum of all UL User data transferred [Kb]Sum of Sessions duration [s]

GSM Performance Degradation due to Introduction of UMTS

The deployment of the UMTS Network shall not degrade Purchasers existing GSM Network performance. Excluding IRAT Hard Handover Feature, both UMTS and GSM Networks are considered independent of each other. This section addresses any concern related to UMTS Equipment installation on GSM Sites and related faults for which Seller has responsibility that could degrade GSM performance.

CSV MOU (from GSM CSV drivetest files)# of Call_Dropped (GSM CSV)# of Call Setup Success (GSM CSV)# of RRC Connections Requests ( GSM UL L3 Messages)# of Connect CC_Alerting /Connect (GSM DL L3 Messages)

UMTS CSVUMTS CSVUMTS CSVUMTS CSVUMTS CSVUMTS CSVUMTS CSVUMTS CSVUMTS CSVUMTS CSDUMTS CSDUMTS CSDUMTS CSDUMTS CSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS PSDUMTS HSDPAUMTS HSDPAUMTS HSDPAUMTS HSDPAUMTS HSDPAUMTS HSDPAUMTS HSDPAHSUPA SessionUMTS HSUPAUMTS HSUPA??GSM CSV

Data Input Detailsfind (more details in "Annex KPI MS1 Tab.")

Use DT Session files:

Measurement Condition:Drivetest output data from CSV Calls onlyIn the event that there are several consecutive RRC Connection Request only the first RRC connection request shall be taken into account for the KPI calculation. Calls are considered as failed during access when a connection is attempted and the UE does not receive Alerting/Connect message in case of drive test measurement. For OSS RANAP: RAB Assignment Response message from the RNC to core Network is considered as a call successful setup.

Measurement Condition: Drivetest output data from CSV Calls onlyAny CSV call successfully handed over from 3G to 2G network within the CSV Service Area shall be considered as drop call for Milestone 2.

This KPI shall be measured at 1% BLER operating point set in UTRAN for voice call. BLER shall be available using counters with Cell Level granularity. KPI for MS3 shall be calculated at Market Level. For MS3, DL BLER shall be measured using RES counters or drive test as required.

UL BLER is collected and presented in the MRR-W (Measurement Results Recording WCDMA) feature in OSS-RC

CSV Cell Capacity shall be calculated based on average DL power allocated to AMR 12.2 RB for this KPI. CellTrafficPower = Net DL Power available in a cell to carry user traffic and is equal to total cell carrier RF power (at system reference point) minus Common/signaling channel power as per RF Planning Guideline/Link Budget)AvgRL PerCall = Average number of Radio Link used to support a Voice Call AvgPowerPerRL = Average RF Power used for a Radio Link to support Voice Call

AS = Active Set size M = Maximum Active Set size as defined in RNCDuration(AS) = Duration of the call in Active Set size of AS (AS=1 to M)

# of HO UTRAN Failures received by UE and # of HO UTRAN commands sent by UEDrivetest output data used: # of HO UTRAN Failures received by UE and # of HO UTRAN commands sent by UE

CC_Alerting(MOC) = (Timestamp of the Call Alerting message?)RRC Connection Request(MOC) = (Timestamp of the Connection Request message?)(to use the Count of the recorded Call Setup time interval for all initiated call and the the count of recorded call setup time interval that are greater than the threshold)Drivetest output data used: Voice Call setup time = CC_Alerting(MOC) RRC Connection Request(MOC)Obs: For mobile to mobile call, calling UE shall be mobile and called UE shall be stationary.

CC_Alerting(MOC) = (Timestamp of the Call Alerting message?)RRC Connection Request(MOC) = (Timestamp of the Connection Request message?)(to use the Count of the recorded Call Setup time interval for all initiated call and the the count of recorded call setup time interval that are greater than the threshold)Drivetest output data used: Voice Call setup time = CC_Alerting(MOC) RRC Connection Request(MOC)Obs: For mobile to mobile call, calling UE shall be mobile and called UE shall be stationary.

Drivetest output data from CSD Calls onlyDrivetest output data from CSD Calls onlyThis KPI shall be measured at 1% BLER operating point set in UTRAN for voice call. BLER shall be available using counters with Cell Level granularity. KPI for MS3 shall be calculated at Market Level. For MS3, DL BLER shall be measured using RES counters or drive test as required. # of BLER_DL BLERT = 1% vs # of BLER_DL > BLERT = 1%(#Faulty DCH Transport Blocks in Uplink after SelectionCombining (Speech)/Total DCH Transport Blocks in Uplink after SelectionCombining (Speech), Sampling period shall be every ten (10) seconds.)

UL BLER is collected and presented in the MRR-W (Measurement Results Recording WCDMA) feature in OSS-RC. Reporting period can be set to between 2 to 64 seconds according to standard. Counters are presented in a PDF format in MRR-W.

Measurement results are available every 15 minutes.BLER shall be available using counters with Cell Level granularity.

# of BLER_UL BLERT=1% vs # of BLER_DL > BLERT = 1%(#Faulty DCH Transport Blocks in Uplink after SelectionCombining (Speech)/Total DCH Transport Blocks in Uplink after SelectionCombining (Speech), Sampling period shall be every ten (10) seconds.)

CC_Alerting(MOC) = (Timestamp of the Call Alerting message?)RRC Connection Request(MOC) = (Timestamp of the Connection Request message?)(to use the Count of the recorded Call Setup time interval for all initiated call and the the count of recorded call setup time interval that are greater than the threshold)The test shall be initiated by making a video call from one UMTS UE to another UMTS UE. In case of multiple RRC connection requests the first RRC connection request will be taken into account for KPI calculation.

Access Failure Rate shall be measured by data session activation (PS) followed by download. In case of multiple RRC connection requests the first RRC connection request will be considered for KPI calculation.

PSD drop Rate shall be measured after start of ftp download . PSD call is considered as dropped when ftp session is manually/abnormally disconnected without completing file transfer due to any reason.

Latency will be measured with the destination server for ping connected directly to the GGSN (i.e. the server on the same Intranet domain as GGSN). RTT will be measured in stationary position. This test will be done with a single UE with R99 RAB PS call with Ping application.

DL User Data Transferred [kb] =Total ftp size download in kilo-bit in one sessionSession duration [s]=Total time (seconds) duration to download single fileSessionDuration(sec) = (time stamp of Session End or Session Error time stamp of Session Start)This metric shall be measured only for Packet Switch Traffic Class (Interactive and Background). KPI Measurement shall be based on RLC (SDU) layer throughput with five percent (5%) target for DL/UL BLER for R99 RAB.

DL User Data Transferred [kb] =Total ftp size download in kilo-bit in one sessionSession duration [s]=Total time (seconds) duration to download single fileSessionDuration(sec) = (time stamp of Session End or Session Error time stamp of Session Start)This metric shall be measured only for Packet Switch Traffic Class (Interactive and Background). KPI Measurement shall be based on RLC (SDU) layer throughput with five percent (5%) target for DL/UL BLER for R99 RAB.

UL User Data Transferred [kb] =Total ftp size download in kilo-bit in one sessionSession duration [s]=Total time (seconds) duration to download single fileSessionDuration(sec) = (time stamp of Session End or Session Error time stamp of Session Start)

This metric shall be measured only for Packet Switch Traffic Class (Interactive and Background). KPI Measurement shall be based on RLC (SDU) layer throughput with five percent (5%) target for DL/UL BLER for R99 RAB.

UL User Data Transferred [kb] =Total ftp size download in kilo-bit in one sessionSession duration [s]=Total time (seconds) duration to download single fileSessionDuration(sec) = (time stamp of Session End or Session Error time stamp of Session Start)UL User Data Transferred [kb] =Total ftp size download in kilo-bit in one sessionSession duration [s]=Total time (seconds) duration to download single fileSessionDuration(sec) = (time stamp of Session End or Session Error time stamp of Session Start)This metric shall be measured only for Packet Switch Traffic Class (Interactive and Background). KPI Measurement shall be based on RLC (SDU) layer throughput with five percent (5%) target for DL/UL BLER for R99 RAB.

PSD IRAT HHO failure KPI does not include HHO Preparation failure. Specific drive route shall be identified at the UMTS RF Service Area boundary to verify this KPI.

In case of multiple RRC connection requests the first RRC connection request will be considered for KPI calculation.Access Failure Rate shall be measured by data session activation (HSDPA) followed by download. This test shall be done with a single UE doing HSDPA call in the Cell under test with 384/64 Kbps associated DCH on the uplink.Access Failure Rate shall be measured by data session activation (HSDPA) followed by download.

# of HS-DSCH_ReleaseDueToFailure ( = HS-DSCH_Drop) = Number of HS-DSCH allocation releases due to radio link and other failures# of HS-DSCH_AllocationSuccess = Number of allocations when the RNC has received RRC: Radio Bearer Re-Configuration Complete message from the UE after successful HS-DSCH MAC-d flow setup HSDPA Drop Rate shall be measured by data session activation (HSDPA) followed by ftp download

Only the peak throughput value recorded in the drivetests is consideredAM_RLC_PDU_Data(kb) ( = user data transferred)

Only the peak throughput value recorded in the drivetests is consideredAM_RLC_PDU_Data(kb) (user data transferred)

AM_RLC_PDU_Data(kb) (user data transferred)AM_RLC_PDU_Duration (session duration)

AM_RLC_PDU_Data(kb) (user data transferred)AM_RLC_PDU_Duration (session duration)

Only the peak throughput value recorded in the drivetests is consideredAM_RLC_PDU_Data(kb) ( = user data transferred)

AM_RLC_PDU_Data(kb) (user data transferred)AM_RLC_PDU_Duration (session duration)Inv estigated variations on:- MOU/drop for Voice Calls- Access failure rate for voice calls- Daily (24 hour) Voice Erlang Traffic

Seller shall ensure that introduction of the UMTS Network does not degrade Purchasers existing GSM Network performance by no more than (10%) ten percent. The method of calculation shall be as described in the UMTS Systems Acceptance (Appendix U16).

Imput Sources for The Tool Cluster Validation ModuleParameter Applied Operation# of RRC Connections Requests L3 Count All# of Connect CC_Alerting /Connect L3 Count All# of Call_Dropped L3, Event Count All# of Call Setup Success L3, Event Count All# of samples below BLER Target L3 Count All# of all BLER DL Samples L3 Count AllCellTrafficPower L3 Find BSS settingAvgRL PerCall L3 Calculate the Average ValuesAvgPowerPerRL L3 Calculate the Average ValueAS - Active Set (list of used AS, 1, 2.M) L3 Find BSS settingM = Maximum Active Set size used L3 Find BSS settingDuration(AS) L3 Count AllCC_Alerting(MOC) L3 Collect the TimestampRRC Connection Request(MOC) L3 Collect the Timestamp# of BLER samples below BLER Theshold L3 Count All# of all BLER DL Samples L3 Count All# of Activate PDP Context Accept L3 Count All# of FTP Downloads Success App Layer Count AllUL/DL User Data Transferred [kb] (Appl. layer - FTP) App Layer Calculate TotalUL/DL FTP Session duration [s] (Appl. layer - FTP) App Layer Calculate Total# of Activate PDP Context Accept Messages L3 Count All# of RRC Connection Requests Messages L3 Count All# of HS-DSCH_ReleaseDueToFailure ( = HS-DSCH_Drop) L3 Count All# of HS-DSCH_AllocationSuccess L3 Count AllPeak DL User data RLC throughput [Kb] L2 Find Max ValueTotal DL User data transferred [Kb] L2 Calculate TotalTotal Sessions duration [s] L3 Calculate TotalPeak UL User data RLC throughput [Kb] L3 Find Max valueTotal UL User data transferred [Kb] App Layer Calculate TotalTotal of Sessions duration [s] L3 Calculate TotalCSV MOU (from GSM CSV drivetest files) L3 Calculate Total

Source Layer (in work)

Load/Update the UMTS Acceptance Campain Drivetest Data from the Tool DT Repository (Market Level)

DT Files Consistency Checkup and Invalid DT Files Removal

Events Events Events Events Events Events Events EventsApp. L App. L App. L App. L App. L App. L App. L App. L

L3 L3 L3 L3 L3 L3 L3 L3L2 L2 L2 L2 L2 L2 L2 L2L1 L1 L1 L1 L1 L1 L1 L1

Cluster "Milestone-1" Acceptance Reporting

KPI Report at cell level

Cluster Level DT Data Parsing,Cluster DT Files Filtering,Invalid DT Files Removal

Cell Level DT Data Parsing,Cell DT Files Filtering,

Invalid DT Files Removal

DT Data parsing and re-combining per Session Type


UMTS CSD DT Data

UMTS PSD DT Data

UMTS HSDPA DT Data

UMTS HSUPA DT Data

GSM CSV

UMTS CSD DT Data

UMTS PSD DT Data

UMTS HSDPA DT Data

DT Data Mining - KPI input data filtering, counting, buffering, etc.


KPI Computation[Cluster Level]

KPI Computation[Cell Level]

Cell Level "Milestone-1" Acceptance Reporting

Cluster Pass/Fail Resolution (Decision)

Report

KPI Report at cluster

level

Optional: Display the Cluster Acceptance

on a map layerOptional: Display on a map layer

the KPI/cell

~ "Cluster Pass" / "Cluster Fail" Acceptance Report~ KPI Summary/Cluster Report ~ The count of Events/Event Type/Cluster Report ~ # of sample valid drivetest/scan sample points used per cell ~ Scanner Vs. Drivetest Coverage Statistical Report ~ On map display of the failed Clusters ~ Map layers: Events/Cell, Scanner Ec/Io on CPICH, Drivetest Ec/No on CPICH"

~ KPI Summary/Cell Report~ The count of Events/Event Type/Cell Report~ # of sample valid drivetest/scan sample points used per cell~ Map layer: Events/Cell(the data used is grouped as individual layers per cell)

Load/Update the UMTS Acceptance Campain Drivetest Data from the Tool DT Repository (Market Level)

DT Files Consistency Checkup and Invalid DT Files Removal

Events Events Events Events Events Events EventsApp. L App. L App. L App. L App. L App. L App. L

L3 L3 L3 L3 L3 L3 L3L2 L2 L2 L2 L2 L2 L2L1 L1 L1 L1 L1 L1 L1

Custom KPI Report

Cell Level DT Data Parsing,Cell DT Files Filtering,

Invalid DT Files RemovalCustom Area DT Filtering

(optional for future developements)



UMTS HSUPA DT Data

GSM CSV

UMTS CSD DT Data

UMTS PSD DT Data

UMTS HSDPA DT Data

UMTS HSUPA DT Data

GSM CSV



KPI Computation[Cell Level]

KPI Computation[Custom Level]

Cell Level "Milestone-1" Acceptance Reporting

Custom Area "Milestone-1" Acceptance Reporting

Optional: Display on a map layer the KPI/cell

Optional: Display the KPI/custom area

~ KPI Summary/Cell Report~ The count of Events/Event Type/Cell Report~ # of sample valid drivetest/scan sample points used per

~ Map layer: Events/Cell(the data used is grouped as individual layers per cell)

~ KPI Summary/Cell Report~ The count of Events/Event Type/Cell Report~ # of sample valid drivetest/scan sample points used per cell~ Map layer: Events/Cell

KPI Definitions and Formulas

KPI

Mile

ston

e 1?

Reference/Definition

2.0 % yes

CSV Drop Rate 2.0 % yes

CSV Quality (DL) yes

CSV Quality (UL)

Cell Capacity yes

1.6 yes

N/A no

yes

Pre-

Laun

ch

"Mile

ston

e 1"

Th

resh

old

Input data for Milestone 1:

[Drivetest Data only]

CSV Access Failure Rate

Access failure is the product of the RRC Connection Failure, NAS Setup Failure and the RAB Establishment Failure. RRC Connection Success is counted when the RNC receives a RRC Setup Complete from the UE. NAS Setup is considered successful when the signaling messages in the call flow during call setup flow is successfully completed by relevant Network Elements. A RAB is considered successfully established when the RAB Assignment Response is sent by RNC to the CN.


Circuit Switched Voice Drop measures the Networks inability to maintain a call. CSV Drop is defined as the ratio of abnormal speech disconnects, relative to all speech disconnects (both normal and abnormal). A normal disconnect is initiated by a RAB Disconnect RANAP message from the MSC at the completion of the call. An abnormal RAB disconnect includes Radio Link Failures, UL or DL interference or other reason and can be initiated by either UTRAN or CN.

# of Call_Dropped# of Call Setup Success

95th percentile of samples

2.0 % BLER


# of samples below BLER Target (BLER_DL 2%)# of all BLER DL Samples


2.0 % BLER

yes? (Q: is the UL

BLER data

available in DT?)



40 UE AMR 12.2k (provided it is achieved

in RF design)

Average number of Voice Calls (AMR 12.2) that can be supported by cell

CellTrafficPower AvgRL PerCall AvgPowerPerRL

Soft/Softer Handover Overhead

Soft/Softer Handover Overhead KPI provides an indication of how many Cells or Sectors were in the active set during the call on an average basis.

AS (list of used AS, 1, 2.M)M = Maximum Active Set size usedDuration(AS)

CSV IRAT Failure Rate

CSV Inter-Radio Access Technology Handover Failure = Hard Handover Failure rate from UMTS and GSM System for voice calls. = ratio between # of HO UTRAN Failures received by UE and # of HO UTRAN commands sent by UE

# of HO UTRAN Failures received by UE# of HO UTRAN commands sent by UE

*Voice Call Setup time (Mobile to PSTN)

95th percentile

6 seconds



CSVAccessFailureRate =100[1CSVCallsCCAlerting/ConnectCSVCalls

RRCConnectionRequest]

CSVDropRate=100CSVCalls

CallDropped

CSVCallsCallSetupSuccess

CSVAccessFailureRate =100[1CSVCallsCCAlerting/ConnectCSVCalls

RRCConnectionRequest]

CSVDropRate=100CSVCalls

CallDropped

CSVCallsCallSetupSuccess

yes

3.0 % yes

CSD Drop Rate 2.5 % yes

CSD Quality (DL) yes

CSD Quality (UL)

N.A no

2.0 % yes

PSD Drop Rate 2.5 % yes

N.A no RTT (Round Trip Time)

240 yes

*Voice Call Setup time (Mobile to Mobile)

95th percentile

9 seconds



CSD Access Failure Rate

Access failure is the product of the RRC Connection Failure, NAS setup failure and the RAB Establishment Failure. RRC Connection Success is counted when the RNC receives a RRC Setup Complete from the UE. NAS Setup is considered successful when the signaling messages in the call flow during call setup flow is successfully completed by relevant Network elements. A RAB is considered successfully established when the RAB Assignment Response is sent by RNC to the CN.


# of Call_Dropped# of Call Setup Success


1.0 % BLER


# of samples below BLER Target (BLER_DL 2%)# of all BLER DL Samples


1.0 % BLER

yes? (is the UL

BLER data

available in DT?)



*CSD Call Setup time

Circuit Switched Data call set up time indicates Network response time to a user request for a video service.


PSD Access Failure Rate

TSwitch Data access failure from a user perspective

# of Activate PDP Context Accept# of RRC Connections Requests

Packet session is considered as dropped when associated RAB has been released abnormally by either UTRAN or CN. Any drop after RANAP: RAB Assignment Response is considered as PS drop call.

# of FTP Downloads Success# of Call Setup Succes

*PSD Latency (any R99 RAB)

Round trip time for a 32 Bytes ping for any R99 PS RABIndicates maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP.

PSD R99 Average DL throughput (kbps) (Unloaded)



210 yes

200 yes

180 yes

N.A no

N/A no

N.A no

N.A no

2.0 % yes Table 41

HSDPA Drop Rate 3.0 % yes

*HSDPA Latency N.A no

PSD R99 Average DL throughput (kbps) (Loaded)



PSD R99 Average UL throughput (kbps) (Unloaded)



PSD R99 Average UL throughput (kbps) (Loaded)



*PSD Call Setup time

PSD call setup time indicates Network response time to a user request for a packet data service. In case of multiple RRC connection requests the first RRC connection request will be considered for KPI calculation.

PDP Context Activation accept (MOC)RRC Connection Request (MOC)

PSD IRAT Failure Rate

Inter-Radio Access Technology (IRAT) is a hard handover failure rate between UMTS and GSM = Hard Handover failure rate when a PS Data call (R99) fail to handover from UMTS network to GSM network

#CellChangeOrderFromUTRAN Failure(PS)#CellChangeOrderFromUTRAN Command(PS)

PSD IRAT Interruption time

Duration of interruption to Packet data service during Hard Handover (is an indicator of interruption time for the packet switch data during Inter-Radio Access Technology hard handover.)

TimeRAUpdateComplete_UETimeCellChangeOrder_RNC

PSD IRAT User Data Interruption time

Duration in seconds to interruption of Packet data service from User perspective during IRAT Hard Handover from 3G to 2G

TimeFirstPacketDataReceivedIn2GTimeLastPacketDataReceivedIn3G

HSDPA Access Failure Rate

# of Activate PDP Context Accept Messages# of RRC Connection Requests Messages

HSDPA session is considered as dropped when associated HS-DSCH has been released abnormally by either UTRAN or CN. This test will be done with a single UE performing HSDPA call in the Cell under test with 384/64 Kbps associated DCH on the uplink and HS-DSCH in the DL with downgrade/upgrade to/from R99 RAB.

# of HS-DSCH_ReleaseDueToFailure ( = HS-DSCH_Drop)# of HS-DSCH_AllocationSuccess

Round trip time for a 32 Bytes ping for HSDPA NRT RAB

1300 yes

1100 yes

700 yes

600 yes

1100 yes

500 yes

N.A no Table 51

N.A no Table 53

N.A no Table 55

10 % yes

Stationary Maximum DL HSDPA Bit Rate (kbps) under no load (UE Category 12)


Peak DL User data RLC throughput [Kb]

Stationary Maximum DL HSDPA Bit Rate (kbps) with 50% DL loading (UE Category 12)


Peak DL User data RLC throughput [Kb]

HSDPA Average DL Throughput (kbps) for UE category 12 under no load



HSDPA Average DL Throughput (kbps) for UE category 12 under 50% DL loading



HSUPA Stationary Peak throughput (kbps) for UE Category 3 (1.45 Mbps)


Peak UL User data RLC throughput [Kb]

HSUPA Stationary Average throughput (kbps) for UE Category 3 (1.45 Mbps)


Sum of all UL User data transferred [Kb]Sum of Sessions duration [s]

*HSDPA Session Activation time

*Average Cell Availability KPI

*Average Cell Non-Maintenance Availability KPI

GSM Performance Degradation due to Introduction of UMTS

The deployment of the UMTS Network shall not degrade Purchasers existing GSM Network performance. Excluding IRAT Hard Handover Feature, both UMTS and GSM Networks are considered independent of each other. This section addresses any concern related to UMTS Equipment installation on GSM Sites and related faults for which Seller has responsibility that could degrade GSM performance.

CSV MOU (from GSM CSV drivetest files)# of Call_Dropped (GSM CSV)# of Call Setup Success (GSM CSV)# of RRC Connections Requests ( GSM UL L3 Messages)# of Connect CC_Alerting /Connect (GSM DL L3 Messages)

Data Input Details

Use

DT

Sess

ion

files

:

Measurement Condition:Drivetest output data from CSV Calls onlyIn the event that there are several consecutive RRC Connection Request only the first RRC connection request shall be taken into account for the KPI calculation. Calls are considered as failed during access when a connection is attempted and the UE does not receive Alerting/Connect message in case of drive test measurement. For OSS RANAP: RAB Assignment Response message from the RNC to core Network is considered as a call successful setup. UMTS

CSVMeasurement Condition: Drivetest output data from CSV Calls onlyAny CSV call successfully handed over from 3G to 2G network within the CSV Service Area shall be considered as drop call for Milestone 2.

UMTS CSV

This KPI shall be measured at 1% BLER operating point set in UTRAN for voice call. BLER shall be available using counters with Cell Level granularity. KPI for MS3 shall be calculated at Market Level. For MS3, DL BLER shall be measured using RES counters or drive test as required.

UMTS CSV

UL BLER is collected and presented in the MRR-W (Measurement Results Recording WCDMA) feature in OSS-RC UMTS

CSVCSV Cell Capacity shall be calculated based on average DL power allocated to AMR 12.2 RB for this KPI. CellTrafficPower = Net DL Power available in a cell to carry user traffic and is equal to total cell carrier RF power (at system reference point) minus Common/signaling channe

umts_kpi

Documents