Regarding your part of the question: "what will happen in case UE moved

out LTE coverage and switched to 3G/2G is it called redirection." There are
3 concepts.
1) Redirection: This decision is entirely left to the network and happens
when the UE is in connected mode. The network generally sends the UE
an "RRC Connection Release" with some redirection information. So, now
the UE moves to Idle mode and based on the redirection information
received, it tries to camp on that frequency (maybe of the same RAT or a
different RAT).
2) Handover: This is again triggered by the network. The UE has to be in
connected mode. The network requests UE to send measurement reports
of serving cell/neighbour cell etc. And based on the measurements, it
initiates handover.
3) On the other hand, if UE is in idle mode and is gradually moving out of
LTE coverage area, then UE decides to reselect to the most preferred RAT
based on the coverage around.
Cell Reselection:
When UE is camping on a cell, it attempts to reselect a better cell. The
UE perform the following steps:
Step 1: Measurements of neighbouring cells
Step 2: Evaluation of the measured results of neighbouring cells
Step 3: Cell reselection and access verification Cell Redirection:
The redirection procedure can be performed by the eNodeB by sending an
RRCConnectionRelease message including redirection information in
redirectedCarrierInfo. This applies also to CSFB. Use with cell reselection
priority other way, is that the eNodeB can optionally include
idleModeMobilityControlInfo in the RRCConnectionRelease message in
order to provide information about cell reselection priority dedicated to the
UE.

Cell reselection happens in IDLE mode to camp on better cell whereas Cell
redirection happens in Connected Mode, generally when directed to 2G or
3G system.
Here is an example of a log that I have examined. The Vendor in this case
is Huawei. 3G(Before) 10.48.49 4495 48.49,2 U SM Activate PDP context
request 10.48.49 8453948.49,2 U RRC DCCH- UplinkDirectTransfer
10.48.49 8454048.49,3 D RRC DCCH- DownlinkDirectTransfer 10.48.49
4496 48.49,3 D SM Activate PDP context reject LTE(after) 10.49.01 7733
49.01,2 D LTE-RRC BCCH:SCH- SystemInformationBlockType1 10.49.01
7734 49.01,2 U LTE-RRC CCCH- RRCConnectionRequest 10.49.01 7735
49.01,3 D LTE-RRC CCCH- RRCConnectionSetup 10.49.01 1852 49.01,4
U LTE-NAS EMM- Tracking area update request 10.49.01 7736 49.01,4 U
LTE-RRC DCCH- RRCConnectionSetupComplete 10.49.01 1853 49.01,5
D LTE-NAS EMM- Tracking area update reject 10.49.01 7737 49.01,5 D
LTE-RRC DCCH- DLInformationTransfer 10.49.01 7738 49.01,5 D LTERRC DCCH- RRCConnectionRelease 10.49.02 7739 49.01,5 U LTE-RRC
CCCH- RRCConnectionRequest 10.49.02 7740 49.01,6 D LTE-RRC
CCCH- RRCConnectionSetup 10.49.02 1854 49.01,6 U LTE-NAS EMMAttach request 10.49.02 7741 49.01,6 U LTE-RRC DCCHRRCConnectionSetupComplete 10.49.02 1855 49.01,7 D LTE-NAS EMMIdentity request 10.49.02 7742 49.01,7 D LTE-RRC DCCHDLInformationTransfer 10.49.02 1856 49.01,7 U LTE-NAS EMM- Identity
response 10.49.02 7743 49.01,7 U LTE-RRC DCCHULInformationTransfer 10.49.02 1857 49.02,1 D LTE-NAS EMMAuthentication request 10.49.02 7744 49.02,1 D LTE-RRC DCCHDLInformationTransfer 10.49.02 1858 49.02,3 U LTE-NAS EMMAuthentication response 10.49.02 7745 49.02,3 U LTE-RRC DCCHULInformationTransfer 10.49.02 7746 49.02,4 D LTE-RRC BCCH:SCHSystemInformationBlockType1 10.49.02 1859 49.02,4 D LTE-NAS EMMSecurity mode command 10.49.02 7747 49.02,4 D LTE-RRC DCCHDLInformationTransfer 10.49.02 1860 49.02,4 U LTE-NAS EMM- Security
mode complete 10.49.02 7748 49.02,4 U LTE-RRC DCCHULInformationTransfer 10.49.03 7749 49.03,3 D LTE-RRC DCCH-

UECapabilityEnquiry 10.49.03 7750 49.03,3 U LTE-RRC DCCHUECapabilityInformation 10.49.03 1861 49.03,3 D LTE-NAS EMM- Attach
accept 10.49.03 1862 49.03,3 D LTE-NAS ESM- Activate default EPS
bearer context request 10.49.03 7751 49.03,3 D LTE-RRC DCCHSecurityModeCommand 10.49.03 7752 49.03,3 U LTE-RRC DCCHSecurityModeComplete 10.49.03 7753 49.03,3 D LTE-RRC DCCHRRCConnectionReconfiguration 10.49.03 7754 49.03,3 U LTE-RRC
DCCH- RRCConnectionReconfigurationComplete 10.49.03 7755 49.03,3 D
LTE-RRC DCCH- RRCConnectionReconfiguration 10.49.03 7756 49.03,4
U LTE-RRC DCCH- RRCConnectionReconfigurationComplete 10.49.03
1863 49.03,4 U LTE-NAS EMM- Attach complete
UE initiates TA updat e2 scenarios 1.When TA change(UE reselect a cell
that does not belong the TAI list provide by MME)(Attach/detach) 2.When
T3412 time expires and check GUTI=GUMMEI+M-TMSI
GUMMEI=MCC+MNC+MMEGI+MMEC M-TMSI = 's the MME TMSI
assigned by MME 3.TAI=MCC+MNC+TAC because from your log UE can
location registration (attach procedure
rrcConrequest>setup>complete>Authentication request >respone>Security
mode command>complete>Activate default EPS bearer context request
>EMM- Attach complete) but UE can not access the EPC(MME,SGW,PDN-GW) or EPC does not allow access of UE 1.TA cluster overlaping
another TA(pagging all time) just men diff MME?==>LSTCELL 2.have TA
list (TAI assing by NME same MME area) NB-TA (LAC NB same UMTs
system) 3.TAC(Traking area Code) just correct? 4.SIB1&SIB2= true?
==>LST CELLSIMAP 5.Co-PCI ? 6.Re-selecct==>LST
CELLRESEL,CELLSEL Cheer Cheer
In fact I have a TAU Reject whenever coming from the 3G I have a Activate
PDP context reject, so I believe that the MME didn't open a default EPS
Bearer on 4G technology and UE once failed the TAU must again make the
attach.A strange thing that I noticed from the log, is that after the attach,
the UE make often a TAU request with repeated TAU accept.

Most of the existing LTE Networks, up to recently, in the USA did not have
the EPC configured for UMTS>>LTE PDP context continuity. So I think it
might be the case for you. For the TAU request with TAU accept, my
thinking is that was a detach (from 3G) and a new attach in LTE.
-Accessibility
-Drop Rate
-Rab Utilizzation
-Average HSDPA/HSUPA simultaneous active user
-Inter system H.O.
-Rab Succes Rate HSDPA/HSUPA-HSDPA MAC-d average user
throughput
-IRATHO per Call
-Volume CS in Mbyte
-Volume di Traffico HSUPA/HSDPA in Mbyte livello MAC-D-CS Fallback to
3G Preparation Rate-CQI And Modulation
-INTRA-Frequency Handover
-Redirection
-INTER-RAT HANDOVER
L'analisi si prefigge di individuare eventuali criticit ed attuare le opportune
azioni per il corretto ripristino della funzionalit della Rete di accesso
mobile-Risoluzione della criticit presente su rete cella;l'analisi pu essere
sintetizzata nei seguenti punti:1)Individuare la pi opportuna azione da
eseguire per il ripristino della corretta funzionalit della cella (in conformit
con i target fissati).2) Assegnare l'azione correttiva.3) Monitorare
l'implementazione dell'azione e le sue conseguenze sulle prestazioni della
cella.Parametrizzazione di Rete Mobile [3G/4G-LTE] - Features 2G/ 3G/ 4G
Sperimentazione 4G Ottima conoscenza delle Features adottate nella RAN
14.0 (Huawei) / RU 40 (NSN):
-Control Channel Parallel Interference Cancellation(Phase 2)
-Dynamic Configuration of HSDPA CQI Feedback Period-Load-based
Uplink Target BLER Configuration
-Dynamic Target RoT Adjustment

-Service-Based PS Handover from UMTS to LTE

-Fast CS Fallback Based on RIM
-Layered Paging in URA_PCH
-Intelligent Access Class Control
-Interference Cancellation
-PS Power Control-Fast LTE/3G Reselection at 2G CS Call Release-RACH
Storm Filtration
-Automatic Level Control
-Dynamic Multiple CCCH