| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Requirement Description
The requirement is to
...
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
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
...
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
General Information:
RAN and Core NF's IP addresses are assigned as below:
- If the NFs are deployed as VNFs, VNFM takes care of the IP address assignment
- If the NFs are deployed as CNFs, Kubernetes assigns a unique IP address to the pod. If it is a single container, docker daemon itself acts as a DHCP server and assigns an IP address to the container.
In both the above cases, assigning an IP address is taken care by the cloud provider itself.
In Core Slicing, netbox-ip-assign microservice is used by SDNC to assign IP address to the VF modules and VNFs. But this is not used effectively by CDS and the multicloud. Kubernetes itself assigns the IP address, moreover assigning a static IP is not a best practice in Kubernetes.
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
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
IP Address:
More than one gateway IP ( where NFs are deployed) 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 - Screen level changes (Stretch goal)
MOCK SCREENS FOR UUI ENHANCEMENTS:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
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,
UUI and SO interaction
API details are documented in SO_impacts
2. SO ↔ CPS(WIP) (Existing APIs are used
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": ""
}
}
} |
2. SO ↔ CPS(WIP)
API Reference:
To Fetch coverage Area to coverage Area TA List Mapping:
...
To Fetch CUCP details wrt to the cell:
3. SO ↔ SDNC (Existing APIs are used)
API used to fetch Network topology:
...
Response from SDNC:
Topology
|
4. SO ↔ AAI
API Used:
To Fetch PNF's:
...