SMO Integration with Network Functions Update
This presentation provides updates on the SMO integration with network functions, showcasing the status of various releases, solutions implemented, and identified gaps for improvement. It details the features implemented, such as support for the O1 interface, NETCONF client integration, and VES event handling. Feedback is welcomed for further enhancements in the upcoming releases.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
OSC: SMO integration with Network Functions Mahesh Jethanandani (PTL for SMO) 4th June 2021 1 1 Non-Juniper
SMO Status (D-release) 2 2 Non-Juniper
SMO O1 Solution NETCONF (Southbound) - Client (SMO) Establish session with NF(s) - Server (NF) Chosen by the vendor/implementor Interoperability testing RESTCONF (Northbound) 3 Non-Juniper
SMO O1/VES Solution SMO VES Collector Two part solution - VES Collector Time Series dB Elastic Search Capability A visualizer (Grafana) - VES Generator Content - Logs - Events Simulator (SIM) Format - Streaming data Generator Near-Real-Time RIC VES O-CU-CP E2 Generator E1 VES Pub O-CU-UP Generator VES F1-c E1 F1-u Generator O-DU VES Open Fronthaul Generator O-RU VES O-Cloud Logs/Events 4 Non-Juniper
SMO D release status D Feature Scope: Support for O1 interface Implementation of NETCONF client in SMO A minimal set of YANG models that demonstrate the capability of the O1 interface Support for O1/VES interface Demonstrate the capability to receive VES events, collect them in a dB, and display them in a dashboard. PTL: Mahesh Jethanandani Status: An implementation of the O1 interface has been checked into Gerrit. Check out this repo. It has been tested on Ubuntu Linux version 20.04. Feedback is appreciated on other versions and operating systems. An implementation of the VES interface based on schema version 7.2.1, with backward compatibility to 7.0, has been submitted into Gerrit 5 5 Non-Juniper
SMO Integration with NF (E-release) 6 6 Non-Juniper
What this presentation is SMO identifying gaps from its implementation - Config Management (CM) - Fault Management (FM) - Performance Management (PM) Commonly referred as Day 0 configuration and management - E.g. Configuring BGP on a router Gaps that are not tied to a particular feature or use-case Target November release 7 7 Non-Juniper
What this presentation is not Redefinition of the SMO architecture Redefinition of the O1 interface 8 8 Non-Juniper
Areas of Focus in D/F-release SMO implementation target - O1 - VES Other interfaces are targeted for future releases Interoperability between SMO and NF 9 9 Non-Juniper
Assumptions for E-release Network Functions (Near RT-RIC, O-CU, O-DU, O-RU) have been instantiated Topologically unknown 10 10 Non-Juniper
Config Management 11 11 Non-Juniper
Gaps IM/DM for Near RT-RIC How does a NF communicate with - SMO? - Other NF Over E2 Over E1 Over F1-c Over F1-u Open Fronthaul 12 12 Non-Juniper
How does a NF communicate with SMO? O-RAN-WG1.01-Interface specification Section 2.1.7 Notify Managed Object Instance Creation - How does MnS Provider know where the MnS Consumer is? Is it part of the initial configuration of the NF? 13 13 Non-Juniper
How do the NF communicate between themselves? E2 Nodes need to establish connection with Near RT-RIC. - How do they discover Near RT-RIC? 14 14 Non-Juniper
Fault and Performance Management 15 15 Non-Juniper
Minimum set of FM and PM identified by MVP-C FM - Subscription (per TS 28.545) https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/yang-models/_3gpp-common-subscription-control.yang (done) - Alarm Dictionary Session on June 8th proposal made and WG10 agreed needs to be converted into IM/DM https://oranalliance.atlassian.net/wiki/spaces/OAMWG/pages/1608155423/Machine-readable+Alarm+Dictionary - Notifications https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI/faultMnS.yaml notifyNewAlarm notifyChangedAlarm notifyClearedAlarm - VES Format PM - Subscription https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/yang-models/_3gpp-common-subscription-control.yang ) - Definitions and Template (per TS 32.404) https://oranalliance.atlassian.net/wiki/download/attachments/1608515800/PM-Counter-and-KPI-Repository.xlsx?api=v2 - Streaming https://forge.3gpp.org/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI/PerfDataStreamingMnS.yaml 16 16 Non-Juniper
Current Challenges Supporting many different types of Network Telemetry data (FM, PM, TCE, ) Supporting different formats and collection mechanisms for the different types: Many different dissemination methods Alarms, File pulls, Streaming Delays introduced by complexity of files - Pull model vs push model; Parsing deeply nested data structures Standardization of content Pre-validation of content 17 17 Non-Juniper
FM Alarm Dictionary Defines the framework for how alarms will be reported?? - Is the content of the alarm standardized? - What are the alarms each node has to support? - E.g. Is the Alarm Id for E2 Node Failure on Near RT-RIC the same as E2 Node Failure on O-CU? 18 18 Non-Juniper
Take away Definition and support of use-cases like network slicing is great - You cannot get there without basic plumbing SMO being able to communicate with each NF NF able to communicate with each other Common definition of alarm types Common definition of performance data that needs to be collected 19 19 Non-Juniper
Fault Monitoring as specified in TS 28.532 NETCONF/YANG based notification - Section 12.1.3 FM Subscription - NotifyNewAlarm - NotifyNewSecAlarm - NotifyClearedAlarm - NotifyChangedAlarm - NotifyChangedAlarmGeneral - NotifyChangedSecAlarmGeneral - NotifyCorrelatedNotificationChanged - NotifyAckStateChanged - NotifyPotentialFaultyAlarmList 20 20 Non-Juniper
