But network baseline is 1/16.
nB=T Used to calculate the number and position of Paging Occasions (PO) and Paging Frames (PF).
The numerical value of nB depends on the value of the defaultPagingCycle (T) and can be set to one of the following values:
4T, 2T, T, T/2, T/4, T/8, T/16, T/32.
When nB is set to T, 2T or 4T, it determines the number of POs per PF, and the PO position in PF.
When nB is set to a value smaller than T, it affects the System Frame Number of the PF, the position of PO in the PF, and also distribution of UE into groups with the same PF.
When nB is set to smaller value, amount of groups is smaller, but amount of UEs inside each groups is larger. When nB is set to a larger value, amount of groups is larger but amount of UEs inside each groups is smaller.
If categoryMAccess is enabled and nBBr is set to the default value (NOT_PRESENT) then further restrictions apply. If highestSupportedCeLevelBr = 0 then nB should be selected from the following available options (T, T/2, T/4, T/8, T/16, T/32) due to the half duplex nature of Cat-M devices. If highestSupportedCeLevelBr = 1 then nB should be selected from the following available options (T/8, T/16, T/32) due to repetitions.
Dependencies: nB=T4 can not be used in combination with specialSubframePattern = 5 on MO EUtranCellTDD, see 3GPP TS 36.213.
Takes effect: After all the cells in the RBS have been locked, and subsequently been unlocked.
I checked near by sites. All have same setting of nb with no paging discard.
I think it not so easy to get the root cause until we review the trace from Core side.
But moreover if we have any other weapon to reduce it , even it Work
At list something we can feedback.