<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zied Ben-Houidi</style></author><author><style face="normal" font="default" size="100%">Giuseppe Scavo</style></author><author><style face="normal" font="default" size="100%">Samir Ghamri-Doudane</style></author><author><style face="normal" font="default" size="100%">Alessandro Finamore</style></author><author><style face="normal" font="default" size="100%">Stefano Traverso</style></author><author><style face="normal" font="default" size="100%">Marco Mellia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Gold mining in a River of Internet Content Traffic</style></title><secondary-title><style face="normal" font="default" size="100%">6th International Workshop on Traffic Monitoring and Analysis, TMA</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Content mining</style></keyword><keyword><style  face="normal" font="default" size="100%">HTTP Traffic</style></keyword><keyword><style  face="normal" font="default" size="100%">URL extraction</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2014</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/2014</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pub-location><style face="normal" font="default" size="100%">London</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">With the advent of Over-The-Top content providers
(OTTs), Internet Service Providers (ISPs) saw their portfolio of
services shrink to the low margin role of data transporters. In
order to counter this effect, some ISPs started to follow big OTTs
like Facebook and Google in trying to turn their data into a
valuable asset. In this paper, we explore the questions of what
meaningful information can be extracted from network data, and
what interesting insights it can provide. To this end, we tackle
the first challenge of detecting “user-URLs”, i.e., those links that
were clicked by users as opposed to those objects automatically
downloaded by browsers and applications. We devise algorithms
to pinpoint such URLs, and validate them on manually collected
ground truth traces. We then apply them on a three-day long
traffic trace spanning more than 19,000 residential users that
generated around 190 million HTTP transactions. We find that
only 1.6% of these observed URLs were actually clicked by users.
As a first application for our methods, we answer the question
of which platforms participate most in promoting the Internet
content. Surprisingly, we find that, despite its notoriety, only 11%
of the user URL visits are coming from Google Search.
</style></abstract></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dimitri Papadimitriou</style></author><author><style face="normal" font="default" size="100%">Zied Ben-Houidi</style></author><author><style face="normal" font="default" size="100%">Samir Ghamri-Doudane</style></author><author><style face="normal" font="default" size="100%">D Rossi</style></author><author><style face="normal" font="default" size="100%">M. Milanesio</style></author><author><style face="normal" font="default" size="100%">P. Casas</style></author><author><style face="normal" font="default" size="100%">Alessandro D’Alconzo</style></author><author><style face="normal" font="default" size="100%">Edion Tego</style></author><author><style face="normal" font="default" size="100%">Francesco Matera</style></author><author><style face="normal" font="default" size="100%">Maurizio Dusi</style></author><author><style face="normal" font="default" size="100%">Tivadar Szemethy</style></author><author><style face="normal" font="default" size="100%">L. Máthé</style></author><author><style face="normal" font="default" size="100%">Alessandro Finamore</style></author><author><style face="normal" font="default" size="100%">Stefano Traverso</style></author><author><style face="normal" font="default" size="100%">Ilias Leontiadis</style></author><author><style face="normal" font="default" size="100%">Yan Grunenberger</style></author><author><style face="normal" font="default" size="100%">L. Baltrunas</style></author><author><style face="normal" font="default" size="100%">Benoit Donnet</style></author><author><style face="normal" font="default" size="100%">Guy Leduc</style></author><author><style face="normal" font="default" size="100%">Y. Liao</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Design of Analysis Modules</style></title></titles><keywords><keyword><style  face="normal" font="default" size="100%">algorithms</style></keyword><keyword><style  face="normal" font="default" size="100%">analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2013</style></year><pub-dates><date><style  face="normal" font="default" size="100%">11/2013</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">D4.1</style></number><publisher><style face="normal" font="default" size="100%">mPlane Consortium</style></publisher><pub-location><style face="normal" font="default" size="100%">Torino</style></pub-location><isbn><style face="normal" font="default" size="100%">D4.1</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language><work-type><style face="normal" font="default" size="100%">Public Deliverable</style></work-type></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Brian Trammell</style></author><author><style face="normal" font="default" size="100%">Stephan Neuhaus</style></author><author><style face="normal" font="default" size="100%">Francesco Matera</style></author><author><style face="normal" font="default" size="100%">Ernst Biersack</style></author><author><style face="normal" font="default" size="100%">Antonio Barbuzzi</style></author><author><style face="normal" font="default" size="100%">Saverio Niccolini</style></author><author><style face="normal" font="default" size="100%">Mohamed Ahmed</style></author><author><style face="normal" font="default" size="100%">Maurizio Dusi</style></author><author><style face="normal" font="default" size="100%">Tivadar Szemethy</style></author><author><style face="normal" font="default" size="100%">Balazs Szabo</style></author><author><style face="normal" font="default" size="100%">P. Casas</style></author><author><style face="normal" font="default" size="100%">A Bär</style></author><author><style face="normal" font="default" size="100%">Konstantina Papagiannaki</style></author><author><style face="normal" font="default" size="100%">Yan Grunenberger</style></author><author><style face="normal" font="default" size="100%">Ilias Leontiadis</style></author><author><style face="normal" font="default" size="100%">Rolf Winter</style></author><author><style face="normal" font="default" size="100%">Zied Ben-Houidi</style></author><author><style face="normal" font="default" size="100%">Giovanna Carofiglio</style></author><author><style face="normal" font="default" size="100%">Samir Ghamri-Doudane</style></author><author><style face="normal" font="default" size="100%">Diego Perino</style></author><author><style face="normal" font="default" size="100%">D Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Use Case Elaboration and Requirements Specification</style></title></titles><keywords><keyword><style  face="normal" font="default" size="100%">architecture</style></keyword><keyword><style  face="normal" font="default" size="100%">measurement</style></keyword><keyword><style  face="normal" font="default" size="100%">platform</style></keyword><keyword><style  face="normal" font="default" size="100%">scenario</style></keyword><keyword><style  face="normal" font="default" size="100%">use case</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2013</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2013</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">D1.1</style></number><publisher><style face="normal" font="default" size="100%">mPlane Consortium</style></publisher><pub-location><style face="normal" font="default" size="100%">Torino</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;&lt;span&gt;The document defines the requirements for the mPlane architecture on the background of a set of scenarios explored by the consortium, a survey of existing comparable measurement systems and platforms and applicable standards therefore, and a set of architectural first principles drawn from the description of work and the consortium's experience.&amp;nbsp;As mPlane is intended to be a fully flexible measurement platform, freely integrating existing probes and repositories with ones to be developed in the project, this document is primarily concerned with the definition of interfaces among mPlane components. While it does enumerate capabilities to be provided by these components, these are primarily intended to ensure the platform has the flexibility required to meet all the scenarios envisioned; the enumerations of measurements, metrics, data types, and other component capabilities are therefore not to be construed to limit the scope of work on components within the project to just those scenarios treated in this document; nor do the scenarios enumerated here define the capabilities to be demonstrated in the project's integrated trial.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;</style></abstract><work-type><style face="normal" font="default" size="100%">Public Deliverable</style></work-type></record></records></xml>