An updated presentation (v1.2) about what is the concept and the idea behind Network Function Virtualisation (NFV) for Tampere University of Technology Service oriented architectures course. Includes introduction to NFV and VNF (Virtualised Network Function) architecture, components and interfaces.
7. Geographically distributed dedicated hardware
devices
router
router
router
router
firewall
firewall
firewall
server
server
server
server
server
server
access
gateway
router router
router
router router
firewall firewall
DHCP
DNS
11. The brave new world of
Network Function Virtualisation
NFV
12. Instead of this …
router
router
router
router
firewall
firewall
firewall
server
server
server
server
server
server
access
gateway
router router
router
router router
firewall firewall
DHCP
DNS
14. Virtualised Network
Functions / devices
● Virtualised network functions run on virtual
hosts on top of the virtualisation
infrastructure in data centers or PoPs
● Virtual infrastructure can extend across PoPs
17. Capacity is general-
purpose capacity
●
●
●
Broadband Customer and Mobile Network PoPs prepare for
prime time in streaming by repurposing capacity to streaming
caches and regional routing and access capacity.
Enterprise customer
fights DDoS with
additional firewall
capacity
Operator prepares for peak
in SMS/MMS messages
Content Service
Provider adds
more capacity
and caching for
prime time
Prime time traffic
requires more firewall
capacity
19. This is called Network Function Virtualisation
Infrastructure (NFVI)…
20. Each of the small boxes can be
a Virtualised Network Function (VNF) …
21. Each of the VNFs can consist of multiple
components (VNFC) …
Load
balancer
Load
balancer
Packet
Filter
Packet
Filter
Packet
Filter
Packet
Filter
Stateful
Firewall
Stateful
Firewall
Stateful
Firewall
Stateful
Firewall
Policy
and Rule
Database
Policy
and Rule
Database
VNFC VNFC
VNFCVNFC
● Each Virtualised Network
Function Component (VNFC)
may consist of several virtual
hosts, which automatically
scale up and down when
needed.
● VNFs and VNFCs can both
provide e.g. REST or netconf
interfaces for management,
monitoring and integration
purposes.
22. Idea is that VNFCs and VNFs can be re-used…
● … as building blocks of
new VNFs and services.
● They are supposed to
have web services like
REST APIs => web
developers are supposed
to be able to build
operator customer
self-service portals
● Standardised interfaces
should mean better
vendor interoperability
=> avoiding vendor
lock-ins