SDN and NFV in FTTH

Submitted by fredrik.nyman on Thu, 03/21/2019 - 09:51

I love acronyms. You got three of them in the title of this post.

In recent years we got Software Defined Networking (SDN) and Network Function Virtualization (NFV). Many of the large telcos have invested millions into research of these subjects and are pushing the industry in this direction. Telefonica has expressed high ambitions to move to a completely SDN/NFV enabled network in record time. All the big ones are involved.

The short story is SDN=automation. A piece of code running in a server can set up the necessary configuration of all technical equipment involved in delivering a service. NFV=software instead of hardware. Those expensive big routers can be reduced to cheaper brute-force ASIC solutions and all that intelligence in implementing advanced functionality is moved to software running on a server in some data center. The expected outcome is faster deployment of new functionality (only upgrade the software), easier scaling (moving the software to more or fewer servers to match the need) and lower cost (cheaper hardware). The agility and flexibility to introduce new functions and scale is often cited as they key benefit.

Image removed.

But agility and flexibility in relation to what? Well if you are a big telco that have been around for 100 years there is a legacy of systems and processes and the way things are done to implement a new service that is considered slow and inflexible in today's rapidly changing world. That is why Telefonica, Deutsche Telekom, AT &T and others are interested in SDN/NFV and that is why much of the industry have this new talking point that gets a lot of attention. At this time perhaps 5G is about to take over the role of most exciting topic on the worlds telecom related conferences, but SDN/NFV still hangs in there and everyone sort of expects 5G to be implemented with SDN/NFV solutions.

Unfortunately the state of SDN/NFV is not as far ahead as many would like, at least not if you are thinking about FTTH. In certain very specific applications there are solutions available - a server with software might replace your BNG in the near future, but as a general technology for all sort of networking… no.

Hopes and expectations are that there will be open-source somehow magically created to implement all the cool services and that you will be able to download a complete network from github, just add the hardware from the cheapest online shop for white box gear that you can google. Reality is something else.

Open-source is great. We have built a lot of functionality in iBOS on open-source, but there is not enough stable open-source out there to create a complete embedded operating system for network equipment with all the functions needed for any normal FTTH network.  You can pick the pieces together but they do not fit out of the box so some (a lot) tweaking is required.

Your see, open-source does not just magically appear. It takes time and devotion from some individual or group of coders that have a common interest or specific need to solve to create the code for it. So unless your needs happen to be the same as theirs you won't be able to just download, compile and run it.

Then there is the matter of getting it production ready. Testing, integration (not least if we talk about white boxes with NFV programs on servers and an SDN controller on top). Telefonica probably have thousands of people working with their systems and network design and research to get there. A city network deploying FTTH have a couple of guys running the network, designing, deploying, troubleshooting and trying to have an eye on the future.

If you pick your whitebox hardware, your embedded network operations system, your SDN controller and your NFV features all from different sources, who is going to put it all together and ensure that it all works together? And who is going to solve the problems when one component fails?

Network operators going down the SDN/NFV route need to be prepared to have their own system and integration testing teams and maybe even find a couple of coders to fix the problems that prevents the solution from working in their environment.

Eventually SDN and NFV technology will make its way into FTTH networks, but for the majority of networks built today and over the next few years, SDN and NFV are not mature enough and too far away from deployment ready to be a good solution for a city network with a handful of engineers doing everything.

Sure, some of the larger telcos will build their networks on this technology, and sure there will be SDN/NFV implementations of certain specific functions (such as the BNG) in the FTTH networksbut the whitebox-NFV-SDN nirvana with open-source that just works out of the box is far away yet.

Don't get me wrong. I think SDN and NFV are very interesting technologies that will change how networks are built and Waystream is of course working on these topics as well. But it is from that work that we realize how far away the solutions worked on today are from being useful for our customers.

Blog posts

Turn on automation of your FTTH network

Submitted by fredrik.nyman on Mon, 04/01/2019 - 09:08

The distributed nature of a fiber to the home network means that you will have equipment spread out and you might not always do the on-site installation yourself. If every switch has to pass your desk for pre-configuration port before getting deployed into the field you will need to deal with the logistics of getting the units from your warehouse via your desk, packing and unpacking, and clearly marking them so that the right unit goes into the right location.

SDN and NFV in FTTH

Submitted by fredrik.nyman on Thu, 03/21/2019 - 09:51

I love acronyms. You got three of them in the title of this post.

In recent years we got Software Defined Networking (SDN) and Network Function Virtualization (NFV). Many of the large telcos have invested millions into research of these subjects and are pushing the industry in this direction. Telefonica has expressed high ambitions to move to a completely SDN/NFV enabled network in record time. All the big ones are involved.

Keeping product lines around

Submitted by fredrik.nyman on Fri, 03/15/2019 - 09:50

Building fibre to the home networks are different from any traditional enterprise or telecommunications network. One of the main differences is the time it takes to complete the network. You make a plan, design a an architecture with VLANs and redundancy and imagine how this will scale as the number of connected customers increase. But then the years go by, because building a fibre network to connect every home in the community can take decades.

Save the planet - work from home

Submitted by fredrik.nyman on Thu, 03/07/2019 - 10:30

In my last post i revealed how dirty a fiber network can be depending on the source of electricity powering the network. I showed how a typcial 24-port access switch might contribute anything between 23kg to 485kg of carbon dioxide per year to the atmosphere depending on the electricity mix and how that can be reduced with lowpower optical modules.

How do you troubleshoot IoT devices?

Submitted by fredrik.nyman on Fri, 02/15/2019 - 13:00

Continuing on the subject of troubleshooting the network. Troubleshooting MPEG video has the benefit of a user that can tell you if it doesn't work and you can simply ask that user if the problem persists once you have fixed it. But what if there isn't any obvious way to determine if things are working, for example is that trashcan really signalling that its' full or does the temperature device really update the building climate control properly?

How to see what your users see

Submitted by fredrik.nyman on Mon, 02/11/2019 - 10:21

Live broadcast TV is one of the most popular services in fibre networks. You can get high quality pictures because there is enough bandwidth to send video uncompressed. But the nature of broadcast media is that it is very sensitive to packet loss or jitter. There is no retransmission of packets because it is live – you can’t hold the stream to get a lost packet back.