top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Detection of too early handover for handover optimization

+2 votes
328 views

As per spec T store Ue Context timer is used so that if with in this time period RLF occuring and applying rrc connection re establishment to source then Too early handover counted.

At what time we should start T store UE Context timer at target ...

posted Oct 21, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button
Your question is not clear to me, can you please rephrase your question. Also give proper reference i.e. which spec etc, it helps to understand the exact issue.
As per spec 3GPP TS 36.300 version 11.7.0 Release 11  page 188
the Tstore UE Context when we should start ...

1 Answer

0 votes

Thanks for clarification -
This is the case of after a successful handover from a UTRAN cell to a target cell in E-UTRAN; the UE attempts to re-connect to the source cell or to another UTRAN cell. So where the timer at the target coming into the picture. (as per my reading of this case this is a protection mechanism)

answer Oct 22, 2013 by Salil Agrawal
Okay then how we will detect too early/wrong based on RLF report only ...ya we can use the timer T store UE Context
Don't you think these two are two independent cases, my thoughts only so ideally should not clash.
Similar Questions
0 votes

What is too early Handover and why does RLF have to occur even if its an early handover?

As per my understanding handover happens due to degrading RSRP/RSRQ and in case of ealry HO both source and NBR should have RSRP/RSRQ very close to each other. Then why does RLF happen. it should be more like a ping pong Handover

+3 votes

I know in optimizing a LTE network that we could measure RSRP,RSRQ ,Power and other conditions, but if all things goes right and still I am getting drop so how could I optimize it from UE side?

+5 votes

I have a C code like this:

int foo(void)
{ 
 int phase;
 . . .
 phase = 1;
 phase = 2;
 phase = 3;
 . . .
}

In case of -O0 gcc generates machine instructions for every assignment 'phase = ...'. But in case of -O2 gcc does not generate instructions for some assignments. Of course, this is correct. However, is there any way to tell gcc that 'phase' object is inspected by another thread, so it should not remove such statements?

0 votes

I am looking for detailed description of optimization flags that are provided by GCC compiler ?

+1 vote

My current compiler settings are

arm-none-eabi-gcc -Wall -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -fshort-double-mcpu=cortex-m4 -mthumb -Qn -Os -finstrument-functions -mlong-calls -c temp.c -o temp.o
so on for temp1, temp2... Etc

I am compiling multiple C files. and linker settings are

ld -r temp.o -o one.o
so on for temp1, temp2... Etc

I am linking multiple .O files. Also I am using linker script i.e link.txt (invoked externally as below)

ld -cref -Map map.txt -S -T link.txt -temp.o -lm -lc -lgcc
arm-none-eabi-gcc -Wall sample.o -O Firmware.abs

Now, At output I get .abs file of 140KB.

My Questions are
1. How to optimize (reduce size of .abs) by using compiler or linker specific options?
2. There are Number of NOT used global variables and Blank Function Calls in my C files (NO Dead Code!!!!). Is it possible to perform some link time optimization.
3. Please Elaborate as I am new to this, I have referred sites, gcc help and tried some "lto" options but NO reduction is size.
4. I also tried using -fdata-sections -ffunction-sections
But It has INCREASED my firmware.abs file size from KB to MB (yes it is MB!!!!) I also wondered WHY?
I am using codesourcery arm toolchain evaluation. It has gcc version 4.5.2

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...