Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | Korea Communication Market Data | List of Contributors | Become a Contributor |    
 
 
Section 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung   Korean Vendors
 
Private 5G | Edge Netmanias Private 5G Analysis KT SK Telecom Verizon AT&T Vodafone DT Telefonica China Mobile Optage NEC Fujitsu Microsoft AWS    
    HFR Ericsson Nokia Huawei Samsung Mavenir Affirmed Metaswitch Athonet Altiostar Airspan Kyocera Apresia    
CHANNELS     HFR Private 5G Solution (my5G)       my5G Solution Components       my5G Key Features        my5G Resources          
EMM Procedure 8 & 9. Handover and Cell Reselection with TAU
May 07, 2014 | By Netmanias (tech@netmanias.com)
Online viewer:
Comments (6)
21
Page 2 of 5

 

     

Table of Contents  

1. Introduction
2. EMM Case 8. Handover with TAU

3. EMM Case 9. Cell Reselection without TAU

4. EPS Entity Information

5. Closing

 

 

2. EMM Case 8. Handover with TAU

 

Figure 1 shows a handover procedure performed when UE in Connected state moves to a TA that it is not registered to. When the UE initially attached the network, MME selected TA1 and TA2 for the UE, and sent a TAI list = {TAI=1, TAI=2}, as included in the Attach Accept message. Initially, the UE was served through eNB2 (Cell 5 in it, to be exact) in TA1. Now it is moving toward eNB5 (Cell 13, to be exact) in TA3 which is not in the TAI list. As this document concerns intra-LTE handover only, we assume both eNB2 and eNB5 are connected to the same MME and S-GW.

 

 

Figure 1. Handover (to a non-registered TA)

 

Handover

 

In the figure above, as the UE moves toward eNB5, a handover event1 is triggered. The UE measures the signal strength of the serving cell and neighbor cells, and sends the results to eNB2, as included in the Measurement Report message. First, the source eNB (e.g. eNB2 above) chooses the type of handover to perform, X2 or S1. In X2 handover, it is the source eNB that selects the target eNB (e.g. eNB5 above), whereas it is MME in S1 handover. Next, handover is performed from eNB2 (Cell 5 in it to be more exact) to eNB5 (Cell 13 in it) (see the previous documents [2][3][4] for detailed handover procedure).

 

Tracking Area Update (TAU)

 

   1)   [UE → MME] TAU Request

When being handed over to the target eNB (eNB5), the UE knows eNB5 does not belong to its assigned TAs. Thus, as soon as the handover is completed, it sends a TAU Request (Update Type=TA Updating, GUTI, Last Visited TAI, KSIASME, NAS-MAC) message to MME, requesting TA update. At this time, the message includes the following information:

 

 

The TAU Request message is sent through an UL Information Transfer message from UE to eNB (as RRC message), and then through an Uplink NAS Transport (NAS-PDU (TAU Request), ECGI, TAI) message from eNB to MME (as S1AP message). The Uplink NAS Transport message, including the TAU Request message and the current cell’s ECGI and TAI, is forwarded to MME.

As the NAS security context has already been established between the UE and MME, the TAU Request message that the UE sends is integrity-protected with the NAS integrity key (KNASint). If the MME’s integrity check on the received TAU Request message fails, the MME performs user authentication and NAS security setup procedures (see the previous document [6]). In this document, we will only discuss cases where the MME succeeds the integrity check. 

 

   2)   [MME] TA Update: Allocating New TAs

Because the UE has moved to a TA that it is not registered to, the MME selects a group of TAs to allocate and configures a new TAI list for the UE. At this time, a new Globally Unique Temporary Identifier (GUTI) may also be allocated.

 

   3)   [UE ← MME] TAU Accept

The MME sends the newly selected TAs (and GUTI if applicable), as included in a TAU Accept (GUTI, TAI List) message. This message, after being encrypted and integrity-protected, is sent through a Downlink NAS Transport message from MME to eNB (as S1AP message), and then through a DL Information Transfer message from eNB to UE (as RRC message).

 

   4)   [UE → MME] TAU Complete

If a new GUTI was allocated, the UE sends the MME a TAU Complete message to acknowledge the receipt of the new GUTI.

 

Once the TAU procedure is completed, the UE, now with the new TAI list (and GUTI if applicable), can be served through eNB5.

 

Page 2 of 5
yuanjiantao 2014-11-16 10:51:55

thanks  very much 

yuanjiantao 2014-11-23 17:37:27

Hi,I have read almost all the documents about EMM topic,thanks for your summary ,it's very useful for me.

there is a typo in this document,"Abbreviations  KSI  ...." 

thanks again.


ohyong 2015-03-02 14:58:16

Many thanks for good material on HO with TAU. I am wondering about whether ENB-UE-S1AP-ID for both S1 Handover and TAU should be identical or not under HO with TAU. Target eNB has its ENB-UE-S1AP-ID during HO execution. And it also has its ENB-UE-S1AP-ID for TAU right after S1 HO.

So should ENB-UE-S1AP-ID be totally identical to both equal eNB(Target) and equal UE under above uttered two phases? Am I thinking right? Otherwise they should be different ENB-UE-S1AP-ID.
Please make sure whether equal or different ENB-UE-S1AP-ID should be related to Target eNB under HO with TAU.

Faisal Adeem Siddiqui 2015-06-24 19:26:12

Why the TAU is necessary after HO if the new cell belongs to different TA ? This can happen after the PS call ends as it happens in 2G/3G (LAC update happens at the end of CS call if LAC is changed during HO).

Ankush Taneja 2020-06-10 22:54:12

Hyperlink in point 3 for table of contents is wrong. It says "Cell reselection without TAU" whereas it should be with TAU

Mohanavamsi Gorantla 2020-07-09 15:05:14

While Cell Reselection , was with TAU .. 

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
Related Contents
08/01/2018
Netmanias Technical Documents
04/02/2018
Netmanias Technical Documents
12/20/2016
Netmanias Blog
08/22/2014
Netmanias Technical Documents
06/11/2014
Netmanias Technical Documents
04/23/2014
Netmanias Technical Documents
04/08/2014
Netmanias Technical Documents
03/21/2014
Netmanias Technical Documents
View All (177)
5G (8) Backbone (2) Backhaul (3) Blockchain (1) CDN (1) Carrier Ethernet (3) Charging (1) Cloud Native (1) Core (1) DHCP (4) ECM (2) EMM (16) EPS (2) Google (1) HLS (1) HTTP Adaptive Streaming (3) Handover (5) IPTV (4) Initial Attach (2) IoT (2) Korea (1) LTE (39) LTE Identification (2) LTE-A (1) MPLS (2) Mobility (2) NAT (7) Netflix (1) Network Architecture (3) Network Protocol (20) New Radio (1) OTT (1) PCRF (3) QoS (3) RCS (3) SDF (2) SDN/NFV (3) SK Telecom (1) Samsung (3) Security (5) Sk Telecom (1) Transparent Cache (1) Video Streaming (4) VoLTE (2) Wi-Fi (1) YouTube (2)
Password confirmation
Please enter your registered comment password.
Password