TELE9752 GROUP PRESENTATION
THE FLUID INTERNET:
SERVICE-CENTRIC MANAGEMENT OF A
VIRTUALIZED FUTURE INTERNET
Group member: Kai Hu
Weili Yin
Xingyu Wu
Yinhao Nie
Xiaoxue Liu
Date:2015/10/21
1
1
OUTLINE







2
Introduction
Background
The internet (r)evolution
The fluid internet
Service delivery in the fluid internet
The challenges of the fluid internet
Conclusion
2
BACKGROUND
1.The internet purpose has changed.
 2. The traditional structure of the Internet has
been unable to meet the new demand
 3.How to solve this issue?

3
3
THE INTERNET (R)EVOLUTION

1. The trend of changing
Increased immersion
and new levels of
interactivity
Infrastructurerelated trends
Internet of Things
Network
virtualization
4
4
THE INTERNET (R)EVOLUTION

2. Three main management challenges.
2.1 The current provision and management is inflexible
2.2 The current quality requirements are versatile and fluctuating.
2.3 Internet management should focus on the mobility support problems.
5
5
THE INTERNET (R)EVOLUTION

3. How to solve these challenges?
Fluid Internet paradigm
3.1 treats services as the first consideration.
3.2 can benefit the elastic provision of virtualized end-to-end service
delivery infrastructures.
6
Current Internet paradigm
Fluid Internet paradigm
leasing of a set of virtual machines,
without any guarantees concerning
their connectivity
Able to lease full-fledged virtual data
center networks
data center virtualization is limited to a
single data center network domain
Facilitates end-to-end virtual service
delivery networks, combining multiple
physical networks
low-level network and computing
requirements
high-level service and user
requirements
6
THE FLUID INTERNET
What technologies constitutes a fluid network management principles?
1.Cloud computing
7
Fluid Internet
2.Service-centric
networking
3.Network
virtualization
Pure networking
capabilities
Current network
virtualization
Pure networking
capabilities
Extension
FURTHER
Informationcentric
networking
Elastic allocation of
resources as well as
high-level capabilities
in both the cloud and the
network
7
From The perspective of current network structure to achieve leasing additional
computational and storage capabilities
THE FLUID INTERNET
8
deliver the service
given the requested quality
guarantees
Different applications
How to achieve leasing
action
Current network structure
8
THE FLUID INTERNET
Three main advantages of the Fluid Internet:
1.
Delegation of management responsibilities.
2.
End-to-end manageability
3.
Dynamic management
9
9
SERVICE DELIVERY IN THE
FLUID INTERNET
More details of the interactions
10

Step 1
Dimensioning
Planning
Provisioning

Step 2
Elastic management
10
STEP 1 DIMENSIONING ,PLANNING
& PROVISIONING


11
the VSIP should calculate the optimal mapping of all SP VSIs to its own VSIs.
But Embedding the newly requested VSI configuration may FAIL due to
① a lack of available resources
② VSIP does not operate a VSI that can satisfy the requested service
guarantees.
11
Several actions performed to deal with such failure








12
Based on the changed resource capacities or service requirements, the
VSIP will adjust one or more of its own VSIs
VSIP performs a horizontal VNE step.
Partitioning the end-to-end VSIs in multiple intra-domain VSI components.
The VSIP maps all intra-domain VSI parts of all its VSIs onto compatible
physical infrastructures.
the VSIP sends requests to the relevant IPs
Adjusting its leased capabilities in line with the results of the horizontal
VNE step.
Each IP solves the vertical VNE problem for all intra-domain VSI
components that are provisioned on its infrastructure.
(mapping virtual capabilities onto concrete physical resources.)
the lease contracts back to the VSIP and SP
Delivering services to its users under the pre-requested service
guarantees.
12
STEP 2 ELASTIC MANAGEMENT
13

The SP is expected to reserve spare capacity in its VSIs to
be able to cope with minor fluctuations in user behavior and
demand

However, providing too much spare capacity would result in
inefficient resource utilization and unnecessarily high costs.
13


14
The SP detects a modified access pattern and decides that
more capabilities are needed to continue supporting the
service adequately. Then the SP forwards the modified
service requirements to the relevant VSIP
VSIP translates them into a modified VSI configuration.
14

Then VSIP is expected to provide some spare capacity in
anticipation of minor service requirement fluctuations.

If the spare capacity is insufficient, or if the modified
requirements cannot be supported by the VSIP’s current set
of VSIs, several other actions need to be taken.

the VSIP performs the horizontal scaling step.
Similar to the horizontal VNE step it performs when provisioning new
services, but these changes in requirements are required to be much
faster than provisioning new services.
(requires fast heuristics that iteratively adapt existing solutions)

the VSIP releases, scales, and/or leases capabilities from different IPs
Based on the modified VSIs resulting from the horizontal scaling step
IPs perform vertical scaling operations.
Similarly, it is a faster online version of the vertical VNE step.

15
15
THE CHALLENGES OF THE FLUID
INTERNET
① REQUIREMENT
TRANSLATION
② SERVICE-CENTRIC
NETWORK
EMBEDDING
③ ELASTIC
MANAGEMENT
④ SERVICE
ADDRESSING AND
PROTOCOL
SIGNALLING
⑤ Security
Although it has huge advantages comparing to traditional network, fluid internet
is still facing challenges in many areas, especially the scientific problems. The
figure above shows five important open issues.
16
16
① REQUIREMENT TRANSLATION

VSIP translates the received end-to-end service
requirements into a VSI configuration. As the first step of
the whole interaction, it is extremely crucial to ensure that
this configuration to be constructed.

Therefore, the algorithms of the translation should be able
to:



17
Translate a wide range of QoS requirements into a set of virtual
capabilities
Connect those capabilities in an end-to-end VSI, and incorporate the
dependencies
Provide suitable solutions that do not interfere the network embedding
process
which makes such algorithms hard to design
17

Current advances
The requirement translation is related to automated
software requirements refinement (semi-automated now)
Fluid Internet-based requirement translation has potential
to achieve fully automated algorithms rather than current
semi-automated tools for two reasons:


18
The translation is less complicated than pure policy refinement
Increasing attention on the design of network programming languages
could be helpful to prove the feasibility and accuracy of a requirement
translation
18
② SERVICE-CENTRIC NETWORK
EMBEDDING


Do not scale well to a huge network (Internet)
Could hardly work in complicated virtual networks

We need distributed network embedding algorithms to:




19
Current network embedding algorithms focus mainly on solving
the problem in a centralized way
scale to immense amounts of VSIs.
support for inter-provider VSIs
Transcend traditional embedding algorithms
19
③ ELASTIC MANAGEMENT

There is a need for an integrated approach that keeps balance
between computationally intensive optimal algorithms with fast
responding to requirements.

Nowsdays, virtual network embedding algorithms focus mostly
on static embedding and do not combine distributed and
dynamic embedding.

Therefore, we need a dynamic algorithm that be able to
adapting VSI based on changes in requirements.
( Similar to cloud management approaches)
20
20
④ SERVICE ADDRESSING AND
PROTOCOL SIGNALLING

The Fluid Internet paradigm reuse ICN concepts, associated
with ICN-related challenges.

Communication protocols between the stakeholders are
needed

21
Should be extended to support configuration of service-centric concepts
21
⑤ SECURITY
22

Remote parties are given access to the management of local
network, which leads to security issues

Fluid Internet should target a distributed security model,
Combining both cloud-originated with network-originated
security concerns.
22
CONCLUSION
23

Three technologies

Three advantages

Five challenges
23
THANK YOU
24
24