• When & Where: Seminars are generally (please, check the timeline and location before coming!) held on:
    • Wednesday afternoon at LINCS (14h-15h, Salle de Conseil) and
    • Thursday afternoon at Barrault (14h-15h, Amphi Saphir).
  • Contact us: if you wish to give a talk, please contact

[Next talks] [All talks]

08/10/2014Filippo Rebecchi (LIP6-UPMC/Thales)DROiD: Adapting to Individual Mobility Pays Off in Mobile Data Offloading
15/10/2014Leonardo Linguaglossa (Alcatel Lucent Bell Labs)Caesar: a content router for high-speed forwarding on content names.

Date:08/10/2014, 14h
Room:LINCS, Salle du Conseil
Speaker:Filippo Rebecchi (LIP6-UPMC/Thales)
Talk:DROiD: Adapting to Individual Mobility Pays Off in Mobile Data Offloading
Abstract:Cellular operators count on the potentials of offloading techniques to relieve their overloaded data channels. Beyond standard access point-based offloading strategies, a promising alternative is to exploit opportunistic direct communication links between mobile devices. Nevertheless, achieving efficient device-to-device offloading is challenging, as communication opportunities are, by nature, dependent on individual mobility patterns. We propose, design, and evaluate DROiD (Derivative Re-injection to Offload Data), an original method to finely control the distribution of popular contents throughout a mobile network. The idea is to use the infrastructure resources as seldom as possible. To this end, DROiD injects copies through the infrastructure only when needed: (i) at the beginning, in order to trigger the dissemination, (ii) if the evolution of the opportunistic dissemination is below some expected pace, and (iii) when the delivery delay is about to expire, in order to guarantee 100% diffusion. Our strategy is particularly effective in highly dynamic scenarios, where sudden creation and dissolution of clusters of mobile nodes prevent contents to diffuse properly. We assess the performance of DROiD by simulating a traffic information service on a realistic large-scale vehicular dataset composed of more than 10,000 nodes.DROiD substantially outperforms other offloading strategies, saving more than 50% of the infrastructure traffic even in the case of tight delivery delay constraints. DROiD allows terminal-to-terminal offloading of data with very short maximum reception delay, in the order of minutes, which is a realistic bound for cellular user acceptance.
Links:back to the list item, list top or summary top

Date:15/10/2014, 14h
Room:LINCS, Salle du Conseil
Speaker:Leonardo Linguaglossa (Alcatel Lucent Bell Labs)
Talk:Caesar: a content router for high-speed forwarding on content names.
Abstract:Today, Internet users are mostly interested to consume content, information and services independently from the servers where these are located.Information Centric Networking (ICN) is a recent networking vein which proposes to enrich the network layer with name-based forwarding, a novel communication primitive centered around content identifiers rather than their location.Despite several name-based forwarding strategies have been proposed, few have attempted to build a content router. Our work fills such gap by designing and prototyping Caesar, a content router for high-speed forwarding on content names.Caesar has several innovative features: (i) a longest prefix matching algorithm that efficiently supports content names, (ii) an incremental design which allows for easy integration with existing network equipments, (iii) support for packet processing offload to graphics processing units (GPUs), and (iv) a forwarding engine distributed across multiple line cards. We build Caesar as a small scale router, and show that it sustains up to 10 Gbps links and over 10 million content prefixes.In addition, GPU offload further speeds up the forwarding rate by an order of magnitude, while distributed forwarding augments the amount of content prefixes served linearly with the number of line cards, with a small penalty in terms of packet processing latency.The full design of a content router also includes a Pending Interest Table and a Content Store. The former is a data-structure used to store pending requests not served yet, while the latter is a packet-level cache used to temporary store forwarded data to serve future requests.We will discuss current and future work on the integration of Pending Interest Table and Content Store in our content router.
Links:back to the list item, list top or summary top