APIs from NSMF to NSSMF Adaptor
1. (Re) Configure NSSI API
...
Interface Definition
...
Description
...
Content-Type
...
application/json
...
Operation Type
...
POST
...
URI
...
https://{adapter-url}/api/rest/provMns/v1/NSS/ConfigureNSSI
1.1. Request
| Code Block |
|---|
{
"configureNSSI": {
"nssiId": "NSSI-C-001-HDBNJ-NSSMF-01-A-ZX",
"nssiName": "eMBB-001",
"sliceProfile": {
"snssaiList": [
"001-100001"
],
"sliceProfileId": "ab9af40f13f721b5f13539d87484098",
"plmnIdList": [
"460-00",
"460-01"
],
"perfReq": {
"perfReqEmbbList ": [
{
"activityFactor": 50
}
]
},
"maxNumberofUEs": 200,
"coverageAreaTAList": [
"1",
"2",
"3",
"4"
],
"latency": 2,
"resourceSharingLevel": "non-shared"
},
"nsiInfo": {
"nsiId": "NSI-M-001-HDBNJ-NSMF-01-A-ZX",
"nsiName": "eMBB-001"
},
"scriptName": "CN1",
"extension": {
"XXX": "XXX"
}
},
"esrInfo": {
"vendor": "ONAP",
"networkType": "core"
}
}
|
1.2. (Synchronous) Response
To be filled
2. Sub-net Capability query: NSMF -> NSSMF (AN, TN, CN)
...
Interface Definition
...
Description
...
Content-Type
...
application/json
...
Operation Type
...
POST
...
URI
...
https://{adapter-url}/api/rest/provMns/v1/NSS/subnetCapabilityQuery
2.1. Request
Request can contain the sub-net type. 1 request can be used to fetch capabilities of more than 1 subnet managed by the same NSSMF - for e.g., in case of Transport, a single request can fetch the capabilities of FH, MH and BH subnets managed by the same TN NSSMF.
| Code Block |
|---|
{
"subnetCapabilityQuery": {
"subnetTypes": {TN-FH, TN-MH}
}
},
"esrInfo": {
"vendor": "ONAP",
"networkType": "transport"
}
} |
2.2. (Synchronous) Response
To be filled
Response can be a json blob (or parameter list) containing a minimum set of relevant attributes such as the below (based on 3GPP TS 28.541):
...
Attribute
...
AN
...
CN
...
TN
...
Latency
...
Yes
...
Yes
...
Yes
...
maxNumberofUEs
...
Yes
...
maxNumberofConns
...
Yes
...
Max Throughput
...
Yes
...
Yes
...
Yes
...
Terminal density
...
Yes