8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 1/9

A: BLER issue:BLER is not only the scope of work that RF can cover, It is the KPI combine the RFand lub transmission. So, sometimes, if we find FR is OK, such as RSCP and Ec/IOshow green in assistant but BLER still very bad, pay attention to the transmissionissue and NodeB hardware issue.Normally , BLER is bad because of the RF reason, so, how to improve Ec/Io will bethe key to improve BLER, as I checked Mumbai cluster, I find 3 reason for bad BLER:

1. Neighbor loss and no handover proper happened2. Site not on air3. Overshoot issue

Neighbor plan now show lot of problem, if we can solve the neighbor issue, we canimprove the KPI greatly. we can solve it by the following step:First , pl make one layer of un on-air layer in mapinfo, and this layer should beinput into Assistant ( Maybe the un on air site data is not so accurate , pl updateyour un on air layer in time )

 Then, when your input in engineer parameter table into assistant , pl make sureafter input , click “C (CellRadius)” button and get Cell Radius

Also in the Project Setting, select WCDMA Theme

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 2/9

Now, we can start the Theme analysis and get the report automatically by click thefollowing button.

 ( If you can’t see the Theme Result window, pl do as following )

In the output Excel table, we should pay attention the following sheet: “OverCoverage” , “Whole PP”and “Neighbor Cell Analysis”

Over Coverage: This sheet is used for you to judge the overshoot issue. For efficient using it, weshould filter it by “Total counter” and “rate”:

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 3/9

All the result, you should manual check one by one , if cell more than 15, top 15should be carefully check. (Pl sort the result as “Rate” if result cell number morethan 15)

One demo for overshoot:

One cell by one cell, input the cell name into the “theme Result view”, double clickthe cell name as following:

 Then, in the related geographic window, we can analysis the result and find tilt need

be change or not. (Pay attention, if the engineer parameter is proper,the result will also not be true.)

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 4/9

Neighbor Cell loss analysis

Auto Check In the assistant scan theme, for each bin, the best RSCP will be considered asservice cell. The neighbor which RSCP gap less than 3db will be pulsed one. Thisparameter can be setting in “Project setting “ window as following:

How to analysis the neighbor loss:First “COUNT” and “Rate” should be great than 3, then filter only Recommended,the result list should be carefully checked.

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 5/9

Manual check Another way to check neighbor is geographic check by Assistant:First input the un on-air layer into mapinfo, then input the neighbor plan excel fileinto assistant:

 The excel file of neighbor plan should be the following format:

 Then, manual check each sector by click the sector on assistant:

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 6/9

 You can right click it and add the lost neighbor into the service cell:

After finish all the checking work, output the new neighbor plan as following:

Filter the status column, find all “Added”, submit them to OMC engineer

But pay attention to the limit of 31 neighbor, you should carefully check this limit,(Unfortunately, delete function not support in current version, you should do it

manually )if more than 31, you should manual check which one is redundancyneighbor and list them also to OMC engineer. The final table submit to OMCengineer should be two table: one for delete and one for add, tell OMC engineer firstdo delete then do add, and feedback the operator log to you also for confirm.

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 7/9

B: Soft/Softer Handover Overhead issue

 This KPI related with overshoot issue, now in RNC, we setting value for activesetting adding threshold as 3db, which means that one neighbor Ec/IO is less thancurrent service cell with 3db, it will be pulsed into the active setting. And only whenthe active cell’s Ec/IO is more than 6db of servicer cell’s Ec/Io, it will be deleted fromthe active setting.

 The value for active setting add/delete in RNC is common for each vendor, so,current ,we don’t want modify it. We want your team find the overshoot issue andtry to make each road with domain cell; this KPI will immediately be matched.

For solve the overshoot issue, Pl refer the previous chapter of over shoot. For makeeach road with only one domain cell, this is hard to do. OMC parameter will be verypowerful of control this, but aimed at good network quality, pl carefully check eachroad, especially 3 sector with same Ec/Io , modify the tilt and azimuth, makedomain cell service the road.

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 8/9

C: Call drop issue

Call drop is not the main issue for current round 1 KPI, we should pay attention notonly the call drop, but also the RRCConnectionAbnormalRel should be carefullychecked:

If we find from dedicate mode to idle mode without normall release, it will be RRCConnection Abnormal Release, it will also be call drop.

As we check the all the call drop issue, most of them still be the issue of neighborlost. Some of call drop is because of overshoot issue , related tilt should be adjust;Also some call drop is because of the site not on air issue, put the google earthscreen copy to the report and go through it .

Pl using the drill down function for each call drop, analysis “WCDMA serving/ActiveSet”, you can get clear picture of why call dropped:

8/3/2019 Huawei - (12200390)

http://slidepdf.com/reader/full/huawei-12200390 9/9