Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Weekly Meetings: OOF-SON Meetings 

For the Frankfurt/El Alto Release page, please see: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

For the Dublin Release page, please see:
Requirements and Test Cases: OOF-PCI Use Case - Dublin Release - ONAP based SON for PCI and ANR 

OOF-PCI Dublin Release Plan: 5G - OOF and PCI (Casablanca carry-over items)

For the Casablanca Release POC page, please see: Casablanca PoC 


Links to Other Pages/Documents:

Documentation files will be uploaded to this Dublin 5G Use Cases page:  5G Use Case (R4 Dublin)Overview (ppt): https://wiki.onap.org/download/attachments/29788530/OOF_PCI_proposal_v4_20180822.pptx?api=v2

SDN-R Documents page: SDN-R Documents

OOF Architecture page: OOF Casablanca (R3) Architecture Alignment

OOF-PCI API spec: PCI Optimization API

Details of PCI Handler microservice, RAN-simulator (ppt):
 https://wiki.onap.org/download/attachments/29788530/PCI_microservice_proposal_v6_Aug22_2018.pptx?api=v2

Policy Code Changes Planned: https://wiki.onap.org/download/attachments/29788530/5GUseCase_OOFPCI_Policy_Impacts_v_0_3.pdf?api=v2 

Casablanca OOF-PCI PoC Demo - Slides

https://wiki.onap.org/download/attachments/29788530/OOF_PCI_POC_Demo_20181213.pptx?api=v2 

Casablanca OOF-PCI PoC Demo - Call Recording

https://wiki.onap.org/download/attachments/29788530/ONAP%20Casablanca%20OOF-PCI%20Use%20Case%20POC%20Demo.mp4?api=v2

Dublin OOF-PCI PoC Demo - Slides

https://wiki.onap.org/download/attachments/68539437/OOF_PCI_Dublin_POC_Demo_20190724_v_2.0.pptx?version=1&modificationDate=1564034905299&api=v2

Dublin OOF-PCI PoC Demo - Call Recording

https://wiki.onap.org/download/attachments/68539437/zoom_0.mp4?version=2&modificationDate=1563985740000&api=v2



Older content for Casablanca PoC (Need to move Gliffy Diagram below)

PCI Optimization based on trigger from SDN-C (RAN Config Change)



Gliffy Diagram
nameOOF - PCI Optimization - RAN Config Change Copy Copy
pagePin3

Note: We had earlier discussed three PCI optimization scenarios (Flows A, B, C). For Casablanca, we are now focused on a minimum viable product which is based on Flow B. The earlier content has been moved to this page ( 5G - PCI (Physical Cell ID) Optimization ) under OOF R3 Planning.

Introduction

  • ONAP Optimization Framework (OOF) provides a policy-driven and model-driven framework for creating optimization applications for a broad range of use cases

  • For Casablanca, OOF enhancements include formulation and solving of optimization problems

  • We propose an OOF enhancement and Proof of Concept (POC) for Casablanca for Physical Cell ID (PCI) Optimization

    • PCI Optimization is a well-understood problem

    • The reading/writing of the Physical Cell ID (PCI) configuration parameter has been included in SDN-C POC work

  • The objective of the POC is to demonstrate disaggregation of the PCI SON functionality, and the data flows needed to implement this in ONAP using OOF

  • We envision a new PCI-Handler Microservice to facilitate the data flow and trigger mechanism

  • The focus of the POC is on data flow and interfaces, and the role of OOF, PCI-Handler-MS, SDN-C Controller and Policy

    - Objective is to incorporate an algorithm in ONAP using OOF, not to develop an algorithm

Casablanca Plan

  • Minimum viable product to make incremental progress in ONAP core modules

  • Develop new PCI Handler microservice and ONAP interfaces and flows needed:

    • (a) to get the required network data to OOF for optimization

    • (b) compute an optimization

    • (c) apply policies

    • (d) execute it using the Controller

  • Casablanca test cases involve:

    • New PCI-Handler-MS (onboarded on DCAE) – interfaces to OOF, Policy, DMaaP

    • OOF – interfaces to PCI-Handler-MS, Policy, SDN-C, (A&AI?)

    • Policy – interface to PCI-Handler-MS, OOF, SDN-C

    • SDN-C – interface to RAN emulator, OOF, Policy, DMaaP

PCI Optimization based on trigger from SDN-C (RAN Config Change)

Gliffy Diagram
namePCI Optimization Flow 3 - RAN Config Change
pagePin16

Steps

...

Step

...

Config change notification

RAN sends notification to SDN-C (e.g. Nbr list change)

...

Publish config data change

SDN-C publishes config data change on DMaaP. Subscribed by PCI-Handler-MS, A&AI (and others).

...

Fetch configuration policies

PCI-Handler MS fetches policies that specify how PCI-Handler-MS will respond to triggers or requests from SO, from DCAE (via DMaaP), SDN-C) (via DMaaP),

PCI-Handler-MS analyzes config change to detect pre-defined signature which will trigger PCI Optimization due to config changes (e.g. Nbr list)

...

Request for PCI optimization for network region.

PCI-Handler MS invokes OOF for pre-defined workflow for PCI Optimization via REST API.This call includes data for the cell and the network reqion involved.

...

Fetch PCI optimization policies

OOF fetches policies that specify how OOF will execute PCI optimization in response to PCI request for optimization

...

Fetch Config data for cells in the region

OOF fetches PCI and Nbr List config data for cells in network region from SDN-C

...

Fetch Inventory data for cells in the region

OOF fetches inventory and topology of cells in network region from AAI

...

Recommended PCI configuration

OOF provides PCI recommendation to PCI-Handler-MS in response to the request from

...

Recommended PCI configuration

PCI-Handler-MS provides PCI recommendation to Policy

...

PCI Configuration decisions

Policy sends message to SDN-C with instruction for configuration changes

...

Change PCI Configuration

...