...
- Populate Core IP address
- Populate the KUD VM's IP address where the Core CNFs are instantiated
- To find KUD VM's IP address
- ??
- Populate logical interface id
- Default it to 45
- Populate next-hop-info
- Select one of the p-interfaces returned at 3.a (RAN endpoint section) as eligible UNI for core end
- Set this p-interface as Core Facing by updating the 'interface-role' of this UNI as 'Core-facing' in AAI. As per TS 28 531 Rel. 16 - Sec.7.3, it is the responsibility of the NSSMF to derive the requirements of TN network. So assign the interface-role at Core NSSMF.
NSSMF Workflow - WIP
API exposed by SO-NSSMF ADAPTER:
Method | URL |
---|---|
POST | {adapter-url}/api/rest/provMns/v1/NSS/QueryEndPointInfo |
Request Example:
JSON Viewer | ||
---|---|---|
| ||
{
"subnetType": [
"AN",
"CN"
],
"coverageAreaTAList": "Beijing;Beijing;HaidianDistrict;WanshouluStreet"
} |
Response Example:
JSON Viewer | ||
---|---|---|
| ||
{
"endPoints": {
"AN": {
"ipAddress": ["xx.xx.xx.xx", "xx.xx.xx.xx"],
"logicalInterfaceId": "12",
"nexthopInfo": ""
},
"CN": {
"ipAddress": ["xx.xx.xx.xx", "xx.xx.xx.xx"],
"logicalInterfaceId": "12",
"nexthopInfo": ""
}
}
} |