# Cloud-Enabled Deployment of 5G Core Network with Analytics Features
## 4 The Testbed
### Slicing Configuration
\begin{table}
\begin{tabular}{c c c c} \hline \hline
**SST Value** & **SD Value** & **DNN** & **UE Identity** \\ \hline
1 & 0x000001 & internet & UE1 \\ \hline
2 & 0x000002 & ims & UE2 \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Network slices in the implemented 5 GCN. SMF1, deployed on _vm_5 GC-CP_, binds its Packet Forwarding Control Protocol (PFCP) interface (the N4 interface in reference-point architecture) to _enp0s9_ physical interface, with an IP address of 192.168.58.111. The same line is present in UPF1 configuration to alter the default PFCP address and ensure that a N4 link is established and PFCP peering has been achieved. The PFCP address is bound to the _enp0s9_ physical interface on _vm_5 GC-UPF_ VM, and equals 192.168.58.121. The GTP-U interface, i.e., the N3 reference point for data transfer, also points to the 192.168.58.121 address. The _subnet_ values reflect the SMF1 configured IP address pool and DNN. The _dev_ value denotes the tunnel interface name, which is used for data tunneling via the N6 interface to DN, i.e., public internet. The SMF1 configuration file is presented in Listing 2. ```
smf:  sbi: - addr: 127.0.0.4 port: 7777 pfcp: - addr: 192.168.58.111 gtpu: - addr: 192.168.58.111 subnet: - addr: 10.45.0.1/16 dnn: internet dns: - 8.8.8.8 - 8.8.4.4 freeDiameter: /root/open5 gs/install/etc/ freeDiameter/smf.conf info: - s_msgsai: - sst: 1 sd: 000001 dnn: - internet tai: - plmn_id: mcc: 666 mmc: 01 tac: 1
```
The configuration of SMF2 and UPF2 handling the second slice (SST:2) is similar to the SMF1/UPF1. The changes reflect the fact that both SMF1/SMF2 and UPF1/UPF2 are deployed on the same VM: _vm_5 GC-CP_ and _vm_5 GC-UPF_, respectively. Therefore, the IP addresses of the PFCP and GTP-U interfaces, although bound to the same interfaces as addresses SMF1/UPF1, are changed. These addresses are configured to 192.168.58.112 and 192.168.58.122 for SMF2 and UPF2, respectively. Since the NFs in the 5 GCN CP are deployed on one virtual machine, the SMF2 SBI interface cannot point to the same IP address as the loopback interface of the _vm_5 GC-CP_. The SMF2 SBI address has been changed to 127.0.0.24 (port remains intact). This change is later reflected upon NF registration in the NRF, thus the SMF2 services are accessible via the altered SBI. Furthermore, the _freeDiameter_ configuration file has been swapped to indicate the distinction between SMF1 and SMF2 in terms of SBI addresses. This file is used to configure the freeDiameter server, which implements the Diameter protocol, used for carrying the Authentication, Authorization and Accounting (AAA) payload. KeyListenOn_ defines an endpoint, on which the NF will listen for authorization requests, and was configured to 127.0.0.24. In the UPF2 configuration file presented in Listing 3, the key _pfcp_, responsible for establishing the N4 link, has been set to the IP address of the SMF2 PFCP interface. The _subnet_ values for this interface differ from the UPF1 settings. To route data traffic from UEs belonging to different PDU sessions to the appropriate destination, the device (_dev_) responsible for forwarding UE2 data traffic points to the _ogstun2_ interface on the _vm_5 GC-UPF_ virtual machine. ```
upf: pfcp: - addr: 192.168.58.122 gtpu: - addr: 192.168.58.122 subnet: - addr: 10.46.0.1/16 dnn: ims dev: ogstun2 smf: pfcp: - addr: 192.168.58.112
```
According to 3 GPP Release 15 [43], the AMF obtains information about the configuration of the slices from the NSSF. Therefore, the NSSF YAML file must be customized for the specific test scenario to include the necessary slice information (Table 4). Both slices are associated with one NRF, which means that both pairs of SMF/UPF are registered with the same NRF. Therefore, the AMF can request service from proper SMFs for a particular slice. The procedure is described as the SMF selection process [43]. The syntax of UERANSIM configuration files differs from those used by the Open5 GS framework. However, the key parameters are still recognizable.