...
| JSON Viewer | ||||
|---|---|---|---|---|
| ||||
{
"name": "urllc_sample",
"files": {},
"limit": 10,
"num_solution": 5,
"timeout": 1200,
"template": {
"homing_template_version": "2018-02-01",
"demands": {
"URLLC": [{
"inventory_provider": "aai",
"inventory_type": "service",
"region": "RegionOne",
"attributes": {
"orchestration-status": "ACTIVE",
"global-customer-id": "5G-customer",
"modelInvariantId":"fda3c1e8-7653-4acd-80ef-f5755c1d3859",
"modelVersionId":"a6906768-1cae-4e78-acd1-d753ac61f3e8"
}
}]
},
"constraints": {
"service_profile_attr": {
"type": "attribute",
"demands": ["URLLC"],
"properties": {
"evaluate":{
"latency": {"lte" : "10 ms"},
"reliability": {"gte" : 99.999}
}
}
}
}
}
}
|
Illustrations
...
1. Call from SO to OOF to Get suitable NST
Inputs: Service Profile parameters
Assume Service Profile contains throughput =7, BW = 10, latency = 22.
Assume that the following NSTs are present in the inventory (at present maintained locally within OOF)
| NST id | Performance Attributes |
|---|---|
| NST1 | throughput, BW, latency |
| NST2 | reliability, user density |
| NST3 | throughput, BW, latency |
| NST4 | terminal density, survivability |
Based on above inventory, and attributes in service profile (not attribute values), (NST1, NST3) are shortlisted.
Attribute Policy contains the value ranges (capability set of each NST). For e.g.:
| NST id | Performance Attributes |
|---|---|
| NST1 | throughput (2..10), BW (5..10), latency (20..50) |
| NST2 | reliability (99.99..99.999), user density (10..10000) |
| NST3 | throughput (11..15), BW (10..25), latency (15..30) |
| NST4 | terminal density (100..5000), survivability (100..200) |
OOF selects NST3 by comparing the attribute value ranges with attribute values in service profile (it has only NST1 and NST3 to choose from).