1. http://www.ist-mupbed.org/ Multi-Partner European Test Beds for Research Networking Graphic/image limits Graphic/image limits. Logo’s should be justified bottom left The European IST project MUPBED Integration of applications with network control plane Henrik Wessing, TNC’2005, 7th of June, 2005, Poznan, Poland

2. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 2 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Motivation Application initiates at client Application requests network resources Network dynamically allocates resources Issues to consider Application to network interface User network interface (UNI) Multidomain traffic engineering Application requirements

3. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 3 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Agenda European IST project MUPBED Objectives Consortium MUPBED test bed Advantages of ASON/GMPLS MUPBED test bed interconnection Reference architecture Applications Initial application groups Test scenarios Modelling activities User communities Workshop on MUPBED Thursday Summary

4. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 4 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed European IST project MUPBED Main Goals Verification of ASON/GMPLS control of multi-domain optical networks Investigate benefits of application driven circuit on demand switching Sub objectives Interoperability experiments between different network domains; To assess the ability of ASON/GMPLS solutions to support demanding research applications. To identify service/network requirements of high-end applications for European research environments To develop guidelines for the introduction of ASON/GMPLS technologies and ultra-broadband services in future European research infrastructures.

5. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 5 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed MUPBED participation Planned duration: 3 years, begin: 1st July, 2004 Consortium: 16 partners from 8 countries Denmark (DTU) Germany (Marconi, T-Systems, FAU, DFN) Hungary (MT (formerly Matav)) Ireland (Juniper) Italy (TILAB, Marconi, CSP, GARR) Spain (Telefonica, RedIris) Sweden (Acreo) Poland (PSNC) Partners: Equipment providers Telecom operators NRENs Application providers User groups

6. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 6 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed IT IP/MPLS IT Network Domain 1Network Domain 2Network Domain 3 Users / Applications Network IT platforms SW components CPU Storage Sensors / Instruments I/O devices ASON/GMPLS Initial reference structure Interaction between IT platforms and network Interoperability between network domains

7. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 7 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed MUPBED network layout Northern test bed: GMPLS enabled Eastern test bed: Ethernet based Central test bed: ASON/GMPLS enabled Southern test bed ASON/GMPLS enabled Western test bed: IP/MPLS based 4 NRENs GÉANT

8. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 8 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Physical L2 tunnels Source: D3.1

9. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 9 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Logical test bed Source: D3.1

10. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 10 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed ASON/GMPLS integration of layers Interconnection between NE (not only through management) UNI signalling for NE interworking NNI signalling for routing purposes Allows for route setup through the control plane Today Tomorrow

11. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 11 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Proposed Reference Architecture Data Plane IP/MPLS SDHOTHLambdaFibre Ethernet IP/MPLS Packet layer Circuit layer MUPBED multi-service transport network Application Plane HQ video conf content/ storage GRID Control Plane GMPLS Peer-to-Peer Approach Overlay approach Packet Layer CP Circuit Layer CP Control Plane Mngmnt Data Plane Mngmnt Plane Application-Network Interface

12. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 12 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed UNI model Direct communication between the application side and the network control and transport plane Application side responsible for requesting resources in the network

13. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 13 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed API model Application communicate through adaptation layer Resource request communicated through API Policing, AAA etc. in adaptation layer

14. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 14 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Applications in the test bed HQ uncompressed video transport Distributed studio and editing equipment Each camera requires 300-600 Mbps Latencies less than 150 ms. Videoconferencing Point to point and multipoint conferencing Latency critical Content and storage Bandwidth critical Grid Virtual Organisations Network availability Security High bandwidth as discussed in previous sessions

15. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 15 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed TILAB test scenario for VO

16. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 16 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Modelling scenarios Modelling to support experiments Application evaluation Static traffic engineering Adaptation evaluation

17. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 17 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed OPNET for modelling at DTU OPNET modelling tool reflects the traditional way of thinking Application triggered LSP setup not directly supported Standard models modified Processes modified and adaptation process implemented

18. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 18 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed User communities Close collaboration with a number of user groups Polytechnico de Torino (Italy) IRT (Germany) UPC (Spain) University of Copenhagen (Denmark).... Applications New and not yet deployed distributed applications Network demands evaluated theoretically and experimentally Constantly searching for new UCs If topics are not covered – let me know!

19. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 19 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Code word: ”Integration” ”Holistic” network view Horizontal integration Interconnection of test beds Integration of common control plane Vertical integration Definition of layer adaption Communication channel Research application validation Human integration Telecommunication world Computer science world Two different network perspectives Common understanding important

20. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 20 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed MUPBED workshop Thursday Objectives Common understanding of application requirements to the network Common understanding of what the network can provide Agenda Short introduction (MUPBED) Ralph Niederberger, R. C. Juelich Application requirements from grid. Motivated by VIOLA and DEISA projects Norbert Meyer, PSNC Grid services in the optical network PIONEER Afrodite Sevasti, GRNET(streamed) GN2, JRA3 and SA3 activities Time allocated for open discussions When & where Thursday the 9th @ 14.00 Congress center, room E Registration not mandatory but very helpful

21. Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed 23/02/2016 - 21 Limit for content Do not exceed Limit for contentGraphic/image limits Limit for content Do not exceed Limit for content Do not exceed Limit for content Do not exceed Summary – MUPBED project Motivation for MUPBED Dynamic resource allocation Investigation of multi domain ASON network issues Requirements of high demanding network applications MUPBED testbed Five larger European testbed Interconnected through NRENs and GÉANT Reference architecture Applications in focus Four preselected application groups Labs being prepared for inter test bed experiments Modelling work to support experimental work Close collaboration with user communities Workshop on MUPBED Thursday afternoon (14.00-17.00)