Supporting Mobility in MobilityFirst F. Zhang, K. Nagaraja, T. - - PowerPoint PPT Presentation
Supporting Mobility in MobilityFirst F. Zhang, K. Nagaraja, T. Nguyen, D. Raychaudhuri, Y. Zhang WINLAB, Rutgers University Technology Centre of NJ 671 Route 1, North Brunswick, NJ 08902, USA Mobile Data Usage Forecast Mobile data [Cisco
WINLAB, Rutgers University Technology Centre of NJ 671 Route 1, North Brunswick, NJ 08902, USA
Mobile data [Cisco Visual Networking Index]
Global mobile data traffic grew 2.3 fold in 2011
More than doubling for the fourth year in a row
By the end of 2012, the number of mobile-connected
devices will exceed the number of people on earth.
Mobile cloud traffic
Mainly medium Mobile cloud traffic will grow 28 fold from 2011 to 2016, will
account for 71% (7.6 exabyets / month) of total mobile data traffic in 2016
Device Mobility
“Can I download a movie while riding the taxi to EWR?”
Content Retrieval and Content Mobility
“ Can I access the content copy that is close to me? ”
Dynamic Context
“Can I send a message to all the people who are attending the Winlab
IAB?”
Each device/content/context has a
Many existing work on creating HRNs
GUIDs are flat, randomly
~ 160 bits
Name assignment service (NAS):
Translating HRNs to GUIDs
5
Globally Unique Flat Identifier (GUID)
John’s _laptop_1 Sue’s_mobile_2 Server_1234 Sensor@XYZ Media File_ABC Host Naming Service Network Sensor Naming Service Content Naming Service
Global Name Resolution Service
Net2.local_ID Context Naming Service Taxis in NB
GNRS
Host H
GUID Network Address H AS1
1. GUID Publishing AS1
GNRS
Host H requestor
lookup
Reply: AS1 for H
GUID Network Address H AS1
1. GUID Publishing AS1
GNRS
Host H
GUID Network Address H AS1
AS1 AS2
GNRS
Host H
GUID Network Address H AS1
AS1 AS2 1. GUID update
GNRS
Host H
GUID Network Address H AS2
AS1 AS2 1. GUID update
(00101100……10011001)
Hash Function
GUID IPx = (44.32.1.153) IP
Strictly 1-overlay-hop lookup
No extra routing requirement (e.g. utilize current BGP)
Every mapping is replicated at K random locations
Lookups can choose closest among K mappings. Much reduced lookup latencies
IPx = (44.32.1.153)
k Hash Functions
GUID IP IP (00101100……10011001) IPx = (67.10.12.1) IP IPx = (8.12.2.3)
GUID 10
GUID AS# 10 1
K=1
AS 1 AS 5
GUID AS# 10 1
K=2
AS 101
GUID AS# 10 1
K=3
AS 200
GUID AS# 10 1
Local replica
Keeping a local copy within the source AS
LNRS vs GNRS
GUID update
Intermediate routers can choose to cache GNRS
Each GUID update has a TTL field
Entry is evicted from the cache when TTL expires
Mobile needs to estimate its stay time when it
13 GUID Update (G, AS2, 2 hours) GUID update AS 2 AS 26 AS 23973 GUID update
GUID AS# G AS2
(G, AS2) (G, AS2) (G, AS2) (G, AS2)
14
GNRS
GUID Network Address Content AS 239 Mobile AS 1
content request content reply AS 239 AS 1
15
GNRS
GUID Network Address Content AS 239 Mobile AS 2
content reply AS 239 AS 1 AS 2
16
GUID Network Address Content AS 239
GNRS
GUID lookups AS 239 Content requests
17
GUID Network Address Content AS 239, cache1, cache 2
GNRS
GUID lookups AS 239 Content requests
GUID mapping cache Content cache 1 Content cache 2
18
GUID NA(s) M1 AS1
Global Name Resolutions Service (GNRS)
Context update
AS1
G1 G2 G3 G4 G5 G6 G7
Context GUID GUID NA(s)
M1 G1-7 AS1
Click
Forwarding Engine Routing Nam e Resolution Mgm t. Classifier
Rx Q Tx Q
To/From Host Host Rx Q Host Tx Q
Content Cache
Rsrc Control
User-level Processes
Next-hop Look up Block Aggregator Block Segmentor Forwarding Table Forwarding Elements To Next-hop Lookup Hold buffer
x86 hardware and runtime
Wired and wireless i/f Wired and wireless i/f
Click-based router
Data forwarding path Implement reliable hop-by-hop transport, storage aware routing
Name resolution, content caching
User-level process Name service structured into two service planes (LNRS + GNRS)
200+ AS’s GUID update/lookup traces
AT&T cell tower data Rutgers CS lawn trace
The distributed GNRS service includes
In-memory GUID mapping database on each GNRS server Multiple replicas Local copies In-network caching
22
CCN, NDN
Hierarchical naming: /parc.com/videos/WidgetA.mpg Semantic routing based on content names
DONA
Flat, self-certifying content names A tree based content routing approach
Hierarchical naming
/parc.com/videos/Widget
A.mpg Interest packets are
Data packets are
Compared to NDN, our design offers the following
Much smaller routing table: our solution relies on existing routing table,
while NDN’s routing table may grow sub-linearly with number of contents
Much lower Update cost: our solution only needs to update K locations
for an update, while NDN needs to update a large number of routing tables
Better Mobility Support: NDN routes data packets by reversing the
interest path
Use case I: downloading popular contents, e.g.,
Use case II: peer-to-peer one-2-many delivery Use case III: content download on the go Use case IV: high density, dynamic content
Orbit prototyping GENI evaluation
Dynamic DNS Mobile IP