Program Access 4.0 / A4 and the Role of the Community. Access 4.0 Team Presenters: Manuel Paul, Bjoern Nagel

Transcription

1 Program Access 4.0 / A4 and the Role of the Community Access 4.0 Team Presenters: Manuel Paul, Bjoern Nagel

2 Access 4.0 is the Design of a new access platform with tight coupling to a cost model Gigabit ready Technology Cost model FTTH/xPON FTTB/G.Fast A4-PoD 1) Cost model developed from day one Strong interworking between architecture / design and Cost modelling Comprehensive application of Design-to-cost methods Hybrid FTTC/xDSL 4G / 5G production of Gigabit IP e.g. located in the CO IP Backbone Access 4.0 Design Cost Case 1) Access 4.0 Point of delivery: production of broadband IP 2

3 Access 4.0 / A4 Scope & Objectives B/OSS Backbone Scope of Access 4.0 Extensive D2C project for FTTH/B Everything monitored in a comprehensive Cost Model Design and engineering using bare metal / OCP hardware, lots of open-source software as well as merchant silicon Application of data center principles, leaf/spine fabric, CI/CD, Clean IT architecture (Las Vegas principle) Objectives of Access 4.0 Save CapEx and OpEx Reduce vendor lock; bring in new players Drive automation Time-to-Market for services (keep business logic SW in house) Increase flexibility for capacity mgmt, change-over, migration, x 900 Control WDM WDM x 1 Leaf /ToR Service Edge Spine-Switch x86 Central EMS Local Management Leaf /ToR Service Edge Spine-Switch Control x86 Control x86 Leaf /ToR Service Edge ONT XGS-PON LT XGS-PON LT XGS-PON LT XGS-PON LT DPU 3

4 Design paradigm: Control plane / user plane split no fragmentation, please App1 App2 App3 Control Plane Fixed / mobile or converged control applications (usually on x86) CP/UP Mediation Layer Drivers D1 D2 D3 D4 D1 D2 D3 D4 Forwarding Plane Platform Compatibility Framework with standard set of APIs avoids hardware lock-in provides compatibility to apps/features through common protocol and data model for forwarding provides compatibility of management tools and practices Anything south of the dotted line to be provided by hardware vendor Programmable hardware on bare metal (Differentiate through performance & exposed feature sets) 4

5 VOLTHA: Successful instantiation of The key Design Principles Open hardware Bare metal switch platform, carrying programmable switching & PON chipsets a PC board (for drivers, services) Modular, based on carrier requirements e.g. specified at Open Compute Project Customize like a PC Transparent regarding technology and cost Open software Open driver & application platform, building on VOLTHA Modular, scalable Standard interfaces & protocols Mediates towards SDN Control Integrates vendors drivers Reduced testing & integration efforts, community-driven *picture sources: EdgeCore Networks, opencord.org 5

6 Hardware Design: Motivation & Design Guidelines Motivation for OCP Specification Eco system for white box PON devices leaves room for improvement! Few devices from few vendors with little telco experience Carriers want at least two suppliers need more choice! DT wishes to foster the community & there was a need for more participation Last but not least : We hope to instigate other contributions to create competition, innovation and better economics... Design guidelines Reuse existing work to allow for quick implementation Use mainstream merchant silicon & COTS (Commercial Off The Shelf) components Comply to relevant standards Allow & promote the use of open source software Aim for state of the art performance at optimum total cost of ownership Create something that the world needs! After some great joint efforts with partners the spec went through the administrative process and is published now! 6

7 Dt olt specification at ocp Design choices and details : Specification selects a first straight forward solution, derive from what works for XGS-PON : Well known merchant silicon combination from Broadcom (Maple/Qumran) with off the shelf driver software (BAL) to be integrated into open source VOLTHA framework. 32 and 64 port variants : good fit to chip granularity, uplink capacity and Central Office size (as number of subscribers) Redundant AC/DC PSUs (hot swappable, VAC, 50-60Hz autoranging & 48VDC), high efficiency Flexible Uplinks : 2x100G as QSFP28 to allows in-rack AOC/DAC plus 8x10/25G SFP28 cages or (C)WDM transceivers for longer reach and WDM for fiber saving Telco environment implies a long life span 10 years is typical The control SW & interface is evolving rapidly - Our spec explicitely embraces this fact! 7

8 Programmable hardware: a4 switching fabric What has changed SDN was never only about central flow / path management it also is about programmability It might not have worked at the beginning as planned but now There is programmable silicon ASICs, NPUs, Smart NICs,. Powerful SDKs for proprietary chipsets Open, domain-specific languages like P4/P4 Runtime Application inside access 4.0 Programming the FIB into silicon on the backplane Distributed routing control plane Programming a service edge into merchant silicon programmed the data path for PPPoE termination Enhanced debugging features abstract to have a common control API independent on hardware used below 8

9 Open components in access 4.0 prototype Hardware XGS PON OLT + ONT Bare metal switches x86 Servers Software Open Network Linux Ubuntu Linux Kafka Kubernetes, Docker + lxc container, KVM Device abstraction via volt-ha and ONOS Service Edge on Tofino (PPPoE, CP and UP) POD Life Cycle Manager (LCM) POD Control Plane (PPA, Weiche ) POD EMS, Grafana green color code: open source / open spec magenta color code: DT development, possibly to be open sourced black color code: DT specific or vendor proprietary 9

10 Looking forward to Extend Collaboration with the community POD API Definition Hardware Specs Service Edge API Device Drivers Overall System Design *logos are courtesy of the respective organizations 10

11 Summary

12 A4 turned two in summer. What has been achieved for ftth/b and What s next? 1 Real code running FTTH/B@A4 Multiple PPPoE sessions All based on bare metal + open source (K8s, voltha) Focus on automation (ONT bring-up, ZTP / capacity- and change mgmt. etc.) 2 Feasibility Study finalized and Cost Model developed Document shared with 30+ experts within DT Assumptions and technology in Cost Model documented; Cost Case is green 3 Collaboration / Community OCP spec for OLT submitted ONF-Community event June 2018 Code contribution for voltha Alignment with other Operators 4 RfQ for Co-Dev Partnership FTTH/B@A4 RfQ issued in June, finalized end of October Objective: find a partner who shares vision and wants to productize the A4 design 12

13 Thank you 13