Validation Process

What is Shakedown Testing

Shakedown testing, also known as site acceptance testing

In Shakedown testing ,We do Functional Testing as well as
Mobility testing.
Functional testing focuses on voice and data tests
performed in each sector of the cell, close to the site. Tests
ensure not only that a device connects to the proper sector,
but also assess fallback mechanisms to make sure that
fallback to circuit-switched voice and 3G data sessions work
properly.
Mobility testing ensures that handovers between the
sectors at the site are happening properly, with a low
degree of latency.handovers are tested at all three of the
sectors: sector A to B, B to C, and C to A.

Types of Tests

We need to perform fallowing tests for Each sector of the site.

Stationary Test
a)Ping
b)PDL
c)PUL
d)Setup
e)CSFB MO
f)CSFB MT
Mobility
a)CW Handover Testing
b)CCW Handover Testing

After Test Completion?

After Test completion Engineer will upload logs on Server.

Validation Team will download Logs from TAPAS DASHBOARD.
Validation Team will process logs in Actix for further Analysis
checking the Kpi values in Actix.
Validation Team will update the tickets on fresh desks.
Good log file Package will uploaded by Validation team in
Xynergy.
Work flow as shown below:
Serve
TAPAS
r

Actix

files+Package

Process & Anaylsis

Good Log

Xynergy

Tools Used in Validation?

TAPAS DASHBOARD
Actix 5.03
QCAT
Fresh Desk

Downloading the log files

Tapas dash Board

File zilla

Stationary KPI

Ping
Ping<50msec(Pass)
Ping<57.5msec(conditional Pass)
What Happen if ping fails??Ans: Ask
for trace route.
Microsoft Office
Word Document

Stationary KPI

PUL
PUL>14Mbps(Pass)
PUL>12.6Mbps(conditional Pass)
PUL Throughput is Dependant on
Backhaul Capacity so based on BH
capacity Threshold Defined.

Stationary KPI
PUL Throughput How do you look in
Actix??

Stationary KPI

PDL
PDL>14Mbps(Pass)
PDL>12.6Mbps(conditional Pass)
PDL Throughput is Dependant on Backhaul Capacity so based
on BH capacity Threshold Defined.
Peak DL Throughput (50 Mbps)
> 40 Mbps(pass)
> 38 Mbps(conditional Pass)
Peak DL Throughput (55 Mbps)
> 45 Mbps(Pass)
> 40 Mbps(conditional Pass)
Peak DL Throughput (75 Mbps)
> 60 Mbps(Pass)
> 55 Mbps(conditional Pass)

Stationary KPI
PDL Throughput How do you look in
Actix??

Stationary KPI
SETUP(CST is the duration from
Channel Request until Alerting)
SETUP<700msec(Pass)
SETUP<2000msec(Pass)
We can Check SETUP Time In Actix as
well as in QCAT.

Stationary KPI
SETUP(CST is the duration from
Channel Request until Alerting)
Actix Slide

Stationary KPI
CSFB MO

Stationary KPI
CSFB MO How do we look in actix??

 CSFB MO??
What to look for?? >>QCAT>>Actix
snap

Stationary KPI
CSFB MT

Stationary KPI
CSFB MT How do we look in actix??

Mobility KPI
Cw
Ccw
Thershold>>>Handover latency
cal??

Mobility KPI

Mobility testing ensures that handovers between the

sectors at the site are happening properly, with a low
degree of latency.handovers are tested at all three of the
sectors: sector A to B, B to C, and C to A.
a)CW Handover Testing
b)CCW Handover Testing
Handover Latency<60msec (Pass)

 Creating a package??Naming
Convention??

Here we can load Log file in Actix

PDL KPI

PUL KPI

Data Validation
1. Load the log files for the following test cases In Actix and ensure that they
meet the following criteria:

For MO/MT Please confirm successful MO eCSFB and successful MTeCSFB.

This is done to ensure that the UE is failing back onto UMTS on the required
channel.

NOTE: Download all the files from dashboard into a folder

Site-Name. In this folder ensure that the all the log files
which are going to be part of the package are put in a
separate folder called Final Package. All the other files
must be put in the main folder.

Data Validation Continue

2. We have to always ensure that the package has the best log
files. Our main criteria is to get a PASSING KPI. It is only in the
worst case (After 5 attempts) that we will look to submit a
package for CONDITIONAL PASS.
3.
Once the Package is complete please rename it as per the
naming
convention below:

Data Validation Continue

Data Validation Continue