SIPquest-Intel Sept29.ppt


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SIPquest-Intel Sept29.ppt

  1. 1. The Future of Enterprise Communications Henning Schulzrinne Chief Scientist, SIPquest Associate Professor, Columbia University, New York September 2003
  2. 2. Enterprise Communication Needs Factory/Plant Teleworkers Branch Office Mobile Professionals Main Office Enterprise Evolving business models and workforce environments Partners/Suppliers Customers
  3. 3. The Future of Enterprise Communication Integrated Multimedia Communication System Enterprise Application Sharing Co Web-browsing Instant Messaging Video Conferencing Audio Conferencing Rich Presence Context Aware Mobility & Multidevice Scheduled & Ad hoc Personalization Synchronous and Asynchronous
  4. 4. Overview <ul><li>Advanced enterprise multimedia communications – beyond the IP PBX </li></ul><ul><ul><li> next-generation VoIP </li></ul></ul><ul><li>Core characteristics and requirements </li></ul><ul><li>Using wireless LAN technology as an enabler for ubiquitous communications </li></ul><ul><li>Roaming beyond the enterprise </li></ul><ul><li>Challenges: E911, management, scaling, reliability </li></ul>
  5. 5. Context-aware multimedia communications <ul><li>Most teams and groups need two forms of collaboration: </li></ul><ul><ul><li>real-time (synchronous)  telephone, ISDN video conferencing, IM </li></ul></ul><ul><ul><li>non-real-time (asynchronous)  mailing lists, shared calendars, shared document folders, project-internal web pages, … </li></ul></ul><ul><li>But… </li></ul><ul><ul><li>each team or group needs to set up complex set of ad-hoc tools </li></ul></ul><ul><ul><ul><li>difficult  often, collaboration = long cc email list </li></ul></ul></ul><ul><ul><ul><li>access control tedious, particularly for external partners </li></ul></ul></ul><ul><ul><li>no integration of synchronous and asynchronous collaboration </li></ul></ul><ul><ul><ul><li>send email of documents during meeting </li></ul></ul></ul><ul><ul><ul><li>versioning problems </li></ul></ul></ul><ul><ul><ul><li>difficult for late joiners or management to catch up </li></ul></ul></ul>
  6. 6. Solution: integration of “phone” and “email/web” world <ul><li>Create a single, task-oriented group </li></ul><ul><li>Records and structures all interactions </li></ul><ul><ul><li>ad-hoc and scheduled (repeating) multimedia conferences: voice, video, text chat, guided web browsing, application sharing </li></ul></ul><ul><ul><li>presence for coordination and presence-enabled ad-hoc conferences </li></ul></ul><ul><ul><li>bulletin board </li></ul></ul><ul><ul><li>shared, protected web pages </li></ul></ul><ul><ul><li>mailing list </li></ul></ul><ul><ul><li>access to recordings of conferences, including IM and application sharing interactions </li></ul></ul><ul><li>SIP as integrating component </li></ul><ul><ul><li>multimedia communications </li></ul></ul><ul><ul><li>event notification, IM and presence </li></ul></ul><ul><ul><li>easily supports cross-enterprise collaboration </li></ul></ul>
  7. 7. Context-aware communication <ul><li>Diversity: Participants with many different devices </li></ul><ul><ul><li>temporarily only access to analog hotel phone or cell phone </li></ul></ul><ul><ul><li>borrowed computer at remote site </li></ul></ul><ul><li>Human context: </li></ul><ul><ul><li>How interruptible am I? </li></ul></ul><ul><ul><li>Where am I – home? movie theatre? office? driving? </li></ul></ul><ul><ul><li>What time zone am I in? </li></ul></ul><ul><ul><li>How much privacy does my environment offer? </li></ul></ul><ul><li>Use “sensors” to determine context information </li></ul><ul><ul><li>data: calendars </li></ul></ul><ul><ul><li>device interaction: which device am I using? been typing lately? </li></ul></ul><ul><ul><li>environment: badges, PIR sensors, RFID, … </li></ul></ul>DHCP server 458/17  Rm. 815 458/18  Rm. 816 DHCP answer: sta=DC loc=Rm815 lat=38.89868 long=77.03723 8:0:20:ab:d5:d CDP + SNMP 8:0:20:ab:d5:d  458/17
  8. 8. Context-aware communications <ul><li>Working within IETF to standardize descriptions for “rich presence” information </li></ul><ul><ul><li>activity, privacy, future activities </li></ul></ul><ul><ul><li>multi-device presence </li></ul></ul><ul><ul><li>assistants and associates </li></ul></ul><ul><li>Also, related to geographic location information </li></ul><ul><ul><li>facilitate face-to-face collaboration </li></ul></ul><ul><ul><li>guide user to appropriate resources (“a conference room with video camera is just around the corner”) </li></ul></ul><ul><li>But needs to respect need for user control and privacy </li></ul><ul><ul><li>IETF is defining privacy policy language </li></ul></ul><ul><ul><li>allows user to control access and propagation of information </li></ul></ul>
  9. 9. Context-aware communication <ul><li>“Opportunistic communications” </li></ul><ul><ul><li>old style: lug around devices – projector, speaker phone, laptop, … </li></ul></ul><ul><ul><li>new: service discovery  borrow networked (wireless) devices in environment </li></ul></ul><ul><ul><ul><li>video projector, echo-cancelled microphone, plasma display, … </li></ul></ul></ul><ul><li>Move live sessions from single, mobile device to multiple local devices  session mobility </li></ul><ul><li>Keep configuration information even when moving and changing devices  service mobility </li></ul><ul><li>Many devices, one address  user mobility </li></ul>
  10. 10. Requirements for context-aware collaboration <ul><li>Cross-platform </li></ul><ul><ul><li>users may temporarily use devices from copy service </li></ul></ul><ul><ul><li>devices from smart cell phone and hotel TV web browser to desk top PC </li></ul></ul><ul><ul><li>participants from different organizations </li></ul></ul><ul><li>Thus, importance of standards </li></ul><ul><ul><li>beware of “our improved version of standard” </li></ul></ul><ul><ul><li>here, web and Internet technologies </li></ul></ul><ul><ul><ul><li>SIP for multimedia communications, IM, presence, events </li></ul></ul></ul><ul><ul><ul><li>RTSP for access to streaming media (media resources, conference recordings) </li></ul></ul></ul><ul><ul><ul><li>HTTP and web services for user interface, conference control and web-based collaboration </li></ul></ul></ul><ul><ul><ul><li>SMTP (and related) for asynchronous collaboration </li></ul></ul></ul><ul><ul><ul><li>RTP for multimedia content </li></ul></ul></ul><ul><ul><ul><li>XML for cross-platform document sharing and whiteboards </li></ul></ul></ul><ul><ul><li>not just protocols, but also configuration and management </li></ul></ul>
  11. 11. Wireless LANs as a key enabler <ul><li>Ubiquitous and context-aware communications requires integrating all modes of wireless communications: </li></ul><ul><ul><li>2G and 3G cellular networks – low-speed data, but broad coverage </li></ul></ul><ul><ul><li>cluster of hotspots with roaming </li></ul></ul><ul><ul><ul><li>e.g., within corporate campus or in convention center or airport) </li></ul></ul></ul><ul><ul><li>sparse 802.11 hotspots </li></ul></ul><ul><li>Need to be able to roam across systems: </li></ul><ul><ul><li>with authentication, authorization, accounting hand-off </li></ul></ul><ul><ul><li>real-time hand-off for on-going multimedia conversations </li></ul></ul><ul><ul><ul><li>maybe across devices </li></ul></ul></ul><ul><li>SIP can support mobility even if network not fully mobility-enabled </li></ul>
  12. 12. Concerns and Issues <ul><li>E-911 </li></ul><ul><ul><li>E-911 difficult for VoIP (and other networked multimedia) </li></ul></ul><ul><ul><li>locate nearest emergency service, not the one on the other end of the VPN </li></ul></ul><ul><ul><li>IP address does not provide location </li></ul></ul><ul><ul><li>Emergency service needs to determine user location </li></ul></ul><ul><ul><ul><li>efforts in North American Emergency Number Association (NENA) to provide architecture </li></ul></ul></ul><ul><li>Management of these capabilities from a variety of devices </li></ul><ul><ul><li>basic configuration via phone </li></ul></ul><ul><ul><li>human configuration via web page </li></ul></ul><ul><ul><li>automated configuration and scripting via web services and standardized configuration files </li></ul></ul><ul><li>Security, Authentication and authorization </li></ul><ul><ul><li>prevent VoIP spam </li></ul></ul><ul><li>QoS for WLAN, primarily </li></ul>
  13. 13. Conclusion <ul><li>Convergence is more than just the conversion of analog phones to packets </li></ul><ul><ul><li>just transport convergence misses opportunities for productivity enhancements and doesn’t solve the lack of use of most tools </li></ul></ul><ul><ul><li>need to do more than replicate dial tone </li></ul></ul><ul><li>Converge synchronous and asynchronous collaboration </li></ul><ul><li>Make capabilities available without configuration – but users only see tools they need and want </li></ul><ul><li>Needs to work in mobile environment – 2G, 3G and 802.11 </li></ul><ul><ul><li>single device and multiple mobile devices </li></ul></ul><ul><li>Cross-platform and standards-based – otherwise, always fall back to least-common denominator phone conference </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.