Your SlideShare is downloading. ×
SIPquest-Intel Sept29.ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SIPquest-Intel Sept29.ppt

161
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
161
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×