Systems Engineering for Software-Defined Network Virtualisation. John Risson, Solutions Engineering Manager IP and Transport Engineering, Telstra

Transcription

1

2 Systems Engineering for Software-Defined Network Virtualisation John Risson, Solutions Engineering Manager IP and Transport Engineering, Telstra

3 Agenda Motivation Case Studies Opportunities and Challenges Questions SESA/INCOSE Telecommunications Working Group

4 Motivation

5 Enablers Software Defined Networking (SDN) decouples data plane and control plane Network Function Virtualisation (NFV) decouples service functions and infrastructure Virtual Service Functions Physical Infrastructure Resources Service Oriented Control and Management Infrastructure Control and Management Duan, Q., Ansari, N., Toy, M., Software Defined Network Virtualization: An Architectural Framework for Integrating SDN and NFV for Service Provisioning in Future Networks, IEEE Networks, Sep/Oct 2016

6 SDN/NFVBenefits Higher Asset Utilisation 1 2 Across whole of Network Today Dedicated Hardware for each network function. Effective Aggregate Capacity Spare Capacity for growth With Virtualised Network Functions Infrastructure Saving Lower Equipment Costs Greater competition due to whiteboxes & open source SW Initial SDN development (professional services) Small saving beyond year 1 Capacity in use Year 1 Year 2 and beyond Note: Long term difference could be marginal due traditional vendors responding to competitive threat Fewer Physical Ports 3 with service chaining 4 6 Ports 18 Ports f1 f2 f3 f1 f2 f3 Virtual Ports Physical Interfaces Lower Deployment Costs Fewer truck rolls. New functions deployed as Software f1 f2 f3 f4 f1 f2 f3 f4

7 SDN/NFVArchitecture Business & Operational Support Systems Management And Orchestration (MANO) Network Self Optimising Intelligence Policies, Analytics & Machine Learning Network PODs Virtual Network Functions Optical Optical Transport Transport Physical Resources Network PODs Virtual Network Functions Optical Optical Transport Transport Physical Resources Distributed SDN & NFV Controllers Optical Optical Transport Transport Physical Resources Distributed API Gateway Apps Service Provider, Partner and Customer applications Centralised & 3 rd Party Clouds NBN Virtual Layer 2 and Layer 3 Networks SDN enabled Optical Transport Logical Connection (Control Plane) Physical Connection (Data Plane) Network Functions self optimise: expand / contract and change location autonomously

8 Case Studies

9 1. Disaster Recovery Cyclone Debbie Edge Edge If all primary links fail, the SDN Application ensures Critical Interstate Traffic has priority. Core Core x During Cyclone Debbie, 1 link failed due to loss of power Primary High Capacity redundant Interstate Links 2 x Temporary physical links established (as backup) Core Core Edge Edge Protecting critical communications over lower bandwidth emergency links.

10 2. National Analytics Backbone Access Network Tap Fixed Broadband Control Server Existing single Collector: With traffic sent over the core network. An Overlay Core network Customer Service Monitoring National Analytics Backbone Provides redundancy for collection of network monitoring data

11 2. National Analytics Backbone Benefit Traditional Overlay Model Native SDN Model Network Traffic Device Port or TAP Overlay Underlay Network Packet Broker Appliance Layer 3 Networks Layer 2 Networks SDN Switch Optical Transport Network Shifts functionality from the underlay hardware to software and Virtual Machines

12 3. Provider Edge Routing Customers IP Metro Area Network Control and Media Gateway Phone Phone Customer Premises Equipment Fibre Edge National Multi Protocol Label Switching Core NFVi POD Virtual Provider Edge (vpe) IP Telephony Application Phone Phone Customer Premises Equipment Fibre + other Edge IP Wide Area Network NFVi: Network Function Virtualisation Infrastructure

13 3. Provider Edge Routing Initial footprint Centralised Control Orchestration Operations & Management OpenStack IP Core Network NFVi PODs NFVi PODs NFVi PODs NFVi: Network Function Virtualisation Infrastructure NFVi PODs NFVi PODs

14 3. Provider Edge Routing NFVi Architecture Networks NFVi Network IP Core Network Telephony Applications Network Spine/Leaf network OpenStack Controller Management Network Management Functions Orchestration Configuration Alarms and Logs Authentication, Authorization, and Accounting (AAA) Backup & Restore Domain Name System (DNS) Reporting Over Cloud OpenStack Storage OpenStack Compute Virtual Provider Edge Under Cloud Director

15 Challenges and Opportunities

16 Technical Challenges Management and Orchestration Traffic and function monitoring; Interoperability; Programmability; Self-management e.g., alarm processing Energy Efficiency Deployment studies; Energy-efficient hardware; Energy-aware function placement NFV Performance Selected hardware acceleration; Performance-flexibility trade-off Resource Allocation Placement, migration and scheduling of virtualised network functions; Resilience; Scaling up and down Security, Privacy and Trust Network performance isolation; Multi-administrator isolation Modelling of Resources, Functions and Services Runtime management; Federated services; Easier modelling/deployment design Mijumbi, R., Serrat, J., Gorricho, J.L., Bouten, N., De Turck, F., Boutaba, R., Network Function Virtualization: State of the Art and Research Challenges, IEEE Communications Survey & Tutorials, VOL. 18, NO. 1, FIRST QUARTER 2016

17 Ecosystem Challenges The industry is still maturing

18 Systems Engineering Opportunities Sys Eng Process Opportunities to influence typical SDN/NFV practices Business analysis Improve discipline of assessment of opportunities to a) cull capital and operational expenditure and b) provide new customer services. Value engineering. Requirements definition Architecture definition Verification Transition Lifecycle model management Enable easier reuse and evolution of requirements across the end to end solution. Model based systems engineering. Systems of systems engineering. Agile systems engineering. Achieve automation, flexibility and interoperability by improving fidelity of models of system resources, functions, services and interfaces. Model based systems engineering. Reliability engineering. Improve continuity and automation of integration testing, for solutions that will contain a mix of traditional and virtualised network elements for some time. Improve automation and frequency of deployment to production environment, while maintaining system availability. Improve use of evolving, concurrent define develop operate models, controlled by evidence and riskbased decision processes. Agile systems engineering.

19 Questions

20 SESA/INCOSE Telecommunications Industry Working Group

21 Working Group Purpose Draft The purpose of this working group is to improve telecommunications services by developing a body of knowledge that advances Systems Engineering of telecommunications solutions.

22 Working Group Feasibility Criteria 1. Eight contributors prepared to invest 30 minutes for a weekly call and an average of one hour per week for the next year in developing working group material. 2. Three engineering executive sponsors of telecommunications solutions, with at least one from a leading US telecommunications service provider. 3. Alignment and cooperation with INCOSE working groups for model-based systems engineering, security systems engineering, agile systems engineering, systems of systems, reliability and critical infrastructure. 4. Plan of work aligned with at least one leading telecommunications industry standards body. 5. Shepherding by SESA and INCOSE technical directors.

23 Working Group Discussion Items Roundtable discussion 15 minutes What two telecommunications systems engineering opportunities interest you? Who could you engage to champion or shepherd the group? What actions could you take to improve working group outcomes? Roundtable reports 15 minutes Report back Next steps Register your interest and contact details today with John Risson, sms

24 Thankyou