GSM Network Planning and Optimization Single Site Verification Work Guidebook V1 0

Internal Use Only
GSM Network Planning and Optimization

Single Site Verification
Work Guideook
Version: V1.0
!eleased y GSM Network Planning and Optimization
"epartment of #ngineering Ser$ice "i$ision of %&#
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
GSM Network Planning and Optimization Work
Guideook
Version introduction'
Version ate !riter "ssessor Translator "mendment records
V1.0 #00$%0&%
#1
'iang (i Chang
)ai*ie+ (u
,iyun+ -u
-haoli
,u (an This document clarifies its
relationship with another
document named Hand-over
Standard of Project Installation
and Test of BSS and Network
Optimization in aspect of
general .erification part. /t
emphasi0es that the .erification
items can be ad*usted according
to the results of pro*ect 1uality
examination.

Internal Use Only
Key words:
2-34 single site .erification4 T4 C5T
Abstract:
This document introduces the tas6s of single site .erification+ including the general test
flow for single site .erification+ preparations for test+ purposes for different test items+
test methods+ and methods for problem analysis and problem handling. 7esides+ this
document also pro.ides the standard for single site .erification and the fre1uently%used
templates for a .erification report.
Abbreviations:
--V -ingle -ite Verification
Tri.e Test
C5TCall 5uality Test
8x,e.8ecei.e ,e.el
8x5ual8ecei.e 5uality
References:
Hand-over Standard of Project Installation and Test of BSS and Network Optimization
GSM P O !adio Network Test "ork G#ide$ook
GSM PO %rossed &ntenna %onnection Sol#tions
GSM PO Network Speec' (#alit) Pro$lems Sol#tions
*+,GP!S !adio Network Optimization "ork G#ide$ook

Internal Use Only
(ontents
)igure *+* &,e position of single site $erification in t,e w,ole pro-ect .////////////////////////////////////////////IV
)igure *+. &,e outline of t,is document .////////////////////////////////////////////////////////////////////////////////////////////////IV
)igure .+0 &,e workflow of single site $erification 1///////////////////////////////////////////////////////////////////////////////IV
)igure 0+1 2 figure of test routes for site $erification in uran areas 3/////////////////////////////////////////////////IV
)igure 0+4 2 figure of test routes for site $erification in suuran areas *5/////////////////////////////////////////IV
)igure 1+6 (,eck t,e asic network parameters of t,e site t,roug, system message 0 *1/////////////////IV
)igure 1+7 (,eck t,e (2 list of t,e cell t,roug, system messge * *4////////////////////////////////////////////////////IV
)igure 1+8 &est results of re$ersely connected sector of t,e site *7////////////////////////////////////////////////////////IV
)igure 1+3 &est results of re$ersely connected &(9 antenna *8////////////////////////////////////////////////////////////IV
&ale 0+* (alling met,ods w,ic, are fre:uently used y (S ser$ice 7/////////////////////////////////////////////////IV
&ale 1+. &,e most common items of GSM single site $erification *.//////////////////////////////////////////////////IV
&ale 1+0 Static power le$el parameters ..//////////////////////////////////////////////////////////////////////////////////////////////IV
&ale 4+1 2cceptance standards for t,e most familiar c,eck items 05//////////////////////////////////////////////////IV
* O$er$iew /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// *
1.1 Terminologies and definitions ............................................................................................................... 1
1.# The significance of single site .erification ........................................................................................... 1
1.9 :utline ................................................................................................................................................... #
. &,e workflow of single site $erification ///////////////////////////////////////////////////////////////////////////////////////////////////// 1
#.1 !or6flow ............................................................................................................................................... ;
#.# Explanations of the wor6flow ............................................................................................................... ;
0 Preparation work for single site $erification //////////////////////////////////////////////////////////////////////////////////////////// 6
9.1 <reparation of tools ............................................................................................................................... =
9.# efine the test methods and test routes ................................................................................................. &
9.#.1 efine test methods ..................................................................................................................... &
except in accordance with applicable agreements. I

Internal Use Only
9.#.# The definition of test routes ........................................................................................................ >
9.#.9 :ther preparations ..................................................................................................................... 10
9.9 Chec6 the configuration of parameters ............................................................................................... 10
9.; Chec6 the site status ............................................................................................................................ 11
1 Verification test and analysis //////////////////////////////////////////////////////////////////////////////////////////////////////////////////// *.
;.1 7asic .erification ................................................................................................................................. 19
;.1.1 <urposes of the .erification ....................................................................................................... 19
;.1.# Verification methods ................................................................................................................. 19
;.1.9 3ethods of problem analysis and problem sol.ing .................................................................. 1?
;.# "ntenna and feeder .erification .......................................................................................................... 1=
;.#.1 <urpose ...................................................................................................................................... 1=
;.#.# Verification methods ................................................................................................................. 1=
;.#.9 3ethods of problem analysis and problem sol.ing .................................................................. 1=
;.9 Verification of call completion between the calling side and the called side ..................................... 1>
;.9.1 <urpose ...................................................................................................................................... 1>
;.9.# Verification methods ................................................................................................................. 1$
;.9.9 3ethods of problem analysis and problem sol.ing .................................................................. 1$
;.; Verification of recei.ed signal le.el .................................................................................................... #1
;.;.1 <urpose ...................................................................................................................................... #1
;.;.# Verification methods ................................................................................................................. #1
;.;.9 3ethods of problem analysis and problem sol.ing .................................................................. ##
;.? Verification of reception 1uality .......................................................................................................... #9
;.?.1 <urpose ...................................................................................................................................... #9
;.?.# Verification methods ................................................................................................................. #9
;.?.9 3ethods of problem analysis and problem sol.ing .................................................................. #;
;.= Verification of hando.er ...................................................................................................................... #?
;.=.1 <urpose ...................................................................................................................................... #?
;.=.# Verification methods ................................................................................................................. #?
;.=.9 3ethods of problem analysis and problem sol.ing .................................................................. #=
;.& Verification of <- ser.ice .................................................................................................................... #&
;.&.1 <urpose ...................................................................................................................................... #&
except in accordance with applicable agreements. II

Internal Use Only
;.&.# Verification methods ................................................................................................................. #&
;.&.9 3ethods of problem analysis and problem sol.ing .................................................................. #>
4 2cceptance standard for single site $erification ///////////////////////////////////////////////////////////////////////////////////// 05
6 2 single site $erification report ///////////////////////////////////////////////////////////////////////////////////////////////////////////////// 0.
except in accordance with applicable agreements. III

Internal Use Only
)igure contents
)igure *+* &,e position of single site $erification in t,e w,ole pro-ect////////////////////////////////////////////////////.
)igure *+. &,e outline of t,is document////////////////////////////////////////////////////////////////////////////////////////////////////////.
)igure .+0 &,e workflow of single site $erification//////////////////////////////////////////////////////////////////////////////////////1
)igure 0+1 2 figure of test routes for site $erification in uran areas////////////////////////////////////////////////////////3
)igure 0+4 2 figure of test routes for site $erification in suuran areas////////////////////////////////////////////////*5
)igure 1+6 (,eck t,e asic network parameters of t,e site t,roug, system message 0////////////////////////*1
)igure 1+7 (,eck t,e (2 list of t,e cell t,roug, system messge *///////////////////////////////////////////////////////////*4
)igure 1+8 &est results of re$ersely connected sector of t,e site///////////////////////////////////////////////////////////////*7
)igure 1+3 &est results of re$ersely connected &(9 antenna////////////////////////////////////////////////////////////////////*8
&ale contents
&ale 0+* (alling met,ods w,ic, are fre:uently used y (S ser$ice/////////////////////////////////////////////////////////7
&ale 1+. &,e most common items of GSM single site $erification//////////////////////////////////////////////////////////*.
&ale 1+0 Static power le$el parameters//////////////////////////////////////////////////////////////////////////////////////////////////////..
&ale 4+1 2cceptance standards for t,e most familiar c,eck items//////////////////////////////////////////////////////////05
except in accordance with applicable agreements. IV

Internal Use Only
1 Overview
1.1 Terminologies and definitions
-ingle site .erification in.ol.es with the test and .erification of single site e1uipment
functions. The purpose is to ensure that the basic functions and radio performance of
each cell under the single site are at a normal operation state.
@sually+ the networ6 test enginner is in charge of single site .erification. The tas6 is to
.erify some basic functions of the testing cells through T and C5T+ including
co.erage+ access+ calls+ and data downloading+ and so on. /f the functions of a site
perform well+ there will be a single site .erification report+ which means an end of
.erification. /f a site has some problems+ efforts should be made to analy0e the
problems and to ma6e some ad*ustments. Then+ there will be a .erification report when
the functions perform well.
1.2 The significance of single site verification
-ingle site .erification is at the first stage of networ6 optimi0ation for pro*ects li6e new
radio networ6 construction+ networ6 capacity expansion+ and networ6 swap. Through
single site .erification+ it is possible to identify a series of ob.ious radio networ6
problems li6e access problems+ call drops+ and so on+ which are caused by e1uipment
performance or co.erage problems. The purpose is to ensure that each site which has a
formal access to the networ6 can ha.e good ser.ice performance and to a.oid drastic
networ6 1uality fluctuations when a new networ6 is constructed or the networ6
capacity is expanded.
-ingle site .erification can help a networ6 optimi0ation engineer to familiari0e himself
with some information in the area+ for example+ radio en.ironment+ site distance+ and
so on+ which lays a solid foundation for cluster optimi0ation in the future.
The position of single site .erification in the whole pro*ect is shown in figure 1%1.
-ingle site .erification follows the stage of single site commissioning testAchec6. !hen
is is confirmed that each cell in the area has completed its single site .erification+ the
single site .erification of the area is completed+ and it is time to mo.e to the next stage+
that is+ cluster optimi0ation.
except in accordance with applicable agreements. 1

Internal Use Only
Bigure 1-1 The position of single site .erification in the whole pro*ect
7esides+ since single site .erification is the start of networ6 optimi0ation+ it should be
ensured that the single site pro*ectAcommissioning test stage has been successfully
completed and there are no ob.ious problems left. The purpose for this confirmation is
to ma6e sure that single site .erification can be smoothly carried out.
Bor details of pro*ect optimi0ation ta6e%o.er+ please refer to a guideboo6 called Hand-
over Standard of Project Installation and Test of BSS and Network Optimization.
1.3 Outline
The outline of this document is shown as follows:
Bigure 1-2 The outline of this document
Chapter # clarifies the wor6flow of single site .erification. 7esides+ it explains tas6s
for different procedures+ including preparations for the .erification+ .erification test+
and .erification criteria and so on.
Chapter 9 introduces the preparation wor6 for single site .erification.

Internal Use Only
Chapter ; introduces the common .erification items+ and it also clarifies what the
tesing methods are li6e and how the problems which occur during test are analy0ed.
Chapter ?+ = introduces respecti.ely the common criteria of test acceptance and the
output of a .erification report+ which are rele.ant to pro*ect .erification.
The contents of the appendixes are as follows:
The appendixes consist of two parts: The first part is an existing template for
.erification report+ which can be used at the wor6 field to write a report4 the second
part introduces TE3- .erification test+ which is a fre1uently%used software+ and
:3C8 data analysis guidance.

Internal Use Only
2 The worflow of single site verification
2.1 !orflow
Bigure 2-3 The wor6flow of single site .erification
2.2 "#$lanations of the worflow
7efore the networ6 optimi0ation team starts to do the single site .erification+ it should

Internal Use Only
be ensured that pro*ect installation+ and commissioning test ha.e been completed+ and
:3C8 has shown that site e1uipment wor6s properly.
<reparation wor6 for single site .erification
<repare tools: 3a6e sure that the test software and test e1uipment wor6 properly.
efine test methods: 3a6e it clear to the client about test methods and tas6s. Bor
example+ ma6e it clear which test methods will be used together C/dle D long call D <-E+
and clarify the details.
efine test routes: 3a6e clear the test routes for sites on basis of different scenarios.
Chec6 parameter configuration and confirm site status: Chec6 site parameters and
confirm site status to ensure that the basic data at :3C8 is configured correctly+ the
site wor6s properly+ and there are no ob.ious alarms.
-ingle site .erification
-ingle site .erification is mainly completed through C5T+ and T. The important thing
is that it should be ensured that before the specific test no ob.ious problems appear in
the basic .erification and antenna and feeder .erification. :therwise+ a series of
following tests will be meaningless.
3a6e an analysis to chec6 whether it meets the single site .erification
re1uirements or not.
3a6e a statistical analysis of the .erification test at :3C8 in relation to the items and
functions which need to be .erified. The *udgment should be based on the re1uirements
of the client. /f the .erification meets the re1uirements+ a .erification report can be
produced. :therwise+ an analysis should be made about the problems which appear in
the .erification+ and an ad*ustment wor6 order should be produced.
<roduce a single site .erification report
/f the site .erification shows that all the re1uirements are satisfied+ a .erification report
should be produced as re1uired.

Internal Use Only
3 %re$aration wor for single site
verification
3.1 %re$aration of tools
-ingle site .erification is mainly completed through tests. Therefore+ before the
.erification starts+ it is necessary to communicate with the client about the .erification
methods+ including the testing system and tools to be chosen.
3a6e clear the testing system and testing handset
The fre1uently%used testing systems include TE3-+ <ilot <ioneer+ Femo+ and so on. "t
the same time+ it is necessary to ma6e clear what 6ind of testing handset will be used
and how many testing handsets are needed for each testing system Cit depends on the
testing methodE. The most fre1uently%used testing handsets include -agem+ -ony
Ercssion+ and Fo6ia. !hatGs important is that if <- .erification is re1uired by the
client+ it should be confirmed whether the 3- used supports E2E ser.ice or whether
the 3- multi%timeslots ability can satisfy the acceptance standard for <- downloading.
Bor example+ upon the .erification+ it is re1uested that the fixed point downloading rate
shoud be higher than 100Hpbs CI100HpbsE+ then the terminal used must support E2E
ser.ice and ;1 multi%timeslot ability at least.

3a6e clear which :3C8 software will be used to analy0e the test data
7esides+ if it is re1uired to create some statistical graph or geographical graph in the
single site .erification report+ it should be clear which bac6ground analysis software
will be used to import the testing log and to analy0e the data+ and which color code will
be used+ and so on.
Bor the preparation of some specific tool+ please refer to -ser Man#al or the guideboo6
for test tools. /n this document+ "ppendix Error: 8eference source not found clarifies
the specifications of TE3- .erification test and :3C8 analysis for reference.
The fre1uently%used guideboo6s of test tools are as follows:
& G#ide$ook for How to -se T+MS to %'eck %S Service

Internal Use Only
& G#ide$ook for How to -se T+MS to %'eck E2<8- Service
& G#ide$ook for %.S *+,GP!S Test from GSM Network Plannin/ and Optimization
.epartment
3.2 &efine the test methods and test routes
3.2.1 &efine test methods
7efore the single site .erification starts+ it is necessary to communicate with the client
and ma6e clear the test methods. The test methods mainly in.ol.e with the following
parts:
Calling methods adopted by C- ser.ice
@sually+ a combination of two calling methods will be adopted for the test+ for
example+ /dle D short call+ /dle D long call+ or /dle D short call D long call. Each
test method has different emphases. Bor details+ please refer to table Table 9%1:
Table 9%1 Calling methods which are fre1uently used by C- ser.ice
Test methods <urposes
/dle /t is used to record the networ6 condition at idle state and
the le.el and CA/ on 7CC)
-hort call /t is mainly used for testing the accessibility and mobility
of networ6.
,ong call /t is mainly used to test the retainability and mobility of
networ6.
Bor short calls+ it is necessary to confirm some information with the client+
including the length of a short call+ the inter.al between two short calls+ and the
length of waiting time when a call is originated abnormally or a call drop
occurs.
Bor short calls or /dle state+ it is necessary to confirm whether the test is based
on fixed 7CC).
Test methods for <- ser.ice
/f E2<8- ser.ice is commissioned for a networ6+ <- ser.ice performance test
should be done upon site .erification. The most common test items include
attach+ << acti.ation+ BT< downloadAupload+ ping test+ and so on.

Internal Use Only
7esides+ other information should also be confirmed+ including whether it is
fixed point test or dri.e test+ whether 2<8- ser.ice test and E2E ser.ice test
should be carried out independently+ what the si0e of document downloaded or
uploaded by BT<+ which protocol will be used C"<<+ ,,C+ 8,CE as the
acceptance standard of throughput.
3.2.2 The definition of test routes
The choice of test routes .aries with different scenarios of site .erification. The test
scenarios are usually di.ided into two categories+ that is+ urban areas and suburban
areas. This classification is based on distribution density of sites and the surrounding
radio en.ironment.
@rban areas
@sually+ urban sites refer to dense urban sitesAmean urban sites. The a.erage site
distance of the surrounding sites is among the range of 900m%1000m Cit depends on
different networ6 en.ironmentE. The main features of test routes in urban areas are as
follows:
a. The test routes should co.er the roads which are co.ered by different
sectors of the sites to be tested. 7esides+ the main streets around the base
stations should also be included.
b. The test routes should reach the areas co.ered by cells which are around
the base stations to be tested so as to ensure that the actual co.erage area
of the site and its hando.er functions can be .erified.
c. The design of test routes should ta6e into consideration the local customes
of tra.el so as to reduce the waiting time at traffic lights.
Bigure Bigure 9%; shows a classic test routes for single site .erification in urban areas:

Internal Use Only
Bigure 9%; " figure of test routes for site .erification in urban areas
-uburban areas
Formally+ suburban sites refer to suburban sitesArural sites. The a.erage site distance of
the surrounding sites is among the range of 1?Hm+ and there are only wide roads
around. The main features of test routes in surburban areas are as follows:
a. The test routes should co.er the roads which are co.ered by different
sectors of the sites to be tested.
b. The test routes should reach the o.erlapping areas of surrounding neighbor
cells so as to ensure that the actual co.erage area of the site and its
hando.er functions can be .erified.
c. Bor isolated sites+ the normal co.erage area of the site should be got
through the test.
Bigure Bigure 9%? shows a classic test routes for single site .erification in suburban
areas:

Internal Use Only
Bigure 9%? " figure of test routes for site .erification in suburban areas
3.2.3 Other $re$arations
7esides+ it is necessary to confirm the following items with the client:
2et the customi0ed -/3 card for test from the client.
/f <- ser.ice needs to be .erified in single site .erification+ it should be ensured
that the /< address+ user name+ and pass word of ftp se.er are got.
2et the digital map which is in form of 3ap/nfo.
3.3 'hec the configuration of $arameters
7efore the site .erification+ engineers responsible for single site .erification need to
chec6 the configuration of :3C parameters of the site to be tested. The purpose is to
a.oid the possible .erification failure cuased by incorrect data configuration.
The chec6 of parameters can be 1uite flexible. :ne method is to export the
configuration table of radio parameters through :3C8 and compare it with the
planning data. :r the parameters can be chec6ed directly at :3C8.
@sually+ the chec6 of parameters includes but is not limited to the following items:
1. Bor basic networ6 parameters+ it should be chec6ed whether 3FC+ 3CC+ ,"C+
8"C+ C/+ 7CC)+ FCC+ 7CC are configured according the planning.
#. /t should be chec6ed whether the site configuration is correct and whether the
number of carrier fre1uency of each cell is the same as that in the planning.

Internal Use Only
9. /t should be chec6ed whether the fre1uency points of each cellGs 7CC)+ and TC)
are configures as planned. /f fre1uency hopping is configured for TC)+ the
parameters related to fre1uency hopping should be chec6ed+ including 3"+
3"/:+ )-F+ and so on. 7esides+ it should be confirmed whether T-C of each
channel is in consistent with 7CC.
;. /t should be chec6ed whether the neighbor cells of each cell are configured as
planned+ and whether the definition of external neighbor cells is correct.
?. /t should be chec6ed whether the channels of each cell are configured as planned+
especially the number of -CC) channels+ the 1uantity and locations of <C)
channels.
=. :ther networ6 parameters should also be chec6ed+ including the minimum access
le.el+ whether C# algorithm is enabled or not+ TJ+ and so on. The chec6 should
follow the template of site planning of radio parameters.
3.( 'hec the site status
Binally+ before the single site .erification+ the site status should also be chec6ed so as to
ensure that the site wor6s properly.
1 /t should be confirmed whether the pro*ect commissioning is completed+ and
whether the single site .erification is completed. The single site .erification is
carried out by engineers responsible for single site .erification. The main tas6 is
to do call 1uality test. Through the single site .erification+ it can be ensured that
the site can pro.ide the basic call ser.ice.
# :3C8 alarms should be chec6ed+ including the current alarms+ and history
alarms. /f the following alarms exit+ it is necessary to communicate with 7--
engineers to manage to sol.e the problems before the .erification test starts:
7ro6en lin6 of ,"<+ bro6en lin6 of T8J+ T8J hardware alarms+ transmission
alarms+ V-!8 alarms+ cloc6 alarms+ and so on.
9 7efore the .erification+ it is necessary to chec6 the basic H</ of base station
through :3C8. The purpose is to ensure that the a.ailability ratio of -CC)+
and TC) is at a normal state+ and that some traffic already exists.

Internal Use Only
( )erification test and analysis
-ingle site .erification usually consists of the following items: 7asic .erification+
.erification of antenna and feeder connection+ downlin6 co.erage le.el+ downlin6 call
1uality+ call functions+ hando.er functions+ and <- ser.ice+ and so on.
uring the process of .erification test+ some abnormal phenomena need special
attention. Bor example+ originating call failure+ hando.er failure+ call drop+ poor .oice
1uality+ and so on. These e.ents may probably reflect all 6inds of networ6 problems
behind. Bor those ob.ious abnormal e.ents+ it is suggested that they should be analy0ed
carefully+ and be sol.ed at the phase of single site .erification if possible.
7esides+ single site .erification items may .ary with different 6inds of pro*ects. Bor
example+ the single site .erification for a swap pro*ect should compare items li6e
co.erage and 1uality before and after the swap.
Table ;%# shows the most common single site .erification items.
Table ;%# The most common items of 2-3 single site .erification
Verification items <urposes Compulsory
or optional
7asic .erificaiton Verification of site engineering parameters
Clongitude and latitude+ antenna height+ and so onE
Verification of 6ey radio parameters in system
messages at idle state
Compulsory
.erification of
antenna and feeder
connection
To confirm whether the co.erage direction of 7CC)
is the same as planned.
To chec6 whether 7CC)+ TC) antennas are
connected in a re.erse way.
Compulsory
Verification of the
calling and the called
function
To .erify the calling and the called functions to see
whether there are calling or called failures.
Compulsory
Verificaiton of
recei.ed signal le.el
To chec6 whether the downlin6 co.erage le.el is
normal and whether the co.erage area is normal.
Compulsory
Verification of
recei.ed signal 1uality
To chec6 whether the downlin6 call 1uality is normal
and whether inside networ6 interference exists.
Compulsory
Verificaiton of
hando.er functions
To chec6 whether the hando.er functions and
neighbor cell data are reasonable.
Compulsory

Internal Use Only
To chec6 the uplin6 recei.ed signal le.el and 1uality.
Verification of <-
ser.ice
To .erify "ttach+ << acti.ation
To .erify BT< download and upload
:ptional
(.1 *asic verification
Fote
"ccording to the re1uirements in the document named Take-over Proced#res from
Project Installation and %ommissionin/ of BSS Side to Network Optimization+
engineering parameter .erification+ C5T+ antenna and feeder chec6+ and so on should
be done before the optimi0ation so as to ensure that the site wor6s properly. /n
consideration of the fact that the 1uality of enginnering super.ision in some pro*ects is
not so high+ therefore some basic problems can not be excluded. /n other words+ at the
phase of single site .erification+ the basic engineering parameters+ radio parameters+
and antenna and feeder system should be .erified. Bor those pro*ects whose
engineering super.ision turns out to be 1uite good+ it is suggested that the basic
.erification can be simplified to some extent.
(.1.1 %ur$oses of the verification
The basic .erification starts as soon as engineers arri.e at the site which is to be
.erified. The purpose is to ensure that the basic engineering parameters and radio
parameters of site CcellsE are configured correctly. /f problems appear at the phase of
basic .erification+ they should be sol.ed first. :therwise+ the follow%up .erification
wor6 will be meaningless.
(.1.2 )erification methods
The .erification of engineering parameters includes the following items:
Chec6 whether the longitude and latitude of the site is correct. /f it is found that
the difference between the actual longitude and latitude of the site and the
planning data is more than 1003 CI1003E+ the longitude and latitude information
should be modified. 7esides+ the networ6 planning engineers should 6now the
modification.
Chec6 whether there is any ob.ious difference between the actual antenna height
and the planning data through eye measurement.

Internal Use Only
Chec6 whether antenna is shooting the air or there is no mechanical downtilt at all
C)owe.er+ according to the plan+ there should be mechanical downtilt.E.
&,e $erification of radio parameters mainly aims to chec6 whether the contents of
system messages of testing handset at idle state are the same as those of planning data.
The purpose of this tas6 is to ensure that the 6ey system parameters of :3C8 are
configured correctly. "t the same time+ it might be found that :3< data and :3C8
data of 7-C are not consistent. The parameters to be chec6ed are as follows:
Chec6 whether the basic networ6 parameters are configured correctly+ for
example+ 3FC+ 3CC+ ,"C+ 8"C+ C/+ 7CC)+ 7-/C+ "ccess3in+ C8:T9#1#+
and so on.
-ystem message 9 can be opened through the test system to confirm whether the
contents there are the same as those of planning data. The following figure shows
the specific contents of the message:
Bigure ;%= Chec6 the basic networ6 parameters of the site through system message 9
Chec6 whether C" list of the cell is configured correctly.
The C" list of the cell refers to all the fre1uency points configured on 7CC)s+
and TC)s+ which can be seen clearly in the descriptions of channels if system
messge 1 of test system is opened.

Internal Use Only
Bigure ;%& Chec6 the C" list of the cell through system messge 1
(.1.3 +ethods of $roblem analysis and $roblem solving
1. The main cause for engineering parameter problems is due to the fact that the
pro*ect installation and commissioning are not carried out according to T--8
reports. /f there are problems with longitude or latitude+ it may be due to the
possibility that the data of engineering in.estigation are not recorded correctly.
/f it is found that the longitude and latitude of the site are not correct+ it should
be confirmed that whether the site is the one to be .erified Cthrough C/ data of
the cellE. Then the longitude and latitude information of the site should be
confirmed with the planning staff. /f it is true that the information of longitude
and latitude is not correct+ it is suggested that the person responsible should tell
the planning staff the correct information+ and as6 them to update it.
/f there is a big difference between the actual antenna height and mechanical
downtilt and those of the planning data+ the problems should be reported to the
engineers to ma6e some corrections. The test should come after the corrections.
#. The main cause for wrong radio parameters is that the parameter configuration at
:3C8 is not correct. /f so+ the suggestion is that staff responsible for :3C8
e1uipment room should ma6e some modifications before the test can start. /n
some cases+ though it does not occur fre1uently+ it is because that :3< data are
not consist with :3C8 data. /n this case+ this problem should be reported to 7--
engineers so as to as6 them to chec6 :3< data and :3C8 data+ to reconfigure
the data+ and so on. :nly after that+ can the test start.

Internal Use Only
(.2 Antenna and feeder verification
(.2.1 %ur$ose
-ince the radio networ6 1uality is closely related to the antenna and feeder system+
antenna and feeder .erification is a necessary and fundamental part of site .erification.
/f the antenna downtilt is not correct+ there will be some ob.ious problems. :n the
other hand+ if the antenna and feeder is connected in a re.erse way+ there will be a
series of problems li6e call drop+ hando.er failure+ and poor .oice 1uality.
The actual co.erage direction of each cellGs antenna can be chec6ed with a
compass.
/mport the engineering parameters including cell a0imuth to the dri.e test
software+ that is+ the map.
/t should be ensured that there is at least one testing handset which is always at the
idle state so as to record the information on 7CC). !hene.er 3- enters the main
co.erage area of a sector+ the Cell / of the cell where 3- resides in should be
paid attention to. "t the same time+ it should be chec6ed whether the antenna
a0imuth is consistent with the Cell /.
/f the co.erage direction of each cellGs main lobe has a certain distance from the
site C100mE+ another handset should be used to do call 1uality test so as to manage
to occupy TC) carrier. /t should be chec6ed whether there is a dramatic drop of
downlin6 le.el when the handset occupies - channel and TC) channel during
the call.
"fter the dri.e test+ logfile should be imported to bac6ground anlysis software.
Then a thematic map will be produced on basis of 7CC) of the cell. !ith the
map+ it can be confirmed whether the Cell / of each cell is almost consistent
with the co.erage direction of a0imuth.
1. "ntenna a0imuth is wrong
uring the test process+ it can be confirmed whether the actual main lobe direction of
each cell is consistent with the planning data C7esides+ a thematic map of 7CC)

Internal Use Only
co.erage can help to *udge whether the Cell / of each cell is almost consistent with
the co.erage direction of a0imuth.E. /f there is an ob.ious difference+ CI90 degreesE+
and there is no sign that 7CC)s of the cell are connected in a re.erse way+ it means
that the direction of the antenna is not right.
/n this case+ the problem should be reported to the engineers so as to ma6e some
corrections.
#. "ntenna is connected in a re.erse way
/f an antenna is connected in a re.erse way+ the problem can still be further classified
into 9 categories. That is+ only 7CC) antenna is connected in a re.erse way+ only TC)
antenna is connected in a re.erse way+ or the whole sector is connected in a re.erse
way.
Bor re.ersely connected 7CC) antenna or re.ersely connected sector+ they can be
obser.ed through the special 7CC)%based map of the cell. "s shown in the following
figure+ there will be an o.erlapping area between the actual co.erage area and the
planning area in bothe cases.
Bigure ;%> Test results of re.ersely connected sector of the site
/f TC) antenna is connected re.ersely+ 7CC) signals and TC) signals of the same cell
will not appear in the same sector. /f 9A; of the carrier fre1uency is assigned to a
subscriber when he originates the call+ it can be seen that the le.el of occupied TC) is

Internal Use Only
lower than that of occupied 7CC) ob.iously. The le.el change during C5T will show
whether TC) antenna of the site is connected in a re.erse way. )ere is a picture:
Bigure ;%$ Test results of re.ersely connected TC) antenna
Bor detailed chec6 procedures+ please refer to GSM PO %rossed &ntenna %onnection
Sol#tions.
This 6ind of problems should be reported to the engineers so as to as6 them to do some
corrections.
Fote: -ince the basic .erification and antenna and feeder .erification are both
fundamental and necessary part of the whole procedures+ it is suggested that these two
.erification items shold be carried out before the follow%up specific .erification wor6.
The purpose is to a.oid unnecessary repetiti.e wor6.
(.3 )erification of call com$letion between the calling side and the
called side
(.3.1 %ur$ose
/n this .erification test+ the calling side will originate a call and the called side will go
through a call completion test. The purpose is to chec6 the call functions of the site
between the calling side and the called side+ call connection time+ and the 1uality of
speech Cmonologue+ call failure+ and cross tal6E.

Internal Use Only
C5T or T will be used to do the test. 7oth the handset of the calling side and the
handset of the called side will use the same dri.e test card. 7esides+ the handsets
will be used in the testing .ehicle to do the test.
@sually+ short call will be used for the test. /t is suggested that the call duration
should be 1? seconds+ and the call inter.al should be 10 seconds.
The calling side should originate calls repetiti.ely+ and the called side should
answer more than 10 calls. 7esides+ it is better that different TC) carrier
fre1uencie are occupied. uring the test+ the engineer responsible should listen
carefully to confirm whether there are problems li6e monologue+ 7idirectional
silence+ cross tal6+ and so on.
" statistical counting of a series of indicators+ li6e call success rate+ call setup
time+ and so on. -ome special e.ents should be paid attention to and their causes
should be analy0ed+ for example+ originating call failure+ congestion+ excessi.e
long call setup time+ and the li6e.
uring the call 1uality testing+ if some cell has ob.ious .oice problems+ for example+
monologue+ 7idirectional silence+ and cross tal6+ the following items should be
chec6ed:
1. Chec6 whether there are unbalanced uplin6Adownlin6 problems+ or se.ere
interferences4
#. Chec6 whether there are self%loop transmission lines4
9. Chec6 whether C/C codes of 3-C side and 7-C side match4
;. Chec6 whether there is something wrong with some time slot in the transmission
circuit4
?. Chec6 whether the configuration of time slots of the time%multiplexed e1uipment
is correct during shared E1 transmission4
=. Chec6 whether the problems are casued by 8TAE8T board failure or T/C board
failure4
Bor detailed chec6 procedures and methods+ please refer to GSM PO Network Speec'

Internal Use Only
(#alit) Pro$lems Sol#tions.
uring the test+ if it is found that the completion rate of some cell is low CK$0LE+ the
following items should be chec6ed:
1. /t should be chec6ed whether there are uplin6Adownlin6 interferences. /f there are
strong uplin6Adownlin6 interferences+ the calling side will hear beep sound when
he originates a call. Then+ 3- will return bac6 to the standby interface C-
assignment failsE.
@plin6 interferences can be chec6ed through the statistical counting of
interference band. /f 7and ; M ? counts is found+ it means that there are se.ere
uplin6 interferences.
-ection Error: 8eference source not found is about downlin6 interferences+ and
this part can be used to *udge downlin6 interferences.
#. /t should be chec6ed whether the problem is caused by networ6 congestion. /f
both the calling side and the called side ha.e TC) congestion+ the networ6 side
will deli.er isconnect signaling+ and the cause .alue is 9;.
Bor those sites which are configured with a low capacity+ for example+ cells
configured with -# or lower+ it is common that the traffic channel will be 1uite
busy upon the commissioning of site. The result is that the call completion
between the calling side and the called side fails.
:perators of :3C e1uipment room should be as6ed to chec6 the ser.ice
occupancy status of all carrier fre1uenciesG time slots. The purpose is to chec6
whether there are still channels a.ailable+ or whether all the channels are
occupied.
9. /t should be chec6ed whether the problem is caused by the fact that the access
parameters are not correctly configured.
The parameters which may influence the call establishment should be chec6ed.
/f the actual configuration is not consistent with the principles+ it should be
modified according to the actual situation. The parameters to be chec6ed
include 8"C) minimum access le.el+ 8xle.N"ccN3in+ C7"+ C75+ and so on.
; /t should be chec6ed whether the problem is caused by cross%connected antenna
and feeder.

Internal Use Only
/f 7CC) antenna or TC) antenna is cross%connected+ the 8J le.el will drop
dramatically when TC) is occupied by the handset Cin comparison to -CC)E.
/f the le.el is too low+ TC) assignment may failure. The result is that there will
be problems with originating calls. Bor the detailed chec6 procedures+ please
refer to Error: 8eference source not found section.
(.( )erification of received signal level
(.(.1 %ur$ose
Chec6 whether the downlin6 co.erage le.el is normal when 3- is at idle mode and
dedicated mode through the dri.e test CBor example+ chec6 whether the le.el is too low
in line%of%sight co.erage area which is close to the cell or whether the le.el of some
cell is lower than any other cell ob.iously.E. The purpose is to chec6 whether the
following problems exist: Carrier fre1uency is abnormal+ antenna and feeder is
connected in a re.erse way+ antenna downtiltAantenna directional angle is not
configured as planned+ there is ob.ious o.ershooting co.erage+ and so on.
(.(.2 )erification methods
The .erification methods are clarified here:
<repare the 3apinfo map which shows the site location. Choose the test radius
and test routes on basis of the site en.ironment.
Carry out T test and 6eep a test log. <ay attention to the Cell / at /dle state so
as to ensure that 3- will reside stably in the cell which is to be tested.
<ay close attention to 8x,e. Bull Cd7mE on 7CC) at idle state through the test
software interface or the testing handset interface.
<ay close attention to 8x,e. -ub Cd7mE on TC) at con.ersation state through the
test software interface or the testing handset interface.
"fter the test+ the bac6ground analysis software should be used to do some
statistical counting for downlin6 le.el at idle mode and dedicated mode
respecti.ely. Then+ it is supposed to produce a 2/- map which shows the
downlin6 le.el distribution.

Internal Use Only
(.(.3 +ethods of $roblem analysis and $roblem solving
The statistical counting of the downlin6 le.el and the 2/- map which shows the
downlin6 le.el distribution will show whether there are ob.ious downlin6 le.el
co.erage problems.
/f there are problems li6e wea6 downlin6 le.el+ shrin6ed co.erage+ the problems can be
analy0ed and chec6ed as follows Cthe chec6 items listed here are to be carried out after
the basic .erificationE:
1. Chec6 the surrounding en.ironment of the antenna of base station to see whether
there are ob.ious obstacles around the antenna+ for example+ billboards+ high
buildings+ high trees+ glass walls and so on. /f there are such obstacles+ the antenna
a0imuth or antenna height should be ad*usted so as to minimi0e their influence.
#. Chec6 whether the parameters which are rele.ant to access are configured
correctly+ including 8xle.N"ccessN3in+ C7"+ C75+ C8: and so on.
9. Communicate with engineers responsible for :3C e1uipment room and as6 them
to chec6 the configuration of data which are related to the output power of carrier
fre1uency. "ctually+ the static power le.el C<wr8eductionE parameter of each T8J
should be chec6ed. The purpose is to a.oid the possibility that the configuration of
this parameter is so large that the attenuation of downlin6 transmission power is
too large. /f this happens+ there will be no downlin6 co.erage.
Table ;%9 -tatic power le.el parameters
Bull name -tatic power le.el
"bbre.iation <w8reduction
escriptions
This parameter represents the static power le.el oftranscei.er. @sually
a static power control is addedon the basis of T8J transmission power
specifiedby -tatic power le.el. Famely+ a restriction isadded based on
the maximum transmission power+thus to get the actual maximum
transmissionpower <n of the T8J. The dynamic power control
isimplemented based on the maximum transmission power <n.
3anagement
ob*ect
T8J
Value range
The maximum output power+ the maximum output power %#d7+ the
maximum output power %;d7+ the maximum output power %=d7+ the
maximum output power %>d7+ the maximum output power %10d7+ the
maximum output power %1#d7+ the maximum output power D1.?d7+ the
maximum output power D1d7+ the maximum output power D0.?d7.

Internal Use Only
Bull name -tatic power le.el
efault
.alue
The maximum output power
;. Communicate with engineers responsible for :3C e1uipment room and as6 them
to chec6 the alarms of the site. @sually+ the alarms which indicate negati.e impact
on site co.erage are as follows: Carrier fre1uency alarms or C@ related alarms+
for example+ <" alarms of carrier fre1uency+ 9db alarms from carrier fre1uency+
C@ -!8 alarms+ and high temperature alarms of carrier fre1uency. There are
also cloc6 alarms+ for example+ cloc6 loss alarms of C33 board. 7esides+ there
are transmission alarms+ for example+ bro6en lin6 alarms of T8J+ yellow code
alarms of transmission+ and so on.
?. Bor a swap pro*ect+ if the original antenna and feeder is reused+ it should be
chec6ed whether a tower amplifier is used before the swap. /f the tower amplifier
is used+ it should be confirmed whether the tower amplifier is used in a right way.
(., )erification of rece$tion -uality
(.,.1 %ur$ose
Chec6 whether there is this 6ind of problem+ that is+ at the con.ersation state+ the
downlin6 le.el is normal but the downlin6 1uality is poor. "t this stage+ it aims to
chec6 the ob.ious interferences in the networ6 or the hardware failures.
(.,.2 )erification methods
The .erification methods are clarified here:
<repare a map named 3apinfo in ad.ance+ which shows the location of the base
station. Choose the appropriate test radius and test routes according to the site
en.ironment.
<ay attention to the downlin6 1uality of handset at con.ersation state during the
test. !ith the actual configuration of site in mind+ it is suggested that special
attention should be paid to 8x5ualN-ub of 7CC) carrier fre1uency and TC)
carrier fre1uency+ and CA/ at con.ersation state. 7esides+ it should be a.oided that
the downlin6 le.el is too low at con.ersation state.
"fter the test+ the :3C8 analysis software should be used to do some statistical

Internal Use Only
counting for downlin6 le.el 1uality at con.ersation state. Then+ it is supposed to
produce a 2/- map which shows the downlin6 le.el distribution.
(.,.3 +ethods of $roblem analysis and $roblem solving
The main causes for poor downlin6 1uality should be analy0ed on basis of the
downlin6 le.el and downlin6 CA/ which are measured in T test. The common causes
for poor downlin6 1uality include interferences inside and outside the networ6+
hardware failures+ inappropriate configuration of neighbor cells and parameters+ and so
on.
1. /f the call 1uality is poor C8x5 I ?E and the downlin6 le.el is normal+ CA/ at that
time needs to be chec6ed. /f CA/ is small CK 10E+ it is ob.ious that downlin6
interferences exist in the cell. The interfering resources may come from inside the
networ6 or outside the networ6.
Bor interferences from inside the networ6+ the fre1uency planning of the site
should be chec6ed through the planning software to see whether there are ob.ious
co%channel and ad*acent channel problems. "t the same time+ it can be confirmed
whether the interfering resources come from the neighbor cells nearby on basis of
the neighbor cell measurement reports. /f it is confirmed that the interfering
resources come from co%channel and ad*acent channel interferences from inside
the networ6+ the rele.ant fre1uency point needs fre1uency optimi0ation.
7esides+ for those cells where fre1uency hopping exists+ it should be confirmed
whether the following fre1uency hopping parameters are configured correctly:
3"+ 3"/:+ )-F and so on.
/f there are interferences from outside the networ6+ sweep generator should be
used to do fre1uency%sweep so as to locate the interfering sources. The most
familiar interfering sources from outside the networ6 include TV station+ high%
power radio station+ microwa.e+ radar+ high .oltage power lines+ secure
conferencing e1uipment+ interference unit at a gas station+ and so on. Bor detailed
chec6 procedures+ please refer to GSM P O Interference Sol#tions-
G#ide$ook.
#. /f the call 1uality is poor C8x5 I le.el ?E and the downlin6 le.el and downlin6 CA/
are normal+ the problem may be caused by hardware failures. /n this case+ it
should be chec6ed whether there are carrier fre1uency alarms or C@ related

Internal Use Only
alarms. Bor example+ <" alarms of the carrier fre1uency+ 9db alarms from carrier
fre1uency+ C@ -!8 alarms+ and high temperature alarms of carrier fre1uency+
and so on. 7esides+ it should be chec6ed whether there are problems with line
connections of radio fre1uency or output port of set%top unit. /f the lines are not
well connected+ you can feel they are 1uite hot.
9. Chec6 the hando.er related parameters. Birst+ chec6 whether there is a complete
configuration of neighbor cells. /f some neighbor cells are omitted+ the handset
can not be connected promptly to the cell which has better signal le.el and 1uality.
Therefore+ the call 1uality will be poor. 7esides+ the following parameters which
are related the cell and its neighbor cells should be chec6ed closely: <72T
hando.er threshold+ le.el hando.er threshold+ <AF .alues+ and so on. The poor call
1uality may be also caused by the fact that the hando.er between cells is not
smooth and there is an increasing amount of interferences. /n this case+ this 6ind
of parameters should be optimi0ed so as to impro.e the speed of hando.er.
(.. )erification of handover
(...1 %ur$ose
The purpose of this .erification is to chec6 whether there are problems with the
configuration of neighbor cell parameters and hando.er parameters from the
perspecti.e of long calls. 7esides+ it should be chec6ed whether there are problems li6e
interferences+ o.ershooting+ and so on.
(...2 )erification methods
)ando.er .erification is usually carried out through long call test. )ere are the details:
uring the test+ long call test will be adopted and the hando.ers on TC) channel
should be recorded.
Examine the neighbor cell list to see whether the nearby neighbor cells of the test
system are all listed out. /f there are cells which should be listed out but not+ it is
suggested that :3C8 engineers should be as6ed to chec6 whether neighbor cells
are omitted or whether there are problems with the existing neighbor cells.
The le.el of both the ser.ing cell and neighbor cells should be chec6ed to see
whether there are hando.er problems+ for example+ hysteretic hando.er+ 1uic6

Internal Use Only
hando.er+ ping%pong hando.er and so on.
"fter the test+ a statistical counting of hando.er e.ents should be done for the test
files so as to get the successful hando.er rate indicator. The source cells and target
cells which are related to unsuccessful hando.ers derser.e special attention.
(...3 +ethods of $roblem analysis and $roblem solving
uring the single site .erification test+ if there are hando.er failure e.ents+ the
following items should be chec6ed:
1. Chec6 whether the neighbor cell data are configured as planned for each cell. /f
the configuration is not right+ the handset can not be connected to the cell which
has the most suitable le.el. The result is that there will be hando.er failures. /t can
be chec6ed whether the neighbor cells are configured completely and correctly
through the neighbor cell list of dri.e test software.
#. !hen hando.er failure occurs+ the rele.ant source cell and target cell should be
paid attention to. /t should be analy0ed whether the hando.er is *ustified in aspects
of geographic topology+ le.el of ser.ing cell+ and le.el of target cell. /t should be
chec6ed whether there are problems with the downlin6 co.erage le.el+ the
downlin6 1uality+ or the target cell.
9. /f the hando.er failure is caused by the donwlin6 co.erage or downlin6 1uality
problems of the ser.ing cell+ section ;.9 and Error: 8eference source not found
should be referred to.
;. /f there are no problems with the ser.ing cell+ it should be analy0ed whether the
location of the target cell is appropriate or whether the le.el of 7CC) is
reasonable. 7esides+ it should also be chec6ed whether the target cell has
problems li6e o.ershooting co.erage or wea6 co.erage.
?. Chec6 whether the target cell has co%channel interferences. That is+ it should be
chec6ed whether the target cell has co%channel cells within a certain range. /t is
1uite possible to ha.e continuous hando.er failures if there are co%channel and co%
7/-C cells.
=. Chec6 whether the hando.er failure is caused by the too slow hando.er. ThatGs
because interferences will increase if the hando.er is too slow. This *udgment can
be made on basis of the le.el of ser.ing cell and ad*acent cells. !ith this 6ind of
problems+ some parameters should be optimi0ed to impro.e the hando.er speed+

Internal Use Only
including hando.er <72T+ le.el threshold+ pre%processing+ and so on.
&. 7esides+ it should be chec6ed whether the ser.ing cell and neighbor cells ha.e
alarms related to C33 cloc6. This 6ind of alarms will lead to fre1uent hando.ers
or no hando.er. This 6ind of problems should be reported to 7-- engineers to be
sol.ed.
(./ )erification of %0 service
(./.1 %ur$ose
28<- ser.ice and E2E ser.ice of 2-3 networ6 are playing a more and more
important role now. The .erification of <- ser.ice is to ensure that there are no
problems with <- ser.ice for those new sites. That is+ there are no problems with data
download and data upload.
(./.2 )erification methods
@sually+ <- ser.ice adopts fixed point test Csome clients may re1uire T testE. )ere are
the details:
:ne handset is used to do <- ser.ice test. 7efore the test+ it should be ensured that
all the preparation wor6 has been done. Bor example+ it should be confirmed
whether <- ser.ice is enabled for the test card+ and whether the account number
and password of the ser.er for BT< download are got.
Choose an appropriate test place. @sually the test should co.er 100 meters
co.ered by the cell so as to gurantee that the downlin6 co.erage le.el and CA/ of
the test place are satisfactory. Bor E2E ser.ice+ it should be ensured that CA/ is
o.er #0 steadily.
-tart the test. The single site .erification test usually does not in.ol.e a lot of test
items. The rele.ant test items include "ttach+ << acti.ation+ BT< download+
33- sending and reception+ and so on. Each item should be tested for 10 times+
and then the a.erage .alue will be recorded. Bor detailed procedures of <- ser.ice
test+ please refer to the <- ser.ice test part in GSM P O !adio Network Test
"ork G#ide$ook.
The :3C8 analysis software can be used to get the test results of different test
items. -ome abnormal e.ents should be paid close attention to+ and be analy0ed+

Internal Use Only
for example+ "ttach failure+ << acti.ation failure+ slow download speed+ T7B
drop+ and so on.
(./.3 +ethods of $roblem analysis and $roblem solving
/f the single site .erification results show that there are abnormal e.ents li6e "ttach
failure+ << acti.ation failure+ slow download speed+ T7B disconnection+ engineers
who are responsible for networ6 planning and optimi0ation can analy0e and sol.e the
problems through the following methods. )ere are the details:
1. Chec6 the test en.ironment
<- ser.ice test is a point to point test. Birst+ it should be ensured that <- ser.ice
of the test system and test handset operates well under a site which wor6s well.
Bor detailed procedures+ please refer to the <- ser.ice test part in GSM P O
!adio Network Test "ork G#ide$ook.
7esides+ the test results of <- ser.ice performance can also be influenced by
BT< ser.er performance+ and its location in the networ6 topology. This 6ind of
problems can also ha.e an impact on the .erification results all the other sites+
so they should be treated with special care.
#. Chec6 the radio en.ironment
uring <- ser.ice .erification+ the radio en.ironment should also be paid
attentiont to. uring the test+ it should be ensured that uplin6Adownlin6 1uality
and CA/ are good+ and there are no fre1uent cell reselections. The purpose is to
guarantee that the .erification results ha.e nothing to do with the radio
en.ironment.
Chec6 data configuration
Chec6 7-C cell parameters to confirm whether O2<8- is enabledP or OE2E
is enabledP.
Chec6 whether the extra abis time slots for transmission are correctly
configured for the site which is to be chec6ed.
Chec6 whether <C) channels are configured for the site.
9. Chec6 the resource configuration
Chec6 the number of <C) channels.

Internal Use Only
Chec6 the time slot configuration on "bis interface.
Chec6 -< configuration on <C C@<<77<C@E board.
Chec6 the bandwidth resource on 2b interface.
Bor item #+ 9+ and ;+ please refer to *+, GP!S !adio Network Optimization
"ork G#ide$ook.

Internal Use Only
, Acce$tance standard for single site
verification
"fter the .erification test+ the :3C8 analysis software is used to analy0e the test log
so as to get the H</ of the test and 2/- map. The statistical counting methods .ary with
different test softwares and :3C8 analysis softwares. This document ma6es a detailed
introduction about how to use TE3- to do the test+ how to export the test log+ and how
to use 3apinfo to do :3C8 analysis and diagrams. Bor details+ please refer to
"ppendix Error: 8eference source not found.
@sually+ the chec6 items and details of single site .erification for each pro*ect .ary
with different re1uirements of our clients. )owe.er+ part four of this document has
discussed the most familiar chec6 items of single site .erification. /n accordance with
the most familiar chec6 items+ the following table recommends some acceptance
standards. -ince the acceptance standards .ary with different re1uirements and
different scenarios+ the following acceptance standards are *ust for your reference.
Table ?%; "cceptance standards for the most familiar chec6 items
Fo. Fame Chec6 items "cceptance standards
1
7asic
.erification
Chec6 engineering parameters
Clongitude+ latitude+ antenna height+
and so onE.
Chec6 the following parameters at
idle state+ including ,"C+ C/+ 7CC)+
FCC+ 7CC+ 7" list and so on.
Confirm whether these parameters are
configured as planned.
#
Verificaiton
of antenna
Chec6 whether the co.erage
direction of 7CC) is configured as
planned. 7esides+ chec6 whether
7CC) antenna+ and TC) antenna are
connected in a re.erse way.
Confirm whether the configuration of antenna
a0imuth differs greatly from that as planned.
Confirm whether 7CC) antenna+ TC) antenna+
or the antenna and feeder of the whole cell are
configured in a re.erse way.
9 Verification
of completed
connection
between the
calling side
and the called
side
Chec6 whether there are
unsuccessful originating calls
between the calling side and the
called side.
Confirm whether the call ser.ice between the
calling side and the called side operates well.
Chec6 whether there are problems with .oice
1uality+ and call setup time.
The successful call establishment rate should
be higher than $?L+ and the originating calls
should be more than 10. 7esides+ the call setup

Internal Use Only
Fo. Fame Chec6 items "cceptance standards
time should be no more than &s Cboth the
authentication and encryption are not enabledE.
;
Verification
of recei.ed
signal le.el
Chec6 whether the downlin6
co.erage le.el is normal+ and whether
the co.erage range is normal.
The downlin6 8xle. should be around
=0d7m on the direct direction+ within 1003 from
the site.
Bor macro 7T- in urban areas+ samples whose
co.erage le.el I%&?d7m should reach >0.
Bor sites in suburban areas+ samples whose
co.erage le.el I%$0d7m should reach >0.
?
Verification
of recei.ed
signal 1uality
Chec6 whether the downlin6 call
1uality is normal+ and whether there
are interferences from inside the
networ6.
/f there is non%hopping+ and the co.erage le.el
is larger than %>?d7m CI%>?d7mE+ the call 1uality
should be lower than le.el # CK le.el #E. /f there is
fre1uency hopping+ and the co.erge le.el is larger
than %>?d7m CI%>?d7mE+ the call 1uality should
be lower than le.el 9 CK le.el 9E.
/f the co.erage is at a normal state+ samples
whose 8x5ual le.el is among 0%; should reach no
less than >0L CQ>0LE+ and samples whose
8x5ual le.el is at = or & should reach no more
than 10L CR 10LE.
=
Verificaiton
of hando.er
functions
Chec6 whether the configuration of
hando.er functions and neighbor cell
data is reasonable. 7esides+ chec6 the
uplin6 recei.ed signal le.el and
1uality.
Formally+ the successful hando.er rate should
be o.er $0L. 7esides+ there should be no
problems li6e ping%pong hando.er+ no hando.er+
or inappropriate target cell.
>
Verification
of <- ser.ice
Chec6 "ttach+ << acti.ation+ BT<
download and upload.
"ttach and << acti.ation should be within #s+
and 1.?s respecti.ely. Bor BT< download speed
Cwhen there is sufficient channel resourceE+
2<8-Q90HbpsE2EQ100HbpsS.
The sign S means that this part will .ary with different pro*ects and different
re1uirements of our client.

Internal Use Only
. A single site verification re$ort
/n practice+ the single site .erification which the networ6 planning department is
responsible for is the last step of networ6 migration before the access to networ6 is
enabled. The single site .erification consists of ; 6ey procedures+ that is+ testing+
problem analysis+ problem handling+ and writing a report. The .erification of each site
is finished with " -ingle -ite Verification 8eport. /f it is accepted by the client+ it
means that the whole .erification is successfully completed.
The .erification report should include the following items:
" list of basic .erification information and status confirmation.
-tatus of H</ related to .erification test. C- ser.ice mainly includes call success
rate+ hando.er success rate+ call drop rate+ co.erage rate+ .oice 1uality+ and so on.
<- ser.ice mainly includes "ttach+ << acti.ation success rate+ a.erage rate of
BT< downloadAupload.
" 2/- map of downlin6 le.el+ downlin6 1uality. The color code should be
configured according to the re1uirements of the client.
"nalysis of special e.ents which occur during the .erification test. Bor example+
call failure+ hando.er failure+ call drop+ and so on.
/f it is a swap pro*ect+ a comparison analysis of tests before and after the swap.
:ther items re1uired by the client.
@sually+ the format of a single site .erification report should be discussed with the
client. /n the appendixes of this document+ two complete templates of single site
.erification are pro.ided Ctemplate 1 and template #E. Template 1 is for a newly
established site+ but the .erification test of <- ser.ice is not included. Template # is for
swap sites+ and the .erification test of <- ser.ice is included.

Internal Use Only
A$$endi# A
A1 Tem$lates of 10+ single site verification re$ort
The format and content of single site .erification report .ary with different pro*ect
re1uirements. The two templates pro.ided here are based on the wor6 field pro*ects.
Template 1 is for a newly established site+ but the .erification test of <- ser.ice is not
included. Template # is for swap sites+ and the .erification test of <- ser.ice is
included.
Si ngl e si te
veri f i cati on templ ate 1. rar

Si ngl e si te
veri f i cati on templ ate 2. rar
A2 1uidance for T"+0 single site verification and O+'R data
analysis
"t present+ TE3- has become the most fre1uently used test tool for single site
.erification test. The documents enclosed here ma6e a detailed introduction about how
to use TE3- to do a series of tests+ including short call+ long call+ fre1uency%sweep+
and <- ser.ice download. 7esides+ the templates here also introduces how to use
TE3- to export test log data+ how to use Excel to do the statistical counting+ and how
to use 3ap/nfo to produce a 2/- map about le.el+ 1uality+ throughput+ and so on.
A gui debook f or
TEMS SSV test metods 2!!"!#1$%V1. 2&. rar

TEMS stat i sti cs
of test data and pl otti ng speci f i cati ons'v3. rar

GSM Network Planning and Optimization Single Site Verification Work Guidebook V1 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GSM Network Planning and Optimization Single Site Verification Work Guidebook V1 0

Uploaded by

Copyright:

Available Formats

Internal Use Only

GSM Network Planning and Optimization

You might also like