2. Catalog
• Overview
• What
• Where
• Why
• Architecture
• Interfaces
• Components
• Currents xApps
• Traffic Steering Use Case
2
3. What is RIC ?
• RAN Intelligent Controller
• Non-Real Time RIC
• Near Real Time RIC
• Goal :
• Based on the information from RAN, use ML or Analyze
information to configure or control RAN.
Non-RT RIC Near-RT RIC
Get information from RAN
Create/Choose training model
A1
Policy
Follow the policy
Adjust RAN parameters 3
5. Why Near-RT RIC ?
Near-RT RIC
Network Intelligence
Resource Assurance
Resource Control
Policy Enforcement
Handover Management
Radio-Link Management
Advanced SON
Load Balancing
RAN Slicing
5
6. The architecture in Near-RT RIC
Messaging infrastructure
• Message interaction in Near-RT RIC
• Low-latency, point-to-point
• RMR(RIC Message Router)
6
7. The architecture in Near-RT RIC
Conflict mitigation
• Resolves potentially overlapping or
conflicting requests from multiple xApps
Direct Conflicts
• Two/more xApps request different
settings but the Control Target & parameters
& configuration are almost the same
Indirect Conflicts
• A xApp uses the parameters of the
antenna angle; B xApp uses the
parameters of the measurement
deviation. Although they do not affect
each other, they all affect the size of the
boundary.
7
8. The architecture in Near-RT RIC
xApp subscription management
• Manages subscriptions from the xApps to the
E2 Nodes
• Merge the identical subscriptions from
different xApps into a single subscription
to the E2 Node
A xApp B xApp
E2 Node E2 Node
A xApp B xApp
xApp subscription management
E2 Node8
9. The architecture in Near-RT RIC
Management services
• LCM(Life-Cycle Management) of xApp
• FCAPS Management of Near-RT RIC
9
10. The architecture in Near-RT RIC
Security
• Prevent malicious xApps from abusing
radio network information.
10
11. The architecture in Near-RT RIC
SDL(Share Data Layer)
• It’s an API
• Be used for storing and sharing any data
• Stateless application processes
11
12. The architecture in Near-RT RIC
xApp
• According to different application
scenarios, perform data monitoring and
parameter adjustment of RAN functions.
Image Descriptor
xApp
12
17. Interfaces – O1
• O1
• Between Non-RT RIC & other components
• Supports Non-RT RIC to :
• FCAPS management
• Software management
• File management
17
18. Interfaces - Comparation
Interfaces Related Layer Basic function
A1 Non-RT RIC Policy-based guidance
E2 E2 Nodes Support RAN function
O1 Non-RT RIC Managements
18
21. Components – Platform : Interface Agents
Responsible for the control messages /
return related information to O1
interface(HTTP), then communicate the
payload to the certain xApp via RMR
messaging.
O1 Mediator
Responsible for receiving A1 policies issued
by non-RT RIC(HTTP), and then
communicate the payload to the certain
xApp via RMR messaging.
A1 Mediator
Responsible for receiving information /
issuing control commands to E2 Node(SCTP),
then communicate the payload to the
certain xApp via RMR messaging.
E2 Termination
21
22. Components – Platform : Managers
E2M supports and records the states for
each RAN.
Includes : Null, Disconnected, Connected,
Shutting-Down, Shut-Down
E2 Manager
It is responsible for distributing routing
policies among the other platform
components and xApps.
Routing Manager
Manages the subscriptions and message
routing of the subscribed messages
between E2 Termination and xApps.
Subscription Manager
To deploy/undeploy xApps, record xApps
status and Health check
xApp Manager
22
24. Traffic Steering Use Case
• Purpose : To maximize the QoE improvement of the worst-
performing priority traffic by intelligently controlling the traffic
between multiple cells.
24
E2 Node Near-RT RIC
E2 setup
E2 Subscription
E2 Indication
