Use Case Overview & Description
The objective of this case is to develop an ONAP-based SON platform using the ONAP Optimization Framework (OOF). The use case focuses on the various information models and flows/interfaces between components to enable various SON functions to be realized. It also focuses on platform enhancements such as enhancements to the Control Loop framework (e.g., Control Loop Co-ordination, different types of targets for Control Loops, etc.), enabling ML-based SON, etc.
Use Case Key Information
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | |||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation |
| ||||||||
| Prior Project "Base" Wiki | Link to the Honolulu release page for this use case | |||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: N.K. Shankaranarayanan | |||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
|
BUSINESS DRIVER
Executive Summary
SON (Self-Organizing Networks) functionality is an essential part of existing 4G mobility networks, and will be even more critical for 5G. SON enables automation to improve network performance and efficiency, improve user experience, and reduce operational expenses and complexity. The objective of the OOF-SON (new name for OOF-PCI) use case is to develop an ONAP-based SON platform using the ONAP Optimization Framework (OOF). We have taken a phased approach since SON is complex, and SON for 5G is still evolving. We started with the Physical Cell Identity (PCI) optimization SON use case in Casablanca, then added some centralized Automated Neighbor Relations (ANR) aspects in Dublin. In Frankfurt, we addressed some enhancements such as basic CM-notify handling (as preparation for O-RAN alignment), adaptive SON, etc. In Guilin, we introduced use of AI/ML by onboarding an offline-trained ML-model to ONAP which will provide additional inputs to PCI optimization based on historical PM data, and stabilized the functionality in Honolulu. In Istanbul, we will align FM messages with relevant standards, move to new 3GPP NRM-based yang models and leverage CPS for RAN configuration.
...
There are no additional organizational management or sales strategies for this beyond whatever is required for ONAP deployment to support 5G.
Development Status
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||
| A&AI | No impact | ||||||||||
| AAF | No impact | ||||||||||
| APPC | No impact | ||||||||||
| CLAMP | No impact | ||||||||||
| CC-SDK |
| (Carryover work): Incorporate new Yang model in edit-config to RANSim. Stretch goal for processing CMNotify update. | |||||||||
| DCAE |
| Develop stndDefined VES message formats for FM/PM/CM. Stretch goal to modify SON-Handler MS and RAN-Sim for FM/PM. | |||||||||
| DMaaP | No impact | ||||||||||
| External API | No impact | ||||||||||
| HOLMES | No impact | ||||||||||
| MODELING | No impact, CPS related modeling aspects will be covered by CPS project | ||||||||||
Multi-VIM / Cloud | No impact | ||||||||||
| OOF | No impact | ||||||||||
| OOM | No impact | ||||||||||
| POLICY |
| No impact | |||||||||
| PORTAL | No impact | ||||||||||
| SDN-C | No impact | ||||||||||
| SDC | No impact | ||||||||||
| SO | No impact | ||||||||||
| VID | No impact | ||||||||||
| VF-C | No impact | ||||||||||
| VNFRQTS | No impact | ||||||||||
| VNF-SDK | No impact | ||||||||||
| CDS | No impact | ||||||||||
| CPS | Models, and interface to store/retrieve OOF SON use case related data |
...
*Each Requirement should be tracked by its own User Story in JIRA
USE CASE DIAGRAM
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
Use Case Functional Definitions
Use Case Title | Title of the Use Case |
Actors (and System Components) | The list of Actors and System Components that participate in the Use Case |
Description | Short overview of the Use Case |
Points of Contact | Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors. |
Preconditions | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed |
Triggers / Begins when | Describes the trigger for beginning the Use Case |
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced |
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced |
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case |
Related Use Cases | List of the Use Cases referenced by this Use Case |
Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
Supporting Files
| Date | Description | File |
|---|---|---|
| May 16, 2022 | Presentation given to Requirements Sub-committee | |
| June 6, 2022 | Presentation given to Requirements Sub-committee | |
| Control Loop Message Format | ||
| Nov 3, 2021 | ITU-T FG AN presentation on SON Use Case |
...