1 / 25

MAINS (Metro Architectures enablINg Subwavelengths)

MAINS (Metro Architectures enablINg Subwavelengths). WP3 Control Plane and Service-Network interface development. Javier Aracil (WPL, UAM) Giacomo Bernini (NXW) MAINS 2 nd EC Technical Review Brussels, March 29 th 2012. Contents. Brief WP3 summary Objectives, activities and Y2 results

tassos
Download Presentation

MAINS (Metro Architectures enablINg Subwavelengths)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MAINS (Metro Architectures enablINg Subwavelengths) WP3 Control Plane and Service-Network interface development Javier Aracil (WPL, UAM) Giacomo Bernini (NXW) MAINS 2nd EC Technical Review Brussels, March 29th 2012

  2. Contents • Brief WP3 summary • Objectives, activities and Y2 results • Technical insight on Y2 results • MAINS-TP Protocol • Nomadic Virtual PC application • MNSI Gateway prototype • MAINS GMPLS prototype

  3. Main WP3 objectives [Y1] Define a service-network interface specification (control & data plane) [Y1] Define enhancements to GMPLS and PCE for sub-wavelength support (MAINS GMPLS & MAINS PCE) [Y2] Implement the service-network interface (prototype) [Y2] Implement the GMPLS control plane for sub-wavelength networks (prototype) [Y3] Implement a centralized PCE server in the metro domain for path computation purposes (prototype)

  4. Activities breakdown Y2/Y3 Y1 Y1 Y2

  5. WP3 workplan M19 Implementation of service-network interface M26 Implementation of centralized MAINS PCE Y2 M24 Implementation of GMPLS extensions

  6. Y2 work summary & main results • Starting points of work • MAINS Architecture, MAINS Transport Protocol & MNSI specs (T3.1, D3.1) • MAINS GMPLS/PCE architecture & protocol extensions (T3.2, D3.3) • Y2 efforts completely devoted to prototype development and early functional testing (T3.3 + T3.4) • Also started implementation of MAINS PCE sw modules (75%, due by M26) • Main Y2 results • MAINS TP prototype (T3.3, D3.2) • MNSI Gateway prototype (T3.3, D3.2) • MAINS GMPLS prototype (T3.4, D3.4)

  7. WP3: from specs to prototypes MAINS TP and MNSI Gateway prototypes Interface specification at control and transport plane WP1 D3.2 Implementation of service network interface D3.1 Service network interface specification D1.1 MAINS GMPLS prototype D3.4 Implementation of GMPLS extension Detailed signalling and routing protocols extensions Y2 results WP2 D3.3 Control plane extensions for GMPLS M26 D2.1 D2.3 D3.5 Implementation of the centralized MAINS PCE Y1 results Y3

  8. Technical insights on Y2 results • [UAM] MAINS-TP • [UAM] Nomadic Virtual PC • [NXW] MNSI Gateway • [NXW] MAINS GMPLS • Y3 future plans

  9. Motivation for transfering Virtual PCs Plenty of small packets in RDP sessions

  10. Motivation for transfering Virtual PCs Really bursty sessions

  11. The MAINS-TP protocol: throughput MAINS

  12. The MAINS-TP protocol: ACK reduction

  13. Nomadic Virtual PC Application

  14. MAINS GMPLS and PCE implementation activities • Three planned deliverables in T3.4: • D3.2 [M19]: Implementation of service-network interface • Deployment of the MNSI Gateway prototype • D3.4 [M24]: Implementation of control plane extensions • Deployment of the MAINS GMPLS controllers prototypes (MAINS LER, MAINS LSRs) • D3.5 [M26]: Implementation of the centralized MAINS PCE • Deployment of the MAINS PCE centralized server prototype D3.5 D3.4 D3.2

  15. [D3.2 insight] MNSI GW prototype • One VBOX Virtual Machine released: • NXW-GMPLS object code + MAINS UNI client dependencies (base libs): • Client Call Controller (CCC) • Signalling Controller and G.RSVP-TE protocol • Link Resource Manager (LRM) • Transport Network Resource Controller (TNRC) • A short guide for installation and operation tips • A set of testing scripts to carry out some early functional tests on the released components • Functional tests scoped to the MAINS UNI signalling initiation: • peering GMPLS edge controllers (UNI-N) released @M24 (D3.4) • Only IETF call setup procedure tested (i.e. delivery of G.RSVP-TE Notify messages)

  16. [D3.2 insight] MNSI Gateway high-level functional split MNSI Gateway MAINS Network Service Controller MAINS UNI-C Client Call Controller (a/z) Resource Ctrl Signalling Signalling Controller Link Resource Manager Transport Network Resource Controller RSVP-TE MNSI Agent (provider) Server Client MNSI MAINS UNI

  17. [D3.4 insight] MAINS GMPLS prototype • Three VBOX Virtual Machines released: • MAINS GMPLS UNI-Client controller • MAINS GMPLS Label Edge Router (LER) controller • MAINS GMPLS Label Switch Router (LSR) controller • Each VM contains NXW-GMPLS stack binaries and libraries • gmpls-ccc, gmpls-ncc, gmpls-rc, gmpls-grsvpte, gmpls-lrm, gmpls-scngw, gmpls-tnrc, • gmpls-manager • startup/shutdown ctrl and automatic handling of software modules with inter-dependencies • gmpls-sh (gsh) interactive CLI • single configuration entry point for the whole GMPLS stack • Early functional tests performed on the MAINS GMPLS controllers • sub-wavelength LSP signalling with transport plane emulation • End-to-end sub-wavelength signalling tests in WP4 during Y3 • “horizontal” integration with application layer (i.e. Virtual PC) • “vertical” integration with transport plane (OPST and TSON)

  18. [D3.4 insight] MAINS GMPLS software modules • Choice to focus on key aspects for the prototype implementation • OSPF-TE not a key feature to validate/demonstrate the MAINS concepts • LRM from each GMPLS controller can directly push towards the MAINS-PCE its local resource information and update them when needed • MAINS concepts and results not affected by OSPF-TE bypass • OSPF-TE used as just a raw TE flooder up to the centralized MAINS-PCE

  19. [D3.4 insight] CP/DP interworking: XML interfaces • Final XML#1 and XML#2 operates very differently in terms of control functions • too many native differences between OPST and TSON • unique transformation function between XML#1/XML#2 and XML#3 became unfeasible • Prototype implementation • Two different “XML clients” developed in the GMPLS CP (TNRC Specific Part) • TNRC SP for OPST ring (XML#1) • TNRC SP for TSON controller (XML#2) • XML#1 and XML#2 called directly from the TNRC Abstract Part • TNRC AP maintains the generalized DP model exported to GMPLS protocols (XML#3 like semantic)

  20. [D3.4 insight] Roles of MAINS GMPLS controllers

  21. MAINS GMPLS developments summary

  22. MAINS GMPLS developments summary (contd.)

  23. RSVP-TE protocol extensions: examples Enhanced Explicit Route Object for a single hop sub-wavelength LSP (from gmpls-grsvpte log) Sub-wavelength SenderTSpec Object (from gmpls-grsvpte log)

  24. Y3 future plans • Ready for EC delivery • MAINS PCE server prototype release (D3.5, M26) • path computation procedures and mechanisms (as per D3.3) • IETF PCE centralized model (RFC4655) • hierarchical PCE model for multi-domain scenarios (draft-ietf-pce-hierarchy-fwk) • sub-wavelength aware network topology • cooperation with TSON SLAE (WP4) to get time-slice allocation • Support to the WP4 integration and tests activities • MAINS GMPLS integration with OPST ring and TSON mesh network (T4.3) • end-to-end sub-wavelength signalling procedures tests • MAINS PCE and TSON SLAE integration for sub-wavelength path computations • “vertical” integration with transport plane through the XML interfaces • Process WP4 feedbacks to refine MAINS GMPLS/ PCE prototypes (bug fixing) • possibly release the final and consolidated MAINS GMPLS/PCE prototypes at the end of the project

  25. Thank you

More Related