I wasn’t aware of such message, it’s interesting.
Paging overload is probably a BSC defense mechanism. The BSC has a paging processing limit, which is usually reached when you mapped too many LAC in your BSC.
Each BSC is handling 6 LAC. That means that the MSC is sending a lot of pagings to each BSC.
If you do something like this :
BSC 1 = LAC 1, 2
BSC 2 = LAC 3, 4
BSC 3 = LAC 5, 6
then each BSC is still handling the same amount of cells, and each cell is still sending the same amount of pagings (1/6th of the whole network pagings, assuming the 6 LAC have equal size)
but each BSC is handling 3 times less pagings -> the paging processing is much less than before.
Thanks for your help.
I found bellow description which can be useful for others, so I share with you:
in 220.127.116.11 of TS 48008. Brief description of the algorithm is provided as follows:
1. A total of 15 flow control levels are available.
2. The MSC first starts T5 (30s). In the period specified by T5, the system does not change the flow control level. After T5 expires, the system starts T6 (also 30s).
3. In the period specified by T6, if the system receives an Overload message again, it decreases the flow control level by 1 and restarts T5. If T6 also expires, the system increases the flow control level by 1 and restarts T5.
4. The preceding steps occur alternatively. To prevent restriction of all services, level 1 is set as the lowest flow control level. When the flow control level increases to level 15, the system ends flow control.
The flow control algorithm aims to protect the BSC against soaring traffic