# Cloud-Enabled Deployment of 5G Core Network with Analytics Features
## 4 The Testbed
### Slicing Configuration  
To implement the testbed, the configuration files of the 5 GCN and 5 GAN need to be tailored. This involves modifying the configuration files of the 5 GCN network functions. In this section, we present the most critical aspects of these configurations as a result of our work. With these contributions, one can configure a cloud-based 5G core network deployment with slicing enabled. For Open5 GS and UERANSIM, these files are formatted in YAML. Both emulated UEs must be aware of the assigned S-NSSAI. The Data Network Name (DNN) associated with an S-NSSAI should be consistent within the deployed 5 GCN. Additionally, the International Mobile Subscription Identity (IMSI) of the UEs must be unique. Each UE's IMSI, along with a complete Subscriber Profile, should already exist in the UDR to facilitate successful authentication via the Authentication Server Function (AUSF). In practice, this requires a corresponding entry in the MongoDB database, which is part of the Open5 GS framework. In the proposed testbed, the 5 GCN is logically divided into two slices: internet and ims. Both slices are dedicated to provisioning data services. The S-NSSAI describing these slices is presented in Table 4. As illustrated in Figure 2, each slice is assigned a dedicated SMF function in the CP and a UPF in the UP. The slices can be distinguished by their respective \begin{table}
\begin{tabular}{c c c} \hline
**VM Name** & **RAM** & **Disk Space** \\ \hline
**vm\_5 GC-CP** & 2048 MB & 6 GB \\ \hline
**vm\_5 GC-UPF** & 1024 MB & 6 GB \\ \hline
**vm\_5G-UERANSIM** & 1024 MB & 6 GB \\ \hline \end{tabular}
\end{table} 
Table 2: VirtualBox guest platforms parameters. \begin{table}
\begin{tabular}{c c c} \hline
**Name** & **Data Networking Space** & **Northbound Networking Space** \\ \hline
**Address pool** & 192.168.56.0/24 & 192.168.58.0/24 \\ \hline
**Virtual interface** & & \\
**on the host OS** & _rboxnet1_ & _vboxnet1_ \\ \hline
**IP address** & 192.168.56.101 & 192.168.58.101 \\ \hline
**Purpose** & host-to-VM access via SSH & traffic related to SBA and reference-point communication of the deployed 5G network \\ \hline \end{tabular}
\end{table} 
Table 3: Logical network configuration. colors (_pink_ for the internet slice and _green_ for the ims slice) of the network function (NF) blocks and the S-NSSAI mentioned within the NFs. The remaining NFs of the 5G CP are shared among the two slices, including the Network Repository Function (NRF), UDR, Unified Data Management (UDM), Binding Support Function (BSF), PCF, AUSF, Network Slice Selection Function (NSSF), and AMF. The configuration presented below is critical for deploying a slice-enabled and virtualized 5 GCN in a cloud environment. We provide examples of the configuration files, all of which are published in the repository [42], to which we refer in the following explanations. To successfully deploy an AMF, it has been configured to support both slices, as shown in Listing 1. The Globally Unique AMF ID (GUAMI) reflects the common PLMN identity and the Tracking Area Identity (TAI) component. The Tracking Area Code (TAC) is shared by AMF and gNB. The _ngap_ interface of AMF, responsible for the handling of Non-Access Stratum (NAS) signaling, is bound to the physical interface _enp0s9_ of the _vm_5 GC-UP_. The SBI interface of the AMF is used for service exposure and access. A default Open5 GS configuration is used since the 5 GCN CP is deployed on a single VM. Therefore, the use of a loopback interface with unique port numbering simplifies the scenario and reduces the risk of failure due to a routing error. ```
amf: sbi: - addr: 127.0.0.5 port: 7777 ngap: - addr: 192.168.58.110 guami: - plmn_id: mcc: 666 mcc: 01 amf_id: region: 2 set: 1 tai: - plmn_id: mcc: 666 mcc: 01 tac: 1 plmn_support: - plmn_id: mcc: 666 mcc: 01 s_nssai: - sst: 1 sd: 000001 - sst: 2 sd: 000002 -