10 likes | 95 Views
http://www.cse.usf.edu/dsg/mobius/. MOBIUS: A TWO-TIER INFRASTRUCTURE FOR MOBILE SOCIAL COMPUTING. MOBIDEW DESIGN REQUIREMENTS. MobiDew: Socially-Aware Data Management for Mobile Users. Use geo-social knowledge for improved: Privacy and trust Resource availability Data availability
E N D
http://www.cse.usf.edu/dsg/mobius/ MOBIUS: A TWO-TIER INFRASTRUCTURE FOR MOBILE SOCIAL COMPUTING MOBIDEW DESIGN REQUIREMENTS MobiDew: Socially-Aware Data Management for Mobile Users • Use geo-social knowledge for improved: • Privacy and trust • Resource availability • Data availability • Reduced latency and battery consumption for mobile users MOBIDEW DESIGN APPROACH • Mobile node architecture • Mobile Tier: • Exports an API for context-aware mobile applications • Collects geo-social context information • Collaborates with the P2P tier for geo-social adaptation • Mobile applications interact with user services in the P2P tier • Both tiers collect, exchange, and infer geo-social • information (e.g., mobile device co-location, Facebook friends) • Super-Peer Election: • Socially Central • Stable • Resource-rich (bandwidth, storage capacity) • Super-Peer Roles: • Perform DHT functions • Collect network characteristics for the social group nodes • Interact with social group nodes to store/retrieve/search data • Maintain super-peer state backups on other social group nodes • Social Group Nodes: • Unstructured P2P topology based on social relationships • Interact with super-peers to store/retrieve data Legend: <tag of social relationship, strength of relationship (weight)> 2 types of DHTs running on the Super-Peers: 1st ID Space: Common Social Group Tag + Geographic Location of the Group: used for storing user content data 2nd ID Space: User globally unique ID space: used for storing user social state data • Mobius Features: • Decentralized architecture • Adaptive and flexible to user’s geo-social context • Allows mobile applications to interact with user-deployed, community • supported services running on a collection of user-owned P2P resources • Improves mobile application performance Nicolas Kourtellis*, Joshua Finnis*, Adriana Iamnitchi*, Cristian Borcea# *Computer Science and Engineering, University of South Florida #Department of Computer Science, New Jersey Institute of Technology • P2P tier architecture • P2P Tier: • API for user-deployed services • Scalable and resilient support for data and service • management • Privacy-preserving geo-social state management MOBIDEW IN THE CONTEXT OF MOBIUS MOBIDEW API: file_id store (file, attributes) file_id[ ] search (content_tags) attributes = {owner_of_file, content_type_of_file, lifetime, recipients, content_tags} file retrieve (file_id) PROTOTYPE IMPLEMENTATION • BitDew (http://www.bitdew.net/ ) leveraged to implement MobiDew • BitDew has 4 core services and uses metadata for data management on P2P nodes: • Data Scheduler: Implicit data movement through transfer orders according to the hosts’ activity and data attributes • Data Catalog: The storage of metadata • Metadata: Replication (number of copies), fault tolerance, lifetime, affinity (with other data), transfer protocol • Data Repository: Interface to data storage • Data Transfer: Reliable out-of-band file transfer between storage nodes • Geo-Social Service (GSS): • Collects the geo-social data of mobile users • Infers social relations, social groups and co-location of users • Outputs partial social graphs used to assign Geo-Social Group Tags (1st ID Space) • Mobile Platform: • Simple applications and geo-social data collection implemented on Windows-based HTC smart phones • SmartCampus (http://smartcampus.njit.edu) test-bed with 100s of smart phones will be used for large scale experiments CONTENT STORING AND SHARING WITH SOCIAL GROUP PERSONAL EVACUATION ROUTE Acknowledgements: Work supported by NSF Grants CNS-0831785 and CNS-0831753