Versions Compared

Key

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

The Base PCI (SON) Wiki is at: 5G - OOF and PCI (Casablanca carry-over items)

Weekly Meetings: OOF-SON Meetings 

Frankfurt demo was given at LFN DTF Virtual F2F Meetings on June 24, 2020:

SlidesOOF_SON_Frankfurt_demo_20200624_v2.0.pptx

Recordinghttps:/

...

/wiki.lfnetworking.org/download/attachments/40370243/ONAP_5G_OOF_SON_use_case_demo.mp4?api=v2


R5 El Alto Carry-over

Two Jira carry over items in SDN-C

...

  • Onboard RAN-Simulator as an official ONAP component (e.g., as part of Demo VNFs repo or Integration test repo),
  • Contribute to ConfigDB (or RuntimeDB) enhancements for SON use case (including any impacts in SON-Handler MS, OOF and SDN-C) => this scope currently only includes yang model driven automatic Config DB schema and API generation.

2. Alignment with O-RAN

  • Netconf config (O1-CM interface), yang model sourced from OIM => this is now de-scoped as we don't have yang models from O-RAN as of Jan 20th, 2020
  • VES messages for config-update notifications also => the scope only includes reception of DMaaP message by SDN-R that would be triggered when RAN sends a VES config-update message. The real VES message sending as well as reception by VES Collector in DCAE is de-scoped as we don't yet have the VES message definition from O-RAN.


3. Control Loop Co-ordination (CLC)
     Demonstrate CLC with PCI and ANR CLs

...

PROJECTPTLUser Story / EpicRequirement
A&AIEpic#1 - OOF/SON Enhancements

E1a: Models & relationship between Config, Operational DB & AAI

AAF

APPC


CLAMPEpic#1 - OOF/SON EnhancementsControl Loop Deployment
CC-SDK

Epic#1 - OOF/SON Enhancements

Enhance Yang model to align with 3GPP and O-RAN

Configuration/Operational Database, Config History (e.g. to revert changes)

RAN Simulator – enhance and include in ONAP codebase*

DCAE

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1888

Other impacts to be addressed in DCAE:

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1811

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1433

Java 11 migration (Stretch goal)

DMaaPNANo impact
External APINANo impact
Integration

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-1330


MODELINGNANo impact

Multi-VIM /

Cloud

NANo impact
OOF

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOPTFRA-616

Dynamic and static optimization, DMaaP interface, Harden the OOF features supporting SON
POLICY

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2162

Enhance the Policy functionality for Control Loop Coordination

PORTALNANo impact
SDN-C

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-1654

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-1796

Related O-RAN Jira: https://jira.o-ran-sc.org/secure/RapidBoard.jspa?rapidView=7&projectKey=OAM&view=detail&selectedIssue=OAM-9 

SDCNANo impact
SONANo impact
VIDNANo impact
VNFRQTSNANo impact
VNF-SDKNANo impact
CDSNANo impact

List of PTLs:Approved Projects


Test cases

No.DescriptionInvolved componentsStatus

1

Successful

storing of PCI and neighbor list data by SDN-C in Runtime DB

reception and handling of DMaaP message by SDN-R with CM notification (simulated from RAN).

DMaaP, SDN-R

NOT YET TESTED

2

Successful

fetching of PCI and neighbor list data from Runtime DB by SON-Handler MS

update of ConfigDB with CM notification updates by SDN-R (upon reception of CM notification over DMaaP from RAN)

SDN-R, DMaaP

NOT YET TESTED

3

Successful fetching of PCI and neighbor list data from Runtime DB by OOF

NOT YET TESTED

4Successful update of HO blacklist indication by SDN-C in Runtime DBNOT YET TESTED5Successfully bring RAN-Sim online and interface with SDN-C

Control Loop co-ordination – denial of 2nd control loop trigger (by Policy) received from SON-Handler MS when first control loop is active

SON-Handler MS, OOF, Policy, SDN-R, RAN-Sim

NOT YET TESTED

6

4

Control Loop

Co

co-ordination

scenario - e.g., defer a control loop until another one acting on the same PNF gets completedNOT YET TESTED7Successful interaction between SDN-C and RAN-Sim using the O-RAN aligned yang models

– re-submitting of 2nd control loop trigger (by SON-Handler MS) and initiating appropriate actions

SON-Handler MS, Policy, SDN-R, RAN-SimNOT YET TESTED
8

5

PCI optimization using AI/ML algorithm triggered from

Keep track of PCI updates being successfully implemented in the RAN and update DB accordingly for future optimizations.

SON-Handler MS
/OOF
, Policy, SDN-R, RAN-Sim

NOT YET TESTED

9Successful PCI control loop (regression but involving Runtime DB and AI/ML algorithm, RAN-Sim as part of ONAP repos)Successful ANR control loop (regression but involving Runtime DB, RAN-Sim as part of ONAP repos)

6

Trigger OOF for adaptive SON with FixedPCI cell list (by SON-Handler MS) when previous PCI updates are not implemented in the RAN

OOF, SON-Handler MSNOT YET TESTED
10

7

Yang-model based schema and API generation for ConfigDB (PoC only)

ConfigDBNOT YET TESTED

Detailed Impacts

Refer to the child wiki pages for the detailed impacts.

...