Professional Documents
Culture Documents
Rahul Rode
NPD GTL
j
ë INTRODUCTION
ë NETWORK PROBLEM IDENTIFICATION
ë REQUIREMENT FOR DRIVE TESTING
ë DRIVE TEST PROCESS
ë DRIVE TEST OUTPUTS
ë MEASUREMENT METRICS
ë DRIVE TEST ANALYSIS
j
Every alive Network needs to be under continues control to maintain/improve
The performance. Drive test is basically the only way to keep track of the n/w
By looking deep into collecting & analyzing drive test data.
Drive testing is the most common and maybe the best way to analyze Network
Performance by means of coverage evaluation, system availability, Networks
Capacity, networks retainability and call quality. Although it gives idea only on
Downlink side of the process.
The drive testing is basically collecting measurement data with a TEMS phone,
But the main concern is the analysis and evaluation part that is done after
Completion of the test.
Remember that you are always asked to perform a drive test for not only showing
The problem, but also explaining them and providing useful recommendations to
Correct them.
ë Drive Test
ë OMC Statistics
ë Customer feedback
ë Test the network from the subscribers point of view
ë Test the complete system, end-to-end (mobile-to-land)
ë Benchmark performance against competitor networks
ë Test specific important routes and areas
ë Test in-building coverage for specific buildings (walk test)
ë Problems reported by statistical analysis, routine drive testing,
customer care centre , etc
Vehicle
Drive test mobile phone
External vehicle mounted GPS
Laptop with drive test software and GPS connection
capability
j
For a typical metro city, at least 1000 calls required for good
statistical confidence
ë Routine Voice call drive test, short call & long Call.
ë Data Drive.
ë MMS , SMS Drive test.
ë Comparative Drive.
ë Problem specific drive test
ë Cell coverage analysis drive test.
ë Walk test.
ë Network is monitored on a regular basis
ë Drive test routes to include all the major roads, important locations,
etc
ë Routes regularly drive tested and problems further analyzed and
solved
ë May require removing interfering carrier, Power Change to
BTS, Frequency Plan change, Neighbor addition , etc.
ë Problems reported by statistical analysis, routine drive testing,
customer care centre , etc
ë Scan feature
Status Information
General Information: Includes Latitude & longitude, server
cell name, date, time , log file name etc
Serving cell: Includes Cell Identity, BSIC, ARFCN ,MCC,
MNC, LAC
Serving + Neighbor cell data: Includes CI, BSIC, ARFCN,
Rxlev
Dedicated channel:Includes Channel number, Timeslot
number, Channel type, hopping information
Radio Environment: Includes serving cell, Rx_Lev, Rx_Qual,
TA, DTX and RL Timeout counter information
ë 2
RxLev Full
RxLev Sub
RxQual Full
RxQual Sub
C/I
BCCH
ë a
Call Drops
Setup Failures
HO Failures
HO Success
ë Coverage Analysis: Level Analysis
Quality Analysis
ë |
o Time
2 ell name
3 GI
!
"#"$ "
%& '''
()%)*"# # +
%& ''(',*$ $
%-.//0/(/1%1*
%& .//0/(11%%1*
jj
ë ½ode
""|2+
ë Time slot:
9
4=
3>
jj
$+798|98,?
98, 798986?6 986
? 986
ë hannel ½ode
+
6393
ë 63 63"93
9363
63
ë iphering Algorithm
/8<
ë Sub hannel Number
|9
|9
, <
jj
ë RxLev : 3
7
3
-
0%7-11%7
ë RxQual @
733
3A@%-;
ë FER 6 3
-
!
+
ë ¦ER Actual 3
73
!
+|
733A@ ""73%%<
B
3A@%A73
1<,B
3A@A;
ë DTX : |
(|>*
"
"
+
ë TA 4
(*
7
4%
//%6 7
ë DTX : |
(|>*
"
"
+
ë ¦SI 7
ë RxLev 3
$
7
ë o & 2
4
ë 3o & 32 23
01
23
+
0<4
+
+
o
Found in another direction means planned orientation is 1st 70, 2nd 170, 3rd 340,
we found 1st 170, 2nd 70, 3rd 240, in sector swap also we found cyclic swap, in
Combiner
Multi coupler
Duplexer
TRX
iia
i2i
aii
¦
13
:
<3
0$
)
/ E
9
<F
1
<
1 E
4 2
<
06E
2
7 | +
1
< E
1 7
$
<
E
| +
1 E
SI ± 808 WALUJ½IDIDU ¦S3WLJ
3 3 :-
!
" #
SI ± 808 WALUJ½IDIDU ¦S3WLJ RX LEVEL GRID = 200 M
i! $2 !
2
2
%i
$ %i
SI ± 808 WALUJ½IDIDU ¦S3WLJ RX QUALT GRID = 200 M
SI ± 808 WALUJ½IDIDU oST SETOR ORIENTATION O0O
%& a2
i
aai
SI ± 808 WALUJ½IDIDU 2ND SETOR ORIENTATION o 0O
%& a2
i
aai
SI ± 808 WALUJ½IDIDU 3RD SETOR ORIENTATION 290O
%& a2
i
aai
SI ± ½G3528 ANPAIDF ¦