Overview
For every new shareable slice creation request, OOF checks whether any existing slice can be reused.
OOF selects the suitable NSI/NSSI for reuse based on the resource utilized for the existing slices. To decide the reusability of slices, it needs to know the remaining capacity available for those slices.
OOF depends on DCAE (Slice Analysis MS) for the relevant details.
Slice analysis MS in turn requests DES (Data Exposure Service) for the PM data for a specific time interval, converts it into configuration data, aggregates the configuration data for the slices and returns it back to OOF.
With this current configuration data, OOF further checks against the actual requirements of these slices from the service/slice profile and finds the occupancy level.
The interface details between OOF and Slice Analysis MS are below.
API Definition
Get utilization of Slices
Interface definition | Description |
---|---|
Content-Type | application/json |
Operation | GET |
URI | /api/v1/slices-config |
Request Body
Attribute | Required | Type | Description |
---|---|---|---|
sliceIdentifiers | Y | List<String> | Identifier for the specific type of slices |
configParams | Y | List<String> | configuration fields expected from Slice Analysis MS |
Response Codes
Code | Description |
---|---|
200 | Data returned successfully |
400 | Bad Request (Error in request attributes) |
500 | Internal server error |
Response Body
Attribute | Required | Type | Description |
---|---|---|---|
sliceConfigResponse | Y | SliceConfigResponse | Response body containing the configuration details for the requested slices |
SliceConfigResponse - Sample Response
{ "sliceConfigDetails": [{ "sliceIdentifier": "5d9b3293-fa20-4776-bb41-92ba5e384419", "aggregatedConfig": { "dLThptPerSlice":27, "uLThptPerSlice":30, "maxNumberOfConns":300 } }, { "sliceIdentifier": "e316f4b2-01fa-479a-8522-64fe9c0c2971", "aggregatedConfig": { "dLThptPerSlice":40, "uLThptPerSlice":25, "maxNumberOfConns":400 } }] }