Along with the introduction of 5G in many CSPs, Radio Access Networks (RANs) are also expected to evolve into a more open architecture such as OpenRAN, with the objectives to:

• Increase cost efficiency, to reduce network roll-out and network operation expenses
• Improve scalability, to help the adoption of new radio technologies (i.e. 5G or the future 6G by 2030)
• Facilitate innovation, by allowing new players into the market to develop new products and solutions

The RAN Intelligent Controller (RIC) is one of the key components of the OpenRAN architecture. It provides an open software hosting platform responsible for controlling and optimising the necessary RAN functions. In practice, the RIC hosts third-party applications from specialist players, called xApps in the case of near-real time applications (i.e. 10 ms to less than 1 sec) and rApps for non-real time functions (i.e. over 1 sec).

Another advantage of xApps and rApps compared to the more traditional SON applications is their flexibility in terms of portability. After minimal adjustment they may be rolled out quickly in a different CSP environment, making app development clearly more cost-effective.

From a business perspective, we can identify three major players in the OpenRAN applications arena:

• the CSP as a xApp/rApp consumer
• the RIC app-hosting provider (typically with a global presence, it may also be a telecom equipment provider)
• the xApp/rApp vendor specialist selling to the CSP through the RIC provider

Of course, other combinations are possible, but at Future Connections we believe the last option is the one capable of offering the best service-value to CSPs, as it leverages the knowledge and experience of a RIC-based solutions specialist developer like us.

Looking at the xApps and rApps ecosystem, we have observedthat many of the network management and optimisation use cases are well served by rApps, where time constraints are not critical, leaving xApps usage for time-bound niche use cases.

It is important to note that new RIC-based applications should be more than just a mere translation of those use cases previously developed for a SON. Rather, they should be a scalable and coherent suite of applications integrating a monitoring layer as a key element, but also incorporating into the new app algorithms an AI/ML layer. The use of AI/ML brings unique value to CSPs, since it allows to issue a set of network recommendations before a potentially performance-impacting situation may take place.

Finally, the xApps and rApps must also include use cases focused on technically complex areas. Examples could be sophisticated AI-driven energy saving solutions targeting CSP’s cost efficiency, or solutions boosting customer experience. Here, again, the use of AI/ML is key to anticipating customer pain points and to implementing autonomous fixes in a full closed-loop mode. A proper customer experience booster application must also find the sweet spot between Customer Experience Index and Service Experience Index so that both customer and operator benefit.