Task #3572

[ndnrtc-arc] Data transfer encounters failure in long-delay environment

Added by Peter Gusev over 5 years ago. Updated almost 5 years ago.

Start date:
Due date:
% Done:


Estimated time:


Problem description (per Yoneda-san):

Consumer stops receiving data over long-delay links after some time.

Problem investigation:

Consumer slowly "drifts away" from producer in issuing challenge interests. In other words, there is accumulating error in frame numbers which are used by consumer for issuing interests for a higher bitrate thread, it manifests itself in producer receiving more “old” interests (i.e. interests for the data that has already been outdated).

Here are some analysis findings:

  • Interest-Data exchange over time: data receipt declines (char 1.png attached)
  • same exchange, but per thread: now we see that “mid” thread suffers (this is the thread used by ARC for challenging data) (chart 2.png attached)
  • amount of new/old incoming interests on producer side (overall and per thread): one can see that mid thread received more old interests over time, while “low” thread didn’t get at all (that’s expected). In general, there should be no “old” interests at all (chart 3.png attached)


1.png (42.3 KB) 1.png Peter Gusev, 03/29/2016 03:14 PM
2.png (45.2 KB) 2.png Peter Gusev, 03/29/2016 03:14 PM
3.png (195 KB) 3.png Peter Gusev, 03/29/2016 03:14 PM
consumer-yoneda-main_camera-delay-test4.tar.gz (518 KB) consumer-yoneda-main_camera-delay-test4.tar.gz Peter Gusev, 03/29/2016 03:16 PM

Updated by Peter Gusev over 5 years ago

  • Description updated (diff)

Updated by Peter Gusev over 5 years ago

Per Yoneda-san:

Dear Peter-san

This is log file in case of 400ms(RTT) environment.
In this case, NDNRTC cannot shit fetching state, and then ARC is never called.

|P|+--L1--+|NDN Hub|+--L2--+|C|
Each link (L1 , L2) is 100Mbps, 200ms(both way)


Updated by Peter Gusev almost 5 years ago

  • Status changed from New to Closed

Also available in: Atom PDF