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
Reference wiki link: Optimization Policy Creation Steps This page has explained "policies" well. To add support for NSSI , please keep "nssi_policies" folder from the zip in "policies" folder
The new zip file to create NSSI policies
View file | ||||
---|---|---|---|---|
|
Code Changes
Service Orchestration (SO)
Code changes done in SO component component
SO api-handler
new package ManagedObject3gppServiceInstances is created, highlights of the functionality:
...
SO catalogDB View file name db_insert_scripts for (RAN NSSMF)Slicing Use Case.sql height 150
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
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
curl --location --request POST 'https://{{k8s}}:30248/api/oof/v1/selection/nsst' \ --header 'Content-Type: application/json' \ --header 'Authorization: Basic dGVzdDp0ZXN0cHdk' \ --header 'Cookie: JSESSIONID=8873161B92F94EA8FA15E5E87108B76F' \ --data-raw '{ "requestInfo": { "transactionId": "c86b3019-39f4-4cd3-b847-b22afe9f36dc", "requestId": "c86b3019-39f4-4cd3-b847-b22afe9f36dc", "sourceId": "so", "timeout": 600, "callbackUrl": "http://0.0.0.0:9000/callback/" }, "sliceProfile": { "latency" : 20, "areaTrafficCapDL" :800 } }' |
Policy
...