In Huawei network, TCH drop increase from 1 % to 2% after cut 5 MHz from 2G, we already try to optimize BCCH & TCH frequency but the drop not improve so much. Can anyone recommend the parameters or/and features that will improve drop in overall network for this case ???
Hehe, wadda you expect? Improvement of DCR? Dude, u slashed 5MHz (count in terms of 200kHz ARFCNs)... Been there, seen it!
Anyway, here are some tricks for improvement: use SFH with max possible number of ARFCNs and take care of proper MAIO allocations, use AMR FR, carefully plan your BCCH, pray! This should improve the KPI but the overall customer experience may get worse because of AMR (robo-voice, etc.)
Thank you for your suggestion.
I have some more questions. AMR FR is recommended, it means no need to activate AMR feature ???
And if I cannot change BB to SFH, what is the different way to improve DCR ???
In our netwrok we have E******* & Huawei, after refram it has no effect in E******* but critical effect in Huawei.
Implementing AMR FR is a good idea but you will also need to redo your frequency plan besides doing a full parameter audit of your database. WOuld also recommend trying to improve your FH planning.
Implementing AMR FR is a good idea but you will also need to redo your frequency plan besides doing a full parameter audit of your database. WOuld also recommend trying to improve your FH planning.
Pray ! yes that is the best ********. God Bless
Amen!
Originally Posted by Optimal
Hi zlobster,
Thank you for your suggestion.
I have some more questions. AMR FR is recommended, it means no need to activate AMR feature ???
And if I cannot change BB to SFH, what is the different way to improve DCR ???
In our netwrok we have E******* & Huawei, after refram it has no effect in E******* but critical effect in Huawei.
It means you have to activate/unlock/enable the feature as per your vendor documentation. Alas, I don't have the specific H/// know-how yet.
Did you do a complete audit/consistency check of all definitions and parameters in your database/BSC/MSC, i.e. NBs, algos, etc.? Either way, I'd recommend you do it again.
If this doesn't help you don't have much left to do. Try to see the root cause of the dropped calls. See if the total DCR is not increased by only few contributing cells. See for RF conflicts on the border area (if any). Also, check to see if some of the refarmed spetcrum is not actually occupying the GSM one.
And the most universal solution there is - set radiolink timeout to MAX.
Try these and we'll talk again.
It means you have to activate/unlock/enable the feature as per your vendor documentation. Alas, I don't have the specific H/// know-how yet.
Did you do a complete audit/consistency check of all definitions and parameters in your database/BSC/MSC, i.e. NBs, algos, etc.? Either way, I'd recommend you do it again.
If this doesn't help you don't have much left to do. Try to see the root cause of the dropped calls. See if the total DCR is not increased by only few contributing cells. See for RF conflicts on the border area (if any). Also, check to see if some of the refarmed spetcrum is not actually occupying the GSM one.
And the most universal solution there is - set radiolink timeout to MAX.
Try these and we'll talk again.
You can also try to play with the parameter RX_LEVEL_MIN_CELL. try increasing the value. There will be fewer drops but thee overall user experience will be a bit degraded due to prolonged calls in spite of bad quality.
hope you can find something similar in your system. The one i discussed here is for the Nokia systems.
* DL Power control is mandatory
* Use some features like repeated SACCH
* Icrease RLT value - actualy , this not solve problem - only hide it
And take care on adjacent channel interference - > so where have neighbor cell with adjacent ARFCN to current cell BCCH ARFCN- put it to TCH, in order to benefit from power control. Also put more downtilt or power reduction to high overshooting cells.
I have some interested feature that might be improve this, Could
anyone have experienced on list of feature below please share to me.
- DRX
- Interference Based Channel Allocation
- Interference Rejection Combining
- Handover Re-Establishment
- Robust Air Interface Signaling
In order to heal something you have to put the right diagnose first. Try to pinpoint the real root cause for the increased DCR. Since you are showing a plot for a cluster/BSC/GERAN (maybe?) it could be the case where 4-5 cells have enormous drop, thus affecting the whole picture. IMHO, that's mandatory. Otherwise, you'd be just masking the problem and this my friend will take its toll someday. With the interest along...
The rest of the features are just make-up. If you choose to allocate on clean channels only and you have a pretty interfered air interface, you'll just end up with blocking, for example. Try to avoid DRX, use only DTX if available. It wrecks more havoc than it helps. IMHO again.
Originally Posted by tremalnike
*
* Icrease RLT value - actualy , this not solve problem - only hide it
I know, I just thought the fat smile at the end will suggest the (harsh) humor (sarcasm?).
You have all the weapons you need. Now stand up and fight.
Oh, and one last thing. As the second paragraph of my signature suggests - There's no such thing as a 'dropped call'. There's only 'handover-to-idle'.
Could you give me the reason advangetage/ dsiadvancetage for DRX, KPIs impact for DRX activation?
Originally Posted by zlobster
In order to heal something you have to put the right diagnose first. Try to pinpoint the real root cause for the increased DCR. Since you are showing a plot for a cluster/BSC/GERAN (maybe?) it could be the case where 4-5 cells have enormous drop, thus affecting the whole picture. IMHO, that's mandatory. Otherwise, you'd be just masking the problem and this my friend will take its toll someday. With the interest along...
The rest of the features are just make-up. If you choose to allocate on clean channels only and you have a pretty interfered air interface, you'll just end up with blocking, for example. Try to avoid DRX, use only DTX if available. It wrecks more havoc than it helps. IMHO again.
I know, I just thought the fat smile at the end will suggest the (harsh) humor (sarcasm?).
You have all the weapons you need. Now stand up and fight.
Oh, and one last thing. As the second paragraph of my signature suggests - There's no such thing as a 'dropped call'. There's only 'handover-to-idle'.
Thanks: 3
Reputation: 50
2G High drop after refram
Been there, seen it!
Reputation: 14
Originally Posted by maverrickforever
Implementing AMR FR is a good idea but you will also need to redo your frequency plan besides doing a full parameter audit of your database. WOuld also recommend trying to improve your FH planning.
Re: 2G High drop after refram
Posting Rules
Bookmarks