ITU-T Kaleidoscope 2010 Beyond the Internet? - Innovations for future networks and services

Size: px

Start display at page:

Download "ITU-T Kaleidoscope 2010 Beyond the Internet? - Innovations for future networks and services"

Sharlene Mitchell
8 years ago
Views:

1 ITU-T Kaleidoscope 2010 Beyond the Internet? - Innovations for future networks and services How can an ISP merge with a CDN? Kideok Cho, Hakyung Jung, Munyoung Lee, Diko Ko, Ted Taekyoung Kwon, and Yanghee Choi Seoul National University, Korea kdcho@mmlab.snu.ac.kr Pune, India, December 2010

CDN? Kideok Cho, Hakyung Jung, Munyoung Lee, Diko Ko, Ted Taekyoung Kwon,

2 Outline Background ISP-centric Content Delivery (icode) Architecture Technical & Business Issues Simulation Results Conclusion 2

3 Paradigm Shifting of Internet The networking problem of old days ( 60s- 70s) Now Resource Sharing Expensive resource (card readers, tape drives) sharing More and more traffic on Internet is attributed to contentoriented services (e.g., file download, web access, etc) Problems: duplicated downloads, flash crowd, etc From Where Conversation To What Distribution of protocol classes 08/09 [source: ipoque] 3

attributed to contentoriented services (e.g.

4 Efficient Content Download Solutions P2P System Swarming technique Scalable but unstable Incurs inter-isp traffic Content Delivery Network Stable and efficient Only paid contents are served Sub-optimal ISP performance Q: How can an ISP exploit the in-network storage for the content delivery services? Emerging technical trend Storage cost reduction Can manipulate packets at the routers Network entities can cache the contents [ITU-T SG13, IETF DECADE, DONA, CCN, ] Network Entities with Storage 4

the in-network storage for the content delivery services?

5 ISP-centric Content Delivery (icode) Overview Exploits in-network storage attached to network entities (e.g., routers) for content delivery services Assume that every content is identified by a uniform resource identifier (URI) Main advantages of icode User experience: stable and reduced d latency of content transfer ISP incentives: inter-isp traffic reduction, traffic engineering, and new business model Incremental deployment is possible 5

, routers) for content delivery services Assume that every content is identified by a uniform resource

6 iproxy performs content lookup, content download, d and DNS resolution on behalf of the end host. (functional entity) icode Architecture itracker is operated by an ISP and is responsible for managing contents inside the ISP. itracker URI URI of Location Database Oi Origin i Server End Host iproxy R1 C2 C3 Location -Address of R2 -Address of R3 -Address of Origin Server C3 R2 C2 R4 C2 C-router R3 Contents idns Server icode C3 Origin Server maintains the content published by the content provider. On receiving DNS query from outside an ISP, idns Server contacts t the itrackerk to return the IP address of C-router caching the content. C-router has a storage module to cache the contents. t It performs content t delivery services upon the request from the iproxy. 6

itracker URI URI of Location Database Oi Origin i Server End Host iproxy R1 C2 C3 Location -Address of R2 -Address of R3 -Address of Origin Server C3 R2 C2 R4 C2 C-router R3 Contents idns

7 icode Operation Inside Cache Hit End Host (1) (6) iproxy (2) (1) Content Request to iproxy (URI of ) (4) (3) (2) itracker Lookup (4) (5) Content Chunk icode C2 (5) C-router C3 itracker C2 (3) itracker Response (Addresses of C-routers) (4) Content Request to C-routers (5) Content Deliveries to iproxyo y (Parallel TX) (6) Content Delivery to End Host 7

C-router C3 itracker C2 (3) itracker Response (Addresses of C-routers) (4) Content

8 ISP without icode icode Operation Outside End Host (1) Local DNS Server (1) DNS Resolution (Local DNS) (2) DNS Resolution (Auth. DNS) (8) (2) (3) DNS Response (7) (4) (CNAME) (3) (4) DNS Resolution (idns in icode) (6) (10) (9) (5) itracker Lookup ISP with icode itracker C2 (5) C-router idns Server C3 Authoritative DNS Server C2 C3 Contents Origin Server (6) itracker Response (address of C-router) (7)-(8) (8) DNS Response (address of C-router) (9) Content Request to C-router (10) Content Delivery to End Host 8

icode itracker C2 (5) C-router idns Server C3 Authoritative DNS Server C2 C3 Contents Origin Server (6) itracker Response

9 Customized Content Delivery Services Current load < th Origin Server C2 C3 iproxy itracker R1 R4 C2 R2 Current load th R3 Server-load-aware icode service: the delivery source can be chosen according to the current load of the origin server. icode service is affordable to small-scale content providers. 9

service: the delivery source can be chosen according to the current load of

10 icode Substantiation over Multiple ISPs iproxy itracker R6 R1 Lease slices of C-routers from other ISP R2 icode R3 R4 R5 Virtualized Network : virtualized slices An ISP can deploy the icode independently of other ISPs 10

11 Simulation Results icode incurs the smallest volume of icode and CDN use the links more inter-isp traffic except CDN evenly than P2P and Client-Server icode offers economic incentives to model ISPs by reducing inter-isp traffic 56.7% reduction compared to CDN P2P achieves less inter-isp traffic icode can achieve load balancing not than client-server model only among C-routers but also among the links of the ISP network 11

12 Conclusion ISP-centric Content Delivery (icode) Exploits in-network storage to deliver the contents to end users Services wide spectrum of content providers ISP incentives: inter-isp traffic reduction & traffic engineering Future Work Content caching policy and delivery issues Implementation & experiments over the large scale testbed 12

incentives: inter-isp traffic reduction & traffic engineering Future Work Content

13 Q&A Kideok Cho, Ph.D. Candidate 13

14 BACKUP SLIDES 14

15 Simulation Environments Simulation Environments Simulator Topology Number of routers & end hosts Content distribution Discrete event-driven simulator 1 transit domain and 5 stub domains generated using GT-ITM 105 routers & 1,000 end hosts Randomly distributed 1,000 contents (1GBytes) Request distribution Zipf distribution with parameter 1.0 Cache size icode caching policy 10GBytes Round-robin among C-routers Comparison Client-server, P2P*, CDN** *: Peers within the same ISP network will be selected first **: Assume that ISP can deploy the CDN Server at the best position i in the ISP network in terms of hop count 15

16 icode Operation inside cache miss End Host iproxy (1) (8) (4) (5) (7) (6) (2) (3) Oi Origini Server C2 C3 Contents (1) Content Request to iproxyo y (URI of ) (2) itracker Lookup (3) itracker Response (itracker Miss) idns Server itracker (4)-(5) DNS Resolution (6) Content Request to Origin Server icode (7) Content Delivery to iproxy C-router (8) Content Delivery to End Host 16

itracker Response (itracker Miss) idns Server itracker (4)-(5) DNS Resolution (6) Content

WAVE: Popularity-based and Collaborative In-network Caching for Content-Oriented Networks

WAVE: Popularity-based and Collaborative In-network Caching for Content-Oriented Networks K. D. Cho et al., IEEE INFOCOM 2012 Workshop, pp. 316-321, March 2012. January 17, 2013 Byeong-Gi Kim Park Laboratory,