Overview
For every new shareable slice creation request, OOF checks whether any existing slice can be reused.
...
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 interface details between OOF and Slice Analysis MS doesn't exist and the details 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 |
Code Block | ||
---|---|---|
| ||
{
"sliceIdentifiers": [
"7e000ddc-7ba1-4fdb-a7ce-8f0a65ab3282",
"cb51e744-bfcf-4188-885a-e3e3c51ed53e"
],
"configParams": [
"dLThptPerSlice",
"uLThptPerSlice",
"maxNumberOfConns"
]
} |
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
...