[ndnSIM] Cache hits: identifying the originator

Spyridon (Spyros) Mastorakis mastorakis at CS.UCLA.EDU
Wed Mar 16 11:30:59 PDT 2016

Hi Thiago,

one quick and dirty way to do that is to append the node id to the name of the data packet as soon as you retrieve it from a cache (following the approach of the link that you mentioned). Could you be more specific why you think this would not work here? It will work, but you have to do this trick in the forwarder class of NFD:

Specifically, you can do it right here:


As far as your second question is concerned, it is feasible to do it. You can add a counter variable to the forwarder class of NFD to figure out how many times you retrieved the same data packet from a node cache.

Hope that this helps!

Spyridon (Spyros) Mastorakis
Personal Website: http://cs.ucla.edu/~mastorakis/ <http://cs.ucla.edu/~mastorakis/>
Internet Research Laboratory
Computer Science Department

> On Mar 8, 2016, at 12:51 PM, Thiago Teixeira <tteixeira at engin.umass.edu> wrote:
> Dear ndnSIM list members,
> I am working in a wireless scenario with N consumers and M producers, connected via intermediate nodes (see example below)
> Consumer 1
> O
>    \
>       O  --  O --  O  --  O … O  --  O
>   / Rtr-1                           Rtr-n   Producer 1
> O
> Consumer 2
> Consumer 1 and 2 issue Interest requests via ConsumerCbr application (same namespace, e.g. /prefix/ ). As the number of routers increase, the link has more collisions and the Interest/Data packets get lost, generating more retransmissions and cache hits.
> Is there a way to know which node originated the cache hit? Also, is there a way to know if a cache hit was originated by a retransmission or by a first-time Interest request?
> I looked at “Finding Id of interest sending node <http://www.lists.cs.ucla.edu/pipermail/ndnsim/2016-March/002455.html>” but that solution seems to not fit in this scenario.
> Thanks for your help,
> Thiago

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20160316/915108c9/attachment.html>

More information about the ndnSIM mailing list