Requirement Description
The requirement is to
- discover the RAN and Core endpoints at NSMF
- auto-populate the Core and RAN endpoints in the TN Slice Profile Screen (UUI)
- discover the endpoints of CU, DU & RU nodes at NSMF
All these endpoints are required as an input to TN NSSMF to create the logical links that denotes back-haul, front-haul and mid-haul interfaces. Endpoint consists of IPAddress, logicInterfaceID and nexthopinfo.
Note:
a. Core, RAN endpoints for back haul are manually entered in UUI and other RAN nodes endpoints for FH and MH are predefined values in the previous releases.
b. RAN endpoint for back haul will be covered in this release
c. Core endpoint, FH and MH endpoints are stretch goal
d. Core endpoint cannot be populated in UUI, as the IP address of CNFs are available after slice allocation. (Deviation of #2 in Requirement Description)
Back-haul endpoints Discovery:
This involves finding the EP (endpoint) details of RAN (CUCP) and Core (AMF) .
RAN Node (CUCP) EP details:
IP Address & NexHopInfo
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFoaWxhIFAiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQWhpbGEgUCIsImxhbmd1YWdlIjoiZW4iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiIxMTc3NDA1OTkiLCJkaWFncmFtTmFtZSI6IlBvcHVsYXRlIENVQ1AgSVAgYWRkcmVzcyIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJEeW5hbWljIERpc2NvdmVyeSBvZiBSQU4gXHUwMDI2IENvcmUgZW5kcG9pbnRzIGF0IE5TTUYiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjExNzc0MDU4OCwiZWRpdGFibGUiOmZhbHNlLCJjZW9JZCI6MTE3NzQ0NjgxLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjozLCJtYWNyb0lkIjoiODFhMjM0NTYtYTMyNi00MmY5LTgyNmYtYWM3OGViNzhkOWM2IiwicHJldmlld05hbWUiOiJQb3B1bGF0ZSBDVUNQIElQIGFkZHJlc3MucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjY5MSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTY0MzI5MTgxNzAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
IP Address:
More than one CUCP can be applicable and can be configured for a slice.
The returned IP addresses should be populated in a list box and all the IP addresses should be chosen as an input to TN NSSMF.
UUI should display a warning and should not allow to the next page, if all the IP addresses are not selected.
The details should be populated in UUI on loading the page.
AN endpoint - nexthopinfo:
NextHopInfo is stored in AAI and it is stored at the time of Simulator Registration with ESR. The nexthopinfo information will be retrieved from AAI and populated in UUI.
NextHopinfo is same for more than one network Functions. This value is going to be populated in text box as before.
The value should be populated in UUI on load of the page.
API Details
- UUI ↔ SO
MOCK SCREENS FOR UUI ENHANCEMENTS:
AutoPopulate nodes for multiple selection in UUI as below,
If all the nodes are not selected it should show the below error message,
Multiple selection of nodes in TN selection page, the selected nodes should be displayed as below,
API exposed by SO:
Get AN &CN EndPoints
Method | URL |
|---|
| POST | /onap/so/infra/3gppservices/v1/QueryEndPointInfo |
Request Example:
{
"subnetType": [
"AN",
"CN"
],
"coverageAreaTAList": "Beijing;Beijing;HaidianDistrict;WanshouluStreet"
}
Response Example:
{
"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": ""
}
}
}
2. SO ↔ CPS
3. SO ↔ SDNC
4. SO ↔ AAI
API Used:
To Fetch PNF's:
https://<ip-address>:<port>/aai/v23/network/pnfs
Response from AAI:
{
"pnf": [{
"pnf-name": "networkId-providerId-10-clientId-0-topologyId-2-nodeId-10.1.1.3",
"pnf-id": "10.1.1.3",
"in-maint": true,
"spare-equipment-indicator": false,
"resource-version": "1642530553170",
"admin-status": "up",
"operational-status": "up",
"relationship-list": {
"relationship": [{
"related-to": "esr-thirdparty-sdnc",
"relationship-label": "org.onap.relationships.inventory.AppliesTo",
"related-link": "/aai/v23/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/7cfa0c7c-0181-4181-8f3b-1edf20a0f47b",
"relationship-data": [{
"relationship-key": "esr-thirdparty-sdnc.thirdparty-sdnc-id",
"relationship-value": "7cfa0c7c-0181-4181-8f3b-1edf20a0f47b"
}]
}, {
"related-to": "network-resource",
"relationship-label": "tosca.relationships.network.LinksTo",
"related-link": "/aai/v23/network/network-resources/network-resource/providerId-10-clientId-0-topologyId-2",
"relationship-data": [{
"relationship-key": "network-resource.network-id",
"relationship-value": "providerId-10-clientId-0-topologyId-2"
}],
"related-to-property": [{
"property-key": "network-resource.network-id",
"property-value": "providerId-10-clientId-0-topologyId-2"
}]
}]
}
}]
}
To Fetch p-interface from AAI:https://<ip-address>:<port>/aai/v23/network/pnfs/pnf/networkId-providerId-10-clientId-0-topologyId-2-nodeId-10.1.1.3/p-interfaces
Response from AAI:
{
"p-interface": [{
"interface-name": "networkId-providerId-10-clientId-0-topologyId-2-nodeId-10.1.1.3-ltpId-512",
"speed-value": "10000000",
"resource-version": "1642530553011",
"in-maint": true,
"operational-status": "up"
}, {
"interface-name": "networkId-providerId-10-clientId-0-topologyId-2-nodeId-10.1.1.3-ltpId-1000001",
"speed-value": "10000000",
"resource-version": "1642530553011",
"in-maint": true,
"operational-status": "up"
}]
}
- The interface name of the fetched p-interface will be the nextHopInfo of the endpoints.
AN endpoint - logicInterfaceID:
As specified in TS 28 541, this field could be a VLAN ID (See IEEE 802.1Q [39]), MPLS Tag or Segment ID. This will be some predefined value in SO to denote the VLAN Id.
