190 likes | 289 Views
IPTComm2007 New York, July 19 th 2007 A. Amirante, T. Castaldi, L. Miniero and S.P. Romano COMICS (COMputers for Interaction and CommunicationS) research group University of Napoli Federico II.
E N D
IPTComm2007 New York, July 19th 2007 A. Amirante, T. Castaldi, L. Miniero and S.P. Romano COMICS (COMputers for Interaction and CommunicationS) research group University of Napoli Federico II “Improving the scalabilityof an IMS-compliant conferencing framework through presence and event notification” IPTComm2007 -- New York City, July 19th 2007
IPTComm2007 -- New York City, July 19th 2007 Agenda • Rationale & Motivation • A standard centralized conferencing architecture • Performance assessment and bottlenecks identification • Improving scalability through distribution of components/responsibilities • Conclusions
IPTComm2007 -- New York City, July 19th 2007 Conference • The term “Conference” can be used to describe any meeting of people that “confer” about a certain topic • Web Conferencing is used to indicate live meetings or presentations over the Internet
IPTComm2007 -- New York City, July 19th 2007 Standardization efforts • No standardization for many years • Lack of interoperability • Platform dependency • Security issues • Cost • Market segmentation • Standardization Bodies • ITU (International Telecommunication Union) • IETF (Internet Engineering Task Force) • 3GPP (3rd Generation Partnership Project)
IPTComm2007 -- New York City, July 19th 2007 IETF SIPPING Working Group • Session Initiation Proposal Investigation • Documents the use of SIP for several applications related to telephony and multimedia • SIP Conferencing Loosely-Coupled Conference Fully Distributed Multiparty Conference Tightly-Coupled Conference SIP Conferencing Framework (RFC 4353): fundamental elements • Notification Service (Event Package, RFC 4575) • Participants • Focus • Policy Server • Mixer
IPTComm2007 -- New York City, July 19th 2007 XCON Working Group • Centralized Conferencing (XCON) • Extends RFC 4353 • Protocol-agnostic (not only SIP) • Data Sharing (not only audio/video) • Suite of Protocols • Conference Control (CCMP?) • Floor Control (BFCP) • Call Signaling (SIP/H.323/IAX/etc.) • Notification (Event Package?)
IPTComm2007 -- New York City, July 19th 2007 XCON Framework Conferencing System Conference Object Conference Object Conference Object Conference Control Server Floor Control Server Focus Notification Service Floor Control Protocol Conference Control Protocol Call Signaling Protocol Notification Protocol Conference Control Client Floor Control Client Call Signaling Client Notification Client Conferencing Client
IPTComm2007 -- New York City, July 19th 2007 CONFIANCE • CONFerencing IMS-enabled Architecture for Next-generation Communication Experience • http://confiance.sourceforge.net/ • Open source implementation of the XCON Framework, compliant with the IMS specification • Extends the Asterisk PBX functionality • Enhanced “MeetMe” application • Support for Conference Management (Scheduler) • Support for Floor Control (BFCP) • Support for BFCP-guided video switching/mixing • Support for MSRP (Message Session Relay Protocol) text chatrooms
IPTComm2007 -- New York City, July 19th 2007 Why Distributed Conferencing? • Centralized Conferencing • Poorly scalable • Limited capabilities • Single point of failure • Towards distribution: • Cascaded Conferencing • Each focus is seen as a participant by the others • Only affects mixers' distribution • Centralized protocols like BFCP don't work
IPTComm2007 -- New York City, July 19th 2007 XMPP SIP DCON Proposal • Distributed Conferencing (DCON) • http://dcon.sourceforge.net/ • Orchestrates the operation of a set of XCON “clouds” • Overlay network interconnecting the clouds • Intra-focus communication • Still based on XCON protocols • Inter-focus communication • Exploits Server-to-Server (XMPP) • Requirements • Focus discovery • Initialization information & spreading of conference events • Setup and managing of distributed conferences • Transparent dispatching of natively centralized protocols among the involved conferencing clouds
IPTComm2007 -- New York City, July 19th 2007 DCON Implementation
IPTComm2007 -- New York City, July 19th 2007 Performance assessment • Tool employed: SIPp • SIP traffic generator • Capable to reproduce fully customizable call scenarios through XML configuration scripts • Capable to also reproduce actual media flows through the RTP/pcap replay function • Used to test two different facets of scalability: • Maximum number of users who can access the system • Resource consumption, given a specific number of users Testbed: OS: Linux Fedora Core 6, kernel 2.6.15 CPU 3,2GHz Intel XEON, RAM 2GB
IPTComm2007 -- New York City, July 19th 2007 Scalability: just signaling • Asterisk does not allow to open more than 1024 Zaptel pseudo-channels (i.e. abstractions of physical channels)simultaneously • Each conference, upon creation, makes use of two such channels • Each conference participant uses a single pseudo-channel • Quasi-linear growth in the number of users in the presence of distribution • Note well: No RTP traffic involved in such tests just signaling!
IPTComm2007 -- New York City, July 19th 2007 Scalability: signalling + audio • 300 users as a maximum limit in the presence of audio streams • Might become critical in case many conferences are activated in a cloud • A reference value for the following tests • Centralized case (one single conference)
IPTComm2007 -- New York City, July 19th 2007 Scalability: 2 islands case
IPTComm2007 -- New York City, July 19th 2007 Scalability: 3 islands case
IPTComm2007 -- New York City, July 19th 2007 Scalability: figures in summary • Migration towards a distributed paradigm allows for a huge reduction in the load of the primary focus • The sum of the CPU levels of all involved foci is less than the CPU level of the single focus in the centralized case • Given a fixed number of local users, remote users distribution among multiple islands adds negligible overhead to the main focus
IPTComm2007 -- New York City, July 19th 2007 Future Work • More performance tests: • Different media: • Involve video, chat, desktop sharing applications, etc. in the trials • Different protocols • Involve BFCP, Conference Control Protocol, etc. in the trials • Different scenarios • Try to reproduce real-world conference configurations • Different overlay topologies • Not just full meshes • Investigate smart p2p approaches
IPTComm2007 -- New York City, July 19th 2007 What else? • See all of you at the demo tomorrow! • Have a look at DCON up and (hopefully ) running… • We also present: • our brand new JAVA-based integrated client • our current prototype of the distributed approach to video mixing • Our contacts: • tobia.castaldi@unina.it • lorenzo.miniero@unina.it • spromano@unina.it • alex.amirante@tin.it