Versions Compared

Key

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

Our aim is to build an O-RAN specific Macro flow-based NSSMF which can integrate with an external NSMF.  Current ONAP slicing use case is using 3GPP 28.531 APIs (Slice-Specific APIs). In addition we would like to provide support for 3GPP 28.532 APIs (as per Generic Provisioning APIs based on Managed Object Instances (MOI))

To achieve this goal: we have made changes in SO , OOF component and have pushed additional policy using Policy Component. Also, SO macro flow is not integrated with OOF

Table of Contents

Prerequisite 

Create Policies required for NSSI selection

...

View file
namenssi_policies.zip
height150

Code Changes

Service Orchestration (SO) 

Code changes done in SO component  

SO api-handler 

new package ManagedObject3gppServiceInstances is created, highlights of the functionality:

  • Validate the request
  • Do service_recipe table lookup
  • Create infraActiveRequest in requestDB
  • Prepare ServiceInstanceRequest with new Resource = nssi

SO bpmn-infra

New module so-bomn-moi is created.

  • In WorkflowAction class: added new workflowType = NetworkSliceSubnet
  • New BPMN flows:
    • AssignRANNssiBB
    • ActivateRANNssiBB
    • ModifyRANNssiBB
    • DeleteRANNssiBB

...

View file
namedb_insert_scripts for (RAN NSSMF)Slicing Use Case.sql
height150

OOF

Existing OSDF APIs are not sufficient to support RAN NSSMF. Since, expectation is to select NSST at runtime. Hence a new API is added "selectNSST". 
NSST selection request from SO Macro flow to OOF

...

languagetext
titleSample NSST selection request
collapsetrue



There is no change in SDC NSST design , also no change in the AAI slicing model 

...