...
- 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
- Following test cases are for an OOF 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 SDNC(R) POC - 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, SDNC(R) Controller and Policy etc
- Objective is to incorporate an algorithm in ONAP using OOF, not to develop an algorithm
- The POC will help to develop details of ONAP interfaces and flows needed:
(a) to get the required network data to OOF for optimization,
(b) determine the recommended reconfiguration, and
(c) execute it using the Controller
Sequence Flows for OOF based PCI Optimization based on 3 different triggers:
(Flow 1) - From SO (new cell addition),
(Flow 2) - From SDNC(R) (RAN config change)
(Flow 3) - From DCAE (fault)
Flow 1: PCI Optimization for trigger from SO (new cell addition)
Gliffy Diagram | ||||
---|---|---|---|---|
|
Functionality per component for common flows (after PCI trigger). See Flow 2, RAN Config change
Step | Component | Functionality | User Stories |
---|---|---|---|
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), SDNC(R) (via DMaaP), | |
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, AAI | Fetch Inventory data for cells in the region OOF fetches inventory and topology of cells in network region from AAI | |
8b | OOF, SDNC(R) | Fetch Config data for cells in the region OOF fetches PCI and Nbr List config data for cells in network region from SDNC(R) | |
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, SDNC(R) | PCI Configuration decisions Policy sends message to SDNC(R) with instruction for configuration changes | |
12 | SDNC(R), RAN | Change PCI Configuration SDNC(R) applies config changes | |
13 | SDNC(R), AAI | Update Inventory SDNC(R) updates inventory as needed for PCI config change |
Flow 2: PCI Optimization for trigger from SDNC(R) - RAN Config Change
Gliffy Diagram | ||||
---|---|---|---|---|
|
Flow 3: PCI Optimization for trigger from DCAE (Alarm/fault)
Gliffy Diagram | ||||
---|---|---|---|---|
|