top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Please provide some details on Tracking Area List in LTE

+4 votes
691 views

I have some doubts about tracking area list in LTE. A TAL contains 1 or more TACs and a UE need not perform TAU while moving across TAs belonging to its TAL.

On the other hand, UE will be pagged in all the TACs included in its TAL. This could have been achieved by simply defining a bigger TA (i.e. TA equivalent to all the TAs in a TAL) ? Is it due to maximum number of eNBs limitation in a TA (typically 100 or less) ? Or is it intended for having UEs in the same area with different TALs ?

posted Nov 28, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

when UE moves within TAs mentioned in TAL, UE will not trigger TAU since MME already know that UE can belong to any of the TA mentioned in the list. When UE moves to a tracking area which is not in the TAL. UE send TAU either UE in RRC-IDLE or RRC - connected.

There is tradeoff between TA size and frequency of TAU. So if TA size is too less then frequency of TAU increases. And when TA size is too large then MME will sends paging message to more number of eNodeB when UE is in RRC -IDLE mode and downlink data is coming for him from then core network.

So a wiser decision need to be taken with respect to TA size.

answer Nov 28, 2013 by Vimal Kumar Mishra
Similar Questions
+1 vote

I know tracking area list is provided by MME to UE to track UE in idle mode. I want to know what is the purpose of having different kind of tracking area type like "consecutive tracking area codes belonging to one plmn" , "non-consecutive tracking area codes belong to one PLMN".

+1 vote

Does the MME or LTE core network assign the same list of TAI to each user originates from same cell ?
If answer is "no" then what would be all possible methods to manage this task ?

+3 votes

Can I change tracking are code on the fly for a cell/eNodeB ? If yes then what will happen with the connected/idle UEs ?

+1 vote

I need to access ClearQuest programatically using Perl. I just found ClearQuest OSLC REST API. Client is planning to use ClearQuest web 7.1.1. I read that it comes with OSLC REST API out the box.
Can someone please provide me some examples on how I can access the CQ through Perl using this API.

...