Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
Alcatel-Lucent Cloud: Shaping the Future NFV OSS David Amzallag TM Forum 2013
Next
Download to read offline and view in fullscreen.

Share

How will virtual networks, controlled by software, impact OSS systems?

Download to read offline

Presentation from the OSS side of the story. How will the network change in the futur when entering the Zettabyte era? SDN/NFV explanations for the future of Telcos.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

How will virtual networks, controlled by software, impact OSS systems?

  1. 1. How will virtual networks, controlled by software, impact OSS systems. Michiel Nuytemans OSS Consulting
  2. 2. Introduction Software-Defined Networking (SDN) Network Function Virtualization (NFV) OSS: Revolution or Evolution Conclusion
  3. 3. Introduction
  4. 4. Welcome to the Zettabyte Era Source: Cisco VNI Global IP Traffic Forecast, 2015–2020 Annual global IP traffic will pass the zettabyte ([ZB]; 1000 exabytes [EB]) threshold by the end of 2016, and will reach 2.3 ZB per year by 2020.* Year Global Internet Traffic 1992 100 GB / day 1997 100 GB / hour 2002 100 GBps 2007 2,000 GBps 2015 20,235 GBps 2020 61,386 GBps Historial Traffic
  5. 5. Global IP traffic is not only growing but also changing Busy-hour Internet traffic is growing more rapidly than average Internet traffic. Globally, IP video traffic will be 82 percent of all IP traffic by 2020, up from 70 percent in 2015. Smartphone traffic will exceed PC traffic by 2020.
  6. 6. The importance of QoS Quality of Service is important
  7. 7. OTT services have an impact on the ARPU
  8. 8.  Grow network capacity.  Support QoS.  Reduce time-to-market. Does this have an impact on the network infrastructure?
  9. 9. But what about the Budget? *based on information from Equinix (2009-2014)
  10. 10.  Multi-technology silo´s.  Multi-vendor networks.  Low level of automation.  Agnostic to services.  Sub-optimal configuration and management. Increased complexity due to mix of vendors and technologies
  11. 11. Software-defined network
  12. 12. The network before SDN Client DC Control Plane Data Plane Control Plane Data Plane Control Plane Data Plane Control Plane Data Plane A B
  13. 13. Life after SDN Control Plane Data Plane Control Plane Data Plane Control Plane Data Plane Control Plane Data Plane Data Plane Data Plane Controller Data Plane Data Plane Application ApplicationApplicationEMS/NMSCLI Vendor- Specific
  14. 14. SDN - Architecture SDN architecture (patterned on Open Flow Foundation materials)
  15. 15. 1. Centrally controlled 2. Software-driven 3. Programmable 4. Open SDN - Definition Data Plane Data Plane Controller Data Plane Data Plane Application ApplicationApplication
  16. 16. Real-time optimization of the network. Use of commodity hardware Rapid-innovation through software updates Platform for network service innovation SDN - Benefits
  17. 17. SDN – B4 - Google Datacenter WAN
  18. 18. Network Function Virtualization
  19. 19.  Applications are deployed on virtual environment.  Virtualization creates abstraction of actual hardware appliance being used.  Virtual environment are easier to deploy and reconfigure. NFV – Analogy to IT Virtualization Source: Basic Virtual IT-Architecture
  20. 20.  VNF are virtual network functions like Firewall, Load balancer, CPE´s, IMS, GGSN, …  VNF use virtual resources (Compute, Storage, Network) provided by NFV infrastructure.  Rapid deployment of VNF´s  Scalable / Elastic  Scale-out  Scale-up  Innovation decoupled from hardware NFV – Definition and Architecture Source: ETSI NFVI architecture
  21. 21. NFV – The case of vCPE´s
  22. 22. OSS: Revolution or Evolution
  23. 23. STRATEGY, INFRASTRUCTURE & PRODUCT OPERATIONS SUPPORT & READINESS FULFILLMENT ASSURANCE ServiceManagement OSS Process Management SLA Monitoring Customer Experience Management Service Quality Management Service Monitoring Service Order Management Service Fulfilment Service Activation Service Inventory Management Service Catalogue Performance Management Fault Management Network Planning & Design Network Inventory Management Auto-Discovery & Reconciliation Configuration Management OSS Mediation Field Service Management ResourceManagement Other Systems (BSS, Trouble Ticketing, etc.) COMARCH OSS SUITE Reusable Components Authentication Service Reporting Service System Repository & Configuration Notification & Escalation Service OSS Console GIS WEB Console One comprehensive system managing the whole network: • Physical elements • Network logical elements • Service instances
  24. 24. ETSI Ref Arch - Comarch OSS NFV - BSS/OSS OSS – Traditional Role Real-time OSS
  25. 25. SDN architecture – vision SDN – BSS/OSS
  26. 26. OSS SUITE - where is the NFV/SDN module? SID MODEL: CFS-RFS-R as a basis for model-driven orchestration Customer Service view triggering scalability and self-healing PNF & VNF as Logical Resources Alarms NFVI and PNF & VNF KPIs for NFVI and PNF & VNF Model-driven orchestration
  27. 27. It’s all about new services being introduced much faster CFS CFS x RFS RFS 1 RFS RFS 1 RFS RFS 3 PNF Network Function PNF Network Function Dedicated Hardware Physical Resource VNF Network Function VNF Network Function Dedicated Hardware Physical Resource Blade Physical Resource Blade Physical Resource Blade Physical Resource Virtual Machine Logical Resource Virtual Machine Logical Resource Virtual Machine Logical Resource ETSI VNF On- boarding: VNF Descriptors in Yang, or TOSCA, etc. ETSI NS On- boarding: NS Descriptors in Yang , or TOSCA, etc. CFS-RFS-R modelling via GUI Service Catalog (No Yang etc. Scripting)
  28. 28. VPN example – traditional implementation
  29. 29. VPN - based on SDN and NFV
  30. 30. VPN – access to business applications and Internet
  31. 31. VPN - implementation details CPE: Control Plane – SDN controller applications Firewall as VNF on NFVI CPE: Data Plane – Flow entries in OFP Switch
  32. 32. VPN - Catalog driven fulfillment class Domain Objects «CFS» VPN «CFS» SiteManagedLAN - IPSubnetwork :int «CFS» SiteAccess - bandwidth «CFS» BusinessApplications - IPAddress - MAC «CFS» Host - MAC - IPAddress «CFS» InternetAccess «CFS» Firewall RFS Firewall «R» vFirewall «R» VM «RFS» SiteAccessFlow «R» CPE_OFPSwitch «R» PE_OFPSwitch «R» OFPSwitchFlowEntries «R» OFPSwitch_FlowEntries «RFS» InternetAccessFlow «R» InternetGateway
  33. 33. VPN – access to business applications and Internet 1. Enterprise Customer, issue and order for an extra Business Application at Site2
  34. 34. VPN - Fulfillment example 2. The customer order updates data in Network and Service Inventory
  35. 35. VPN - Fulfillment example 3. Network is „reprogrammed” based on data -> Data flows are updated 3 3 3 3 3
  36. 36. As a finale note…
  37. 37. Thank You michiel.nuytemans@comarch.com Comarch AG Avenue de la Toison d'Or 67 1060 Brussels Phone. +32 2 535 55 00 Fax. +32 2 535 55 01 www.comarch.com
  • williammdavis

    Dec. 3, 2016

Presentation from the OSS side of the story. How will the network change in the futur when entering the Zettabyte era? SDN/NFV explanations for the future of Telcos.

Views

Total views

974

On Slideshare

0

From embeds

0

Number of embeds

0

Actions

Downloads

51

Shares

0

Comments

0

Likes

1

×