## 7 Experimental Results  
The interactive GUI of the IBN application is shown in Figure 10 where users can submit their intents in the form of contracts. After that these contracts are translated with the help of both policy configi  
Figure 10: GUI of intent-based networking tool.  
Figure 11 shows the downlink throughput of all three slices, we have achieved a maximum of 32 MB/s throughput for eMBB, 26 MB/s for IoT, and 16 MB/s for URLLC slice downlink throughput while performing the Iperf test for each slice. For the downlink case, we have already specified 40, 40, and 20 MB/s of throughput in slice contract for each slice. However, the configurations provided from the IBN tool were properly deployed and configured the resources for each slice.  
The uplink throughput speed tested with Iperf for each slice is presented in Figure 12, as mentioned above the up-rate throughput specified in the network slice template was 20, 20, and 10 MB/s respectively. Although we have got a maximum of 19 MB/s for slice#1 and 17 MB/s for slice#2 and 7 MB/s for slice#3. In our experimental setup, we have 100 MB/s connection and SDR USRP B210 also provides up to 100 MB/s spectrum support. The results show the performance of our system is stable and the required slices were created dynamically.  
Figure 13 presents the downlink and uplink throughput test performed with Iperf only at access network eNB. We just provide the configurations to the RAN slicing configurator with different QoS, such as radio resource block (RBs) and 20, 40, 60, 80, and 100% spectrum resources of the RAN eNB. You can see that by increasing the resources of RAN, you can increase the uplink and downlink  
Figure 11: Iperf downlink throughput for three slices.  
Figure 12: Iperf uplink throughput for three slices.  
throughput of the network slice. When we have created a slice with 20% resources of eNB, it provides low 4.5 MB/s and 9 MB/s throughput speed for UL and DL respectively. On the other hand, by using the 100% resources of RAN, it shows 69 MB/s of DL and 41 MB/s of UL speed. Thus, after getting the slice template configurations from the RAN slicing configurator, FlexRAN can deploy those configurations at physical eNB and share the resources accordingly.  
The downlink throughput with simulated UEs is presented in Figure 14 where four simulated OAI UEs are connected with the deployed RAN slice successfully. The Iperf results show that the maximum of 12 MB/s downlink speed throughput was achieved for one UE in our test-bed. This test has been carried out with multiple time slots and UEs are connected properly all the time. Although, sometimes the connection problem occurs due to poor signal strength of SDR USRP B210. We test our slicing system with eight simulated OAI UEs and it shows promising performance in terms of bandwidth, latency, and delay. Thus, our system is totally dependent on open-source systems like OSM, FlexRAN, OAI EPC, OAI eNodeB, and OAI UEs. Hence, our IBN system can automate the network configurations and generate a slice template with the help of policy configurations and deploy these resources requirements into underlying infrastructure by using OSM orchestrator and FlexRAN controller.  
Figure 14: Iperf throughput test results with simulated UEs.  
Figure 13: Iperf downlink and uplink throughput test for eNB resource sharing.