“The difference between extracting simplicity and mastering complexity is largely whether we focus on defining the right abstractions or creating new mechanisms.”
Scott Shenker.
The diagram below provides a slide taken from a speech by Scott Shenker on the principles behind SDN (Software Defined Networking).
You can listen to the words surrounding this slide roughly 14 minutes into the video.
Shenker speaks of the concept of abstraction / modularity within software, coming from the work of Barbara Liskov in the 1970’s, allowing one person to solve the complexity of one module of a solution, which is then highly simplified when it is called upon by other programmers.
The slide above points to the fact that networking hasn’t used this concept of abstraction, meaning that a developer has to build the complete solution and can’t just build on the abstracted work of others. SDN is the mechanism of developing these abstractions to simplify networking.
This in turn provides the potential for simplification of OSS when it calls on an SDN, but also in the abstraction of elements of the OSS and interfacing to your OSS.
Earlier this week, I was lucky enough to be introduced to a talented RAN automation expert. He’s one of Australia’s foremost, hands-on, experts on SON
I was listening to a group of telco experts on a podcast the other day. As they were talking, I kept picturing the image of
Earlier in the year, we wrote a series of articles about the chasm that exists between OSS/BSS buyers and sellers (pt1, pt2, pt3, pt4, pt5, pt6). “The chasm” is
Actually, maybe a few related questions. As you’ve seen from recent articles such as this, I’m increasingly interested in the cross-over worlds of comms and
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
