## 1 Introduction  
The evolution of mobile wireless systems towards heterogeneous networks with the introduction of fifth-generation systems has significantly increased the complexity of radio resource management [1]. Researchers [2] have investigated plausible options for implementation of the slicing concept at the RAN level by a mobile network operator to respond to the needs of vertical applications. In addition, they discuss the main challenges of RAN slicing, paying particular attention to the resource allocation problem between slices sharing the same spectrum. When it comes to distributing network slices across physical resources, one of the biggest challenges is RAN network slicing. Researchers in [3] aimed to improve network performance and flexible use of network resources by dynamically using network resources to meet the different requirements of activated network slices. As a method, researchers [3] proposed a data-driven RAN slicing mechanism based on a resource-sharing algorithm operating at the Slice Orchestrator (SO) level. In order to ensure uninterrupted transmission in new 5G systems based on mobility management network slicing, management schemes are widely required due to the diversity of 5G application scenarios. Network slicing is used in the Cloud Radio Access Network (C-RAN), Software Defined Network (SDN) and Network Function Virtualization (NFV) to provide point-to-point connectivity between physical radio equipment and the radio equipment controller. A suitable approach for integration is not yet available. Network slicing needs to work with other 5G technologies to enable more network slices to be used in future 5G networks [4]. In 5G, the level of flexibility on the radio access network side can be achieved by implementing multiplexing of numerology types in the frequency domain. For example, Ultra Reliable Low Latency Communication (URLLC) traffic requires a short slot length to meet stringent latency requirements, while the Enhanced Mobile Broadband (eMBB) use case typically requires a medium slot length. A long slot length is used for Massive Machine Type Communication (mMTC). Therefore, among the set of supported numerology types for a given operating band and distribution configuration, URLLC may be represented by the number associated with the shortest slot length, eMBB may be represented by the number associated with the medium slot length and mMTC may be represented by the number associated with the largest slot length. In order to meet the latency and data rate requirements of the UE for different network slices such as URLLC, eMBB and mMTC, the physical resources in the gNB need to be dynamically managed according to the incoming packet types. The overall system includes end-to-end User Equipment (UE), Distributed Unit (DU), Control Unit (CU), User Plane Function (UPF) and Data Network (DN). The network slicing architecture is shown in Figure 1. In order to manage different network slices on the core network side, a dedicated UPF is positioned for each network slice when going to the data network. On the RAN side, however, there appears to be a single physical resource block for these three different network slices. Having a single resource block creates the need to dynamically manage it to meet the needs of three different networks. Bandwidth and slot width requirements vary depending on the needs of the applications that will be using the network slices. Sometimes applications can be closed and the resources they use reassigned to other network slices to increase efficiency. As mobile data usage continues to grow and advanced applications are deployed, it has been observed that inflexible mobile network architectures cannot meet evolving service requirements. It is stated that 5G mobile networks will have to overcome challenges such as higher capacity, higher data speed, lower end-to-end latency, multiple device connections, reduced cost and continuous quality of service that cannot be effectively addressed in 4G.