SBI Configuration

There are registerIP and bindingIP design on every NF’s sbi interface.

SBI interface

This is due to some orchestration, such as Kubernets or OpenStack, has the design of service IP mapping.

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.

Sample configuration

We provide a sample config to connect to outer ran under /sample/ran_attach_config/. The architecture is as following.

free5GC sample config

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.

SMF Configuration

A. Configure SMF with S-NSSAI

  1. Configure NF Registration SMF S-NSSAI in smfcfg.conf
snssai_info:
- sNssai:
    sst: 1
    sd: 010203
  dnnSmfInfoList:
    - dnn: internet
- sNssai:
    sst: 1
    sd: 112233
  dnnSmfInfoList:
    - dnn: internet
  1. Enable ULCL feature in smfcfg.conf
    ulcl:true
  1. Configure UE routing path in uerouting.yaml
ueRoutingInfo:
  - SUPI: imsi-2089300007487
    AN: 10.200.200.101
    PathList:
      - DestinationIP: 60.60.0.101
        DestinationPort: 8888
        UPF: !!seq
          - BranchingUPF
          - AnchorUPF1

      - DestinationIP: 60.60.0.103
        DestinationPort: 9999
        UPF: !!seq
          - BranchingUPF
          - AnchorUPF2

For more detail of SMF config, please refer to here.