distributed push to talk over internet networks n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Distributed Push-To-Talk over internet networks PowerPoint Presentation
Download Presentation
Distributed Push-To-Talk over internet networks

Loading in 2 Seconds...

play fullscreen
1 / 17
ulric-baker

Distributed Push-To-Talk over internet networks - PowerPoint PPT Presentation

85 Views
Download Presentation
Distributed Push-To-Talk over internet 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. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Distributed Push-To-Talk over internet networks By: Asaf Oren & Gilad Eisenberger Supervisor: Ittay Eyal Spring 2009 Networked Software Lab

  2. Goals • Enable PTT communications between users without a central service • Create implementation that works over the internet • Use reasonable amounts of bandwidth • Learn • Have fun

  3. What is Push-To-Talk (PTT)? • A method of communicating • One user can talk at a time • Press button to start talking • Release button when finished

  4. Internet networks • Available everywhere • Not reliable • IP Based • Great model for private (and public) networks • Accessible to us • This is what we base our assumptions on

  5. Requirements (the “problem”) • Application, distributed • Joining, leaving • Request floor, release floor • User interface

  6. Solution • C#, .Net, Visual Studio • UDP Networking • WinAPI for sound • Serialization • Low-level network protocol • Single threaded

  7. Protocol Stack

  8. Implementation • Originally – 3 phases • Server-Client • Mixed mode • Distributed • Actually – only 2 phases • Dropped mixed mode

  9. Server-Client • Two different applications • Similar general design • Asymmetric protocol

  10. General application structure

  11. Protocol message types • Server->Client • Add, Remove User • Floor Response, Changed • Sound (not reliable) • Client->Server • Connect, Disconnect • Floor Request, Released • Sound (not reliable)

  12. Distributed • Symmetry • Tree topology • Changes in user management • Protocol changes • Remove Floor Changed message • Changes in User messages

  13. General structure of generic client

  14. Conclusion • Works! (demo at end) • Great proof-of-concept • Meets requirements • Many problems solved • Few problems left open • NAT, Reconnections, Security

  15. Future work • Can be adapted to commercial product • Can add new features (not part of original problem) • Text messaging • Private talks

  16. Demo

  17. Questions • (and hopefully answers)