RENOVATION is in! Be it in houses or in networks …
We renovate our houses primarily to provide a facelift and customize the look and feel to suit our needs. In the process, we do not usually throw away all old items but reuse a few of them and further invest in buying new ones.This is, very well, true for Telco Networks that now needs a RENOVATION or an urgrade with virtualisation technologies such as: Software Defined Networks (SDN) and Network Function Virtualisation (NFV). Let’s explore the Telco imperative to virtualise their networks.
Why virtualise a Telco Network
- Custom suited to operators need in the long run by enabling network programmability
- Aligned to future evolution path on Telco networks
- To launch services faster and automate time-consuming activities like provisioning and making networks AGILE
- To make the network vendor agnostic in the long run
- To save on OPEX year on year
SDN Market is expected to reach USD 8 Billion by 2018 as predicted by IDC. Gartner, in its Hype curve has put SDN/NFV in the category "Trough of disillusionment" which is not disappointing and should be interpreted not in "Over Hyped" category but in actual "Reality mode" with realistic revenue predictions.
It is important to understand that SDN and NFV are different terminologies and technologies and should not be confused or used alternatively. Separate standardization firms are working towards their evolution. Open Networking Foundation (ONF) is a leading standardization body for SDN and ETSI Industry Specification Group (ISG) for NFV. However many more standardization institutions/technology bodies, such as IETF, Openstack, Opensource, and ONAP, etc., also provide their viewpoints on SDN/NFV. SDN/NFV can be implemented mutually exclusively but operators shall benefit most when they could combine the advantages of both the technologies and implement it together.
Fig: Correlation between SDN, NFV and Open Innovation
Let us now bust some myths floating around SDN/NFV for Telcos.
Myth 1: SDN/NFV equipment reduces the floor space occupancy (footprints) of equipment required
Reality: SDN/NFV equipments use commercial off-the-shelf (COTS) hardware, which are not custom made, hence it may not be possible at once to beat the advantages of ATCA based H/W or other vendors custom made H/W built purely to keep up with software processing speed. Of course technologies like DPDK are evolving to speed up the system but Hardware computing (occupying same footprint and power) falling short compared to speed of software is not uncommon
Myth 2: SDN/NFV equipment requires you to throw away all that is running inventory of Network Elements
Reality: There shall be a phase existing where both legacy and new technologies co-exist and move to future. There will be an overlay concept where old legacy equipment can be latched onto new systems at the same time accommodating new SDN/NFV system.
Myth3: SDN/NFV is suitable for each type of applications
Reality: Whereever the computing power is more and physical speeds are less, it is optimal to virtualize applications in comparison to those which require high throughput. eg: OSS/BSS layers, Layer 4 to 7 applications are among the first to be virtualized and last is Packet Gateways with a lot of Physical throughput requirements.
The prime applications that would evolve with these technologies are:
1) SD WAN
2) Virtualization of IMS and EPC 4G network
3) Zero touch provisioning
4) Service Chaining
5) Virtualized CDN
6) vCPE and Residential Gateways
The glimpse of network with SDN and NFV co-existing is depicted in the below graphics.
Fig: SDN+NFV Architecture, Source: Intel
SDN talks about separating the control plane from the bearer(data) part while NFV is more about putting software functions of Virtual modules. Interestingly, Openflow - the popular protocol in SDN environment originated in the college campus area. With the evolution of ICT technologies, the future SDN/NFV is all set to ROCK!