Content and Context in Mobility First

Transcription

1 and Context in Mobility First Presented by: Rich Martin WINLAB, Rutgers University Technology Centre of NJ 671 Route 1, North Brunswick, NJ 08902, USA

2 Using the for content and context Globally unique identifier () for any communication entity Sue s_mobile_2 Server_1234 Media File_ABC Taxis in NB is the narrow waist Overload the * - for content - for context John s _laptop_1 Host Naming Service Sensor Naming Service Sensor@XYZ Naming Service Globally Unique Flat Identifier () Global Name Resolution Service Context Naming Service Network * In the computer science sense Network address Net1.local_ID Net2.local_ID

3 Mapping the to content Unified framework for: Authenticated content distribution Scale up to allow large distribution Scale down to accommodate limited distributions Strategy: Map a to consistent content Static or replicated dynamic Rely on to maintain mapping trees of to network addresses -> Implementing anycast and multicast using tables

4 Base example using MobiltyFirst stack C Host Address H1, H2 requestor 2. lookup 3. Reply: H1 and H2 4. content request 5. content reply C Host H1 C Host H2

5 Adding Contextual Communications What is Communication Context? Anything in the environment that impacts communication: Social states: Free, busy, interruptable, popularity Social roles: Wife, kids, boss, student Activities: Driving, having lunch Time and Location: At work, home, latitude/longitude Channel Conditions: high bandwidth, congested, free Network attachment points: high cost, low cost, free. Why is this important? Examples: Call a specific phone, but only when the user is not driving. Call the phone in the passenger s seat of a specific car Send a message to everyone who is at tea time on Wednesday. Send a reminder message to leave before I might miss my flight. Get the content of the most popular action movie last month Too hard to add all the above environmental variables into the MF routing and forwarding layer

6 Contextual Communications Strategy Describe the environment at the naming layer Each environmental description gets a Can communicate with devices in the matching environment, w/o their addresses Description is generalized in a simple expression language Environment sensing is an external service Each example would get a Use MF communications API to abstract higher-levels of communication Send short notification could go to , SMS, AIM Send to all in a group -> group gets a, which is a named expression

7 Realizing Contextual Communications in MobilityFirst Client Context Name + message MobilityFirst Router Context Expression s Network Addresses Name Assignment Service Context Resolution Service Context Name + Context Expression + ->NAs Context Solver End devices Environmental Sensing And Evaluation NAs + message Legacy Router Server_1234 Sensor@XYZ

8 Tea-Time Example Winlab Tea-Time Client Mobility First API Send::1234 Come 2 the talk MobilityFirst Router Data plane Compute plane :1234 :1234 :5678 Name Assignment Service Context Resolution Service MobilityFirst Router Compute plane Context Expression All phones and WiFi devices in the break room between 1-5PM when the tea and coffee pots are hot Real-time location service + sensor net :1234 ->phone 1: SMS@ >phone 2: SMTP@ >laptop: AIM@ 5678 AIM: End devices SMS@ SMTP@ Legacy Networks

9 Status and Open issues Real Components coming together MF router, Context Resolution Service, Sensing + localization(octopus), Demonstrations: Sending SMS when a device is at a specific location Sensing Phone location in a vehicle (mobicom demo) Open issues: Latency of Mobility First higher-level communications Potentially at a lot of translations (lots of arrows) Late bindings This might be OK for the higher-level communications? Need experience with this Scalability of content distribution using Do the tables scale?

10 Backup slides

11 Use Case I: Request / Reply C Host Address H1, H2 requestor 2. lookup 3. Reply: H1 and H2 4. content request 5. content reply C Host H1 C Host H2

12 Use Case II: Inconsistent Entries C Host Address H 2. lookup 3. Reply: H 1. requestor C Host H

13 Use Case II: Inconsistent Entries C Host Address H 2. lookup 3. Reply: H Update 1. requestor 6. Keep checking until H C Host H

14 Use Case II: Inconsistent Entries C Host Address H 2. lookup 3. Reply: H Update 1. requestor 6. Keep checking until H C Host H

15 Use Case III: Caching C H, Host Address 2. lookup requestor R 3. Reply: H 4. content request 5. content reply 1. C Host H

16 Use Case III: Caching C Host Address H, R 2. lookup cache R 3. Reply: H 4. content request 5. content reply 1. C Host H 6. R decides to cache the content

17 Use Case III: Caching C Host Address H, R 2. lookup cache R 3. Reply: H 4. content request 5. content reply 1. C Host H 6. R decides to cache the content requestor