lte x2 handover failure rate

[khc...@siswa.um.edu.my]

Hi

I am trying to simulate the performance of x2 handover in LTE-EPC and I want to see its failure rate. 

I had simulated the UEs to move in random direction from one enodeB to another enodeB. Using part of the codes from the lena-x2-handover.cc file, I was able to output the handover success messages on the command prompt. However, I am interested to know when a handover failure had occurred as well. Does anyone knows how to see Handover failure?

Thanks

[Nicola Baldo]

It is not straightforward to measure the handover failure rate, as the current LTE ns-3 model does not support radio link failure (see the documentation).
However, two LteEnbRrc methods  HandoverJoiningTimeout () and HandoverLeavingTimeout () are expected to be called when a HO fails. So, you could intercept these methods to infer that a failure has occurred.

By the way, it would be nice to have some trace sources exactly to intercept these timeout events... if someone could contribute a patch for this, it would be very much appreciated.

[khc...@siswa.um.edu.my]

Hi Nicola

Thank you for your reply.

I had tried to deliberately set theHandoverJoiningTimeout to a very low value using the following command to get a HO failure:

       Config::SetDefault ("ns3::LteEnbRrc::HandoverJoiningTimeoutDuration", TimeValue (MilliSeconds (1)));

I applied the command to the lena-x2-handover.cc file, but when I run it, the following message came out:

ubuntu@ubuntu-Lenovo-G500s:~/tarballs/ns-allinone-3.18/ns-3.18$ ./waf --run lena-x2-handover
Waf: Entering directory `/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build'
[1036/2199] cxx: src/lte/examples/lena-x2-handover.cc -> build/src/lte/examples/lena-x2-handover.cc.12.o
[2104/2199] cxxprogram: build/src/lte/examples/lena-x2-handover.cc.12.o -> build/src/lte/examples/ns3.18-lena-x2-handover-debug
Waf: Leaving directory `/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build'
'build' finished successfully (3.635s)
/NodeList/4/DeviceList/0/LteUeRrc/ConnectionEstablished UE IMSI 1: connected to CellId 1 with RNTI 1
/NodeList/2/DeviceList/0/LteEnbRrc/ConnectionEstablished eNB CellId 1: successful connection of UE with IMSI 1 RNTI 1
/NodeList/2/DeviceList/0/LteEnbRrc/HandoverStart eNB CellId 1: start handover of UE with IMSI 1 RNTI 1 to CellId 2
/NodeList/4/DeviceList/0/LteUeRrc/HandoverStart UE IMSI 1: previously connected to CellId 1 with RNTI 1, doing handover to CellId 2
msg="X2-U data received but no X2uTeidInfo found", file=../src/lte/model/lte-enb-rrc.cc, line=2001
terminate called without an active exception
Command ['/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build/src/lte/examples/ns3.18-lena-x2-handover-debug'] terminated with signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --command-template="gdb --args %s <args>").


I not sure how to use the debugger. But when I tried running the debugger as in the above message, the following output message is obtained:

ubuntu@ubuntu-Lenovo-G500s:~/tarballs/ns-allinone-3.18/ns-3.18$ ./waf --run <lena-x2-handover> --command-template="gdb --args %s <args>"
bash: lena-x2-handover: No such file or directory

Please advise

Thanks

[khc...@siswa.um.edu.my]

And so far, all the Handovers performed are completed successfully. I have used the traces for HO start and HO end successful provided. And the number of HO starts and HO end successful are the same. I believe this means that all HO are completed successfully rite.

I have tried it in scenarios with many UEs attached to an EnodeB moving at high speed and also with high level of noise. But I didn't get any HO failures.

Is there any other things I need to set to trigger a HO failure?

Thanks

On Monday, October 21, 2013 5:43:45 PM UTC+8, Nicola Baldo wrote:

[Umair Masood]

I can help you with the debugger. You need to install the ddd debugger like ( sudo apt-get install ddd ).. It will install the ddd debugger. To debug your problem you need to type in ( ./waf --run lena-x2-handover --command-template="ddd %s". It will take you to the Gui of the debugger. Since ddd is the GUI of gdb, you can see everything over there. I would recommend one thing that you shouldn't login from your root directory to install your debugger because sometimes it would produce errors like ( gdb: waiting to run ).

[khc...@siswa.um.edu.my]

Hi

Thanks.

I installed it using the Ubuntu Software Center feature.

After running the debug command, the following output messages is displayed:

Waf: Entering directory `/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build'
Waf: Leaving directory `/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build'
'build' finished successfully (1.580s)
Traceback (most recent call last):
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 97, in waf_entry_point
    run_commands()
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 155, in run_commands
    run_command('shutdown')
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Scripting.py", line 146, in run_command
    ctx.execute()
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Context.py", line 87, in execute
    self.recurse([os.path.dirname(g_module.root_path)])
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/.waf-1.7.11-edc6ccb516c5e3f9b892efc9f53a610f/waflib/Context.py", line 128, in recurse
    user_function(self)
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/wscript", line 922, in shutdown
    visualize=Options.options.visualize)
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/wutils.py", line 215, in run_program
    return run_argv(execvec, env, cwd=cwd)
  File "/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/wutils.py", line 132, in run_argv
    retval = subprocess.Popen(argv, env=proc_env, cwd=cwd).wait()
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1308, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

[KH Chua]

Hi

In the lte documentation, it is stated that Radio Link Failure is not supported because the RRC Idle mode is not properly modelled.

I like to ask, what are the challenges in modelling the RRC Idle mode? Is it the complexity?

If I want to try to model the RRC idle mode, is there any reference you can suggest?

Thanks

On Monday, October 21, 2013 5:43:45 PM UTC+8, Nicola Baldo wrote:

[KH Chua]

But i think i understand why such error message occurs already.

[Kwong Chiew-Foong]

Hi there KH Chua,

I'm just wondering if you can share with us why such message "X2-U data received but no X2uTeidInfo found" actually pop out during the Non-Ideal RRC operation.

CF Kwong

[C.F. Kwong]

Hi there,

I'm just wondering if you can share with us why such message "X2-U data received but no X2uTeidInfo found" actually pop out during the Non-Ideal RRC operation.

CF Kwong

On Saturday, 23 November 2013 23:40:00 UTC+8, Budiarto Herman wrote:

Hi,

For books, I'd recommend Chapter 7 of [1] for Idle mode and Section 22.7 of [2] for Radio Link Failure. You can also check the 3GPP standard specification, which is unfortunately scattered in several documents, e.g., TS 36.331, TS 36.304, TS 36.213, TS 36.133.

-budi-

[1] H. Holma, A. Toskala. (2009) "LTE for UMTS - OFDMA and SC-FDMA Based Radio Access".

[2] S. Sesia, I. Toufik, M. Baker. (2011) "LTE - The UMTS Long Term Evolution: From Theory to Practice".

[Ritu Borah]

pLEASE SEND ME THE CODES OF THIS PROGRAM

[Kwong Chiew-Foong]

Hello there Budiarto,

When I run UseIdealRRC = false, my simulation shows the error as follows:

msg="X2-U data received but no X2uTeidInfo found", file=../src/lte/model/lte-enb-rrc.cc

What it means actually? I'm using ns3.20. Is that a bug that has not fixed yet?

Thanks.

CF

On Saturday, 23 November 2013 10:40:00 UTC-5, Budiarto Herman wrote:

Hi,

For books, I'd recommend Chapter 7 of [1] for Idle mode and Section 22.7 of [2] for Radio Link Failure. You can also check the 3GPP standard specification, which is unfortunately scattered in several documents, e.g., TS 36.331, TS 36.304, TS 36.213, TS 36.133.

-budi-

[1] H. Holma, A. Toskala. (2009) "LTE for UMTS - OFDMA and SC-FDMA Based Radio Access".

[2] S. Sesia, I. Toufik, M. Baker. (2011) "LTE - The UMTS Long Term Evolution: From Theory to Practice".

torstai, 14. marraskuuta 2013 17.14.47 UTC+2 KH Chua kirjoitti:

[Kwong Chiew-Foong]

Hello there,

When I run UseIdealRRC = false, my simulation shows the error as follows:

msg="X2-U data received but no X2uTeidInfo found", file=../src/lte/model/lte-enb-rrc.cc

What it means actually? I'm using ns3.20. Is that a bug that has not fixed yet?

Thanks.

CF

On Monday, 18 November 2013 08:32:01 UTC-5, KH Chua wrote:

[Nicola Baldo]

Hi Kwong,

if you use this in your code (as in the previous posts)

Config::SetDefault ("ns3::LteEnbRrc::HandoverJoiningTimeoutDuration", TimeValue (MilliSeconds (1)));

then I am not surprised at all that you get the error "X2-U data received but no X2uTeidInfo found" when you have UseIdealRRC = false.
Please read the LTE model documentation (in particular the section on the RRC) to understand what HandoverJoiningTimeout is used for.

On Sunday, August 3, 2014 5:08:11 AM UTC+2, Kwong Chiew-Foong wrote:

Hello there,

When I run UseIdealRRC = false, my simulation shows the error as follows:

msg="X2-U data received but no X2uTeidInfo found", file=../src/lte/model/lte-enb-rrc.cc

What it means actually? I'm using ns3.20. Is that a bug that has not fixed yet?

Thanks.

CF

On Monday, 18 November 2013 08:32:01 UTC-5, KH Chua wrote:

But i think i understand why such error message occurs already.

On Monday, October 21, 2013 7:56:12 PM UTC+8, KH Chua wrote:

Hi Nicola

Thank you for your reply.

I had tried to deliberately set theHandoverJoiningTimeout to a very low value using the following command to get a HO failure:

      

[C.F. Kwong]

Hi Nicola,

Many thanks for your reply.

It seems that from the document, I realised that the current NS3-LTE module does not support handover failure, that's why the LTE document advice the user to do "tuning" to avoid handover failure. The only way I can think off to capture the handover failure is, like you said, harvest the information when the HandoverJoiningTimeout is triggered. The question is, how to harvest the information? Need to dig into the codes I guess, especially in the lte-enb-rrc.cc.

CF Kwong

On 4 August 2014 06:55, Nicola Baldo <nba...@cttc.es> wrote:

This message is eligible for Automatic Cleanup! (nba...@cttc.es) Add cleanup rule | More info

Hi Kwong,

if you use this in your code (as in the previous posts)

Config::SetDefault ("ns3::LteEnbRrc::HandoverJoiningTimeoutDuration", TimeValue (MilliSeconds (1)));

then I am not surprised at all that you get the error "X2-U data received but no X2uTeidInfo found" when you have UseIdealRRC = false.
Please read the LTE model documentation (in particular the section on the RRC) to understand what HandoverJoiningTimeout is used for.


On Sunday, August 3, 2014 5:08:11 AM UTC+2, Kwong Chiew-Foong wrote:

Hello there,

When I run UseIdealRRC = false, my simulation shows the error as follows:

msg="X2-U data received but no X2uTeidInfo found", file=../src/lte/model/lte-enb-rrc.cc

What it means actually? I'm using ns3.20. Is that a bug that has not fixed yet?

Thanks.

CF

On Monday, 18 November 2013 08:32:01 UTC-5, KH Chua wrote:

But i think i understand why such error message occurs already.

On Monday, October 21, 2013 7:56:12 PM UTC+8, KH Chua wrote:

Hi Nicola

Thank you for your reply.

I had tried to deliberately set theHandoverJoiningTimeout to a very low value using the following command to get a HO failure:

      

I applied the command to the lena-x2-handover.cc file, but when I run it, the following message came out:

ubuntu@ubuntu-Lenovo-G500s:~/tarballs/ns-allinone-3.18/ns-3.18$ ./waf --run lena-x2-handover
Waf: Entering directory `/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build'
[1036/2199] cxx: src/lte/examples/lena-x2-handover.cc -> build/src/lte/examples/lena-x2-handover.cc.12.o
[2104/2199] cxxprogram: build/src/lte/examples/lena-x2-handover.cc.12.o -> build/src/lte/examples/ns3.18-lena-x2-handover-debug
Waf: Leaving directory `/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build'
'build' finished successfully (3.635s)
/NodeList/4/DeviceList/0/LteUeRrc/ConnectionEstablished UE IMSI 1: connected to CellId 1 with RNTI 1
/NodeList/2/DeviceList/0/LteEnbRrc/ConnectionEstablished eNB CellId 1: successful connection of UE with IMSI 1 RNTI 1
/NodeList/2/DeviceList/0/LteEnbRrc/HandoverStart eNB CellId 1: start handover of UE with IMSI 1 RNTI 1 to CellId 2
/NodeList/4/DeviceList/0/LteUeRrc/HandoverStart UE IMSI 1: previously connected to CellId 1 with RNTI 1, doing handover to CellId 2
msg="X2-U data received but no X2uTeidInfo found", file=../src/lte/model/lte-enb-rrc.cc, line=2001
terminate called without an active exception
Command ['/home/ubuntu/tarballs/ns-allinone-3.18/ns-3.18/build/src/lte/examples/ns3.18-lena-x2-handover-debug'] terminated with signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --command-template="gdb --args %s <args>").


I not sure how to use the debugger. But when I tried running the debugger as in the above message, the following output message is obtained:

ubuntu@ubuntu-Lenovo-G500s:~/tarballs/ns-allinone-3.18/ns-3.18$ ./waf --run <lena-x2-handover> --command-template="gdb --args %s <args>"
bash: lena-x2-handover: No such file or directory

Please advise

Thanks


On Monday, October 21, 2013 5:43:45 PM UTC+8, Nicola Baldo wrote:

It is not straightforward to measure the handover failure rate, as the current LTE ns-3 model does not support radio link failure (see the documentation).
However, two LteEnbRrc methods  HandoverJoiningTimeout () and HandoverLeavingTimeout () are expected to be called when a HO fails. So, you could intercept these methods to infer that a failure has occurred.

By the way, it would be nice to have some trace sources exactly to intercept these timeout events... if someone could contribute a patch for this, it would be very much appreciated.

--
You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/VohVCgr66e0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

[C.F. Kwong]

Its just a simple code.

On 14 Oct 2014 00:59, "namrata katti" <namrata....@gmail.com> wrote:

hi,
 can you please send me that code of calculating number of handovers, where i am getting problem with it
 

[Budiarto Herman]

Hi,

For books, I'd recommend Chapter 7 of [1] for Idle mode and Section 22.7 of [2] for Radio Link Failure. You can also check the 3GPP standard specification, which is unfortunately scattered in several documents, e.g., TS 36.331, TS 36.304, TS 36.213, TS 36.133.

-budi-

[1] H. Holma, A. Toskala. (2009) "LTE for UMTS - OFDMA and SC-FDMA Based Radio Access".

[2] S. Sesia, I. Toufik, M. Baker. (2011) "LTE - The UMTS Long Term Evolution: From Theory to Practice".

torstai, 14. marraskuuta 2013 17.14.47 UTC+2 KH Chua kirjoitti:

[namrata katti]

[charef....@gmail.com]

i see Your Search about handover failure rate, You have reached a conclusion

plz help in code how calculate number of handover failure.