Page 2 of 113. Showing 1,122 results (0.042 seconds)
Anomaly Detection Use Case
Introduction: Anomaly Detection (AD), QoE Predictor (QP) and Traffic Steering xApp's are three components in Anomaly Detection use case in Near RT RIC … for end to end testing of AD use case Names of the xApp to be deployed must match with what the on-boarder has AD uses message types TS_ANOMALY_UPDATE to sendNetwork Slicing Use Case
Table of Contents Sub pages The O1 Simulator offers support for demonstrating the O-RAN-SC E-Release Network Slicing use case proposed by Radisys … to start a simulated O-DU and how to use the Network Slicing use case features are below. A video demonstrating these capabilities was presented in this meeting0. Closed Loop Use Case Symbology
, existing, an to be developed messages. End note TEST –[#red]> SMO : Test Message SMO -> NF1 : Existing Message NF1 –[#blue]>> SMO : Message Implemented for Use Case … @startuml Autonumber Skinparam sequenceArrowThickness 2 Skinparam sequenceArrowColor Black skinparam ParticipantPadding 5 skinparam BoxPadding 10 Title “UseNetwork Slicing Use Case v2.pptx
Network Slicing Use Case September 24, 2021 Introduction Network Slicing Use Case Configuration Management/Monitoring O-DU rApp [1.1] O1 to send Slice … Will subsequently reconfigure the PRB resources Will use _3gpp-nr-nrm-nrcelldu.yang for Cell/slice configuration SMO will publish OpenAPI for this YANG modelUse case driven YANG modules for O-DU
Scope The page will discuss and document the necessary yang modules to be supported by O-DU to ensure the end-to-end functionality of the D-Release use case … on 2021-03-04 it was decided to create a yang modules for O-RAN-SC DU with a minimum parameter set supporting the D-Release Closed loop use case. The initial ideaRun Apex Policy for O-RU & O-DU use case
This page describes how to run the stand-alone ONAP policy framework and deploy the apex policy designed for O-RU and O-DU use case. Assumption … & O-DU use case All the ingredients of apex policy designed for O-RU & O-DU use case are available here: cd nonrtric/test/usecases/oruclosedlooprecoveryRelease G: Automation Composition for O-DU Slice Assurance use case
the complete ONAP installation done via OOM. This use case is created using Kubernetes participant available in ONAP The use case implementations are located … for this use case. Instructions for the SMO installation can be found here https://wiki.o-ran-sc.org/display/RICNR/Release+G%3A+Policy+Clamp+installationRun microservice script for O-RU & O-DU use case
Prerequisits The following need to be installed to run the script according to these instructions: Docker Kubernetes Helm 3 Run To run the script for the O-RU & O-DU Closed Loop Recovery use case with necessary simulators, download the repo (defaults to master branch): git cloneUse Case Epics and Associated User Story Itemization (DRAFT - Work In Progress)
These pages list the proposed epics for this use case, also providing some user story descriptions to help illustrate the content of each epic. These epics are divided into Execution Time, Deployment Time and Training Time categories.2020-02-27 Meeting notes - E2 Simulator enhancements for Traffic Steering use case
to support Traffic Steering use case Discussion items Time Item Who Notes 5min E2 Simulator current status @all Current E2 Simulator capabilities: setup subscription indication 5min Enhancing E2 Simulator @all Before specific enhancements for Traffic Steering use case: WG3 alignment