Transcript PPT - Homepage

P4P meeting
Eitan Efron, VP BD
[email protected]
January 2008
The Bandwidth Explosion
Demand for P2P and Video Creates Pressure
And the network just can’t cope…
Existing Infrastructure
P2PTV
(Joost etc.)
HTTP Video
(YouTube etc.)
P2P
Downloads
(BitTorrent etc.)
Bandwidth Demand
P4P targets: max delivery, minimize ISP pain
POOR user experience
New Technologies are Required
%
of traffic
UnMonetized
P2P
Internet
video
Can not
be
throttled
Throttled
using DPI
Monetized
P2P
Time
Cache = Network Optimization Engine
Core / POP
Router
DPI
Cache
Saves on bandwidth
Ensures & accelerates
QoS
Reduces pressure on the network
Complements DPI install base
Defers infrastructure upgrades
Backbone
Out of main
traffic path
Caching = Up to 95% Savings !
X 20 value
(95% BHR)
Cache
Out
In
3Gbps
250Mbps (80Mbps international)
Caching = Accelerated Performance
BitTorrent Cache acceleration example
680MB, Maple Story Update
Peers only
With server
With Cache
DWLD speed
65Kb/s
375Kb/s
9.2Mb/s
DWLD time
23 hours
4 hours
9 minutes
X 150 faster
performance
High Definition (HD) Delivery Opportunity
Cache = Monetization through Service
Differentiation
Charge Users
for performance
Charge Content
owners for delivery
GOLD
5 Mbps
500 GB
HD
5 Mbps
SILVER
500 Kbps
50 GB
SD
500 Kbps
10 GB
basic
best effort
BRONZE 50 Kbps
SLA / Acceleration
Users
Over the top content
Cache
ISP content
P4P Modes
A
1.
2.
3.
4.
AppTracker
Peer query Tracker
AppTracker quarries iTracker (3)
iTracker sends peering suggestions (2)
Tracker updates peers’ list
iTracker
2
3
1
Internet
4
ISP
Peer
B
C
AppTracker
Internet
2
iTracker
iTracker
3
1
Peer
3
1
4
ISP
2
ISP
Peer
4
AppTracker
Internet
iTracker May Increase Load on ISP Network
INTERNET
AppTrackers
iTracker
CORE
internal
Peers
list
ACCESS
ISP
Domain
DSLAM
CMTS
DSLAM
CMTS
DSLAM
CMTS
DSLAM
CMTS
Increase
load on
limited &
expensive
Uplinks
iTracker auto Cache Discovery Optimizes Network
Performance
INTERNET
AppTrackers
Single
Cache can
be located
at core
No Uplink
reciprocity
iTracker
CORE
internal
Peers
+ cache
Cache
ACCESS
ISP
Domain
Relieve
load on
limited
Uplinks
DSLAM
CMTS
DSLAM
CMTS
DSLAM
CMTS
DSLAM
CMTS
iTracker Implementing Cache Discovery
iTracker/AppTracker provide users with a list of Good
Peers & Cache Servers
Good Peers =
Users in same POP range
Users with higher Uplink capacities
Users with lower infrastructure cost metrics
Caches in ISP cloud
POP
NOC
Enables full control by ISP to optimize to ISP
infrastructure constraints
E.g. MSO/WiMAX operators with limited uplinks capacity will
want to reduce load on peer uplinks and increase use of
Caching
iTracker + Cache Field Experience
200% increase in performance
iTracker +
cache discovery
Introduced
Suggested iTracker Cache Discovery Format
A
P4P iTracker
iTracker query
(Get Map)
Map
• IP range -> POP, “cost”
metrics, Good Peers
• IP range -> Cache servers +
Vendor Specific Data (VSD)
AppTracker iTracker
2
1
4
3
Internet
ISP
Peer
ISP/Vendor
DB update
AppTracker
Additional compilation
A. Get Map (iTracker query)
B. Get vendor specific cache location
GetServers(IP,hash,VSD, protocol)
Vendor
Specific
plug-ins
Vendor A
Vendor B
Summary
Cache = relives the load on the network +
sustains/improves QoE + new monetization
opportunities, over existing ISP infrastructure
iTrackers cache discovery = improves savings and
user experience by additional 200%
Further network optimization can occur through
Additional caching levels (e.g. aggregation, Access)
Automatic Cache discovery embedded at Client level (e.g.
where P4P is not implemented), e.g. BitTorrent CDP
Cache + iTracker + DPI
DPI throttles only traffic in local caching devices and local peers
Energize Your Network
Thank you for listening.
Meeting Customers’ Demands in
the New Digital Media Age
www.oversi.com