Open RAN (O-RAN) Architecture and RAN Intelligent Controller (RIC)

The architecture of Open RAN allows flexibility in deployment. The RAN Intelligent Controller (RIC) developed by the O-RAN Alliance is intended to enable AI/ML-based access to the elements in the radio network. You'll learn about the details of RIC, including the split onto Near-Real-Time RIC (Near-RT RIC) and Non-Real-Time RIC (Non-RT RIC), along with the O-RAN Alliance-defined interfaces related to both, namely E2 and A1.
In this webinar, we cover the following topics:
✔︎ O-RAN definitions and entities
✔︎ O-RAN architecture and deployment options
✔︎ RAN Intelligent Controller (RIC)
✔︎ Near-RT RIC and E2
✔︎ Non-RT RIC and A1
Join dr Marcin Dryjanski of Rimedo Labs on a webinar delivered at the Intelefy platform on "O-RAN Architecture and RIC".
Download our O-RAN whitepaper:
www.rimedolabs.com/blog/the-o...
You can find more technical content on wireless, O-RAN, 5G, and beyond on our blog:
* www.rimedolabs.com/blog/priva...
* www.rimedolabs.com/blog/3gpp-...
* www.rimedolabs.com/blog/intro...
You can check out the Intelefy University: courses.intelefy.com/
#ORAN​ #OpenRAN #5G​ #allthingswireless​ #knowledgesharing #PrivateNetworks #5GNR

[@SharpKnife523]

Excellent! Thank you!

[@joaogustavo5223]

thank you for the amazing explanation, it really helped.

[@RimedoLabs]

Thanks, we're glad it's helpful.

[@manishvyas172]

Very well explained Thanx a lot

[@ahmedelsabbagh4568]

Thanks a lot for your clarification, it was so helpful

[@RimedoLabs]

Thank you!

[@user-zg8kg1zw3i]

That was very well explained Thanks Alot!!. There was one description when if cloud fails and Near RT RIC is collapsed/disconnected, still E2 node should have default setting and network should work. But that would make our whole O-Cloud to collapse. Correct me if I am wrong!

[@RimedoLabs]

Thanks for the question. The point here is that the Near-RT RIC connection/functionality is broken. In addition, if the cloud infrastructure fails it only could fail where the RIC is deployed and that could be in a different place than the rest of the infrastructure.

[@thompsonlewis5972]

Awesome presentation! Is it possible to get the slide deck in in PDF format. When I view the slides it is quite blurry.

[@RimedoLabs]

Thanks, we're glad you like it. The slides are available under this link, after you subscribe to our newsletter: mailchi.mp/5cc584269396/w36l66fgmk

[@georgioskarouzos7418]

Very helpful! Would it be necessary a Conflict Mitigation function in Non-RT RIC to resolve conflicting requests from multiple rApps ?Thank you

[@RimedoLabs]

Thank you for your message. Conflict mitigation in Non-RT RIC is also currently being worked on in O-RAN WG2.

[@SharpKnife523]

Some vendors are talking about the relationship between Non-RT RIC and NWDAF. I am unsure how NWDAF can benefit Non-RT RIC for policy decisions on the Radio. NWDAF is generating analytics intelligence in the core mostly from the KPIs learned in the core (some KPIs are learned from OAM, but the integration piece is not defined). Will Non-RT RIC ultimately become some type of DAF like RAN-DAF that can offer RAN analytics to consumers in different domains like core?

[@RimedoLabs]

Yes, that is correct. There is a discussion to get interfaces between SMO or even Near-RT RIC to the NWDAF. I believe one of the important use case for this would be Network Slicing, where to get end-to-end SLA assurance this is beneficial.

[@victorlee9428]

@@RimedoLabs
MaxLinear just has issued a new open ran 5g SoC chip called “Sierra”.
A very powerful chip!!!!

[@yacineatroune]

Nice content but can't see what's being presented video quality very bad

[@RimedoLabs]

Thanks, we're glad that you find the content useful. The slides are available under this link, after you subscribe to our newsletter: mailchi.mp/5cc584269396/w36l66fgmk