Table of Contents
U-mobile 26/09/2017
Dr. Paulo Mendes is a vice-Director (2014) of COPELABS, the SITI coordinator, and an Associate Professor of University Lusofona, where he heads the PhD programme in Informatics, NEMPS. Paulo is also a co-founder of SENCEPTION Lda, a spin-off of COPELABS. He has a BEng in Informatics Engineering by Univ. Coimbra (93); MSc in Computers and Electrotecnical Engineering (1998) by IST, UTL, Lisboa, and a PhD in Informatics Engineering by Univ. Coimbra (2004). He was the Telematics Director of Fernave, S.A. (1994-1998); Invited Researcher (00-03) at Columbia University, NY, EUA; researcher at CISUC, Universidade de Coimbra (1996-2002). He was also a Senior Researcher (2003-2007) at NTT DoCoMo Euro-Labs, Munich, Germany, and the co-coordinator of the Internet Architectures and Networking area of UTM, INESC Porto (2007-2010). His research interests relate to cooperative wireless systems, self-organizing networks, and complex networks. His track-record includes over 50 scientific peer-reviewed papers. Paulo is also author in 13 international patents.
U-mobile arche
- extend NDN arche with DTN blocks
- Forwarding
- DTN tunneling
- used as transport mechanism for opportunistic
- statically coupled / independent
- Opportunistic off-paath content discovery OOCD
- new routing table D-FIB
- points interests towards network edge
- discovery of local available content
- NREP
- name-based push service
- routing based on: name, prioriteis TTL, geo,
- Wifi direct
- Northbound APIs
- keyword-based mobile app sharing (KEBAPP)
- app-centric computation and communication
- information discovery through app driven and app defined namespace hierarchy
- AP-assisted and WiFi Direct scenario
- QoS
- Umobile hotspot with docker
- Service manager deploy service on hotspot
- Umobile as a whole
- User-service
- Persense mobile light
- Oi!
- route planner
- Now@
- Hotspot
- service migration, execution, NDN-Opp
- Gateway
- parte of service, content providers infastructure
- Service migration
- actually remote service deployment
- DTN forwarding
- Stakeholder
- services
- service provider devices, hotspots, router, service manager
- enduser
Umobile Lab
- Demonstration platform for the project
- Join NDN Testbed
- join FED4FIRE
- Simulate mobility by bringing interfaces up/down
- github.com/umobileproject
NDN operation in Opportunistic Wireless Networks (40 min)
We’ll describe the NDN framework for Opportunistic Networks (NDN-Opp), which is being developed aiming to support opportunistic forwarding based on users’ interests and their dynamic social behavior. NDN-Opp will be demonstrated in a micro-blogging urban scenarios in which a user, makes use of the Now@ application to generate and share expressions of interest in the form of tagged information (e.g., nearby supermarket offers or restaurant review), as well as to generate data related to those interests. This demo aims to show how NDN-Opp allows users to benefit from locally available information.
- Problem of NDN
- limitation of breadcrum routing (NDN)
- routing node mobile
- Few solutions approaches lead to DTN!
- –
> Creating DTN underlay for NDN, DTN face in NFD
- using IBR-DTN!
===== Social-aware metrics derived from contextualization (40 min) =====
U
MOBILE integrates in its end-user service application the Contextual Manager (CM), a module that assists in a more efficient data dissemination via capturing and infering network and proximity context. In this tutorial we shall go over the UMOBILE contextual manager and explain two main families of routing metrics: i) how the contextual manager can provide metrics derived from encounter duration; ii) how the contextual manager can provide metrics derived from interests and interest matching.
- NDN based routing for opportunistic network
- social behavior
- handling interest
- Carrier: high latency
- Dissemination of name prefix reachability - OK, data source announce its content
- m-path routing combined with adaptive forwarding
- Oppotunistic forwarding??
- handling data
- breadcrumb: not support opp. network
- Opportunistic - OK
- selective forwarding strategy based on prob of neighbor to meet node interestin name prefix
- computation of social weights for each potential dest of a name prefix
- high-level
- OppFace: implements queuing system
- Opp channel and receiver
- Forwarder: strategy for forwarding
- router: compute next hop
- Face manager
- Connectivity manager: low-level communication channels, supporting push communication (emergency)??.
- Handling data: opportunistic forwarding
- strategies
- prob. of meeting interested nodes
- Social weights provided by: Contextual Manager, PIT
- paper: social-aware forwarding algorithm: Waldir Moreira 2012/2013
- Handling interest: dissemination of Name prefix reachability
- M-path rouitng with adaptive forwarding
- assumptions
- lower intermittent conn of data sources
- caching devices announce its name prefix
- link state announcements (LSA) exchanged based on INT/DATA msg
- digitally signed based on structure of opp network
- Requirements
- not building network topology
- avoid hello messages
- selective dissemination of LSA due to dynamic affinity network
- next hops forwar a name-refix based on data reachabilitty cost:
- data validity dV by data owner: how long will the data be there
- link cost, wireless contact duration via interface I, LC
- reach at least 1 copy of data
- LSA(/x/y/1) in a node Nx:
- local copy: LSA = f(dVNx(/x/y/1) * otherwise LSA= f(LCNB, dV_NB(/x/y/1)
- Ranking interfaces
- A: neighbor degree centrality
- U: neighbor avaliablitiy
- D: timelapse b/w INT and DATA
- Rank (/x/y/1) increases with A, U; decreases with D
- build on top of Named-data link state routing (NLSR)
- Hierarchical naming scheme
- LSDB synchronization on top of INT/DATA
- NDN security
- not using: LSA, m-path dijkstra, hello protocol
- contribution, modification:
- LSA of namespaces
- no dissemination of LSAs Adjacency
- selective dissemination
- any device that stores a data copy can announce its name prefix
- link/interface mgmt based on opp. faces
- delete LSA for name prefixes when dV expires
- Demo
- github.com/copelabs-siti/ndn-opp
- not rely on wifi/IP, only use wifi discovery
- tools in the UI
- Pushed data: trick, put data to the FIB and make the device the source and send to others.
Contextualization aspects integration into the network operation
- user, network, apps, etc.
- contextual managemnt
- capgure module
- affinity network data (peer lists, peer INT)
- visited network (connectivity)
- resource usage (app, cpu, battery)
- Inference moudle
- affinity network characterization
- usage and similarity characterization
- capture module:
- visted network
- wifi, roaming, wifi scans, (1 week collection)
- related libraries: Persense mobile light
- affinity network: wifi direct, bluetooth
- resource usage
- storage
- Inference module
- PerSense: demo implementation