Saturday School: Open and Virtualised is not Single-Vendor! In the heartbreaking story “Into the Wild” Chris McCandless died after eating wild sweet pea, Hedysarum mackenzii, misidentified as wild potato, Hedysarum alpinum. It shows the value of calling something by the correct name. Telecoms could learn this lesson. I illustrated the growth in mobile data with images of 4 mobile phones. Now it just so happens that 2 of these devices were proprietary HW and SW and interfaces (Single-Vendor who was the only one who would supply chargers etc) and when we bought a new handset we had to re-buy all the accessories from the same vendor. The later 2 were running open SW, built around a 3rd party chipset, and have standard physical and SW interfaces (e.g. (Micro)USB(-C) 3.5mm audio jacks and Bluetooth). Today we buy them and do not think for a second that we can use any charger, headphones, Qi charger etc and load the same apps onto any model, and expand memory with MicroSD. We’re at this same inflexion point with RAN. There are proprietary solutions, where I can only connect Vendor E radios to Vendor E SW running on Vendor E HW; and there are fully open solutions which I can run on any server (upon which I can run other applications in parallel) and connect other companies radios to. Should we call the HTC U24 Pro “Single Vendor”, running Android14 on Snapdragon 7 Gen 3 chipset, which I can accessorise with my existing Bose wireless earphones and Anker chargers? I can delete all the manufacturer apps and put my own on there. Should I equivalate Vendor E SW, running on 3rd party CaaS, on Dell Servers (which might be also running UPF and a Computer Vision App) connected over OFH to Vendor E oRU with - Vendor F oRUs on order - to a 100% Vendor E proprietary solution? No, it’s Multi-Vendor Open vRAN vs Single-Vendor tRAN. #Infrastructure #EveryDaysaSchoolDay #Mobile 🤳🏼 #Telecommunications #CallEverythingByItsRightName Previous Post: https://lnkd.in/ezzzPuQT
Very well chosen handset examples there Paul 😅
Interesting view
🚀 Rethinking & Building new #Telco
4dWhere’s the iPhone ))))