thomas baron. user communities and needs audioconference videoconference webcast av recording ...
TRANSCRIPT
User Communities and Needs Audioconference Videoconference Webcast AV Recording Chat Indico General Public Information
2300 staff people in 10 departments >10000 users 2 sites CH/F
257 physical meeting rooms! Typically in a collaboration ~70-100
(official) meetings per day
“Collaboration is working together to achieve a goal” Wikipedia
Sharing InformationDebatingAnalysingDecidingVoting…
Physical meetingE-communicationRemote meetings…
Building (accelerators, experiments…)OperatingDiscovering (new physics etc.)…
Remote collaborationTextual e-communication
○ Synchronous: chat etc.○ Asynchronous: email, blogs, web etc.○ Medium: IP
Audio○ Telephone; point2point, multipoint (audio-conferencing)
(medium: copper wire)○ VoIP (medium: IP)
Audiovisual○ Synchronous: videoconference, webcast○ Asynchronous: video recordings ○ Medium: IP
Audioconference
Phone conferencing3-way directly from the traditional desktop
phoneVia the PBX (29 participants max) through
the PSTN phoneVia the CERN standard (for the
organisation), needs bookingVia the Alcatel Audioconference system
Videoconference A natural evolution Visual as opposed to strictly audio
Better presence feeling, clearer understanding (body language…)
Usually on public IP networks Efficient if
Good quality (resolution, framerate etc.)Low latency ( < 250ms ); impact depends on the
interactivityOn any network condition (jitter, packet loss, net
latency)Excellent audio required (echo cancellation, lip sync…)
Videoconference Cost saver (travel, hotel, food…) Time saver (travel…) Fast and efficient Green! (reduces CO2 emissions)
Example: one person from Chicago needing to travel 5 times per year to Geneva:10000kg CO293 hrs productive time lost2500 EUR
Videoconference: Rooms
Since about 10 years Currently 60 equipped rooms… and
growing! Industry-standard equipment: H323/SIP
compatible
Videoconference: Rooms Various sizes and configurations
From 6 people (small meeting rooms) to 100 + people (amphitheatres)
Homogeneity of interfaces Tandberg/Cisco equipment
System reliability Remote Administration/Support
Centralized H.323 endpoints manager: TMS (Tandberg Management Suite)○ Usage statistics○ Diagnostics and Alarms○ Software update
Videoconference: H323 H.323-based Videoconference
Industry Standard Point to point (direct connection from one endpoint to the other) MCU (multipoint control units) – expensive hardware units on which
the H.323 endpoints can connect for meetings with more than 2 sites○ Embedded small MCUs in VC codecs (<5 sites)○ MCU services
EsNet in the USA RMS in France DFN in Germany CERN recently purchased a Tandberg MSE8000 MCU
Additional Features○ Data sharing (H.239)
Scale:○ Limited by the number of ports (usual average of 10 to 20 sites per
meeting)
Videoconference: H323
Routing
MCU
Limitations:- Scale- Latency: transcoding, Multiplexing, rate matching- Topology: single point of Failure; cascading is difficult
Videoconference: H323
Pros:High qualityHigh reliabilityHigh compatibility
Cons:LatencyTopologyRoom-based mostly!
Videoconference: EVO Desktop videoconference
Java based: multiplatform (win, mac, linux) Compatible with the H323 world (gateways) Created by Caltech in the 90s based on CERN
needsNow 90% of all LHC VC sessions~ 40 meetings per day
ScaleHundreds of people connected (peak 800) overallPeak of >350 people connected to the same
meeting!
Videoconference: EVO
Integrated features:ChatPresenceRecording
http://evo.caltech.edu
Videoconference: EVO
Participants
Recording
Chat
Video window
Buddy list
Whiteboard
Desktop sharing
Shared files
Videoconference: EVO
Flexible and extensible routing/topologyInherited from the research computing gridsTransparent server failure recovery
MonALISA Evo client
Test !
Videoconference: Vidyo
Desktop VC Ongoing pilot
Potential future alternative for CERN Globally same routing strategy than EVO
but introduces an interesting tech change: H.264 SVC (scalable video coding)Better resilience to network problemsLatency reduced to the minimum (no
transcoding!)
Videoconference: Vidyo
SupportsH323 devicesPhonesPCs (mac, win, linux)Mobile devices (Android, iOS)
Test!
Videoconference: Use Cases
MobilityStay connected everywhere with mobile
devices (wifi, 3G)Airport, planes, trains!
Recruitment interviews
Webcast
Typical audiences (simultaneous connections):Around 50 people for seminars100 for collaboration meetings1500 for AMS live launch15000 for LHC startup in 2008 (several
hundred thousands unique Ips)
Using CERN servers
Using streamingcompanies
Webcast: Infrastructure 4 Flash Media Servers
1 “origin” (master); 3 “edges” (slaves), load-balanced 12 encoder PCs (= rooms equipped)
encoder
origin
Edge #1
Edge #2
Edge #3
Clients
LAN WAN
Webcast: Acquisition
Needs same inputs as VC: Reuse! VGA + Camera
VC Device
Presenter PC
Osprey 240e audio/video acquisition
Epiphan DVI2USB
Audio + video
VGA
Webcast: Acquisition
Encoding (live+recording): Flash Media Live Encoder
Added home made web layer for operation
Webcast: Monitoring
Flash Administration Console Live statistics
Webcast: Use Cases LHC First Beam:
Date: 10th September 2008Duration: 9.5 hoursAudience:
○ ~2-500.000 webcast○ 2488 TV news reports
Servers: initially CERN then
GroovyGecko (partner)Location: CERN Control
CenterCommunication: Satellite uplink (Eurovision/EBU) +
videoconference (experiments CRs)View
Webcast: Use Cases LHC First Physics:
Date: 30th March 2010 Duration: 6.5 hours Audience:
○ ~700.000 webcast○ ~800 TV news reports
Servers: GroovyGecko
(partner) Location: CERN Control
Center + experiments Control
rooms Communication: Satellite uplink (Eurovision/EBU) + fiber
(experiments CRs) View
Webcast: Use Cases
AMS Launch : Date: 16th May 2011Duration: 1 hourAudience: 1500/3300Servers: CERNLocation: CERN A/V Studio and Kennedy Space
CenterCommunication: Satellite downlink+uplink
(Eurovision/EBU)View
Webcast: Use Cases
ATLAS Live6 permanent TV channels
○ Internal information○ Outreach
Servers: CERNFormat: web + Android + iPhone
Web Lectures
Video on demand Live webcast recordings Publishing system developed in
collaboration with the U. of Michigan https://micala.cern.ch Lectures published on CDS New player under development Project with iTunesU
Web Lectures
Processes:Recording 2 videos full frame
○ Camera○ Slides
Automated change detection on SlidesManual slides checkCreation of XML fileTranscoding to web formatsPublishing on CDS
Chat
New service for CERN Synchronous text-based interactions
with presence information Based on jabber (XMPP compliant) and
Jappix (web client)
Indico: What is it?
Integrated Digital Conference Data repository:
Long term archival of events related material (slides, minutes etc…)
Event organisation web app Live event support tool Hub for CERN collaboration services
Indico: History
Started as an European Project (2002):First time used in 2004
In production at CERN: http://indico.cern.ch
And in > 90 institutions around the world:GSI, DESY, Fermilab,…
• Free and Open Source
Indico: History
Stats:140k events620k talks800k files~10.000 visitors per day
Indico: Conference Management Supports the whole event lifecycle
1. Fully customizable web portal2. Programme definition3. Call for abstract and reviewing4. Registration, e-payment, badge creation5. Agenda creation6. Submission of slides and papers7. Paper reviewing8. Evaluation survey
Ex.: OAI7, iCHEP 2010
Indico: Simple Events
Timetable, material storage and … Collaboration Services bookings Ex.: ISEF2011 students at CERN!
General Public Information Network of connected information
screens (LCD screen + PC) One central server Implemented using the Scala solution Central management web interface
GroundFloor
FirstFloor
GPI: Use Cases
Conference Rooms attached screens 4 Panels outside Rooms B, C, D, E
Display the next 4 events in each meeting room
GPI: Use Cases
General Meeting announcement 2 Global Directions Panels
Display events of the day in rooms A, B, C, D, E and F
GroundFloor
FirstFloor