“The only real life is the collective life of the race; individual life has no existence except as an abstraction.”
Auguste Comte.
Starting with the network layer, each step up the management hierarchy gives a shallower representation of device data, but a broader view of device connectivity.
Or as described in an earlier post entitled “What an OSS shouldn’t do,” each subsequent step northbound does the same thing:
Conversely, each step down the management stack should produce a narrower (ie not so many device interconnections), but deeper field of view (ie a deeper level of information about the fewer devices).
This concept will be even more important when managing virtualised networks. As described in this post, virtualised networks have more “moving parts” to manage so it will be important that this complexity is abstracted before being presented to the OSS and BSS layers.
Will this actually occur? Let’s wait and see what the market produces in coming years.
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.
