1 / 16

Intentional Naming System for Mobile Networks

Explore the WIND project by Hari Balakrishnan and John Guttag at MIT aimed at enabling resource discovery in dynamic, mobile networks using intentional names and late binding for optimal performance. Learn about the INS architecture, routing protocols, and decentralized resolvers for robust and responsive network operation. Discover the future of network configuration, security, and adaptation in a diverse device ecosystem.

jfetzer
Download Presentation

Intentional Naming System for Mobile Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wireless Networks of Devices (WIND) Hari Balakrishnan and John Guttag MIT Lab for Computer Science http://wind.lcs.mit.edu/ NTT-MIT Meeting, January 2000

  2. Future networks Audio Video Sensors Wireless Devices Mobile users Motivation Networks today Clients Routers Web servers

  3. Automatically obtain active map of region Location-based wireless services • Spontaneous networking • Communication & control • Mobility & group communication

  4. WIND project • Configuration • Topology formation in mobile networks • Routing • Protocols for mobile device networks • Resource discovery • New naming system for device networks • Adaptation • Congestion Manager for multimedia • Security & privacy • Private location support system

  5. Resource discovery • Problem: advertise and locate networked services • Heterogeneous environment • Wide variety of devices, services, and information • Dynamic environment • Mobile nodes and services • Variable, unpredictable performance • Device failures • Services composed of groups of nodes

  6. Solution: Intentional Naming System (INS) Names are intentional; apps know what, not where Expressiveness Integrate name resolution and message routing to handle mobility Responsiveness Decentralized, cooperating resolvers Robustness Name resolvers self-configure into overlay network Easy configuration

  7. Naming and service discovery • Wide-area naming (DNS) • Attribute-based systems (X.500) • Brokers (CORBA, ANSA) • Service location protocol (IETF) • Device discovery • Jini, Universal plug-and-play • Intentional Naming System (INS) • Mobility & dynamism via late binding • Decentralized, serverless operation • Easy configuration

  8. [vspace = mit.edu/thermometer] [building = ne43 [floor = 5 [room = *]] [temperature < 600F] data Intentional names • Expressive name language (like XML) • Providers announce descriptive names • Clients make queries • Attribute-value matches • Wildcard matches • Ranges • [vspace = lcs.mit.edu/camera] • [building = ne43 • [room = 510]] • [resolution=800x600] • [access = public] • [status = ready]

  9. Query • [building = ne-43 • [room = 510]] • [entity = camera] INS architecture Name Name resolver Client Periodic advertisement Overlay network of resolvers Service

  10. Name resolver functions • Name lookup • Routing protocol • Handling service mobility • Message forwarding • Self-configuration algorithm

  11. [building = ne-43 • [room = 510]] • [entity = camera] • [building = ne-43 • [room = 510]] • [entity = camera] Routing protocol tracks changes Service Name Name resolver Triggered update Client Overlay network of resolvers Service mobility

  12. Late binding handles mobility Name resolver • [building = ne-43 • [room = 504]] • [entity = camera] Forward to best location • [building = ne-43 • [room = *]] • [entity = camera] • flag = ANY • [building = ne-43 • [room = 510]] • [entity = camera] data Intentional anycast

  13. Intentional multicast for group communication Name resolver • [building = ne-43 • [room = 504]] • [entity = camera] Forward along spanning tree • [building = ne-43 • [room = *]] • [entity = camera] • flag = ALL • [building = ne-43 • [room = 510]] • [entity = camera] data

  14. Two notable properties • Robustness • Distributed cooperation without centralized servers • Routing information about names • Multicast forwarding • Self-configuration • Resolver network topology based on network performance • Decentralized spanning tree algorithm

  15. Status • Java implementation of INS & applications • Active map, video delivery, audio jukebox, camera network (demo) • Alpha code release for NTT • Scalability & deployment • Wide-area architecture being designed • Standardization: MIME for devices/services (XML-based)

  16. Summary • Future networks will include heterogeneous devices & services • Configuration, routing, discovery, adaptation, security • INS handles resource discovery in dynamic, mobile networks • Expressiveness: intentional names • Responsiveness: late binding • Robustness: decentralized resolvers • Configuration: self-configuration protocol http://wind.lcs.mit.edu/

More Related