P4P meetingEitan Efron, VP BD

eitane@oversi.com

January 2008

The Bandwidth Explosion

And the network just can’t cope…

Existing Infrastructure

Bandwidth DemandPOOR user experience

P2PTV

(Joost etc.)

HTTP Video

(YouTube etc.)

P2P

Downloads

(BitTorrent etc.)

Demand for P2P and Video Creates Pressure

P4P targets: max delivery, minimize ISP pain

New Technologies are Required

%of traffic

Time

Monetized P2P

Un-Monetized P2P

Internet video Can not

be throttled

Throttled using DPI

Cache = Network Optimization Engine

CacheCache

Backbone

Core / POP

RouterRouter

Saves on bandwidth

Ensures & accelerates QoS

Reduces pressure on the network

Complements DPI install base

Out of main

traffic path

DPI

Defers infrastructure upgrades

Caching = Up to 95% Savings !

CacheOut 3GbpsIn 250Mbps (80Mbps international)

X 20 value(95% BHR)

Caching = Accelerated Performance

BitTorrent Cache acceleration example

High Definition (HD) Delivery Opportunity

Peers only With server With Cache

DWLD speed 65Kb/s 375Kb/s 9.2Mb/s

DWLD time 23 hours 4 hours 9 minutes

680MB, Maple Story Update

X 150 faster performance

Cache = Monetization through Service Differentiation

GOLD 5 Mbps

SILVER 500 Kbps

BRONZE 50 Kbps

Charge Usersfor performance

Charge Content owners for delivery

500 GB

50 GB

10 GB

Cache

Users

SLA / Acceleration

HD 5 Mbps

SD 500 Kbps

basic best effort

Over the top content

ISP content

P4P Modes

Peer

AppTracker iTracker

ISP

Internet 1 4

2

3 1. Peer query Tracker2. AppTracker quarries iTracker (3)3. iTracker sends peering suggestions (2)4. Tracker updates peers’ list

Peer

AppTracker

iTracker

ISP

Internet

1 4

2

3

Peer

iTracker AppTracker

ISP

Internet

1 4

2

3

A

B C

iTracker May Increase Load on ISP Network

DSLAM CMTS CMTSCMTSCMTS

INT

ER

NE

TC

OR

EA

CC

ES

S

DSLAM DSLAM DSLAM

iTracker

AppTrackers

ISPDomain

Increase load on

limited & expensive Uplinks

internalPeerslist

iTracker auto Cache Discovery Optimizes Network Performance

DSLAM CMTS CMTSCMTSCMTS

INT

ER

NE

TC

OR

EA

CC

ES

S

Cache

DSLAM DSLAM DSLAM

Relieve load on limited Uplinks

Single Cache can be located

at core

AppTrackers

iTracker

ISPDomain

No Uplink reciprocity

internalPeers+ cache

iTracker Implementing Cache Discovery

iTracker/AppTracker provide users with a list of Good

Peers & Cache ServersGood Peers =

Users in same POP rangeUsers with higher Uplink capacities Users with lower infrastructure cost metrics Caches in ISP cloud

POPNOC

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

iTracker + cache discovery

Introduced

200% increase in performance

Suggested iTracker Cache Discovery Format

Peer

AppTracker iTracker

ISP

Internet 1 4

2

3

A

Map• IP range -> POP, “cost” metrics, Good Peers• IP range -> Cache servers + Vendor Specific Data (VSD)

P4P iTracker

ISP/Vendor DB update

A. Get Map (iTracker query)

AppTracker

Additional compilation

B. Get vendor specific cache locationGetServers(IP,hash,VSD, protocol)

iTracker query(Get Map)

Vendor A

Vendor B

Vendor Specificplug-ins

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

Meeting Customers’ Demands in

the New Digital Media Age

www.oversi.com

Thank you for listening.

Energize Your Network