Transcript Content Delivery Infrastructure

Content Delivery Development
Activities
Roger Bolam
June 2005
TNC 2005
1 of 35
Content Delivery Activities
• Content Delivery
• Videoconferencing
– JVCS onDemand
– JVCS Check
– Access Grid
• Voice over IP
June 2005
TNC 2005
2 of 35
Content Delivery
• CDN Architecture Group (streaming)
• Involved in a number of initiatives
including
– Audio streaming and download
– Shaping and strategy for future UK content
delivery
• Monitoring Digital TV developments
– Possible networked delivery of Teachers TV
June 2005
TNC 2005
3 of 35
JVCS-onDemand
• Instant videoconferencing scheduling for
up to 48sites, using bespoke booking
system
• Voice switched or continuous presence
with data and application sharing
• Videoconference sessions can be
managed by users
June 2005
TNC 2005
4 of 35
June 2005
TNC 2005
5 of 35
June 2005
TNC 2005
6 of 35
June 2005
TNC 2005
7 of 35
June 2005
TNC 2005
8 of 35
June 2005
TNC 2005
9 of 35
June 2005
TNC 2005
10 of 35
JVCS-check
• Automated audio and video analysis tool
• Instantly useable through JVCS
onDemand
• Improves scalability of JVCS resources
• Promotes good practice for
videoconferencing use within JANET
community
June 2005
TNC 2005
11 of 35
Technology
Hamlet PLM-1 Overlay Unit
Audio In
Video In
DVD Player
Video Out
Audio Out Video Out
AMX Controller
Video Distribution
Amplifier
Audio
Amplifier
Audio Amplifier
Audio Out
Video Out Video In
Video In
Audio In Video In
Serial Port
Tandberg 6000
Network
June 2005
Monitor
TNC 2005
12 of 35
Access Grid Support Centre
• Fully operational service to UK e-Science
Videoconferencing community
• 50+ nodes deployed and registered to use
service
• Developments in H.323/AG/VRVS
conversion facilities and quality assurance
testing
• Other developments include improved VIC
and RAT and presentation collaboration.
June 2005
TNC 2005
13 of 35
Videoconferencing Futures
• Videoconference recording and content
ingestion
• SIP videoconferencing
• AGSC QA testing
• Fully automated JVCS-IP (using
onDemand technology)
June 2005
TNC 2005
14 of 35
Voice
• Created Voice Advisory Group
• Testing of local and end to end voice on
JANET
• JANET community voice survey
• Consider voice models for JANET
community
• Monitor regulations
June 2005
TNC 2005
15 of 35
Traditional Voice Model
PBX Z
PBX Y
PSTN
June 2005
TNC 2005
16 of 35
VoIP Model
VoIP
PBX
June 2005
VoIP
PBX
IP Network
TNC 2005
17 of 35
Integrated Model
PBX
PBX
PSTN
PSTN
PSTN
VoIP
VoIP
IP Network
June 2005
TNC 2005
18 of 35
How is VoIP being used
• Replacing local telephony switching
equipment (PBX) with VoIP solutions
• Utilising PC’s with VoIP software clients
• Using IP networks to “backhaul” voice
traffic
• VoIP uses packet switched networks
(shared and best efforts), traditional
telephony uses circuit switched networks
(dedicated and predictable)
June 2005
TNC 2005
19 of 35
VoIP Today
• Skype 23 million users (15 thousand new
users per day)
• VoIP equipment in wide spread in JANET
community – inter organisational basis
• Traditional equipment suppliers -Mitel,
Avaya, Erricson coming in to marketplace
• Traditional telcos routing voice traffic over
IP networks
June 2005
TNC 2005
20 of 35
VoIP on JANET
• JANET is a best efforts IP network that
can support VoIP
• UKERNA is not a telecommunications
provider
• Voice traffic is routed over JANET
everyday
• Development work continues to ensure
people can communicate over JANET in
an effective manner
June 2005
TNC 2005
21 of 35
VoIP and Reguations
• Five EU directives covering; Framework;
interconnection and access; data
protection; universal service; authorisation
• Ofcom regulations only applicable to
certain “types” of VoIP service
• Technology is maturing – regulations are
evolving
• VoIP handset is not necessarily a
telephone
June 2005
TNC 2005
22 of 35
Publicly Available Telephone Services
• PATS heavily regulated, ECS are not
• PATS are regulated as a telecommunications
provider – 999, operator services and availability
criteria
• Number of key criteria define PATS;
– a service available to the public
– for originating and receiving national and international
phone calls
– that provides access to the emergency services; and
– through a number or numbers in a national or
international telephone numbering plan
June 2005
TNC 2005
23 of 35
Why VoIP?
• Potential cost saving in the longer term
• Convergence of data and voice
infrastructures
• Feature Rich (locally)
• Voice manufacturers and providers may
force the issue (evolve or die)
• Mobility
June 2005
TNC 2005
24 of 35
VoIP Services?
• Three possible models for VoIP services
on JANET
• SIP supported services on JANET, and
provide directory services
• Deploy and manage central VoIP switch
with tailored clients
• Provide advice and central support for
trunking / interconnecting PBX
June 2005
TNC 2005
25 of 35
VoIP Services?
• Three possible models for VoIP services
on JANET
• SIP supported services on JANET, and
provide directory services
• Deploy and manage central VoIP switch
with tailored clients
• Provide advice and central support for
trunking / interconnecting PBX
June 2005
TNC 2005
26 of 35
Central
Directory
Server
JANET
Oxford
Reading
PSTN
June 2005
TNC 2005
27 of 35
VoIP Services?
• Three possible models for VoIP services
on JANET
• SIP supported services on JANET, and
provide directory services
• Provide advice and central support for
interconnecting local voice switches
• Deploy and manage central VoIP switch
with tailored clients
June 2005
TNC 2005
28 of 35
JANET
Oxford
June 2005
Reading
TNC 2005
29 of 35
Oxford
Bristol
JANET
Swansea
June 2005
Reading
TNC 2005
30 of 35
VoIP Services?
• Three possible models for VoIP services
on JANET
• SIP supported services on JANET, and
provide directory services
• Provide advice and central support for
trunking / interconnecting PBX
• Deploy and manage central VoIP switch
with tailored clients
June 2005
TNC 2005
31 of 35
Oxford
Swansea
JANET
Central JANET
Voice Server
Reading
June 2005
Bristol
TNC 2005
32 of 35
Bristol
Oxford
JANET
Central JANET
Voice Server
Swansea
June 2005
Reading
TNC 2005
33 of 35
VoIP considerations
• Choice of local VoIP equipment critical
• Support for SIP in a standards based
environment (including manufacturer interworking)
• Addressing and numbering – expandable and
standards based (ENUM and e.164)
• PSTN breakout – remains with the telcos (at the
moment)
• Where does this technology sit within the
organisation? (telephony / data)
June 2005
TNC 2005
34 of 35
Contact Details
Roger Bolam
[email protected]
Arron Bowley
[email protected]
http://www.ja.net/development
June 2005
TNC 2005
35 of 35