Drop-It: A Contextual Location Based Messaging System in MobilityFirst FIA

Francesco Bronzino, Kem Alimole, Kiran Nagaraja, Ivan Seskar, Dipankar Raychaudhuri

Introduction to MobilityFirst Demo Components

Demo Scenario: Retrieving a MessageDemo Scenario: Dropping a Message

MobilityFirst Architecture

Challenge•Host and network mobility•Varying level of wireless connectivity•Multi-homing

Core

WiMax BSWiFi AP DTN

Prevalent mobile devices in the Internet

Motivation•Historic shift from PCs to mobile devices•~4 B Cell phones vs. ~1 B PCs in 2010.

MobilityFirst Routers/APs

MobilityFirst End Host Protocol Stack and Messaging Application

•Naming and dynamic resolution•Trusted communication•Edge-aware routing•Extensible in-network services

GNRS

Global Name Resolution Service•Generalized Storage-Aware

Routing (GSTAR)•Hybrid GUID and network

address based routing

• Global Name Resolution Service

• Narrow waist of the protocol stack

• Distributed approach

•Client stack prototype implementation available for JAVA (Android) and C (Linux)•Multihoming support (Wifi, Ethernet and Wimax)

Globally Unique Flat IdentifiersGlobal Name Resolution Service

Host Naming Service

Content Naming Service

Context Naming Service

Integrated storage and computing

Routers with integrated storage

and computing

Hop-by-hop transport

Media file MContext C

John’s laptopSue’s phone

GNRS

1

21.Update phone location manually or

through QR code scan (indoor demo does not allow GPS usage)

2.Interface to “Drop” a message at a particular location

3.List of messages “Dropped” at a particular location. The swipe to this tab automatically triggers the retrieval of the available messages

3

2

GNRS

1

Location A

Location A

Location B

1. User identified by GUID 1 Drops a

message at location identified by GUID A

2. User 1 updates the GNRS of the binding<GUID A -> GUID 1>

References

1. User 2 arrives at location A and tries to

retrieve available messages

2. The query to the GNRS return the

mapping<GUID A -> GUID 1>

3. User 2 sends a request message with

destination GUID 14. The MF router binds

the chunks with destination 1 to NA2

5. User 1 receives the request and respond with the messages it

has dropped at location A

Network 1

Network 2

•D. Raychaudhuri, K. Nagaraja and A. Venkataramani, "MobilityFirst: A Robust and Trustworthy MobilityCentric Architecture for the Future Internet", ACM SIGMobile Mobile Computing and Communication Review (MC2R), Volume 16 Issue 4, October 2012

• F. Bronzino, K. Nagaraja, I. Seskar, and D. Raychaudhuri, 'Network Service Abstractions for a Mobility-Centric Future Internet Architecture", to appear in Proceedings of 8th ACM Workshop on Mobility in the Evolving Internet Architecture (MobiArch) 2013, Miami, FL, October, 2013

• T. Vu, A. Baid, Y. Zhang, T. D. Nguyen, J. Fukuyama, R. P. Martin, D. Raychaudhuri, "DMap: A Shared Hosting Scheme for Dynamic Identifier to Locator Mappings in the Global Internet ", Proceedings of IEEE ICDCS 2012, Macau, June 2012

1

Network 21

3. If the User moves to a new network it needs

to update the GNRS with the new

<GUID -> NA> pair

✴No infrastructure required except for the GNRS Location B