There are registerIP and bindingIP design on every NF’s sbi interface.
This is due to some orchestration, such as Kubernets or OpenStack, has the design of service IP mapping.
Use Kubernets as an example. K8S has the service type that enable users to define the service IP outside the pod. But the service IP may be different from the IP assigned inside the pod. Therefore, if we register the binding IP inside the pod to NRF, NRF cannot know which service IP outside the pod has attached. As the result, we need to separate registerIP from bindingIP in this scenario.
If you are not sure what IP you should set, just configure it as the same IP address.
We provide a sample config to connect to outer ran under
/sample/ran_attach_config/. The architecture is as following.
As the result, user’s RAN IP must set to 192.168.0.0/24 subnet or let the routing route to this subnet.
Notice: If user wants to use the setting, aware to set 192.168.0.1 to your host as well.
A. Configure SMF with S-NSSAI
- Configure NF Registration SMF S-NSSAI in
snssai_info: - sNssai: sst: 1 sd: 010203 dnnSmfInfoList: - dnn: internet - sNssai: sst: 1 sd: 112233 dnnSmfInfoList: - dnn: internet
B. Configure Uplink Classifier (ULCL) information in SMF
- Enable ULCL feature in
- Configure UE routing path in
ueRoutingInfo: - SUPI: imsi-2089300007487 AN: 10.200.200.101 PathList: - DestinationIP: 188.8.131.52 DestinationPort: 8888 UPF: !!seq - BranchingUPF - AnchorUPF1 - DestinationIP: 184.108.40.206 DestinationPort: 9999 UPF: !!seq - BranchingUPF - AnchorUPF2
- DestinationIP and DestinationPort will be the packet destination.
- UPF field will be the packet datapath when it match the destination above.
For more detail of SMF config, please refer to here.