Professional Documents
Culture Documents
Does it
mean UE goes idle on Uu interface (possibly short inactivity timer on eNB) while it had
requested for some data earlier but before data reaches at S-GW, UE has already
moved Idle mode? Please explain
ANS;;; It is not necessary that UE has requested some data from IP world. Usually when
there is no data transmission happen for an UE for a configured time (user inactivity
timer) at the eNodeB, RRC Connection Release is triggered for that UE .
Once the PGW receives an IP packet for an UE , it forwards the packet to SGW and
since SGW doesn't have tunnel towards eNodeB for that UE, it sends downlink data
notification. As results, MME does paging for that UE.
Please capture and analyze the wireshark logs at PGW . Verify from IP traffic is coming
for that UE by using the filter.
This will help you to find out the exact reason .
I tested data path using the iperf application. Once the UE goes into idle mode and after
that I pump data for iperf . MME does paging .
Q---here are couple of procedures are defined which consist of NAS as well as RRC
signalling messages exchange.
I want to know, Is there any procedure exists in lte when an UE receives RRC
Connection Reconfiguration along with NAS message and responds back to network
with NAS message first and then Reconfiguration Complete to eNodeB.
Usually, I saw UE sends RRC Connection Reconfiguration Complete message first then
NAS response message.
ANS:-- First reconfiguration message will be sent & then NAS messages.
With SRB1 , NAS message will be piggy backed with RRC messages
AbuseComment
Q:--- There is no exchange of information transferred in RRCConnectionReconfiguration message used for handover. Handover in connection mode is completely taken
care by eNodeB, i think UE wont be having any invisibility. But eNodeB will ask UE to camp on neighbor eNodeB based on measurement report and this will not give information
about S1 or X2 handover.
ANS: hi,
To ascertain which HO has happened, we can use PLMN information to check which
PLMN(MME) you are connected to.
-> PLMN information comes in the broadcast information in SIB1.
In the UE logs we can check the PLMN information when the UE is attached to source
eNB and then
-> Check the PLMN information of the target eNB which we can check when UE has
made the non contention based RACH, again in the SIB1 message.
Now two scenario can happen:
Scenario 1:
If the PLMN in SIB1 in source eNB is NOT same as that of target eNB then their MME is
different.
Since MME is different so X2 HO cannot happen and in this case only S1HO can
happen.
Scenario2:
If PLMN in SIB1 in source eNB is same as that of target eNB then their MME is
different.
Here in this case we cannot identify from the UE logs.