- This topic has 14 replies, 1 voice, and was last updated 8 years, 1 month ago by pix.
24th May 2010 at 06:39 #62834GuybrushGuest
Is there a limit of number of paging messages that can be sent on Abis? How can this limit of capacity be calculated?
Guybrush25th May 2010 at 13:23 #62835pixGuest
the pagings are sent on the RSL, and those channels are usually defined with a variable size. So the capacity cannot be calculated (or let’s say that i’m not aware of the method).
However, the ABIS is probably never a limitation regarding paging. The limit comes from the radio PCH capacity, and also from the BSC processing. Deoending on your vendor, you might be able to find an indicator that measures the RSL load of the Abis.
(RSL is alcatel specific : it is the channel on the Abis that carries all radio signalling for 1 TRX only)
FYI, to further decrease the paging load on the Abis, you can activate a feature that aggregates multiple paging commands into one big paging message.4th June 2010 at 12:24 #62836RexGuest
CCH_Paging_Command_Abis_discarded_cong_rate reached 5 percent. Is it to high? What’s the recommended threshold (ALU) and any solution to reduce it? Should we increase MFRS? MFRS is 5, BS_AG_BLKS_RES is 4. What’s the cause of high Paging_command_lost_Abis in some cells?
Rex4th June 2010 at 16:56 #62837pixGuest
it is very high…
could you share with us the full description of the counter ? what is the trigger event ?
i’m not sure whether the congestion is in the abis link or on the radio interface. From the name of the indicator, of course, it looks like the abis is congested.
So i’ll work on this assumption…
You must either
1- reduce the number of paging
2- increase the RSL capacity
(a) activate MULTIPLE PAGING feature (it will aggregate n paging requests into only one “Abis” paging message)
(b) reduce the size of your LAC
(c) ensure that the paging is done with TMSI (? huh… i don’t think that would help though)
(a) use RSL Multiplexing “statistical 64kb/s” “NORMAL LOAD” (4 RSL / 64kbps)
(b) if that’s already done, use “HIGH LOAD” (2 RSL / 64kbps). That means you’ll have to define more RSL timeslots on your Abis
pix7th June 2010 at 12:34 #62838RexGuest
the full description of the indicator is this:
Rate of discarded “PAGING COMMAND” messages received by the BTS on Abis interface over the number of “48.058 PAGING COMMAND” messages received by the BTS on Abis and had to be sent for CS and PS traffic to the MS.
Thanks for your solutions. By MULTIPLE PAGING feature, did you mean Multiple CCCH? I think it’s optional feature which we don’t have and need to pay I think. The only solution left is reduce the size of LAC, but, again I’m not sure because the mentioned LAC is in the big city. Dividing in 2 LACs will lead to high SDCCH congestion due to LU.
All BTSs use statistical 64 kb/s multiplexing (Normal load). Using High Load, again, maybe we need secondary Abis for each BTS.
Any comment on this?
Rex.8th June 2010 at 15:58 #62839PixGuest
The indicator “CCH_Paging_Command_Abis_discarded_cong_rate” actually refers to Paging Cmd which are well received by the BTS (= the Abis is NOT congested), but cannot b forwarded on the Air interface because the PCH is congested.
So forget about my previous post. The solutions are:
1/ reduce your LAC size (still…)
2/ increase the number of PCH blocks in the BCCH (= decrease AG_BLKS_RES by one, or rather set it to “1” and activate AG_PCH_PREEMPT = ENABLE)
3/ activate the multiple CCCH feature 🙂
The “multiple paging messages within one Paging Command” is not a commercial feature : it is just a way to reduce the RSL load on the Abis. It doesn’t impact the Air interface at all. It is free.
pix8th June 2010 at 21:48 #62840RexGuest
we’ll try with the solution under 2 and 3 first, and then see what happens.
Rex.11th June 2010 at 12:50 #62841RexGuest
1. In 6 cells (single cells) we changed AG_BLKS_RES from 4 to 3. As a result CCCH_Paging_Command_Abis_discarded_cong_rate for this object zone of 6 cells decreased from 5.5 % (aprox) to 1.8 %. The other indicator CCCH_AGCH_load_CS_Abis_max increased from 18% to 23% (that’s AGCH loading).
2. In 11 cells (micro cells and some single cells with 2 TRXs) we changed AG_BLKS_RES from 4 to 1 and activated AG_PCH_PREEMPT. Results for the object zone of these 11 cells: CCCH_Paging_Command_Abis_discarded_cong_rate decreased from around 6% to around 0.57 %.
Did we do a good thing, since paging congestion decreased?
Is the AGCH loading to much? I think better a bit increase in loading (AGCH) than an increase in paging congestion.
What do you think if we continue the same with all cells in the LAC?.
And, what if we activate AG_PCH_PREEMPT for the cells with AG_BLKS_RES=3?
There is an indicator CCCH_Paging_Multiple_Paging_Command_received_Abis (nb) and is around 660000. Is that mean we already have activated multiple CCCH feature. How to check that, I can’t see it among Cell or BSS parameters.
Rex11th June 2010 at 17:33 #62842PixGuest
First of all, thanks a lot for sharing your results so precisely, this is very important to me.
1. Max AGCH load = 23%, I think this is totally acceptable. I believe that it can increase up to 60% without negative impact on the call setup.
2. You cannot activate AG PCH PREEMPT if BLKS = 3. It can be activated only if BLKS = 0 or 1. However, you didn’t share your AGCH Load after activating the PREEMPTION. Was it still OK ?
I know the preemption looks fantastic, but there is something I don’t like about preemption : I am not sure the “PCH Load” and the “AGCH Load” indicators are correctly computed.
If I were you, I’d set:
BLKS = 1
PREEMPT = enable
And I would monitor MC925f very closely (Number of IMMEDIATE ASSIGN COMMAND messages received by the BTS on Abis and discarded due to congestion).
3. The Multiple CCCH : I am afraid your eyes are not going past the word “multiple” 🙂 “Multiple CCCH” and “Multiple Pagings” are different features !
The “Multiple Pagings Commands on Abis” mean that the BSC aggregates several paging requests into 1 Abis message, insttead of 1 request for 1 Abis msg.
There are two parameters to control this feature :
Defaults values indicates that this feature is activated by default. This is a new B10 feature, which is (therefore) activated during the migration. Keep it enable 🙂
pix14th June 2010 at 08:33 #62843RexGuest
sorry I forgot to mention that about AGCH load with BLKS=1 and PREEMPT activated. It was increased to around 30%.
Immediate_assign_command discarded due to congestion it remains in 0%.
What you think to not go directly to blks=1, first blks=2 see what happens. If it’s still OK then to go to blks=1.
Thank you very much for your proffesional suggestions,
Regards,14th June 2010 at 09:43 #62844PixGuest
The problem is that with blks = 2, the PCH preemption cannot be activated. Therefore, the AGCH might congest.
I am not saying it *will*, but it *could*.
Therefore, it is safer to try “BLKS = 1 with Preemption” rather than “BLKS = 2 without Preemption”
Anyway, just try it out, if there is congestion, just change the settings… Let me know what happens.
Pix14th June 2010 at 11:27 #62845RexGuest
Yes, I know about preemption should activate only when blks=1. But, I wanted to see how it looks without preemption with blks=2. Anyway, we’ll change to blks=1 and with preempt after that.
Thanks Pix, you really helped me.
Rex14th June 2010 at 13:22 #62846PixGuest
no problem, you’re welcome 🙂4th September 2012 at 06:40 #62847AyatGuest
we are going to swap a part of our network with 6 LACs replaced by 2 LACs…….
CCCH and SDCCH＝not combine
Reserved AGCH blocks (BS-AG-BLK-RES) BSAGBLKRES ＝ 2
Number of multi-frames of the PCH (BS_PA_MFRAMS) BSPAMFRAMS ＝ 5
So could you help me to know the imprtant notice about this swap5th September 2012 at 18:14 #62848pixGuest
look for the AGCH congestion rate and the PCH congestion rate. You can’t miss them, they are available per cell in the NPO.
Then, you can also monitor the AGCH radio load and PCH radio load. They should not exceed 60% (in theory), to avoid any possible blocking.
Finally, check the RSL load on the Abis : it is the physical channel that carries all those pagings. Look for : LAPD Congestion, in BTS object, or in Lapd object, I forgot.
Keeping only 2 AGCH blocks is rather low, focus especially on hourly AGCH radio load & congestion.