Solve ACC HSDPA problem generated by pmAllocRejHwHsDschUsers
A big problem is coming with the traffic growth in the networks, especially if your network has not the capacity growth that you would like to.
The impact of this problems is directly over ACC HSDPA and ACC EUL. I'm talking about the HS-DSCH ALLOC REJECTION. It's commom see this problem in RBS 3000 and RBS 6000 with just 1 DUW. The most part of these cases happens where featureStateHsdpaMc is ACTIVE.
NOTE: featureStateHsdpaMc when ACTIVE will force the pair of carriers use the same HS-TXM, then if you have a site with 3 sectors and 2 carriers for instance 2100 MHZ per sector, these carriers will use the same HS-DSCH resource, if featureStateHsdpaMc is NOT ACTIVE than this rule does not need be followed.
This happens because you have a high traffic scenario or the HS-DSCH Codes just are not enough. I'm talking about the reponse of the command get . resources -> numHsCodeResources and the counter pmAllocRejHwHsDschUsers.
HsDschResources pmAllocRejHwHsDschUsers long Peg,ropReset
------------------------------------------------------------------------------------------------------------------------------------
The number of attempts to allocate resources for new HS-DSCH user that is rejected due to lack of HS resource capacity.
Counter type: Peg
Counter is reset after measurement interval: Yes
Condition: Stepped when an attempt to allocate resources for a new HS-DSCH user is rejected due to lack of HS resource capacity. HS-FACH is not applicable to this counter and HS-FACH transmissions do consequently not trigger the stepping of this counter. The actual measurement is started when the HS-DSCH resources are setup.
Undefined value: -1
Well you have some ways to fight against it. Then is essential have numHsCodeResources=3 configured per DUW and use recommended setting of maxNumADchReservation=250 per DUW.
NOTE: In W13A HSDPA MULTI CARRIER does not work if you have 2 DUW and for instance a sector with 2 carriers A and 1 created in different DUW. In W13B, W14 you have a feature that can chnage this scenario.
1) If you have 2 DUW scenario try to balance traffic with other carriers in this same sector, this way you can try to use HS resources from both DUW.
2) Try to balance traffic with neighbors or downtilt the sector if this is a overshooter.
3) No way? Tried 1 and 2 and not happens? Here you will play a hard game.
3.1) For 1 DUW one way to solve or reduce the impact over ACC HSDPA is...
3.1.2) Check the counter pmAllocRejHwHsDschUsers per carrier and also check in Utrancell the HSDPA Users per carrier.
3.1.3) With this information try to imagine what configuration would be the best for your case.
3.1.4) Then use the command rrh cellIdMapping -all and logMacHs_2 to check which carrier is allocated in each HS Code Resource.
3.1.5) If the feature featureStateHsdpaMc is ACTIVE set the feature to 0, save CV and restart the Node or block/deblock Node in RNC. Repeat block/deblock until you have the best configuration. This is really boring cause if somebody reset the Node or the Node come down the resources will be allocated different and you will have to fix it again.
3.1.6) Check again the commands rrh cellIdMapping -all and logMacHs_2, you will see that the allocation is different. Now is time to check if this configuration is the best for you.
In my tests I can't see big losses in HSDPA THROUGHPUT because of the deactivation of featureStateHsdpaMc and you will have depending of the case big improvement of ACC HSDPA if the problem is this.
Remember this is a emergencial action to keep good ACC HSDPA and the solution for this case is install the second DUW to have more HS codes available.
4) I did the item 3 in my 1 DUW site, have an improvement but not enough. What do do now?
4.1) Now it's time to be more agressive. You can set then numHsCodeResources=4 but before you have to check pmAllocRejADch, ADCH utilization (pmUsedADch) and the utilization of CE DL.
When you set numHsCodeResources=4 you will reduce CE DL available (get . available), you can recover it reducing the maxNumADchReservation, but you have to check how much you can reduce to avoid other problems.
If it is possible OK do it, set numHsCodeResources=4 and reduce ADCH to have CE DL available and check the commands rrh cellIdMapping -all and logMacHs_2, you will see that now you have 4 HS codes with different distribution. Again, save CV file and block/deblock node in RNC until you have the best configuration.
TIP: If it is not possible to configure numHsCodeResources=4 beacuse ADCH or CE DL Available try to set numEulResources to 0. Yes you will deactivate EUL but remember this is temporary and emergencial case, could be a solution to keep ACC HSDPA.
DownlinkBaseBandPool pmAllocRejADch long Peg,ropReset
------------------------------------------------------------------------------------------------------------------------------------
The number of attempts to allocate resources for new HS-DSCH user that is rejected due to lack of A-DCH resources.
Counter type: Peg
Counter is reset after measurement interval: Yes
Condition: Stepped when an attempt to allocate resources for an HS-DSCH user is rejected due to lack of A-DCH resources. The actual measurement is started when the HS-DSCH resources are setup.
Undefined value: -1
DownlinkBaseBandPool pmUsedADch sequence:long [11] PDF,ropReset
------------------------------------------------------------------------------------------------------------------------------------
The distribution of A-DCH resource utilization, as percentages of the baseband pool resources currently reserved for A-DCH.
Counter type: PDF
Counter is reset after measurement interval: Yes
Condition: Sampled each second of the granularity period (gives 900 values). The actual measurement is started when the HS-DSCH resources are setup.
PDF ranges:
[0]: Number of CEs currently reserved for A-DCH in the baseband pool
[1]: Number of sampled values in range [0..20[ %
[2]: Number of sampled values in range [20..40[ %
[3]: Number of sampled values in range [40..50[ %
[4]: Number of sampled values in range [50..60[ %
[5]: Number of sampled values in range [60..70[ %
[6]: Number of sampled values in range [70..80[ %
[7]: Number of sampled values in range [80..85[ %
[8]: Number of sampled values in range [85..90[ %
[9]: Number of sampled values in range [90..95[ %
[10]: Number of sampled values in range [95..100] %
DownlinkBaseBandPool pmSumCapacityDlCe long ACC,ropReset
------------------------------------------------------------------------------------------------------------------------------------
Aggregate of all sample values (measurement_value) recorded within the ROP for number of used DL Channel Elements.
Counter type: ACC
Scanner: Primary
Counter is reset after measurement interval: Yes
Condition: A new sampled value is added each second of the granularity period. The actual measurement is started when the DownlinkBaseBandPool is created.
Undefined value: -1
DownlinkBaseBandPool pmSamplesCapacityDlCe long SCAN,ropReset
------------------------------------------------------------------------------------------------------------------------------------
Number of samples in pmSumCapacityDlCe (that is, pmSamplesCapacityDlCe = pmSamplesCapacityDlCe + 1, whenever pmSumCapacityDlCe is to be updated).
Counter type: SCAN
Scanner: Primary
Counter is reset after measurement interval: Yes
Condition: Stepped each time a measurement value is sampled for pmSumCapacityDlCe. The actual measurement is started when the DownlinkBaseBandPool is created.
Undefined value: -1
5) Now for RBS 3000. If you have RBS 3000 try to install 2 HSTX-60 boards, this boars supports 3 HS Codes each and this way you will reduce the chance to have problems with the pmAllocRejHwHsDschUsers and ACC HSDPA.
5.1) There are cases that you have 2 HSTX-60 boards with numHsCodeResources=3 and have the problem, in this case you can try work with steeredHsAllocation.
5.1.1) If ACTIVE, deactivate featureStateHsdpaMc, save CV file and block/deblock Node in RNC. Check the KPIs.
5.1.2) If item 5.1.1 was not enough check the resources and the allocation.
rrh cellIdMapping -all
lhsh 000800 logMacHs
lhsh 000700 logMacHs
!7 and 8 are my TX BOARDS SLOTs, yours could be different!
5.1.3) In RNC block the Node. In the Node set the feature steeredHsAllocation to true. (get . stee)
5.1.4) get . hsCodeResourceId to check that all are 0. Then you have to set according the best configuration for you, for example:
Here I have a SET for 4 Codes that we will check after, but is the same concept if you have 6 Codes. See I put 2 carriers to 4, 2 carriers to 3 and 1 carrier to 1 and the last one to 2. In this case 1 and 2 are my carriers with more HS LOAD.
5.1.5) Save CV file and deblock the Node. Check the KPIs.
6) Cases with HSTX-45 boards.
6.1) Try to change these boards to HSTX-60 or change the Node-B to DUW.
6.1.1) 6.1 Not possible? Ok then try the same that I explained before use steeredHsAllocation and deactivate featureStateHsdpaMc and check.
6.1.2) 6.1.1 not OK? Try to set numEulResources to 0 and free resources, this way you can try to set numHsCodeResources=3 in a HSTX-45 but is not good. If you do that do not forget to check the same things that you mention to check in DUW, item 4.1.
Attached a file that can help you to calculate all I said, this file was not made by me, but it's very useful and I downloaded it here.
Add Rep, please.
Last edited by dadoba; 2014-12-09 at 09:12 AMReason: Fixing words
Re: Solve ACC HSDPA problem generated by pmAllocRejHwHsDschUsers
This is a very good information.
And related to your comment here :
"NOTE: In W13A HSDPA MULTI CARRIER does not work if you have 2 DUW and for instance a sector with 2 carriers A and 1 created in different DUW. In W13B, W14 you have a feature that can chnage this scenario."
What "feature" is it ?
Originally Posted by dadoba
A big problem is coming with the traffic growth in the networks, especially if your network has not the capacity growth that you would like to.
The impact of this problems is directly over ACC HSDPA and ACC EUL. I'm talking about the HS-DSCH ALLOC REJECTION. It's commom see this problem in RBS 3000 and RBS 6000 with just 1 DUW. The most part of these cases happens where featureStateHsdpaMc is ACTIVE.
NOTE: featureStateHsdpaMc when ACTIVE will force the pair of carriers use the same HS-TXM, then if you have a site with 3 sectors and 2 carriers for instance 2100 MHZ per sector, these carriers will use the same HS-DSCH resource, if featureStateHsdpaMc is NOT ACTIVE than this rule does not need be followed.
This happens because you have a high traffic scenario or the HS-DSCH Codes just are not enough. I'm talking about the reponse of the command get . resources -> numHsCodeResources and the counter pmAllocRejHwHsDschUsers.
HsDschResources pmAllocRejHwHsDschUsers long Peg,ropReset
------------------------------------------------------------------------------------------------------------------------------------
The number of attempts to allocate resources for new HS-DSCH user that is rejected due to lack of HS resource capacity.
Counter type: Peg
Counter is reset after measurement interval: Yes
Condition: Stepped when an attempt to allocate resources for a new HS-DSCH user is rejected due to lack of HS resource capacity. HS-FACH is not applicable to this counter and HS-FACH transmissions do consequently not trigger the stepping of this counter. The actual measurement is started when the HS-DSCH resources are setup.
Undefined value: -1
Well you have some ways to fight against it. Then is essential have numHsCodeResources=3 configured per DUW and use recommended setting of maxNumADchReservation=250 per DUW.
NOTE: In W13A HSDPA MULTI CARRIER does not work if you have 2 DUW and for instance a sector with 2 carriers A and 1 created in different DUW. In W13B, W14 you have a feature that can chnage this scenario.
1) If you have 2 DUW scenario try to balance traffic with other carriers in this same sector, this way you can try to use HS resources from both DUW.
2) Try to balance traffic with neighbors or downtilt the sector if this is a overshooter.
3) No way? Tried 1 and 2 and not happens? Here you will play a hard game.
3.1) For 1 DUW one way to solve or reduce the impact over ACC HSDPA is...
3.1.2) Check the counter pmAllocRejHwHsDschUsers per carrier and also check in Utrancell the HSDPA Users per carrier.
3.1.3) With this information try to imagine what configuration would be the best for your case.
3.1.4) Then use the command rrh cellIdMapping -all and logMacHs_2 to check which carrier is allocated in each HS Code Resource.
3.1.5) If the feature featureStateHsdpaMc is ACTIVE set the feature to 0, save CV and restart the Node or block/deblock Node in RNC. Repeat block/deblock until you have the best configuration. This is really boring cause if somebody reset the Node or the Node come down the resources will be allocated different and you will have to fix it again.
3.1.6) Check again the commands rrh cellIdMapping -all and logMacHs_2, you will see that the allocation is different. Now is time to check if this configuration is the best for you.
In my tests I can't see big losses in HSDPA THROUGHPUT because of the deactivation of featureStateHsdpaMc and you will have depending of the case big improvement of ACC HSDPA if the problem is this.
Remember this is a emergencial action to keep good ACC HSDPA and the solution for this case is install the second DUW to have more HS codes available.
4) I did the item 3 in my 1 DUW site, have an improvement but not enough. What do do now?
4.1) Now it's time to be more agressive. You can set then numHsCodeResources=4 but before you have to check pmAllocRejADch, ADCH utilization (pmUsedADch) and the utilization of CE DL.
When you set numHsCodeResources=4 you will reduce CE DL available (get . available), you can recover it reducing the maxNumADchReservation, but you have to check how much you can reduce to avoid other problems.
If it is possible OK do it, set numHsCodeResources=4 and reduce ADCH to have CE DL available and check the commands rrh cellIdMapping -all and logMacHs_2, you will see that now you have 4 HS codes with different distribution. Again, save CV file and block/deblock node in RNC until you have the best configuration.
TIP: If it is not possible to configure numHsCodeResources=4 beacuse ADCH or CE DL Available try to set numEulResources to 0. Yes you will deactivate EUL but remember this is temporary and emergencial case, could be a solution to keep ACC HSDPA.
DownlinkBaseBandPool pmAllocRejADch long Peg,ropReset
------------------------------------------------------------------------------------------------------------------------------------
The number of attempts to allocate resources for new HS-DSCH user that is rejected due to lack of A-DCH resources.
Counter type: Peg
Counter is reset after measurement interval: Yes
Condition: Stepped when an attempt to allocate resources for an HS-DSCH user is rejected due to lack of A-DCH resources. The actual measurement is started when the HS-DSCH resources are setup.
Undefined value: -1
DownlinkBaseBandPool pmUsedADch sequence:long [11] PDF,ropReset
------------------------------------------------------------------------------------------------------------------------------------
The distribution of A-DCH resource utilization, as percentages of the baseband pool resources currently reserved for A-DCH.
Counter type: PDF
Counter is reset after measurement interval: Yes
Condition: Sampled each second of the granularity period (gives 900 values). The actual measurement is started when the HS-DSCH resources are setup.
PDF ranges:
[0]: Number of CEs currently reserved for A-DCH in the baseband pool
[1]: Number of sampled values in range [0..20[ %
[2]: Number of sampled values in range [20..40[ %
[3]: Number of sampled values in range [40..50[ %
[4]: Number of sampled values in range [50..60[ %
[5]: Number of sampled values in range [60..70[ %
[6]: Number of sampled values in range [70..80[ %
[7]: Number of sampled values in range [80..85[ %
[8]: Number of sampled values in range [85..90[ %
[9]: Number of sampled values in range [90..95[ %
[10]: Number of sampled values in range [95..100] %
DownlinkBaseBandPool pmSumCapacityDlCe long ACC,ropReset
------------------------------------------------------------------------------------------------------------------------------------
Aggregate of all sample values (measurement_value) recorded within the ROP for number of used DL Channel Elements.
Counter type: ACC
Scanner: Primary
Counter is reset after measurement interval: Yes
Condition: A new sampled value is added each second of the granularity period. The actual measurement is started when the DownlinkBaseBandPool is created.
Undefined value: -1
DownlinkBaseBandPool pmSamplesCapacityDlCe long SCAN,ropReset
------------------------------------------------------------------------------------------------------------------------------------
Number of samples in pmSumCapacityDlCe (that is, pmSamplesCapacityDlCe = pmSamplesCapacityDlCe + 1, whenever pmSumCapacityDlCe is to be updated).
Counter type: SCAN
Scanner: Primary
Counter is reset after measurement interval: Yes
Condition: Stepped each time a measurement value is sampled for pmSumCapacityDlCe. The actual measurement is started when the DownlinkBaseBandPool is created.
Undefined value: -1
5) Now for RBS 3000. If you have RBS 3000 try to install 2 HSTX-60 boards, this boars supports 3 HS Codes each and this way you will reduce the chance to have problems with the pmAllocRejHwHsDschUsers and ACC HSDPA.
5.1) There are cases that you have 2 HSTX-60 boards with numHsCodeResources=3 and have the problem, in this case you can try work with steeredHsAllocation.
5.1.1) If ACTIVE, deactivate featureStateHsdpaMc, save CV file and block/deblock Node in RNC. Check the KPIs.
5.1.2) If item 5.1.1 was not enough check the resources and the allocation.
rrh cellIdMapping -all
lhsh 000800 logMacHs
lhsh 000700 logMacHs
!7 and 8 are my TX BOARDS SLOTs, yours could be different!
5.1.3) In RNC block the Node. In the Node set the feature steeredHsAllocation to true. (get . stee)
5.1.4) get . hsCodeResourceId to check that all are 0. Then you have to set according the best configuration for you, for example:
Here I have a SET for 4 Codes that we will check after, but is the same concept if you have 6 Codes. See I put 2 carriers to 4, 2 carriers to 3 and 1 carrier to 1 and the last one to 2. In this case 1 and 2 are my carriers with more HS LOAD.
5.1.5) Save CV file and deblock the Node. Check the KPIs.
6) Cases with HSTX-45 boards.
6.1) Try to change these boards to HSTX-60 or change the Node-B to DUW.
6.1.1) 6.1 Not possible? Ok then try the same that I explained before use steeredHsAllocation and deactivate featureStateHsdpaMc and check.
6.1.2) 6.1.1 not OK? Try to set numEulResources to 0 and free resources, this way you can try to set numHsCodeResources=3 in a HSTX-45 but is not good. If you do that do not forget to check the same things that you mention to check in DUW, item 4.1.
Attached a file that can help you to calculate all I said, this file was not made by me, but it's very useful and I downloaded it here.
Thanks: 
Solve ACC HSDPA problem generated by pmAllocRejHwHsDschUsers
Originally Posted by dadoba
Bookmarks