Active ISP Involvement
in Content-Centric Future Internet
2013.01.23
Eugene Kim
4th IFIP International Conference
on New Technologies, Mobility and Security, NTMS 2011
Contents
1. Introduction
2. Background
3. Future Internet Architecture
4. A Surrogate Architecture
5. Benefit to Providers
6. Comparison with CDN
7. Conclusion
Introduction
•
Changes to the internet infrastructure of the internet
1) Cooperation of many ISP
2) Partnership with the CP
The paper focuses on the enhanced
1) benefits for ISP
2) Their increased role in supporting a content-centric future Internet
architecture
Introduction
The reluctance of ISPs to be
involved in a next-generation
Internet model has been
considered as one of major
hindrances in the evolution of
the Internet
overlay architecture, which can be deployed incrementally and supports a
business model that provides a
“win win”
situation for both network service
provider (i.e. the ISPs) and CP.
Solution
=
Overlay architectur
e
the evolution of the
Internet
Introduction
•
Surrogate
–
a network–edge device, located close to the user, which acts
as a relay for the user to access, organize, provision and
monitor Internet content.
–
integrate into content delivery networks as well as other
overlays and serve as a basis for implementing a content–
centric Internet architecture.
Background – Structure of Internet
•
Core network : acts as a backbone and its routers support multiple
telecommunications interfaces to switch and forward packets at the
highest speed.
•
Edge networks : are connected to one or multiple core routers and are in
close proximity to the end users, assuring aggregation and distribution of
their traffic.
Background – Content Delivery
•
CDNs are the Web and designed to reduce the
overhead of the content server by bringing the
content to the network edge, closer to the user, similar
to a cache memory on a computer.
•
Content is pushed to the edge and is delivered as fast
as possible through appropriate replication and
caching technologies.
Background – Content Centric Networks
•
CCN (Content Centric Networks)
–
any network that considers content as a central and
paramount entity
–
recently the notion of named content that decouples a
content’s location from its identity, security and access, has
been introduced.
–
retrieves a content by parsing its name
•
The emergence of a CCN, evolution of the CDN into a
rational infrastructure which can support a variety of
content from multiple origins in a flexible and scalable
way raises a number of for its key players.
Background – ISP involvement
•
The role of ISPs is limited to that of a data carrier,
through fast packet delivery(at the core) and access
provisioning (at the edge).
Background
•
Limits of CDN model
– limit to consider is the potential for growth in the infrastructure of CDN operators, as the content model changes.
– Increasing the size of the deployed infrastructure in the ISP domain is too costly, redundant to a large degree, and not scalable.
•
Value for ISPs
– it would be better to have servers close to the users, it would also be
better to have application servers close to suppliers of content.
•
User-side issues
– As the Internet becomes more
content–oriented, other issues such as restriction to access, security and performance guarantees arise
Future Internet Architecture
• The surrogate implements support for a number of content–specific services including content search, request, create or add.
• Surrogates and content repositories create an overlay of a logical content–centric Internet architecture.
• End users are logically directly connected to this overlay through virtual clients.
• Inside this virtual cloud, surrogates operate as forwarding nodes while repositories act as storages.
A Surrogate Architecture
• Web server, which receives the users’ input through a GUI running on the Web client inside the UE.
– Web–based GUIs are used to implement the virtual client side since most user platforms (UE) come equipped with a Web browser
• Application servers with the help of the index engine and local cache gather content and transform this content into the service the user requests.
– The surrogate through the application servers
allow the content/service providers to deploy their services.
• Index engine accomplishes server selection and traffic engineering through access of the ISP’s topology and overall overlay network condition, although the precise means to accomplish.
A three layer content delivery system
•
No specific CDN provider owns nor implements the CDN resources
– ISP is responsible for the surrogates and the repositories implemented in its AS
•
1 layer (InP)
– InP(i.e. the ISP) is responsible for implementing and maintaining the
physical resources (e.g. routers, switches, surrogates, repositories, physical links, etc.) inside the AS (Autonomous System) it operates.
•
2 layer (Virtual Network Provider)
– The VNP gathers resources from one or more ISPs and builds a virtual network, which is composed of virtual nodes and links
•
3 layer (CP)
Benefit to Providers
•
Server selection and traffic engineering
– For example in case of Akamai, the optimal server selection is substantially degraded for end users outside of the USA.
•
coupled and affect one another’s performance Local content access
– CP needs not have to deal with a CDN provider with a global presence toreplicate its content around the world.
– Instead of that the regional ISPs could provide superior local network
coverage and deliver flawless high quality media content throughout its AS.
•
Enhanced security and billing
– End user is always authenticated by the ISP to grant access to the network. – This authentication can be further extended through a Single Sign-On (SSO)
technique to access restricted content.
– The ISPs could also control the delivery of copyrighted content to an illegitimate user.
– The ISPs are also capable of implementing fine–grained billing for the usage of commercial content and could supply the billing information to the CPs.
Comparison with CDN
Criteria
CDN (Akamai)
Proposed model
At th edge Redirection, caches and local
storages. Implements computing (application server) and storages at the edge. Virtual client No notion of client virtualization. Virtualize user’s client through computing
support at the Edge Cloud.
Deliver Content only Service and content
InP’s role InPs are not involved. CDN provider
maintains the CDN. Active involvement of the InPs who maintains the Edge Cloud infrastructures Business model CDN and CPs are in the
value chain. InP, VNP (in case of content overlay) and CP/SP are in the value chain. Potential
providers Need major investment, suitable for industry giants. Need small investment, good for even medium/small companies.
