Service - TNC2013

Download Report

Transcript Service - TNC2013

Active Distributed & Dynamic Optical Network Access Systems
Next Generation Access Network
Łukasz Podleski (PSNC)
Work in the ADDONAS project is financially supported by Narodowe Centrum Badan i Rozwoju (PL), The Technology Strategy
Board (UK) and Bundesministerium für Bildung und Forschung (DE) under the FP7 PIANO+ initiative
05/06/2013
TERENA Networking Conference
1
Problems in today’s
access/metro networks
• Current architectures do not naturally support multiple
operators in seamless delivery of their services to end-users
• Fair share of the resources among multiple operators is difficult
• End-users are increasingly
becoming content providers
– requires symmetric links
in the access network
• No quality guarantees for services
• No flexibility in changing network
operators by end-user
• No possibility of dynamic
service setup
Functional requirements
• Access network as an active and distributed system
– switching and grooming of service flows added
– services equally accessible from any end-point in the network
• Virtualization of network resources
• Dynamic bandwidth allocation
• Symmetric user-to-network links
– users uploading and downloading services equally well
• Guaranteed quality of experience for end user
• Multiple services of any type coexisting on the same
infrastructure
05/06/2013
TERENA Networking Conference
3
ADDONAS solution (1)
overall view
Nowadays solution:
Infrastructure Providers are
offering access to the services
(mostly triple-play model: VoIP,
Internet & IPTV) to the group of
directly connected users
ADDONAS solution:
Infrastructure Provider is offering the
physical infrastructure, using which
Virtual Service Operators are
providing access to the services
offered by the Service Providers
(multi-play model)
05/06/2013
TERENA Networking Conference
4
ADDONAS solution (2)
relations between entities
Virtual Service Operator
• Obtains slice of the physical infrastructure from the Infrastructure Provider
• Has arragements with the Service Providers and Users
• Provides access for users to the services
Service Provider
• Provides services to the user
• May have arragements with many
VSOs
Infrastructure Provider
•
Provides physical infrastructure for the Virtual Service Operators
05/06/2013
TERENA Networking Conference
5
ADDONAS solution (3)
relationships
Each Service Operator or User may
interact with many Virtual Service
Operators
Each Virtual Service Operator posses
its own virtual infrastructure (slice)
Infrastructure Provider is accounting
Virtual Service Operators instead of a
number of users
05/06/2013
TERENA Networking Conference
6
User perspective –
connecting via VSO
ADDONAS
User
05/06/2013
TERENA Networking Conference
7
User perspective –
connecting via SP
ADDONAS
User
INTERNET
05/06/2013
TERENA Networking Conference
8
Motivation behind using SDN
Software Defined Networking approach enables:
• fast and dynamic (re)configuration of the network end-to-end
connections
• ease of management - done from a central point (SDN controller)
• network customization - each VSO can independently create its own
network configuration
OpenFlow advantages:
Flexibility & granularity: traffic definition per connection
Extensible
Easy of management
Easy slicing of network resources
05/06/2013
TERENA Networking Conference
9
Users communicating with
Service Providers or
Virtual Service Operators
VSO
VSO
SP
EXT-ASL.U
EXT-ASL.SP
Service Layer
Slice Controller (VSO)
Slice Management
User
Management
Control Layer
Virtual Service Operator:
• Network Operating
System (NOS)
• Application plug-ins
(e.g. Service
composition,
virtualization)
Application Layer
ADDONAS SDN AON
reference architecture
SPs
Management
AAA
Network Operating System (NOS)
Service
Assessment
Slice (VSO)
Supervisor
Control Management
AAA
Monitoring
Network & IT
Resources DB
Virtualized
Resources DB
Virtualization
Service
Composition
•
•
05/06/2013
Hardware
Virtualization
Layer
Active optical access for
symmetric end-user services
and new business models
Distributed 3-stage OPST
solution for metro Ethernet
transport
Distributed datacentres
enabling ultra fast services
VSO Manager
EXT-CL.SS
EXT-CL.HVL
•
EXT-SS.HVL
EXT-SS.DCM
FlowVisor
Forwarding Management
Translation
Monitoring
VSO manager,
coordinated the
concurrent
operation of VSOs
SlicePolicy
Policy
Slice
Slice
Policy
Network
Resources DB
Resources
Allocation
EXT-HVL.N
Data Center
management
Network resources
management and
networking polices
EXT-DCM.DC
Physical Infrastructure
User
Devices
Access Network
Metro Network
TERENA Networking Conference
Data Centers
10
ADDONAS data plane
architecture
Keymile provides access switch –
Milegate node, which is providing
symmetric 1Gbps link to the users
Intune provides OPST distributed 3-stage
switch, which interconnects endpoints in
the full-mesh topology
• ADDONAS architecture connects users to the metro network using Keymile’s Milegate nodes
• Metro core network is created using Intune’s distributed 3-stage switch
05/06/2013
TERENA Networking Conference
11
Main entities
of the Control-Layer architecture
• Endpoint
– Physical or virtual machine present in the
architecture (IP termination point)
• Service
– Definition of the traffic, that will be sent over the
network from the Service Provider’s endpoint
• Virtual 2 Network
– Dedicated path (flow) connecting user’s
endpoint to the service
05/06/2013
TERENA Networking Conference
12
Endpoints
in the Control-Layer architecture
• Endpoints are physical (like user’s access devices, physical
servers) or virtual (user’s or service provider’s virtual
machines) entities present in the architecture.
• Each endpoint registered in the Control-Layer can provide
service(s) in the ADDONAS solution
• Each endpoint registered in the Control-Layer can obtain
access to the service by setup of a dedicated virtual network.
Service
Service
Service
Service
Service
Service
Endpoint
05/06/2013
Endpoint
TERENA Networking Conference
13
Services
in the Control-Layer architecture
• Service defines traffic requirements for data transported
using the virtual network
• Use of OpenFlow enables traffic definition for a service with
fine granularity (from pure L2 to L4), which allows to better
network resources utilization and control than in nowadays
L2/L3 solutions.
• Each service has reserved bandwidth for its own purposes
(virtual networks to the customers) on the server endpoint –
service provider has full control over throughput resources
P2P / P2MP
ADDONAS
UNICAST
/ MULTICAST
network
Endpoint
05/06/2013
Flow
Policy
Flow
Policy
Flow
Policy
Flow
Policy
TERENA Networking Conference
Service
Endpoint
14
Service data-model
«struct»
Service Traffic Definition
+servicelinkdefinition[1..*] : Service Link Definition
«struct»Flow Policy
+relativeFlowPriority[1] : short(idl)
+dl_dst[1] : boolean(idl)
+dl_src[1] : boolean(idl)
+dl_type_val[1] : unsigned short(idl)
+dl_vlan[1] : boolean(idl)
+dl_vpcp[1] : boolean(idl)
+dl_vpcp_val[1] : unsigned short(idl)
+nw_dst[1] : boolean(idl)
+nw_src[1] : boolean(idl)
+nw_tos[1] : boolean(idl)
+nw_tos_val[1] : short(idl)
+nw_proto[1] : boolean(idl)
+nw_proto_val[1] : short(idl)
+tp_dst[1] : boolean(idl)
+tp_dst_val[1] : short(idl)
+tp_src[1] : boolean(idl)
+tp_src_val[1] : short(idl)
28/05/2013
«struct»
Service Link Definition
+linktype[1] : Link Type
+nettype[1] : Network Type
+traffictype[1] : Traffic Type
+flowpolicy[1..*] : Flow Policy
«enumeration»
Link Type
+"UPSTREAM"
+"DOWNSTREAM"
«enumeration»
Network Type
+"P2P"
+"P2MP"
+"MP2MP"
«enumeration»
Traffic Type
+"UNICAST"
+"MULTICAST"
Review Meeting in Poznań
15
Virtual Networks
in the Control-Layer architecture
• Virtual Network represents a dedicated path (with
guaranteed QoE) from the customers endpoint to the service
provider’s server
• Virtual Network’s path is created using traffic definition of the
service and requested bandwidth.
• Each endpoint can have established many virtual networks at
the same time.
ADDONAS
network
Endpoint
05/06/2013
Service
Service
Service
Endpoint
TERENA Networking Conference
16
Progress of work
• First prototypes of the Control Layer and OF
Agent’s (support for non-OpenFlow devices)
are ready and tested
• First prototype of the Service Layer is ready
• Work on the Slice Supervisor and slice
resources management is in progress
05/06/2013
TERENA Networking Conference
17
High-level view on the
ADDONAS testbed
Service
Service
Service
Provider
Provider
Provider
Service Layer
Control Layer
FlowVisor
18
05/06/2013
TERENA Networking Conference
Improvements to access and metro
networks
• ADDONAS architecture supports multiple operators in
seamless delivery of their services to end-users
• End-users can act as content providers
• Quality guarantees for delivered services
• Flexibility in changing network operators by end-user
• Dynamic service setup
05/06/2013
TERENA Networking Conference
19
Project information
• Start date: 15 October 2011
• Duration: 24 months
• Total Person Months: 292
• Consortium:
Poznan Supercomputing and Networking Center (Project coordinator)
Intune Networks Belfast
University of Bristol
Compound Semiconductor Technologies Global
Keymile
• Web page: www.addonas.eu
05/06/2013
TERENA Networking Conference
20
Thank you for your attention
After the presentation:
short demo at the PIONIER / PSNC booth (no 14)
Work in the ADDONAS project is financially supported by Narodowe Centrum Badan i Rozwoju (PL), The Technology Strategy
Board (UK) and Bundesministerium für Bildung und Forschung (DE) under the FP7 PIANO+ initiative
05/06/2013
TERENA Networking Conference
21