1. 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/2013TERENA Networking Conference1

2. 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

3. 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/2013TERENA Networking Conference3

4. ADDONAS solution (1) overall view 05/06/2013TERENA Networking Conference4 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)

5. ADDONAS solution (2) relations between entities Infrastructure Provider Provides physical infrastructure for the Virtual Service Operators 05/06/2013TERENA Networking Conference5 Service Provider Provides services to the user May have arragements with many VSOs 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

6. ADDONAS solution (3) relationships 05/06/2013TERENA Networking Conference6 Each Virtual Service Operator posses its own virtual infrastructure (slice) Each Service Operator or User may interact with many Virtual Service Operators Infrastructure Provider is accounting Virtual Service Operators instead of a number of users

7. User perspective – connecting via VSO 05/06/2013TERENA Networking Conference7

8. User perspective – connecting via SP 05/06/2013TERENA Networking Conference8

9. 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 05/06/2013TERENA Networking Conference9 OpenFlow advantages: Flexibility & granularity: traffic definition per connection Extensible Easy of management Easy slicing of network resources

10. ADDONAS SDN AON reference architecture 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 Virtual Service Operator: Network Operating System (NOS) Application plug-ins (e.g. Service composition, virtualization) Users communicating with Service Providers or Virtual Service Operators VSO manager, coordinated the concurrent operation of VSOs Network resources management and networking polices 05/06/2013TERENA Networking Conference10

11. ADDONAS data plane architecture 05/06/2013TERENA Networking Conference11 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

12. 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/2013TERENA Networking Conference12

13. 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. 05/06/2013TERENA Networking Conference13 Endpoint Service

14. 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 05/06/2013TERENA Networking Conference14 Endpoint P2P / P2MP UNICAST / MULTICAST Flow Policy Service ADDONAS network Endpoint

15. Service data-model 28/05/2013Review Meeting in Poznań15

16. 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. 05/06/2013TERENA Networking Conference16 Endpoint ADDONAS network Service

17. 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/2013TERENA Networking Conference17

18. High-level view on the ADDONAS testbed 05/06/2013TERENA Networking Conference 18 Service Layer Control Layer Service Provider FlowVisor

19. 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/2013TERENA Networking Conference19

20. 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/2013TERENA Networking Conference20

21. 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/2013TERENA Networking Conference21