Forcing a Tracking Area Update: How 4G Uses TAI Lists in Special Scenarios
A device normally sends a Tracking Area Update (TAU) when it enters a Tracking Area that is not in the TAI list it currently holds. There are other triggers too, such as periodic timer expiry, but this post is about something more specific: special scenarios where the network arranges its Tracking Areas and TAI lists on purpose, so that a device must update its location when a particular change happens.
Here are three examples from the specification:
1. NB-IoT and WB-E-UTRAN
The network is configured so that no Tracking Area contains both NB-IoT and WB-E-UTRAN cells, and the MME never puts both kinds in one TAI list. So when a device moves between the two, it must perform a TAU, and the MME learns the new RAT type from the Tracking Area the eNodeB reports.
2. Satellite Store and Forward (S&F) mode
A satellite operates either in S&F mode or not, never both at once. S&F cells and non-S&F cells use different Tracking Areas, so a UE moving between them is triggered to perform a TAU.
3. 15 EPS bearers per UE
Some MMEs support 15 EPS bearers per UE and some do not. The MME allocates a TAI list with homogeneous support, so a UE moving between the two kinds of MME performs a TAU in either direction.
Features like User Plane CIoT EPS Optimisation, 15 bearers per UE, and satellite access may all require the MME to adapt how it builds the TAI list.
The takeaway: the same idea is reused for very different problems. Separate areas with different characteristics into different Tracking Areas or TAI lists, and crossing the boundary forces a location update that lets the network respond.
It is a small design choice, but it keeps signalling simple and the network in sync with the device. What other 3GPP design patterns have caught your eye? Let me know in the comments.
#4G #LTE #3GPP #Telecom #NBIoT #SatelliteIoT #EPS #MobileNetworks