###### Abstract  
The 3 GPP standardized the physical layer specification in 5G New Radio to support enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) coexistence in usage scenarios including aerial vehicles (AVs). Dynamic multiplexing of URLLC traffic was standardized to increase the outage capacity. DM allocates a fully overlapped bandwidth part (BWP) of eMBB and URLLC AVs to perform the immediate scheduling of URLLC traffic by puncturing ongoing eMBB traffic. However, DM often suffers from a significant frame error incurred by puncturing. Meanwhile, BWP can be sliced orthogonally for eMBB and URLLC AVs, possibly preventing overdimensioning the resources depending on the eMBB and URLLC traffic loads. In this paper, we propose a dynamic BWP allocation scheme that switches between two multiplexing methods, dynamic multiplexing (DM) and orthogonal slicing (OS), so as to minimize an impact of uRLLC traffic on eMBB traffic. To implement efficient BWP allocation, the capacity region is analyzed by considering the effect of physical layer parameters, such as modulation and coding scheme (MCS) levels and code block group size on DM and OS. OS is effective for improving the eMBB throughput under a URLLC latency constraint for deterministic and predictable URLLC traffic, whereas DM has limited error-correcting capability against the URLLC's puncturing effect. The relative MCS level of eMBB and URLLC is critical in determining the eMBB traffic tolerance against puncturing. Identifying the performance tradeoff between DM and OS, the tolerance level is quantified by a URLLC load threshold. It is given in an approximate closed form, which is an essential reference for selecting DM over OS, enabling dynamic BWP allocation for the URLLC AV. URLLC; eMBB; unmanned aerial vehicle; bandwidth part; resource allocation; dynamic multiplexing; orthogonal slicing +
Footnote †: journal: Sensors  
0000-0001-998-22000-0000-0000-0000-0000-00000-0000-0000-0000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-00000-000000-0000  
(URLLC) services, are supported for high data rate traffic and low-latency/high-reliability traffic, respectively. Each service scenario has its own quality of service (QoS) requirements that need to be satisfied. More specifically, the data rate for eMBB services must be maximized while satisfying two conflicting requirements for URLLC service (i.e., latency and reliability). The NR system aims to efficiently support diverse AVs with different usage scenarios in a single carrier bandwidth (CBW). To this end, it includes new physical layer specifications, such as numerologies for subcarrier spacings (SCS) and slot length, code block group (CBG)-based transmission, bandwidth part (BWP), and preemption-based URLLC scheduling. Along with other physical layer specifications, a preemption-based scheduling mechanism allows URLLC traffic to be immediately scheduled by puncturing or superposing ongoing eMBB traffic. Notably, the preemption-based scheduling in 3 GPP is also referred to as eMBB/URLLC dynamic multiplexing (DM) in the literature. A detailed description of the eMBB/URLLC DM (or simply DM) was reported previously [2]. The concept of DM was first introduced in [3], wherein it was argued that URLLC traffic with Poisson arrival should be wideband allocated to increase capacity while satisfying the outage capacity of URLLC. Furthermore, because of the sporadic nature of URLLC, traffic tends to underutilize a given wideband resource and it would be more efficient to schedule eMBB traffic in resources that are not occupied by URLLC traffic. That is, the motivation of DM in [3] was to maximize the outage capacity of URLLC traffic while increasing the resource utilization of the system. However, in [3], only the URLLC outage capacity and system resource utilization were considered in DM without considering the throughput of eMBB traffic or eMBB/URLLC sum throughput.