<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/>
    <title>Project-Team:ASAP</title>
    <link rel="stylesheet" href="../static/css/raweb.css" type="text/css"/>
    <meta name="description" content="Overall Objectives - Structure of the team"/>
    <meta name="dc.title" content="Overall Objectives - Structure of the team"/>
    <meta name="dc.subject" content=""/>
    <meta name="dc.publisher" content="INRIA"/>
    <meta name="dc.date" content="(SCHEME=ISO8601) 2014-01"/>
    <meta name="dc.type" content="Report"/>
    <meta name="dc.language" content="(SCHEME=ISO639-1) en"/>
    <meta name="projet" content="ASAP"/>
    <!-- Piwik -->
    <script type="text/javascript" src="/rapportsactivite/piwik.js"></script>
    <noscript><p><img src="//piwik.inria.fr/piwik.php?idsite=49" style="border:0;" alt="" /></p></noscript>
    <!-- End Piwik Code -->
  </head>
  <body>
    <div class="tdmdiv">
      <div class="logo">
        <a href="http://www.inria.fr">
          <img style="align:bottom; border:none" src="../static/img/icons/logo_INRIA-coul.jpg" alt="Inria"/>
        </a>
      </div>
      <div class="TdmEntry">
        <div class="tdmentete">
          <a href="uid0.html">Project-Team Asap</a>
        </div>
        <span>
          <a href="uid1.html">Members</a>
        </span>
      </div>
      <div class="TdmEntry">Overall Objectives<ul><li><a href="./uid3.html">General objectives</a></li><li class="tdmActPage"><a href="./uid8.html">Structure of the team</a></li></ul></div>
      <div class="TdmEntry">Research Program<ul><li><a href="uid15.html&#10;&#9;&#9;  ">Distributed computing</a></li><li><a href="uid16.html&#10;&#9;&#9;  ">Theory of distributed systems</a></li><li><a href="uid17.html&#10;&#9;&#9;  ">Peer-to-peer overlay networks</a></li><li><a href="uid18.html&#10;&#9;&#9;  ">Epidemic protocols</a></li><li><a href="uid19.html&#10;&#9;&#9;  ">Malicious process behaviors</a></li><li><a href="uid20.html&#10;&#9;&#9;  ">Online social networks and recommender systems </a></li></ul></div>
      <div class="TdmEntry">Application Domains<ul><li><a href="uid22.html&#10;&#9;&#9;  ">Overview</a></li></ul></div>
      <div class="TdmEntry">New Software and Platforms<ul><li><a href="uid30.html&#10;&#9;&#9;  ">MediEgo: A recommendation solution for webmasters</a></li><li><a href="uid31.html&#10;&#9;&#9;  ">AllYours-P2P: A distributed news recommender (former WhatsUp)</a></li><li><a href="uid32.html&#10;&#9;&#9;  ">HyRec: A hybrid recommender system</a></li><li><a href="uid33.html&#10;&#9;&#9;  ">GossipLib: A library for gossip-based applications</a></li><li><a href="uid34.html&#10;&#9;&#9;  ">YALPS: A library for p2p applications</a></li><li><a href="uid35.html&#10;&#9;&#9;  ">HEAP: Heterogeneity-aware gossip protocol</a></li><li><a href="uid36.html&#10;&#9;&#9;  ">Brow2Brow: Browser-to-browser serverless toolboxes</a></li><li><a href="uid37.html&#10;&#9;&#9;  ">WebGC: Web-based Gossip Communication</a></li></ul></div>
      <div class="TdmEntry">New Results<ul><li><a href="uid39.html&#10;&#9;&#9;  ">Highlights of the Year</a></li><li><a href="uid44.html&#10;&#9;&#9;  ">Models and abstractions for distributed systems</a></li><li><a href="uid52.html&#10;&#9;&#9;  ">Large-scale and user-centric distributed systems</a></li></ul></div>
      <div class="TdmEntry">Bilateral Contracts and Grants with Industry<ul><li><a href="uid73.html&#10;&#9;&#9;  ">Technicolor</a></li><li><a href="uid74.html&#10;&#9;&#9;  ">Orange Labs</a></li><li><a href="uid75.html&#10;&#9;&#9;  ">Web Alter-Egos Google Focused Award</a></li></ul></div>
      <div class="TdmEntry">Partnerships and Cooperations<ul><li><a href="uid77.html&#10;&#9;&#9;  ">National initiatives</a></li><li><a href="uid82.html&#10;&#9;&#9;  ">European initiatives</a></li><li><a href="uid95.html&#10;&#9;&#9;  ">International Initiatives</a></li><li><a href="uid108.html&#10;&#9;&#9;  ">International Research Visitors</a></li></ul></div>
      <div class="TdmEntry">Dissemination<ul><li><a href="uid126.html&#10;&#9;&#9;  ">Promoting scientific activities</a></li><li><a href="uid180.html&#10;&#9;&#9;  ">Invited talks</a></li><li><a href="uid191.html&#10;&#9;&#9;  ">Teaching, supervision, juries</a></li></ul></div>
      <div class="TdmEntry">
        <div>Bibliography</div>
      </div>
      <div class="TdmEntry">
        <ul>
          <li>
            <a id="tdmbibentmajor" href="bibliography.html">Major publications</a>
          </li>
          <li>
            <a id="tdmbibentyear" href="bibliography.html#year">Publications of the year</a>
          </li>
          <li>
            <a id="tdmbibentfoot" href="bibliography.html#References">References in notes</a>
          </li>
        </ul>
      </div>
    </div>
    <div id="main">
      <div class="mainentete">
        <div id="head_agauche">
          <small><a href="http://www.inria.fr">
	    
	    Inria
	  </a> | <a href="../index.html">
	    
	    Raweb 
	    2014</a> | <a href="http://www.inria.fr/en/teams/asap">Presentation of the Project-Team ASAP</a> | <a href="http://www.irisa.fr/asap">ASAP Web Site
	  </a></small>
        </div>
        <div id="head_adroite">
          <table class="qrcode">
            <tr>
              <td>
                <a href="asap.xml">
                  <img style="align:bottom; border:none" alt="XML" src="../static/img/icons/xml_motif.png"/>
                </a>
              </td>
              <td>
                <a href="asap.pdf">
                  <img style="align:bottom; border:none" alt="PDF" src="IMG/qrcode-asap-pdf.png"/>
                </a>
              </td>
              <td>
                <a href="../asap/asap.epub">
                  <img style="align:bottom; border:none" alt="e-pub" src="IMG/qrcode-asap-epub.png"/>
                </a>
              </td>
            </tr>
            <tr>
              <td/>
              <td>PDF
</td>
              <td>e-Pub
</td>
            </tr>
          </table>
        </div>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid3.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid15.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
      <div id="textepage">
        <!--DEBUT2 du corps du module-->
        <h2>Section: 
      Overall Objectives</h2>
        <h3 class="titre3">Structure of the team</h3>
        <p>Our ambitious goal is to provide the algorithmic foundations of
large-scale dynamic distributed systems, ranging from abstractions
to real deployment. This is reflected in the following objectives:</p>
        <a name="uid9"/>
        <h4 class="titre4">Objective 1: Decentralized personalization</h4>
        <p>Our first objective is to offer full-fledged personalization in notification
systems. Today, almost everyone is suffering from an overload of
information that hurts both users and content providers. This suggests
that not only will notification systems take a prominent role but also
that, in order to be useful, they should be personalized to each and
every user depending on her activity, operations, posts, interests,
etc. In the <span class="smallcap">Gossple </span> implicit instant
item recommender, through a simple interface, users
get automatically notified of items of interest for them, without
explicitly subscribing to feeds or interests. They simply have to let
the system know whether they like the items they receive (typically
through a like/dislike button). Throughout the system's operation the
personal data of users is stored on their own machines, which makes it
possible to provide a wide spectrum of privacy guarantees while
enabling cross-application benefits.</p>
        <p>Our goal here is to provide a fully
decentralized solution without ever requiring users to reveal their
private preferences.</p>
        <a name="uid10"/>
        <h4 class="titre4">Objective 2: Personalization: Cloud computing meets p2p</h4>
        <p>Our second objective is to move forward in the area of
<b>personalization</b>. Personalization is one of the biggest
challenges addressed by most large stake holders.</p>
        <p><b>Hybrid infrastructures for personalisation.</b> So far, social
filtering techniques have mainly been implemented on centralized
architectures relying on smart heuristics to cope with an increasing
load of information. We argue however that, no matter how smart these
heuristics and how powerful the underlying machines running them, a
fully centralized approach might not be able to cope with the
exponential growth of the Internet and, even if it does, the price to
be paid might simply not be acceptable for its users (privacy,
ecological footprint, etc.).</p>
        <p>At the other end of the spectrum, lie fully decentralized systems
where the collaborative filtering system is implemented by the
machines of the users themselves. Such approaches are appealing for
both scalability and privacy reasons. With respect to scalability,
storage and computational units naturally grow with the number of
users. Furthermore, a p2p system provides an energy-friendly
environment where every user can feel responsible for the ecological
foot-print of her exploration of the Internet. With respect to
privacy, users are responsible for the management of their own
profiles. Potential privacy threats therefore do not come from a
big-brother but may still arise due to the presence of other users.</p>
        <p>We have a strong experience in devising and experimenting with such
kinds of p2p systems for various forms of personalization. More
specifically, we have shown that personalization can be effective
while maintaining a reasonable level of privacy. Nevertheless,
frequent connections/disconnections of users make such systems
difficult to maintain while addressing privacy attacks. For this
reason, we also plan to explore hybrid approaches where the social
filtering is performed by the users themselves, as in a p2p manner,
whereas the management of connections-disconnections, including
authentication, is managed through a server-based architecture. In
particular, we plan to explore the trade-off between the quality of
the personalization process, its efficiency and the privacy
guarantees.</p>
        <a name="uid11"/>
        <h4 class="titre4">Objective 3: Privacy-aware decentralized computations</h4>
        <p>Gossip algorithms have also been studied for more complex global
tasks, such as computation of network statistics or, more generally,
aggregation functions of input values of the nodes (e.g., sum,
average, or max). We plan to pursue this research direction both from
a theoretical and from a practical perspective. We provide two
examples of these directions below.</p>
        <p><b>Computational capabilities of gossip</b>. On the theoretical
side, we have recently started to study gossip protocols for the
assignment of unique IDs from a small range to all nodes (known as the
<i>renaming</i> problem) and computing the rank of the input value of
each node. We plan to further investigate the class of global tasks
that can be solved efficiently by gossip protocols.</p>
        <p><b>Private computations on decentralized data.</b> On a more
practical track, we aim to explore the use of gossip protocols for
decentralized computations on privacy sensitive data. Recent research
on private data bases, and on homomorphic encryption, has demonstrated
the possibility to perform complex operations on encrypted data. Yet,
existing systems have concentrated on relatively small-scale
applications. In the coming years, we instead plan to investigate the
possibility to build a framework for querying and performing
operations for large-scale decentralized data stores. To achieve this,
we plan to disseminate queries in an epidemic fashion through a network
of data sources distributed on a large scale while combining privacy
preserving techniques with decentralized computations. This would, for
example, enable the computation of statistical measures on large
quantities of data without needing to access and disclose each single
data item.</p>
        <a name="uid12"/>
        <h4 class="titre4">Objective 4: Information dissemination over social networks</h4>
        <p>While we have been studying information dissemination in practical
settings (such as WhatsUp in <span class="smallcap">Gossple </span>), modeling such dynamic systems
is still in its infancy. We plan to complement our practical work on
gossip algorithms and information dissemination along the following
axes:</p>
        <p><b>Rumour spreading</b> is a family of simple randomized algorithms
for information dissemination, in which nodes contact (uniformly)
random neighbours to exchange information with them. Despite their
simplicity these protocols have proved very efficient for various
network topologies. We are interested in studying their properties in
specific topologies such as social networks be they implicit
(interest-based as in <span class="smallcap">Gossple </span>) or explicit (where users choose their
friends as in Facebook). Recently, there has been some work on
bounding the speed of rumour spreading in terms of abstract properties
of the network graph, especially the graph's expansion properties of
conductance and vertex expansion. It has been shown that high values
for either of these guarantees fast rumour spreading—this should be
related to empirical observations that social networks have high
expansion. Some works established increasingly tighter upper bounds
for rumour spreading in term of conductance or vertex expansion, but
these bounds are not tight.</p>
        <p>Our objective is to prove the missing tight upper bound for rumour
spreading with vertex expansion. It is known that neither conductance
nor vertex expansion are enough by themselves to completely
characterize the speed of rumour spreading: are there graphs with bad
expansion in which rumours spread fast? We plan to explore more
refined notions of expansion and possibly other abstract graph
properties, to establish more accurate bounds. Another interesting and
challenging problem is the derivation of general lower bounds for
rumour spreading as a function of abstract properties of graphs. No
such bounds are currently known.</p>
        <p><b>Overcoming the dependence on expansion</b>:
Rumour spreading algorithms have very nice properties as their simplicity, good performances for many networks but they
may have very poor performance for some networks, even though these
networks have small diameter, and thus it is possible to achieve fast
information dissemination with more sophisticated protocols. Typically
nodes may choose the neighbours to contact with some non-uniform
probabilities that are determined based on information accumulated by
each node during the run of the algorithm. These algorithms achieve
information dissemination in time that is close to the diameter of the
network. These algorithms, however, do not meet some of the other nice
properties of rumour spreading, most importantly, robustness against
failures. We are investigating algorithms that combine the good
runtime of these latest protocols with the robustness of rumour
spreading. Indeed these algorithms assumed that the network topology
does not change during their run. In view of the dynamism of real
networks, in which nodes join and leave and connection between nodes
change constantly, we have to address dynamic network models. We plan
to investigate how the classic rumour spread algorithms perform in the
face of changes. We plan also in this area to reduce the size of the
messages they use, which can be high even if the amount of useful
information that must be disseminated is small.</p>
        <p><b>Competing rumours</b>: Suppose now that two, or more, conflicting
rumours (or opinions) spread in the network, and whenever a node
receives different rumours it keeps only one of them. Which rumour
prevails, and how long does it take until this happens? Similar
questions have been studied in other contexts but not in the context
of rumour spreading. The <i>voter</i> model is a well studied graph process that can be viewed as a competing
rumour process that follows the classic PULL rumour spreading
algorithm. However, research has only recently started to address the
question of how long it takes until a rumour prevails. An interesting variant of the problem that has not been considered
before is when different rumours are associated with different weights
(some rumours are more convincing than others).
We plan to study the above models and variations of them, and
investigate their connection to the standard rumour spreading
algorithms. This is clearly related to the dissemination of news and
personalization in social networks.</p>
        <a name="uid13"/>
        <h4 class="titre4">Objective 5: Computability and efficiency of distributed systems</h4>
        <p>A very relevant challenge (maybe a Holy Grail) lies in the definition
of a computation model appropriate to dynamic systems. This is a
fundamental question. As an example there are a lot of peer-to-peer
protocols but none of them is formally defined with respect to an
underlying computing model. Similarly to the work of Lamport on
"static" systems, a model has to be defined for dynamic systems.
This theoretical research is a necessary condition if one wants to
understand the behavior of these systems. As the aim of a theory is to
codify knowledge in order it can be transmitted, the definition of a
realistic model for dynamic systems is inescapable whatever the aim we
have in mind, be it teaching, research or engineering.</p>
        <p><b>Distributed computability</b>:
Among the fundamental theoretical results of distributed computing,
there is a list of problems (e.g., consensus or non-blocking atomic
commit) that have been proved to have no deterministic solution in
asynchronous distributed computing systems prone to failures.
In order such a problem to become solvable in an asynchronous
distributed system, that system has to be enriched with an appropriate
oracle (also called failure detector). We have
been deeply involved in this research and designed optimal consensus
algorithms suited to different kind of oracles.
This line of research paves the way to rank the distributed computing
problems according to the "power" of the additional oracle they required
(think of "additional oracle" as "additional assumptions"). The
ultimate goal would be the statement of a distributed computing
hierarchy, according to the minimal assumptions needed to solve
distributed computing problems (similarly to the
Chomsky's hierarchy that ranks problems/languages according to the
type of automaton they need to be solved).</p>
        <p><b>Distributed computing abstractions</b>: Major advances in
sequential computing came from machine-independent data abstractions
such as sets, records, etc., control abstractions such as while, if,
etc., and modular constructs such as functions and procedures. Today,
we can no longer envisage not to use these abstractions. In the
"static" distributed computing field, some abstractions have been
promoted and proved to be useful. Reliable broadcast, consensus,
interactive consistency are some examples of such abstractions.
These abstractions have well-defined specifications. There are both
a lot of theoretical results on them (mainly decidability and lower
bounds), and numerous implementations. There is no such equivalent
for dynamic distributed systems, i.e. for systems characterized by
nodes that may join and leave, or that may change their
characteristics at runtime. Our goal is to define such novel
abstractions, thereby extending the theory of distributed systems to
the dynamic case.</p>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid3.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid15.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
    </div>
  </body>
</html>
