Вы находитесь на странице: 1из 14

During prepration the site integration data plz look on the following parameters BCCH- carrier freq.

BSIC- NCC + BCC varies from 0 to 7 LAC- related to paging RAC- related to gprs NSEI related to GPRS SLOT CDED related to GPRS how many slot r dedicated in these slots no voice calls only data calls CDEF related to GPRS how many slot are default means either r used 4 voice or data

CMAX= 100 % if no voice calls then all TSL are occupied by data RLT= directly related to SACCH frame (SLOW ASSOCIATED CONTROL CHANNEL) RXP= receiving mobile power (With this parameter you define the minimum power level an MS has to receive before it is allowed to access the cell.) SL= related to HO (With this parameter you define the minimum signal level of an adjacent cell, when a handover is allowed to one of them.) D max= is distance from which max. mobile can initate a call HSN MAIO BCF_ID BTS_ID PLMN (With this parameter you define to which PLMNs the MS is permitted to report measurement results. The values relate to the NCC part of the BSICs) FRL related to dual rate lower limit (With this parameter you define the percentage of full rate TCH resources that must be available for traffic channel allocation. Full rate TCHs are allocated until the number of free full rate resources is reduced below the threshold given in the parameter. The half rate resources are then allocated.) FRU related to dual rate upper limit (With this parameter you define the percentage of full rate TCH resources that must be available for traffic channel allocation. Full rate TCHs are again allocated when the number of the free full rate resources increases above the threshold given by the parameter.) ATT(allow_IMSI_attach_detach) (With this parameter you define whether IMSI attach/detach is used in the cell) DR == direct retry= for traffic sharing 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 number of zero results (With this parameter you define the number of zero results which can be omitted when the measurement results of the adjacent cells are averaged.) P MAX= BTS power P MAX-1 P MAX-2 PMRG (With this parameter you define a threshold in the power budget process. The handover margin prevents repeated handover between adjacent cells.) QMRG (With this parameter you define a threshold for a handover caused by signal quality)

LMRG

(With this parameter you define a threshold for a handover caused by signal level.)

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

U CAN PROCESS THE DUMP EITHER NETACT PLAN EDITOR SOFTWARE B/C FROM OSS THE FORMAT OF DUMP IS XML

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

channel
TCHF TCHH TCHD ERACH NOTUSED SDCCH

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 sites and TRX count / LAC is depends on the which mode are used combined(when BCCH&SDCCH are on single time slot) or noncombined(when BCCH&SDCCH are on different time slot) , how many blocks for AGCH and paging

MBCCH MBCCHC

MBCCB SBCCB

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

MPBCCH

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 BSC

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 12 TRX means 12*2=24 slots of PCM .now remaining 8 slots are distributed accordingly.3 slots for these TRX signalling and one slot for BTS signalling ...............one for syncronization ...........n remaing three slots are AD polling(abis dynamic polling)which is used 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 n PCM slots both working as master n slave which tends to increase the speed of data that is main reason that EGDE speed is more that Simple GPRS.........

detail
Full rate traffic channel Half rate traffic channel Dual rate traffic channel Random access channel of extended area RTSL does not have radio definition or Abis allocation Dedicated control channel (SDCCH/8)

Broadcast control channel Broadcast control channel combined with SDCCH (BCCH+SDCCH/4)

Broadcast control channel combined with SDCCH and CBCH (BCCH+SDCCH/4+CBCH) SDCCH with CBCH

Packet control channel (PBCCH + PCCCH + PDTCH + PACCH + PTCCH) <option>

GPRS PROCESS if we required GPRS and EDGE enable in the site then first requirement is E1 or media b/w BSC and SGSn one E1 contains 30 TSL then we create Gb-link b/w them with different combination of TSL one TSL =64 kbps 2 TSl=128kbps 3 TSl=192 kbps for the creation of gblink we req. port details , CIR,name BSC gb-link , NSEi, NSVCEI all are same thing one BSc conatins 6 BCSU card 1 BCSU card contains 2 PCU one PCU = 64 TSL the mapping of TRX and Traffic manager for EDGE n/w is done on the PCU after gb link creation sites are attached to that if city or CBD sites are attached to 2 TSL or 3 TSL gb link it means whose BW=128,192 kbps town sites or upcounty sites attached to 1TSL gb-lonk max. 40 cells are attached to one gb-link attachment of cells to gb-link is depends on the usage of GPRS b/c for good n/w all gb=link are equally utilized if data speed issue then cross check the CDED and CDEF value and enhace it and also go through with the NSEI band width if cells are increasing and u need the gb-lonk for GPRS enable then put a request for media in 1 E1 u can create max gb link whose count of TSL=30 like that 10gb-link of 3 TSL= 10*3=30 TSL it means 1 E1 is full RAC PLANNING IS THERE LIKE LAC NEAR SITES ALL IN SINGLE RAC B/C PDP ACTIVATION AND DEACTIVATION IS GOING ON IN GPRS OR TBF IN UL AND DL CASE

ND REPORTS AND MML COMMANDS use 51 report for the GPRS and EDGE enable or disable cells use 226 report for UL and Dl throughput for GPRS and EDGE 243 for the utilization of Gb-link after adding the sending and receiving column 280 for DAP id's ZFWO =BCSU=0&&6;BTS;= provide the details BSC / wise where or in those cells GPRS is working ZWUP= NO. OF ET IN BSC ZDTI= PCM STATUS ZUSI=IN WHICH MODE ET IS.

FOR SD BLOCKING calculate SD traffic - continous for 4 days from report no =182 then process it traffic in merlang convert into erlangafter / by 1000 then find available sd slots corresponding to CI no. of TSL of sd *8 *8 depends on the combined and non- combined mode then vlookup from erlang table with .5 GOS the obtained value is equipped value u got traffic and equipped find utilization > 70% utilization of SD resoirces then increase SD slot accordingly watch or monitar then KPI

standard 1 TRX= no - SD(combined mode) 2 TRX = 1 sd 3 TRX= 2 SD 4 TRX = 3 SD or depends on SD traffic either Airport site , college site and VSAT site check weather all TRX are working shift the SD slot also in case of blocking if traffic is less ckeck weather dual rate is imlemented or not

FOR TCH BLOCKING find TCH traffic from report then find TCHF and TCHD in the PLMN / cell wise if TCHD with FRL=40% and FRU=60% then during calaculation of equipped directly calculate =1.4*TCHD calculate equipped erlang after taking data from Erlang table with GOS=2% calculate erlang of TCHF and TCHD then add it find total equipped TCH erlang and u hav. Traffic then calculate utilization with FR and FR + HR data can be manuplated or edited min. consecutive 3 to 4 days then TRX addition list is prepared to remove congestion and cells are coming within utilization consider all cells having > 80% utilization also cross check wether site created on full E1 and Half E1 during TRX additon BCSU constrain also consider then BSC utilization if it is > 95% then it may be malfuctioning adding of XDR may be properly- b/c single XDR seizes approx 100 ckts at a time . if utilization of BSC is high and XDR drop is there then first add XDR in that particular BSC nokia system - single site having max. 12 TRX if site is created on half E1 then two sites = 6+6 TRX max. in the whole process of confi. If we can talk regarding = V+D then no signalling TSL are count that is excluded only DATA TSL and TCH TSL are consider

site audit orientation height of GSM tilt -mechanical or electrical swap move clockwise and anti clockwise site radiating all TRX are working DVGA is working connections are proerly verify lat and long

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 apply 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 inteferenceneighbours 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 wayschange 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


51 related to gprs or edge enable cells 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 182 for SD traffic 186 for tch traffic 190, 196 for interference n quality 204 226 for KPI of data 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 for cell, site n BSC 243 for gb-link utilization

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