More Related Content
What's hot
What's hot (20)
Similar to Near rt ric tc
Similar to Near rt ric tc (20)
Recently uploaded
Recently uploaded (20)
Near rt ric tc
- 1. Near-RT RIC Training Course Nick Huang 1
- 2. Catalog • Overview • What is RIC? • Where is Near-RT RIC? • Why Near-RT RIC? • 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 : • 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
- 4. Where is Near-RT RIC ? 4
- 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. • xApps • Messaging infrastructure • Conflict mitigation • xApp subscription management • Management services • Security • Share Data Layer 6 The architecture of Near-RT RIC
- 7. The architecture in Near-RT RIC xApp • Data monitoring • Parameter adjustment Image Descriptor xApp 7
- 8. The architecture in Near-RT RIC Messaging infrastructure • Message interaction in Near-RT RIC • Low-latency, point-to-point • RMR(RIC Message Router) 8
- 9. The architecture in Near-RT RIC Conflict mitigation • overlapping • conflicting Direct Conflicts • Two/more xApps request different settings to a control target Indirect Conflicts • A xApp : antenna angle • B xApp : measurement deviation • They all affect the size of the boundary 9
- 10. The architecture in Near-RT RIC xApp subscription management • Manages subscriptions from the xApps to the E2 Nodes A xApp B xApp E2 Node E2 Node A xApp B xApp xApp subscription management E2 Node 10
- 11. The architecture in Near-RT RIC Management services • LCM(Life-Cycle Management) of xApp • FCAPS Management of Near-RT RIC 11
- 12. The architecture in Near-RT RIC Security • Prevent malicious third-party xApps from abusing radio network information. 12
- 13. The architecture in Near-RT RIC SDL(Share Data Layer) • It’s an API • Related to database • Stateless application processes 13
- 14. Interfaces • A1 • E2 • O1 14
- 15. Interfaces – A1 Non-RT RIC Near-RT RIC Policy-based guidance ML model management A1 • Between Near-RT RIC & Non-RT RIC 15
- 16. Interfaces – E2 • Between Near-RT RIC & E2 Nodes • E2 Nodes : • O-DU • O-CU CP/UP • O-eNB 16
- 17. E2 Interface Interfaces – E2 17
- 18. Interfaces – O1 • O1 • Between Non-RT RIC & other components • Supports Non-RT RIC to : • FCAPS management • Software management • File management 18
- 19. Interfaces - Comparation Interfaces Related Layer(from Near-RT RIC) Basic function A1 Non-RT RIC Policy-based guidance E2 E2 Nodes Support RAN function O1 Non-RT RIC Managements 19
- 20. • RIC Platform(RICPLT) • xApps(RICAPP) Components 20
- 21. Components 21
- 22. Components – Platform : Interface Terminations Report faults and events Report real-time Performance Management data O1 Mediator Receiving A1 policies issued by Non-RT RIC(HTTP) Sending A1 policy feedback to Non-RT RIC(HTTP) Communicate the payload to the certain xApp via RMR messaging. A1 Mediator Routing messages from the xApps through the SCTP connection to the E2 Node Communicate the payload to the certain xApp via RMR messaging. E2 Termination 22
- 23. Components – Platform : Managers E2M supports and records the states for each RAN. Includes : Null, Disconnected, Connected, Shutting-Down, Shut-Down E2 Manager Distributing routing policies 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 support Health check xApp Manager 23
- 24. Currents xApp(Cherry Release) • Admission Control(AC) xApp • HelloWorld demo(HW) xApps • KPI Monitor(KPIMON) xApp • QoE Prediction(QP) xApp • QoE Prediction-Driver(QPD) xApp • Anomaly Detection(AD) xApp • Traffic Steering(TS) xApp • ML-based xApp • Measurement Campaign(MC) xApp 24 Traffic Steering Use Case
- 25. Traffic Steering Use Case • Purpose : To maximize the QoE improvement(handover) 25 E2 Node Near-RT RIC E2 setup E2 Subscription E2 Indication
- 26. Message Flow 26 QP driver xApp QP xApp (8) RMR (QOE-PRED-REQ) TS xApp (9) RMR (QOE-PREDICTION) (5) RMR (A1 POLICY Create) RMR (TS_ANOMALY_UPDATE) RMR (TS_ANOMALY_ACK) (6) RMR (TS-UE-LIST) cell metrics UE metrics Query UE Signal Strength (7) Query UE and Cell data KPIMON Near RT RIC A1Med (1) E2 Setup Req/Resp (3) E2 Indication (2) E2 Subscription E2 SIM (10) Handover Decision (4) SDL Set E2 Term AD xApp
- 27. Thank you 27
Editor's Notes
- Based on the information from RAN, use ML or Analyze information
- According to different application scenarios, perform data monitoring and parameter adjustment of RAN functions. xApp descriptor that contains configuration data for the xApp
- The RIC Message Router (RMR) is a thin library which allows applications to send messages to other applications. RMR provides insulation from the actual message transport system, as well as providing endpoint selection based on message type.
- Resolves potentially overlapping or conflicting requests from multiple xApps
- Merge the identical subscriptions from different xApps into a single subscription to the E2 Node
- fault, configuration, accounting, performance, security
- Be used for storing and sharing any data to database Stateless : Reduce resource consumption
- The main message carried on the A1 interface is
- In order to realize Near-RT RIC's control of E2 Node, E2 Node will send some messages through E2 interface, such as: A, if Near-RT RIC needs to adjust parameters, it will first suspend the process and then issue related policies
- O1 termination communicates with non-rt ric through O1 interface and exposes O1-related management services from Near-RT RIC.
- Null : No RAN in DB Disconnected : connection failed, E2T dies or E2T initialized Connected : Get a setup request from remote RAN Shutting-Down/Shut Down : Tear down RAN connection ------------------------- It is responsible for distributing routing policies among the other platform components and xApps.
- To maximize the QoE improvement(handover) of the worst-performing priority traffic by intelligently controlling the traffic between multiple cells.