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
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 | ||||
---|---|---|---|---|
|
There is no change in SDC NSST design , also no change in the AAI slicing model
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
...