[ndnSIM] Integration of ndn in LTE simulations

Gustavo Gonzalez gonzalezcga at gmail.com
Wed Jul 8 02:03:15 PDT 2015

Hello Spyridon,

Thank you very much for the information provided.

Regarding your answers, the segmentation alarm was related to the LTE
module. I fixed that one already.

And regarding the PIT table in the attachment you could verify the two
scenarios that I mention. The first one (lena-simple-epc_ueCons_
ueProd.cc) makes reference to two ueNodes which should exchange interest
and data packets as NDN establishes but the problem here is that the flow
of packets is not happening.

The second scenario (lena-simple-epc_enbCons_remoteHostProd.cc) makes
reference to a enbNode which forwards interest messages and the remoteHost
which provides the data messages according to the interests received. As
you can check here the NDN packets are transmitted without problems.

My main concern is why I cannot transmit ndn packets over the ueNodes and
it is possible over the wired nodes composing the rest of the LTE

Thank you very much for the hints you could provide me.


On Tue, Jul 7, 2015 at 3:17 AM, Spyridon (Spyros) Mastorakis <
spiros.mastorakis at gmail.com> wrote:

> Hi Gustavo,
> I am not familiar with the LTE principles, so I will try to answer the
> NDN-related questions.
> > 1. When I enable the ndn feature in the script and I configure the
> remoteHost (sort of Internet) as a "producer" and some enbNodes (base
> stations) as a "consumer" the ndn packets can be visualized without any
> problem but what it is important to analyse is the ndn traffic among
> ueNodes and here the problem because as soon as I set a ueNode as a
> consumer or producer, then the ndn traffic cannot be visualized. What could
> be the possible cause of this?
> The visualizer is a very unstable part of NS3. It is not a part of ndnSIM,
> thus I am sorry, but I cannot really help you with that. The only thing
> that we have done is to slightly modify some python bindings to introduce
> the NDN structures (i.e., CS, PIT, FIB). I would suggest that you send an
> email to the mailing list related to the visualizer or NS3.
> > When I set in the simulation the remoteHost as a producer and one
> enbNode as a consumer and changed the data payload length to 5000 it
> immediately showed me a segmentation alarm when I ran ./waf due to the MTU
> maximum length (1500B) but when I tried the same configuration with the
> ueNodes any alarm was shown. Do the ueNodes have a different behaviour or
> configuration that should be taken into account to run a simulation like
> this?
> What do you mean segmentation alarm? Is this related to NDN or the LTE
> module of NS3?
> >
> > The other thing is that I see the PIT table during the simulating and it
> can be seen that it is erased after issuing an ndn interest, letting me
> suppose that probably it received a data message using the reverse path and
> that's why the entry get erased but I am not sure though.
> >
> A PIT entry is being deleted in two cases:
> 1) When it is satisfied (i.e., the desired data packet has returned)
> 2) When it is unsatisfied (i.e., a timeout occurs indicating that the
> desired data packet has not returned)
> Let me know shall you need anything else.
> --
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> PhD Computer Science
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20150708/79dc762f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lena-simple-epc_ueCons_ueProd.cc
Type: text/x-c++src
Size: 8327 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20150708/79dc762f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lena-simple-epc_uenNodeCons_remoteHostProd.cc
Type: text/x-c++src
Size: 8320 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20150708/79dc762f/attachment-0001.bin>

More information about the ndnSIM mailing list