3G SSV DT Purpose Process

HUAWEI TECHNOLOGIES CO., LTD.
Page 1

3G SSV Drive Test
Purpose & Methodology

Review
This guide defines the prerequisites, workflow,
deliverables and checklist deliverables for radio network
single site verification service. It aims to guide the
related service delivery departments and personnel to
get familiar with the service delivery content and to
deliver the service by following the standard flow, thus
delivering the service with a high efficiency and a good
quality.

Purpose of SSV DT
Installation quality Audit (such as cross cable)
Parameter Audit (such as PSC, LAC/RAC, URA, NBR, frequency)
Hardware problem checking
Functional Verification (service wise)
Accessibility
Retainability
Mobility (SHO & IRAT HO)
Capacity & Congestion
Data performance
Cell Re/Selection

Page 3
Prerequisites

Page 4

Site is Integrated successfully
Cell planning report and site database
- SSV Template approved
Tools Setup
- Probe & Assistant
- MapInfo/GoogleEarth
- Test UE, GPS & other Tools.

Good preparation will improve SSV efficiency extremely, which are included in following
slides:
Prerequisites

Page 5
Site Status Audit
Before SSV test, information about Site Status must be confirmed from the RNC engineer.
The target for site status audit is to make sure the test site is working normally, otherwise it
must influence SSV. It includes:
- Alarm audit; (pay attention to transmission related alarms)
- Cell status;
- HSDPA/HSUPA status
- Neighbor list checking (if handover is required to be test)
- Basic parameters
Parameters Audit
Before SSV, the test engineer must get the configuration file and audit it.
Workflows

Page 6
Radio Network
Tuning
Equipment Installation
Commissioning &
Implementation

Verification Test
Y
Problem
Found?
N
SSV Report
Generation
Troubleshooting
Test Methodology Definition
and Route Design
SSV
Report
SSV Control
Table
Tools Setup
System
Parameters Audit
Workflows

Page 7
There are four stages in the single site verification.

Methodology Definition and Route Design
Verification Test
Troubleshooting
SSV Report Generation
Methodology Definition and Route Design

Page 8
Before starting the drive test, we need to define the test methodology with customer,
including:

Test Method: long call, short call, Video call, throughput test method, etc.
Test Period for each type of test.
Categories for test UE.
File Size for Download and Upload (throughput) and ftp window size configuration.
DT Check Items as per SSV report format.
The principles for SSV DT route planning must be defined together with customer.

Methodology- Typical Example

Page 9
Network
Mode on the
Device
Test Case
Category
UE # Terminal Configuration Configuration Details
3G
Dynamic
MS1 Scanner
Scanner Till -105 for City Sites and
Till -95 for Road Sites
MS2 Short Call
15 sec dur, and 10 sec gap to MSC
number
MS3 Long Call
4 min dur, and 7 sec gap to MSC
number
MS4
R99 UL/DL R99 FTP UL/DL 1MB
Ping
32B ping with <1s between pings to
measure latency
MS5 Video Call
Duration of call is 120 seconds, with
attempt time out of 20 sec and idle
time of 20 sec. Both UEs locked on
3G
Static
MS1 Category III (HSPA)
5 x DL 10MB | 5 x UL 10MB | 32B
ping with <1s between pings
MS2 Category VI (HSPA)
5 x DL 10MB | 5 x UL 10MB | 32B
MS3 Category VIII (HSPA)
5 x DL 10MB | 5 x UL 10MB | 32B
MS4 Category X (HSPA)
5 x DL 10MB | 5 x UL 10MB | 32B
DT Check Items- Typical Example

Page 10
Category Checks
Check
Comm
ent
(OK/
NOK/NA)
Idle Mode
Frequency and Scrambling Code correctly defined
Cell selection and reselection parameters are as planned
The LAC/RAC is correctly defined
LA update procedure is checked
MO-SMS and MT-SMS
PS
PS attach is checked
PS detach is checked
PS PDP activation and deactivation is checked

Handover
Soft handover for voice service to and from the 3G cells checked OK
Soft handover for VP service to and from the 3G cells checked OK
Soft handover for PS service to and from the 3G cells checked OK
DT Check Items- Typical Example

Page 11
General
Confirm Site is on -air and no alarm on site.
Check with Neighbor Relation table
Check R99 (Voice, VP 5 call sampling in each sector)
Check HSPA (5 calls in each sector)
Check cell reselection (2G to 3G and vice versa)
Dedicated Mode
Call from BL to BL (both incoming and outgoing)
Call from BL to other operators

(both incoming and outgoing)
Inter system HO (3G to 2G)
Voice Quality
Test Handover to first neighbor ( both incoming and outgoing)

Silent call
Category Checks
Check
Comm
ent
(OK/
NOK/NA)
Types of SSV DT

Page 12
In 3G DT, we have to perform two types of test
Statistic Test: In static Drive test, we have to go one by one in each sector around
100m & we choose better Level(RSCP & Ec/Io),after that we start static test. Static Test
Means without moving in sector we have to do our work.

Dynamic Test/Moving Test: In the dynamic drive test we have to move the each
sector with Genex Probe connect and record its values of RSCP & Ec/No. The Value of
RSCP & Ec/No should be good. In dynamic Drive test we have to test Coverage, quality
and Handovers of all the sectors in Long call. Long Call:- Long call means continuous
call on testing number.

DT KPI

Page 13
CLASSES INDICATORS SERVICES Minimum accepted value
Data
Performance
PS DL throughput
in R99 for FTP
Transfers
R99 Data Services
(Measured on Application Level)
Average throughput = 80% of the RAB capacity for all RABs
PS UL throughput
in R99 for FTP
Transfers
R99 Data Services
Average throughput = 80% of the RAB capacity for all RABs
PS DL FTP
Throughput for
HSDPA (UE
Category. 6, 10 ,
20) (FTP); TCP,
window size =
256k
Category 20
HSDPA 21.1 Mbps (Measured on
Application Level)
Site Acceptance Throughput:
Avg. throughput > 14Mbps & Peak throughput >=16 Mbps.The
stationary UE is near the antenna (CQI >=27); 2.MTU=1500;TCP
receive window size>256KB;file size=200MB.
Category 20
HSUPA 5.8 Mbps (Measured on
Application Level)
Site Acceptance Throughput:
Avg. throughput > 3.6Mbps & Peak throughput >=4 Mbps.The
stationary UE is near the antenna (CQI >=27); 2.MTU=1500;TCP
receive window size>128KB;file size=50MB.
Successful
Completion rate
R99 & HSDPA
The rate of 3G services successfully completed should exceed 90%
of total number of calls = 30 call
Drive Test Tools
UE1/MS1-Huawei U6100
UE4-Huawei E372u
DT software- Genex Probe: V200R300C02SPC400 or upper
version.
Car GPS.

Page 14
DT Tools Connection Procedure

Page 15
Connect the USB cables to the Huawei test phones. Connect the other end of
the USB cables to USB ports on the laptop.
Connect the GPS and Huawei Data Card for HSPA to the laptop, either via USB
or via serial port. Insert the Dongle into a USB port. Note: If the laptop does not
have a sufficient number of USB cables then a 1x4 USB multiplexer may be
used. Switch on the laptop and open Genex Probe V200R300SPC400 or upper
version.
Open WCDMA view template from project and press F8 for displaying Device
configure window as bellow and configure all MS,GPS and Data card.


Page 16
GPS,MS & Data
Card
Configuration

Page 17
All configured device
are ready to be
connect.Red
marked Symbol
means not
connected

Page 18
Connect MS,GPS and
Data card until all red
color symbol turned to
GreenGreen color
symbol means devices
are connected and ready
to start drive test.
Now you
are ready
for DT.

Page 19
For SSV DT we use three(3) Huawei MS and one Huawei Data Card for following
purpose
Keep MS1/UE1- Idle Mode( PSC and DL UARFCN Locked for checking
coverage).
Keep MS2/UE2-Idle Mode (UMTS Locked for checking cell re/selection and
RSCP,URA,LAC etc.)
Keep MS3/UE-3 (Auto Mode for checking all type of Mobile Originating
call(short call/long call) for both voice and video, all types of
handover(soft/softer and I-RAT) checking and R99 throughput checking etc).
UE4/Data card will use for HSDPA /HSUPA throughput checking.
N.B: During MOC and MTC test, MS3 always used as a MO terminal and MS2 as
a MT terminal.

Check List Checking Process from SSV DT
1. Before starting the test, we have to lock the frequency which we want to test form Test
+ Forcing Function + WCDMA forcing features as follows(bellow left side snapshot).
2. After reaching the site we try to test the stationary test within 100m of every sector of
the site. For stationary test in idle we record a log file by Pressing f5 and check the
PSC, cell ID and other parameter in Basic Information window of Genex probe for
MS2(bellow right side snapshot)

Page 20
3. After that we collect a log for cell selection and reselection in idle mode by moving
clockwise and anticlockwise of the site. Cell selection-reselection command shows in
the signaling tab into event list window(bellow left side snapshot).
4. After completing the stationary test we start the connection test for MS3. For MOC and
MTC we use MS3 for MOC and MS2 for MTC for Voice call. In connection we check the
RSCP, Ec/Io from basic window into Active set. We can see the UL power from the
Power control window form basic information(bellow right side snapshot)

Page 21
5. Then we check the Video call for the sector by generating calls from MS3 to MS2.
6. After completing Connection Test we start the throughput test.
7. In throughput test we use the Data card and mobile which are connected as MS4 and
MS3.
8. In HSDPA and HSUPA test we use Data card which is connected as MS4. For HSDPA we
download a file from given server and check the speed from Net per second or RLP
throughput window. RLP throughput window can found form view + WCDMA + RLP
throughput(bellow left side snapshot).
9. For HSUPA we upload a file to the given server(bellow right side snapshot).

Page 22
10. The R99 test is performed by MS3. In MS3 we download a file from given server. And
the server is 202.4.173.18. User Name and Password of the server to download the file is
same and it is ftpuser. We can check the speed of R99 from the bellow snapshot.

Page 23

11. For checking Irat handover of CS and cell reselection from 2G cell to 3G cell in packet
mode of PS are performed by MS3, MS1. In this test we set the mobile network in Auto
MODE to check the 3G to 2G Handover in MS3(check from bellow left side snapshot).
12. For cell reselection in CS mode and 3G to 2G and 2G to 3G we perform it Automatically
by MS2 (check it from right side snapshot).

13. In Cell reselection test in PS mode, first we have to connect internet by the dialup then
we can check this test by browsing.

Page 24

14. After completing those tests we perform the mobility test. In mobility test MS2 is in idle
mode MS3 in dedicated mode, MS1 is in PS mode. In MS1 we download a file from the
given server. In this test we try to cover the entire possible road in that particular site
15. In mobility test, we check also the soft and softer handover for the particular site for both
CS and PS mode.
16. After completing all the functionality test, we have to perform coverage test by locking
PSC and 1st carrier frequency of particular sector and drive until sector RSCP <=-
105dBm.

Page 25
Useful Plots
Server plots: useful to find out feeder swap or overshooting.
RSCP Plot: To check out coverage hole.
UE/MS plot: To check out Neighbor relation.
Ec/Io Plot: To check out good throughput and pilot pollution area.

Page 26
Figure: PSC Plot. Figure: RSCP Plot.
Figure: Ec/Io Plot.
Analysis & Troubleshooting

Page 27
The post-analyze engineer needs to analyze and record the problems, troubleshoot and
output the SSV report according to the template.
When abnormal events happen during testing a site, the test & analysis engineer has to
analyze the issue, give a recommendation and record all of it. After the
recommendation is approved by the expert and implemented, the SSV engineer has do
verify that site again.

Most of the problems in SSV phase are related to installation and parameter problems,
so RF Engineer has to distinguish the problems and send the solution to different
teams, apart from monitoring the troubleshooting progress. It is recommended to
propose that installation team prepares one team to be dedicated to troubleshoot SSV.
A SSV Record Table is required to record all the SSV actions, including problems, test
times, test date and by the SSV control table it is easy to get progress statistics.

Common Problem & Solution in 3G SSV DT
Problem Symptom
1. Scrambling code setting is wrong: The scrambling found from MS is different than
planned.
2. Feeder swap: CPICH RSCP is 20dB lower then before.
1.Solution for wrong SC
The scrambling code may be wrong in RNC,check the RNC datasheet.
The scrambling code from MS is the same of another sector of same site planned,may
be the Tx/Rx feeder is crossed to the another sector.
2.Solution for Feeder Swap
Need to check the connection between feeder and antennas.

Page 28
Report Generation

Page 29
Once the test result is acceptable and problems are solved, generate the SSV Report.
Report format will be as per operator demand.
Common Problem & Solution in 3G SSV DT
Test Process of Swapping Check
Items: Antenna Swapping Test.
Purpose: To verify the Rx feeder installation is right.
Method: Switch the Transmitter form one feeder to another, Check the RSCP changed
or not. If no change happened, its means that the feeder is correct.

Page 30
A
n
t
e
n
n
a
-
A

A
n
t
e
n
n
a
-
B

A
n
t
e
n
n
a
-
A

A
n
t
e
n
n
a
-
B

Sector_A Sector_B
Sector_A Sector_B
T
x
/
R
x

T
x
/
R
x

R
x

T
x
/
R
x

R
x

R
x

Right Wrong

Page 31
Thank You
www.huawei.com

3G SSV DT Purpose Process

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

3G SSV DT Purpose Process

Enviado por

Direitos autorais:

Formatos disponíveis

HUAWEI TECHNOLOGIES CO., LTD.

Você também pode gostar