Developing Content Caching of IP Traffic for 3G, 4G and NGN

Md. Abdul Hadi

Telecommunication Sector

Bangladesh

Developing Content Caching of IP Traffic for 3G, 4G and NGN

Introductions: Multimedia contents are increasing tremendously from an ever growing number of

smartphones and tablet users The capacity of the MW links, Radio network, Backhaul and Core Network cannot practically

cope with the explosively growing mobile traffic due to the centralized nature of mobilenetwork architectures

An important portion of mobile multimedia traffic is duplicating downloads due to customernatures

Way Forwards of Duplicate Contents Transmissions:

By adopting intelligent caching strategies inside the mobile networks Enabling mobile users to access popular content from caches of nearby MNO gateways (e.g.,

using Selective IP Traffic Offload (SIPTO) techniques Reducing traffic load via intelligent caching of popular content would enhance the energy

efficiency of 4G networks contributing to the evolution of green 5G networks effectively.

Business Gain in terms of Technology and users QoE: Both Core caching and RAN caching can significantly reduce user-perceived latency as well as

the transmission of redundant traffic over the network and reduce Transmission cost as well. Caching in 3G and 4G LTE networks have both been proven to be able to reduce mobile traffic

by one third to two thirds. Reducing traffic load via intelligent caching of popular content would enhance the energy

efficiency of 3G & 4G networks contributing to the evolution of green 5G networks effectively. Caching at the edge of the network has the effect of smoothening traffic spikes and balancing

the backhaul traffic over a long period of time.

Mobile network architectures with / without caching:

Typical and generalized mobile network architectures Mobile network incorporating caching at different layers

Where to Cache: At the Packet Core Network At The 3G RAN (RNC) At the eNB 4G RAN At Aggregation location inside Network

What to Cache: Video Streaming Images and WEB Social Media content

Where, What and How to Cache

New Revenue Streams: Tiered Service Level Agreement Fair Usage Bandwidth Allocation Real Time Service upgrade

Higher Network Efficiency that cope new revenue streams:

Intelligent Traffic Offloading

EDGE Caching Adaptive Traffic Shaping (RAN-Aware)

Revenue v Traffic Growth:

Subscribers expect more service with less cost Operators must optimize network with lower

cost per bit Revenue gap might be partially minimized

through adopting Technological evolutions i.e.features addition without adding newHardware, planning convergence in eachDomain during accruing new Products /Technology

Internet Off-Loading Techniques

Internet Offload Gateway / EDGE Cache Network Architecture :

Minimize Traffic to CoreNetwork

Reduce Core Network OpEx /CapEx

Reduce CapEx / OpEx forBackbone Transmission,IP/MPLS

Savings References : Different Mobile Market

IEEE Communication Magazine February 2014

Traffic Offloading Functions (TOF)

Title Name: Traffic Offload Method, Traffic Offload Function Entity and Traffic Offload System

Changing Landscapes in Mobile Telecommunication

Telcos, Carriers, MSOs and ISPs need for building CDN and Transparent Services inside theNetwork to achieve below changing Landscapes:

TV is no more ‘the entertainment gatekeeper’: Customer wants connected experience (seamless

between – device, network, content.

Real-time entertainment is getting big to bigger: Most of mobile phone owners watch video at

least once a week on their phone.

Tablet users like long-form content: Many People who watch video on tablets, are viewing full-

length TV episodes or full-length movies.

Customer Experience is the critical pillar of differentiation: Customer experience in terms of

network availability and service quality are powerful branding of any Operator which accelerating

new acquisition and customer attachment in the network. Moreover Operator changing rate for a

customer is very less for MNP enabled countries if Operator can meet customer QoE.

The lines are blurring between the roles of over-the-top (OTT) providers, network owners and

device manufacturers.

Content Caching History and Focus on Transparent Caching

History of Content Caching Technology for Network Optimization:

It has been available for many years and today.

Originally for basic web caching: Web pages, HTML files, Web Objects.

Objectives: Application acceleration and scaling.

Service Specific Caching, like as Google cache.

Business Model: Content Delivery Network (CDN) make their money from content publishers

who typically pay based on volume.

Focus on Transparent Caching (TC): It scores high in network Operational savings andenhancing perceived QoE because of-

Optimizes Bandwidth, store & deliver popular OTT web content in caches positioned locally

within a service Network.

Brings in better QoE altogether, specially for popular contents.

TCs do not manipulate content protocols or file types or do not disrupt business logic for the

owners of cached content

Brings in new revenue opportunities for OTT content monetization which ensure guaranteed

QoE.

Future Services, Optimization building block and Solution Segmentation

Types of Traffic Management & Caching Systems: Proprietary based caching i.e. Google, Akamai which provide only HTTPS based Traffic

Management. Transparent Caching, supports HTTP/HTTPS: PeerApp, Oversi, Bluecoat, BTI, Dialogic, Juniper,

Verivue, Huawei Internal CDN and Transparent Caching: Cisco, Juniper, Edgeware, Verivue, Huawei, ZTE,

Alcatel Lucent, Azuki, Skytide

Transparent Caching Features

History of Content Caching Technology for Network Optimization:

It has been available for many years and today.

Originally for basic web caching: Web pages, HTML files, Web Objects.

Objectives: Application acceleration and scaling.

Service Specific Caching, like as Google cache.

Business Model: Content Delivery Network (CDN) make their money from content publishers

who typically pay based on volume.

Focus on Transparent Caching (TC): It scores high in network Operational savings andenhancing perceived QoE because of-

Optimizes Bandwidth, store & deliver popular OTT web content in caches positioned locally

within a service Network.

Brings in better QoE altogether, specially for popular contents.

TCs do not manipulate content protocols or file types or do not disrupt business logic for the

owners of cached content

Brings in new revenue opportunities for OTT content monetization which ensure guaranteed

QoE.

Transparent Caching Features (Cont.)S

MA

RT

Should Cache: Most-viewed/viral, Potential viral, in multi-codec, multi-size, multi-device prof Should keep unique copy of content for different URL Should do "prefix caching" - where initial portions of videos are cached to reduce playback

latencies Should do "Segmented Caching" - with the basic minimum implementation of "popularity-based

segmented caching" , caching of entire videos is dynamically managed based on popularity predictions.

Should do "Caching with network DVR like seek functionality“ Must support multiple protocols and content types : HTTP videos, HTTP-based file sharing,

Adobe, QuickTime, Silverlight, real-time messaging protocol (RTMP) and real-time streaming protocol (RTSP)

Tran

spar

ent

Should not impact any application or service logic, meaning critical functions like authorization and click-through implementations are preserved so as not to impact OTT/content business models.

Should not serve stale content or content that has been removed from the internet.

BU

SIN

ES

S P

RO

CE

SS

Rules should be controlled within the jurisdiction of its network Operations by allowing SPs to determine the speed at which content should be accelerated while being mindful of congesting downstream elements in the network.

Should allow SPs to manage - "white-listing / black-listing" of URL (Content source, request source / subscriber) and specific content or content genre / category

Should allow SPs to define : "house keeping rules"--- For cache time to expire--- Content cache hit v content cache level--- Clean-up / purging rules

Should allows SPs to configure : content sync rules between master & cache content serving nodes; manage ACCP (Access Control for Content Copy)

Transparent Caching Features (Cont.)

AR

CH

ITE

CT

UR

E

Should support "distributed and hierarchical - Architecture" for Broadband and

"distributed - architecture" for wireless / IP-Core.

Should support "transparent in-band architecture" where the session between the

subscriber and origin would preserved, but requested objects are cached or served

from cache based on analysis performed by the cache system

Traffic for "transparent in-band cache systems" would be redirected using

--- Policy based routing (PBR)

--- Deep packet inspection solution

--- Web cache communication protocol (WCCP)

--- Application load balancing equipment

Should support "transparent in-band architecture" Border Gateway Protocol (BGP) or

static Routing, is would direct request traffic to a cache manager, where request is

analyzed and based on an algorithmic decision, a specific content request is directed

to a cache server that has object in storage to serve the object. In the event that the

requested content is not available, the cache manager would tell a cache server to

retrieve the content from the internet for the next user. Cache manager (Master) would

be centrally located.

Transparent Caching Features (Cont.)

Qo

E

Should have QoE agent, continuously monitoring and measuring following and

accordingly system should optimize itself automatically:

-- Perceptual Quality of content available in cache.

-- Quality measurement of content received from source v cached v stream

downloads.

-- Quality measurement of content served directly from source to end-device,

passing through cache manager.

STA

TS

& O

AM

System Should log every metadata of request, response into database and CDR

System should allow data-query interface & API for "Business intelligence and

analytics”

System should provide some real-time information on via dynamic UI (Browser based)

--- Cache gain details (The ratio between Cache output and Cache input). A

higher Cache gain indicates higher Cache efficiency

--- Cache hit ratio

System should allow - Network Management & OAM stuff, along with SNMP support