During prepration the site integration data plz look on the following parameters

BCCH
BSIC
LAC
RAC
NSEI related to GPRS SLOT
CDED related to GPRS how many slot r dedicated
CDEF related to GPRS how many slot are default means either r used 4 voice or data
RLT
RXP
SL
D max
HSN
MAIO
BCF_ID
BTS_ID
PLMN
FRL related to dual rate lower limit
RRU related to duala rate upper limit
ATT
DR == direct retry
CI
BSC _ ID
Neighbour details
LDWS = related to neighbour parameter
LUWS === related to neighbour parameter
LDW = related to neighbour parameter
LUW = related to neighbour parameter
NOZ
P MAX
P MAX-1
P MAX-2
PMRG
QMRG

LMRG

Plz look on that parameters before creating the site in OSS / OMC

after site integrate first cross check with integration packages so ………….u sure that all parameters
are created properlt that is called DUMPchecking
one BSC=6 BCSU(Base control signalling unit)
one BCSU = support 110 TRX
1 TRX= 8 time slots
total no. of TRX = 110 *6=660 TRX in single BSC

one BSC = One LAC

one LAC = 367 sites of 2+2+2 configration
one LAC = 266 sites of 4+4+4 configaration
one BSC= 660* 8 = time slots but if dual rate is implemented that it consider as two slots

one BSC= two Lac also but for city one LAC b/c it effects SD blocking and LAC updation on that channel

if one of any time slot, TRX n BCSU is over it seems to be BSC capacity is over

Rehoming is also consider for in fill sites

one BSC= 1 to 248 BCF

one BSC= 1 t0 248 BTS

one BTS means = one sector of any configaration

one BCF means= one site of three or four sector

if u can use Metro BTS and distance b/w two sectors is more than 5m then we can use two BCF for single site

BCF= Base control function

BTS= Base transreciever system

NSEI= is hardware device which supports the GPRS in n/w

one NSEI== suppports 64 BTS and 128 TRX if any one of them is full then we can assign second NSEI port in same B

one ATTER is supports the 110 TRX b/w Transcoder n BSC so we can also calculate the no. of atters is used

one PCM having 32 slots in which one trx is supported by two PCM slots so in NOKIA system one PCM suports the 1
12*2=24 slots of PCM …….now remaining 8 slots are distributed accordingly………….3 slots for these TRX signalling
for BTS signalling ...............one for syncronization ...........n remaing three slots are AD polling abis dynamic polling w
for EGPRS b/c in that case these slots are also used for data with the time slots of TRX .........in that moment TRX time
slots both working as master n slave which tends to increase the speed of data that is main reason that EGDE speed
Simple GPRS.........
 Monitoring these KPIs

sd drop less than 2 %

Sd blocking less than 1 %
Tch drop less tha 3 %
Tch blocking no in n/w to remove this allpy half rate/dual rate/ AMR/ add more TRX in that cells

TCH assignment greater than 95 % if it is less max. chance of SWAP in that site
HOSR is greater that 95 %

Random Access Success Rate, greater than 98 %

if SD drop is high plz look on that parameters= overshooting , shift the SD time slot , may be
hardware issue, interference, change the values of RXP, PMAX………, may be issue of uplink or
downlink issue in that cells for UL put a TMA in that cell n for DL provide tilt ,re orient that anteena.

for TCH drop first cross check the BCCH of that cell , hardware issue may be,change RXP and RLT
value………find out there is any inteference………neighbours are properly defined or not……….

if hardware issue plz cross check the VSWR it is not greater than 1.3 otherwise cross check all
connections from begining to end , use the spectrum analyzer for ul issues, if TRX is faulty then
cross check with 208 report for in which u see that diff. b/w UL n DL power or say link balance is not
proper………..may be duplexer or combiner faulty...............if 100 ft feeder cable is used than 1.2 dbm
loss per 100 ft. so ht. is also effects the KPI......change the oscillator requency in BTS which also
effects our KPI........if any alaram like channel failure rate is high then remove it through ONM
candidate..........may be anttena connection faulty............ if any cell not taking calls plz cross check
the OMC n CGI data if that is not same then cells r not able to taking calls. b/c CGI creation in swtich
n OMC data in NOC.........so both r same .............

for HOSR plz change the hand over parameters , all ho are create in both ways………change the SL if
some cells having poor HOSR………….
for HOSR plz change the hand over parameters , all ho are create in both ways………change the SL if
some cells having poor HOSR………….

if BOI card is faulty in the BTS it means no incoming HO and no outgoing HO from that cells , ur
mobile getting signal but u r enable to make a call from that cells…………..it is simply the processor
card
plz look on these following reports for any problem in n/w

61 report is related to one way HO

67 report for Syn . In the same BCF that is yes otherwise no
111 related to BCCH
130 related to SD congestion
135 related to TCH congestion , threshold is 120 sec.
150, 153 , 154 related to HO in which u see which cell having max. no. of HO failure with their reasons
163 for TCH drop , in which u seee actual reason for drop may be RF , LAPD, Transcoder failure, link flatucate
190, 196 for interference n quality
232 report for overshooting acc. To tell. Theort more than 95 % samples within 3.3 km
208 for link balance if the diff . b/w ul n dl is grater tha 5 dbm then TRX is faulty
216 that is analyzer report foe cell, site n BSC

see the current alarams for any problem in particular cells

ZEAT log are very clear in BSC b/c it effects HOSR
 site creation data
site is created in NOC
on air
check with implementation report all TRX r working fine n taking calls and VSWR is right
then see in KPI report about their traffic status

drive test done of that site ………….before that physical audit ..orientation,,,,,,,,,,tilt………..are
proper acc. To plan n customer is satisfied