BCR 3.0 Kpi

This spreadsheet presents the results form the BCR3.
0 KPI AT&T subset
The spreadsheet contains multiple worksheets which will increase when test cases and results/KPI's are completed and a
There are 3 main worksheets:

1. Summary - this worksheet provides an overview of progress
2. BCR3.0 KPI - this worksheet contains detailed development progress and execution results for KPI's and lin
3. KPI-3.0-xyz - these spreadsheets provide additional information for individual KPI test cases such as test sta
Not planned test cases are KPI's that have been excluded from the BCR2.4 KPI subset as these are not required for AT&T
BCR 3.0 KPI Te st Case De velopm e nt
BCR 3.0 KPI Ex
Developed Untested
20%
Developed 10 iteration tested

Developed Partially Tested
In progress
Blocked
11%
Not Possible
69%
Not Planned
100%
esults/KPI's are completed and available
xecution results for KPI's and links to test reports in html and iTest formats
al KPI test cases such as test statistics generated in iTest
s these are not required for AT&T

BCR 3.0 KPI Execution Res ults
Fail
Pass
Not Planned
Remaining
inProgess
NotPossible
100%
AT&T
Feature Number
Test Name
FTS-118617
From BSR Femto to 3G Macro Network Intra

R2
Frequency in handover region for PS and CS+PS, with
MAHO
Requirement 118617 Number
FTS-118617
From BSR Femto to 3G Macro Network Inter

R3
Frequency in handover region for PS and CS+PS, with
MAHO
FTS-118617
Macro to Femto HO success rate Handover

success rate for PS and CS+PS
R7
FTS-118617
From BSR Femto to 2G Macro Network

InterRAT (Cell Change Order) in handover
region
R8
FTS-118617
Macro to Femto mean interruption time during

the handover phase for PS and CS+PS
R9
FTS-118617
Femto to Macro HO mean interruption time

during the handover phase for PS and CS+PS
R10
FTS-118617
Voice Speech Quality - AMR 12.2 kbps Femto

Mobile to PSTN/ISDN for 24/32 simultaneous
calls
R13
FTS-118617
Voice Speech Quality - AMR 12.2 kbps Femto

Mobile to Femto Mobile for 24/32 simultaneous
calls
R14
FTS-118618
CS Data Call Set up Time (UMTS signaling only)
R15
FTS-118619
Test Requirement:
FTS-77715 (BCR 2.2) R12
The
mean interruption
time during PS or CS+PS
FTS-106897
(BCR 2.4) R46
handover phase
R16
FTS-118620
PS Drop Call Rate
R17
FTS-118621
R99 PS DL User Throughput
R18
FTS-118622
R99 PS UL User Throughput
R19
FTS-118623
Two Simultaneously HSPDA User Throughput
R20
FTS-118624
Four Simultaneous Voice calls
R21
BCR2.5
y
FTS-120107
SSCP setup success rate (without support of new PM

counters
R5
FTS-120107
HSUPA RB setup success rate
R6
FTS-120107
Macro 2G to Femto network handover success rate

for CS
R7
Requirement: FTS-77715, FTS-83234, FTSbetween

Femto and 3G
network..
(VS.AttIntraFreqMAHOFemto3GMacroCS
106897,
FTS-120107,
FTS-118617
The
percentage of failed handovers should/be
-VS.SuccIntraFreqMAHOFemto3GMacroCS)
R9
Test
KPI-3.0-003
<
1%.Ref:
VS.AttIntraFreqMAHOFemto3GMacroCS
Macro
to Femto
Mean Interruption time during
Test Ref:
KPI-3.0-004
Requirement:
FTS-77715,
FTS-83234, FTSDefinition
Test
Ref: KPI-3.0-006
the
handover
phase
for PS FTS-83234, FTSRequirement:
FTS-77715,
106897,
FTS-120107,
FTS-118617
Femto
3G Macro
Network
Inter
Frequency
Requirement:
FTS-77715,
FTS-83234,
FTSThis
KPItomeasures
the
typical
interruption
time
106897,
FTS-120107,
FTS-118617
R7
Mobile PS
Assisted
CS Handover
Failure
Rateto=
106897,
FTS-120107,
FTS-118617
during
handover
from
Macro
network
R8
Macro
Handover Success Rate
100* to Femto PS
R10
Femto
to
3G
Macro
Network
Femto.
Femto
toprovides
2G Macro
PSpercentage
Blind Handover
Success
This
KPIto
the
of successful
(VS.AttInterFreqMAHOFemto3GMacroCS
Femto
Macro
HO
mean
interruption
time
Intramean
Frequency
in handover
region be
for <
CS+PS,
The
interruption
time should
200
Rate
within
handover
region
PS
handovers
between
Macro
Femto. /
-VS.SuccInterFreqMAHOFemto3GMacroCS)
during
the handover
phase
forand
CS+PS
with
MAHO
ms
This percentage
KPI
defines of
thesuccessful
percentage of successful
The
this
VS.AttInterFreqMAHOFemto3GMacroCS
This
KPI measures
the typical handovers
interruptionoftime
Handover
failure
rate.
Definition
Femto
to 2G
Macro
Blind PS Handover
type
should
be
>
98%.
during
from
Femto
to since
Macro
provides
the percentage
of failed
Intra
This
KPICS+PS
is
not handover
measured
via counters,
the
operations
Definition
Network.
Frequency
Mobile
Assisted
CS+PS
handovers
measurement
is
actually
at
the
UE.
The
performed
(these
by
the Inter-RAT
Macro
3G to
Femtoare
PStriggered
Handover
Success
Rate
Test
Ref:
KPI-3.0-016
The mean
interruption
should
be < 200
between
Femto
and 3Gtime
network.
handover
Cell
Change
Order).
=
Requirement:
FTS-77715,
FTS-83234,
FTS-be
Femto
tohandovers
3G
Macro
Network
ms
The
percentage
of
failed
should
commences
when
UE
receives
an
RRC
The
percentage
of the
successful
handovers
of this
100
*Frequency
106897,
FTS-120107
R5
Inter
in handover region message.
for CS+PS,
Definition
< 1%.
RADIO
BEARER
RECONFIGURATION
type
should
be >
98%.
(VS.HHO.Succ3GMacroToBsrPSHO/VS.HHO.Att3
with
MAHO
Definition
The
PS
data handover interruption period will
Definition
GMacroToBsrPSHO).
Handover
failure
rate.
start
when
the
UE
stops
receiving
RLC
PDUs
Femto to 2G Macro PS Blind Handover Success
This
KPI provides the percentage of failed Inter
and
Rate =
Frequency
Assisted
KPI is CS+PS
not
will
finish atMobile
the This
resumption
of measured
the Handovers
PDUs. via
100*(VS.SuccInterFreqBlindFemto2GMacroHOP
Macrothe
to Femto
CS+PS Handover
between Femto
and
3G network..
counters,
since
measurement
is actually
at
Femto
to 3G Macro
Network
S/VS.AttInterFreqBlindFemto2GMacroHOPS)
Success
Ratehandover
The UE.
percentage
of failed
handovers
should
be
the
The
Intra
Frequency
Mobile
Assisted
CSPS
Handover
Test
Details
Test
Description:
Incoming
SCCP Setup
Success
<
1%.
commences
when
the UE receives
an RRC
Failure
Rate =
100
Rate
Definition
RADIO
BEARER RECONFIGURATION
message.
* (VS.AttIntraFreqMAHOFemto3GMacroCSPS
Macro
Femto Mean
UEtoAssisted
Femto
to 2G
This
KPIperiod
Femto
to 3Gdata
Macro
Network
Inter
Frequency
The
CS+PS
handover
-VS.SuccIntraFreqMAHOFemto3GMacroCSPS)
Interruption
time
during
theinterruption
handover
phase
Macro
PSthe
Handover
Success
Rate within
provides
percentage
of successful
CS+PS
Mobile
Assisted
CSPS
FailureRLC
Rate =
will
start
when
the
UE Handover
stops
receiving
/ VS.AttIntraFreqMAHOFemto3GMacroCSPS
for
CS+PS
handover
region
handovers
between
Macro
and
Femto.
Thistypical
KPI provides
the time
100 KPI measures the
PDUs
This
interruption
This
KPI defines the
percentage
of successful
The
percentage
succecssful
handovers
of
percentage
of at
Iuof
connections
which
were
*during
(VS.AttInterFreqMAHOFemto3GMacroCSPS
and
willCS+PS
finish
the
resumption
of the
PDUs.
handover
from
Macro
network
to
UE assisted
Femto
2G
Macro
PS Handover
this
type
beto
>
98%.
successfully
set HO
up
at
the BSG
-VS.SuccInterFreqMAHOFemto3GMacroCSPS)
Femto
to should
Macro
mean
interruption time
Femto.
operations
performed
(these
are
triggered
by
Definition
/ VS.AttInterFreqMAHOFemto3GMacroCSPS
(where
Iu connections
are
terminated)
in200
during
the
handover phase
for
PS be <
The
mean
interruption
time
should
the
Inter-RAT
Cell Change
Order).
Macro
3G
to requests
Femto
CS+PS
Handover
Success
response
to
coming
from
the
SGSN.
This
KPI
measures
the
typical
interruption
time
ms
The
percentage
of successful handovers of this
Rate
= PS handover
The KPI
during
from Femto to Macro
Definition
type
be > 98%.
100 *should
(VS.HHO.Succ3GMacroToBsrCSPSHO
/
does
not
between
Iu-IP or Iu-ATM
Network.
This
KPI
isdistinguish
not measured
via counters,
since the
Definition
VS.HHO.Att3GMacroToBSRCSPSHO).
connections.
The
mean interruption
time
should
< 200
measurement
is actually
at the
UE. be
The
Femto
to 2G Macro
PS Blind
Handover
Success
This
ms KPI measures the success of setting up Iu
handover
Rate =
connections
theUE
Femto
Gateway.
Definition
commences within
when the
receives
an RRC
100*(VS.SuccMAHOFemto2GMacroPS/VS.AttMA
This
success
should exceed
99%.
KPIBEARER
is notrate
measured
via counters,
since the
RADIO
RECONFIGURATION
message.
HOFemto2GMacroPS)
Definition
measurement
is
actually
at
the
UE. Theperiod
The CS+PS data handover interruption
Incoming
SCCP the
Setup
Rate = RLC
100 *
handover
will start when
UE Success
stops receiving
VS.SuccIncomingSCCPReq
/
commences when the UE receives
an RRC
PDUs
Test
Ref: KPI-3.0-007
VS.AttIncomingSCCPReq
RADIO
message.
and willBEARER
finish atRECONFIGURATION
the resumption of the
PDUs.
Requirement:
FTS-77715,
FTS-83234,
FTSThe PS data handover
interruption
period
will
106897,
FTS-120107,
FTS-118617
start when
the UE stops
receiving RLC PDUs
R13
and
Test
Ref:
KPI-3.0-008
Voice
Speech
Quality
-SCCP
AMR 12.2
kbps
Femto
Outgoing
Setup
Success
will finish
at the
resumption
of the
PDUs.
Requirement:
FTS-83234,
FTSMobile to PSTN /FTS-77715,
ISDN for 24/32
simultaneous
Rate
106897,
FTS-120107,
FTS-118617of Iu
calls
This KPI provides
the percentage
R14
The mean Voice
Speech
MOS value
Connections
which
were quality
successfully
set upin
Voice
Speech
Quality
- AMR 12.2 kbps Femto
this
case
be >=3.5
within
theshould
Mobile(and
to Femto
forin24/32
simultaneous
SGSN
IPC if Mobile
present)
response
to
calls
requests originating from a BSG. The KPI does
The
not mean Voice quality MOS value in this case
should be >=3.2
distinguish
between Iu-IP or Iu-ATM
Test Ref:KPI-3.0-009
connections.
Requirement: FTS-77715 R12, FTS-106897
R15
Test Description: R15 CS DataThis
CallKPI
Set up
Test
KPI-3.0-010
Time Ref:
(UMTS
signaling
measures
the
success only)
of setting up Iu
Requirement:
FTS-83234
R3,
FTS-106897
R16
The call setup
delay
is defined
as
the time
connections
associated
with
a particular
BSG
Test
Description:
Femto
Femto
required
establishR16
a CS
data to
call
from mean
a
within
thetoSGSN.
interruption
time
during
PS
or
CS+PS
handover
UMTS
This success rate should exceed 99%.
Test
Ref: KPI-3.0-011
phase
mobile to another UE in the same UMTS
Definition
Requirement:
FTS-77715
FTS-106897
R17
The
meanThe
interruption
timeR5,
during
PS
CS+PS
network.
delay
assumes
both
mobiles
Outgoing
SCCP
Setup
Success
Rate
= or
100
*are
Test
Description:
R17 PSisDrop
Call Rate (2
Femto
to Femto
handover
attached
to the same
MSC./ < 200ms
VS.SuccOutgoingSCCPReq
mins
duration, excludes coverage cause)
(downlink)
Starting
event:
Originating
UE
sends
VS.AttOutgoingSCCPReq
Test
Ref:
KPI-3.0-012
PS
drop
call
rate
is defined
as the on
total number
and
< 300
ms
(uplink)
measured
CCCH:RACH:RRC
Connection
Requestthe
on voice
first
Requirement:
FTS-77715
R18
of
abnormally
released
and
packet user
planes.PS RAB over the total
Preamble
Test
Description:
R18
R99
PS DL User Overall
number
of Successful
RAB
Establishments
The
handover
can
beRate
identified
as having for
Finishing
event:
Originating
UE
receives
SCCP
Setup
Success
Throughput
PS.
commenced
when
the
UE
receives
an
DCCH:DCH:Direct
Transfer
Alerting
response
Test
Ref:
KPI-3.0-013
This
KPI
provides
the
percentage
oflayer
Iu
Average
downlink
user
application
PS
drop call
rate shall
be
less than
0.6% with a
rrc_radioBearerReconfiguration
message
The
total UEfor
to
call
setup
delay
shall
Requirement:
FTS-77715
R19
Connections
which
were
successfully
setbe
upless
throughput
4UE
simultaneous
users,
Notes:
new_U_RNTI.
than 6s
(mean)
10 s(95%ile
) User
Test
Description:
R19
R99 PS UL
through
a with and
configured
128
Compliance
with
this
KPI
should
be
based
on a
The PS
data
handover
period
will
Test
Ref:
KPI-3.0-017
Notes:
This
requirement
supercedes
FTS-for
Throughput
particular
BSG.
This
KPIinterruption
does
not
distinguish
kbps
RAB,
shall
be
larger
than
110
kbps
normalised
call UE
duration
of 2FTS-83234,
minutes
start
when
the
stops
receiving
RLC(e.g.
PDUs
Requirement:
FTS-77715,
FTS-a 60
Test
Ref:
KPI-3.0-014
77715-581
(related
to
R2.2
R11).
Average
uplink
user
application
layer
between
Iu-IP
or
Iu-ATM
connections.
each
user.
FTP
downloading
file size
shall
be 10
minute
call
would
be
equivalent
to
30
2
minute
and
106897,
FTS-120107
R6
Requirement:
FTS-77715
R5,success
FTS-106897
R20
throughput
for 4,
2the
simultaneous
users,rate of
This
KPI measures
overall
Iu
Mbytes.
calls).
will finish
the
resumption
the PDUs. BSG
HSUPA
RBat
setup
success
rateof
Test
Description:
R20 with
Two
Simultaneously
configured
connections
with
associated
64,
a particular
Reference
[VF_GRS]
CAP_KPI_001
This
is not
a Throughput
new KPI;
it simply qualifies
an
Note
This
KPI
provides
thebe
percentage
of55,
RAB
HSPDA
User
128
kbps
RAB,
shall
larger
than
110
irrespective
of whether
the
This
was
originally
added
asconnections
FTS-77715-873..
existing
KPI
(FTS-77715-867
R2.2
R5)
to
Test
Ref:
KPI-3.0-015
QUALCOMM
UE
LOG_CODE
0x4134
(WCDMA
attempts
mapped
on
E-DCH
tranport
channel in
Average
user
downlink
application
kbps
for each
user
respectively.
FTPlayer
originate
at
the
BSG
or
the SGSN.
clarify
Requirement:
R5, HSPDA
FTS-106897
RLC
DL
AM PDU)
provides
information
UL
throughput
for
2FTS-77715
simultaneous
usersR21
downloading
This
success
rate
file
should exceed
99%. on
some
assumptions
how
KPI should be
Test
Description:
R21
Four
Simultaneous
received
number
ofon
PDUs
. this
which
succeed
on
RAB
assignment
shall
be
size
shall
be 10based
Mbytes.
Definition
tested.
Voice
calls
This requirement
supercedes
FTS-106897-1575
procedure.
RABs
mapped
onuser.
E-DCH
larger
than
2 Mbps
for
each
FTP
Reference
[VF_GRS]
CAP_KPI_002.
Overall
SCCP
Setup
Success
Rate
= transport
100 *
Throughput
indicated
by FTS-77715-523
shall
(related
to R2.4
channel
downloading
fileR4)..
size shall
be
(VS.SuccOutgoingSCCPReq
+ 50 Mbytes.
be
met
with
4 simultaneous
voice
calls.
are
considered
if either
initially
attempted
Note:
The
following
conditions
to thison
KPI
VS.SuccIncomingSCCPReq)
/ apply
Voice
quality
(MOS) indicated
by
FTS-77715E_DCH
or
configured
as
E-DCH
during
the
RAB
CQI>16
for
Category
8
UE
with
10
codes.
(VS.AttOutgoingSCCPReq +
582
shallfor
beCategory
met with64UE
simultaneous
voice
assignment
procedure.
Note:
Normal
call
CQI>19
with
5 codes.
VS.AttIncomingSCCPReq)
Test
Ref:
KPI-3.0-018
calls.
release
during
the procedure
will impact the
Reference
[VF_GRS]
CAP_KPI_003.
Requirement:
success ratio. FTS-77715, FTS-83234, FTS106897,
FTS-120107
R7
This success
rate should exceed 99%.
Macro 2G to Femto network handover success
rate for CS
This KPI provides to percentage of successful
handovers from 2G Macro to Femto.
This success rate should exceed 99%.
Development
Run 1
Test Area
Test case Developed in iTest Validation details
Pass/Fail
Result
Mobility - Cell Reselection
Test case has been run

successfully with 10
iterations
Pass
0%
Mobility - Femto To 3G - Inter

iterations
Pass
0%
U-Dragon issue
Pass
100%
Mobility - Inter RAT
U-Dragon issue
Pass
100%
Mobility - Femto To 3G - Intra
Result to be checked
manually
Pass
114ms
120ms
manually
Pass
187ms
196ms
Voice Quality

iterations
Pass
3.6900
Voice Quality

iterations
Pass
3.8100
Call-P

iterations
Pass
5.3878s
Mobility - Femto To Femto
manually
Pass
173 DL
190 UL
PS Data HSDPA & R99

iterations
Pass
0%
PS Data - R99

iterations
Pass
122kbps
PS Data - R99

iterations
Pass
59kbps
PS Data HSDPA

iterations
Pass
UE1: 3.2 Mbps

UE2: 3.74 Mbps
QC chipset
U900 and QC
6695
Voice Quality

iterations
Pass
3.9990
Availability
manually
Pass
100%
Availability

iterations
Pass
100%
U-Dragon issue
Pass
100%
FTS-120107
RRC redirection to macro success rate
R8
FTS-120107
Service based handover to macro success rate
R9
FTS-120107
Radio Bearer Reconfiguration Success Rate
R10
FTS-120107
Call Release Time- Mobile to PSTN
R13
FTS-120107
Call Release Time- Mobile to Mobile
R14
FTS-120107
Recovery Time - Link Loss
R15
FTS-120107
Recovery Time - Power Loss
R16
FTS-120107
Provisioning Time: Boot to Assign CGI (may delete,

Dave to check with Akhilesh)
R19
FTS-120107
XY Lock Time: Time from AP Plugged in to XY Location R20

Assigned (only applies to AP with GPS)
BCR2.4.1
y
FTS-106897
Femto to Femto CS handover failure rate
R2
FTS-106897
Femto to Femto PS and CS+PS call handover failure

rate
R3
FTS-106897
Cell reselection failure for a UE moving from one

femto to another femto which are within the same
group
R5
FTS-106897
HSDPA
avg thoughput % of peak on air interface
Test Requirement:
(measured
FTP 2.4)
application)
FTS-106897at(BCR
R5
R6
FTS-106897
R7
FTS-106897
HSUPA Mean User Data Rate [kbit/s]

avg thoughput on air interface (measured at FTP
application) for the aggregate cell with IPsec
encryption activated
Time For Arrival of femtocell Notification at UE
Test Requirement:
FTS-106897 (BCR 2.4) R7
FTS-106897
Time For Deletion of femtocell at UE on Leaving BSR

Femto CPE Coverage
R9
FTS-106897
Test Requirement:
Voice calls connection times
R10
FTS-106897
R99 PDP context activation connection time
R11
FTS-106897
HSxPA PDP context activation connection time
R12
FTS-106897
Macro to Femto HO success rate Handover success

rate
R13
FTS-106897
Macro to Femto HO mean interruption time during the R14

handover phase
R8
106897, FTS-120107
R8
RRC Redirection to macro success rate
This KPI provides the percentage of successful
RRC redirection attempts from a Femto BSR to
the
Test
KPI-3.0-020
macroRef:
network.
Test
Ref: KPI-3.0-021
Requirement:
FTS-77715,
FTS-83234,
This success rate
should exceed
99%. FTSRequirement:
FTS-77715, FTS-83234, FTS-R9
106897,
FTS-120107
Definition:
106897,
FTS-120107
R10
Service
based
handover
macro success
rate
RRC Redirection
to MacrotoSuccess
Ratio = 100
Radio
Bearer
Reconfiguration
Success
Rate
This
KPI
provides
the percentage
of +
successful
*Test
((VS.SuccActiveCallReDirectUMTS
Ref:
KPI-3.0-022
This
KPI
provides
the percentage
of
successful
service
based
handover
attempts
from
Femto
VS.NumSuccActCallBRM
+ FTS-83234, FTSRequirement:
FTS-77715,
performed
RB reconfigurations
from UE pointBSR
VS.NumSuccCallRedirectBRM
+
106897,
FTS-120107
R13
ofview
to
Macro
VS.SuccActiveCallRedirect2G)
/
Test
Ref:network.
KPI-3.0-023
Call
Release
time - mobile to PSTN
from
the attempts.
This
success
rate
should
exceed
99%. FTS(VS.NumAttCallRedirectBRM
+
Requirement:
FTS-77715,
FTS-83234,
This
KPI
represents
the
time
between
the
NAS
The number
of successful Radio Bearer
Test
Ref: KPI-3.0-025
Definition:
VS.NumAttActCallBRM
+ and the
106897,
FTS-120107
R14
request
to
release
call
reconfigurations
is adefined
as
the difference
Requirement:
FTS-77715,
FTS-83234,
FTSService
Based
Handover
VS.AttActiveCallReDirectUMTS
+ Success
Call
Release
time
- mobiletotoMacro
mobile
acknowledgement
between
the*
106897,
FTS-120107
R16
RatioKPI
= 100
VS.AttActiveCallReDirect2G))
This
represents
the time
between
the NAS
that
the
radio
resources
have
been
released
for
number
ofTime
attempted
reconfigurations
and
Recovery
- PowerRB
Loss
((VS.HHO.SuccCSServiceBased2GHO
+
request
to
a call and
the
that
call
forrelease
aofcall
between
athat
UE connected
to a
the
number
failed
RB
reconfigurations
where
This
KPI
measures
the
time
the
Femto
BSR
.HHO.SuccCSServiceBased3GHO) /
acknowledgement
Femto
BSR
and
a
UE
connected
to
the
PSTN.
a
takes
to reestablish communication+with the
(VS.HHO.AttCSServiceBased2GHO
that
the release
radio resources
have to
been
released for
The
call
time
(mobile
PSTN)
failure
is definedfollowing
as any
reconfiguration
Femto
Gateway
a power
loss.should
.HHO.AttCSServiceBased3GHO))
that
call
for
a6call
between a UE connected to a
be
than
seconds.
Test
Ref:
KPI-3.0-026
operation
which
does nottime
result
an
Theless
power
loss
recovery
forinareceit
FemtoofBSR
Femto
BSR
and
a
UE
connected
to
the
The start
for
the
KPI12
is minutes.
defined as macro
the
Requirement:
FTS-77715,
FTS-83234,
FTSRB
should
betime
no
more
than
Test
Ref:
KPI-3.0-024
network.
Test
Ref:
KPI-3.0-027
point
where
the Complete
NAS:
Disconnect
message
is
106897,
FTS-120107
R19
Reconfiguration
message.
The
time
should
be
measured
from
the
point
Requirement:
FTS-77715,
FTS-83234,
FTSThe
call release
time
(mobile
to mobile)
should
Requirement:
FTS-77715,
FTS-83234,
FTSreceived
Provisioning
Time:
Boot
toexceed
Assign
CGIby the
This success
rate
should
99%.
where
a link
loss
has
been
detected
106897,
FTS-120107
R15
be
less
than
8
seconds.
106897,
FTS-120107
by the
cell.
This
KPIsmall
measures
the time that a Femto R20
gateway,
Recovery
TimeTime
- Link
Loss
The
startTime:
time
for
the
KPIais
is
defined
as
the
XY
Lock
from
AP
Plugged
inthe
to point
XY
The
end
time
for
KPI
defined
as
network
takes
to the
assign
CGI
unique
and
power
is re-provided
to
theorFemto
to the
This
KPI
measures
theDisconnect
time
that
the
Femto
BSR
point
where
the
NAS:
message
is
Location
Assigned
wherewhere
thetoIuathe
Release
Complete
Message is sent
identifier
point
Femto
is fully functioning
takes
to measures
reestablish
communication
with the
received
This
time
that
a Femto
BSR
fromKPI
the
small
tonot
the
gateway.
Femto
BSR
thatcell
hasthe
been
previously
again.
Femto
Gateway
in
thesend
caseitsofXY
a link loss. back
by theto
small
takes
acquire
and
connected
tocell.
the
Femto
network,iflocation
or
a Femto
Femto
Note:
This
KPI
is only
applicable
the
The
link
loss
recovery
time
for
a
Femto
BSR
The
end
time
for
the
KPI
is
defined
as
the
point
to
BSR previously
that has been successfully in service
has
(i.e.
should
be no
more than
3could
minutes.
where
the
Iu
Release
Complete
Message
isbut
sent
the
Femto
Gateway.
This
be
a BSR that
been
previously
connected
to the
network
the
The not
time
should
beto
measured
from to
thethe
point
from
the
small
cell
the
gateway.
has
been
previously
connected
for
some reason
needs abeen
new CGI
oscillator
hasloss
previously
fullyassigned.
disciplined)
where
a
link
has
been
detected,
and
the
network,
The
duration
of this
should notare
exceed
32
and
the Femto's
NTPKPI
parameters
recent.
linkone
is
or
that has previously been connected to
minutes.
This
reconnected
to the
point
where
the
Femto
is
the network
but
for
some
reason
needs
towith
reOpen
Issue:
This
KPI
is
still
under
debate
KPI
does
not
apply
if
the
Femto
has
been
fully functioning again.
acquire
AT&T.
Since
cannot
be assigned
until
theand
switched
off CGI
for an
extended
period of
time
and
send
a
new
XY
location.
oscillator
has been disciplined, it is not clear
has to
The
duration
of this
KPI should not exceed 20
that
this aKPI
can
be met.
perform
cold
start
to re-discipline the
minutes.
The time should
be measured from the point
oscillator
behaviour.
Open
This
KPIisisbooted
still under
debate
whereIssue:
a Femto
BSR
for the
first with
time
AT&T.
to the Since XY location cannot be measured
until
oscillator
has been
disciplined,
is not
pointthe
where
the gateway
completes
the it
assign
clear
that this KPI can be met.
CGI interaction.
The time should be measured from the point
where the Femto BSR is booted to the point
where the
XY location is sent to the Femto gateway.
Test Ref: KPI-3.0-028 old KPI-2.4-039
Requirement: FTS-83234 R4, FTS-106897 R2
Test Description: This KPI should have the
following pre-requites in place. Two Femtos
Test
Ref: KPI-3.0-029
KPI-2.4-040
appropriately
configuredold
such
that each others
Requirement:
R2, FTS-106897
details are in theFTS-83234
intra-frequency
lists. It is R3
Test
Description:
This
should
have the
assumed
that as this
is aKPI
Femto
to Femto
following
in place. Two Femtos
handover pre-requites
this will be intra-frequency.
An
Test
Ref: KPI-3.0-030
KPI-2.4-032
appropriately
configuredold
such
that each
others
automated controllable
attenuation
system
is
Requirement:
R5 lists. It is
details
incan
theFTS-106897
intra-frequency
in placeare
and
control
Femto 1 and
Femto 2
Test
Description:
An
automated
UE
is
logged
assumed
thatUE.
as this
a Femto tocontrol
Femto
signal to the
The is
attenuation
is set
and
monitored
andbe
cell id is checked toAn
verify
handover
this UE
will
such Ref:
that the
can intra-frequency.
only see
the Femto 1 and
Test
KPI-2.4-016
that
the UEKPI-3.0-031
serving cellold
is Femto
1. system
Next the
automated
controllable
marginally see
Femto
2,attenuation
or R16,
not see
Femto 2isR6
at
Requirement:
FTS-77715
FTS-106897
automated
attenuation
adjusts
the 2
in
place
and
can
controlsystem
Femto
1
and Femto
all.
Next
the
automated
UE
is
placed
into
CS
Test
Description:
Automated
HSDPA 2PS a
call
attenuator
1 (Femto
1)attenuation
and attenuator
signal
to the
The
control is set
voice
call
andUE.
once
the
call
hasOnce
been
is
performed
on
1
Femto
cell.
the
HSDPA
(Femto
2) the
such
that
Femto
2 isthe
better
such
that
UE
can
only
Femto
1 and
successfully
held
for approximately
10 seconds
Test
Ref:
KPI-3.0-032
old see
KPI-2.4-017
bearer
is established
an
automated
candidate
than
Femtothen
1 and
ensures
thatFTP
the
marginally
see Femto
2,
orfaded
not
Femto
2 at
the attenuators
are
cross
such
that
the
Requirement:
FTS-106897
R7 see
session
is started
and
connected
to be
the
data
reselection
criteria
is met.
Test
will
divided
all.
Next
the
automated
UE
is placed
into
a PS
neighbouring
Femtowithin
2 is a
better
candidate,
Test
Description:
Automated
HSUPA
server
(FTP
server)
the
test
evenly
between
intra and
inter-frequency.
Such
call
and
data
transfer
started
e.g.
FTP,
Ping
etc.
quality
(Ec/No),
and
signal
strength
(RSCP)
(Category 3 UE,
1.46Mbps)
PS call
is performed
environment.
After
connection
is
established
that
50%
reselection
attempts
will
be
intraonce
the serving
call
has Femto
been
successfully
held
forUE
Test
Ref:
KPI-3.0-033
old
KPI-2.4-033
than
the
1. HSUPA
The automated
on
1 are
Femto
cell.
Once
the
bearer
files
repeatedly
downloaded
from
the is
data
frequency
and 10
50%
inter-frequency
Femto
approximately
seconds
the
attenuators
are
Requirement:
FTS-77715
R29,
FTS-106897
should
maintain
the
CS
voice
call
and
correctly
established
then
an
automated
FTP
session
isR8
server
(FTP server)
and
times/data rate
reselection.
Where
inter-frequency
reselection
cross
faded
such
that
the
neighbouring
Femto
Test
Description:
This
should
have
the
handover
to
Femto
2
and
continue
to
maintain
started
and
connected
toKPI
the
data
(FTP
recorded.
All
DL throughputs
arenoise
toserver
be
is
tested
the
test
may in
require
source
2
is
a better
quality
and isto
following
pre-requites
place.a(Ec/No),
A UEAfter
which
the
call
for
atcandidate,
least
30 seconds
once
the
server)
within
theapplication
test
environment.
measured
at
FTP
layer
(includes
interfere
with
the
serving
cell
to serving
reduce
the
Test
Ref:
KPI-3.0-034
old
KPI-2.4-034
signal
strength
(RSCP)
than
the
Femto
automated
and
can
also
be
power
cycled
orthe
handover
is
We
can
verify
connection
iscompleted.
established
files
are
repeatedly
TCP,
RLC,
RF
overheads)
over
entire
filethatthe
quality
(Ec/No)
of
the
serving
cell
to
force
Requirement:
FTS-106897
R9
1.
automated
UE
should
maintain
the
PS
mode
a server
controllable
attenuation
UE The
haschanged
performed
the
handover
onto
the
uploaded
to theand
data
(FTP
server)
and
transfer
period.
intent
is
to measure
the
UE
to
reselect
toThe
Femto
2.
Both
Femto
1and
Test
Description:
This
KPI
should
have
the
call
and
correctly
handover
to
Femto
2 Next
and
system
and
a Femto
with
MM
Information
correct
Femto
by
checking
the
cell
id.
the
times/data
rate
recorded.
All
UL
throughputs
time necessary
to
perform
a FTPAtransfer
of is
an
Femto
2 should
have
each
others
details
following
pre-requites
in place.
UEmode
which
continue
maintain
the
call
andthe
data
should
enabled.
The
UE
isispower
cycled
or
automated
UE
call
and
are
toRef:
be to
measured
atended
FTP
application
layer
ASCII
file,
from
the
FTP
Server
to
the
UE
in
DL
Test
KPI-3.0-035
old
KPI-2.4-003
populated
in
the
neighbour
cell
lists.
When
the
automated
and
canwhilst
also
power
cycled
oronly
continue
transfer
foroverheads)
atbe
least
30 over
seconds
changed
to
UMTS,
the
attenuation
attenuators
reconfigured
such
that
UE
can
(includes
TCP,
RLC,
RF
entire
andhas
from
UE to and
FTP
Server
in
UL.FTS-106897
The
duration
Requirement:
FTS-77715
R11,
UE
reselect
to the
neighbouring
Femto
cell
mode
changed
amarginally
controllable
attenuation
once
the
handover
is
completed.
We
can
verify
control
is
set
such
that
the
Femto
is
not
seen
see
the
Femto
1
and
see
Femto
2,
file
transfer
period.
The intent
is to measure
can
be
measured
as
time
elapsed
R10
e.g.
Femto
2has
thethe
cell
idthe
should
bebetween;
checked
system
and
athen
Femto
with
MM
Information
that
the
UE
performed
handover
onto
by
the
UE
and
the
is
now
but
is of
or
not
see
Femto
2UE
at
all.
Assearching
the
automated
the
time
necessary
to
perform
a
FTP
transfer
First
FTP
data
packet
received
on
the
Test
Description:
Automated
CS
calls
from
the
UE
log
ensure
that
UE
has
enabled.
The
UEto
isby
power
cycled
or
mode
the
correct
Femto
checking
the
cell
id.
out
of
zone.
Next
the
attenuation
is
adjusted
UE
is
now
in
mode
itTCP
should
perform
a Next
cell
an
ASCII
file,
from
the
FTP
Server
to
the
UE
in
Test
Ref:
KPI-3.0-036
old
KPI-2.4-013
mobile/Server
and
Last
ACK
FIN
received
performing
aidle
mixture
of
MOC,
MTC
and
MTM
reselected
to
the
correct
Femto.
The
pass
changed
such
that
it
registers
with
the
Femto,
the
automated
UE
call
is
ended
and
the
such
that
the
Femto
is
not
visible
to
reselection
back
toFTP
the
Femto
1 calls
and
this
can
be
DL
and1from
UE FTS-77715
to
Server
in
UL.
TheUE,
Requirement:
R13,
FTS-106897
by
mobile
acknowledging
all
TCP
packets.
Both
within
Femto.
The
mixture
of
will
be
criteria
for
this
test
case
is
that
cell
reselection
MMInformaiton
is received
and
HomeZone
attenuators
reconfigured
such
that
UEstrength
can
only
that
is the
quality
(Ec/No),
and
signal
verified
by
checking
the
cell
id
to
verify
the
UE
duration
can
be
measured
as
the
time
elapsed
R11
messages
can
be
captured
with
WireShark
on
evenly
split
33.3%
MOC,
33.3%
MTC
and
33,3%
failure
rate
for
asuitable
UE
moving
from
one
Femto
to
Information
is displayed.
The
attenuators
are
see
the
Femto
1
and
marginally
see
2,
(RSCP)
are
now
for
the
UE
register.
is back
on
the
original
test
Femto
1.toFemto
The
test
between;
First
FTP
data
packet
on
theis
Test
Description:
Automated
R99
PS
calls
test
PC
that
issued
the
FTP.
Alsoreceived
the
reported
MTM.
another
Femto
within
the
same
group
should
set
such
that
the
Femto
is
visible
to
the
UE
and
or
not
see KPI-3.0-037
Femto
2 at
all.
As
the
automated
Once
registered
with
Femto
the
MMI
of the
Test
Ref:
old
KPI-2.4-014
now
ready
to
be
repeated.
CS
service
mobile/Server
and
TCP
ACK
FIN
received
are
performed
using
1the
Femto.
PDP
context
times/data
rates
asLast
reported
by
the
FTP
client
be <1%.
the
Macro
is
justFTS-77715
visible
the
UE
and
also
is
now success
in
idle
mode
ittoshould
perform
a cell
UE
should
display
the
HomeZone
information.
Requirement:
R14,
FTS-106897
handover
is defined
as
upon
source
by
mobile
acknowledging
all
TCP
packets.
Both
activation
time
isalso
recorded
and
checked
application
may
befor
used
for
results.
For
For
MOC, by
the
call
setup
delay
is
defined
the
detected
the
Femto
NCELL
list
reselection
back
to
the
Femto
1 criteria.
and
thisas
can
The
for
arrival
of HomeZone
notification
at
R12
BSR time
send
rrc_radioBearerReconfiguration()
with
messages
can
beestablish
captured
with
WireShark
on
against
measurement
and
pass
This
HSDPA
10MB
file
size
should
be
used.
Pass
time
required
to
a
CS
voice
call
from
Note:
Therewhen
is
nothe
message
triggering
cell
population.
Next
theAutomated
attenuators
are
adjusted
be
verified
by
checking
the
cell
id
to
verify
the
UE
isPC
from
UE
receives
the
uplink
Test
Description:
R5
and
R6
PS
new_U_RNTI,
it
receives
test
that
issued
FTP.
Also
the
reported
delay
is
defined
as
the
time
required
to
criteria
that
single
UE
HSDPA
user
a
UE
to
a terminal
in
the
PSTN.
Call
setup
time
reselection
and
it is
difficult
toaverage
measure.
The
such
that
the
Macro
will
be
come
the
better
Test
Ref:
KPI-3.0-038
old
KPI-2.4-037
UE
is
back
on
the
original
test
Femto
1.
The
message
(RRC)
"RRC
Connection
Request"
(to
calls
are
performed
using
1
Femto.
A
mixture
of
bsrap_bsrUeContextRelease()
from
target
BSR.
times/data
as
reported
by
the
FTP
client
perform
therates
PDP
context
activation
initiated
by
throughput
shall
be
greater
than
6000
kbps
is
measured
from
the
originating
UE
sending
UE
is
moved
out
of
the
coverage
area
and
in
candidate
and
the
UE
should
reselect
from
the
Requirement:
FTS-106897
R13
test(HSDPA)
is now
ready
tostart
be
repeated.
The
perform
LAU)
until
the
UE
receives
the test
R5
50%
and
R6
(HSUPA)
50%
PS For
calls
application
may
also
be
used
for
results.
the
UE,
in
order
to
a
data
session.
UE
application
layer
throughput
for
V2.x
hardware
CCCH:RACH:RRC
Connection
Request
onThe
first
some
point
Femto
serving
cell
to
Macro
neighbour
cell.a
Test
Description:
This
KPI
should
have
the
should
also
be
repeated
and
evenly
split
with
downlink
message
(NAS)
"MM
Information".
are
performed
using
1the
Femto.
PDP
context
HUDPA
10MB
file
size
should
be
used.
Pass
changes
its
PDP
state
from
INACTIVE
tomacro
ACTIVE.
and
greater
than
4000
kbps
for
V1.x
hardware
preamble
until
the
originating
UE
receives
in
time
the
UE
decides
re-select
the
The
time
for
arrival
of
HomeZone
notification
following
pre-requites
into
The
3G
Macro
CS+PS
handover,
in
this
case
the
aof
CS
call
is at
Time
For
Arrival
HomeZone
Notification
at
activation
time
isofregarded
recorded
and
checked
Handover
success
rate
isplace.
defined
as
criteria
that
single
UE
HSDPA
average
user
This
procedure
is
as
part
the
data
for
a
corresponding
UE
category
8
with
CQI>
DCCH:DCH:
Direct
Transfer
(NAS:
Alerting
Test
Ref:
KPI-3.0-039
old
KPI-2.4-041
cell.
Iffrom
the
UE
is the
placed
in
an
area,
which
should
UE
is
when
the
UEand
receives
the
uplink
is
appropriately
configured
such
that
the
Femto
setup
first
then
PS
call
for
this
multi-RAB
UE
should
be
less
than
1.5
seconds.
Next
the
against
measurement
pass
criteria.
(NumUeContextRelease)/
throughput
shall
be
greater
than
1000
kbps
call
setup
in
this
definition.
If
the
UE
is
indefined
PMM
25.
All cell
HSDPA
tests
should
be
conducted
with
message)response.
The
pass
criteria
is
Requirement:
FTS-106897
R14
trigger
reselection,
and
then
the
macro
message
(RRC)
"RRC
Connection
Request"
is
present
in
the
intra/inter-frequency
(simbearer)
test.
Handover
attempts
are
attenuator
of
the
Femto
is set
such
that
the(to
UE
(NumRadioBearerReconfig).
Femto
torequest
Femto
application
layer
throughput
for
a have
IDLE
state,
it
must
perform
a
service
a
UE
which
is
capable
of
the
maximum
data
as
less
than
4s
(mean)
and
6s
(95%ile)
for
Test
Description:
This
KPI
should
the of
cell
radio
islist.
activated,
this
could
be
the
start
perform
LAU)
until
the
UE
receives
the
neighbour
This
KPI
will
devided
evenly
evenly
divided
as
PS
handover
(50%)
and
cannot
see
Femto
and
the
UE
either
power
This
delay
isthe
defined
as
the
time
required
toto
Cell
Handover
Success
Rate
is
defined
as
the
corresponding
UE
HSUPA
category
3.
All
HSUPA
procedure
(PS
signalling
connection
and
Iu)
rate
supported
by
the
Femto
e.g.
current
Femto
13.6k
SRB
and(50%)
5.5s
(mean)
and
8s
(95%ile
) for
following
pre-requites
in could
place.
A
Femto
and
the measurement.
Stop
be
the
RRC
downlink
message
(NAS)
"MM
Information".
between
intra
and
inter
(50%)
Macro
CS+PS
handover
(50%).
cycled
or
mode
changed
and
the
test
repeated.
perform
the
PDP
context
activation
initiated
number
of
successful
handovers
from
BSR
tests
should
be
conducted
with
aprocedure
UE
which
isby
become
CONNECTED.
This
is
BSR can
support
HSDPA
Category
8, bearer
3.4k
SRB.
Macro
3GPMM
cell
appropriately
configured
Connection
Request
message
for
3G
or such
Time
For
Arrival
of
HomeZone
Notification
atof
hand-in.
automated
controllable
the
UE,
order
to
start
a
data
session.
The
UE
Femto
toin
BSR
Femto,
inas
the
handover
region,
capable
ofAn
the
maximum
data
rate
supported
not
normally
regarded
part
PDP
7.2Mbps.
that
each
others
details
are
in of
the
intra/interImmediate
Assignment
request
inthe
2G.
The
KPI
UE
should
less
than
1.5
seconds.
Next
the
attenuation
system
is in
place
and
can
control
The
PS
and
CS+PS
service
handover
success
changes
itsbe
PDP
state
from
INACTIVE
to
ACTIVE.
relative
to
the
total
number
of
handover
by
the
Femto
e.g.
current
Femto
BSR
can
context
activation
procedure
in
this
definition.
For
MTC,
the
delay
isKPI.
defined
assuch
the
frequency
lists.
Itsetup
is
assumed
that
Femto
to
are
UE
KPI
but
not
BSR
Femto
This
clause
attenuator
of
the
Femto
and
Macro
is the
set
Femto
and
3Gcall
Macro.
The
control
rate
is
defined
as
upon
source
BSR
send
This
procedure
is
regarded
as
of
data
attempts.
support
HSDPA
Category
3,attenuation
bearer
PDP
context
activation
time
is part
measured
KPI
Threshold
time
required
in
UMTS
network
to
establish
a
Macro
3G
handover
KPI
will
be
divided
evenly
is
for
reference
only.
that
the
UE
cannot
see
the
Macro
and
the
UE
set
such
that
the
UE can
only
see
rrc_radioBearerReconfiguration()
with
call
setup
in
this
definition.
If the
UE
is(number
in3G
PMM
number
of
unsuccessful
handovers
=the
1.46Mbps.
between
UE
sending
UL layer
>4000
kbps
application
throughput
with
CS
voice
call
from
a failure
voice
terminal
between
intra
and
inter
(50%)
frequency
The
cell
reselection
rate
for ainUE
moving
either
power
or
mode
changed
and
the
Macro
and
marginally
see
the
Femto,
or
not
see
new_U_RNTI,
it(50%)
receives
IDLE
state,
it cycled
must
perform
a and
service
request
of
handover
- (number
of successful
DCCH:rrcConnectionRequest
UE
receiving
V1.x
hardware.
PSTN/ISDN
toattempts)
a UE
in UMTS.
Call
setup
time
is
cases.
AnFemto
automated
controllable
attenuation
from
one
toNext
another
Femto
within
the
test
repeated.
the
Femto
at
all.
the
automated
UE
is
bsrap_bsrUeContextRelease()
from
target
BSR.
procedure
(PS
signalling
connection
and
Iu)
to
handovers)
The
FTP
Mean
User
Data
Rate
[kbit/s]
denotes
DL
NAS:ActivatePDPContextAccept.
Pass
>6000
kbps
application
layer
throughput
with
measured
from
the
starting
event:
BSR
sending
system
is in
place
and
can
control
the
Femto
same
group
be
<1%.
placed
into
ashall
CS
voice
call
once
the
call
hasis
Handover
success
rate
is
defined
as
become
PMM
CONNECTED.
This
procedure
The
handover
success
rate
=
(number
of
the
average
data
rate
(application
throughput)
criteria
is a3G
PDP
context
activation
timetoless
V2.x
hardware.
Paging
Request
for
CS
termination
UE
and
Macro
signal
tocall
the
UE.
The
It
is
understood
and
agreed
that
this
test
case
been
successfully
held
for
approximately
10
(NumUeContextRelease)/
not
normally
regarded
as
part(if
of
the
PDP
successful
handovers)
kbps
(number
of attempts).
in
kbit/s.
(Average
experienced
throughput
than
3.6 finishing
sec
on
SRB
SRB
13.6
kbps
The
following
conditions
apply
to
this
KPI;
until
the
event:
BSR
sending
RAB
attenuation
is3.4
set
such
that
the
UE
can
is
not
a Femto
specific
KPI
and
isthis
measuring
the
seconds
the control
attenuators
are
cross
faded
such
(NumRadioBearerReconfig).
context
activation
procedure
inDSL
definition.
The
handover
failure
rate
for
Femto
to
FemtoCS
while
uploading
a file)
),
the
backhaul
is
is
used
then
3
sec
delay)
CQI>25
forResponse
Category
8 ifMSC
UE
with
10
codes.
assignment
to
for
this
UE.
only
see
the
Macro
and
marginally
see
the
performance
of
the 3G
UEFemto
and
Macro
cell.
It isThe
also
that
the
neighbouring
a better
PDP
context
activation
time
isismeasured
calls
should
be
less
1%.
able
to
support
this
data
rate.
IPsec
encryption
isthan
activated
Pass
criteria
shall
be
less
than
4.5s
(mean)
and
Femto,
or
not
see
the
Femto
at
all.
Next
the
agreed
that
the
purpose
of
performing
this
candidate,
quality
(Ec/No),
and
signal
strength
The
PSabsence
and
Femto
to Femto
Cell it is test
between
UECS+PS
sending
UL DSL
In
the
of
a
good
backhaul
UL
128kbps
8s
(95%ile).
automated
UE
isserving
placed
a CS
voice
call
case is than
check
that
Femto
does
not
interfere
(RSCP)
the
Macro.
For
inter
Handover
Failure
Rate
is into
defined
as
the
number
DCCH:rrcConnectionRequest
and
UE
receiving

iterations
Pass
100%

iterations
Pass
100%

iterations
Pass
100%
CS Voice

iterations
Pass
1.2059
sec
CS Voice

iterations
Pass
0.3534s
Availability
In progress
Manual Test
Pass
2.10s
Availability
In progress
Manual Test
Pass
4.31min
Availability
In progress
Manual Test
Pass
12min
Availability
In progress
Manual Test
Pass
13min

iterations
Pass
0%

iterations
Pass
0%

iterations
Pass
0%
PS Data HSDPA

iterations
Pass
7532Kb/s
PS Data - HSUPA

iterations
Pass
1347kb/s
In progress
Manual Test
Pass
0.5
seconds
In progress
Manual Test
Pass
0.5
seconds
Call-P

iterations
Pass
PS Data - R99

iterations
Pass
2.0367s
MOC
5.2773s
MTM
2.6938s
PS Data HSDPA

iterations
Pass

iterations
Pass

iterations
Pass
1.9669s
R5
1.9281s
R6
100%
114ms
330ms
FTS-106897
UL Voice Speech Quality AMR 12.2 kbps Femto

Mobile to PSTN/ISDN
16 Simultaneous Voice calls
R15
FTS-106897
DL Voice Speech Quality AMR 12.2 kbps PSTN/ISDN

to Femto Mobile
R16
FTS-106897
Voice Speech Quality AMR 12.2 kbps Femto Mobile

to Femto Mobile
R17
FTS-106897
Delay between first power-on with factory default

settings and femtocell service availability (including
NTP synch)
R17a
FTS-106897
Delay between first power-on with factory default

settings and femtocell service availability (including
NTP synch + software download)
R17b
BCR2.3
y
FTS-83234
Femto to Femto CS Handover

The mean interruption time during the handover
phase
R5
FTS-83234
UL Voice Speech Quality AMR 12.2 kbps Femto

Mobile to PSTN/ISDN
R6
FTS-83234
R7
FTS-83234

to Femto Mobile
MOS Value
to
Femto
Mobile
Test
Requirement:
Four
Simultaneous
Voice
FTS-83234
(BCR 2.3)
R7 calls
FTS-83234
R9
FTS-83234
FTS-83234
Voice Speech Quality on Sample Basis when One

Simultaneous R99 PS User with 384 kbps Bearer In
Very Close Proximity To The femto CPE For Three
Simultaneous Voice Calls
Voice
Speech
Quality
on Sample
Basis
when
One
DL Voice
Speech
Quality
AMR 12.2
kbps
PSTN/ISDN
Simultaneous
R99 PS User with 384 kbps Bearer In
to Femto Mobile
Very Close Proximity To The Femto CPE For Three
UL
DL Voice
Voice Speech
Speech Quality
Quality AMR
AMR 12.2
12.2 kbps
kbps Femto
Femto
Mobile
Mobile to
to PSTN/ISDN
Femto Mobile
Eight Simultaneous Voice calls
FTS-83234

to Femto Mobile
R12
FTS-83234

to Femto Mobile
R13
FTS-83234
R14
FTS-83234
FTS-83234
FTS-83234
FTS-83234
FTS-83234
FTS-83234
Voice Speech Quality on Sample Basis when One

Simultaneous R99 PS User with 384 kbps Bearer In
Very Close Proximity To The femto CPE For Seven
Voice
Speech
Quality
on Sample
Basis
when
One
DL Voice
Speech
Quality
AMR 12.2
kbps
PSTN/ISDN
Simultaneous
R99 PS User with 384 kbps Bearer In
to Femto Mobile
Very Close Proximity To The femto CPE For Seven
FTP
R99Speech
Throughput.
max
bit kbps
rate. Femto
(measured
DL Voice
Quality% of
AMR
12.2
at
FTP application)
Mobile
to Femto Mobile
Three Simultaneous Voice Calls Are Already
Established
HSxPA avg thoughput % of peak on air interface
(measured
at FTP application)
Test Requirement:
Three
Simultaneous
FTS-83234
(BCR 2.3)Voice
R16 Calls Are Already
Established
FTS-106897 (BCR 2.4) R30
PS User Data R99 Throughput In Uplink Per femto CPE
when One Simultaneous Voice Call Already
Established In Very Close Proximity To The femto CPE.
% of max bit rate. (measured at FTP application)
FTP R99 Throughput % of max bit rate. (measured
at FTP application)
Three/One/Seven Simultaneous Voice Calls Are
Already Established
(measured
at FTP application)
Test Requirement:
Three/One/Seven
Simultaneous
FTS-83234 (BCR 2.3)
R16,18,19 Voice Calls Are
Already
Established
FTS-106897
(BCR 2.4) R33
R8
R10
R11
R15
R16
R17
R18
R19
R20

Requirement: FTS-106897 R15
Test Description: This test case is based on
measuring the UL quality of a UE to PSTN/ISDN
Test
Ref: KPI-3.0-041
old KPI-2.4-056
call. Whilst
there are another
15 UE's are in
Requirement:
FTS-106897
R16 14 (7 pairs)
call. In order to make
15 UE calls,
Test
Description:
This
test
case
is either
basedas
on
can be
setup as MTM
with
the
15th
measuring
theorDL
quality
of a UE
to PSTN/ISDN
loopback call
call
to another
Femto
UE or
Test
Ref: KPI-3.0-042
old KPI-2.4-054
call.
Whilst
there
arepoint.
another
15 UE's are
in
2nd PSTN/ISDN
end
Automated
MTM
Requirement:
FTS-106897
R17 14 (7 pairs)
call.
order
to make
15 UE
calls,
calls In
are
established
next
either
a MOC to
Test
Description:
This test
case
is either
based on
can
be
setupMOC
as MTM
the
15th
PSTN/ISDN,
to UEwith
on another
Femto,as
or
measuring
theorDL
quality
of a MTM
call.
loopback
call
to another
Femto
UEWhilst
or
MOC Ref:
loopback
iscall
established.
There
are
now
Test
KPI-3.0-043
old
KPI-2.4-046
there
are another
15point.
UE's are
in call. There
2nd
PSTN/ISDN
end
Automated
MTMa will
15
active
CS
voice
calls
in
progress.
Next
Requirement:
FTS-106897
R17a
therefore
be
in
total
16
active
calls.
First
14
calls are
established
next either
a MOC
to CS
16th
automated
call,
AMR 12.2
kbps
Test
Description:
ToMOC
automate
the test
it
UE's
(7
pairs)
as automated
to perform
MTM
PSTN/ISDN,
to UE on
another
Femto,
or
voice
callpossible
toMOC
PSTN/ISDN
is established.
Afactory
premust
be
to reset
to setup
calls
to
one another.
Nextthe
theFemto
8th call
MOC
loopback
iswaveform
established.
There
are now is
recorded
audio
isKPI-2.4-047
played
backed
Test
Ref:
KPI-3.0-044
oldNext
default
settings
via
a pair
CLI.
theand
power
isUE's
again
between
a
8th
UE's
15
16.
15
active
CSand
voice
calls in and
progress.
Next
a
from
the
UE
received
recorded
at
Requirement:
FTS-106897
R17b
controlled
a Blackbox
power
control
15
and 16 via
are e.g.
the
UE's
thatAMR
voice
quality
will
16th
call,
MOC
12.2
kbps
CS
PSTN/ISDN
AnTo
audio
analysis
scoring
Test automated
Description:
automate
theand
test
itthen
system
andside.
the
Femto
switched
and
be
performed
on.
Thereisis
are
now 16off
active
CS
voice
callpossible
to
established.
pretool (TBD)
is PSTN/ISDN
then
used
to the
compare
source
must
be
to
reset
Femtothe
to Afactory
back
to
create
first
power
on cycle.
A
voice
calls
in progress.
A pre-recorded
audio
recorded
audio
waveform
is played
backed
and
received
signals
to
establish
a
Perceptual
default
settings
via
a
CLI.
Next
the
power
is
mechanism
to be
established
to measure
waveform
is has
played
backed
onreceived
UE15
and
from
the
PSTN/ISDN
side
and
and
Evaluation
of Speech
Quality
(PESQ)
score
of
controlled
Test
Ref:from
KPI-3.0-045
via
e.g.
a Blackbox
old KPI-2.4-043
power
control
the
time
power
on
the
Femto
is in
received
and
recorded
atuntil
UE16.
An
audio
recorded
at the
the
UE is
side.
An
audio
analysis
the
UL audio.
PESQ
an
algorithmic
non
Requirement:
FTS-83234
R5,
FTS-106897
R18
system
and
Femto
is including
switched
off
and
then
service
and
NTP
synch.
analysis
andtransmitting
scoring
tool
(TBD)used
is then
used
to
and
scoring
tool
(TBD)
isKPI
then
to
subjective
(objective)
audio
quality
score
from
back
Test
Description:
to create
first
This
onshould
cycle.
have
A compare
the
The
pass
criteria
forpower
this
test
is
that
the
total
compare
the
source
and
received
signals
to
the
source
and
received
to
establish
which
audio
scoring
tools
deriveTwo
their
uniquea
mechanism
following
pre-requites
has
to
be
established
in signals
place.
to
Femtos
measure
time
from
power
on
until
providing
service
establish
aKPI-3.0-046
Perceptual of
Evaluation
of Speech
Perceptual
Evaluation
Speech
Quality
(PESQ)
Test
Ref:from
old
KPI-2.4-049
Estimated
Mean
Opinion
Score
(EMOS).
It
is
appropriately
configured
such
that
each
others
the
time
power
on
until
the
Femto
is
in
should be
less than
90
minutes.
Quality
(PESQ)
score
ofPESQ
the R6,
UL->DL
audio. R20
score
ofare
thethat
DL
audio.
is
an
algorithmic
Requirement:
FTS-83234
FTS-106897
preferable
PESQ
scores
are
used
service
details
and
intransmitting
the
intra-frequency
including
lists.
NTPfor
synch
It KPI
is as
+
PESQ
is an algorithmic
non
subjective
non
subjective
(objective)
audio
quality
Test
Description:
This
case
isFemto
based
on
these
aredownload.
comparable
other
audio
software
assumed
that
as
this
The
iswith
atest
pass
Femto
criteria
to
forscore
this
(objective)
audio
quality
score
from
which
from
which
audio
scoring
tools
derive
their
measuring
the
UL
quality
of
a
UE
to
PSTN/ISDN
application
PESQ
scores
where
as EMOS/MOS
handover
will
betime
intra-frequency.
Anuntil
test
is thatthis
the
total
from power
on
audio
scoring
tools
derive
their
unique
Test
Ref:
KPI-3.0-047
old
KPI-2.4-050
unique
Estimated
Mean
Opinion
Score
(EMOS).
call.
Whilst
there
another
3 UE's
are
in call.
scores
cannot
be are
compared.
Next
all
calls
are
providing
automated
service
controllable
should
attenuation
be less
than
system
90
is
Estimated
Mean
Opinion
Score
(EMOS).
Itbe
isR21
Requirement:
FTS-83234
R7,
FTS-106897
It
is
preferable
that
PESQ
scores
for
In
order
to
make
3 UE
calls,
2 (1pair)
can
terminated
and
the
test
is
repeated.
The
pass
minutes.
in
place
and
can
control
Femto
1 are
andused
Femto
2
preferable
that
PESQ
scores
are
used
for
KPI
Test
This
test either
case
is
based
onas
KPI
asDescription:
these
are
comparable
with
audio
setup
as
with
the
third
as
loopback
criteria
isMTM
that
the
MOS
should
be other
larger
than
signal
to
the
UE.
The
attenuation
control
is set
these
are
comparable
with
measuring
the
DLscores
quality
ofother
aUE
UE
to
PSTN/ISDN
application
PESQ
where
as
EMOS/MOS
call
orthat
callthe
to
another
Femto
oraudio
2nd
3.5
(mean).
such
UE
can
only
see
the
Femto
1
and
Test Whilst
Ref:
KPI-3.0-048
old
KPI-2.4-048
application
PESQ
scores
where
EMOS/MOS
call.
there
are
another
3 as
UE's
are
in call.
scores
cannot
be
compared.
Next
all
calls
areat
PSTN/ISDN
end
point.
Automated
calls
marginally
see
Femto
2,
or R8,
not
seeMTM
Femto
2
Requirement:
FTS-83234
R22
scores
cannot
be
Next
all The
calls
are
In
order
to make
3compared.
UE
calls,
(1FTS-106897
pair)
can be
terminated
and
the
test
is
repeated.
are
established
next
either
a2
MOC
to
all.
the
automated
UE
is
placed
into pass
aon
CS
TestNext
Description:
This
test
case
is
based
terminated
and
the
testthird
is another
repeated.
The
pass
setup
asisMTM
with
the
either
as
loopback
criteria
that
the
MOS
should
be
larger
than
PSTN/ISDN,
MOC
to
UE
on
Femto,
or
voice call once
thequality
call has
been
successfully
measuring
the
DL
of
a
MTM
call.
Whilst
criteria
is
that
the
MOS
should
be
larger
than
call
or
call
to
another
Femto
UE
or
2nd
3.5 (mean).
MOC
loopback
is established.
There
are now 3
held
for
approximately
10
seconds
the
Test
Ref:
KPI-3.0-049
old
KPI-2.4-058
there
are
another
2
UE's
are
in
call.
There
will
3.5 (mean).
PSTN/ISDN
end point.
Automated
MTM an
calls
active
CS voice
calls
progress.
Next
attenuators
cross4infaded
such that
the a
Requirement:
FTS-83234
R9
therefore
beare
in total
active
Firstly
are
established
next
either
a calls.
MOC
to
automated
MOC
AMR
12.2
kbps
CS
voice call
to
neighbouring
Femto
2setup
istest
a better
Test
Description:
his
case
based
on
MTM
UE
to UE
call
theninis
acandidate,
second
Note:
MTM
voice
quality
target
all
otheraudio
test
PSTN/ISDN,
tois
UE
on
another
Femto,
or
PSTN/ISDN
isMOC
established.
A
pre-recorded
quality
(Ec/No),
and
signal
strength
(RSCP)
measuring
the
DL
quality
of
a
MOC
to
automated
MTM
call
isHowever
established.
There
are3
casesRef:
and is
KPI
is
this
test
case
MOC
loopback
is 3.2.
established.
There
are
now
waveform
played
backed
from
the
UE
and
Test
KPI-3.0-050
old
KPI-2.4-057
than 4the
serving
Femtocalls
1. The
automated
UE
PSTN/ISDN
call.
Whilst
there
are
another
4 UE's
now
active
CScalls
voice
in
progress.
On
one
requires
target
which
isPSTN/ISDN
more
challenging
active
CS3.5
voice
in progress.
Next an
received
and
recorded
An
Requirement:
FTS-83234
should
maintain
the
CSat
voice
call waveform
and side.
correctly
are
in
one
of
which
is
a R10
multipair
ofcall
MTM
a pre-recorded
audio
isto
combined
with
the
configuration
ofis16
automated
MOC
AMR
12.2 kbps
CS
voice
call
audio
analysis
and
scoring
tool
(TBD)
isactive
then
Test
Description:
This
case
based
onbe
handover
to Femto
2
andtest
continue
to
maintain
RAB/simbearer
R99
call.
There
therefore
played
backed
and
received
andwill
recorded
at
UE
calls
which
is
also
more
challenging
for
the
PSTN/ISDN
is
established.
A
pre-recorded
audio
used
to
compare
the
source
and
received
measuring
the
DL
quality
of aaMTM
Whilst
the
call 4for
at
least
30 seconds
oncecall.
the
in
total
active
calls.
Firstly
MTM
UE1
to
UE2
the
UE.
An
audio
analysis
and
scoring
tool
Femto.
This
has
been
highlighted
to
the
KPI
waveform
is
played
from
the
PSTN/ISDN
Test
Ref:
KPI-3.0-051
old
KPI-2.4-052
signals
to another
establish
abacked
Perceptual
Evaluation
of
there
4
UE's
are
in call
one
of the
handover
is
completed.
We
can
verify
that
call isare
then
ato
second
automated
pair
of
(TBD)
issetup
then
used
compare
source
and
document
owners.
side
and
and
recorded
at
UE.
AnThere
Requirement:
FTS-83234
R11,the
FTS-106897
Speech
Quality
score
the
UL
audio.
which
areceived
multi-RAB/simbearer
R99
call.
UE hasisperformed
handover
onto
the
automated
calls(PESQ)
are
setup
asaof
MOC
to
received
signals
tothe
establish
Perceptual
audio
analysis
and
scoring
tool
(TBD)
isFirstly
then a
R25
PESQ
is
an algorithmic
non
subjective
will
therefore
be
in
total
4UE4.
active
calls.
correct
Femto
byUE3
checking
the
cell
id.score
Next
the
PSTN/ISDN
from
and
There
are
now
4
Evaluation
of
Speech
Quality
(PESQ)
of
"The Description:
target
isUE2
intended
to
beand
appropriate
used
to compare
the
source
received
Test
test
case
isawhich
basedfor
on
(objective)
audio
quality
score
from
MTM
UE1
call
isprogress
setup
then
automated
UE
call
isThis
ended
and
the
active
CS to
voice
calls
in
2
aresecond
MTM
and
the
UL->DL
audio.
PESQ
isofKPI-2.4-053
an
algorithmic
non
Test
Ref:
KPI-3.0-052
old
the
enterprise
market
where
expect
voice
signals
to establish
aisPerceptual
Evaluation
of
measuring
the
ULcall
quality
awe
UE
tobetween
PSTN/ISDN
audio
scoring
tools
derive
their
unique
automated
MTM
established
attenuators
reconfigured
such
that
UE
can
only
2
are
MOC
to
PSTN/ISDN.
Next
a
R99
PS
RAB
is
subjective
(objective)
audio
quality
score
from
Requirement:
FTS-83234
R12,
FTS-106897
quality
on
a
fully
loaded
system
to be
more
of
Speech
Quality
(PESQ)
score
of
the
DL
audio.
call.
Whilst
there
areare
another
7 active
UE's
are
in
call.
Estimated
Mean
Opinion
Score
(EMOS).
Itvoice
is
UE3
and
UE4.
There
4
CS
see
the
Femto
1UE1
and
marginally
see
Femto
2,
established
on
and
anow
data
transfer
started.
which
audio
scoring
tools
derive
their
unique
R26
a sensitive
issue
for
operators
than
aisfully
PESQ
an
algorithmic
subjective
In
to Femto
make
7
calls,
6are
(3
pairs)
can
beas
preferable
that
PESQ
used
for
KPI
calls
inissee
progress.
Next
anon
R99
PS
RAB
or order
not
2 UE
atscores
all.
As
the
automated
UE1
should
be in
close
proximity
to
Femto.
Estimated
Mean
Opinion
Score
(EMOS).
It is
Test
Description:
This
test
case
is the
based
on
loaded
residential.
It
iswith
aa
deliberate
target
that
(objective)
audio
quality
score
from
which
setup
as
MTM
with
the
7th
either
as
loopback
these
are
comparable
other
audio
established
on
UE1
and
data
transfer
started.
UE
is
now
in
idle
mode
it
should
perform
a
cell
A
pre-recorded
audio
waveform
is
played
Test
Ref:
KPI-3.0-053
old
KPI-2.4-051
preferable
that
PESQ
scores
are
used
for KPI as
measuring
the
DL
quality
of
a
UE
to2nd
PSTN/ISDN
we must
hard
to
achieve."
Kevin
Pendleton,
audio
scoring
tools
derive
their
unique
call
or
calltry
to
another
Femto
UE
or
application
PESQ
scores
where
as
UE1
should
be
inFTS-83234
close
proximity
toEMOS/MOS
the
Femto.
reselection
back
to
the
Femto
and
this
can
backed
from
one
of
the
PSTN/ISDN
handsets
Requirement:
R13,
FTS-106897
these
are
comparable
with
other
audio
call.
Whilst
there
are
another
71(EMOS).
UE's
in
call.
Bill
Dickson
28/01/2010
Estimated
Opinion
Score
It is
PSTN/ISDN
end
point.
Automated
MTM
calls
are
scores
cannot
be
compared.
Next
allare
calls
are
On
one
pairMean
ofand
MTM
calls
a pre-recorded
audio
beorder
verified
by
checking
the
cell
idpairs)
to
verify
the
and
received
recorded
at
UE3
or
UE4.
An
R27
application
PESQ
where
as
EMOS/MOS
In
to that
make
7scores
UE
calls,
6are
(3
can
beas
preferable
PESQ
scores
used
for
KPI
established
next
either
ais
MOC
to
PSTN/ISDN,
terminated
and
the
test
repeated.
The
pass
waveform
is
played
backed
and
received
and
UE
is
back
on
the
original
test
Femto
1.
The
audio
analysis
and
scoring
tool
(TBD)
is
then
Test
Description:
This
test
case
isallbased
on
scores
cannot
be compared.
Next
calls are
setup
as
MTM
with
the
7th
either
as
loopback
these
are
comparable
with
other
audio
MOC
to
UE
on
another
Femto,
or
MOC
criteria
is
that
the
MOS
should
be
larger
than
recorded
at
the
end
UE.
An
audio
analysis
and
Test
KPI-3.0-054
old
KPI-2.4-060
test or
isRef:
ready
to
be
repeated.
CS
voice
used
tonow
compare
the
source
and
received
measuring
the
DL
quality
of
a
MTM
call.
Whilst
terminated
and
the
test
is
repeated.
The
call
call
to
another
Femto
UE
or
2nd
application
PESQ
scores
where
as
EMOS/MOS
loopback
is
established.
There
are
now
7 pass
3.5
(mean).
scoring
tool
(TBD)
isaUE's
then
used
to
compare
the
Requirement:
FTS-83234
R14,
FTS-106897
handover
interruption
can
be
identified
by
UE
signals
to
establish
Perceptual
Evaluation
of
there
7MOS
are
in
call.
will
criteria
is another
that
the
should
be
larger
than
PSTN/ISDN
endbe
point.
MTM
calls
are
scoresare
cannot
compared.
Next
allThere
calls
are
active
CS
voice
calls
inAutomated
progress.
Next
an
8th
source
and
signals
to
establish
a Data
R28
log Vocoder
Packet
Characteristics
v2
(No
Speech
Quality
(PESQ)
score
ofto
the
UL->DL
therefore
bereceived
in total
8
active
calls.
First
6
UE's
3.2
(mean).
established
next
either
aisMOC
PSTN/ISDN,
terminated
and
the
test
repeated.
The
pass
automated
call,
MOC
AMR
12.2
kbps
CS
voice
Perceptual
Evaluation
ofto
Speech
Quality
(PESQ)
Test
Description:
This
test
case
is
based
onto
12.2kbps)
or
(Speech
good
12.2kbps),
during
audio.
PESQ
is
an algorithmic
non
subjective
(3
pairs)
as
automated
perform
MTM
calls
MOC
to
UE
on
another
Femto,
or
MOC
criteria
isthe
that
the
MOS
should
bea
larger
than
call
toRef:
PSTN/ISDN
is
established.
A
pre-recorded
Test
KPI-3.0-055
old
KPI-2.4-059
score
of
UL->DL
audio.
PESQ
is
an
measuring
the
DL
quality
of
a
of
MOC
to
hand
over
period.
The
handover
can
be
(objective)
audio
quality
score
from
which
one
another.
Next the 4th
call setup
is again
loopback
is established.
There
are
now
7 UE
3.5
(mean).
audio
waveform
is played
backed
from
the
Requirement:
FTS-83234
R15,
FTS-106897
algorithmic
non
subjective
(objective)
PSTN/ISDN
call.
Whilst
there
are
another
8 UE's
identified
by
UE
receives
audio
scoring
tools
derive
their
unique
between
4th
pair
UE's
7 and
8.
UE's audio
7anand
active
CSavoice
calls
in progress.
Next
8th8
and in
received
and
recorded
PSTN/ISDN
side.
R29
quality
score
from
which
audio
scoring
tools
are
one
of Opinion
which
isScore
a at
multirrc_radioBearerReconfiguration
message
Estimated
Mean
(EMOS).
Itwith
is
are
thecall
UE's
that
voice
quality
will
beCS
perofmed
automated
call,
MOC
AMR
12.2
kbps
voice
An
audio
analysis
and
scoring
tool
(TBD)
is onbe
Test
Description:
This
test
case
is
based
derive
their
unique
Estimated
Mean
Opinion
RAB/simbearer
R99
call.
There
will
therefore
new_U_RNTI.
preferable
that
PESQ
scores
are
used
for KPI
on.
There
are
now
8 established.
active
CS
voice
calls
in as
call
to
PSTN/ISDN
is
A
pre-recorded
Test
Ref:
KPI-3.0-056
old
KPI-2.4-020
then
used
to
compare
the
source
and
received
measuring
the DL
ofother
MTM
call.
Whilst
Score
(EMOS).
Itcalls.
isquality
preferable
that
PESQ
scores
in
totalare
8 active
First
3apairs
of
MTM
calls
Note
these
comparable
with
audio
progress.
A
pre-recorded
audio
waveform
is
audio
waveform
is8played
backed
from
the of
Requirement:
FTS-83234
R16,
FTS-106897
signals
tofor
establish
aUE's
Perceptual
Evaluation
there
are
another
are
in
call
one
used
KPIUE
as
these
are
comparable
with
are
established
e.g.
UE1
to
UE2,
to of
UE4
1.
QUALCOMM
LOG_CODE
for
Vocoder
application
PESQ
scores
where
asUE3
EMOS/MOS
played
backed
on
UE7
and
received
and
PSTN/ISDN
side
and
received
and
recorded
at
R30
Speech
Quality
(PESQ)
score
of
the
UL
audio.
which
is
atomulti-RAB/simbearer
R99
call.
There
other
audio
application
PESQ
scores
where
as
and
UE5
There
are
now
6 active
MTM
Packet
Characteristics
is
0x7144.
scores
cannot
beaudio
compared.
Next
all
calls
are
recorded
at UE6.
UE8.
An3 audio
analysis
and
scoring
the
UE
side.
An
analysis
and
scoring
tool
Test
Description:
automated
CS
voice
calls
PESQ
is an
algorithmic
non
subjective
will
therefore
be
inLOG_CODE
total
8 be
active
calls.
First
4
EMOS/MOS
scores
cannot
compared.
Next
CS
voice
calls
in
progress.
Then
two
further
2.
QUALCOMM
UE
0x412F
contains
terminated
and
the
test
is
repeated.
The
tool
(TBD)
ison
then
used
to
compare
the
source
Test
Ref:
KPI-3.0-057
old
KPI-2.4-022
(TBD)
is MTM
then
used
to
compare
thee.g.
source
and
are
started
UE1,
UE2
and
UE3.
Next
anpass
(objective)
audio
quality
score
from
which
pairs
of
calls
are
established
UE1
to
all
calls
are
terminated
and
the
test
is
calls
are
established
as
UE
to
PSTN/ISDN
on
information
ofsignals
radioBearerReconfiguration.
criteria
issignals
that
the
MOS
should
be
than
and
received
to is
establish
alarger
Perceptual
Requirement:
FTS-83234
R17,
FTS-106897
received
to
establish
a
Perceptual
automated
R99
PS
call
performed
on
UE4.
audio
scoring
tools
derive
their
unique
UE2,
UE3
to
UE4
...UE7
to UE8.
There
are
now
repeated.
The
pass
that
MOS
UE7
and
UE8.
Next
acriteria
R99
PSis(PESQ)
RAB
isthe
3.
CS
voice
handover
interruption
can
also
be
3.5
(mean).
Evaluation
of
Speech
Quality
score
of
R31
Evaluation
of
Speech
Quality
(PESQ)
score
of
Once
the
R99
bearer
is
established
then
an
Estimated
Mean
Opinion
(EMOS).
It
is
8
active
CS
voice
calls
in
progress.
Next
a
R99
should
be
larger
than
3.2
(mean).
established
on
UE1
and
aScore
data
transfer
started.
identified
by
recorded
voice
gap,
using
Cool
the DL
UL->DL
audio.
PESQ
an
algorithmic
non
Test
Description:
As
per
KPI-2.4-018
with
the
audio.
PESQ
is
an
algorithmic
non
automated
FTP
session
isis
started
and
preferable
that
PESQ
scores
are
used
for
KPIthe
as
PS
RAB
is established
on
UE1
and
data
UE1
should
be in
close
proximity
toa score
the
Femto.
Editor.
Test
Ref:
KPI-3.0-058
old
KPI-2.4-019
subjective
(objective)
quality
from
exception
that
prior
toaudio
the
automated
R5
PS
subjective
(objective)
audio
quality
score
from
connected
to the
data
server
(FTP
server)
these
are
comparable
with
other
audio
transfer
started.
UE1
should
be
in
close
On
one
pair
of
MTM
calls
e.g.
UE
7
to
UE8,
a
4.
Requirement:
It
is
recommended
FTS-83234
to
play
R18,
a
mono
FTS-106897
tone
which
audio
scoring
tools
derive
their
unique
call
starting,
3 UE's
located
on
the
same
Femto
which
audio
scoring
toolsOn
derive
their
unique
within
theto
test
environment.
After
connection
is
application
PESQ
scores
where
as
EMOS/MOS
proximity
the
Femto.
one
pair
of
MTM
pre-recorded
audio
waveform
is(EMOS).
played
R32
during
the
test.
Estimated
Opinion
Score
It
are
in acannot
CSMean
call.
This
KPI should
also
be backed
Estimated
Mean
Opinion
Score
(EMOS).
It is
is
established
files
repeatedly
downloaded
scores
be
compared.
Next
all
are
calls
e.g.
UE
7and
toare
UE8,
aautomated
pre-recorded
audio
and
received
recorded
atare
the
end
UE.KPI
An
Test
Description:
An
CScalls
voice
call
preferable
that
PESQ
scores
for
as
automated
to
run
with
HSUPA
asused
per
preferable
that
PESQ
scores
are
used
for
KPI
as
from
the
data
server
(FTP
andKPI-2.3terminated
and
the
test
is server)
repeated.
The
pass
waveform
is
played
backed
and
received
and
Test
Ref:
KPI-3.0-059
old
KPI-2.4-021
audio
analysis
and
scoring
tool
(TBD)
is
then
is
started
on
UE1.
Next
an
automated
R99
PS
The
pass
criteria
for
Femto
to
Femto
CS
voice
these
are
comparable
with
other
audio
014
and
with
3the
UE's
located
onbe
the
same
Femto
these
are
comparable
with
other
audio
times/data
rate
recorded.
Next
files
are than
criteria
is
that
MOS
should
larger
recorded
at
the
end
UE.
An
audio
analysis
and
Requirement:
FTS-83234
R16,
FTS-106897
used
to
compare
the
source
and
received
call
is
performed
on
UE2.
Once
the
R99
bearer
Handover
isPESQ
that
the
mean
interruption
application
scores
where
as
EMOS/MOS
in
a (mean).
CS
call.
For HSUPA
test
Category
3 time
UE
application
PESQ
scores
where
as
EMOS/MOS
repeatedly
uploaded
to the
data
server
(FTP
3.5
scoring
tool
(TBD)
isan
then
used
toEvaluation
compare
the
R33
signals
to
establish
a
Perceptual
of
should
is
established
be
less
then
than
200ms.
automated
FTP
scores
cannot
be
compared.
Next
all
are
should
be
used.
For
HSDPA
Category
8session
UE
scores
cannot
be
compared.
Next
all calls
calls
are
server)
and
times/data
rates
recorded.
All
UL
source
and
received
signals
to
establish
a
Test
Description:
As
per
KPI-2.4-015
with
the
Speech
Quality
(PESQ)
score
of the
is
started
and
connected
torepeated.
the
dataUL->DL
server
terminated
and
the
is
The
should
be
used.
terminated
and
the test
test
is
repeated.
The
pass
and
DL
throughputs
are
to
be measured
atpass
FTP
Test
Ref:
KPI-3.0-060
old
KPI-2.4-023
Perceptual
Evaluation
of
Speech
Quality
(PESQ)
exception
that
prior
to
the
automated
R99
PS
audio.
PESQ
is the
an
algorithmic
non
subjective
(FTP
server)
within
the
test
environment.
After
criteria
is
that
MOS
should
be
larger
than
criteria
isthe
that
the
MOS
should
be
larger
application
layer
(includes
TCP,
RLC,
RF than
Requirement:
FTS-83234
R17,
FTS-106897
score
of
UL->DL
audio.
PESQ
is
an
call
starting,
3
UE's
located
on
the
same
Femto
(objective)
audio
quality
score
from
which
connection
established files are repeatedly
3.2 (mean).
(mean).is
3.5
overheads)
over
entire file transfer
period. The
R34
algorithmic
non
subjective
(objective)
are
in scoring
a CS call.
audio
tools
derive
unique
downloaded
from
the
datatheir
server
(FTPaudio
server)
intent
isscore
to measure
theper
time
necessary
to the
Test
Description:
As
KPI-2.4-018
with
quality
from
which
audio
scoring
Estimated
Mean
Opinion
Score
(EMOS).
It is
and
times/data
rate
recorded.
Next
filestools
are
perform
a that
FTP
transfer
of R18,
an
ASCII
file,
from
the
exception
prior
to
the
automated
R5
PS
derive
their
unique
Estimated
Mean
Opinion
Requirement:
FTS-83234
FTS-106897
R33
preferable that
PESQ to
scores
are used
for
KPI
as
repeatedly
uploaded
the data
server
(FTP
FTP
Server
to
the
UE
in
DL
and
from
UE
toFemto
FTP
call
starting,
3
UE's
located
on
the
same
Score
(EMOS).
It is
that
PESQ
scores
Test
Description:
Aspreferable
per
KPI-2.4-015
with
the
these
are
comparable
with
other
audio
server)
and
times/data
rates
recorded.
All
UL
Server
UL.
The
duration
can
be
measured
as
are
in
ainCS
call.
This
KPIthe
should
also
beR99with
used
for
KPI
as
these
are
comparable
exception
that
prior
to
automated
PS
application
PESQ
scores
where
as
EMOS/MOS
and DL throughputs are to be measured at FTP
the
time
elapsed
between;
First
FTP
data
automated
to
run
with
HSUPA
as
per
KPI-2.3other
audio
application
PESQ
scores
where
as
call
starting,
1 be
UE's
located
onNext
the
same
Femto
scores
cannot
compared.
all
calls
are
application
layer
(includes
TCP,
RLC,
RF
packet
oncannot
the
mobile/Server
andFemto
Last
014
and
with
3 UE's
located
on
the same
EMOS/MOS
scores
compared.
are
in
areceived
CS
call.
terminated
and
test
is be
repeated.
TheNext
pass
overheads)
overthe
entire
file
transfer
period.
The
TCP
ACKcall.
FINterminated
received
bytest
mobile
acknowledging
in
acalls
CS
For
HSUPA
Category
all
are
the
test
is 3 UE
criteria
the
MOS
should
be
larger
than
intent
isis
tothat
measure
theand
time
necessary
to
all
TCP be
packets.
Both
messages
can
be
should
used.
For criteria
HSDPA
Category
8MOS
UE
repeated.
TheFTS-83234
pass
that
the
Requirement:
FTS-106897
3.5
(mean).
perform
a FTP
transfer
of R19,
an is
ASCII
file,
fromR33
the
captured
WireShark
on
test PC that
issued
should
bewith
used.
larger
than
3.2
(mean).
Test
Description:
As
per
KPI-2.4-015
with
FTP Server to the UE in DL and from UE
tothe
FTP
the
FTP.
Also
the
reported
times/data
rates
as
exception
thatThe
prior
to the automated
R99 PS
Server in UL.
duration
can be measured
as
reported
by the
FTP located
client application
may also
Requirement:
R34
call
starting,
7FTS-106897
UE's
on the
the time
elapsed
between; First
FTPsame
data Femto
be used
for call.
results.
Test
Description:
As per KPI-2.4-018 with the
are
in
areceived
CS
packet
on the mobile/Server and Last
exception that prior to the automated R5 PS
TCP ACK FIN received by mobile acknowledging
Voice Quality

iterations
Pass
3.9990
Voice Quality

iterations
Pass
3.7933
Voice Quality

iterations
Pass
3.6670
Availability
In progress
Manual Test
Pass
20 mins
Availability
In progress
Manual Test
Pass
20 mins

iterations
Pass
173ms
Voice Quality

iterations
Pass
4.0060
Voice Quality

iterations
Pass
3.5310
Voice Quality

iterations
Pass
4.0300
Voice Quality

iterations
Pass
3.5420
Voice Quality

iterations
Pass
4.4800
Voice Quality

iterations
Pass
4.0400
Voice Quality

iterations
Pass
4.0190
Voice Quality

iterations
Pass
4.4500
Voice Quality

iterations
Pass
4.0170
Voice Quality

iterations
Pass
4.0200
PS Data - R99

iterations
Pass
PS Data HSDPA

iterations
Pass
PS Data - R99

iterations
Pass
PS Data - R99

iterations
Pass
PS Data HSDPA

iterations
Pass
58k UL
119kUL
367kUL-udragon ftp
3
voice
issue
calls
+1
60kDL
packet
120kDL
Average
360kDL
60k
UL
DL data
118kUL
rate is
361kUL5250Kb/s udragon
7.5Mbps
60k
UL
ftp
issue
Average
118kUL
60kDL
UL data
364kUL120kDL
rate is
udragon
360kDL
1187Kb/s
1
ftpvoice
issue
1.2
call mbps
+1
60kDL
packet
120kDL
(360kDL
for all
7.5Mbps
DL and
1.2Mbps
UL)
Average
DL data
rate is
5109
Average
UL data
rate is
1186
BCR2.2
y
FTS-77715
Success rate of CS calls for MOC, MTC and MTM
R2
FTS-77715
Success rate of PS calls
R3
FTS-77715
Success rate of CSD calls
R4
FTS-77715
CS Voice Drop Call Rate
R6
FTS-77715
CS Data Drop Call Rate (call duration 2 mins)
R7
FTS-77715
Femto -> Macro Handover Failure Rate From BSR

Femto To 3G Macro Network Intra Frequency in
handover region
R8
FTS-77715
Femto -> Macro Handover

Failure Rate From BSR Femto To 3G Macro Network
Inter Frequency in handover region
R9
FTS-77715
Femto -> Macro 2G Handover Failure Rate in

handover region
R10
FTS-77715
FTP - R99 Throughput on UL 64, UL 128, UL 384, DL

64, DL128, DL384. % of max bit rate.
(measured at FTP application)
R15
FTS-77715

(measured at FTP application)
R16
FTS-77715
UL Voice Speech Quality - AMR 12.2 kbps Femto

Mobile to PSTN/ISDN
R17
FTS-77715
DL Voice Speech Quality - AMR 12.2 kbps PSTN/ISDN

to Femto Mobile
R18
FTS-77715
Voice Speech Quality - AMR 12.2 kbps Femto Mobile

to Femto Mobile
R19
FTS-77715
Voice Latency Femto Mobile to Femto Mobile call

excluding DSL contribution
FTS-77715
Delay between following power-on and femtocell

service availability
R24
FTS-77715
3G PING (Round Trip Delay) ping delay on UL 64, UL

128, UL 384, DL 64, DL128, DL384
R26
FTS-77715
HSDPA PING (Round Trip Delay) using 64kbps UL

bearer
R27
FTS-77715
HSUPA 1.4 Round Trip Time using HSDPA DL bearer
R28
FTS-77715
Access restriction time in the case of authorized UE
R31
FTS-77715
Access restriction time in the case of non authorized

Femto UE
R32
FTS-77715
Access restriction time in the case of non authorized

public UE
R33

Requirement: FTS-77715 R2, FTS-106897 R37
Test Description: Automated CS calls
performing a mixture of MOC, MTC and MTM
Test
KPI-3.0-062
old KPI-2.4-008
withinRef:
1 Femto.
The mixture
of calls will be
Requirement:
FTS-77715
R3, FTS-106897
R38
evenly split 33.3%
MOC, 33.3%
MTC and 33,3%
Test
Automated
repeated PS
MTM.Description:
The success rate
will be calculated
and
calls
withinSuccess
1 Femto.
PSand
callspass
will criteria
be evenly
recorded.
rate
are
Test
Ref: KPI-3.0-063
old KPI-2.4-004
split
between
defined
as: R99 33.3%, R5 (HSDPA) 33.3%
Requirement:
FTS-77715
R4,
FTS-106897
and
R6 Setup
(HSUPA)
33.3%.Rate
The
rate will
CS Call
Success
=success
(CS Successful
(BCR
2.4) R39 and recorded. Success rate and
be
RRCcalculated
Connection
Establishment Rate) * (1Test
Description:
Automated
CSD MTM call
pass
criteria
are
defined
as:
(Standalone
CS SRB Drop
Rate/100))
* CS RAB
Test
Ref:KPI-3.0-064
old
KPI-2.4-002
within
Femto.
The success
rate
be
PS
Call1Setup
Success
Rate
=)/100.
( PSwill
Successful
Establishment
Success
RateR6,
CS VoiceR41
Requirement:
FTS-77715
FTS-106897
calculated
and recorded.
Success
rate (and
RRC
Connection
Establishment
Rate)
1Call Setup
Success
Rate
for MOC,
MTC* and
Test
Description:
Automated
are
pass
criteria
areSRB
defined
as: CS CS
Callcalls
Setup
(Standalone
PS
Drop
PS RAB
MTM shall be
greater
thanRate/100))
99% are to* be
performed
using
1
Femto.
Calls
held
Success
Rate =Success
(CS Successful
RRC Connection
Establishment
Rate
/100
Test
Ref:KPI-3.0-065
old
KPI-2.4-005
for
a minimum Rate)
of 2 minutes.
Then callCS
should
Establishment
* (1-(Standalone
SRB
PS
Call Setup Success
Rate R7,
shall
be greater
Requirement:
FTS-77715
FTS-106897
be
released.
Any
dropped
calls
within
the
2R42
Drop
Rate/100))
* CS
RAB
Establishment
than 99%.
Results
for
R99,
R5 and
willcall
be
Test
Description:
Automated
CSDR6
MTM
minute
period
should
beData
recorded.
CS
drop call
Success
Rate )/100.
CS
Call Setup
stored
separately.
Where
possible
within
Femto.asCalls
are to
be heldwithin
a the
rate
is 1
defined
the total
number
offorthan
Success
Rate
for
MTM
shall
be
greater
automation
environment
the
same
UE device
Test
Ref: of
KPI-3.0-066
old
KPI-2.4-035
minimum
2 minutes.
Then
call the
should
be
abnormally
released
CS
RAB
over
total
99%
will
be used fordropped
R99,
R5 calls
andR8,
R6.
Requirement:
FTS-77715
FTS-106897
R43
released.
within
the 2 for
number of Any
Successful RAB
Establishments
Test
Description:
This KPI
should have
the
minute
period
should
recorded.
CSD
drop
CS. Pass
criteria
is CSbe
voice
drop call
rate
shall
following
pre-requites
in place.
The Femto
is
call
rate
is
defined
as
the
total
number
of
be less
than
0.5%
Test
Ref:
KPI-3.0-067
old KPI-2.4-036
appropriately
configured
that the
abnormally released
CSDsuch
RAB over
the 3G
total
Requirement:
FTS-77715
R9, FTS-106897 R44
Macro
is of
present
in theRAB
intra-frequency
number
Successful
Establishments for
Test
Description:
This KPI should
have the
neighbour
list.
An
automated
controllable
CSD. Pass criteria is that CSD drop call rate
following
pre-requites
in
place.
The
Femto
is
attenuation
system
is in place and can control
shall
be less
than 0.6%.
Test
Ref:
KPI-3.0-068
old
KPI-2.4-038
appropriately
such
that the control
3G
Femto and 3Gconfigured
Macro. The
attenuation
Requirement:
FTS-77715
R10, FTS-106897
Macro
is present
in the
inter-frequency
is set such
that the
UE can
only see the Femto
R45
neighbour
list. see
An automated
controllable
and marginally
the 3G Macro,
or not see
Test
Description:
This
should
havecontrol
the
attenuation
system
in KPI
place
and can
the
Macro
at all.isNext
the
automated
UE is
Test3G
Ref:
KPI-3.0-069
old
KPI-2.4-015
following
place.
The
Femto is
Femto,
3Gpre-requites
Macro
and ifin
required
a noise
placed into
a CSFTS-77715
voice
call
once
the
call has
Requirement:
R15,
FTS-106897
appropriately
configured
such
that
thesuch
2G
source.
The attenuation
control
is set
been
successfully
held
for
approximately
10
R47
Macro
is UE
presentonly
in the
inter-RAT
neighbour
list.
that
the
see
the cross
Femto
and such
seconds
thecan
attenuators
are
faded
Test
Description:
Automated
R99
PS call
is
An automated
controllable
attenuation
system
marginally
see the
3G 3G
Macro,
or not
the 3G
that the
neighbouring
a see
better
Test
Ref:
KPI-3.0-070
oldMacro
KPI-2.4-018
performed
on 1can
Femto
cell.
Onceisand
the
R99
is
in place
and
control
Femto
Macro
at all.
Next
the automated
UE 2G
is placed
candidate,
quality
(Ec/No),
and
signal
strength
Requirement:
FTS-106897
R48
bearer
isThe
established
then
an automated
FTP
Macro.
attenuation
control
ishas
setbeen
such
that
into
aDescription:
CS
voice
once
the callHSxPA
(RSCP)
than
thecall
serving
Femto.
The
automated
Test
Automated
PS
call is
session
is started
and
connected
to marginally
the
data
the
UE can
only
see
the
Femto and
successfully
held
forthe
approximately
10HxDPA
seconds
UE
should
maintain
CSthe
call
and
correctly
performed
on
1 Femto
cell.
Once
the
server
(FTP
server)
within
test
see
the
2GKPI-3.0-071
Macro,
or
not
see
the
2G Macro
at
the
attenuators
are
cross
faded,
and
noise
Test
Ref:
old
KPI-2.4-046
handover
to the
3Gconnection
Macro
and
continue
to
bearers
(HSDPA
and
HSUPA)
are
established
environment.
After
is
established
all.
Next
the automated
UER17,
issuch
placed
a CS
source
increased,
thatinto
theand
Requirement:
FTS-106897
maintain
the callFTS-77715
for
at least
30 is
seconds
then
anpotentially
automated
FTP
session
started
files
are
downloaded
from
theonce
data
voice
callrepeatedly
once3G
the
call
has
successfully
neighbouring
Macro
is a been
better
candidate,
R49
the
handover
is
completed.
We
can
verify
that
connected
to
the
data
server
(FTP
server)
server
(FTP
server) and10
times/data
rate
held
for
approximately
seconds
the
quality
(Ec/No),
andAn
signal
strength
(RSCP)
Test
Description:
automated
MOC
AMR
the UE
has
performed
the
handover
onto
the to
within
the
test
environment.
After connection
is
recorded.
Next
files
are
repeatedly
uploaded
attenuators
are
cross
faded
such
that
the
Test
Ref:serving
KPI-3.0-072
old
KPI-2.4-047
than
the
Femto.
automated
12.2
kbps
CS
voice
toThe
PSTN/ISDN
correct
Macro
bycall
checking
the
cellisid. UE
Next
established
files
are
repeatedly
downloaded
the
data3G
server
(FTP
server)
and
times/data
neighbouring
2G
Macro
is aR18,
better
candidate,is
Requirement:
FTS-77715
FTS-106897
should
maintain
the
CS
call
and
correctly
established.
A
pre-recorded
audio
waveform
the automated
UE
isthe
ended
and
the (FTP
and
also
uploaded
from
data
server
rates
recorded.
Allcall
UL
and
DL
throughputs
are
quality
(Ec/No),
and
signal
strength
(RSCP)
R50
handover
totimes/data
thefrom
3G Macro
and
continue
played
backed
therate
UE
and
received
and
attenuators
reconfigured
such
that
UE can
only
server)
and
recorded.
Allto
to
bethe
measured
at
FTP
application
layer
than
serving
Femto.
The 30
automated
UE
Test
Description:
An
MOC
AMR
maintain
the
call
formarginally
at automated
least
seconds
once
recorded
at and
PSTN/ISDN
side.
An
audio
analysis
see
the
Femto
and
see
the
seperate
DL
UL
throughputs
are
to3G
be
(includes
TCP,
RLC,
RF
over
entire
Test
Ref:
KPI-3.0-073
old
KPI-2.4-045
should
maintain
the
CSoverheads)
call
and
correctly
12.2
kbps
CS
voice
call
PSTN/ISDN
iscompare
the handover
is completed.
We
can
verify
that
and
scoring
tool
(TBD)
isto
then
used
to
Macro,
or not
see
the
3G
Macro
at
all.
As the
measured
atperiod.
FTP
application
layer
(includes
file
transfer
The
intent
is
to
measure
Requirement:
FTS-77715
R19,
FTS-106897
handover
toand
the
2G Macro
and
continue
totheais
established.
A
pre-recorded
audio
UE
hasRF
performed
the
handover
onto
the
source
signals
towaveform
establish
automated
UE
isreceived
in idle
mode
it
should
perform
TCP,
RLC,
overheads)
over
entire
file
the
time
necessary
to
perform
aseconds
FTPside
transfer
of
R51
maintain
the
call
for
at
least
30
once
played
backed
from
and
correct
3G
Macro
by the
checking
the
cell
id.and
Next
Perceptual
Evaluation
of
Speech
Quality
(PESQ)
a cell
reselection
back
toPSTN/ISDN
the
Femto
cell
transfer
period.
The
intent
is to
measure
the
an
ASCII
file,
from
the
FTP
Server
to
the
UE
in
Test
Description:
An
automated
MTM
CS
AMR
the
handover
isUE
completed.
We
can
verify
that
received
and
recorded
at ended
the
UE
side.
An
audio
the
automated
call
is
and
the
score
of the
UL
audio.
PESQ
is
an
algorithmic
this
can
be
verified
by
checking
the
cell
id
time
necessary
to
perform
a
FTP
transfer
oftoan
0 Test
Ref:
KPI-3.0-074
old
KPI-2.4-063
DL
from
UE
to
Server
inisUL.
The
12.2
kbps
voice
callFTP
istool
established.
A
pretheand
UE
has
performed
the
handover
onto
the
analysis
and
scoring
(TBD)
then
used
to
attenuators
reconfigured
such
that
UE
can
only
non
subjective
(objective)
audio
quality
score
verify
the
UE
is
back
on
the
original
test
Femto.
ASCII
file,can
from
the
FTP Server
toFTS-106897
the
UEelapsed
in DL
Requirement:
FTS-77715
R20,
duration
be
measured
the
time
recorded
audio
waveform
isas
played
backed
correct
2G
Macro
by
checking
the
cell
id.
Next
compare
the
source
and
received
signals
see
Femto
and
marginally
see
the
3G to
from
which
audio
scoring
tools
derive
their
Thethe
test
is
now
ready
to
be
repeated.
and
from
UE
toreceived
FTP
Server
inrecorded
UL.
The
duration
R52
between;
First
FTP
data
packet
received
on the
from
UE1
and
at
UE2.
the
automated
UEthe
call
is
ended
and
the
establish
aand
Perceptual
Evaluation
Speech
Macro,
or
not
see
3G
Macro
atof
all.
As
the
unique
Estimated
Mean
Opinion
Score
(EMOS).
can
be
measured
as
the
time
elapsed
between;
Test
Description:
An
automated
MTM
CS
mobile/Server
and
Last
TCP
ACK
FIN
received
An
audio
analysis
and
scoring
tool
(TBD)
is AMR
attenuators
reconfigured
such
that
UE
can
only
Quality
(PESQ)
score
of
the
DL
audio.
PESQ
is
automated
UE
is
in
idle
mode
it
should
perform
It
is
preferable
that
PESQ
scores
are
used
for
Test
Ref:
KPI-3.0-075
oldall
KPI-2.4-024
Femto
to data
Macro
Cell
Handover
Failure
Rate
is
First
FTP
packet
received
on
the
12.2
kbps
voice
callmarginally
is
established.
A preby
mobile
acknowledging
TCP
packets.
Both
then
used
to compare
the
source
and
received
see
the
Femto
and
see
the
2G
an
algorithmic
non
subjective
(objective)
audio
a
cell
reselection
back
to
the
Femto
cell
and
KPI
as
these
are
comparable
with
other
audio
Requirement:
FTS-77715
R24,
FTS-106897
defined
as
the
number
of
unsuccessful
mobile/Server
and
Last
TCP
ACK
FIN
received
recorded
audio
waveform
is
played
backed
messages
canfrom
be the
captured
withscoring
WireShark
on
signals
to
establish
a Perceptual
Evaluation
of
Macro,
or
not
see
2G
Macro
at
all.
As
the
quality
score
which
audio
tools
this
can
be
verified
by
checking
the
cell
id
to
application
PESQ
scores
where
as
EMOS/MOS
R56
handovers
from
BSRthe
Femto
to
3Gthe
Macro
by
mobile
acknowledging
allAlso
TCP
packets.
Both
from
UE1
and
received
and
recorded
at
UE2.
test
PC
that
issued
FTP.
reported
Speech
Quality
(PESQ)
score.
PESQ
is
an
automated
UE
isback
in
idle
mode
it
should
perform
derive
their
unique
Estimated
Mean
Opinion
verify
the
UE
isbe
on
the
original
test
Femto.
scores
cannot
compared.
Next
the
Test
Description:
Femto
power-on
toto
be
Network
intra-frequency,
inbe
the
handover
messages
can
captured
with
WireShark
on
An
audio
analysis
tool
will
required
times/data
rates
as
reported
by
the
FTP
client
algorithmic
nonbe
subjective
(objective)
audio
aThe
cell
reselection
back
to
the
Femto
cell
and
Score
(EMOS).
It
is
preferable
that
PESQ
scores
Test
Ref:
KPI-3.0-076
old
KPI-2.4-010
test
is
now
ready
to
be
repeated.
call
is
ended
and
the
test
is
automated
with
the
use
of
reboot
command.
region,
relative
to
the
total
number
of
handover
test
PC
that
issued
the
FTP.
Also
the
reported
measure
theverified
voice
call
latency.
Femto
Mobile
application
may
also
bechecking
used
for
results.
quality
score
from
which
audio
scoring
tools
this
can
be
by
the
cellMOS
idwith
to
are
used
for
KPI
as
these
are
comparable
Requirement:
FTS-77715
R26,
FTS-106897
repeated.
The
pass
criteria
is
that
the
Femto
will
be
controlled
via
automation
system
attempts.
number
of
unsuccessful
times/data
rates
as Estimated
reported
by
the
FTP
client
to
Mobile
Voice
call
latency,
call
bearer
delay,
derive
their
unique
Mean
Opinion
verify
the
UE
isduring
back
on
the
original
test
other
audio
application
PESQ
scores
where
as R57
Femto
to
Cell
Failure
Rate
is
should
beMacro
larger
thanHandover
3.5
(mean),
3.2
(95%tile).
and
rebooted,
reboot
Femto
to
beFemto.
handovers
=
(number
of
handover
attempts)
application
may
also
be
used
for
results.
For
is
one
way
end-to-end
delay
for
the
speech
The
following
file
sizes
should
be
used
Score
(EMOS).
Itready
is
preferable
that
PESQ
scores
The
test
isand
now
to
be
repeated.
EMOS/MOS
scores
cannot
be
compared.
Next
Test
Description:
Automated
R99
PS
call
defined
as
the
number
of
unsuccessful
monitored
logged.
Service
availability
will
(number
of
Successful
handovers).
The
Femto
HSxPA
10MB
file
size
should
be
used.
Pass
channel
when
the
call
is
in
progress.
The
end
throughput
testing
and
bearer
configurations:
are
used
for
KPI
as
these
are
comparable
with
Test
Ref:
KPI-3.0-077
old
KPI-2.4-011
the
automated
call
is
ended
and
the
test
is
within
1that
Femto.
Once
R99
PS
bearer
is
handovers
from
BSR
Femto
to
3G
Macro
be
measured
from
the
start
of
the
reboot
until
->
Macro
Handover
Failure
Rate
shall
be
less
criteria
single
UE
HSDPA
average
user
reference
points
are
the
Mouth
Reference
Point
1MB
file
for
UL
and
DL
R99
RAB
64
kbps
and
other audio
application
PESQ
scores
where
as
Requirement:
FTS-77715
R27,
FTS-106897
Femto
to inter-frequency,
Macro
Cell
Handover
Failure
Rate
repeated.
The
pass
criteria
isaccepted
that
the
MOS
established
and
PDP
context
anofis
Network
in
the
handover
Femto
is
correctly
started
and
transmitting
and
than
1%.
throughput
shall
be
greater
than
84.00%
(MRP)
of
one
mobile
and
the
Ear
Reference
128
kbps
EMOS/MOS
scores
cannot
be
compared.
Next
R58
defined
as
the
number
of
unsuccessful
should
be
larger
than
3.5
(mean),
3.2
(95%tile).
automated
ping
(ICMP
echo
request)
isshould
region,
relative
to
the
total
number
ofpass
handover
in
service.
Pass
criteria
is
that
Femto
be
peak
physical
layer
bit
rate
for
the
Point
(ERP)
in UL
the
other
mobile.
The
10
MB
file for
and
DL
R99
RAB
384
kbps
the
automated
call
is
ended
and
the
test
is PS
Test
Description:
Automated
R5
(HSDPA)
handovers
from
Femto
to
2G
GSM
Macro,
performed
with
aBSR
32
Byte
and
times
recorded.
attempts.
The
number
of
unsuccessful
in
service
in
less
than
3
minutes.
corresponding
UE
category
with
CQI>
24.
All
criteria
is
such
that
the
Femto
Mobile
to
Femto
Test
Ref: KPI-3.0-078
old
repeated.
The
pass
criteria
is that
the
MOS
call
within
1
Femto
using
a KPI-2.4-012
Cateory
8 UE.
Once
in
the
region,
relative
to
the
total
This
ishandover
repeated
with
aof
500
Byte
payload.
handovers
=should
(number
handover
attempts)
HSxPA
tests
be
conducted
with
athan
UEThe
Mobile
Voice
call
latency
should
be
less
Requirement:
FTS-77715
R28,
FTS-106897
Automated
test
will
be
split
evenly
between
the
should
be
larger
than
3.2
(mean),
3.0
(95%tile).
HSDPA
PS
bearer
is
established
and
PDP
number
of
handover
attempts.
number
of
test
should
be
performed
equally using
(number
ofmean
Successful
handovers).
Therate
Femto
which
isR99
capable
of
the
maximum
data
200
msec
and
(95%
250 ping
msec),
R59
various
bearer
options
for
context
accepted
anconfiguration
automated
unsuccessful
handovers
= -(number
of(ICMP
matched
UL
and
DL
bearer
configurations
with
->
Macro
Handover
Failure
Rate
shall
be
less
supported
by
the
Femto
e.g.
current
Femto
BSR
excluding
any
delay
by
DSL.
Test
Description:
Automated
R6
(HUDPA)
PS
R99
UL
and
DL.
Such
that
UL
64
UL
echo
request)
is
performed
with
a(16.6%),
32
Byte
and
handover
attempts)
-intruduced
(number
of
Successful
32
Bytes
500
Byte
payload
results
e.g.
UL
than
1%.
Test
Ref:and
KPI-3.0-079
old
can
support
HSDPA
Category
8,
of
The
latency
shall
be
end
to
end.
DSL
delay
call
within
1Femto
Femto
using
a KPI-2.4-029
Cateory
(HSUPA
128
(16.6%),
UL This
384
(16.6%),
DLbearer
643(16.6%),
times
is
repeated
with
a
500
handovers)
->
Macro
Handover
Failure
64K
DLrecorded.
64L
(33.3%),
UL
128K
DL
128L
(33.3%)
Requirement:
FTS-77715
R31,
FTS-106897
7.2Mbps
and
Category
3,
bearer
contribution
isHSUPA
not
easy
to1%.
be
meaured.
1.46Mbps)
/ Category
8(16.6%).
(HSDPA
7.2Mbps)
DL128
(16.6%),
DL384
Test
passUE.of
Byte
payload.
The
test
should
be
performed
RateUL
should
be
less
than
and
384K
DL
384K
(33.3%).
The
purpose
R60
1.46Mbps.
Once
HSUPA
PSbearer
bearer
is established
and PDP
criteria
than
94
% of
using
a is
UL
64K
with
a DL
7.2MBps
the test
isthroughput
to
measure
the
Round
Trip
Delay
Test
Description:
Femto
isphysical
set ping
to
closed
context
accepted
an32
automated
(ICMP
corresponding
radio
bearer
layer
bit
(Category
8the
UE)
for
Byte
and
500
Byte
(RTD)Ref:
from
originating
UE
and
the
data
Test
oldwith
KPI-2.4-030
mode.
An KPI-3.0-080
automated
UE
anavalid
SIM and
i.e.
echo
is performed
with
32test
Byte
rate. request)
payload
results.
The
purpose
of
the
is to is
server.
Pass
criteria
for
R99
32
Bytes
payload
Requirement:
FTS-77715
FTS-106897
the
UErecorded.
is authorised
on
theR32,
Femto
ACLa and
also
times
This
is
repeated
with
500
measure
the Round
Trip (95%ile).
Delay (RTD)
from
the
200ms
(mean)
and
230
Pass
criteria
R61
the
HLR,
comes
into
coverage
of
the
Femto
by
Byte payload.
The the
testdata
should be performed
originating
and
criteria
for
R99
500UE
Bytes
is Femto
300msisserver.
(mean)
and 350ms
Test
Description:
set to Pass
closed
either;
attenuator
automatically
using
aadjusting
ULKPI-3.0-081
HSUPA
1.46Mbps
bearer
with
aor
DLby
for
HSDPA
32
Bytes
payload
is
68ms
(mean)
Test
Ref:
old
KPI-2.4-031
(95%ile).
mode.
Anthe
automated
with
an
invalid
changing
mode
of UE
the
UE.
When
the SIM
UE
HSDPA
7.2Mbps
for
32
Byte
and
500
Byte
andthe
82 (95%ile).
Pass criteria
R99
500ACL,
Requirement:
R33,
FTS-106897
i.e.
UEtoiscamp
notFTS-77715
authorised
onfor
the
attempts
onto
the Femto
itFemto
should
be
payload
results.
The
purpose
of the
test is to
Bytes
isinto
80ms
(mean)
(95%ile).
R62
comes
coverage
ofand
the95ms
Femto
by either;
accepted
within
1.5 Trip
seconds.
Specifically
the
measure
the
Round
Delay
(RTD)
from
the
Test
Description:
Femto
is set to
open
mode.
adjusting
attenuator
automatically
or by
access
time
of
the
authorized
UE
should
be
originating
UE and
the data
server.
Pass
An
automated
UE with
an invalid
SIM
i.e.criteria
the
changing
the
mode
of
the
UE.
When
the
UE
measured
between
uplink
(RRC)
for HSDPA
32 Bytes the
payload
is message
68ms
(mean)
UE
is not authorised
on the
the Femto
Femto
asshould
there is
attempts
to campRequest"
onto
it
"RRC
Connection
(to for
perform
LAU)not
and
82
(95%ile).
Pass
R99
500
no
valid
HLR within
entry.
As criteria
Femto
is inSpecifically
open
mode
be
1.5
seconds.
andaccepted
downlink
message
(RRC)
"Security
Bytes
is 80ms
(mean)
and
95ms
(95%ile).
ACL
does
not
apply
The
UE
comes
into
the
access time
of the
non authorized
Command".
Access
restriction
time in UE
the case
coverage
the Femto
by either;
adjusting
should
be of
measured
between
the
uplink
of authorized
UE should
be less
than
1.5
attenuator
automatically or by changing the
message
seconds. (RRC) "RRC Connection Request" (to
mode
of LAU)
the UE.
the UE
attempts
to
perform
andWhen
downlink
message
(NAS)
camp
ontoUpdating
the Femto
it should
not be
accepted
"Location
Reject".
Access
restriction
within
seconds.
access
time in2the
case ofSpecifically
non authorized
Femto UE
restriction
timethan
in the
of non authorized
should be less
1.5case
seconds
public UE should be measured between uplink
message (RRC) "RRC Connection Request" (to
CS Voice

iterations
Pass
100%
PS Data HSDPA & R99

iterations
Pass
100%
CS Data

iterations
Pass
100%
CS Voice

iterations
Pass
0%
CS Data

iterations
Pass
0%
Mobility - Femto To 3G - Intra

iterations
Pass
0%

iterations
Pass
100%
U-Dragon issue
Pass
100%
PS Data - R99

iterations
Pass
PS Data HSDPA

iterations
Pass
Voice Quality

iterations
Pass
60k UL
118kUL
369 kULudragon
1347kb/s
ftp issue
4268kb/s
60kDL
120kDL
360kDL
4.0400
Voice Quality

iterations
Pass
3.5080
Voice Quality

iterations
Pass
4.4720
Voice Quality
Manual Test
Pass
185 ms
Availability
Result to be check
manually
Pass
<2.43
mins
PS Data - R99

iterations
Pass
PS Data HSDPA

iterations
Pass
PS Data - HSUPA

iterations
Pass
Authentication
Observed UE latching
to another femto after
several tries
Pass
64K/32b
122ms
64K/500b
242ms
32b
58ms
128K/32b
500b
140ms
75ms
128K/500b
222ms
32b 64ms
384K/32b
500b
112ms
78ms
384K/500b
135ms
0.615
seconds
Authentication
several tries
Pass
0.6
seconds
Authentication
several tries
Pass
1.4
seconds
FTS-77715
Percentage of successful Femto initialization

procedures
R34
FTS-77715
R35
FTS-77715
FTS-77715
Time of Cell Reselection from BSR Femto CPE to

3G Macro Network Intra Frequency in handover
region Note: This KPI is dependent on the UE not
the Femto cluster network elements
Time of cell reselection from BSR Femto CPE to
3G Macro Network inter frequency in handover
region Note: This KPI is dependent on the UE not
the Femto cluster network elements
Time of Cell Reselection from BSR Femto CPE
Network to 2G Macro
FTS-77715
Paging Success Rate
R38
FTS-77715
Average interval of recovering system faults

(Mean Time To Repair) of typical gateway
configuration (BSG, LVF, IPC)
R41
FTS-77715
Reconfiguration parameter download delay
R43
FTS-77715
Firmware upgrade download delay
R44
R36
R37

Requirement: FTS-77715 R34, FTS-106897
R63
Test Description: Femto initialization to be
Test
Ref: KPI-3.0-083
performed
using with the use of reboot
Requirement:
FTS-77715
R35
command. Femto
will be controlled
via
Test
Description:
automation
system and rebooted, during
reboot Femto to be monitored and logged.
Test Ref: KPI-3.0-084
Service availability will be checked and number
of successfully initializations counted and
Test Description:
number of failures also counted. Femto
initialization
success rate is defined as the
Test
Ref: KPI-3.0-085
number
of timesFTS-77715
when the Femto
Requirement:
R37 is initialized
successfully
after power on versus the total
Test
Description:
number of Femto power on. It is assumed that
the backhaul
network isold
working
properly. The
Test
Ref: KPI-3.0-086
KPI-2.4-007
successful initialization
is defined
by the layer
Requirement:
FTS-77715
R38, FTS-106897
one
R67 receives message
DPAT_Binding_Update_Response,
defined in
Test
Description: Automated CSas
calls
Test
Ref: KPI-3.0-087
IRD-BSR-BVG.
The
pass
criteria
is a success
performing
MTM
call
within
1 Femto,
UE1 will
Requirement:
FTS-77715
R41 UE under
rateUE2
greater
than
99%.
call
where
UE2
is the paging
Test
test. Description:
The paging success rate is defined as the
total number of received paging message
SERVICE REQUEST received by the BSR from
the UE as response to a UMTS CS/PS paging
Test Description:
procedure over total number of UMTS CS/PS
paging procedures. The pass criteria is rate
>98%
Test Description:
Availability
In progress
Manual Test
Pass
100%
Availability
In progress
Manual Test
Pass
0.5sec
Availability
In progress
Manual Test
Pass
0.5sec
Availability
In progress
Manual Test
Pass
1.3 sec
Paging

iterations
Pass
100%
Availability
In progress
Manual Test
Pass
12 min
Availability
In progress
Manual Test
Pass
12 sec
Availability
In progress
Manual Test
Pass
1.4 min
un 1
Run 2
Pass/Fail
Date
<1%
10/31/2011
<1%
10/31/2011
>98%
11/29/2011
>98%
12/2/2011
<200ms UL 12/1/2011
<300ms DL
<200ms UL 11/8/2011
<300ms DL
>3.5
12/8/2011
>3.2
12/7/2011
6..0s
9/1/2011
<200ms DL 10/12/2011
<300ms UL
0.6%
8/30/2011
>110kbps
8/18/2011
>55kbps
9/2/2011
>2Mbps
9/13/2011
>3.2 MTM
>3.5 MTC
>3.5 MOC
9/26/2011
>99%
10/5/2011
>99%
9/4/2011
>99%
10/2/2011
Results Notes
Tested in IPRC on
SIGRAN network
Detailed Results
Test report
location (HTML)
Test report
location (iTest)
Femto Details
Cluster Details
Serial:
Software version: BSR03.00.21_p
Hardware version: v2
Serial:
Power: 250mW Femto 709
Serial:
Serial:
Serial:
Serial:
Software version: BSR-03.00.30
Serial:
Software version: BSR-03.00.29
Serial:
Software version: BSR-03.00.8_p
Hardware version: v1.2
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Software version: BSR-03.00_17p
Serial:
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.18
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
Pass/Fail
Run 3
Result
Pass/Fail
Run 4
Result
Pass/Fail
Run 5
Result
Pass/Fail
Result
>99%
9/28/2011
>99%
9/29/2011
>99%
9/27/2011
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
6.0 seconds 8/22/2011
8.0 seconds 8/31/2011
3.0 mins
9/1/2011
12.0 mins
9/1/2011
<32.0 mins 10/11/2011
<20.0 mins 9/30/2011
<1%
9/16/2011
<1%
10/7/2011
<1%
9/16/2011
5040Kb/s
9/13/2011
1200kb/s
9/13/2011
<1.5
seconds
9/21/2011
<1.5
seconds
9/21/2011
4.0s MOC
6.0s MTM
8/23/2011
3.0s
7/28/2011
3.0s
8/23/2011
98%
10/3/2011
200ms dl
300ms ul
10/5/2011
Tested in IPRC on
SIGRAN network
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Software version: BSR03.00.10.38
Serial:
Serial:
Serial:
IOT Cluster1
(SGSN 3, MSC3)
Release 2.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.12
Serial:110945000
2
Software version:
BSR-02.04.50.42
IOT
Cluster3
Hardware
version:
(SGSN
3, MSC3)
DNI v2.5
EE
Release
2.10
Power: 250mW
Femto 705
IOT Cluster3
(SGSN 3, MSC3)
Release 2.13
IOT Cluster3
(SGSN 3, MSC3)
Release 2.14
IOT Cluster3
(SGSN 3, MSC3)
Release 2.6
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.6
IOT Cluster3
(SGSN 3, MSC3)
Release 2.16
IOT Cluster3
(SGSN 3, MSC3)
Release 2.15
>3.5
9/2/2011
>3.5
9/4/2011
>3..2
9/6/2011
<90 mins
9/21/2011
<90 mins
9/21/2011
200ms
10/12/2011
>3..5
8/12/2011
>3..5
8/14/2011
>3..2
9/8/2011
>3..5
8/14/2011
>3..2
8/8/2011
>3..5
9/9/2011
>3..5
9/11/2011
>3..2
8/11/2011
>3..5
9/11/2011
>3..2
9/8/2011
60k UL
120kUL
360kUL
60kDL
1176kb/s
120kDL
360kDL
8/18/2011
60k UL
120kUL
360kUL
60kDL
60k
UL
120kDL
120kUL
360kDL
360kUL
60kDL
1176kb/s
120kDL
5040kb/s
360kDL
8/18/2011
11/18/2011
8/18/2011
11/18/2011
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
IOT Cluster3
(SGSN 3, MSC3)
Release 2.1
IOT Cluster3
(SGSN 4, MSC3)
Release 2.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.17
IOT Cluster3
(SGSN 3, MSC3)
Release 2.1
IOT Cluster3
(SGSN 3, MSC3)
Release 2.2
IOT Cluster3
(SGSN 3, MSC3)
Release 2.0
IOT Cluster3
(SGSN 4, MSC3)
Release 2.1
IOT Cluster3
(SGSN 4, MSC3)
Release 2.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.1
IOT Cluster3
(SGSN 3, MSC3)
Release 2.2
IOT Cluster3
(SGSN 3, MSC3)
Release 2.1
IOT Cluster3
(SGSN 4, MSC3)
Release 2.3
IOT Cluster3
(SGSN 4, MSC3)
Release 2.2
IOT Cluster3
(SGSN 3, MSC3)
Release 2.13
Serial:110945000
2
Software version:
BSR-02.04.50.42
IOT
Cluster3
Hardware
version:
(SGSN
3, MSC3)
DNI v2.5
EE
Release
2.12
Power: 250mW
Femto 705
IOT Cluster3
(SGSN 3, MSC3)
Release 2.14
IOT Cluster3
(SGSN 3, MSC3)
Release 2.3
99%
8/30/2011
99%
8/24/2011
99%
7/28/2011
0.5%
8/30/2011
0.6%
7/28/2011
<1%
9/19/2011
99%
9/1/2011
99%
9/28/2011
60k UL
8/18/2011
120kUL
360kUL
60kDL
1176kb/s
9/13/2011
120kDL
3364kb/s
360kDL or
V2 5040kb/s
>3..5
8/12/2011
>3..5
8/14/2011
>3..2
8/8/2011
200ms
9/28/2011
<3 mins
9/21/2011
64/64 32
Bytes
160ms
64/64 500
64/hs
Bytes 32
bytes
280ms90ms
64/hs,
500
128/128
32
bytes
Bytes
hsupa
10ms
150ms
160ms128/1
TTI 32 bytes
28 500
68ms hsupa
Bytes
10ms TTI
240ms
<1.5
500 bytes
384/384 32
seconds
80ms
Bytes
(BCR2.4.1)
130ms
hsupa Ping
384/384 32
<1.5
500 Bytes is
Bytes
seconds
restricted to
150ms
180ms in
BCR2.4.0
<2 seconds
hsupa 2ms
TTI 32 bytes
60ms hsupa
2ms TTI 500
bytes 72ms
7/28/2011
9/13/2011
8/8/2011
9/23/2011
10/4/2011
10/4/2011
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
Serial:
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.11
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.15
IOT Cluster3
(SGSN 3, MSC3)
Release 2.15
IOT Cluster1
(SGSN 3, MSC3)
Release 2.0
IOT Cluster1
(SGSN 3, MSC3)
Release 2.4
IOT Cluster3
(SGSN 3, MSC3)
Release 2.11
IOT Cluster3
(SGSN 3, MSC3)
Release 2.20
IOT Cluster3
(SGSN 3, MSC3)
Release 2.21
IOT Cluster3
(SGSN 3, MSC3)
Release 2.19
IOT Cluster3
(SGSN 3, MSC3)
Release 2.15
IOT Cluster2
(SGSN 3, MSC3)
Release 3.0
IOT Cluster3
(SGSN 3, MSC3)
Release 2.14
IOT Cluster3
(SGSN 3, MSC3)
Release 2.15
IOT Cluster3
(SGSN 3, MSC3)
Release 2.9
IOT Cluster3
(SGSN 3, MSC3)
Release 2.10
IOT Cluster3
(SGSN 3, MSC3)
Release 2.11
99%
9/2/2011
<1s
9/21/2011
<1s
9/21/2011
<4s
9/29/2011
98%
8/24/2011
<30mins
9/27/2011
<1min
9/19/2011
<3mins
10/6/2011
Serial:
Serial:
Serial:
Serial:
Serial:
IOT Cluster3
Software version: BSR-03.00.8_p (SGSN 3, MSC3)
Release 2.10
Serial:
Serial:
Serial:
Marked Overal
Development
Execution
Result
Developed
Untested
Developed 10 Developed
iteration
Partially
tested
Tested
In progress
Blocked
Not Possible
Not Planned
Pass/Fail List
Fail
Options
Pass
Not Planned
Remaining inProgess
NotPossible
Fail
Pass
Not planned
NotPossible
InProgress
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
0
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
0
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
0
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
0
61
10
18
89
Pass
Pass
Pass
Pass
Pass
Pass
Pass

BCR 3.0 Kpi

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BCR 3.0 Kpi

Transféré par

Droits d'auteur :

Formats disponibles

This spreadsheet presents the results form the BCR3.

0 KPI AT&T subset

There are 3 main worksheets:

BCR 3.0 KPI Ex

Developed 10 iteration tested

esults/KPI's are completed and available

s these are not required for AT&T

From BSR Femto to 3G Macro Network Intra

Requirement 118617 Number

From BSR Femto to 3G Macro Network Inter

Macro to Femto HO success rate Handover

From BSR Femto to 2G Macro Network

Macro to Femto mean interruption time during

Femto to Macro HO mean interruption time

Voice Speech Quality - AMR 12.2 kbps Femto

Voice Speech Quality - AMR 12.2 kbps Femto

CS Data Call Set up Time (UMTS signaling only)

PS Drop Call Rate

R99 PS DL User Throughput

R99 PS UL User Throughput

Two Simultaneously HSPDA User Throughput

Four Simultaneous Voice calls

SSCP setup success rate (without support of new PM

HSUPA RB setup success rate

Macro 2G to Femto network handover success rate

Requirement: FTS-77715, FTS-83234, FTSbetween

Test case Developed in iTest Validation details

Mobility - Cell Reselection

Developed 10 iteration tested

Test case has been run

Mobility - Femto To 3G - Inter

Developed 10 iteration tested

Test case has been run

Mobility - Femto To 3G - Inter

Developed Partially Tested

Mobility - Inter RAT

Developed Partially Tested

Mobility - Femto To 3G - Intra

Developed Partially Tested

Mobility - Femto To 3G - Inter

Developed Partially Tested

Developed 10 iteration tested

Test case has been run

Developed 10 iteration tested

Test case has been run

Developed 10 iteration tested

Test case has been run

Mobility - Femto To Femto

Developed Partially Tested

PS Data HSDPA & R99

Developed 10 iteration tested

Test case has been run

Developed 10 iteration tested

Test case has been run

Developed 10 iteration tested

Test case has been run

Developed 10 iteration tested

Test case has been run

UE1: 3.2 Mbps

Developed 10 iteration tested

Test case has been run

Developed Partially Tested

Developed 10 iteration tested