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)
Steps
Step | Component | Functionality | User Stories |
|---|---|---|---|
| 2 | Policy, PCI-Handler-MS, OOF, SO, SDN-C, AAI, DCAE Collector | Modules loaded with changes for PCI Optimization | |
| Run time | |||
| 3(b) | RAN, SDN-C | Config change notification RAN sends notification to SDN-C (e.g. Nbr list change) | |
| 4(b) | SDN-C | Publish config data change SDN-C publishes config data change on DMaaP. Subscribed by PCI-Handler-MS, A&AI (and others). | |
| 5 | PCI-Handler-MS, Policy | 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) | |
| 6 | PCI-Handler-MS, OOF | 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. | |
| 7 | OOF, Policy | Fetch PCI optimization policies OOF fetches policies that specify how OOF will execute PCI optimization in response to PCI request for optimization | |
| 8a | OOF, SDN-C | Fetch Config data for cells in the region OOF fetches PCI and Nbr List config data for cells in network region from SDN-C | |
| 8b | OOF, AAI | Fetch Inventory data for cells in the region OOF fetches inventory and topology of cells in network region from AAI | |
| 9 | OOF, PCI-Handler-MS | Recommended PCI configuration OOF provides PCI recommendation to PCI-Handler-MS in response to the request from | |
| 10 | PCI-Handler-MS, Policy | Recommended PCI configuration PCI-Handler-MS provides PCI recommendation to Policy | |
| 11 | Policy, SDN-C | PCI Configuration decisions Policy sends message to SDN-C with instruction for configuration changes | |
| 12 | SDN-C, RAN | Change PCI Configuration SDN-C applies config changes |