- This topic has 18 replies, 1 voice, and was last updated 8 years, 4 months ago by Irshad.
17th March 2010 at 08:57 #61521HellsingGuest
Hi all, i’m new @ Core staff and would like to know if Routing Area update is presented on Gn interface?? because we swapped Gn traffic over IP MPLS backbone and suddenly RAU decrease, is this normal? Thanks in advance17th March 2010 at 10:17 #61522PixGuest
“Gn” interface, between SGSN and GGSN ? I cannot find any valid reason why it would behave in such a way. It is not normal, and should not even be possible ! 🙂
Have you done any other change ? For example, activation of the Gs interface, or actvation of LA/RA combined update ? Change of LAC planning, or RAC planning, on the radio side ?
pix17th March 2010 at 11:03 #61523HellsingGuest
Changing LAC/RAC @ Radio side i think yes, another detail that we have Two SGSN and we finish migration from old SGSN last weekend but the problem just apperead after swap on IP/MPLS backbone and i think it’s not a possbile reason for this problem.
could the problem be related with Inter SGSN RA?17th March 2010 at 13:50 #61524pixGuest
yes, if there is only one SGSN instead of 2, then you should see less inter-SGSN RA updates. But the number of RAU (inter+intra) should be the same as before.
The RAU is a procedure starter by the MS. The MS doesn’t care about your Gn interface… it just cares about the RA in the new cell : same or different than before ?
If different, then a RAU is done.
I’m not familiar with interSGSN RAU : are they going through the GGSN ? I thought the SGSN would contact the other SGSN directly… (to be verified !)18th March 2010 at 09:49 #61525HellsingGuest
Whats exactly the relation betwenn periodic RA and normal RA? shoul the number be the same?18th March 2010 at 11:09 #61526pixGuest
periodic RA : after expiry of a timer, the MS is forced to perform a RA update, even if it didn’t move
normal RA : the MS has moved and changed RA, physically.18th March 2010 at 11:17 #61527HellsingGuest
so i think the only reason that periodic RA change is LAC/RAC redesign, or timer change? isn’t it18th March 2010 at 13:10 #61528PixGuest
Periodic RA increase is due to timer change only.
Check out 23.060
The Periodic RA Update Timer function monitors the periodic RA update procedure in the MS. The length of the periodic RA update timer is sent in the Routeing Area Update Accept or Attach Accept message. The periodic RA update timer is unique within an RA. Upon expiry of the periodic RA update timer, the MS shall start a periodic routeing area update procedure.
and also 24.008
Periodic routing area updating is used to periodically notify the availability of the MS to the network. The value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate “periodic updating”. The procedure is controlled in the MS by timer T3312. When timer T3312 expires, the periodic routing area updating procedure is started. Start and reset of timer T3312 is described in subclause 184.108.40.206.
So the timer is called T3312 ! Default value is 54mn.
The value of this timer is used if the network does not indicate another value in a GMM signalling procedure. For example in the Routing Area Update Accept : the SGSN can indicate a different timer.
Pix19th March 2010 at 08:06 #61529HellsingGuest
Thanks pix, but really i’m a little bit confused about this, as in our case no LAC/RAC change was done and no timer change and RAU and periodic RAU decreased. any other suggestions?22nd March 2010 at 14:50 #61530HellsingGuest
In the same context, i take a Gn (Inter SGSN) Trace with wireshark to investigate about Inter SGSN RAU failure, how can i find Inter SGSN RAU message among my trace?22nd March 2010 at 15:28 #61531pixGuest
you should read the 3GPP documents I pointed out earlier ^^
220.127.116.11.2 Inter SGSN Routeing Area Update
The new SGSN sends SGSN Context Request (old RAI, TLLI, old P TMSI Signature, New SGSN Address) to the old SGSN to get the MM and PDP contexts for the MS.22nd March 2010 at 15:48 #61532HellsingGuest
Thanks pix , i’m on it now.23rd March 2010 at 10:06 #61533HellsingGuest
ok for the whole procedure but in order to investigate about Inter SGSN RAU failure (Nokia SGSN), what are the ways to investigate? otherwise what are the IP frames in the trace that could be helpful?17th June 2010 at 09:29 #61534kamal kotechaGuest
You must have same RAC in unique PAPU..Otherwise it will cause failure & 2955 will be triggered..
Ultimately,RAC planning should be done in such as way that same RAC remain unique between PAPU…you should use same RAC in bsc such a way that you can manage these BSC in same PAPU..Thats all..!30th June 2011 at 11:40 #61535thakurGuest
How to analysis call fail in 3G