No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


The user idlecut timer issue

Publication Date:  2014-11-07 Views:  100 Downloads:  0
Issue Description

me60 idle cut timer seems not correct

【Problem Details】 Config idle-cut function in pre-authentication domain, idle-cut timer set as 2 minutes/100K. subscriber do nothing after get the IP address of pre-authentication domain. test result show that ME60 always cut subscriber after around 5 is not the same as we expected(2 minutes)

Handling Process
Root Cause

system report subscriber traffic in fixed speed instead of real time:

type LPUK/LPUN board report traffic of 16 subscribers every 200 millisecond (80 subscribers/second)

type LPUA board report traffic of 64 subscribers every 200 millisecond (320 subscribers/second).

For example, the current subscribers of LPUK/LPUN board are:


<BAS>dis access-user slot


Slot : 2 Total user : 12412


Slot : 3 Total user : 15272


Slot : 7 Total user : 6908


LPUK/LPUN board report 80 subscriber traffic per second, so the cycle for report each subscribers traffic are:

Slot2 :12412/80 = 155 seconds

Slot3 :15272/80 = 190 seconds

Skot7: 6908/80 = 86 seconds


system will not report subscriber traffic immediately when subscriber online(it is no meaning to do that, because it must be 0), subscriber will be put into a report queue.


The configuration of idle-cut is 2 minutes, it less than traffic report cycle, under such condition system will use traffic report cycle instead of idle cut time. because system can judge it is idle or not only after get two traffic result, so the actual idle cut time is betwen traffic report cycle and two times of traffic report cycle .


This is a normal mechanisms.