The Drivetest Data Validation Rules - Each raw shows the rules and the specific filters to be applied fo
Drivetest type (see the comments in the header cells for addtl. details) ---> to be used in the XPLORE U
Loaded (and UL/DL Loading Conditions
yes Valid Driveroute Samples
Minimum # of sites to
Entire Driveroute
DT UE Location
Milestone 1
Milestone 2
Milestone 3
test/cluster
Completed
Test Type
Validation KPI Collected
Test ID
(Mandatory for Validation Decision)
Test Case
->see the "Validation KPI Tab for
details)
yes
yes
yes
yes
outdoor
Unloaded?)
mt1
mobile tests
Voice Calls (90 n/a ~CSV Access Failure Ratio
seconds) UE to PSTN ~CSV Call Setup Time
~CSV Drop Ratio
~Cell Capacity
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt2
mobile tests
Voice Call Indefinite n/a ~CSV Quality (BLER)
UE to PSTN ~Voice MOS
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt3
mobile tests
FTP DL 2 MB file using n/a ~PSD Access Failure Rate
any of the following PS ~PSD Drop Rate
RB (PS DL/UL) PS ~PSD Call Setup Time
384/64, PS 128/64, PS ~*Soft/Softer HO Failure Rate
64/64 ~*Soft/Softer HO Overhead
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt4
mobile tests
FTP DL 10 MB file n/a ~PSD Average DL Throughput
using any of the ~*Soft/Softer HO Failure Rate
following PS RB (PS ~*Soft/Softer HO Overhead
DL/UL) PS 384/64, PS
128/64, PS 64/64
[Please 2 MB No
FTP UL clarify:file using
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt5
mobile tests
n/a ~PSD Average UL Throughput
any of the following PS ~*Soft/Softer HO Failure Rate
RB (PS DL/UL) PS ~*Soft/Softer HO Overhead
384/64, PS 128/64, PS
64/64
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt6
mobile tests
HSDPA Call 5 code n/a ~PSD HSDPA Access Failure
(and 15 code when Rate
available) ~PSD HSDPA Drop Rate
~PSD HSDPA Peak and Average
Throughput
~PSD HSDPA Call Setup Time
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt7
mobile tests
Voice Call (90 n/a ~CSV Call Setup Time (3G
seconds) UE to 3G to 3G)
~*Soft/Softer HO Failure
Rate
~*Soft/Softer HO Ratio
~CSV Access Failure Overhead
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt8
mobile tests
Voice Calls (90 n/a
seconds) with other ~CSV Call Setup Time
than 12.2 kbit/s codec. ~CSV Drop Ratio
~Cell Capacity
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
yes
yes
yes
outdoor
Unloaded?)
Loaded (and
mt9
mobile tests
HSUPA n/a ~PSD HSUPA Throughput
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
yes
r?
stationary
st1
n/a
n/a
Unloaded?)
outdoor/indoo outdoor/indoo outdoor/indoo outdoor/indoo outdoor/indoo outdoor/indoo outdoor/indoo
Loaded (and
tests
Voice Calls (90 >=10 ~CSV Access Failure Ratio
seconds) UE to PSTN % ~CSV Call Setup Time
(=#of ~CSV Drop Ratio
sites/c ~Cell Capacity
luster) ~*Soft/Softer HO Failure Rate
/10) ~*Soft/Softer HO Overhead
yes
yes
yes
stationary
r?
st2
n/a
n/a
Unloaded?)
Loaded (and
tests
FTP DL 2 MB file using >=10 ~PSD Access Failure Rate
any of the following PS % ~PSD Drop Rate
RB (PS DL/UL) PS (=#of ~PSD Call Setup Time
384/64, PS 128/64, PS sites/c ~*Soft/Softer HO Failure Rate
64/64 luster) ~*Soft/Softer HO Overhead
/10)
yes
yes
yes
stationary
r?
st4
n/a
n/a
Unloaded?)
Loaded (and
tests
FTP UL 2 MB file using >=10 ~PSD Average UL Throughput
any of the following PS % ~*Soft/Softer HO Failure Rate
RB (PS DL/UL) PS (=#of ~*Soft/Softer HO Overhead
384/64, PS 128/64, PS sites/c
64/64 luster)
/10)
yes
yes
yes
r?
st5
n/a
n/a
stationary
Unloaded?)
Loaded (and
tests
Ping Test of 32 byte >=10 ~PSD Latency
packets using DCH % ~*Soft/Softer HO Failure Rate
channels (=#of ~*Soft/Softer HO Overhead
sites/c
luster)
/10)
yes
yes
yes
stationary
r?
st6
n/a
n/a
Unloaded?)
Loaded (and
tests
HSDPA Call 5 code >=10 ~PSD HSDPA Access Failure
(and 15 code when % Rate
available) (=#of ~PSD HSDPA Drop Rate
sites/c ~PSD HSDPA Peak and Average
luster) Throughput
/10) ~CSV Access Call Setup Time
~PSD HSDPA Failure Ratio
yes
yes
yes
stationary
r?
st7
n/a
n/a
Unloaded?)
Loaded (and
tests
Voice Calls (90 >=10
seconds) with other % ~CSV Call Setup Time
than 12.2 kbit/s codec. (=#of ~CSV Drop Ratio
sites/c ~*Soft/Softer HO Failure Rate
luster) ~*Soft/Softer HO Overhead
/10)
yes
yes
yes
r?
st8
n/a
n/a
stationary
Unloaded?)
Loaded (and
tests
HSUPA >=10 ~PSD HSUPA Throughput
% ~*Soft/Softer HO Failure Rate
(=#of ~*Soft/Softer HO Overhead
sites/c
luster)
/10)
yes
yes
no
outdoor
n/a
n/a
?
mobile tests
Video Calls (90 ~CSD Access Failure Ratio
Seconds) ~CSD Call Setup Time
~CSD Drop Ratio
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
no
outdoor
n/a
n/a
?
mobile tests
Video Call Indefinite ~CSV Quality (BLER)
~Video MOS
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
no
mobile tests
Voice IRAT KPI ~Voice IRAT Failure Rate
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
yes
yes
no
mobile tests
Packet IRAT KPI ~PSD IRAT Failure Rate
~PSD Packet Interruption Time
~*Soft/Softer HO Failure Rate
~*Soft/Softer HO Overhead
s and the specific filters to be applied for the collected Cluster Acceptance drive test files depending of the
etails) ---> to be used in the XPLORE UMTS Cluster Validation Engine
# of locations req. for the
(Archive-type files used)
Time interval between
Call Terminated by
/Session Duration
Connection Type
FTP Volume Size
Calls / Sessions
Call Destination
Static PING test
Call Initiated by
FTP Direction
Call Duration
Voice Codec
Call Source
PING Test
KPI Collected
"A Party"
"B Party"
PING test
(to be collected/reported only)
->see the "Validation KPI Tab for
details)
PSTN
UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner?
Test Vehicle Test Vehicle Test Vehicle Test Vehicle Test Vehicle Test Vehicle Test Vehicle Test Vehicle Test Vehicle
*Scanner RSCP Measurements 90 A A 15 CSV any(?) n/a n/a n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest seconds/call seconds
route
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest route
PSTN
*Scanner RSCP Measurements indefinite (till A Cal 30 CSV any(?) n/a n/a n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest Call Drop) l seconds
route Dro
*Scanner Ec/Io mesurements (Vs. p
Lat/Lon) along the Drivetest route
Server
Net/FTP
*Scanner RSCP Measurements n/a A A manual PSD n/a 2MB DL n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest
route
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest route
~PSD Average DL Throughput
Server
Net/FTP
*Scanner RSCP Measurements n/a A A manual PSD n/a 10MB DL n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest
route
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest route
~PSD Access Failure Rate
Server
Net/FTP
*Scanner RSCP Measurements n/a A A manual PSD n/a 2MB UL n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest
route
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest route
~PSD Access Failure Rate
Server
Net/FTP
*Scanner RSCP Measurements n/a A A manual HSDPA n/a 10MB DL n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest
route
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest route
3G Mobile
*Scanner RSCP 90 A A 15 CSV any(?) n/a n/a n/a n/a n/a
Measurements (Vs. seconds/call seconds
Lat/Lon) along the Drivetest
route
*Scanner Ec/Io
PSTN
*Scanner RSCP Measurements ? A A ? CSV AMR12.2k
route bps
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest route
Server
Net/FTP
*Scanner RSCP Measurements n/a A A manual HSUPA n/a 10MB UL n/a n/a n/a
(Vs. Lat/Lon) along the Drivetest
route
*Scanner Ec/Io mesurements (Vs.
Lat/Lon) along the Drivetest
route~PSD HSUPA Access Failure
PSTN
UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner? UE+Scanner?
90 A A 15 CSV any(?) n/a n/a n/a n/a n/a
seconds/call seconds
Server
Net/FTP
~PSD Average DL Throughput n/a A A manual PSD n/a 2MB DL n/a n/a n/a
Server
Net/FTP
~PSD Access Failure Rate n/a A A manual PSD n/a 2MB UL n/a n/a n/a
~PSD Drop Rate
~PSD Call Setup Time
Server
Net/FTP
n/a A A manual PSD n/a n/a n/a yes 10 100
0PI
NGS
[32B
]/sec
tor
Server
Net/FTP
n/a A A manual HSDPA n/a 10MB DL n/a n/a n/a
PSTN
~Cell Capacity ? A A ? CSV AMR12.2k
bps
Server
Net/FTP
~PSD HSUPA Access Failure n/a A A manual HSUPA n/a 10MB UL n/a n/a n/a
Rate
~PSD HSUPA Drop Rate
~PSD HSUPA Call Setup Time
3G Mobile
90 A A 15 CSD n/a n/a n/a n/a n/a n/a
seconds/call seconds
3G Mobile
indefinite (till A Cal 30 CSD n/a n/a n/a n/a n/a n/a
Call Drop) l seconds
Dro
p
~PSD Packet User Interruption
Time
ending of the
Minimum stated number of
Minimum stated number of
Attempts/Sector (for static
collected) data/sector (for
Minimum # of Call Setup
Minimum # of Call Setup
collected) data/cluster
hours worth of (valid
hours worth of (valid
samples/drive route
Minimum valid DT
Minimum valid DT
Attempts/Cluster
samples/sector
tests only)
n/a 350 n/a n/a n/a 10%
sampl
es
more
than
12 n/a n/a n/a n/a the #
10%
sampl
es
more
than
n/a 350 n/a n/a n/a the #
10%
sampl
es
more
than
12 n/a n/a n/a n/a the #
10%
sampl
es
more
than
12 n/a n/a n/a n/a the #
10%
sampl
es
more
than
12 n/a n/a n/a n/a the #
10%
sampl
es
more
than
n/a 350 n/a n/a n/a the #
10%
sampl
es
more
than
n/a 350 n/a n/a n/a the #
10%
sampl
es
more
than
12 n/a n/a n/a n/a the #
10%
sampl
es
more
than
the #
n/a n/a n/a 60 n/a 10%
sampl
es
more
than
n/a n/a n/a 60 n/a the #
10%
sampl
es
more
than
n/a n/a n/a 60 n/a the #
10%
sampl
es
more
than
n/a n/a n/a n/a n/a the #
10%
sampl
es
more
than
n/a n/a 2 n/a n/a the #
10%
sampl
es
more
than
n/a n/a n/a 60 n/a the #
10%
sampl
es
more
than
n/a n/a 2 n/a n/a the #
10%
sampl
es
more
than
n/a n/a n/a n/a n/a the #
?
n/a n/a n/a n/a n/a ?
Description
Mobile-to-PSTN voice call
Originating side located in the vehicleA Party calls B Party and call held for 90 seconds.
A Party Terminates.Time between calls = 15 seconds
Mobile- to-PSTN voice call
Originating-side located in the vehicleA Party calls B Party and call held indefinitely.
If call drops, re-establish call immediately within 30 seconds.
Mobile-in-Car in idle state, requests PDP context activation, connect to FTP server and initiate FTP DL
of 2 MB file using allocated radio bearer.
Purpose is to use whatever radio bearer allocated, and to try and achieve a mix of data radio bearers
between 384,128, and 64 in DL.
At end of DL, wait some time (depends on parameters for inactivity) for DCH to be released, then
deactivate thein idlecontextrequests PDP context activation, connect to FTP server and initiate FTP DL
Mobile-in-Car PDP state, activation. Repeat the cycle.
of 10 MB file using allocated radio bearer.
Purpose is to use whatever radio bearer allocated and to try and achieve a mix of data radio bearers
between 384,128, and 64 in DL.
At end of DL, wait some time (depends of parameters for inactivity) for DCH to be released, then
Mobile-in-Car in idlecontextrequests PDP context activation, connect to FTP server and initiate FTP UL
deactivate the PDP state, activation. Repeat the cycle.
of 2 MB file. At end of UL, wait 15 seconds for DCH to be released and PDP context is deactivated.
Repeat Cycle.
HSDPA tests will be done with a single UE doing HSDPA call in the Cell under test with a 384 Kbps
associated DCH on the UL (capable of downgrading to 64 Kbps)
FTP DL of minimum 10 MB zipped file.
mobile-to-3G mobile call
Originating side located in the vehicle, terminating side located in office.
A party calls B party and call held for 90 seconds.
A Party Terminates
Time between calls = 15 seconds
Mobile to PSTN using AMR rate other than 12.2kbit/s
NB That this test is only applicable when rates other than 12.2kbit.s are supported in Ericsson release.
Details of test to be mutually defined.
HSUPA tests will be done with a single UE doing HSUPA call in the Cell under test .
FTP UL of minimum 10 MB zipped file.
NB That this test is only applicable when HSUPA is supported in Ericsson release.
Details of test to be mutually defined.
Mobile-to-PSTN voice call
Originating side located in the vehicleA party calls B party and call held for 90 seconds.
A Party Terminates.Time between calls = 15 seconds
The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be
done for everyin idle state, requests PDP context activation, connect to FTP server and initiate FTP the
Mobile-in-Car sector of Node chosen. The test locations shall either be indoor locations, subject to DL
of 2 MB file using allocated radio bearer.
Purpose is to use whatever radio bearer allocated, and to try and achieve a mix of data radio bearers
between 384,128, and 64 in DL.
At end of DL, wait some time (depends on parameters for inactivity) for DCH to be released, then
deactivate the PDP state, activation. Repeat the cycle.
Mobile-in-Car in idlecontextrequests PDP context activation, connect to FTP server and initiate FTP UL
of 2 MB file. At end of UL, wait 15 seconds for DCH to be released and PDP context is deactivated.
Repeat Cycle.
The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be
done for every sector of Node chosen. The test locationslarge ping tobe indoor locations, subject to the
Mobile is Idle and requests PDP context activation, then shall either force DCH channel pings specific
IP address with 32 byte packet, set 1000 pings, repeat cycle.
The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be
done for every sector of Node chosen. The test locations shall either be indoor locations, subject to the
indoor coverage be done with a single UE Section 5.3 or shall the Cell under test to a specified
HSDPA tests willrequirements contained in doing HSDPA call inbe outdoor locationswithbe 384 Kbps by
associated DCH on the UL (capable of downgrading to 64 Kbps)
FTP DL of minimum 10 MB zipped file.
The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be
done for every sector of Node chosen. than test locations shall either be indoor locations, subject to the
Mobile to PSTN using AMR rate other The 12.2kbit/s
NB That this test is only applicable when rates other than 12.2kbit.s are supported in Ericsson release.
Details of test to be mutually defined.
The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be
HSUPA tests will be done withchosen. The doing HSUPA shallin the Cell indoor test .
done for every sector of Node a single UE test locations call either be under locations, subject to the
FTP UL of minimum 10 MB zipped file.
NB That this test is only applicable when HSUPA is supported in Ericsson release.
Details of test to be mutually defined.
The Stationary Tests are to be done for ten-percent (10%) of all Sites within the Cluster, and are to be
3G-to-3G video call
Originating-side located in the vehicle, terminating-side located in office.
A Party calls B Party and call held for 90 seconds
A Party Terminates
Time between calls = 15 seconds
3G-to-3G Video call
Originating-side located in the vehicle, terminating-side located in office.
A Party calls B Party and call held indefinitely
if call drops re-establish call immediately within 30 seconds
Voice inter-system handovers and Cell re-selections to be obtained on IRAT-Specific Drive Route
Packet inter-system handovers (Cell change orders) and Cell re-selections to be obtained on IRAT-
specific Drive Route
Report - Cluster Drivetest
Report - Mapping (the In-
Building Walktests
Results Mapping
Report - Details
mapping)
*Show Cluster Driveroute *for InBuilding Tests Only: Show the • all raw results ,measurements and
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be
*Show Cluster Driveroute Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the • all application of allowable
afterraw results ,measurements and
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where Cluster Driveroute
*Show the serv. is expected to be *for InBuilding Tests(Vs. floor plan)
Ec/Io mesurements Only: Show the after application of allowable
• all raw results ,measurements and
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be
*Show Cluster Driveroute Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the afterraw results ,measurements and
• all application of allowable
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
*Show the serv. is expected to be
where Cluster Driveroute *for InBuilding Tests(Vs. floor plan)
Ec/Io mesurements Only: Show the after application of allowable
• all raw results ,measurements and
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be
*Show Cluster Driveroute Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the afterraw results ,measurements and
• all application of allowable
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be
*Show Cluster Driveroute Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the • all application of allowable
afterraw results ,measurements and
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be
*Show Cluster Driveroute Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the afterraw results ,measurements and
• all application of allowable
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be
*Show Cluster Driveroute Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the • all application of allowable
afterraw results ,measurements and
*Show Failure Events (Lat/Lon, Scanner RSCP measurements (Vs. KPI achieved before application of
Explain) floor plan) along the in-building walk- allowable exemptions,
*Show the Voice Coverage Map test route • all processed results
(show the "Service Area"=areas *for InBuilding Tests Only: Scanner ,measurements and KPI achieved
where the serv. is expected to be Ec/Io mesurements (Vs. floor plan) after application of allowable
n/a *for InBuilding Tests Only: Show the • all raw results ,measurements and
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
n/a Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the • all application of allowable
afterraw results ,measurements and
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
n/a *for InBuilding Tests(Vs. floor plan)
Ec/Io mesurements Only: Show the after application of allowable
• all raw results ,measurements and
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
n/a Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the afterraw results ,measurements and
• all application of allowable
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
n/a *for InBuilding Tests(Vs. floor plan)
Ec/Io mesurements Only: Show the after application of allowable
• all raw results ,measurements and
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
n/a Ec/Io mesurements (Vs. floor plan)
*for InBuilding Tests Only: Show the afterraw results ,measurements and
• all application of allowable
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
n/a *for InBuilding Tests(Vs. floor plan)
Ec/Io mesurements Only: Show the after application of allowable
• all raw results ,measurements and
Scanner RSCP measurements (Vs. KPI achieved before application of
floor plan) along the in-building walk- allowable exemptions,
test route • all processed results
*for InBuilding Tests Only: Scanner ,measurements and KPI achieved
Ec/Io mesurements (Vs. floor plan) after application of allowable
UMTS KPI, Thresholds and the Imput Data Sources---> used for Milestones 1 - 3
Milestone 1 Milestone 1 KPI Parameter
Mandatory KPI Report Only (per Annex E Table from "U16 UMTS
("Cl. Acceptance KPI System Acceptance Procedures
Decision KPI"): ("FYI KPI"): v7.12.doc")
yes ~CSV Access Failure Ratio
yes ~CSV Drop Ratio
yes ~CSV Quality (BLER)
yes ~CSV Quality (BLER)
yes yes ~Cell Capacity
yes ~Soft/Softer Handover Overhead (cluster
yes ~CSV Call Setup Time (Mobile to PSTN)
yes ~CSV Call Setup Time (Mobile to Mobile)
(not mentioned here)
(not mentioned here)
(not mentioned here)
(not mentioned here)
yes ~CSV Call Setup Time
yes yes ~PSD Access Failure Rate
yes yes ~PSD Drop Rate
yes ~PSD Latency
yes ~PSD Average DL Throughput
yes ~PSD Average DL Throughput
yes ~PSD Average UL Throughput
yes ~PSD Average UL Throughput
yes yes ~PSD Call Setup Time
(not mentioned here)
(not mentioned here)
(not mentioned here)
yes ~PSD HSDPA Access Failure Rate
yes ~PSD HSDPA Drop Rate
(not mentioned here)
(not mentioned here)
(not mentioned here)
yes ~PSD HSDPA Average Throughput
yes ~PSD HSDPA Average Throughput
yes ~PSD HSUPA Throughput
yes ~PSD HSUPA Throughput
yes ~PSD HSDPA Call Setup Time
(not mentioned here)
(not mentioned here)
(not mentioned here)
yes ~PSD HSUPA Access Failure Rate
yes ~PSD HSUPA Drop Rate
yes ~PSD HSUPA Call Setup Time
yes *Scanner RSCP Measurements (Vs.
yes *Scanner Ec/Io mesurements (Vs. Lat/Lon)
yes *for InBuilding Tests Only: Show the
yes *for InBuilding Tests Only: Scanner Ec/Io
yes ~Voice MOS
yes ~PSD HSDPA Peak Throughput
yes ~Soft/Softer HO Failure Rate (cluster level)
yes ~Video MOS
yes ~Voice IRAT Failure Rate
yes ~PSD IRAT Failure Rate
yes ~PSD Packet Interruption Time
yes ~PSD Packet User Interruption Time
es---> used for Milestones 1 - 3
KPI Parameter Pre-Launch KPI Launch KPI Post Launch KPI
(from "U12 UMTS Network KPI v6.10.doc") Thresholds Thresholds Thresholds
(Milestone 1) (Milestone 2) (Milestone 3)
-U12- -U12- -U12-
CSV Access Failure Rate ≤ 2.0 % ≤ 2.0 % ≤ 2.0 % >
CSV Drop Rate ≤ 2.0 % ≤ 1.5 (2) % ≤ 1.5 (2) % >
CSV Quality (DL) 95th percentile of 95th percentile of 95th percentile of >
CSV Quality (UL) 95th percentile of 95th percentile of 95th percentile of >
Cell Capacity ≥ 40 UE AMR ≥ 40 UE AMR Measure and >
Soft/Softer Handover Overhead ≤ 1.6 ≤ 1.6 ≤ 1.7 >
CSV IRAT Failure Rate N.A. ≤ 5.0 % ≤ 5.0 % >
*Voice Call Setup time (Mobile to PSTN) 95th percentile ≤ 6 95th percentile ≤ 6 95th percentile ≤ 6 >
*Voice Call Setup time (Mobile to Mobile) 95th percentile ≤ 95th percentile ≤ 95th percentile ≤ >
CSD Access Failure Rate ≤ 3.0 % ≤ 2.0 % ≤ 2.0 % >
CSD Drop Rate ≤ 2.5 % ≤ 2.5 % ≤ 3.0 % >
CSD Quality (DL) 95th percentile of 95th percentile of 95th percentile of >
CSD Quality (UL) 95th percentile of 95th percentile of 95th percentile of >
*CSD Call Setup time N.A. 95th percentile ≤ 9 N.A. >
PSD Access Failure Rate ≤ 2.0 % ≤ 2.0 % ≤ 2.0 % >
PSD Drop Rate ≤ 2.5 % ≤ 2.0 % ≤ 2.0 % >
*PSD Latency (any R99 RAB) N.A. 95th percentile ≤ N.A. >
PSD R99 Average DL throughput (kbps) ≥ 240 ≥ 240 ≥ 150 (Counter), ≥ >
PSD R99 Average DL throughput (kbps) ≥ 210 ≥ 210 ≥ 150 (Counter), ≥ >
PSD R99 Average UL throughput (kbps) ≥ 200 ≥ 200 ≥ 150 (Counter), ≥ >
PSD R99 Average UL throughput (kbps) ≥ 180 ≥ 180 ≥ 150 (Counter), ≥ >
*PSD Call Setup time N.A. 95th percentile N.A. >
PSD IRAT Failure Rate N.A. ≤ 5.0 % ≤ 5.0 % >
PSD IRAT Interruption time N.A. 95th percentile , ≤ N.A. >
PSD IRAT User Data Interruption time N.A. Measure and N.A. >
HSDPA Access Failure Rate ≤ 2.0 % ≤ 2.0 % ≤ 2.0 % >
HSDPA Drop Rate ≤ 3.0 % ≤ 2.0 % ≤ 2.0 % >
*HSDPA Latency N.A. 95th percentile N.A. >
Stationary Maximum DL HSDPA Bit Rate (kbps) ≥ 1300 ≥ 1300 ≥1300 (at RLC >
Stationary Maximum DL HSDPA Bit Rate (kbps) ≥ 1100 ≥ 1100 N.A. >
HSDPA Average DL Throughput (kbps) for UE ≥ 700 ≥ 700 ≥ 700 (at off >
HSDPA Average DL Throughput (kbps) for UE ≥ 600 ≥ 600 N.A. >
HSUPA Stationary Peak throughput (kbps) for ≥ 1100 ≥ 1100 Measure and >
HSUPA Stationary Average throughput (kbps) for ≥ 500 ≥ 500 Measure and >
*HSDPA Session Activation time N.A. 95th percentile N.A. >
*Average Cell Availability KPI N.A. N.A. N.A.** >
*Average Cell Non-Maintenance Availability KPI N.A. N.A. N.A.** >
GSM Performance Degradation due to ≤ 10 % ≤ 10 % ≤ 10 % >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) >
(not mentioned here) N.A. >
(not mentioned here) N.A. >
(not mentioned here) N.A. >
(not mentioned here) N.A. >
(not mentioned here) N.A. >
KPI Parameter XPLORE Validation Module
(from "U12 UMTS Network KPI v6.10.doc") KPI Parameter Input data for the Milestone
Reference/Definition 1:
[Drivetest Data only]
CSV Access Failure Rate Access failure is the product # of RRC Connections
CSV Drop Rate Circuit Switched Voice Drop # of Call_Dropped
CSV Quality (DL) Voice quality shall be # of samples below BLER
CSV Quality (UL) Voice quality shall be # of samples below BLER
Cell Capacity Average number of Voice CellTrafficPower
Soft/Softer Handover Overhead Soft/Softer Handover AS (list of used AS, 1, 2….M)
CSV IRAT Failure Rate CSV Inter-Radio Access # of HO UTRAN Failures
*Voice Call Setup time (Mobile to PSTN) Voice call set up time CC_Alerting(MOC)
*Voice Call Setup time (Mobile to Mobile) Voice call set up time CC_Alerting(MOC)
CSD Access Failure Rate Access failure is the product # of RRC Connections
CSD Drop Rate # of Call_Dropped
CSD Quality (DL) CSD Data quality shall be # of samples below BLER
CSD Quality (UL) CSD Data quality shall be # of samples below BLER
*CSD Call Setup time Circuit Switched Data call set CC_Alerting(MOC)
PSD Access Failure Rate TSwitch Data access failure # of Activate PDP Context
PSD Drop Rate Packet session is considered # of FTP Downloads Success
*PSD Latency (any R99 RAB) Round trip time for a 32 Bytes RTT (Round Trip Time)
PSD R99 Average DL throughput (kbps) DL Packet Switched Data DL User Data Transferred
PSD R99 Average DL throughput (kbps) DL Packet Switched Data DL User Data Transferred
PSD R99 Average UL throughput (kbps) UL Packet Switched Data UL User Data Transferred
PSD R99 Average UL throughput (kbps) UL Packet Switched Data UL User Data Transferred
*PSD Call Setup time PSD call setup time indicates PDP Context Activation
PSD IRAT Failure Rate Inter-Radio Access #CellChangeOrderFromUTR
PSD IRAT Interruption time Duration of interruption to TimeRAUpdateComplete_UE
PSD IRAT User Data Interruption time Duration in seconds to TimeFirstPacketDataReceive
HSDPA Access Failure Rate Table 41 # of Activate PDP Context
HSDPA Drop Rate HSDPA session is considered # of HS-
*HSDPA Latency Round trip time for a 32 Bytes
Stationary Maximum DL HSDPA Bit Rate (kbps) Highest RLC blocks Peak DL User data RLC
Stationary Maximum DL HSDPA Bit Rate (kbps) Highest RLC blocks Peak DL User data RLC
HSDPA Average DL Throughput (kbps) for UE Total number of RLC blocks Sum of all DL User data
HSDPA Average DL Throughput (kbps) for UE Total number of RLC blocks Sum of all DL User data
HSUPA Stationary Peak throughput (kbps) for Highest RLC blocks Peak UL User data RLC
HSUPA Stationary Average throughput (kbps) for Total number of RLC blocks Sum of all UL User data
*HSDPA Session Activation time Table 51
*Average Cell Availability KPI Table 53
*Average Cell Non-Maintenance Availability KPI Table 55
GSM Performance Degradation due to The deployment of the UMTS CSV MOU (from GSM CSV
?
Data Input Details
Use DT
find (more details in "Annex
Session files:
KPI MS1 Tab.")
Measurement Condition: UMTS CSV
Measurement Condition: UMTS CSV
This KPI shall be measured at UMTS CSV
UL BLER is collected and UMTS CSV
CSV Cell Capacity shall be UMTS CSV
AS = Active Set size UMTS CSV
# of HO UTRAN Failures UMTS CSV
CC_Alerting(MOC) = UMTS CSV
CC_Alerting(MOC) = UMTS CSV
Drivetest output data from UMTS CSD
Drivetest output data from UMTS CSD
This KPI shall be measured at UMTS CSD
UL BLER is collected and UMTS CSD
CC_Alerting(MOC) = UMTS CSD
Access Failure Rate shall be UMTS PSD
PSD drop Rate shall be UMTS PSD
Latency will be measured with UMTS PSD
DL User Data Transferred UMTS PSD
DL User Data Transferred UMTS PSD
UL User Data Transferred UMTS PSD
UL User Data Transferred UMTS PSD
UMTS PSD
PSD IRAT HHO failure KPI UMTS PSD
UMTS PSD
UMTS PSD
In case of multiple RRC UMTS HSDPA
# of HS- UMTS HSDPA
UMTS HSDPA
Only the peak throughput UMTS HSDPA
Only the peak throughput UMTS HSDPA
AM_RLC_PDU_Data(kb) UMTS HSDPA
AM_RLC_PDU_Data(kb) UMTS HSDPA
Only the peak throughput HSUPA Session
AM_RLC_PDU_Data(kb) UMTS HSUPA
UMTS HSUPA
?
?
Inv estigated variations on: GSM CSV
Imput Sources for The Tool Cluster Validation Module
Parameter Source Layer (in work) Applied Operation
# of RRC Connections Requests L3 Count All
# of Connect CC_Alerting /Connect L3 Count All
# of Call_Dropped L3, Event Count All
# of Call Setup Success L3, Event Count All
# of samples below BLER Target L3 Count All
# of all BLER DL Samples L3 Count All
CellTrafficPower L3 Find BSS setting
AvgRL PerCall L3 Calculate the Average Values
AvgPowerPerRL L3 Calculate the Average Value
AS - Active Set (list of used AS, 1, 2….M) L3 Find BSS setting
M = Maximum Active Set size used L3 Find BSS setting
Duration(AS) L3 Count All
CC_Alerting(MOC) L3 Collect the Timestamp
RRC Connection Request(MOC) L3 Collect the Timestamp
# of BLER samples below BLER Theshold L3 Count All
# of all BLER DL Samples L3 Count All
# of Activate PDP Context Accept L3 Count All
# of FTP Downloads Success App Layer Count All
UL/DL User Data Transferred [kb] (Appl. layer - FTP) App Layer Calculate Total
UL/DL FTP Session duration [s] (Appl. layer - FTP) App Layer Calculate Total
# of Activate PDP Context Accept Messages L3 Count All
# of RRC Connection Requests Messages L3 Count All
# of HS-DSCH_ReleaseDueToFailure ( = HS-DSCH_Drop) L3 Count All
# of HS-DSCH_AllocationSuccess L3 Count All
Peak DL User data RLC throughput [Kb] L2 Find Max Value
Total DL User data transferred [Kb] L2 Calculate Total
Total Sessions duration [s] L3 Calculate Total
Peak UL User data RLC throughput [Kb] L3 Find Max value
Total UL User data transferred [Kb] App Layer Calculate Total
Total of Sessions duration [s] L3 Calculate Total
CSV MOU (from GSM CSV drivetest files) L3 Calculate Total
Load/Update the UMTS Acceptance Campain Drivetest Data from the Tool D
DT Files Consistency Checkup and Invalid DT Files R
Cluster Level DT Data Parsing, Cell Level DT Data Parsing,
Cluster DT Files Filtering, Cell DT Files Filtering,
Invalid DT Files Removal Invalid DT Files Removal
DT Data parsing and re-combining DT Data parsing and re-combining
per Session Type per Session Type
UMTS UMTS UMTS UMTS UMTS UMTS UMTS
CSD DT PSD DT HSDPA HSUPA GSM CSD DT PSD DT HSDPA
Data Data DT Data DT Data CSV Data Data DT Data
DT Data Mining - KPI input data filtering, DT Data Mining - KPI input data filtering,
counting, buffering, etc. counting, buffering, etc.
Events Events Events Events Events Events Events Events
App. L App. L App. L App. L App. L App. L App. L App. L
L3 L3 L3 L3 L3 L3 L3 L3
L2 L2 L2 L2 L2 L2 L2 L2
L1 L1 L1 L1 L1 L1 L1 L1
KPI Computation KPI Computation
[Cluster Level] [Cell Level]
Cell Level "Milestone-1" Acceptance
Cluster "Milestone-1" Acceptance Reporting
Reporting
Cluster Pass/Fail Optional: Display the
KPI Report at Optional: Display on a map layer
Resolution (Decision) Cluster Acceptance KPI Report at cell level
cluster level the KPI/cell
Report on a map layer
~ "Cluster Pass" / "Cluster Fail" Acceptance Report ~ KPI Summary/Cell Report
~ KPI Summary/Cluster Report ~ The count of Events/Event Type/Cell Report
~ The count of Events/Event Type/Cluster Report ~ # of sample valid drivetest/scan sample points used per
~ # of sample valid drivetest/scan sample points used per cell
cell ~ Map layer: Events/Cell
~ Scanner Vs. Drivetest Coverage Statistical Report (the data used is grouped as individual layers per cell)
~ On map display of the failed Clusters
~ Map layers: Events/Cell, Scanner Ec/Io on CPICH,
Drivetest Ec/No on CPICH"
rivetest Data from the Tool DT Repository (Market Level)
ckup and Invalid DT Files Removal
l DT Data Parsing,
Custom Area DT Filtering
T Files Filtering,
(optional for future developements)
DT Files Removal
ing and re-combining DT Data parsing and re-combining
Session Type per Session Type
UMTS UMTS UMTS UMTS UMTS
HSUPA GSM CSD DT PSD DT HSDPA HSUPA GSM
DT Data CSV Data Data DT Data DT Data CSV
- KPI input data filtering, DT Data Mining - KPI input data filtering,
g, buffering, etc. counting, buffering, etc.
Events Events Events Events Events Events Events
App. L App. L App. L App. L App. L App. L App. L
L3 L3 L3 L3 L3 L3 L3
L2 L2 L2 L2 L2 L2 L2
L1 L1 L1 L1 L1 L1 L1
Computation KPI Computation
Cell Level] [Custom Level]
lestone-1" Acceptance Custom Area "Milestone-1" Acceptance
Reporting Reporting
Optional: Display on a map layer Optional: Display the
Custom KPI Report
the KPI/cell KPI/custom area
port ~ KPI Summary/Cell Report
vent Type/Cell Report ~ The count of Events/Event Type/Cell Report
etest/scan sample points used per ~ # of sample valid drivetest/scan sample points used per
cell
l ~ Map layer: Events/Cell
ed as individual layers per cell)
KPI Definitions and Formulas
"Milestone 1"
Milestone 1?
Pre-Launch
Threshold
Input data for
KPI Reference/Definition Milestone 1:
[Drivetest Data only]
CSV Access ≤ 2.0 % yes Access failure is the product of the # of RRC Connections
Failure Rate RRC Connection Failure, NAS Requests (UL L3 Messages)
Setup Failure and the RAB # of Connect CC_Alerting
Establishment Failure. RRC /Connect (DL L3 Messages)
Connection Success is counted
CSV Drop Rate ≤ 2.0 % yes Circuit Switched Voice Drop # of Call_Dropped
measures the Network’s inability to # of Call Setup Success
maintain a call. CSV Drop is
defined as the ratio of abnormal
speech disconnects, relative to all
CSV Quality (DL) 95th yes Voice quality shall be measured by # of samples below BLER
percentile BLER Target (BLER_DL ≤ 2%)
of samples # of all BLER DL Samples
≤ 2.0 %
BLER
CSV Quality (UL) 95th yes? Voice quality shall be measured by # of samples below BLER
percentile (Q: is BLER Target (BLER_UL ≤ 2%)
of samples the # of all BLER DL Samples
≤ 2.0 % UL
BLER BLER
Cell Capacity ≥ 40 UE yes Average number of Voice Calls CellTrafficPower
AMR 12.2k (AMR 12.2) that can be supported AvgRL PerCall
(provided it by cell AvgPowerPerRL
is achieved
in RF
Soft/Softer ≤ 1.6 yes Soft/Softer Handover Overhead AS (list of used AS, 1, 2….M)
Handover KPI provides an indication of how M = Maximum Active Set size
Overhead many Cells or Sectors were in the used
active set during the call on an Duration(AS)
average basis.
CSV IRAT Failure N/A no CSV Inter-Radio Access # of HO UTRAN Failures
Rate Technology Handover Failure = received by UE
Hard Handover Failure rate from # of HO UTRAN commands
UMTS and GSM System for voice sent by UE
calls. = ratio between # of HO
*Voice Call Setup 95th yes Voice call set up time indicates CC_Alerting(MOC)
time (Mobile to percentile Network response time to a user RRC Connection
PSTN) ≤6 request for a voice service. This Request(MOC)
seconds KPI is applicable only for drive test.
*Voice Call Setup 95th yes Voice call set up time indicates CC_Alerting(MOC)
time (Mobile to percentile Network response time to a user RRC Connection
Mobile) ≤9 request for a voice service. This Request(MOC)
seconds KPI is applicable only for drive test.
CSD Access ≤ 3.0 % yes Access failure is the product of the # of RRC Connections
Failure Rate RRC Connection Failure, NAS Requests (UL L3 Messages)
setup failure and the RAB # of Connect CC_Alerting
Establishment Failure. RRC /Connect (DL L3 Messages)
Connection Success is counted
CSD Drop Rate ≤ 2.5 % yes # of Call_Dropped
# of Call Setup Success
CSD Quality (DL) 95th yes CSD Data quality shall be # of samples below BLER
percentile measured by BLER Target (BLER_DL ≤ 2%)
of samples # of all BLER DL Samples
≤ 1.0 %
BLER
CSD Quality (UL) 95th yes? CSD Data quality shall be # of samples below BLER
percentile (is the measured by BLER Target (BLER_UL ≤ 2%)
of samples UL # of all BLER DL Samples
≤ 1.0 % BLER
BLER data
*CSD Call Setup N.A no Circuit Switched Data call set up CC_Alerting(MOC)
time time indicates Network response RRC Connection
time to a user request for a video Request(MOC)
service.
PSD Access ≤ 2.0 % yes TSwitch Data access failure from a # of Activate PDP Context
Failure Rate user perspective Accept
# of RRC Connections
Requests
PSD Drop Rate ≤ 2.5 % yes Packet session is considered as # of FTP Downloads Success
dropped when associated RAB has # of Call Setup Succes
been released abnormally by either
UTRAN or CN. Any drop after
RANAP: RAB Assignment
*PSD Latency (any N.A no Round trip time for a 32 Bytes ping RTT (Round Trip Time)
R99 RAB) for any R99 PS RAB
Indicates maximum delay for 95th
percentile of the distribution of
delay for all delivered SDUs during
PSD R99 Average ≥ 240 yes DL Packet Switched Data average DL User Data Transferred
DL throughput throughput using R99 RAB [kb] (FTP)
(kbps) (Unloaded) measured at application layer Session duration [s] (FTP)
(Total number of RLC blocks sent
over the observation window
PSD R99 Average ≥ 210 yes DL Packet Switched Data average DL User Data Transferred
DL throughput throughput using R99 RAB [kb] (FTP)
(kbps) (Loaded) measured at application layer Session duration [s] (FTP)
(Total number of RLC blocks sent
over the observation window
PSD R99 Average ≥ 200 yes UL Packet Switched Data average UL User Data Transferred
UL throughput throughput using R99 RAB [kb] (FTP)
(kbps) (Unloaded) measured at application layer Session duration [s] (FTP)
(Total number of RLC blocks sent
over the observation window
PSD R99 Average ≥ 180 yes UL Packet Switched Data average UL User Data Transferred
UL throughput throughput using R99 RAB [kb] (FTP)
(kbps) (Loaded) measured at application layer Session duration [s] (FTP)
(Total number of RLC blocks sent
over the observation window
*PSD Call Setup N.A no PSD call setup time indicates PDP Context Activation
time Network response time to a user accept (MOC)
request for a packet data service. RRC Connection Request
In case of multiple RRC connection (MOC)
requests the first RRC connection
PSD IRAT Failure N/A no Inter-Radio Access Technology #CellChangeOrderFromUTR
Rate (IRAT) is a hard handover failure AN Failure(PS)
rate between UMTS and GSM = #CellChangeOrderFromUTR
Hard Handover failure rate when a AN Command(PS)
PS Data call (R99) fail to handover
PSD IRAT N.A no Duration of interruption to Packet TimeRAUpdateComplete_UE
Interruption time data service during Hard Handover TimeCellChangeOrder_RNC
(is an indicator of interruption time
for the packet switch data during
Inter-Radio Access Technology
PSD IRAT User N.A no Duration in seconds to interruption TimeFirstPacketDataReceive
Data Interruption of Packet data service from User dIn2G
time perspective during IRAT Hard TimeLastPacketDataReceive
Handover from 3G to 2G dIn3G
HSDPA Access ≤ 2.0 % yes Table 41 # of Activate PDP Context
Failure Rate Accept Messages
# of RRC Connection
Requests Messages
HSDPA Drop Rate ≤ 3.0 % yes HSDPA session is considered as # of HS-
dropped when associated HS- DSCH_ReleaseDueToFailure
DSCH has been released ( = HS-DSCH_Drop)
abnormally by either UTRAN or # of HS-
CN. This test will be done with a DSCH_AllocationSuccess
*HSDPA Latency N.A no Round trip time for a 32 Bytes ping
for HSDPA NRT RAB
Stationary ≥ 1300 yes Highest RLC blocks throughput Peak DL User data RLC
Maximum DL over the observation window throughput [Kb]
HSDPA Bit Rate including re-transmission
(kbps) under no
load (UE Category
Stationary ≥ 1100 yes Highest RLC blocks throughput Peak DL User data RLC
Maximum DL over the observation window throughput [Kb]
HSDPA Bit Rate including re-transmission
(kbps) with 50%
DL loading (UE
HSDPA Average ≥ 700 yes Total number of RLC blocks sent Sum of all DL User data
DL Throughput over the observation window transferred [Kb]
(kbps) for UE including re-transmission Sum of Sessions duration [s]
category 12 under
no load
HSDPA Average ≥ 600 yes Total number of RLC blocks sent Sum of all DL User data
DL Throughput over the observation window transferred [Kb]
(kbps) for UE including re-transmission Sum of Sessions duration [s]
category 12 under
50% DL loading
HSUPA Stationary ≥ 1100 yes Highest RLC blocks throughput Peak UL User data RLC
Peak throughput over the observation window throughput [Kb]
(kbps) for UE including re-transmission
Category 3 (1.45
Mbps)
HSUPA Stationary ≥ 500 yes Total number of RLC blocks sent Sum of all UL User data
Average over the observation window transferred [Kb]
throughput (kbps) including re-transmission Sum of Sessions duration [s]
for UE Category 3
(1.45 Mbps)
*HSDPA Session N.A no Table 51
Activation time
*Average Cell N.A no Table 53
Availability KPI
*Average Cell Non- N.A no Table 55
Maintenance
Availability KPI
GSM Performance ≤ 10 % yes The deployment of the UMTS CSV MOU (from GSM CSV
Degradation due Network shall not degrade drivetest files)
to Introduction of Purchaser’s existing GSM Network # of Call_Dropped (GSM
UMTS performance. Excluding IRAT Hard CSV)
Handover Feature, both UMTS and # of Call Setup Success
Session files:
Use DT
Data Input Details
Measurement Condition:
Drivetest output data from CSV
CC _ Alerting/ Connect
ailureRate 100* 1
CSV _ Calls
CSVAccessF
RRC _ Connection quest
CSV
Calls only
Re
In the event that there are several UMTS
consecutive RRC Connection CSV _ Calls
Measurement Condition:
Drivetest output data from CSV
CallDroppe d
CSVDropRat e 100 *
CSV _ Calls
CallSetupS
Calls only
Any CSV call successfully handed UMTS uccess
CSV CSV _ Calls
over from 3G to 2G network within
This KPI shall be measured at 1%
BLER operating point set in UTRAN
for voice call.
BLER shall be available using UMTS
counters with Cell Level granularity. CSV
UL BLER is collected and
presented in the MRR-W
(Measurement Results Recording
WCDMA) feature in OSS-RC UMTS
CSV
CSV Cell Capacity shall be
calculated based on average DL
power allocated to AMR 12.2 RB for
this KPI. UMTS
CellTrafficPower = Net DL Power CSV
AS = Active Set size M
M = Maximum Active Set size as AS * Duration ( AS )
defined in RNC
Duration(AS) = Duration of the call UMTS
SoftSofter Handover AS 1
M
in Active Set size of AS (AS=1 to M)
# of HO UTRAN Failures received
CSV Duration
AS 1
( AS )
by UE and # of HO UTRAN
commands sent by UE
Drivetest output data used: # of HO UMTS
UTRAN Failures received by UE CSV
CC_Alerting(MOC) = (Timestamp
of the Call Alerting message?)
RRC Connection Request(MOC) =
(Timestamp of the Connection UMTS
Request message?) CSV
CC_Alerting(MOC) = (Timestamp
of the Call Alerting message?)
RRC Connection Request(MOC) =
(Timestamp of the Connection UMTS
Request message?) CSV
Drivetest output data from CSD
Calls only
UMTS
CSD
Drivetest output data from CSD
Calls only
UMTS
CSD
This KPI shall be measured at 1%
BLER operating point set in UTRAN
for voice call.
BLER shall be available using UMTS
counters with Cell Level granularity. CSD
UL BLER is collected and
presented in the MRR-W
(Measurement Results Recording
WCDMA) feature in OSS-RC. UMTS
Reporting period can be set to CSD
CC_Alerting(MOC) = (Timestamp
of the Call Alerting message?)
RRC Connection Request(MOC) =
(Timestamp of the Connection UMTS
Request message?) CSD
Access Failure Rate shall be
measured by data session
activation (PS) followed by
download. In case of multiple RRC UMTS
connection requests the first RRC PSD
PSD drop Rate shall be measured
after start of ftp download . PSD call
is considered as dropped when ftp
session is manually/abnormally UMTS
disconnected without completing PSD
Latency will be measured with the
destination server for ping
connected directly to the GGSN
(i.e. the server on the same Intranet UMTS
domain as GGSN). RTT will be PSD
DL User Data Transferred [kb]
=Total ftp size download in kilo-bit
in one session
Session duration [s]=Total time UMTS
(seconds) duration to download PSD
DL User Data Transferred [kb]
=Total ftp size download in kilo-bit
in one session
Session duration [s]=Total time UMTS
(seconds) duration to download PSD
UL User Data Transferred [kb]
=Total ftp size download in kilo-bit
in one session
Session duration [s]=Total time UMTS
(seconds) duration to download PSD
UL User Data Transferred [kb]
=Total ftp size download in kilo-bit
in one session
Session duration [s]=Total time UMTS
(seconds) duration to download PSD
UMTS
PSD
PSD IRAT HHO failure KPI does
not include HHO Preparation
failure. Specific drive route shall be
identified at the UMTS RF Service UMTS
Area boundary to verify this KPI. PSD
UMTS
PSD
UMTS
PSD
In case of multiple RRC connection
requests the first RRC connection
request will be considered for KPI
calculation. UMTS
Access Failure Rate shall be HSDPA
# of HS-
DSCH_ReleaseDueToFailure ( =
HS-DSCH_Drop) = Number of HS-
DSCH allocation releases due to UMTS
radio link and other failures HSDPA
UMTS
HSDPA
Only the peak throughput value
recorded in the drivetests is
considered
AM_RLC_PDU_Data(kb) ( = user UMTS
data transferred) HSDPA
Only the peak throughput value
recorded in the drivetests is
considered
AM_RLC_PDU_Data(kb) (user data UMTS
transferred) HSDPA
AM_RLC_PDU_Data(kb) (user data
transferred)
AM_RLC_PDU_Duration (session
duration) UMTS
HSDPA
AM_RLC_PDU_Data(kb) (user data
transferred)
AM_RLC_PDU_Duration (session
duration) UMTS
HSDPA
Only the peak throughput value
recorded in the drivetests is
considered
AM_RLC_PDU_Data(kb) ( = user HSUPA
data transferred) Session
AM_RLC_PDU_Data(kb) (user data
transferred)
AM_RLC_PDU_Duration (session
duration) UMTS
HSUPA
UMTS
HSUPA
?
?
Inv estigated variations on:
- MOU/drop for Voice Calls
- Access failure rate for voice calls
- Daily (24 hour) Voice Erlang GSM
Traffic CSV
Milestone 1 Formula
(Drivetest-Only based KPI computation)
CC _ Alerting/ Connect
ailureRate 100* 1
CSV _ Calls
CSVAccessF
RRC _ Connection quest
CSV
Re
_ Calls
CallDroppe d
CSVDropRat e 100 *
CSV _ Calls
CallSetupS
CSV _ Calls
uccess
SamplesBelowBLERT arg et
CSVDLQuali 100 *
CSV _ Calls
ty
AllBLERSam
CSV _ Calls
ples
CellTraffi cPower
CSVCellCapacity
AvgPowerPe rRL * AvgRLPerCa ll
M
AS * Duration ( AS )
SoftSofter Handover AS 1
M
Duration ( AS ) From UTRAN Failure
AS 1
CS _ Calls
Handover
CSV 3G 2GHandover Failure Rate 100 *
Handover From UTRAN Command
CS
_ Calls
Voice Call setup time = CC_Alerting(MOC) – RRC Connection Request(MOC)
Voice Call setup time = CC_Alerting(MOC) – RRC Connection Request(MOC)
CC _ Alerting / Connect
CSD _ Calls
CSD Access Failure R ate 100 * 1
RRC Connection Re quest
CSD _ Calls
CallsDrop
CSD _ DropRate 100 *
CSD _ Calls
CallsSetupSuccess
CSD _ Calls
SamplesBelowBLERT arg et
DL 100 *
CSD _ Calls
CSDQuality
AllBLERSam
CSD _ Calls
ples
Activate PDP Context Accept
PSD Access Failure R ate 100 * 1
PSD _ Calls
RRC Connection Re quest
PSD _ Calls
ftpDownloa dSuccess
PSDCallDro pRate 100 * 1
ftpSe ssion
CallSetupSuccess
ftpSe ssion
UserDataTransf erred (k b)
ughput( k bps)
PSD _ Call
PSDAv gThro
SessionDuration(sec )
PSD _ Call
UserDataTransf erred (k b)
ughput( k bps)
PSD _ Call
PSDAv gThro
SessionDuration(sec )
PSD _ Call
PSD_IRATUserDataInterruptionTime =
(TimeFirstPacketDataReceivedIn2G – TimeLastPacketDataReceivedIn3G)
Activate PDP Context Accept
HSDPA Acce ssFailureRate 100 * 1 HSDPA_ Session
RRC Connection Re quest
HSDPA_ Session
HS - DSCH_Drop
HSDPA _ DropRate 100 *
HSDPA _ Call
HS DSCH _ AllocationSuccess
HSDPA _ Call
UserDataTransf erred (k b)
HSDPA_ Throughput
HSDPA_ Call
SessionDuration(sec )
HSDPA_ Call
UserDataTransf erred (k b)
HSDPA_ Throughput
HSDPA_ Call
SessionDuration(sec )
HSDPA_ Call
UserDataTransf erred (k b)
HSDPA_ Throughput
HSDPA_ Call
SessionDuration(sec )
HSDPA_ Call
UserDataTransf erred (k b)
HSDPA_ Throughput
HSDPA_ Call
SessionDuration(sec )
HSDPA_ Call
UserDataTransf erred (k b)
HSUPA _ Throughput
HSUPA _ Se ssion
SessionDuration(sec )
HSUPA _ Se ssion
UserDataTransf erred (k b)
HSUPA _ Throughput
HSUPA _ Se ssion
SessionDuration(sec )
HSUPA _ Se ssion
IE Name Range/Unit Arg *
Altitude (ft) –1312 ... 29028 – p
ft
Altitude (m) –400 ... 8848 – p
m
AS Cell Name Text 1 ... 6 u
c
AS CPICH –34 ... 0 1 ... 6 u
Ec/No dB
AS CPICH RSCP –135 ... –15 1 ... 6 u
dBm
AS No of Members 0 ... 6 – u
AS SC 0 ... 511 1 ... 6 u
AS UARFCN DL WCDMA 1900A: 1 ... 6 u
9660 ... 9940 1900B:
410 ... 689
2100:00:00
10550 ... 10850
Averaged BER (%) 0 ... 100 – n
%
Call Event Success 0 ... 100 – u
Rate
%
Compressed Mode 0, 1 – u
CW Sc No of UARFCNs 0 ... 255 – sp
cw
CW Sc RSSI –115 ... –25 1 ... 255 sp
dBm cw
CW Sc UARFCN WCDMA 1900A: 1 ... 255 sp
9660 ... 9940 1900B: cw
410 ... 689
2100:00:00
10550 ... 10850
Det Neigh Cell Name Text 1 ... 6 u
c
Det Neigh CPICH Ec/No –34 ... 0 1 ... 6 u
dB
Det Neigh CPICH RSCP –135 ... –15 1 ... 6 u
dBm
Det Neigh CPICH Tx –31 ... 50 1 ... 6 u
Power
dBm
Det Neigh No of 0 ... 6 – u
Members
Det Neigh Pathloss 30 ... 165 1 ... 6 u
dB
Det Neigh SC 0 ... 511 1 ... 6 u
Det Neigh UARFCN DL 0 ... 16383 1 ... 6 u
DPCCH ISCP DL –135 ... –15 – t
dBm
DPCCH RSCP DL –135 ... –15 – t
dBm
"Finger" elements
(general remarks)
Finger ... –34 ... 0 1 ... 48 me
Ec/No dB q
sr
Finger ... No of 0 ... 48 – me
q
sr
Finger ... RSCP –135 ... –15 1 ... 48 me
dBm q
sr
Finger ... RSSI –95 ... –30 1 ... 48 me
dBm q
sr
Finger ... SC 0 ... 511 1 ... 48 me
q
sr
Finger ... Slot 0 ... 15 1 ... 48 me
q
sr
Finger ... Slot Pos 1 ... 2560 1 ... 48 me
q
sr
Finger ... Type Text 1 ... 48 me
q
sr
Finger ... UARFCN 0 ... 16383 1 ... 48 me
q
sr
Finger ... Position SC 0 ... 511 1 ... 2560 me
q
sr
Finger ... Position Ec/No –34 ... 0 1 ... 2560 me
dB q
sr
Finger ... Position RSCP –135 ... –15 1 ... 2560 me
dBm q
sr
Finger ... Position RSSI –95 ... –30 1 ... 2560 me
dBm q
sr
Finger ... Position Slot 0 ... 15 1 ... 2560 me
q
sr
Finger ... Position Type Text 1 ... 2560 me
q
sr
Finger ... Position 0 ... 16383 1 ... 2560 me
UARFCN
q
sr
GSM Neigh ARFCN See appendix G.3 under 1 ... 32 e
"ARFCN BCCH"
m
q
ne
GSM Neigh BSIC Text 1 ... 32 e
m
q
ne
GSM Neigh No of 0 ... 32 – e
m
q
ne
GSM Neigh RxLev –120 ... –10 1 ... 32 e
dBm m
q
ne
Hardware Text – u
Heading (deg) 0 ... 360 – p
degrees
HO Event Type 0 ... 6 – u
HO Event Type (Text) Text – u
HS 16-QAM Modulation 0 ... 100 – qh
Rate
%
HS CQI (Max) 0 ... 30 – qh
See Description
HS CQI (Median) 0 ... 30 – qh
HS CQI (Min) 0 ... 30 – qh
HS CQI Feedback Cycle 0 ... 255 – qh
HS CQI Repetition 0 ... 15 – qh
Factor
HS-DSCH ACK Rate 0 ... 100 – qh
%
HS-DSCH BLER 0 ... 100 – qh
%
HS-DSCH DTX Rate 0 ... 100 – qh
%
HS-DSCH Error Blocks 0 ... 20000 – qh
No Of
HS-DSCH HARQ 0 ... 8 – qh
Processes No Of
HS-DSCH NACK Rate 0 ... 100 – qh
%
HS-DSCH 0 ... 100 – qh
Retransmission Rate
%
HS-DSCH 0 ... 20000 – qh
Retransmissions
HS-DSCH Throughput 0 ... 4000 – qh
(kbit/s)
kbit/s
HS H-RNTI 0 ... 65535 – qh
HS Phy Requested 0 ... 4000 – qh
Throughput (kbit/s)
kbit/s
HS Phy Scheduled 0 ... 4000 – qh
Throughput (kbit/s)
kbit/s
HS Phy Served 0 ... 4000 – qh
Throughput (kbit/s)
kbit/s
HS QPSK Modulation 0 ... 100 – qh
Rate
%
HS-SCCH 0 ... 31 1 ... 8 qh
Channelisation Code
HS-SCCH 0 ... 8 – qh
Channelisation Codes
No Of
HS-SCCH Text – qh
Channelisation Codes
(Text)
HS-SCCH Decode 0 ... 100 – qh
Success Rate
%
HS-SCCH OVSF Code 0 ... 127 1 ... 4 qh
HS-SCCH OVSF Codes 0 ... 4 – qh
No Of
HS-SCCH OVSF Codes Text – qh
(Text)
HS Serving Cell 0 ... 511 – qh
HS Session 0 ... 1 – qh
HS Session (Text) Text – qh
HS Transport Block 0 ... 65535 1 ... 8191 qh
Count (Abs)
HS Transport Block 0 ... 65535 1 ... 50 qh
Count (Accu)
HS Transport Block 0 ... 65535 1 ... 50 qh
Count (Curr)
HS Transport Block Size 0 ... 8191 1 ... 50 qh
bits
HS Transport Block 0 ... 31 – qh
Sizes No Of
IMEI Text – u
Inter-freq Event Criteria Text 1 ... 10 u
Inter-freq Event Name Text 1 ... 10 u
Intra-freq Cells Text – u
Intra-freq Event Criteria Text 1 ... 10 u
Intra-freq Event Name Text 1 ... 10 u
Inter-RAT Event Criteria Text 1 ... 5 u
Inter-RAT Event Name Text 1 ... 5 u
Latitude –90 ... 90 – p
degrees
Latitude (Text) Text – p
Longitude –180 ... 180 – p
degrees
Longitude (Text) Text – p
MCC 000 ... 999 – u
Message Hex Dump Text – u
Payload
MNC 000 ... 999 (sometimes 00 – u
... 99)
Mode 0 ... 3 – u
Mode - System 1, 2 – u
Mode - System (Text) Text – u
Mon Neigh Cell Name Text 1 ... 6 u
c
Mon Neigh CPICH –34 ... 0 1 ... 6 u
Ec/No
dB
Mon Neigh CPICH –135 ... –15 1 ... 6 u
RSCP
dBm
Mon Neigh CPICH Tx –31 ... 50 1 ... 6 u
Power
dBm
Mon Neigh No of 0 ... 6 – u
Members
Mon Neigh Pathloss 30 ... 165 1 ... 6 u
dB
Mon Neigh SC 0 ... 511 1 ... 6 u
Mon Neigh UARFCN DL WCDMA 1900A: 1 ... 6 u
9660 ... 9940 1900B:
410 ... 689
2100:00:00
10550 ... 10850
MS Behavior Modified Text: "B", "C", or a – e
(Text) combination of these
letters (or empty string)
me
n
Other/Own, 0 ... 10 0 ... 10 s
Max 1 SC dB cp
Other/Own, 0 ... 10 0 ... 10 s
Max 2 SCs dB cp
Other/Own, 0 ... 10 0 ... 10 s
Max 3 SCs dB cp
Other/Own, 0 ... 10 0 ... 10 s
Max 4 SCs dB cp
"Other/Own 2nd" 0 ... 10 0 ... 10 s
elements
dB cp
"Other/Own 3rd" 0 ... 10 0 ... 10 s
elements
dB cp
"Other/Own 4th" 0 ... 10 0 ... 10 s
elements
dB cp
PDP Access Point Text 1 ... 11 u
Name
PDP Address Text 1 ... 11 u
PDP Contexts Active 0 ... 11 – u
PDP Delay Class Text 1 ... 11 u
PDP LLC SAPI 3, 5, 9, 11 1 ... 11 u
PDP Mean Throughput Text 1 ... 11 u
PDP NSAPI 5 ... 15 1 ... 11 u
PDP Peak Throughput Text 1 ... 11 u
PDP Precedence Class Text 1 ... 11 u
PDP Radio Priority Text 1 ... 11 u
PDP Reliability Class Text 1 ... 11 u
Poss No of AS 0 ... 10 0 ... 10 s
Members
dB cp
Poss No of AS 0 ... 10 0 ... 10 s
Members 2nd
dB cp
Poss No of AS 0 ... 10 0 ... 10 s
Members 3rd
dB cp
Poss No of AS 0 ... 10 0 ... 10 s
Members 4th
dB cp
Power Control Indication –1, 0, 1 – eK
DL
m
n8
q
Power Control Indication –1, 0, 1 – eK
UL
m
n8
q
RACH Initial TX –50 ... 34 – m
dBm
RACH Max Preambles 0 ... 64 – e
q
RACH Message TX –50 ... 34 – m
dBm q
RACH Transmitted 0 ... 64 – u
Preambles
RAT Control 0 ... 3 – e
me
n
RAT Control (Text) Text – e
me
n
RB Setup UL DPCH SC 0 ... 108 – u
RLC AM DL Log Ch Text 1 ... 4 e
Type
q
RLC AM DL PDU 0 ... 100 1 ... 4 e
Retran (%)
q
RLC AM DL PDU Thr 0 ... 3600 1 ... 4 e
kbit/s q
RLC AM DL SDU Thr 0 ... 3600 1 ... 4 e
kbit/s q
RLC AM UL Log Ch Text 1 ... 4 e
Type
q
RLC AM UL PDU Thr 0 ... 2048 1 ... 4 e
kbit/s q
RLC AM UL SDU Thr 0 ... 2048 1 ... 4 e
kbit/s q
RLC DL Entity Data Text: 1 ... 32 e
Mode
"TM", "UM", or "AM" m
RLC DL Throughput 0 ... 3600 1 ... 32 e
kbit/s m
n5
n8
RLC No of Entities 0 ... 32 – e
m
n8
RLC UL Entity Data Text: 1 ... 32 e
Mode
"TM", "UM", or "AM" m
RLC UL Throughput 0 ... 2048 1 ... 32 e
kbit/s m
n5
n8
RLC/Trsp DL 0 ... 3600 – u
Throughput (Best)
kbit/s
RLC/Trsp UL 0 ... 2048 – u
Throughput (Best)
kbit/s
RRC State 0 ... 5 – u
RRC State (Text) Text – u
SAN Cell Id 0 ... 228 – 1 1 ... 38 u
SAN Cell Id (CI Part) 0 ... 216 – 1 1 ... 38 u
SAN Cell Id (CI Part Text: "0000" ... "FFFF" 1 ... 38 u
Hex)
SAN Cell Id (RNC Part) 0 ... 212 – 1 1 ... 38 u
SAN Cell Id (RNC Part Text: "000" ... "FFF" 1 ... 38 u
Hex)
SAN Cell Name Text 1 ... 38 u
c
SAN Cell Type 1 ... 4 1 ... 38 u
c
SAN Cell Type Abbr Str Text 1 ... 38 u
c
SAN CPICH –34 ... 0 1 ... 38 u
Ec/No dB
SAN CPICH –135 ... –15 1 ... 38 u
RSCP dBm
SAN CPICH Tx Power –31 ... 50 1 ... 38 u
dBm
SAN No of Members 0 ... 38 – u
SAN Pathloss 30 ... 165 1 ... 38 u
dB
SAN SC 0 ... 511 1 ... 38 u
SAN UARFCN DL WCDMA 1900A: 1 ... 38 u
9660 ... 9940 1900B:
410 ... 689
2100:00:00
10550 ... 10850
SAN URA Id 0 ... 228 – 1 1 ... 38 n
q
"Sc Best" elements
(general remark)
Sc Best Aggr Eb/Io (dB) –10 ... 21 1 ... 512 s
dB cp
Sc Best Aggr Ec (dBm) –130 ... –25 1 ... 512 s
dBm cp
Sc Best Aggr Ec/Io (dB) –30 ... 0 1 ... 512 s
dB cp
Sc Best Aggr-Peak Ec 0 ... 90 1 ... 512 s
(dB)
dB cp
Sc Best Cell Name Text 1 ... 512 s
cp
c
p
Sc Best Cell Type 1 ... 3 1 ... 512 s
cp
c
p
Sc Best Delay Spread 0 ... 255 1 ... 512 s
cp
Sc Best Io –115 ... –25 – s
dBm cp
Sc Best No of SCs 0 ... 512 – s
cp
Sc Best Peak Eb/Io (dB) –10 ... 21 1 ... 512 s
dB cp
Sc Best Peak Ec (dBm) –130 ... –25 1 ... 512 s
dBm cp
Sc Best Peak Ec/Io (dB) –30 ... 0 1 ... 512 s
dB cp
Sc Best –130 ... –25 1 ... 512 s
P-SCH Ec (dBm) dBm cp
Sc Best –30 ... 0 1 ... 512 s
P-SCH Ec/Io (dB) dB cp
Sc Best Rake Finger 1 ... 51 1 ... 512 s
Count
cp
Sc Best SC 0 ... 511 1 ... 512 s
cp
Sc Best SC Group 0 ... 7 1 ... 512 s
cp
Sc Best SIR (dB) –25 ... 30 1 ... 512 s
dB cp
Sc Best –130 ... –25 1 ... 512 s
S-SCH Ec (dBm) dBm cp
Sc Best –30 ... 0 1 ... 512 s
S-SCH Ec/Io (dB) dB cp
Sc Best Time Offset 0 ... 38399 1 ... 512 s
chips cp
Sc Best Time Offset Slot 1 ... 2560 1 ... 512 s
Pos
cp
Sc Best UARFCN WCDMA 1900A: – s
9660 ... 9940 1900B: cp
410 ... 689
87.5
10550 ... 10850
"Sc 1st" elements
"Sc 2nd" elements
"Sc 3rd" elements
"Sc 4th" elements
SCH TS Sc –24 ... 0 1 ... 2560 sp
Es/Io (dB) dB (max; see ts
Comm.)
SCH TS Sc 0 ... 2560 – sp
No of Segm ts
SCH TS Sc Segm 1 ... 2560 1 ... 2560 sp
(max; see ts
Comm.)
SCH TS Sc 1 ... 2560 – sp
Time Diff 1-2 ts
SCH TS Sc 1 ... 2560 – sp
Time Diff 2-3 ts
SCH TS Sc UARFCN WCDMA 1900A: – sp
9660 ... 9940 1900B: ts
410 ... 689
2100:00:00
10550 ... 10850
Sector Control 0, 1 – me
n
Sector Control (Text) Text – me
n
Serving Cell Id 0 ... 228 – 1 – u
Serving Cell Id (CI Part) 0 ... 216 – 1 – u
Serving Cell Id (CI Part Text: "0000" ... "FFFF" – u
Hex)
Serving Cell Id (RNC 0 ... 212 – 1 – u
Part)
Serving Cell Id (RNC Text: "000" ... "FFF" – u
Part Hex)
Serving Cell LAC 0 ... 65535 – u
Serving Cell LAC (Hex) Text: "0000" ... "FFFF" – u
Serving Cell Name Text – u
c
Serving Cell RAC 0 ... 255 – u
Serving Cell RAC (Hex) Text: – u
"00" ... "FF"
Serving CPICH Ec/No –34 ... 0 – u
dB
Serving CPICH RSCP –135 ... –15 – u
dBm
Serving CPICH Tx –31 ... 50 – u
Power
dBm
Serving Pathloss 30 ... 165 – u
dB
Serving SC 0 ... 511 – u
Serving UARFCN DL WCDMA 1900A: – u
9660 ... 9940 1900B:
410 ... 689
2100:00:00
10550 ... 10850
Serving URA Id 0 ... 228 – 1 – q
SF DL 1 ... 512 – t
SF UL 1 ... 512 – t
SHO Event Rate 0 ... 50 0 ... 3600 u
SHO Event Success 0 ... 100 – u
Rate
%
SHO Percent Softer 0 ... 100 – u
% c
SHO State 0 ... 2 – u
c
SHO State (Text) Text – u
c
SIB Id 0 ... 25 – u
SIR –20 ... 30 – e
dB m
q
t
SIR Target –20 ... 30 – u
dB
Spectr Ana Sc DL Freq 1930 ... 1990 1 ... 2560 s
or ss
2110 ... 2170 MHz
Spectr Ana Sc DL No of 0 ... 2560 – s
Freq
ss
Spectr Ana Sc DL RSSI –115 ... –25 1 ... 2560 s
(dBm)
dBm ss
Spectr Ana Sc UL Freq 1930 ... 1990 1 ... 2560 sr
or ss
2110 ... 2170 MHz
Spectr Ana Sc UL No of 0 ... 2560 – sr
Freq
ss
Spectr Ana Sc UL RSSI –115 ... –25 1 ... 2560 sr
(dBm)
dBm ss
Speed (km/h) 0 ... 250 – p
km/h
Speed (mph) 0 ... 155 – p
mph
Str Neigh Cell Name Text 1 ... 6 u
c
Str Neigh CPICH Ec/No –34 ... 0 1 ... 6 u
dB
Str Neigh CPICH RSCP –135 ... –15 1 ... 6 u
dBm
Str Neigh SC 0 ... 511 1 ... 6 u
Str Neigh Type 3 ... 4 1 ... 6 u
Str Neigh UARFCN DL 0 ... 16383 1 ... 6 u
TEMS Software Version Text – u
Time (Text) Text – u
Trsp Ch BLER, DL (Log) 0 ... 63 1 ... 32 u
Trsp Ch BLER, DL (%) 0 ... 100 1 ... 32 u
%
Trsp Ch BLER, DL (%, 0 ... 100 – u
Worst)
%
Trsp Ch Id DL 1 ... 32 1 ... 32 e
m
q
t
Trsp Ch No of DL 0 ... 32 – e
m
q
t
Trsp Ch No of UL 0 ... 32 – e
m
q
t
Trsp Ch No of Error 0 ... 4095 1 ... 32 e
Blocks
m
q
t
Trsp Ch Rec Blocks 0 ... 4095 1 ... 32 t
Trsp Ch Throughput DL 0 ... 2048 1 ... 32 e
(kbit/s)
kbit/s
Trsp Ch Throughput DL 0 ... 2048 – e
Total (kbit/s)
kbit/s
Trsp Ch Throughput UL 0 ... 2048 1 ... 32 e
(kbit/s)
kbit/s
Trsp Ch Throughput UL 0 ... 2048 – e
Total (kbit/s)
kbit/s
Trsp Ch Type DL Text 1 ... 32 e
m
q
t
Trsp Ch Type UL Text 1 ... 32 e
m
q
t
UE Initial Transmit –60 ... 44 – u
Power
dBm
UE Tx Power –60 ... 44 – u
dBm
UL Interference –110 ... –70 – u
dBm
UTRA Carrier RSSI –128 ... –30 – u
dBm
Description Code
Height above sea level in feet. e
eK
Height above sea level in meters. eV
m
Cell name of each active set member. me
Argument: Active set ID identifying a specific active set. n
CPICH Ec/No of each active set member. n5
Argument: Active set ID. n8
CPICH received signal code power of each active set member. q
Argument: Active set ID. qh
The number of base stations in the active set. Valid only in state Cell_DCH. s
Scrambling code of each active set member. sp
Argument: Active set ID. sr
Downlink UARFCN of each active set member. t
Argument: Active set ID. u
c
cp
cw
Bit error rate, measured using either the pilot bits or the TPC bits on the DPCCH channel (choice da
depends on slot format).
Reported in Q11 format. A 100% error figure means 2047 detected errors. ne
Averaged over reporting period. p
Calculated as follows: ss
# Call Ends / (# Call Ends + # Blocked Calls + # Dropped Calls) ts
Only events occurring in WCDMA mode are counted.
Use of compressed mode.
0: False
1: True
CW scanning: Number of UARFCNs scanned.
CW scanning: RSSI of UARFCNs scanned.
Argument: The channels are sorted by ascending UARFCN. The argument 1 gives the channel with
the lowest UARFCN.
CW scanning: UARFCNs of channels scanned, sorted in ascending order.
Argument: 0 gives the first channel currently scanned, 1 the second, etc.
Cell name of each detected neighbor.
Argument: Neighbor identity.
CPICH Ec/No of each detected neighbor.
Argument: Neighbor identity.
CPICH received signal code power of each detected neighbor.
Argument: Neighbor identity.
CPICH transmit power of each detected neighbor.
Argument: Neighbor identity.
Number of detected neighbors.
Pathloss of each detected neighbor. Calculated as Primary CPICH Tx Power – CPICH RSCP.
Argument: Neighbor identity.
Scrambling code of each detected neighbor.
Argument: Neighbor identity.
Downlink UARFCN of each detected neighbor.
Argument: Neighbor identity.
DPCCH interference signal code power on downlink.
DPCCH received signal code power on downlink.
The Rake fingers are not sorted by signal strength; they come in the order they are reported.
The ordinal ("1st", etc.) refers to a UMTS frequency. Separate elements are provided for each of the
four possible UMTS frequencies.
The Motorola E1000 may report these measurements on a number of different channels (see the
element Finger Position Type); the other devices that support finger measurements always report on
the CPICH.
The "Finger" and "Finger Position" series of elements contain the same data. The latter series
consists of arrays of size 2560 corresponding to the sequence of chips in a radio frame timeslot, with
the received finger information positioned at the correct indices. These elements are provided for bar
chart plotting. The Finger Slot Pos element is of course not needed in the Finger Position series and
is consequently absent from it.
Ec/No for each Rake finger.
Argument: Rake finger number.
Total number of Rake fingers.
RSCP for each Rake finger.
Argument: Rake finger number.
RSSI for each Rake finger.
Argument: Rake finger number.
Scrambling code for each Rake finger.
Argument: Rake finger number.
Radio frame timeslot index for each Rake finger.
Argument: Rake finger number.
Position (chip index) of each Rake finger within the radio frame timeslot.
Argument: Rake finger number.
Type of channel on which each Rake finger is reported (e.g. CPICH).
Argument: Rake finger number.
UARFCN for each Rake finger.
Argument: Rake finger number.
Same as Finger SC (see general remarks).
Argument: Chip index.
Same as Finger Ec/No (see general remarks).
Argument: Chip index.
Same as Finger RSCP (see general remarks).
Argument: Chip index.
Same as Finger RSSI (see general remarks).
Argument: Chip index.
Same as Finger Slot (see general remarks).
Argument: Chip index.
Same as Finger Type (see general remarks).
Argument: Chip index.
Same as Finger UARFCN (see general remarks).
Argument: Chip index.
ARFCNs of measured GSM neighbors.
Argument: 1 gives the neighbor with the highest signal strength, etc.
Base Station Identity Codes (in text format) of measured GSM neighbors.
Argument: See GSM Neigh ARFCN.
Number of measured GSM neighbors.
Received signal strength of measured GSM neighbors.
Argument: See GSM Neigh ARFCN.
Description of UE model.
Direction of testing vehicle measured in degrees clockwise from north.
Type of latest handover.
0: Unknown (e.g. because no cell file loaded)
1: Soft
2: Softer
3: Hard
4: Handover to UTRAN
5: Handover from UTRAN
6: GSM
As HO Event Type but in plain-text format (same strings).
The percentage of the time 16-QAM has been used as modulation method.
The maximum value of the CQI (Channel Quality Indicator).
The definition of the CQI values is given in 3GPP TS 25.214, section 6A.2.
The median CQI value.
Compare HSDPA CQI (Max).
The minimum CQI value.
Compare HSDPA CQI (Max).
CQI feedback cycle, controlling how often the UE transmits new CQI information on the uplink (see
3GPP TS 25.214, section 6A.1.2). A value of zero means that the UE shall not transmit any CQI
information.
CQI repetition factor, controlling how often the UE repeats CQI information on the uplink (see 3GPP
TS 25.214, section 6A.1.2).
ACK / (NACK + ACK) ratio on the HS-DSCH.
Block error rate on the HS-DSCH.
DTX rate on the HS-DSCH.
Number of error blocks on the HS-DSCH.
Number of active HARQ (Hybrid Automatic Repeat Request) processes on the HS-DSCH.
NACK / (NACK + ACK) ratio on the HS-DSCH.
Retransmission rate on the HS-DSCH.
Number of retransmitted blocks on the HS-DSCH.
Throughput on the HS-DSCH.
HSDPA Radio Network Temporary Id. Fetched from HSDPA Configuration Report.
Calculated as: (Average requested transport block size based on CQI) / (2 ms)
Calculated as: (Average transport block size in TTIs where data is transferred) / (2 ms)
(Only TTIs in which data is actually received are considered in the throughput calculation.)
Calculated as: (Average transport block size counting all TTIs) / (2 ms)
(All TTIs, also those in which no data is received, are included in the throughput calculation.)
The percentage of the time QPSK has been used as modulation method.
Channelisation codes used on the HS-SCCH, arranged in ascending order.
Argument: Channelisation code index.
Number of channelisation codes used on the HS-SCCH.
List of HS-SCCH channelisation codes in text format.
Decode success rate on the HS-SCCH. For the decoding to count as a success, both the first and
the second parts must have been completed successfully.
Orthogonal Variable Spreading Factor codes used on the HS-SCCH, arranged in ascending order.
Argument: OVSF code index.
Number of Orthogonal Variable Spreading Factor codes used on the HS-SCCH.
List of HS-SCCH Orthogonal Variable Spreading Factor codes in text format.
The scrambling code index of the HSDPA serving cell.
Indicates whether the session is an HSDPA session.
0: No
1: Yes
Same as HS Session but in text format.
Block counts for all possible HSDPA transport block sizes, accumulated over the current session.
Argument: The transport block size itself (not an index).
Block counts for HSDPA transport block sizes currently in use, accumulated over the current session.
Argument: Transport block size index.
Block counts for HSDPA transport block sizes currently in use, collected over the latest report period.
Argument: Transport block size index.
Transport block sizes on the HS-DSCH.
Argument: Transport block size index.
Number of HSDPA transport block sizes currently in use.
International Mobile Equipment Identity, the unique equipment identity of the UE.
Event criteria governing when the UE should send inter-frequency measurement reports.
Argument: One argument for each event criterion.
Names of events governing sending of inter-frequency measurement reports by the UE. The events
extracted to this element are "e2a", "e2d", and "e2f". Other inter-frequency events are not extracted.
Argument: One argument for each event criterion. There may be multiple criteria for the same event.
Cells on which the UE has been ordered to perform intra-frequency measurements.
Valid only in connected mode.
Event criteria governing when the UE should send intra-frequency measurement reports.
Argument: One argument for each event criterion.
Names of events governing sending of intra-frequency measurement reports by the UE. The events
extracted to this element are "e1a", "e1b", "e1c", and "e1d". Other intra-frequency events are not
extracted.
Argument: One argument for each event criterion. There may be multiple criteria for the same event.
Event criteria governing when the UE should send inter-RAT measurement reports.
Argument: One argument for each event criterion.
Names of events governing sending of inter-RAT measurement reports by the UE. The only event
extracted to this element is "e3a". Other inter-RAT events are not extracted.
Argument: One argument for each event criterion. There may be multiple criteria for the same event.
Latitude recorded by positioning equipment.
Latitude as text. For the presentation format, see the Route Analysis User's Manual, appendix C.4.
Longitude recorded by positioning equipment.
Longitude as text. For the presentation format, see the Route Analysis User's Manual, appendix C.4.
Mobile Country Code.
Contains the hexadecimal string of a Layer 3 message or mode report.
Used for text-format logfile export only.
Mobile Network Code. May consist of two or three digits.
0: None
1: No service
2: Idle mode
3: Connected mode
UE mode.
1: WCDMA
2: GSM
UE mode: "WCDMA" or "GSM".
Cell name of each monitored neighbor.
Argument: Neighbor identity.
CPICH Ec/No of each monitored neighbor.
Argument: Neighbor identity.
CPICH received signal code power of each monitored neighbor.
Argument: Neighbor identity.
CPICH transmit power of each monitored neighbor.
Argument: Neighbor identity.
Number of monitored neighbors.
Pathloss of each monitored neighbor. Calculated as Primary CPICH Tx Power – CPICH RSCP.
Argument: Neighbor identity.
Scrambling code of each monitored neighbor.
Argument: Neighbor identity.
Downlink UARFCN of each monitored neighbor.
Argument: Neighbor identity.
Indicates whether the UE behavior has been changed from the default.
Empty string: No modification of UE behavior
B: Modification of UE behavior in network (RAT Control information element)
C: Modification of UE reselection behavior: (Sector Control information element)
Combinations of these letters may appear.
CPICH scanning (section 8.4): Estimated ratio between polluting signal power and desired signal
power on a CPICH control channel, based on the assumption that there is only one possible member
in the active set.
Applies to the first UMTS frequency scanned (lowest UARFCN).
Argument: Power threshold (in dB) relative to the power of the strongest scrambling code; used to
identify possible active set members.
As Other/Own, Max 1 SC except that the active set is assumed to have at most two possible
members.
Applies to the first UMTS frequency scanned.
As Other/Own, Max 1 SC except that the active set is assumed to have at most three possible
members.
Applies to the first UMTS frequency scanned.
As Other/Own, Max 1 SC except that the active set is assumed to have at most four possible
members.
Applies to the first UMTS frequency scanned.
Same as "Other/Own, ..." but for the second UMTS frequency.
Same as "Other/Own, ..." but for the third UMTS frequency.
Same as "Other/Own, ..." but for the fourth UMTS frequency.
Host name or network address for each active PDP context.
Argument: PDP context index.
User address (IPv4/IPv6).
Argument: PDP context index.
Number of active PDP contexts.
Delay class as defined by sub-scription (Subscribed, 1, 2, 3, or 4).
Argument: PDP context index.
LLC Service Access Point Identifier.
Argument: PDP context index.
Mean throughput (100 bytes/h–50 MB/h).
Argument: PDP context index.
Network SAPI (Service Access Point Indicator).
Argument: PDP context index.
Peak throughput as defined by subscription. 1–256 kB/s.
Argument: PDP context index.
Precedence class as defined by subscription: Subscribed, High, Normal, or Low priority.
Argument: PDP context index.
Radio priority level as defined by subscription.
Argument: PDP context index.
Reliability class as defined by subscription.
Argument: PDP context index.
CPICH scanning: The estimated number of possible members in the active set.
Applies to the first UMTS frequency scanned (lowest UARFCN).
Argument: Power threshold (in dB) relative to the power of the strongest scrambling code.
Same as Poss No of AS Members but for the second UMTS frequency.
Same as Poss No of AS Members but for the third UMTS frequency.
Same as Poss No of AS Members but for the fourth UMTS frequency.
Inner loop power control indication on downlink.
Based on the recent history of power control decisions:
The value –1 means that the power has been adjusted predominantly downward.
The value 0 means that the upward and downward power adjustments have canceled out exactly.
The value +1 means that the power has been adjusted predominantly upward.
Inner loop power control indication on uplink. Works the same way as Power Control Indication DL,
which see.
Transmit power of first RACH preamble in dBm.
Maximum number of preambles in one preamble ramping cycle.
Transmit power of last RACH preamble in dBm.
Number of preambles used in this preamble ramping cycle.
Use of Lock to RAT function in UE.
0: Lock to RAT disabled (default)
1: Locked to GSM 900/1800
2: Locked to GSM 850/1900
3: Locked to WCDMA
Same as RAT Control but in text format.
The scrambling code of the uplink DPCH.
Type of downlink logical channel, e.g. "DCCH".
Argument: Logical channel index.
PDU retransmission percentage. Calculated as:
Argument: Logical channel index.
Radio Link Control PDU throughput (Acknowledged Mode, downlink), counting both control PDUs
and AM PDUs.
Argument: Logical channel index.
Radio Link Control SDU throughput (Acknowledged Mode, downlink).
Argument: Logical channel index.
Type of uplink logical channel, e.g. "DCCH".
Argument: Logical channel index.
Radio Link Control PDU throughput (Acknowledged Mode, uplink), counting both control PDUs and
AM PDUs.
Argument: Logical channel index.
Radio Link Control SDU throughput (Acknowledged Mode, uplink).
Argument: Logical channel index.
Downlink RLC entity data mode: Transparent Mode, Unacknowledged Mode, or Acknowledged
Mode.
Argument: RLC entity.
Total RLC downlink throughput.
Argument: RLC entity.
Total number of RLC entities on uplink and downlink.
Uplink RLC entity data mode: Transparent Mode, Unacknowledged Mode, or Acknowledged Mode.
Argument: RLC entity.
Total RLC uplink throughput.
Argument: RLC entity.
Highest downlink throughput for all RLC entities/transport channels.
Highest uplink throughput for all RLC entities/transport channels.
State of RRC protocol:
0: No service
1: Idle mode
2: Connected_Cell_FACH
3: Connected_Cell_DCH
4: Connected_Cell_PCH
5: Connected_URA_PCH
The state is set to idle when the UE registers, and the information element is then updated each time
the state changes.
See 3GPP TS 25.331.
RRC State in text format.
Serving/Active Set + Neighbors window: Cell identity of each cell listed.
Argument: Indicates the row in the window. In Cell_DCH mode, the active set is on top (max 4
rows), whereas in other modes the serving cell is found on row 1. In either case the neighbors follow
directly beneath.
Cell Identity part of SAN Cell Id: bits 12 through 27 (in decimal).
Argument: See SAN Cell Id.
Cell Identity part of SAN Cell Id: bits 12 through 27 in hexadecimal.
Argument: See SAN Cell Id.
RNC part of SAN Cell Id: bits 0 through 11 (in decimal).
Argument: See SAN Cell Id.
RNC part of SAN Cell Id: bits 0 through 11 in hexadecimal.
Argument: See SAN Cell Id.
Serving/Active Set + Neighbors window: Name of each cell listed.
Argument: Window row.
Serving/Active Set + Neighbors window: Type of cell for each cell listed.
1: Serving cell
2: Active set member
3: Monitored neighbor
4: Detected neighbor
Argument: Window row.
As SAN Cell Type but with text strings indicating the type of cell:
SC: Serving cell
AS: Active set member
MN: Monitored neighbor
DN: Detected neighbor
Argument: Window row.
Serving/Active Set + Neighbors window: CPICH Ec/No for each cell listed.
Argument: Window row.
Serving/Active Set + Neighbors window: CPICH RSCP for each cell listed.
Argument: Window row.
Serving/Active Set + Neighbors window: Primary CPICH transmit power for each cell listed.
Argument: Window row.
Serving/Active Set + Neighbors window: Total number of cells listed.
Serving/Active Set + Neighbors window: Pathloss for each cell listed. Calculated as Primary CPICH
Tx Power – CPICH RSCP.
Argument: Window row.
Serving/Active Set + Neighbors window: Scrambling code for each cell listed.
Argument: Window row.
Serving/Active Set + Neighbors window: Downlink UARFCN for each cell listed.
Argument: Window row.
Serving/Active Set + Neighbors window: URA identity of each cell listed.
Argument: Window row.
These elements combine scrambling codes from all scanned UMTS frequencies, sorted by
descending Aggr Ec/Io. The sorting order of the "Best" elements is not affected by the settings in the
General window (section 8.4.10.1).
CPICH scanning: The aggregate code power of the scrambling code (Eb, energy per bit) relative to
the total signal power in the channel (Io).
Argument: 1 is the scrambling code with the highest Aggr Ec/Io, etc.
CPICH scanning: The aggregate code power (energy per chip) of each scanned scrambling code.
The aggregate code power is a measure of the total signal power (distributed around the main peak
due to multipath propagation) that is above the PN threshold (see section 8.4.1).
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The aggregate code power of the scrambling code (Ec, energy per chip) relative to
the total signal power in the channel (Io).
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The difference between the aggregate code power and peak code power.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: Deduced name of the cell that uses each scanned scrambling code.
The algorithm determining the cell name takes as input the SC number, the UARFCN, and the
position reported. It searches the cell file for cells with matching SC number and UARFCN within a 50
km radius. If multiple matches are found, the cell closest to the position is selected.
If no positioning data is available, the information element will still be presented, but the cell names
may then of course be wrong. The algorithm in this case simply picks the first cell in the cell file with
matching SC number and UARFCN.
Invalid if no cell file is loaded.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: Categorization of the cells that use the scanned scrambling codes.
1: The cell with the strongest Aggr Ec.
2: All neighbors of the "1" cell, as indicated by the cell file.
3: All other cells.
In the "Sc Best" element, this categorization is applied for each UMTS frequency, so there will be one
"1" with associated "2"s for each frequency.
Invalid if no cell file is loaded.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: Time in chips between the first and last Ec/Io peak that is above the PN threshold
(see section 8.4.1). This is a measure of the signal spreading due to multipath propagation.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The total signal power in the channel.
CPICH scanning: The number of scrambling codes scanned.
CPICH scanning (section 8.4): The peak code power of each scanned scrambling code (Eb, energy
per bit) relative to the total signal power in the channel (Io), i.e. the difference between them in dB.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The peak code power of each scanned scrambling code (Ec, energy per chip) in
dBm.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The peak code power of each scanned scrambling code (Ec, energy per chip)
relative to the total signal power in the channel (Io), i.e. the difference between them in dB.
Argument: See Sc Best Aggr Eb/Io.
The peak code power of each scanned scrambling code on the primary synchronization channel
(P-SCH).
Argument: See Sc Best Aggr Eb/Io.
The peak code power (Ec) of each scanned scrambling code on the primary synchronization channel
(P-SCH), relative to the total signal power in the channel (Io).
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: Number of Ec/Io peaks (multipath components) that are above the PN threshold.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The number of each scanned scrambling code.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The number of the group to which each scanned scrambling code belongs.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: Received SIR (in dB) for scanned scrambling codes.
Argument: See Sc Best Aggr Eb/Io.
The peak code power of each scanned scrambling code on the secondary synchronization channel
(S-SCH).
Argument: See Sc Best Aggr Eb/Io.
The peak code power (Ec) of each scanned scrambling code on the secondary synchronization
channel (S-SCH), relative to the total signal power in the channel (Io).
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The time offset of the radio frame (10 ms = 38,400 chips) for each scanned
scrambling code.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: Equal to
(Sc Best Time Offset mod 2560) + 1.
Argument: See Sc Best Aggr Eb/Io.
CPICH scanning: The UARFCN of the CPICH currently scanned.
Same as "Sc Best" elements except that only the first UMTS frequency is considered.
Argument: The sorting order depends on the General window setting: see section 8.4.10.1.
Same as "Sc Best" elements except that only the second UMTS frequency is considered.
Argument: The sorting order depends on the General window setting: see section 8.4.10.1.
Same as "Sc Best" elements except that only the third UMTS frequency is considered.
Argument: The sorting order depends on the General window setting: see section 8.4.10.1.
Same as "Sc Best" elements except that only the fourth UMTS frequency is considered.
Argument: The sorting order depends on the General window setting: see section 8.4.10.1.
SCH timeslot scanning (section 8.5): Power in each segment (1, 2, 4, or 8 chips depending on setup)
of the scanned timeslot.
Argument: Index of timeslot segment (not chip index). If "Every 2" has been chosen, the argument
range is 1 ... 2560/2, i.e. 1 ... 1280; for "Every 4", the range is 1 ... 640; for "Every 8", the range is 1 ...
320.
SCH timeslot scanning: Number of scanned timeslot segments (each with length 1, 2, 4, or 8 chips
depending on setup).
SCH timeslot scanning: Position of each timeslot segment scanned, expressed as a chip index. The
first chip has number 1.
Argument: Index of timeslot segment (not chip index). If "Every 2" has been chosen, the argument
range is 1 ... 2560/2, i.e. 1 ... 1280; for "Every 4", the range is 1 ... 640; for "Every 8", the range is 1 ...
320.
SCH timeslot scanning: The time separation in chips between the strongest peak and the second
strongest.
SCH timeslot scanning: The time separation in chips between the second strongest peak and the
third strongest.
SCH timeslot scanning: UARFCN scanned.
Use of Lock to Sector function in UE in idle mode:
0: Lock to Sector disabled
1: Lock to Sector enabled
Same as Sector Control but in text format.
Cell identity of the serving cell.
Not valid in Cell_DCH mode.
Cell Identity part of Serving Cell Id: bits 12 through 27 (in decimal).
Not valid in Cell_DCH mode.
Cell Identity part of Serving Cell Id: bits 12 through 27 in hexadecimal.
Not valid in Cell_DCH mode.
RNC part of Serving Cell Id: bits 0 through 11 (in decimal).
Not valid in Cell_DCH mode.
RNC part of Serving Cell Id: bits 0 through 11 in hexadecimal.
Not valid in Cell_DCH mode.
LAC of serving cell.
Not valid in Cell_DCH mode.
LAC of serving cell in hexadecimal format.
Not valid in Cell_DCH mode.
Name of the serving cell.
Not valid in Cell_DCH mode.
RAC of serving cell.
Not valid in Cell_DCH mode.
RAC of serving cell in hexadecimal format.
Not valid in Cell_DCH mode.
CPICH Ec/No of the serving cell.
Not valid in Cell_DCH mode.
CPICH received signal code power of the serving cell.
Not valid in Cell_DCH mode.
CPICH transmit power of the serving cell.
Not valid in Cell_DCH mode.
Pathloss of the serving cell. Calculated as Primary CPICH Tx Power – CPICH RSCP.
Not valid in Cell_DCH mode.
Scrambling code of the serving cell in idle, Cell_FACH, Cell_PCH, and URA_PCH mode.
Not valid in Cell_DCH mode.
Downlink UARFCN of the serving cell in idle, Cell_FACH, Cell_PCH, and URA_PCH mode.
Not valid in Cell_DCH mode.
URA (UTRAN Region Area)identity of the serving cell.
Not valid in Cell_DCH mode.
Spreading factor on downlink.
Spreading factor on uplink.
Number of Radio Link events (both failures and successes) per second over the last arg seconds,
where arg is the value of the argument.
About the events, see appendix H.
Argument: See above. Argument = 0 means that the events are counted from the beginning of the
logfile.
Soft handover success rate. Calculated as:
(# add + # rem + # repl ) / # all
where
add = Radio Link Addition events
rem = Radio Link Removal events
repl = Radio Link Replacement events
all = all Radio Link events, including failures
About the events, see appendix H.
A measure of the amount of softer handover. Calculated as:
# softer / (# softer + # soft )
where
softer = Radio link event indicating success occurs while in softer handover (and with more than one
member in active set)
soft = Radio link event indicating success occurs while in soft handover (and with more than one
member in active set)
A radio link event is one of Radio Link Addition, Radio Link Removal, and Radio Link Replacement.
Requires that a cell file has been loaded (otherwise the element is invalid).
Soft handover state.
0: Unknown (no cell data loaded)
1: Soft handover
2: Softer handover
Requires that a cell file has been loaded (otherwise the value will always be 0).
Invalid when AS No of Members =) (Ec/No>=) No
Ec - No = -106 - No = -14
AMR 12.2 Voice -106 -14 -92 No = Ec - Ec/No = -106 - ( -14) = -92
CS 64 Video -101 -12 -89
PS 64 -101 -12 -89
PS 128 -98 -11 -87
here the power requirements (Ec) are
PS 384 -93 -10 -83 high but the Ec/No is slightly lower
Max No for minimum Ec or as an example for a given Energy [dB] examples
Ec limited by the Min Ec/Io
Min. Ec/No (max "negative" segment length) No
it takes in consideration the max distance if No>Ec Ec
Ec
Ec No
Minimum Ec
Ec No
No
AMR CS 64 PS 64 PS 128 PS 384
12.2 Video
Notes on Quantities Denoting Signal Power
Eb = Ec + 21.07dB = Scrambling code energy per bit as measured by a scanner (except during the SCH timeslot scan).
Ec = RSCP = Scrambling code energy per chip as measured by a scanner (except during the SCH timeslot scan).
= Received signal code power, identical with Ec according to 3GPP TS 25.215, section 5.1.6.
No = RSSI = Total energy per chip measured by a UE.
= Received signal strength indicator, identical with No
Io: Total energy per chip as measured by a scanner.
Ec/No: Signal-to-noise ratio measured by a UE on CPICH
Ec/Io: Signal-to-noise ratio as measured by a scanner. on CPICH
SIR: Signal-to-interference ratio measured by a UE on DPCH.
Es: Scrambling code energy per chip as measured by a scanner during the SCH timeslot scan.
•Eb/No = Ec/Io + Processor Gain. – The ratio of the Energy per information bit(Eb) to the power spectral density of thermal noise(No).
Processor Gain varies with different Class of Service. CS-Voice(12.2kbps) is 25dB while PS-Data(384kbps) is 10dB.
•RSCP – Received Signal Code Power. The energy per chip in the downlink common pilot channel, average over 512 chips. RSCP can be related to GSM BCCH
•Mean Served - the mean number of successful service connections
•Ec/Io - The ratio of the energy per chip (Ec) in the downlink common pilot channel (RSCP) to the power spectral density (Io) of all received signals (including the pilot itself).
•Ec/Io (UMTS) vs C/I (GSM) ==>>•Ec/Io and C/I are not the same
Ec – Pilot Channel
C – Traffic Channel
Io –Everything ( total wide band received power – pilot, traffic, this cell, other cells)
I – interference ( co/adj channels not including traffic channel)
The indoor coverage levels:
Service Pilot RSCP threshold Ec/No requirement
AMR 12.2 Voice >= -14
>= -106 dBm [ERICSSON -101dBm] dB
CS 64 Video >= -101 dBm >= -12 dB
PS 64 >= -101 dBm >= -12 dB
PS 128 >= -98 dBm >= -11 dB
PS 384 >= -93 dBm >= -10 dB
On Street RF Design Levels to yield in Car Service:
Service Pilot RSCP threshold Ec/No requirement
AMR 12.2 Voice >=-100dBm [-95dBm] ERICSSON value>=-14dB
CS-64 >=-97dBm >=-12dB
PS-64 >=-97dBm >=-12dB
PS-128 >=-92dBm >=-11dB
PS-384 >=-87dBm >=-10dB
uding the pilot itself).
FileName (last valid value)
CollectionYear
CollectionMonth
CollectionDay
Start Time (ms)
EndTime (ms)
FileSize
Distance
Occurences
ServingSectorID (last valid value)
CSV_Call Duration
CSV_Uu_IncomingCallSetupFail
CSV_Uu_OutgoingCallSetupFail
CSV_Uu_OutgoingCallOk
CSV_Uu_IncomingCallOk
CSV_Uu_CallDropped
CSV_Uu_CallCompleted
CSV_Uu_TrCh_DownlinkBlerAgg
CSV # of Quality Samples Passing
CSV # of Quality Samples NOT Passing
CSV_Uu_TrCh_UL_BlerAgg
CSV # of UL_Quality Samples Passing
CSV # of UL_Quality Samples NOT Passing
CSV_CallSetupTime(RRC_REQandCCAlerting)
CSV_CallSetuptime_MP_PassingSamples
CSV_CallSetupTime_MP_NOTPassSamples
CSV_CallSetuptime_MM_PassingSamples
CSV_CallSetupTime_MM_NOTPassSamples
CSV_DurationOfActiveSetSize1
CSV_DurationOfActiveSetSize2
CSV_DurationOfActiveSetSize3
CSV_DurationOfActiveSetSize4
CSV_DurationOfActiveSetSize5
CSV_DurationOfActiveSetSize6
CSV_IRAT_Success
CSV_IRAT_Fail
CSV_RRC - HandoverFromUTRANFailure
CSV_RRC - HandoverFromUTRANCommand-GSM
CSV_RRC - ActiveSetUpdateComplete
CSV_RRC - ActiveSetUpdate
CSD_Uu_OutgoingCallSetupFail
CSD_Uu_IncomingCallSetupFail
CSD_Uu_OutgoingCallOk
CSD_Uu_IncomingCallOk
CSD_Uu_CallDropped
CSD_Uu_CallCompleted
CSD_Uu_TrCh_DownlinkBlerAgg
CSD # of Quality Samples Passing
CSD # of Quality Samples NOT Passing
CSD_Uu_TrCh_UL_BlerAgg
CSD # of UL_Quality Samples Passing
CSD # of UL_Quality Samples NOT Passing
CSD_Uu_TimeBetweenRRC_REQandCallStart
CSD_CallSetuptime_PassingSamples
CSD_CallSetupTime_NOTPassSamples
PS_Uu_IncomingCallSetupFail
PS_Uu_OutgoingCallSetupFail
PS_Uu_OutgoingCallOk
PS_Uu_IncomingCallOk
PS_Uu_CallCompleted
PS_Uu_CallDropped
PS_Call Duration
PS_DurationOfActiveSetSize1
PS_DurationOfActiveSetSize2
PS_DurationOfActiveSetSize3
PS_DurationOfActiveSetSize4
PS_DurationOfActiveSetSize5
PS_DurationOfActiveSetSize6
PS_UserData_DL_RAB_64K (bytes)
PS_TransferDuration_DL_RAB_64K
PS_UserData_DL_RAB_128K (bytes)
PS_TransferDuration_DL_RAB_128K
PS_UserData_DL_RAB_384K (bytes)
PS_TransferDuration_DL_RAB_384K
PS_UserData_UL_RAB_64K (bytes)
PS_TransferDuration_UL_RAB_64K
PS_UserData_UL_RAB_128K (bytes)
PS_TransferDuration_UL_RAB_128K
PS_UserData_UL_RAB_384K (bytes)
PS_TransferDuration_UL_RAB_384K
PS_PingRTT
PS_PingSamplesPass
PS_PingSamplesFail
PS_MeanCallSetupTime(msecs)
PSD_CallSetuptime_PassingSamples
PSD_CallSetupTime_NOTPassSamples
PS_IRAT_Success
PSD_IRAT_Failure
HSDPA_Uu_Call_Dropped
HSDPA_Uu_CallSetup_OK
HSDPA_Uu_CallSetup_Fail
HSDPA_UserData_DL_RAB (bytes)
HSDPA_DL_TransferDuration
HS_DL_AppThroughputMax
HSDPA_UserData_UL_RAB (bytes)
HS_UL_TransferDuration
HS_UL_AppThroughputMax
HSDPA_PingRTT
HSDPA_PingSamplePass
HSDPA_PingSamplesFail
HSDPA_MeanSessionSetupTime(msecs)
HSDPA Session Activation_PASS_Samples
HSDPA_SessionActivationTime_NOTPASS_Samples
Occurences
All
BLER_Mean
BLER_Max
BLER_Min
CallSetupTime_Mean
CallSetupTime_Max
CallSetupTime_Min
Mean_EcIo
Max_EcIo
Min_EcIo
Mean_RSCP
Max_RSCP
Min_RSCP
Occurences
BLER_Values
Samples
Occurences
CallSetupTimeSecs_Value
Samples
Occurences
EcIo_Value
Samples
Occurences
All
CQI_0
CQI_1
CQI_2
CQI_3
CQI_4
CQI_5
CQI_6
CQI_7
CQI_8
CQI_9
CQI_10
CQI_11
CQI_12
CQI_13
CQI_14
CQI_15
CQI_16
CQI_17
CQI_18
CQI_19
CQI_20
CQI_21
CQI_22
CQI_23
CQI_24
CQI_25
CQI_26
CQI_27
CQI_28
CQI_29
CQI_30
Occurences
RSCP_Value
Samples
Occurences
ServingSectorID (last valid value)
CS_RAB_SetupOk
CS_RAB_SetupFail
CS_RAB_ReleaseOk
CS_RAB_ReleaseFail
CS_RAB_ReconfigOk
CS_RAB_Reconfig_Fail
PS_RAB_SetupOk
PS_RAB_SetupFail
PS_RAB_ReleaseOk
PS_RAB_ReleaseFail
PS_RAB_ReconfigOk
PS_RAB_ReconfigFail
RRC_OK
RRC_Reject
RRC_Abort
Occurences