- This topic has 13 replies, 1 voice, and was last updated 4 years, 2 months ago by
Ahmed.
-
AuthorPosts
-
6th January 2009 at 11:13 #55292
RL
GuestDear all,
Could you please share for the periodic location update period that we should set in the network.
In my network we set 10 hour. Is it too much???
Thank you very much.
6th January 2009 at 13:20 #55293riz
Guesthi RL,
yeah i think 10 hour is very high, in our network its 6 hours which is a standard value as far as networks in our country are concerned ๐
6th January 2009 at 15:15 #55294Pix
GuestHello,
The value of T3212 sets the duration between two periodic location update. Typical value is 3 or 4 hours.
If too short, then resources are occupied too much with signalling (SDCCH, BTS processor, MSC processor, VLR, etc.)If too long, then it can happen that MS are not accessible anymore (battery died, for example) but the MSC still believe they can be paged.
The drawbacks of a longer value are rather inconsequential … It looks like it’s better to have a value too long than too short ๐
Now, be careful than the implicit detach timer “t” set in the MSC/VLR is longer than the T3212. Because if it’s shorter, then it means that “t” expires before T3212: the IMSI is detached by the VLR, but the MS is not aware of that…
6th July 2010 at 05:22 #55295hihi
Guestwhere is the timer?in VLR OR
MS6th July 2010 at 06:35 #55296Bijoy
GuestT3212 is a cell Timer.
Br\\
Bijoy27th July 2010 at 08:28 #55297Tanuj
Guesttypically we are using 4 hours as std. value in our nw, the value is gioven as 40 (1=6 minutes so 40*6=240 mins.
2nd August 2010 at 06:36 #55298AYAT
GuestPix
is (โtโ detach timer
the the timer that network will purge the sub
in our network T3212=2.9 H
and network will delete the subscriber after 24 H
is that time thesame for (โtโ detach timer ??
2nd August 2010 at 08:54 #55299ayat
Guesthi pix
1. T3213(periodical timer in Radio) = 174min
2. t(periodical timer in VLR) = 240min (large than T3213, so it is available if the T3213 is not successful)
3. purge timer = 24Hoursbut ,we have a problem with high nmber of absent subscriber
4th August 2010 at 08:27 #55300ffflyer
GuestT3212 value varies significantly between networks, I’ve seen values as long as 12 hours and as short as 2 hours. It really depends on a strategy, LA shapes and sizes and signaling transport capacity. Have in mind that short T3213 value also affect battery life time for MS, especially for low consuming customers.
10th August 2010 at 13:00 #55301SKCG
GuestI think 4 hours is fine at most cases.
18th August 2010 at 08:05 #55302AK
GuestI guess 3 hrs for T3212 is widely accepted in the world. But it depends on various parameters.
23rd August 2010 at 10:28 #55303Ayat
GuestHi pix
Thanks for your support
but i am afraid i did not umderstand why do we redude the VLR time (purge time)??
could you explain
boz as i said we have high map error absent sb.i think it will increase this error
24th August 2010 at 12:20 #55304pix
GuestAyat,
you said:
———————–1. T3213(periodical timer in Radio) = 174min
2. t(periodical timer in VLR) = 240min (large than T3213, so it is available if the T3213 is not successful)
3. purge timer = 24Hours————————
the t(periodical timer in VLR) is at a good value, so IMO it means that the MS which are no more “available” are quickly marked as “detached” by the VLR.
So my previous recommendation is actually already done in your network ๐
the purge timer would not influence your KPI (afaik).i can’t help more…
pix15th January 2020 at 15:49 #71214Ahmed
Guestthe Timer was set to one hour in our NW so i have changed it to 4 Hours on 2G and 3G w, what are the expected KPI’s that could improve , any idea ??
-
AuthorPosts
- The forum ‘Telecom Design’ is closed to new topics and replies.