top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

In Intra frequency X2-AP Handover how UE will measure neighbour cell RSRP,RSRQ.

+2 votes
In Intra frequency X2-AP Handover how UE will measure neighbour cell RSRP,RSRQ.
posted Oct 6, 2015 by Mallikharjuna Reddy

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

1 Answer

0 votes

For intra freq HO, ENB needs to configure A3 event measurement to UE . Then UE performs neighbour cell measurement using A3 event and sends to eNB. After getting A3 meas eNB performs HO preparation using X2AP if x2 connection available between both eNB otherwise it performs using S1AP.

answer Oct 11, 2015 by Veer Pal Singh Yadav
Thank youVeer Pal Singh Yadav for your answer. But my question was Suppose in case of Inter frequency handover we are using Measurement Gap to measure Neighbours.In case of cell-reselection to Inter,Intra frequencies we are using DRX cycle  to measure Neighbours. So in Intra frequency handover my UE is in Active data session to Serving eNB in this situation how UE measures neighbour cell.
If  my concept was wrong please let me know.
In case of intra freq measurement UE does not requires meas gap because it is already tuned with same frequency. So its UE responsibility to make gap for doing intra frequency measurement. Pls get more detail in 36.133 3gpp specs in section E-UTRAN intra frequency measurements.
Similar Questions
+3 votes

On what basis, source eNodeB decides to consider RSRP or RSRQ for neighbor cell power measurement ?

+1 vote

Unlike for A3 and A5 events, for A6 event frequency offset is not considered while evaluating entering and leaving condition. Can anyone please explain this particular case ?

+2 votes

I have basic handover related query. How source eNodeB get to know when it has to trigger handover required message ? I mean to ask, how a source eNodeB come to know the threshold values of RSRP or RSRQ or both (related to target eNodeB) , required to do a successful handover towards eNodeB ? Is it due to network planning ?