Open mchristopoulou opened 1 year ago
Hi all, I tried to use nr channel, but I failed with the following error yy@yy:~/ms-van3t/ns-3-dev$ ./ns3 run scratch/v2p-vam-nr Sumo: wait for socket: 1s Loading configuration ... done. aborted. cond="protocolNumber != Ipv4L3Protocol::PROT_NUMBER && protocolNumber != Ipv6L3Protocol::PROT_NUMBER", msg="unsupported protocol 35143, only IPv4 and IPv6 are supported", +0.000000000s -1 file=/home/yy/ms-van3t/ns-3-dev/src/nr/model/nr-ue-net-device.cc, line=213 terminate called without an active exception Command 'build/scratch/ns3-dev-v2p-vam-nr-optimized' died with <Signals.SIGABRT: 6>. Do you have any Idea or can you give hints? Thank you mycode.txt
Hi all,
I am going through the lte-enb-rrc.cc file of ns3-mmwave https://github.com/nyuwireless-unipd/ns3-mmwave/blob/new-handover/src/lte/model/lte-enb-rrc.cc to better understand the secondary cell handover implementation. While comparing to the original lte-enb-rrc.cc file of the ns-3.38 version, I noticed that there are some trace sources missing regarding handover failure (referenced below).
I was wondering whether these trace sources are relevant or not to the ns3-mmwave handover implementation, and whether this was the reason they are not part of the ns3-mmwave code. For example, when there is a handover failure in the mmWave cells, then the UE switches to the LTE eNB (recorded in the LteSwitchStats.txt to my understanding), so there is no need for generating such sources? Probably, I am missing some of the specifics of the secondary cell algorithm, so any insights are appreciated.
I understand that the current version of ns3-mmwave uses the ns-3.38 version of ns3, which normally includes these trace sources.
The trace sources are the following and can be found in lines 2107-2127 in this link https://gitlab.com/nsnam/ns-3-dev/-/blob/ns-3.38/src/lte/model/lte-enb-rrc.cc :
Thank you