1. CLUE MCU use cases Espen Berger February. 15 – 16, 2012

2. UC –MCU behaviour Alice dial into a MCU and want video on all screens. Alice prefer the MCU to choose which media streams to receive Policy use cases – Alice prefer segment switching over site switching – Alice prefer video-layout = ’hollywood-squares’ – Alice wants to update the switch policy during the call Out of scope (?) – Alice wants to select who is on each screen

3. 3x camera representation A-leftA-MiddleA-Right Composed Switched VC1 (A-Left), VC2(A-Middle), VC3 (A-Right) AC1, AC2, AC3 AC4 (Mixed – room ) VC4, composed AC4, mixed VC5, Switched AC4, mixed

4. MCU - example CD A-leftA-MiddleA-Right B

5. 3x stream offer from MCU An MCU want to send upto 3 video and 3 audio streams, they might or might not be related. CLUE Advertisement Captures VC1 ('Virtual1') not composed; switched; VC2 ('Virtual2') not composed; switched; VC3 ('Virtual3') not composed; switched; AC1 ('Audio1') not composed; switched; AC2 ('Audio2') not composed; switched; AC3 ('Audio3') not composed; switched; CaptureSet { VC1, VC2, VC3 } { AC1, AC2, AC3 }

6. Default view CLUE Configure VC1, VC2, VC3 AC1, AC2, AC3 State1: 2x Personal and 1x meeting room CDB Blaa blaa MCU optimize by having same policy for all capture streams Lip-sync enabled by matching RTCP SDES CNAME No spatial information required except for next active speaker matching

7. Switch policy - Site CLUE Configure VC1, VC2, VC3, switch-policy=’Site’ AC1, AC2, AC3 State2a: 3x camera active speaker (Site switched) State1: 2x Personal and 1x meeting room

8. Switch policy – Segment State1: 2x Personal and 1x meeting room State2: Right segment from triple is active (Segment switching) CLUE Configure VC1, VC2, VC3, switch-policy=’Segment’ AC1, AC2, AC3

9. MCU with Policies – Segment: Switch in only active segment – Site: Switch in whole room – Round-Robin: Rotate every 10 sec – [TEXT+] CLUE Advertisement VC1 ('Virtual1') not composed; switched; switch-policy={Segment, Site, Round-Robin} CLUE Configure VC1, switch-policy={Segment}

10. MCU with Video-layout (Inspired by xcon [1]) – dual-view, single-view, Hollywood-squares – [TEXT+] // Extension point CLUE Advertisement VC1 (’Composed1') composed; not switched; video-layout={dual-view, hollywood-squares } CLUE Configure VC1, video-layout=hollywood-squares // Or with both VC1, switch-policy=Segment, video-layout=hollywood- squares

11. Participant lock – A named participant (e.g. From RFC4575 or XCON) – Can be requested by conference identifier CLUE Advertisement VC1 (’Composed1') composed; not switched; participant-lock=true CLUE Configure VC1, particpant=’charlie@acme.org’

12. Correlate information RTCP SDES – CNAME: Canonical name (RFC3550) – SRCNAME: to Label Individual Sources (draft-westerlund-avtext-rtcp-sdes-srcname-00) Lip-sync enabling – Same CNAME & SRCNAME Media stream identifiers (msid) Meta – information

13. Issues How to handle advertisements with 25 streams – An MCU could offer 1 – N and EP can request M Reproduction of audio when positions are not fixed Grouping of capture streams when you request 3x switched streams? How to lock participants when the offer from MCU is 3x virtual streams – XCON or RFC4575 CLUE policy announcement? – E.g. Switch-policy = { site, segment, round-robin }

14. THANK YOU

15. A regular three screen system Has three screens Can receive 6x audio streams LeftMiddleRight Speaker