![]() ![]() ![]() Not at all sure, it would be a development in the right economic direction. At the time, I had reservations about its impact on network planning, operations, and network efficiency. I believed there could be other ways to offer the same variety of service experiences without this additional (what I perceived as an unnecessary) complexity. With the “We can” rationale based on the maturity of cloudification and softwarization frameworks, such as cloud-native, public-cloud scale, cloud computing (e.g., edge), software-defined networks (SDN), network-function virtualization (NFV), and the-one-that-is-always-named Artificial Intelligence (AI). It felt a bit (a lot, actually) as a “let’s do it because we can” thinking. My thoughts were that taking the slicing concept to the limit might actually not make any difference to not having it, except for a tremendous amount of orchestration and management overhead (and, of course, besides the technological fun of developing it and getting it to work). I did simply not see (or get) the point of introducing this level of complexity. Full disclosure … when I was first introduced to the concept of Network Slicing, from one of the 5G fathers that I respect immensely (Rachid, it must have been back at the end of 2014), I thought that it was one of the most useless concepts that I had heard of. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |