In the past couple of months, we delivered several webinars together with Intelefy University related to Open RAN. In this post, you can find the collection of them, in the particular order, where the first one serves as an overview and high-level discussion, whereas the next ones dig more and more into details of O-RAN, as specified by O-RAN ALLIANCE.
RIMEDO Labs Blog
In this post, we focus on the implementation of a simple xApp tailored for the traffic steering use case. The goal of this xApp is to support the network providers to reassign the traffic from one gNB to the other in order to meet some predefined criteria. We will see some results of the great opportunity offered by Open RAN that the operator can easily install, modify or remove the xApp when needed.
In this post, we briefly present, how the concept of open RAN meets immediately one of the key approaches in distributed software design, mainly CI/CD. Clearly, these two domains cannot be compared directly, but as we will see, the O-RAN concept modifies significantly the whole software design process.
Open RAN is the separation of software functionality from the underlying hardware. This is called “disaggregation.” It is also the process of defining functional blocks in the network and clearly and precisely specifying the interfaces between those functional blocks. Most who study such things believe it to be true. But before we break out the Champaign, we should be a bit more circumspect and evaluate the threats to Open RAN. What might prevent Open RAN from reaching its potential?