Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | Korea Communication Market Data | List of Contributors | Become a Contributor |    
 
 
Section 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung   Korean Vendors
 
CHANNELS     HFR    |  Mobile Fronthaul Solution  |  Carrier Ethernet Solution  | Resources        
CHANNELS     ZARAM    |  XGSPON 10G SFP+ ONT  |  Use cases  | Evolution of FTTH Access Network    

 

Google Global Cache (GGC) Operations for YouTube (1): KT Case (Without GGC)
April 16, 2012 | By Chris Yoo (tech@netmanias.com)
Online viewer:
Comments (2)
17

We are going to present you workflow that shows how a YouTube video is downloaded to a subscriber device via Google Global Caches installed in LG U+. Below, we will look at downloading over the KT Internet, which has no Google Global Cache installed in it.

 

In the subsequent post, downloading procedures in the LG U+ Internet, which has Google Global Caches installed in it, will be discussed using two different cases - on a Cache Hit and on a Cache Miss (i.e. when a Google Global Cache has a video requested and when it does not). 

 

YouTube Downloads over the KT Network

 

We assumed a network configured as follows for the purposes of this post:

  • On the grey board in the left [Google Server (USA)]: YouTube server (www.youtube.com) and Google Global Cache (o-o.preferred.lax04t01.v1.lscache6.c.youtube.com) located in US
  • On the grey board in the right [KT Network (Korea)]: A KT subscriber connected to KT network in Korea
  • On the grey board in the middle [Transit]: Transit network that connects KT network to a network in US

 

 

  1. The KT subscriber enters www.youtube.com into his browser to access a YouTube server. The subscriber device sends a DNS query to a KT DNS server (the DNS server doesn't have to be a KT DNS server) to obtain the IP address of the YouTube server.
  2. The KT DNS server gives the subscriber device the IP address of the YouTube server (i.e. 74.125.71.136).
  3. The subscriber accesses the YouTube server and clicks "Avatar" on YouTube.
  4. The subscriber device sends a HTTP GET message to the YouTube server to request an Avatar video.
  5. This is the most important step of the process. The YouTube server checks the IP address of the subscriber device when it receives the HTTP GET message. This step is to check whether or not the IP address of a device is within the range assigned to an operator who has Google Global Caches installed in its network. In this example, KT has no Google Global Cache in its network.
  6. Therefore, the YouTube server gives the hostname of a Google Global Cache located in US (i.e. o-o.preferred.lax04t01.v1.lscache6.c.youtube.com) to the subscriber device.
  7. The subscriber device performs a DNS query about hostname = o-o.preferred.lax04t01.v1.lscache6.c.youtube.com.
  8. As a result of the query, the subscriber device receives an IP address of 74.125.215.176, which is the IP address of the Google Global Cache located in US.
  9. Now, the subscriber device sends a request for the video to the server at 74.125.215.176.
  10. The subscriber downloads the video from the Google Global Cache (presumably located in LA since the hostname has "lax"). The RTT between two countries is very high - about 200 ms. Besides, if there is heavy traffic (e.g. in the evening), buffering will be severe. Severe enough to keep the subscriber from watching the video.

 

Nidhi 2015-03-18 19:45:57

how to connectl GGC servers to its own Network and what is the implementaion procedure means which N/W elements is reuired? how give the coonectivity for switch to router?

Chris Yoo 2015-03-19 10:15:34

Hi Nidhi,

I hope help you with the following document: 

https://www.netmanias.com/ko/?m=view&id=cshare&no=5455

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
View All (819)
4.5G (1) 5G (88) AI (6) AR (1) ARP (3) AT&T (1) Akamai (1) Authentication (5) Big Data (2) Blockchain (3) C-RAN/Fronthaul (17) CDN (4) CPRI (4) Carrier Ethernet (3) China (1) China Mobile (2) Cisco (1) Cloud (5) CoMP (6) Connected Car (4) DHCP (5) Edge Computing (1) Ericsson (2) FTTH (6) GSLB (1) GiGAtopia (2) Gigabit Internet (19) Google (7) Google Global Cache (3) HLS (5) HSDPA (2) HTTP Adaptive Streaming (5) Handover (1) Huawei (1) IEEE 802.1 (1) IP Routing (7) IPTV (21) IoST (3) IoT (55) KT (42) Korea (19) Korea ICT Market (1) Korea ICT Service (13) Korea ICT Vendor (1) LG U+ (18) LSC (1) LTE (78) LTE-A (16) LTE-B (1) LTE-H (2) LTE-M (3) LTE-U (4) LoRa (7) MEC (3) MPLS (2) MPTCP (3) MWC 2015 (8) NB-IoT (6) Netflix (2) Network Protocol (21) Network Slicing (4) New Radio (9) Nokia (1) OSPF (2) OTT (3) PCRF (1) Platform (2) QoS (3) RCS (4) Roaming (1) SD-WAN (17) SDN/NFV (71) SIM (1) SK Broadband (2) SK Telecom (34) Samsung (5) Security (16) Self-Driving (1) Small Cell (2) Spectrum Sharing (2) Switching (6) TAU (2) UHD (5) VR (2) Video Streaming (12) VoLTE (8) VoWiFi (2) Wi-Fi (31) YouTube (6) blockchain (1) eICIC (1) eMBMS (1) iBeacon (1) security (1) telecoin (1) uCPE (2)
Password confirmation
Please enter your registered comment password.
Password