FYP: Peer-to-Peer Communications Framework on Android Platform

1,684 views

Published on

  • Be the first to comment

  • Be the first to like this

FYP: Peer-to-Peer Communications Framework on Android Platform

  1. 1. P2P CommunicationFramework on Android Platform By Liu Tianwei
  2. 2. Outline• Introduction• Motivation + Proposed Solutions.• Recap of work done• Design Decision and Limitation• Implementation result and performance• Demo• Limitation and Future Work
  3. 3. Introduction
  4. 4. Problem• Need for better mobile network infrastructure.• Traditional Mobile Network are not designed to scale fast and cheaply.
  5. 5. Motivation• Provide an alternatives to traditional mobile network infrastructure.• Lower the infrastructure cost for each additional devices added to the network.
  6. 6. Propose Solution• A P2P communication framework on mobile platform.• Open Source to allow developers to easily integrate with their existing source code.
  7. 7. Recap of work done• Server Implementation• Literature Reviews• Geoscribe Webservice implementation
  8. 8. Design Decisions and Limitations• Platform• Hardware Choices and Limitation• Network Design• AutoConnection
  9. 9. Platform• Open Source• Large Developer Community• Comprehensive Java Apis.
  10. 10. Network DesignDesigned Considered:• Centralized Index• Gnutella (Query Flooding)• Hierarchical Overlay• Distributed Hash Table
  11. 11. Centralized Index
  12. 12. Gnutella
  13. 13. Hierarchical Overlay
  14. 14. Distributed Hash Table • A distributed database over large number of peers that supported query&update operations. • Information stored in database in the form of key value pairs. • Peers query database with key
  15. 15. Network DesignModified Gnutella network. • Easy to implement. • Bluetooth hardware limitations. • Server-less implementation.
  16. 16. Hardware Choices and LimitationsAndroids Offers:• Bluetooth• Wireless - Fidelity
  17. 17. Bluetooth
  18. 18. Bluetooth
  19. 19. Bluetooth
  20. 20. Bluetooth
  21. 21. Bluetooth
  22. 22. Wireless Fidelity• IEEE 802.11 Standard (b/g/n)• via router• Direct device to device (ad-hoc)
  23. 23. Hardware Choices and LimitationsFocused on Bluetooth • Bluetooth has well defined apis • Wi-Fi ad-hoc mode not supported on android. • rooting is required for Wi-Fi ad-hoc.
  24. 24. Hardware Choices and Limitations
  25. 25. Hardware Choices and Limitations
  26. 26. AutoConnection• Experimental feature to overcome in-ability to stay always discoverable.• Centralized Geo-location indexing server.• Maintain Bluetooth scatter-net topology.
  27. 27. Implementation Result and Performance• Framework Overview• Key Features• Performance Metrics
  28. 28. Framework Overview
  29. 29. Framework OverviewAndroid Interface Definition Language(AIDL)
  30. 30. Framework OverviewUse Cases:• Ad-hoc gaming network• Instant Messaging Application• File Sharing• Video Sharing• Internet sharing• Geo-location Triangulations, etcs
  31. 31. Key Features• Open-Source• No Rooting Required• Packet Routing• No need for Centralized Index Server• Flow Control / Traffic Policing• Auto Connections
  32. 32. Performance MetricsAverage Maximum throughput : 54Kbps 324#565789)6:8-6$ +!" *!" )!" (!" !" !"#$%&% &!" %!" $!" #!" !" !" !," #" #," $" $," %" %," &" &," ()*)+,)-$)./%0120)1
  33. 33. Demo
  34. 34. Limitations of Framework• Bluetooth chipset on Androids phones.• Pairing between devices• Lack of security• Dependency on Geo-Location Indexing Server(AutoConnection)
  35. 35. Future works• Wi-Fi Ad-hoc communication.• Server-less implementation• Optimization• Security
  36. 36. Q&A

×