.

1. RIC

2. What is RIC?
• RIC: RAN Intelligent Controller
• Near-RT RIC
• Non-RT RIC
• (Near-RT RIC is response quicker (<=10^-3 seconds),than Non-RT RIC(1
second))
Why need near-RT RIC?
• There will be a lot of RANs connect to RIC , so we need Near-RT RIC to
configer and conrtol these RANs.

3. Overview structure -1
 E2 nodes:
• O-eNB
• O-CU-CP
• O-DU
 RAN:
• O-eNB
• O-CU-CP
• O-DU
• O-RU

4. How it work of A1 & E2 interface ?
Step1 get RAN imformaton
Step2 design or create the ML module
Step3 translate the A1 policy
Step4 check the information in E2
nodes is in the range of A1 policy or not
Step5 near RT RIC change the
parameter of E2 nodes.
Non RT RIC
Near RT RIC
E2 nodes
A1
E2

5. Detail in E2 interface
Non RT RIC
Near RT RIC
E2 nodes
A1
E2

6. Overview structure
• Terminatons
• O1 mediator
• A1 mediator
• E2 termination
• xAPPs
• xApp image
• xApp descriptor

7. Overview structure • Messaging Infrastructure
• Interacton in RIC
• Low latency use RMR
• Conflict Mitigation
• Direct Conflict
• Indirect Conflict

8. Overview structure
• xAPP Subscription Management
• Management services
• Implement Life cycle managemen
(of xAPPs)
• FCAPS mangements (of near RT

9. Overview structure
• Security
Avoid malicious xAPPs use too much
information
• SDL (Share database layer)

10. Detail structure

11. • E2 Manager
• Routing Mager

12. Concept vs. details