SIP Beyond Telecom


Published on

The Session Initiation Protocol (SIP) was originally defined as a protocol for creating and managing sessions. Its main use is for telecommunication applications but given its extensibility and flexibility features it may be used for other implementations as well. Many segments are looking today for their next generation communication and control solutions these include applications such as transportation control, public transportation monitoring, elderly and healthcare applications and home automation. Traditionally most of these segments have been using proprietary implementations but lately we see a growing trend for implementing standard based solutions. RADVISION has gained experience in such solutions. This webinar is delivered by our leading technology and architecture people, people who have taken a significant role in shaping many of the VoIP standards to date. Please join us to gain from their experience and insights.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SIP Beyond Telecom

  1. 1. TitleName TitleName SIP Beyond Telecom Sasha Ruditsky CTO Tsahi Levent-Levi Project Director & Community Facilitator
  2. 2. Agenda SIP for Telecom Why Beyond Telecom? Examples Gaps and Challenges About RADVISION
  3. 3. SIP for Telecom
  4. 4. SIP – The PSTN Alternative
  5. 5. Rich Multimedia
  6. 6. Presence and IM – Already “Beyond” Telecom
  7. 7. Why Beyond Telecom?
  8. 8. SIP Events Mechanism Keeping up to date
  9. 9. Subscribing for events Alice Notifier SUBSCRIBE
  10. 10. Subscribing for events Alice Notifier SUBSCRIBE 200 OK
  11. 11. Subscribing for events Alice Notifier SUBSCRIBE 200 OK NOTIFY 200 OK
  12. 12. Subscribing for events Alice Notifier SUBSCRIBE 200 OK NOTIFY 200 OK NOTIFY 200 OK event
  13. 13. Subscribing for events Alice Notifier SUBSCRIBE 200 OK NOTIFY 200 OK NOTIFY 200 OK PUBLISH 200 OK Bob
  14. 14. SIP Events Mechanism: Packages The actual events you SUBSCRIBE Are indicated in separate RFCs Can optionally use proprietary events Presence service itself is a set of event packages Mechanism RFC SUBSCRIBE/NOTIFY RFC 3265 PUBLISH RFC 3903 presence package RFC 3856 presence.winfo package RFC 3857 reg RFC 3680
  15. 15. SIP Solves a Lot of Problems Session establishment Routing NAT traversal Security Signaling compression Open protocol Extensions
  16. 16. What do you see as SIP’s strongest point?  Session initiation and management  Events mechanism and extensibility  Security and NAT traversal solutions  Openness  Large ecosystem and deployments base
  17. 17. We Can Do Better, But Do We Want To? Time and investment to design a new and better protocol H.323 took 5 years (1995-2000) to get to version 4, which was mature enough
  18. 18. We Can Do Better, But Do We Want To? Huge install base and ecosystem of SIP products 438,000 IP PBX’s were shipped worldwide in 2008 IDC, Worldwide IP PBX and Desktop Hardware IP Phone Market Forecast, 2008-2012: Using the PBX as the Foundation of Unified Communications
  19. 19. We Can Do Better, But Do We Want To? The best technical solution is not always the one that wins Betamax vs. VHS
  20. 20. Examples
  21. 21. Transportation The Need In-vehicle monitoring Traffic management Employ SIP Events mechanism There’s even an obsoletedraft for that (draft-singh-simple-vehicle-info-01) New cars can already connect to IP networks Requires more standardization, but incentives exist
  22. 22. Transportation: Sample message <?xml version="1.0" encoding="utf-8" ?> <vehicle-info xmlns="urn:ietf:params:xml:ns:vehicle-info" entity="" state="full" version="1111111111" > <vehicle-state> <status>open</status> <ignition>on</ignition> <fuel unit="gallon">3.0</fuel> <temperature unit="F">68</temperature> <passengers>3</passengers> <airbags>closed</airbags> </vehicle-state> <vehicle-diagnostics> <obdii DTC="P0120">Throttle Switch Malfunction</obdii> <obdii DTC="P1390">Timing Belt Skipped a Tooth</obdii> <obdii RTData="EngineCoolantTemp" unit="F">20</obdii> <obdii RTData="VehicleSpeed" unit="Miles">55</obdii> <obdii RTData="EngineRPM" unit="RPM">3257</obdii> </vehicle-diagnostics> </vehicle-info>
  23. 23. Gaming The Need: Telecom for games Add to online games Presence IM Voice and video chats
  24. 24. Gaming: How Big Is It? Vivox – billions of voice minutes served Second Life World of Warcraft Facebook
  25. 25. Surveillance & Streaming The Need: Replacement for RTSP Advantages Allows bidirectional audio Easier integration into VoIP systems But… there are missing methods There’s even an obsolete draft for that (draft-whitehead-mmusic-sip-for-streaming-media-05)
  26. 26. Surveillance & Streaming: Devices Grandstream GXV3601 IP Camera Zyxel V750W surveillance camera
  27. 27. IPTV and IMS The Need: Triple-play deployments Utilize IMS solution architecture Advantages: IPTV is a service QoS in a multi-service domain Network topology support Security and authentication Users and services profiles and properties Billing Service blending
  28. 28. IPTV and IMS: Architecture IPTV Applications Transport Functions Transport Control Functions UE Core IMS RACS Transport Processing Functions SSF IPTV Service Control Functions CoD-CF BC-CF PVR-CF … IPTV Media Functions (Control & Delivery) CoD-MF BC-MF PVR-MF … Xa Gm ISC Xc Xd NASS SDF UPSF Sh ShISC Ut Cx y2
  29. 29. Home Automation The Need: Control and monitor consumer electronics around the home Advantages Employ SIP Events mechanism Allow connectivity out of the home Enable security and NAT traversal
  30. 30. Home Automation: Architecture SIP SIP Gateway Gateway Gateway SIP Proxy IP Phone PC SensorsSurveillance Appliances Mobile network Car network Internet Corporate network SIP
  31. 31. Railroads The Need: Communicate and control tracks and trains from different vendors Solution: Demonstration of how “off the shelf” SIP can be used by railroads Employ specialized events packages
  32. 32. Trains: Architecture
  33. 33. Trains: Multiple devices, multiple networks
  34. 34. Should non-telecom industries use open standards or create proprietary solutions? Use open standards, such as SIP Create industry specific communication standards Use proprietary implementations
  35. 35. Where Else? Smart energy grid Medical devices Industrial automation …
  36. 36. Gaps and Challenges
  37. 37. Standardization is still missing SIP Provides powerful extension mechanisms, however actual extension do require additional specifications: New SIP Events packages Format of SUBSCRIBE bodies Format of NOTIFY bodies Additional SIP messages Additional SIP messages’ headers Additional SIP message headers’ parameters
  38. 38. How do we deal with industry specific solutions? Standardize @ IETF? Standardize elsewhere? Go for “proprietary” extensions?
  39. 39. A bit about us
  40. 40. Who is RADVISION THE INDUSTRY’S EXPERT IN VISUAL COMMUNICATIONS RADVISION is the leading provider of core technologies, products and solutions that enable unified multimedia communications over IP, 3G and emerging next generation IMS networks.
  41. 41. Technology Business Unit Mission To be the first choice for developers of IP Voice and Video Communications Solutions with innovative, high quality products and services
  42. 42. SIP Developer Suite SIP Developer Suite - Confidential SIP Toolkit RTP Stack SDP Stack SCTP Add-On SigComp Add-On IMS Add-On XML Schema Package MS Add-on (CSTA) STUN ICE NAT T. Toolkits ICE XDM Toolkit MSRP Toolkit IPSec Add-on STUN SIMPLE Presence Add-on TURN Basic SIP TK Add-Ons Toolkits
  43. 43. SIP Server Platform Application Layer SIP Server Platform Layer Proxy & Redirect Server Registrar Server Location DB Component SIP Server Core Module IMS SIP Stack Security Component Presence & Events Server OS Abstraction Layer (Common Core) Server Reference Implementations B2BAF And Service Library Auxiliary Diameter XDM XCAP
  44. 44. API Wrapping Quick Start Programs V2oIP Web Clients Embedded Video Clients IMS Core Elements IMS Clients Resource Prioritization Hosted Service Networks IP-PBX Solutions Unified Communications Presence Applications Proprietary Event- Notification Solutions Global Services Signaling & Media Expertise Global Presence Market Share & IOT Reduced Project Risk Short Time-to- Revenue 17 years of technological leadership Global Services
  45. 45. Learn more and be part of our community Developer Community Corporate Website Newsletter Blogs
  46. 46. Thank you Sasha Ruditsky Chief Technology Officer RADVISION Technology Business Unit Tsahi Levent-Levi Project Director & Community Facilitator RADVISION Technology Business Unit