aodv + location-aided routing protocol in ns3

[Jack Lin]

Hello,

I am trying to implement aodv + LAR + energy judgement in NS3, so here is the idea:

(1)  When destination node receives RREQ, it will add it's position information and velocity information in RREP, then source node parse RREP to update information about destination node. 

(2) Before source node broadcast RREQ, positon information of Request Zone will be added in RREQ. So when intermediatenodes receive RREQ, I think it need to analysis RREQ and add some criteria(such as position information judgement and remaining energy information judgement) for each intermediatenode to determine to rebroadcast RREQ or not. 

(3) If the intermediatenode is not in Request Zone or it's remaining energy is too low, it will not reboadcast RREQ to save energy. 

Is that right? There are several questions confusing me:

(1) How to add position information judgement and remaining energy information judgement for each intermediatenode to determine to rebroadcast RREQ or not.

(2) How destionation node add information in RREP and how source node parse RREP.

(3) Are there any available source code about this simulation. There are many papers about this scheme, but I can't find the source code in the paper.  

Thanks a lot.

[Tommaso Pecorella]

Hi, answers in-line

On Friday, November 27, 2015 at 3:00:15 AM UTC+1, Jack Lin wrote:

Hello,

I am trying to implement aodv + LAR + energy judgement in NS3, so here is the idea:

(1)  When destination node receives RREQ, it will add it's position information and velocity information in RREP, then source node parse RREP to update information about destination node. 

(2) Before source node broadcast RREQ, positon information of Request Zone will be added in RREQ. So when intermediatenodes receive RREQ, I think it need to analysis RREQ and add some criteria(such as position information judgement and remaining energy information judgement) for each intermediatenode to determine to rebroadcast RREQ or not. 

(3) If the intermediatenode is not in Request Zone or it's remaining energy is too low, it will not reboadcast RREQ to save energy. 

Is that right? There are several questions confusing me:

 

(1) How to add position information judgement and remaining energy information judgement for each intermediatenode to determine to rebroadcast RREQ or not.

No idea, it's a decision specific to the protocol you're implementing. It should be explained in the papers.

A node can know its energy and position (position and movement direction / speed) though the appropriate objects installed in the node, i.e., the energy models and the position models. Study the manual.

 

(2) How destionation node add information in RREP and how source node parse RREP.

It depends on the protocol. I guess you'll have to modify the RREP and RREQ headers to add the fields for these infos. If the papers you're studying didn't mention/describe this part, then you can safely assume that they're just crapware.

Once you did extend the headers, you'll have the appropriate getters and setters, assuming that you did extend them in the right way.

 

(3) Are there any available source code about this simulation. There are many papers about this scheme, but I can't find the source code in the paper. 

As far as I know, no, you'll have to develop the simulation by yourself using a modified AODV. You can try asking the papers authors.

Cheers,

T.

 

Thanks a lot.

[Cong Lin]

Thanks Tommaso. Your suggestions help me a lot, and I guess I know how to work on. 

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

[Ali Alshehri]

Hello 

Dear Jack

I am working on idea close to yours, just have a question, how did you increase the size of the header packet, and how did you add the position of the nodes in the header? I am struggling with that, 

thank you