P 4 P meeting Eitan Efron VP BD

Зарегистрируйтесь, чтобы просмотреть полный документ!

P 4 P meeting Eitan Efron, VP BD eitane@oversi. com January 2008

The Bandwidth Explosion Demand for P 2 P and Video Creates Pressure And the network just can’t cope… Existing Infrastructure P 2 PTV (Joost etc. ) HTTP Video (You. Tube etc. ) P 2 P Downloads (Bit. Torrent etc. ) Bandwidth Demand P 4 P targets: max delivery, minimize ISP pain POOR user experience

New Technologies are Required % of traffic Un. Monetized P 2 P Internet video Can not be throttled Throttled using DPI Monetized P 2 P Time

Cache = Network Optimization Engine Core / POP Router DPI Cache Saves on bandwidth Ensures & accelerates Qo. S 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 3 Gbps 250 Mbps (80 Mbps international)

Caching = Accelerated Performance Bit. Torrent Cache acceleration example 680 MB, Maple Story Update Peers only With server With Cache DWLD speed 65 Kb/s 375 Kb/s 9. 2 Mb/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

P 4 P Modes A 1. 2. 3. 4. App. Tracker Peer query Tracker App. Tracker quarries i. Tracker (3) i. Tracker sends peering suggestions (2) Tracker updates peers’ list i. Tracker 2 3 1 Internet 4 ISP Peer B C App. Tracker Internet 2 i. Tracker 3 1 Peer 3 1 4 ISP 2 ISP Peer 4 App. Tracker Internet

i. Tracker May Increase Load on ISP Network INTERNET App. Trackers i. Tracker CORE internal Peers list ACCESS ISP Domain DSLAM CMTS Increase load on limited & expensive Uplinks

i. Tracker auto Cache Discovery Optimizes Network Performance INTERNET App. Trackers Single Cache can be located at core No Uplink reciprocity i. Tracker CORE internal Peers + cache Cache ACCESS ISP Domain Relieve load on limited Uplinks DSLAM CMTS

i. Tracker Implementing Cache Discovery i. Tracker/App. Tracker 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/Wi. MAX operators with limited uplinks capacity will want to reduce load on peer uplinks and increase use of Caching

i. Tracker + Cache Field Experience 200% increase in performance i. Tracker + cache discovery Introduced

Suggested i. Tracker Cache Discovery Format A P 4 P i. Tracker query (Get Map) Map • IP range -> POP, “cost” metrics, Good Peers • IP range -> Cache servers + Vendor Specific Data (VSD) App. Tracker i. Tracker 2 1 4 3 Internet ISP Peer ISP/Vendor DB update App. Tracker Additional compilation A. Get Map (i. Tracker query) B. Get vendor specific cache location Get. Servers(IP, hash, VSD, protocol) Vendor Specific plug-ins Vendor A Vendor B

Summary Cache = relives the load on the network + sustains/improves Qo. E + new monetization opportunities, over existing ISP infrastructure i. Trackers 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 P 4 P is not implemented), e. g. Bit. Torrent CDP Cache + i. Tracker + 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

Скачать презентацию P 4 P meeting Eitan Efron VP BD

9df6791326e6499dc6dc77b3446c69c2.ppt

Количество слайдов: 15