1 / 10

Mediactrl Framework

This draft proposes a framework for defining the logical entities and model for core interactions between Application Servers (AS), Media Servers (MS), and Media Resource Brokers (MRB). It focuses on the use of SIP for establishing control channels and media sessions, providing a common framework and leveraging SIP for location, security, session negotiation, and MS selection. The draft also discusses scenarios such as IVR services, XCON mapping, and conference services.

pantano
Download Presentation

Mediactrl Framework

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. Mediactrl Framework • draft-melanchuk-mediactrl-framework-00 Tim Melanchuk (Ed.) tim.melanchuk@gmail.com

  2. Framework Goals • define the logical entities for the protocol: • Application Server (AS) • Media Server (MS) • Media Resource Broker (MRB) • define a model for core interactions • define entity roles for several key use case scenarios • Non goal: define specific protocol functions

  3. Model - Control Channel • AS uses SIP to establish TCP/TLS connection to MS • SIP dialog called “Control Dialog • TCP/TLS connection called “Control Channel” • SIP/SDP signaling based on COMEDIA • draft-boulton-sip-control-framework-05 • may be m:n control channels between AS(s) & MS(s) • control channels used as transport for MediaCtrl Protocol Application Server SIP (Control Dialog) TCP/TLS (Control Channel) Media Server

  4. User Agent Media Server Model - Media Sessions • Signaling for media sessions between UA & AS may be SIP or other protocol • AS signals to MS using SIP • SIP dialog called “Media Dialog • Standard 3PCC model if UA & AS use SIP • no relation between media sessions and control channels • media sessions identified within the MediaCtrl Protocol Application Server SIP (Control Dialog) User Signaling (e.g. SIP) SIP (Media Dialog) TCP/TLS (Control Channel) RTP/SRTP

  5. Model Benefits • Using SIP to establish both Control Channels and media sessions provides a common framework and allows leveraging SIP for: • location and rendezvous capabilities • security and identity properties • session negotiation (RTP for media, TCP for control) • selection of MS based on capability sets (RFC 3840) • TCP/TLS Control Channel(s) allows for reliable transmission of arbitrary sized PDUs

  6. IVR Services • For simple announcement services, an AS may use the R-URI mechanism from RFC 4240 instead of Control Channels • For interactive services, AS uses MediaCtrl Protocol in the Control Channel to request MS IVR functions • VoiceXML services may be requested by an AS using either MediaCtrl Protocol in the Control Channel or the RFC 4240 R-URI mechanism

  7. XCON Mapping SIP User Signaling • AS has the role of the conference focus • MS acts as the media mixer Participant A (Conference Aware) Application Server (Focus) XCON User Signaling H3.23 User Signaling SIP (Control Dialog) SIP (Media Dialog) for A RTP/SRTP Control Channel (MediaCtrl Protocol) SIP (Media Dialog) for B Participant B Media Server (Mixer) RTP/SRTP

  8. Conference Services • AS uses MediaCtrl Protocol in the Control Channel to request functions such as: • allocate, manage, and remove media mixers • IVR functions for participants or the mix (e.g. announcements or recording) • media related controls, such as requested by conference aware participants through an XCON protocol (e.g. “unmute me”) • Participants are added/removed via either SIP (conference URI of the SIP Media Dialog) or using the MediaCtrl Protocol

  9. Floor Control & BFCP • BFCP defines Floor Control Server (FCS) & Floor Chair • Floor Chair is part of application logic and if automated, should be part of the AS • FCS could be co-located with either the AS or MS but both need to interact with the FCS (e.g. via the Control Channel) • Scenario of the FCS co-located with MS is described in the draft

  10. Discussion • Is this the right model? • What else is needed? • MRB discussion? • Control Channel usage (e.g. which entity initiates)? • more/less scenario discussion? • other? • Adopt as WG item?

More Related