Integration of LTE with ndn

[Gustavo Gonzalez]

First of all please receive my greetings.

I post some doubts in this opportunity regarding to the integration of ndn with LTE.

1. I have been running lena-simple-epc example included in ns3. I realized that in the ueNodes it is not possible to verify the data transmitted and received by the node. However, when trace files are enabled it is possible to verify the traffic generated by these nodes. Is this a normal behaviour of the nodes? Should they show through the visualizer the traffic in real time that flows through them?.

2. ndn consists on interests and data messages. When I enable this feature in the script and I configure the remoteHost as a "producer" and some enbNodes 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?

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?

Thanks for the hints that could be provided to solve this issue.

Regards.

[Konstantinos]

HI Gustavo,

Please see inline.

On Monday, July 6, 2015 at 9:45:06 PM UTC+1, Gustavo Gonzalez wrote:

First of all please receive my greetings.

I post some doubts in this opportunity regarding to the integration of ndn with LTE.

1. I have been running lena-simple-epc example included in ns3. I realized that in the ueNodes it is not possible to verify the data transmitted and received by the node. However, when trace files are enabled it is possible to verify the traffic generated by these nodes. Is this a normal behaviour of the nodes? Should they show through the visualizer the traffic in real time that flows through them?.

What do you mean that the UE can't verify that data is transmitted/received? It depends on the protocols you use. For example TCP is acknowledged contrary to UDP. What other type of verification do you need? Be realistic, e.g. how do you verify that we received your post? Is it by getting a reply to your message?

I can't understand the last question. NetAnim visualisation of LTE networks is limited at the moment. 

 

2. ndn consists on interests and data messages. When I enable this feature in the script and I configure the remoteHost as a "producer" and some enbNodes 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?

As I mentioned in the previous question, NetAnim support of LTE is limited.

• Animate packets over wired-links and wireless-links (Limited support for LTE traces. No support for Ipv6) (https://www.nsnam.org/wiki/NetAnim_3.106)

 

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?

Unless you give us the full error, we can not be 100% sure. I would only speculate that the MTU for p2p is 1500 but that shouldn't raise a segmentation fault. Only drop of packets.

 

Thanks for the hints that could be provided to solve this issue.

Regards.

PS: Please keep discussions on the list. If you do not receive a reply right away might mean that other people are busy or do not know the right answer.

[Gustavo Gonzalez]

Thank you very much for the response Mr. Katsaros,

I will upload the code so you can simulate it and realize the points I highlight in the email.

Regards.

--
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/f6AGDdOd7ZM/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.

[Gustavo Gonzalez]

Dear Mr. Konstantinos,

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. I have been reading in the tutorials but I can't find hints to help to solve this issue.

Another question that I have is where I could find a detailed explanaition of the fields that compose the LTE structure. As you can see in the attachment three it is composed by many field and flags. I understand some of them but I would like to have a complete knowledge about it.

And finally why do I have packets of a length from 1094 and other from 1054? I suppouse that the 1094B is because of the tunneling (GTP) implemented by the EPC but what about the 1054B?.

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

Regards.

[Konstantinos]

Hi Gustavo,

Sorry but I can not help you with this. I can not run your scenarios as they require the NDN module.

Even though NSNSim is based on NS-3, it is a completely different simulator. 

I would suggest you to ask your question to the NDN mailing list http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim

It could be an issue with the GlobalRouting implementation of NDN.

K.

[Gustavo Gonzalez]

Ok Mr. Konstantinos,

I will put in touch with them.

Regards.

[Renato Cavalcante]

Hi all,

I'm implementing LTE networks with NDN in ndnSIM.

My scenario is:

     __________               ---------                   ___________

    | enbNodes | -----------| SGW |---------------| remote host |

    -----------------               ---------                   -------------------  

      _______

     |ueNodes|

     -------------

The problem happen in the wireless network (between ueNodes and enbNodes).

When the ueNodes is the consumer and enbNodes is the producer, the Interest packets has been send, but without Data packets received (figure1 attached).

When the ueNodes is the producer happen an error (figure2 attached).

What class and method should I customize?

I wait for your help.

Thanks in advance.

[Tommaso Pecorella]

Hi,

first of all, use a different thread next time. The one you're using is dating back to 2015.

About the specific error, it seems that you're trying to send unrecognized packets to the UE.

Mind that, at the moment, only TCP and UDP packets over IPv4 are handled.

Double check your code, and make sure to encapsulate your packets in the right way.

Cheers,

T.

[Renato Cavalcante]

Thanks Tommaso.

The NDN protocol stack, is different of the TCP/IP stack (figure in attachment).

I think that is need customize some class in the LTE module. 

Mainly the class that works IPv4, UDP and TCP, to insert NDN stack.

I don't know exactly which class and methods need of changes.

Thanks. 

[Tommaso Pecorella]

As I said, check what kind of packets are being sent to the nodes.

LTE must have UDP or TCP over IP. What's above them is not important.

About what classes can/should be modified to handle more protocols... well, you have to discover where the problem is before trying to solve it, and so far (also from the picture you sent) you haven't found the issue.

T.

[Renato Cavalcante]

Hi Tommaso, thanks for reply.

NDN architecture has only two packets kind: interest and data packets. 

In this packets not have IP and UDP or TCP. 

Besides that, NDN has the named-based routing (i.e., the interest packets names).

The consumidor (e.g., ueNode), send interest packets and it's expected the producer (e.g., eNodeB) response with data packets. 

This are the packets transmitted.

I dont know, if encapsule the ndn packet in ip packet, will be workable for me.

Since it will modify the routing and cache based on the name of the NDN interest packets.

I need to investigate this a bit more.

Again, thank you very much.

[Perumal Kuppuudaiyar]

Hi,

Have you resolved the issue? if you have resolved the issue, can you please share the working version?

Thanks.
Perumal

On Monday, July 6, 2015 at 10:45:06 PM UTC+2, Gustavo Gonzalez wrote:

[Renato Cavalcante]

Hi Perumal.

I don't resolved yet. 

I am working in others issues now and will back for this problem in coming soon.

Regards,

Renato.

[Furkan Küçük]

Any progress? I am working on integrating NDN and LTE module, however, no luck for now. I would be very appriciated if I could get some help!

[Renato Cavalcante]

Hi Furkan,

for now I'm working on other projects, however, I have interest in going back to this question.

I realize that besides me and you, others have interests in this matter, maybe we could work together.

Greetings.