# Cloud-Enabled Deployment of 5G Core Network with Analytics Features
## 4 The Testbed
### Slicing Configuration
In the verification scenario, a single common gNB is used to support a multi-slice infrastructure and to relay PDU session establishment requests to a shared AMF. The UERANSIM software implementation of gNB shares the combination of MCC and MNC values with the AMF to indicate that the emulated 5 GAN belongs to the same PLMN as the 5 GCN. The gNB configuration file also specifies the TAC value (_tac: 1_), which is present in the AMF and SMF1/SMF2 configuration files, for each of the supported slices. According to the network configuration, the radio link, N2 and N3 interfaces are bound to the _enp0s9_ with an IP address of 192.168.58.130. The gNB is associated with a single AMF, which is identified by the IP address 192.168.58.110. The gNB also supports both slices, as indicated in Table 4.

UEs are configured with the initial slice according to the topology presented in Figure 2. The configuration files for UE1 and UE2 specify the compliance of PLMN, identify the gNB that provides access to the AN, and describe the default/supported NSSAIs. UE1 and UE2 have been assigned unique IMSIs, which have been registered in the MongoDB subscriber database. ## 5 Verification of the Testbed

In the deployed 5G network architecture, the following scenario is designed to verify the testbed. Two UEs (_UE1_, _UE2_) send a registration request via NAS message to a shared AMF. As the UEs are authorized, the separation related to slicing occurs. The AMF performs the SMF selection procedure and finds an SMF suitable for the particular S-NSSAI and Data Network. If the selection is successful, the AMF requests the creation of a PDU session from the SMF. As a result, the PDU session for a given UE should be created in a respective logical network. That is, the UE1 PDU session request to _internet_ DN should be managed by SMF1, and the data transfer tunnel should be anchored at UPF1. The exact procedure should be repeated for the UE2 PDU session establishment request. Supplementary figures and listings are published in the repository [42]. Our contribution is focused on creating a robust environment for future research rather than benchmarking performance metrics. This means we have prioritized developing a flexible and reliable testbed that researchers can use to explore various aspects of 5G core networks. By validating the functional integrity and practical deployment of network functions within our testbed, we provide a solid foundation for future performance evaluations and optimizations. Our work facilitates further research by enabling the testing, validation, and enhancement of different components and configurations of 5G networks. The verification of the virtualized 5 GCN consists of two subparts: Initial Registration and service request triggered by UE. However, since UEs are configured to initiate the PDU session request immediately after accessing the network, both procedures are combined. To reduce the risk of 5G network initialization error, we propose the following deployment steps:

1. 5G Core Network control plane: Start all Open5 GS CP NFs in the following order: \[NRF\to AMF\to UDR\to UDM\to NSSF\to AUSF\to PCF\to BSF\to SMF1\to SMF2\]
2. 5G Core Network user plane: 1. Enabling NAT and tunneling. 2. Starting Open5 GS user plane NFs: UPF1 and UPF2. 3. 5 GAN: Start UERANSIM gNB instance. Each of the NFs registers with the NRF through its dedicated SBI for NF management. During NF registration, an HTTP/2 PUT request is issued to the _/nwr-nfn/v1/nf-instances/_ endpoint of the NRF. Once the CP functions of the 5 GCN are registered, the UP functions can be deployed. Before running the executables for UPF1 and UPF2 on the _vnn_5 GCN-UPF_ VM, it is essential to set up port forwarding and TUN interfaces for data tunneling. Listing 4 shows the necessary commands for the Debian operating system. 1. [label=.] 2. Necessary network configuration of the UPF VM.