1 / 24

Orit levin orit@radvision

Conferencing Requirements for SIP Based Applications. Orit levin orit@radvision.com. draft-levin-sipping-conferencing-requirements-00.txt Levin/Even/Zmolek/Petrie/Koskelainen RADVISION/Polycom/Avaya/Pingtel/Columbia University. The Outline of the Draft.

tbatten
Download Presentation

Orit levin orit@radvision

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conferencing Requirements for SIP Based Applications Orit levin orit@radvision.com IETF Interim Meeting

  2. draft-levin-sipping-conferencing-requirements-00.txt Levin/Even/Zmolek/Petrie/Koskelainen RADVISION/Polycom/Avaya/Pingtel/Columbia University IETF Interim Meeting

  3. The Outline of the Draft Hierarchal Application (Signaling) Model SIP Star Conferencing Application SIP Star Real Time Multimedia Conferencing Application IETF Interim Meeting

  4. Reasons for Hierarchal Application Model A Means to Describe the Reality A Basis for Terminology Definition A Means to Understand Each Other’s Requirements A Means to Describe and Classify the Requirements IETF Interim Meeting

  5. Meta Application Objectives Everything that is out of scope of standard applications Different Sets of Participants Everything that is out of scope of SIP Conferencing Application Bridging to PSTN End Users IETF Interim Meeting

  6. Applications’ Reality Example of a Complete Application Presence SIMPLE Based Application Chair Control Application in the Roadmap • Members’ Management • Applications’ Coordination Real Time (Voice and Video) Star Conferencing Application Instant Messaging Full Mesh Application White Board T.120 Based Application IETF Interim Meeting

  7. The Hierarchal Application ModelExample 2 Meta Application SIP Voice Conferencing Application White Board T.120 Based Application Media Control Voice (Data) Plane IETF Interim Meeting

  8. The Hierarchal Application ModelExample 2 Meta Application SIP Voice Conferencing Application Media Control White Board T.120 Based Application Voice (Data) Plane IETF Interim Meeting

  9. SIP Star Conferencing Application Model An Association of SIP User Agents for providing a shared application in Star Topology Center Participant vs. Edge Participants A Center Participant has a SIP Dialog with each one of Edge Participants and internally maintains correlation among the dialogs Both Center and Edge Participants are capable of being a Conference Chair IETF Interim Meeting

  10. SIP Star Conferencing Application SIP Star Conference EDGE SIP Dialog UA CENTER EDGE UA SIP Dialog UA SIP Dialog UA EDGE IETF Interim Meeting

  11. SIP Star Conferencing ApplicationMain Requirements’ Guidelines Tight Conference Control (in contrast to loose) Pre-arranged and Spontaneous Conferencing Support Center Participant SHALL be able to add and disconnect SIP baseline Participants IETF Interim Meeting

  12. SIP Star RT MultimediaConferencing Application Model SIP Star Conferencing Application with one or more RT Media (Data) Planes RT Media Plane is a subset of RTP media streams established by SDP means SHOULD contain Media Control Sub-application(s) May have Data Planes that are not RT Media Planes IETF Interim Meeting

  13. SIP Star Real Time Multimedia Conferencing Application SIP Star Conference EDGE SIP Dialog UA CENTER RTP/RTCP UA EDGE SIP Dialog Media Processor UA RTP/RTCP RTP/RTCP SIP Dialog UA EDGE IETF Interim Meeting

  14. SIP Star RT MultimediaMedia Plane Model Media Plane groups RT media streams (belonging to different SIP dialogs) for various application reasons Media Plane contains zero or more Media Processors Media Processor contains zero or more Presentation Spaces IETF Interim Meeting

  15. Example: a Default Audio “Media Processor” Presentation Spaces M RTP Audio Plane A+B M+B M+C RTP A RTP B M+A+B • Conference participants: • Edge (Remote): A, B, C • Center (Local): M • M, A, and B are the loudest speakers • Note: Each remote participant • has an associated SIP dialog Media Processor RTP C IETF Interim Meeting

  16. A TypicalSIP Star RT Multimedia Conference Center Participant Edge Participant CONFERENCING/CALL PLANE Conferencing Center Logic Conferencing Edge Logic (Optional) Basic UA SIP Basic UA Conferencing Extensions Presentation Spaces VIDEO DATA PLANE MP RTP/RTCP MP RTP/RTCP AUDIO DATA PLANE IETF Interim Meeting

  17. SIP Star RT MultimediaConferencing Application Main Requirements Conferencing “Presentation” Requirements Identity of the user presented to you Presentation status (list) of your media Point-to-Point Requirements Capabilities Exchange Procedure Expressiveness Autonomous Media Control RTCP Feedback Application Driven Media Control Open Issue IETF Interim Meeting

  18. Issues We Need to Address First Hierarchal Application (Signaling) Model Do We Have a Clear Enough Terminology in order to Describe the Requirements? SIP Star Conferencing Application Conference Identification Scope of the Baseline Requirements Baseline Means for their Implementation SIP Star Real Time Multimedia Conferencing Application Direction for Resolving Application Driven Media Control Issue IETF Interim Meeting

  19. A Proposal :Separate the Work into Three DocumentsAllowing for Moving Forward Simultaneously Hierarchal Application (Signaling) Model Definition and Examples SIP Star Conferencing Application Definition Requirements and their mapping to primitives SIP Star Real Time Multimedia Conferencing Application Definition Requirements and their mapping to primitives IETF Interim Meeting

  20. Backup Slides for Follow-up Discussion Conference Identification Application Driven Media Control IETF Interim Meeting

  21. Conference Identification User Wants to Create a Conference with Certain Specifications “Conference Service” Description is Required User Wants to Join an Existing (or a Scheduled) Conference Global Conference Identification is Required IETF Interim Meeting

  22. Implicitly: The URI Option • “SIP URI Conventions for Media Servers” draft-burger-sipping-msuri-01.txt • The Request-URI of INVITE specifies a Conference (rather then a User) • Registration with IANA • Spontaneous Conference • The Initiator of the Conference Creates a Unique Conference Identifier • The New Conference Identifier Triggers Conference Creation by the MCU IETF Interim Meeting

  23. Explicitly: New Headers • “The SIP Join and Fork Headers”draft-mahy-sipping-join-and-fork-00.txt • New Headers Used with INVITE to • Explicitly Join a Dialog (specified by Call-ID) IETF Interim Meeting

  24. Application Driven Media Control Request for maximum (reserved) bandwidth Request for specific (current) bandwidth Request for using specific parameters: CODEC and its Params, Resolution, Frame Rate, etc. A Showstopper: Video Conferencing Applications MUST have deterministic way to switch between video sources IETF Interim Meeting

More Related