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!
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.
Hello Mr Dryjanski. Please provide me clarifications on the following : i) Are all new radio units self-configured by Non-RT RIC through Open FH M-plane interface ? ii) Are capacity resources assigned to E2 nodes by SMO through O2 interface ? Thank you
Thanks for your question. To our knowledge, A1 seems to look as a "one way interface" - i.e., policy, ML models and Enrichment Information (EI) going from Non-RT RIC to Near-RT RIC. The other side is simply responding with e.g., policy status, or requesting certain information (EI).
Hello Mr Dryjanski. Based on your recommended blog post regarding O-RAN deployment, for low latency(URLLC) the O-CU shall be deployed closer to the user, which requires realizing it along with O-DU in the edge cloud. a) I assume that in the edge cloud there will be also a UPF and DNN. Is it correct ? b) Would it be more beneficial-from latency of data processing point of view-to consider the O-DU in the cell site rather than in edge cloud? Thank you
The short answer is yes, but for the latency considerations and user plane delay, we recommend you to go directly to the O-RAN specification on this matter, namely: "O-RAN Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN 8.0" (more specifically, chapter 5.2.1 and the text around it). You can download it from here: specifications.o-ran.org/specifications.
Hello Mr Dryjanski. Given that O-Cloud can host the O-RAN functions near-RT RIC (along with xApps) and O-DU means that it is considered as an edge-Cloud. For the O-CU-CP and O-CU-UP functions another O-Cloud is used, which is considered as central-Cloud. Is it correct ? Thank you
Thank you for the question. There are various options considered by O-RAN for deployment of the particular function. You can find those and the details in one of our blog posts: rimedolabs.com/blog/o-ran-deployment-scenarios/
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?
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.
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
great session
thank you for the amazing explanation, it really helped.
Thanks, we're glad it's helpful.
Excellent! Thank you!
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!
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.
Very well explained Thanx a lot
Thanks a lot for your clarification, it was so helpful
Thank you!
Hello Mr Dryjanski. Please provide me clarifications on the following : i) Are all new radio units self-configured by Non-RT RIC through Open FH M-plane interface ? ii) Are capacity resources assigned to E2 nodes by SMO through O2 interface ? Thank you
Thank you for the question. For both, the answer is: they may be configured using those interfaces.
Very helpful! Would it be necessary a Conflict Mitigation function in Non-RT RIC to resolve conflicting requests from multiple rApps ?Thank you
Thank you for your message. Conflict mitigation in Non-RT RIC is also currently being worked on in O-RAN WG2.
Hello Mr Dryjanski. Is it possible the database in near-RT RIC to provide data/feedback to Non-RT through A1 interface?
Thank you
Thanks for your question. To our knowledge, A1 seems to look as a "one way interface" - i.e., policy, ML models and Enrichment Information (EI) going from Non-RT RIC to Near-RT RIC. The other side is simply responding with e.g., policy status, or requesting certain information (EI).
Hello Mr Dryjanski. Based on your recommended blog post regarding O-RAN deployment, for low latency(URLLC) the O-CU shall be deployed closer to the user, which requires realizing it along with O-DU in the edge cloud. a) I assume that in the edge cloud there will be also a UPF and DNN. Is it correct ? b) Would it be more beneficial-from latency of data processing point of view-to consider the O-DU in the cell site rather than in edge cloud? Thank you
The short answer is yes, but for the latency considerations and user plane delay, we recommend you to go directly to the O-RAN specification on this matter, namely: "O-RAN Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN 8.0" (more specifically, chapter 5.2.1 and the text around it). You can download it from here: specifications.o-ran.org/specifications.
Hello Mr Dryjanski. Given that O-Cloud can host the O-RAN functions near-RT RIC (along with xApps) and O-DU means that it is considered as an edge-Cloud. For the O-CU-CP and O-CU-UP functions another O-Cloud is used, which is considered as central-Cloud. Is it correct ? Thank you
Thank you for the question. There are various options considered by O-RAN for deployment of the particular function. You can find those and the details in one of our blog posts: rimedolabs.com/blog/o-ran-deployment-scenarios/
@RimedoLabs Thank you very much for your valuable feedback
Awesome presentation! Is it possible to get the slide deck in in PDF format. When I view the slides it is quite blurry.
Thanks, we're glad you like it. The slides are available under this link, after you subscribe to our newsletter: mailchi.mp/5cc584269396/w36l66fgmk
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?
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.
@@RimedoLabs
MaxLinear just has issued a new open ran 5g SoC chip called “Sierra”.
A very powerful chip!!!!
Nice content but can't see what's being presented video quality very bad
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