Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

Dynamic network configuration to target multicell scenarios for moving UE #63

Open
rtobi opened this issue Jul 1, 2021 · 2 comments
Open

Comments

@rtobi
Copy link

rtobi commented Jul 1, 2021

Hello!
I hope to find some help here. I am using INET 3.6 but most likely the problem also exists in newer versions:
Once UEs remain in the same cell D2D communication works very well, both using multicasts and unicasts. At the moment where one UE switches to another cell, only multicasts are working for this UE. Unicasts are also not working again once all UEs completed their handover and are located in the new cell.
While trying to hunt the problem down, I have come to suspect that the problem is the IPv4NetworkConfigurator as it only supports static routes. I suppose that once a UE switches cell and the network topology changes, the routing to the corresponding eNodeB is not appropriate anymore. Can my assumption be correct?
Is there a way to circumvent the problem? I tried to use the RIP routing, but it probably only works once the routing tables are updated. I also tried to reinitialize the IPv4NetworkConfigurator and tried to recompute the routes (IPv4NetworkConfigurator ::computeConfiguration()). Unfortunately, I did not have success. Maybe I can setup the network in a different way to not run into this problem?

Many thanks for any ideas and comments!

@jaquesantoss
Copy link

Hi, I'm trying to use SimuLTE for VANET simulation, but I'm getting the following error:
Error NLOS urban macrocell path loss is valid for d < 5000 m --in module (LtePhyUeD2D)
I saw somewhere that went through something similar, could you tell me how you solved it? Thank you in advance.

@rtobi
Copy link
Author

rtobi commented Jul 21, 2021

Hi,
not a solution but an explanation: (riebl/artery#160).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants