This paper was converted on www.awesomepapers.org from LaTeX by an anonymous user.
Want to know more? Visit the Converter page.

RAN Slicing in Multi-MVNO Environment under Dynamic Channel Conditions

Darshan A. Ravi , Vijay K. Shah, Chengzhang Li, Tom Hou, and Jeffrey H. Reed
Bradley Department of ECE, Virginia Tech, Blacksburg, VA, 24061
Emails:{darshan19, vijays, licz17, hou, reedjh}@vt.edu
This work has been partially supported by DARPA HR0011-19-C-0096.
Abstract

With the increasing diversity in the requirement of wireless services with guaranteed quality of service(QoS), radio access network(RAN) slicing becomes an important aspect in implementation of next generation wireless systems(5G). RAN slicing involves division of network resources into many logical segments where each segment has specific QoS and can serve users of mobile virtual network operator(MVNO) with these requirements. This allows the Network Operator(NO) to provide service to multiple MVNOs each with different service requirements. Efficient allocation of the available resources to slices becomes vital in determining number of users and therefore, number of MVNOs that a NO can support. In this work, we study the problem of Modulation and Coding Scheme(MCS) aware RAN slicing(MaRS) in the context of a wireless system having MVNOs which have users with minimum data rate requirement. Channel Quality Indicator(CQI) report sent from each user in the network determines the MCS selected, which in turn determines the achievable data rate. But the channel conditions might not remain the same for the entire duration of user being served. For this reason, we consider the channel conditions to be dynamic where the choice of MCS level varies at each time instant. We model the MaRS problem as a Non-Linear Programming problem and show that it is NP-Hard. Next, we propose a solution based on greedy algorithm paradigm. We then develop an upper performance bound for this problem and finally evaluate the performance of proposed solution by comparing against the upper bound under various channel and network configurations.

Index Terms:
5G and Beyond Networks, RAN Slicing, Dynamic Channel Conditions, Performance Bound

I Introduction

With the advent of Internet of Things (IoT), number of devices accessing the internet has been increasing exponentially. Ericsson has estimated that about 5 billion IoT devices will be connected to the internet and about 2.6 billion 5G subscriptions by the end of 2025 [1]. Efficient utilization of available spectrum resources becomes vital to accommodate this growth. Adding to this requirement, is the complexity of users having varied QoS requirements.

To address this complexity, Radio Access Network (RAN) slicing technology has been widely adopted by several industrial communities [2, 3]. With the help of RAN slicing, operators can perform service customization, isolation and multi-tenancy support on a common physical network infrastructure by enabling logical as well as physical separation of network resources [4]. This multi-tenancy support enables network operators (NO) to support multiple mobile virtual network operators (MVNOs) in the form of a slice. The Third-Generation Partnership Project (3GPP) has identified network slicing as one of the key technologies to achieve varied performance requirements — such as high throughput, low high security goals in 5G networks [5].

One of the key features of RAN slicing is that - MVNOs are assigned slices that are independent from one another [6]. That is, the allocation of the radio resources is up to the NO who can allocate them at will, based on the QoS requirement while ensuring complete isolation between slices. The NO we consider is based on Software Defined - Radio Access Network (SD-RAN) controller architecture comprising of a Slice Manager and MVNO specific scheduler. The NO architecture is formally introduced in Section III.

Once the QoS requirements for each MVNO is collected by NO, the core problem lies in allocation of scarce spectrum resources such that each MVNO’s QoS requirement is met for all its users. We consider spectrum resources as resource blocks (RB). This is a difficult problem because over provisioning of RB for a user, will result in wastage and under provisioning might not meet the QoS requirements. Therefore the design of efficient slicing algorithm to meet each MVNO user’s requirement is key for optimal usage of RB. Also, from a business standpoint, optimal usage of RB which will result in increased number of users served in a time slot and thereby increased number of MVNOs supported by fixed number of RB is of great interest.

One of the factors which influence the slicing decision, is the channel condition experienced by the RB during its path towards the users. In order to convey the channel information, each user in the network sends a CQI report back to the NO. Often in real world scenarios, the channel conditions do not remain the same. They keep varying with respect to time and frequency. In order to take into account of this dynamic channel condition, the users send the CQI report in regular intervals with its periodicity determined by the NO and in between this interval, the channel conditions are assumed to remain same [7]. In order to remain close to reality, we consider dynamic channel conditions in our work.

We illustrate the problem of RAN Slicing under dynamic channel conditions by considering minimum data rate per time slot for each user as a specification by MVNOs. Calculation of data rate for a user at a given time depends on MCS level chosen for the user by the NO at that time. Choice of MCS level in turn depends on the CQI report sent from the users of MVNO. Now, the problem we are addressing in this paper is, how do we create a channel conditions aware slice for each MVNO such that, maximum number of MVNO user’s minimum data rate requirement is met.

Even though RAN resource allocation issue has been studied extensively in the recent past [8],[6],[9], the problem of resource allocation to MVNOs under dynamic channel conditions is relatively new. This is discussed more in Section II. Design of efficient resource allocation/slicing enforcement algorithm is not trivial and is met with unique challenges:

  • Users maximization: Meeting the minimum data rate requirement for maximum number of MVNO users in the slice time slot. This can be achieved by choosing the optimal number of RB and the MCS level for each user.

  • Orthogonality: Each RB should be allocated to only one user across all MVNOs at a given time slot to avoid interference  [10],[11],[12].

  • Support advanced 5G technologies: The RB allocation should also facilitate in implementation of advanced 5G technologies such as CoMP and MIMO [9].

The aim of this work is to design, analyze and validate MCS aware RAN Slicing(MaRS) algorithm that take into consideration the challenges mentioned above. To summarize, this work makes the following contributions:

  • We formulate the MCS aware RAN Slicing (MaRS) problem as a Non-Linear Programming Optimization problem in Section V using the model developed in Section III. We will also prove the NP-Hardness of the MaRS problem.

  • We propose a solution for this problem using the greedy algorithm paradigm in Section VI.

  • We develop an upper performance bound for the MaRS algorithm in Section VII.

  • We provide an implementation of the proposed solution and carry out an exhaustive evaluation in Section VIII.

II Related Works

There has been significant work to address the problem of RAN slicing, especially in the recent past. There have been many excellent surveys on this topic  [4, 10, 13, 14, 12]. The authors in these surveys provide a comprehensive information regarding the work being done on this topic. Additionally, a book has been published on the topic of RAN Slicing where many slicing algorithms have been proposed [15]. Specifically [13] covers the advancements in RAN slicing which is based on the SDN architecture. The architecture considered in our work loosely follows the work covered in [13].

In the recent works, the RAN slicing problem [16, 17, 18] has been dealt by designing solutions using various theoretical means optimization [19, 20], game theory [21]. There has also been many advancements where several machine learning approaches have been used to address the RAN Slicing problem – {Reinforcement Learning [22], Deep Learning [23, 24, 25]}. These machine learning approaches are not suitable for deployment due to their huge data requirements for training and the time it requires to do so. Moreover accurate predictions of the channel conditions are required to make the slicing algorithm effective.

One of the key limitation of these works is that it does not show the actual deployment of RAN slices on top of a physical network. Although the authors in the paper [9] discuss RAN slicing policies and enforcement problem by considering fine grained control of resources, it falls short when we bring in dynamic channel conditions. Moreover, the problem formulation considers slice as allocation of certain percentage of resource blocks from a given pool without considering the underlying requirement for these slices.

One of the work which closely focuses on addressing RB allocation problem is [11]. The authors propose a RB partitioning algorithm which focuses on allocating RB to every MVNO by simultaneously maximizing the percentage of satisfied MVNOs while allocating the minimum amount of RB. However, the problem in [11] does not take into account the dynamic channel conditions.

Our work can be closely compared to [8]. The authors of [8] address the problem of RAN slicing by considering dynamic channel conditions in a SD-RAN based architecture. One of the key architectural differences between our work and [8] is the flexibility offered to the MVNO in the SD-RAN architecture. In [8], the authors consider individual slice managers for each slice but a common scheduler for all the users. This provides very less flexibility for MVNOs. In our work, we consider independent scheduler for all MVNOs. This allows MVNO, the option of choosing its users for scheduling at each time interval. Section III discusses this in detail.

In [26], the authors address the RAN Slicing problem for multiplexing eMBB and URLLC slices. Although the paper [26], considers the MCS selection in the design of the slicing algorithm, it again falls short in providing MVNO the flexibility in scheduling as the architecture considered in completely different.

The papers [27, 28] present a framework for LTE virtualization. The authors propose an architecture for virtualizing the LTE base stations (called eNodeB in LTE architecture) with the objective of having different operators sharing the same physical resources. The solution is based on a hypervisor (as in CPU virtualization), which hosts different virtual nodes, allocates the resources and is responsible of the spectrum sharing and data multiplexing. In [29], the framework from  [27, 28] is used to present a algorithm for scheduling physical RB for the virtual nodes. The main idea of this algorithm is that if a eNodeB is overloaded and a neighbor eNodeB has available resources, a user is selected to be migrated to the unloaded eNodeB. Although the concept of centralized control is similar to our work, the problem statement is completely different. In our work, we are addressing the problem of RAN slicing in a multi-MVNO environment as opposed to resource sharing.

In summary, our work addresses the shortcomings of these papers by providing more flexibility to the MVNOs, developing efficient slicing algorithm with dynamic channel conditions and carrying out a thorough validation.

III System Model

We consider a NO administering a single 5G5G RAN base station BB and set of ={1,2,\mathcal{M}=\{1,2...,M}\} MVNOs as depicted in Fig. 1.The NO serves the MVNOs by creating virtual RAN slices built on top of underlying physical network BB. We split NO functionally into Slice Manager and MVNO scheduler. This architecture lies inline with 5G RAN concepts, where the management and orchestration is implemented as a Software Defined Network (SDN). We adopt the architecture principle similar to  [8][30], and include additional features to aid the proposed slicing procedure.

Once the NO collects the minimum data rate slice request from all MVNOs, it creates an instance of MVNO scheduler for each MVNO in the network.We define Λmi\Lambda_{m}^{i} as the minimum data rate requirement for each user ii of MVNO im,m,m\forall i\in m,m\in\mathcal{M},\forall m. MVNO Scheduler for all mm\in\mathcal{M} provides a scheduling order of users belonging to mm, 𝒰m\mathcal{U}_{m}, to the Slice Manager. The Slice Manager, which has the CQI information for each user in the network, dynamically assigns the resources on BB to each MVNO slice based on this scheduling order sent by the MVNO. Advantage of this architecture is that it leaves the choice of scheduler implementation, up to the MVNO. Each MVNO may employ unique scheduling algorithm.

Since the BS follows 5G5G cellular technology, spectrum resources are organized as grids of RB, that span across both time and frequency domains [31]. Each RB represents the minimum spatio-temporal scheduling unit. Considering NRBN_{RB} and TT as the number of available subcarriers and temporal slot respectively, the set of available RB is |Rb|=NRB×T|R_{b}|=N_{RB}\times T in the physical RAN network for a certain bandwidth.

Implication of time slot T. Theoretically, the time slot TT can range from 1 TTI(tt) to 10001000’s of TTIs, depending upon how dynamically the slice manager wishes to operate resource slicing policy. Under realistic consideration and in lieu with next-generation O-RAN architecture [32], it is expected that the slicing manager will either reside in non-real-time Ran Intelligent Controller(RIC) or near-real-time RIC, which are respectively, in order of >1>1s and (10100010-1000 ms) time scales [33]. Thus, in our work, we consider that TT will be a large value, in range of several milliseconds. Further, we consider the user’s minimum data rate requirement is defined per time slot TT.

Dynamic Channel Conditions. We consider the channel conditions to be dynamic in nature and may vary in frequency and time, but remain consistent within the time slot TT. This is similar to aperiodic csi reporting [7]. Depending upon the channel condition obtained from CQI reports for users of the MVNOs being served, the Slice Manager determines a suitable MCS for transmission depending on each MVNO user’s minimum data rate requirement, out of 2929 MCS levels as per 5G 3GPP specification [31]. Let 𝒞\mathcal{C} denote the set of available MCS, i.e., 𝒞={0,1,,28}\mathcal{C}=\{0,1,\dots,28\}. The MCS determines how much information (in bits) is modulated and coded in each RB by the BS. The higher the MCS is, the higher the modulation and coding rate is. That means, the maximum amount of information that can be transmitted on one RB also depends on the channel conditions. If the channel condition is poor and the NO uses a high MCS, then the information carried in the RB will not be successfully received and decoded. Therefore, the achievable data rate by an RB depends on both MCS level chosen by the NO as well as the channel condition for this RB.

Let qumir,tq_{u^{i}_{m}}^{r,t} denotes the maximum MCS that can be used for a certain RB rr to serve a user umi𝒰mu^{i}_{m}\in\mathcal{U}_{m} such that the information carried in RB can be successfully received by the user at TTI tTt\in T.

1qumir,t|C|1\leq q_{u^{i}_{m}}^{r,t}\leq|C|

Let vc,tv^{c,t} denote the modulation and coding rate for a resource block under MCS c𝒞c\in\mathcal{C} and dumir,c,td_{u^{i}_{m}}^{r,c,t} denote the maximum achievable data rate by RB rr for the user umiu^{i}_{m} under MCS c𝒞c\in\mathcal{C} at time tTt\in T. If cqumir,tc\leq q_{u^{i}_{m}}^{r,t}, the transmission would be successful and the achievable data rate is vc,tv^{c,t}. Otherwise, the transmission would be unsuccessful and the data would be lost. That is,

dumir,c,t={vc,t,ifcqumir,t0otherwised_{u^{i}_{m}}^{r,c,t}=\begin{cases}v^{c,t},\hskip 5.69054pt$if$\hskip 5.69054ptc\leq q_{u^{i}_{m}}^{r,t}\\ 0\hskip 5.69054pt$otherwise$\end{cases} (1)
Refer to caption
Figure 1: The SD-RAN slicing architecture.

Finally, the NO also imposes a restriction on maximum throughput allowed per MVNO slice, namely Λm¯\overline{\Lambda_{m}}, depending on channel conditions or business requirements. This restriction prevents any individual MVNO slice from overloading the network. An intuitive way of selecting Λmi\Lambda_{m}^{i} may be from pure business perspective, i.e, whichever MVNO pays the most will get higher throughput. However, in general the choice of maximum throughput in a multi-MVNO, limited resources environment introduces a new problem that is out of the scope for this work.

IV SD-RAN Workflow

Before we proceed with designing of the Slicing Algorithm, it is important to understand how different components in the SD-RAN architecture interact with each other to serve users of MVNO. In this section, we present the workflow for our SD-RAN architecture in Fig 1.

The NO communicates with several components before it assigns resources to a specific user of a MVNO. After a MVNO requests services from a NO, the task of allocating resources can be broadly divided into 4 steps.

Step 1: Acquiring RAN information

After a MVNO submits a request for a service to the Slice Manager of the NO, the Slice Manager acquires the RAN information. This RAN information contains the number of users in the network for the MVNO, the channel conditions experienced by each user and the available resources in terms of RB in the network to serve the MVNO. In Fig. 2, the base station and the users in the network is represented by a single RAN block.

Step 2: Acquiring scheduling information

An instance of the scheduler is created in the NO for each MVNO that requests a service. It is up to the MVNO on how the scheduling algorithm is implemented. For example, a particular MVNO may use round robin and other MVNO might opt for priority scheduling. Its one of the novelty in our work where we provide the MVNO, the flexibility of choosing the scheduling algorithm. In order to make a slicing decision, the Slice Manager interacts with the instance of the MVNO scheduler to acquire the scheduling list which is a list of users and its unique minimum data rate requirement that is generated through MVNO specific scheduling algorithm.

Step 3: Making Slicing Decision

After Step 2, the Slice Manager has all the required information to make a slicing decision. It has the list of users that it needs to serve with its minimum data rate requirement, their channel conditions and the available resources in the network to serve them. Now, the Slice Manager limits the number of users that can be served for a MVNO by imposing a upper bound of maximum throughput allowed per slice. Using the MCS-aware Ran Slicing Algorithm, the slice manager makes a Slicing Decision by assigning resources to the users of the multiple MVNOs across time TT.

Step 4: Enforcing Slicing decision

After the Slice Manager makes the Slicing Decision for time slot TT, it is conveyed to the MVNO scheduler and enforced on RAN. The MVNO scheduler can use this Slicing Decision as an input to generate the scheduling list for the next time slot TT.

Refer to caption
Figure 2: SD-RAN slicing architecture workflow diagram.

V Problem Formulation

In this section, we formulate the MCS-aware RAN Slicing (MaRS) problem as a Non Linear Optimization problem. The problem aims at determining the optimal set of resource blocks to be allocated to each MVNO mm\in\mathcal{M} in time slot TT, such that maximum number of users can be served across MVNOs in TT, by considering – (1) MVNO’s minimum bit rate requirement is met for each of its user, (2) Each MVNO scheduler’s unique user scheduling order is ensured, and (3) The total throughput per slice does not exceed the maximum allowable throughput set by the NO for that MVNO slice.

Notation. Let set 𝒰m={um1,umj,uk|Um|}\mathcal{U}_{m}=\{u^{1}_{m},\dots u^{j}_{m},\dots u^{|U_{m}|}_{k}\} denote the scheduling order of all users belonging to MVNO mm\in\mathcal{M}.

Decision variables. Let umiu^{i}_{m} denotes whether a user ii belonging to MVNO mm can be served by the Slice Manager. Let xmr,i,tx^{r,i,t}_{m} denote the whether a certain RB rRr\in R is allocated to any user umiu^{i}_{m} in MVNO mm at TTI tTt\in T. Let yi,mc,ty^{c,t}_{i,m} denote whether a MCS level cc is chosen by a user umiu^{i}_{m} at TTI tt.

P1:maxxmr,i,t,yi,mc,tmMumi𝒰mumi\displaystyle P1:\underset{x^{r,i,t}_{m},y_{i,m}^{c,t}}{\max}\sum_{m\in M}\sum_{u^{i}_{m}\in\mathcal{U}_{m}}u^{i}_{m} (2)
umiUmxmr,i,t1,r,t\displaystyle\sum_{u^{i}_{m}\in U_{m}}x^{r,i,t}_{m}\leq 1,\forall r,t (3)
c×yi,mc,tcmaxr,i,txmr,i,t,t,i,m,r,c\displaystyle c\times y^{c,t}_{i,m}\leq c^{r,i,t}_{max}x^{r,i,t}_{m},\forall t,i,m,r,c (4)
cyi,mc,t1,m,i,t\displaystyle\sum_{c}y^{c,t}_{i,m}\leq 1,\forall m,i,t (5)
umiumj,i<j,m\displaystyle u^{i}_{m}\geq u^{j}_{m},\forall i<j,\forall m (6)
tTrRxmr,i,tyi,mc,tdumir,c,tumiΛmi,m,i\displaystyle\sum_{t\in T}\sum_{r\in R}x^{r,i,t}_{m}y^{c,t}_{i,m}d_{u^{i}_{m}}^{r,c,t}\geq u^{i}_{m}\Lambda_{m}^{i},\forall m,i (7)
tTrRumiUmxmr,i,tyi,mc,tdumir,c,tΛm¯,m\displaystyle\sum_{t\in T}\sum_{r\in R}\sum_{u^{i}_{m}\in U_{m}}x^{r,i,t}_{m}y^{c,t}_{i,m}d_{u^{i}_{m}}^{r,c,t}\leq\overline{\Lambda_{m}},\forall m (8)
xmr,i,t,yi,mc,t,umi{0,1}\displaystyle x^{r,i,t}_{m},y^{c,t}_{i,m},u^{i}_{m}\in\{0,1\} (9)

The maximization problem given in (2) targets to accommodate maximum number of users to satisfy the constraints. Constraint (3) indicates that a resource block can be allocated to one UE at any given time. Equation (4) indicates that MCS chosen for a user cannot be greater than maximum MCS supported by any resource block r at that time. Moreover, equation (5), ensures that a single MCS level is chosen for a user at time tt. Constraint (6) ensures that scheduling order determined by MVNO scheduler is maintained in allocating resources. Equation (7) meets the minimum data rate requirement for each user belonging to a MVNO. Equation (8) indicated the maximum data rate achieved by the resources allocated to MVNO is under the maximum allowable throughput for MVNO.

Theorem 1.

The MaRS problem is NP-Hard.

Proof.

In order to prove the NP Hardness, consider the optimization problem defined in Equation (2) for a single MVNO and for a single time slot tTt\in T. Therefore, we drop the mm and tt notation. Further, we consider channel condition is the same across all base stations (and RBs), then the MCS level for all the RBs will be same, c𝒞c\in\mathcal{C}. This affects Equations (7) and (8). Therefore, we can rewrite the optimization problem and the constraints as follow,

P2:maxxr,iui𝒰ui\displaystyle P2:\underset{x^{r,i}}{\max}\sum_{u^{i}\in\mathcal{U}}u^{i} (10)
rRxr,iui\displaystyle\sum_{r\in R}x^{r,i}\geq u^{i} (11)
rRxr,iΛm¯\displaystyle\sum_{r\in R}x^{r,i}\leq\overline{\Lambda_{m}} (12)
xr,i,ui{0,1}\displaystyle x^{r,i},u^{i}\in\{0,1\} (13)

Notice that P2 is a maximum coverage problem, which is a classic NP-Hard problem  [34]. Since MaRS problem can be modeled as a maximum coverage problem, MaRS problem is also a NP-Hard problem. ∎

TABLE I: Notation Table
Symbol                 Definition
\mathcal{M} A set of MVNOs requesting slices from NO.
Λmi\Lambda_{m}^{i} Minimum data rate req. for user ii in MVNO mm\in\mathcal{M}.
Λm¯\overline{\Lambda_{m}} Maximum allowable throughput for a slice mm\in\mathcal{M}.
𝒰m\mathcal{U}_{m} Scheduling List for MVNO mm\in\mathcal{M}
𝒞\mathcal{C} A set of possible MCS values as per 3GPP specifications.
umiu_{m}^{i} Represents a UE ii belonging to MVNO mm\in\mathcal{M}.
vc,tv^{c,t} The modulation and coding rate for an RB
under MCS c𝒞c\in\mathcal{C} at time tTt\in T.
qumir,tq_{u^{i}_{m}}^{r,t} The maximum MCS that can be used for a certain RB rr
to user belonging to MVNO mm\in\mathcal{M} at time tTt\in T.
dumir,c,td_{u^{i}_{m}}^{r,c,t} The maximum achievable data rate by RB rr
for a UE umiu_{m}^{i} under MCS c𝒞c\in\mathcal{C} at time tTt\in T.
cmaxr,i,tc^{r,i,t}_{max} Maximum mcs that can be selected for a RB rr
for user ii at time tTt\in T.
T\mathcal{L}^{T} Slicing List - List of users to be scheduled across MVNOs
at time TT.
CmaxC_{max} Maximum MCS that can be selected for a user at any
TTI tTt\in T.
hth^{t} Maximum achievable data rate for a user at each tti tt.
c~\tilde{c} MCS used to achieve maximum data rate at each TTI hth^{t}.
AtA^{t} List to hold maximum data rate for each user for
every TTI tTt\in T.
RtotR_{tot} Total available RB in the network.
R^\hat{R} RB that have been already allocated in TT.
RR^{\prime} RB that contribute to achieve maximum data rate hth^{t} at each
TTI tTt\in T.
cc^{\prime} MCS value for RR^{\prime} that achieve the maximum data rate hth^{t}.
RR* Total RBs used to meet data rate requirements all the users
in time slot TT.
CC* MCS used for all the RB in RR*.
UU Users served in time slot TT.

VI MCS Aware RAN Slicing Algorithm

In this section, we develop the MCS aware RAN slicing algorithm based on a greedy paradigm.

VI-A Key Intuitions behind the Proposed Algorithm

The design of the MaRS algorithm is based on the following key intuitions.

Refer to caption
Figure 3: An example for MCS selection.

Intuition 1. From MaRS problem objective function (See Eq. 2), it is obvious that we need to maximize the number of users that can be served in TT for each MVNO mm\in\mathcal{M}. We consider the minimum data rate requirement to be per time slot TT and we say that a user umiu_{m}^{i} is served only if it is allocated sufficient resource blocks such that its minimum data rate Λmi\Lambda^{i}_{m} is met in TT. Based on this observation, we should minimize the number of resource blocks utilized to serve each user.

Intuition 2. We sort the users across MVNOs in increasing order based on their minimum data rate requirement Λmi\Lambda^{i}_{m}. We call it as Slicing List T\mathcal{L}^{T}. Even though, each user can have its own minimum data rate requirement, we must follow the scheduling order defined by the MVNO (equation (6)). That is, for some MVNO mm if the scheduling order is um1,um2{u^{1}_{m},u^{2}_{m}}, we must always allocate resources to um1u^{1}_{m} first even if Λm1>Λm2\Lambda_{m}^{1}>\Lambda_{m}^{2}. This ensures that in a case of insufficient resource blocks to support all users in TT, the user which is first in the scheduling order gets higher priority than other users. However, we do not maintain any scheduling order across MVNOs. That is, for any MVNOs m,nm,n, the Slicing List can be T={Λm1,Λm2,Λn1}\mathcal{L}^{T}=\{\Lambda_{m}^{1},\Lambda_{m}^{2},\Lambda_{n}^{1}\} if Λm2<Λn1\Lambda_{m}^{2}<\Lambda_{n}^{1}.

Intuition 3. To incorporate the channel conditions in the slicing decision, we must consider the effect of MCS selection on RB. In Fig. 3, we use an example to show the dependency between MCS selection and number of RB. Suppose a user is requesting a data rate of 8 from a Base Station which has 9 RB. The channel conditions for each of the resource block is denoted in their respective grid position. If the BS chooses MCS 3 for transmission, 3 RB are required to meet the user’s data rate requirement as 3×3=93\times 3=9. If BS choose MCS 4 for transmission, the user’s data rate requirement can be met by just 2 RB as 2×4=82\times 4=8. Therefore, choosing the higher MCS reduces the RB utilization to meet the data rate requirement. From the previous ideas, we know that we must use least amount of resources to serve users to maximize the number of users served. This implies, we must choose the maximum MCS for each user at any given time.

Intuition 4. The slicing decision is an iterative approach where in, we allocate the subset of unallocated resource blocks based on its MCS level to a user of MVNO at each iteration. The slicing decision is controlled by two main factors, the minimum data rate requirement for each user Λmi\Lambda^{i}_{m} and the maximum allowable throughput decided by the NO for each MVNO, Λm¯\overline{\Lambda_{m}}. Eventually, the algorithm exits when all the users have been served or when all RB are allocated.

VI-B Algorithm Details

In this section, we discuss on how we utilize the MCS levels on the RB in making the slicing decisions.

Recall that the first step in our algorithm is the generation of the slicing list T\mathcal{L}^{T}. This depends on:

  • the minimum data rate requirement for each user Λmi,umi,m\Lambda^{i}_{m},\forall u^{i}_{m},m.

  • the scheduling list sent by each MVNO 𝒰m,m\mathcal{U}_{m},\forall m.

Using these information, the Slice Manager develops T\mathcal{L}^{T} which is valid for time slot TT by two-stage sorting, as shown in Alg. 1.

Algorithm 1 Slicing List
1:Collect scheduling order and minimum data rate requirement Λmi\Lambda_{m}^{i} for each user.
2:Generate a tuple for each user which contains MVNO id, scheduling order, minimum data rate <m,i,Λmi>,i,m<m,i,\Lambda_{m}^{i}>,\forall i,m.
3:Add all users to the list T=[<m,i,Λmi>],i,m\mathcal{L}^{T}=[<m,i,\Lambda_{m}^{i}>],\forall i,m.
4:Sort T\mathcal{L}^{T} based on Λmi\Lambda_{m}^{i}.
5:Sort T\mathcal{L}^{T} based on ii.
6:return T\mathcal{L}^{T}

With the Slicing List T\mathcal{L}^{T} as the input, we present the MCS-aware RAN Slicing algorithm in Alg. 2. The algorithm outputs the least number of resource blocks and their MCS level in the time slot TT such that each user’s minimum data rate requirement is met.

As discussed in the previous section, the algorithm uses an iterative approach wherein at each iteration, it serves a user according to T\mathcal{L}^{T}. This algorithm consists of two key steps.

(i) Step 1. Finding the optimal number of resource blocks and their MCS level which maximizes the achievable data rate at each TTI tTt\in T - This is addressed by iterating over the MCS values that a user can support, followed by iterating over each TTI. Remember, the achievable data rate at each TTI, is directly related to the MCS level chosen for its resource blocks. Therefore, in our algorithm, we iterate over each TTI, starting with the maximum MCS CmaxC_{max}, first to calculate the data rate. We keep track of the maximum achievable data rate by updating hth^{t} after each iteration of MCS c~\tilde{c}.

(ii) Step 2. Greedily allocate the resource blocks for each user such that their requirement is met. Once we have the list containing the maximum achievable data rate and the corresponding resource blocks with the MCS value for each TTI AtA^{t}, we now allocate the resources to the user in TT. Our key idea is to minimize the number of resource blocks for each user which will subsequently help us in maximizing served users in TT. As discussed in previous section, in order to minimize the RB utilization, we need to choose the higher MCS. Following this idea, we follow a greedy approach where in we choose the resource blocks with maximum MCS first in AtA^{t} to meet the minimum data rate requirement for each user. This enables us to choose the least amount of resource blocks and corresponding MCS at each TTI tTt\in T, such that each user’s requirement Λmi\Lambda_{m}^{i} is met for time TT.

Algorithm 2 MCS-aware RAN Slicing Algorithm

Input: Slicing list T\mathcal{L}^{T}, Λmi\Lambda^{i}_{m} minimum bit rate requirement for each user belonging to mvno mm, vcv^{c} achievable bit rate with MCS level cCc\in C, maximum allowable throughput for a MVNO Λm¯,m\overline{\Lambda_{m}},\forall m, the maximum mcs that can be supported by a resource block at TTI tt, qr,tq^{r,t}.

Output: Set of allocated RBs RR^{*} and MCS level CC^{*}, for each user in T\mathcal{L}^{T}.

1:Initialize R=ϕR^{*}=\phi and C=ϕC^{*}=\phi
2:Initialize already allocated RBs, R^=ϕ\hat{R}=\phi
3:Total RBs, RtotR_{tot}
4:for each user, umiu_{m}^{i} in T\mathcal{L}^{T} do
5:    current data rate for each user, dmi=ϕd_{m}^{i}=\phi
6:    current data rate for each MVNO, dm=ϕd_{m}=\phi
7:    if dmλmd_{m}\geq\lambda_{m} then
8:         break     
9:    for each MCS, c=Cmax,,1c=C_{max},\dots,1 do
10:         list to hold each TTI information, At=ϕA^{t}=\phi
11:         if R^Rtot=ϕ\hat{R}\cap R_{tot}=\phi then
12:             return “No solution”          
13:         for t=0,,Tt=0,\dots,T do
14:             maximum data rate at tti t ht=ϕh^{t}=\phi
15:             for c~=Cmax,,c\tilde{c}=C_{max},\dots,c do
16:                 candidate RB for MCS c~\tilde{c}, Rcan=ϕR_{can}=\phi
17:                 for rRtotr\in R_{tot} do
18:                     if rR^=ϕr\cap\hat{R}=\phi and qr,tc~q^{r,t}\geq\tilde{c} then
19:                         Rcan=RcanrR_{can}=R_{can}\cup r
20:                         if Rcan×vc>htR_{can}\times v^{c}>h^{t} then
21:                             ht=Rcan×vch^{t}=R_{can}\times v^{c}
22:                             R=Rcan,c=c~R^{\prime}=R_{can},c^{\prime}=\tilde{c}                                                                             
23:             add tuple δit=<c,R,ht>\delta^{t}_{i}=<c^{\prime},R^{\prime},h^{t}> to the list AtA^{t}          
24:         sort AtA^{t} based on decreasing order of cc^{\prime}
25:         for each tuple δit\delta_{i}^{t} in AtA^{t} do
26:             hu=hu+δit[ht]h_{u}=h_{u}+\delta_{i}^{t}[h^{t}]
27:             Ru=Ruδit[R]R_{u}=R_{u}\cup\delta_{i}^{t}[R^{\prime}]
28:             cu=cuδit[c]c_{u}=c_{u}\cup\delta_{i}^{t}[c^{\prime}]
29:             if huΛmih_{u}\geq\Lambda_{m}^{i} then
30:                 R=RRuR^{*}=R^{*}\cup R_{u}, R^=R^R\hat{R}=\hat{R}\cup R^{*}
31:                 C=CcuC^{*}=C^{*}\cup c_{u}
32:                 U=U+1U=U+1
33:                 break                           
34:return UU, RR^{*} and CC^{*}

VI-C Time Complexity

We will now discuss the complexity of MaRS algorithm. To compute the maximum data rate for a user at each TTI, the time complexity is O(|C||Rtot|)O(|C||R_{tot}|). We need to compute this for the each TTI tTt\in T. Therefore, the total time complexity to compute maximum data rate for a user in time TT is, O(|T||C||Rtot|)O(|T||C||R_{tot}|). After that, we sort maximum data rate achieved across TTIs. The sorting operation in represented in Line 24 which has the complexity of O(|T||logT|)O(|T||logT|). Now, we iterate over each element in the sorted list to meet the data rate requirement, O(|T|)O(|T|). Then MaRS algorithm allocates the optimal resources RuR_{u} and chooses its MCS cuc_{u} for each user across TTI if possible for the current MCS cc. Therefore the total complexity for each iteration of cc is O(|T||C||Rtot|)+O(|T||logT|)+O(|T|)=O(|T||C||Rtot|)O(|T||C||R_{tot}|)+O(|T||logT|)+O(|T|)=O(|T||C||R_{tot}|). Since there are |C||C| possible values of cc, the complexity is O(|T||C|2|Rtot|)O(|T||C|^{2}|R_{tot}|). Now MaRS algorithm calculates this for every user in |LT||L^{T}|. Therefore, the total time complexity of MaRS algorithm is O(|LT||T||C|2|Rtot|)O(|L^{T}||T||C|^{2}|R_{tot}|).

Theorem 2.

If there exists a feasible solution for any given user in T\mathcal{L}^{T}, Algorithm 2 will find it.

Proof.

As discussed in the previous section, for each user, Algorithm 2, calculates the maximum achievable data rate for each TTI tTt\in T. The algorithm goes over every possible combination of the resource blocks and MCS to determine this data rate. Once the algorithm generates AtA^{t}, the maximum achievable data rate for a user at each TTI, it proceeds with RB allocation. Now, as long as the sum of the data rates in AtA^{t} is greater than minimum user data rate requirement, the algorithm provides a solution. That is, given a finite set of unallocated RB and a user umiu^{i}_{m} with minimum data rate requirement of Λmi\Lambda_{m}^{i},

δitAtδit[ht]Λmi\displaystyle\sum_{\forall\delta_{i}^{t}\in A^{t}}{\delta_{i}^{t}[h^{t}]}\geq\Lambda_{m}^{i} (14)

the algorithm will find sub set of RB and corresponding MCS across TT which meet Λmi\Lambda_{m}^{i} as long as equation (14) is met. ∎

VII Performance Bound

As proven in Theorem 1, the MaRS problem is NP-hard and it is not feasible to find a polynomial-time optimal solution. Therefore, it is vital to develop an upper bound for the objective function defined in Exp. (2). This upper bound can be used as a benchmark to measure the performance of the scheduling algorithm that we presented in section V.

When RR, the maximum number of resource blocks in time TT is given, our problem aims to find a subset of RR for each user. Choice of this subset depends on cc, the MCS selected for them. Note that, if we want to maximize Exp. (2), we need to find a subset which contains least amount of RBs.

Since we want to find an upper bound for objective function in Exp. (2) , let us consider a fictitious scenario of excellent channel condition for every user in time TT. Therefore, every resource block rRr\in R, can support the maximum MCS value that a user can support during its allocation. That is,

qumimax=maxr,tqumir,t.\displaystyle q_{u^{i}_{m}}^{\max}=\max_{r,t}\ q_{u^{i}_{m}}^{r,t}. (15)

We further consider that the MVNO scheduler always uses the maximum MCS for each user. That is,

dumir,c,t=qumimax\displaystyle d_{u^{i}_{m}}^{r,c,t}=q_{u^{i}_{m}}^{\max} (16)

We then proceed with the allocation of the resource blocks for each user following the slicing list, t\mathcal{L}^{t}. In this fictitious scenario, the data rate achievable for each user in time TT, is directly proportional to the number of resource blocks allocated to it at time TT. Therefore, we can re-write constraints (7), (8) as,

tTrRxmr,i,t×dumir,c,tumiΛmi,m,i\displaystyle\sum_{t\in T}\sum_{r\in R}x^{r,i,t}_{m}\times d_{u^{i}_{m}}^{r,c,t}\geq u^{i}_{m}\Lambda_{m}^{i},\forall m,i (17)
tTrRumiUmxmr,i,t×dumir,c,tΛm¯,m\displaystyle\sum_{t\in T}\sum_{r\in R}\sum_{u^{i}_{m}\in U_{m}}x^{r,i,t}_{m}\times d_{u^{i}_{m}}^{r,c,t}\leq\overline{\Lambda_{m}},\forall m (18)

We can see that, the criterion to meet each user’s minimum data rate requirement completely depends on number of resource blocks allocated to it. Since we assume the maximum MCS level for each resource block, any allocation of the resource block with MCS dumir,c,td_{u^{i}_{m}}^{r,c,t}, for a user to meet Λmi\Lambda_{m}^{i} would use least amount of resource blocks. Therefore, if we use the least amount of resource blocks for every user, we can find the maximum users that can be supported by the given set of resource blocks RR for time slot TT.

In this section, we developed a very intuitive based upper performance bound for the MaRS algorithm. In the following section, we perform simulations of this upper bound and compare the performance of MaRS algorithm with it.

VIII Performance Evaluation

In this section, we assess the performance of the MaRS algorithm proposed in Section VI. We evaluate MaRS algorithm in terms of its ability to achieve our objective function of maximizing the users served by varying various 5G network parameters. We use the upper bound developed in section VII as the benchmark for this purpose.

Network Setting

We simulate an 5G NR base station deployed in a certain environment serving 𝒩\mathcal{N} number of users. This BS and user deployment can be modeled using any standard approaches such as hexagonal, square lattice or stochastic geometry based Poisson Point process [35]. We consider this BS to be operating as frequency division duplexing(FDD) system with a channel bandwidth of 20MHz, which is divided into 1200 subcarriers organized into Rtot=R_{tot}=100 RB. while considering sub-carrier spacing of 15Khz. Each PRB represents the minimum scheduling unit and consists of 12 subcarriers and 14 symbols.

For each user in the network, the expected channel condition (in terms of MCS) is randomly chosen. For each MCS cc, the modulation and the coding rate vc,tv^{c,t} is obtained from [36].

Configurable Parameters. There are many configurable system parameters such as the time slot TT, number of MVNO MM, users of each MVNO umiu^{i}_{m}, minimum data rate for each user λmi\lambda_{m}^{i}, the maximum throughput allocated per MVNO slice by NO Λm\Lambda_{m}. We evaluate the performance of MaRS algorithm under various combination of these settings.

The number of users served in the time slot TT would be the sole performance metric for all our simulation settings.

Results

In this section, we evaluate the proposed algorithm against the upper bound against varying parameters.

Varying Channel Propagation. We first evaluate the performance of MaRS algorithm under channels with varying LOS signal strength. We assume Rician fading channel with no frequency and time correlation.

Refer to caption
Figure 4: MaRS algorithm Performance under different Rician factors.

Fig. 4 compares the performance of MaRS algorithm against the upper bound for different Rician factor KK. The configuration used for the experiments is listed in Table. II.

Time Slot, TT 5
Number of MVNOs, MM 2
Number of users per MVNO, umiu_{m}^{i} 10
Minimum Throughput required per user, Λmi\Lambda_{m}^{i} 50 Mb/Slot
Maximum allowed throughput per MVNO slice, Λm¯\overline{\Lambda_{m}} 500 Mb/slot
TABLE II: Simulation Parameters - varying channel propagation.

Under this configuration, we can see that MaRS algorithm can achieve near-optimal performance. In particular, when the Rician factor K=0K=0 (i,e. Rayleigh fading), 4 and 8, the number of users served by the MaRS algorithm is within  10% of the respective upper bound. For K=8K=8, the performance of MaRS algorithm is as good as the upper bound. This can be attributed towards the higher availability of resources that can be allocated to fewer number of users.

Varying Time Slot TT. We now evaluate MaRS algorithm by varying the slice time slot. Increasing the time slot TT, increases the available resources to meet slice requirements per TT. Therefore, for this experiment, we increase the minimum data rate requirement for each user while also increasing the maximum available throughput. We consider Rayleigh fading to model the channel and generate MCS values for each user.

TT 20,50,100
MM 2
umiu_{m}^{i} 10
Λmi\Lambda_{m}^{i} 100 Mb/Slot
Λm¯\overline{\Lambda_{m}} 5 Gb/slot
TABLE III: Simulation Parameters - varying slice slot time TT.
Refer to caption
Figure 5: MaRS algorithm performance under different Time Slot TT.

Fig. 5 shows the performance of the MaRS algorithm in comparison with the upper bound. Clearly increasing the number of available resources, increases the performance of the MaRS algorithm. This is evident in Fig 5 for T=100T=100 TTIs, where MaRS algorithm catches up with the upper bound in terms of number of users served across MVNOs.

Varying other simulation parameters. We now vary other system parameters to evaluate MaRS algorithm performance. We understand the behaviour of MaRS algorithm by considering three scenarios of the network configurations as shown in Table IV for our simulations. We assume Rayleigh fading channels for all the simulations.

Scenario 1 Scenario 2 Scenario 3
TT 50 50 50
MM 3 2 3
umiu_{m}^{i} 15 10 5
Λmi\Lambda_{m}^{i} 100 Mb/Slot 100 Mb/Slot 50 Mb/Slot
Λm¯\overline{\Lambda_{m}} 5 Gb/slot 5 Gb/slot 5 Gb/slot
TABLE IV: Simulation Parameters - 3 network scenarios.
Refer to caption
Figure 6: MaRS algorithm performance comparison for 3 scenarios.
Refer to caption
Figure 7: MaRS algorithm performance comparison for 3 scenarios with random data rate for each user.

In Fig. 6, Scenario 1 represents a network scenario where there are many users with high minimum data rate requirement and few resources to allocate them. Here, we can see that MaRS algorithm is within  5% of the upper bound. In Scenario 2, we decrease the load on the base station by reducing the number of MVNOs and users. Even in this case, we can see MaRS algorithm achieves near-optimal performance. Finally in Scenario 3, where the number of resource blocks are plenty, we see that MaRS algorithm performs as well as the upper bound. Further, we also tried varying the data rate requirement for each user in the network under these 3 scenarios(Fig 7).We choose a random data rate for each user between 10 Mb/Slot to 150 Mb/slot, the results obtained is similar to the previous case where the data rate is fixed.

Fast changing channel. Until now, we have considered time correlation for each user in the network where the channel conditions remains constant for each user in time slot TT. We now consider a network scenario where the channel conditions for each user changes at each TTI. We still assume Rayleigh fading channels with no frequency correlation. Table V shows the settings used for this evaluation.

TT 20,50,100
MM 2
umiu_{m}^{i} 30
Λmi\Lambda_{m}^{i} 10 Mb/Slot
Λm¯\overline{\Lambda_{m}} 250 Mb/slot
TABLE V: Simulation Parameters - fast changing channel.
Refer to caption
Figure 8: MaRS algorithm performance for fast changing channels.

Fig 8, represents the obtained results. We can see that MaRS algorithm performance is with in  5% of the upper bound. As mentioned in the earlier section, we have developed the MaRS algorithm and evaluated its performance for near real-time and non-real-time configuration of the Ran Intelligent Controller (RIC) in O-RAN architecture. By demonstrating that MaRS algorithm’s performance is near optimal, we can say MaRS algorithm is a viable option for deployment for non-real-time and near-real-time RIC.

RB Utilization. Finally, we evaluate the performance of MaRS algorithm in terms of number of RB utilized to serve the users across all MVNOs in the networks. We say a user is served when its minimum data rate is met at time slot TT. We measure the number of RB utilized to serve users in 3 scenarios presented earlier under different MCS selection criterion. MCS selection criterion:

  • Maximum MCS: We assume that each RB in TT for a user can support the maximum MCS.

  • Average MCS: We calculate the average MCS level for a user across TT and assume that each RB in TT supports this average value.

  • Lowest MCS: We calculate the lowest MCS level for a user across TT and assume that each RB in TT can only support the lowest value.

Refer to caption
Figure 9: Comparison of MaRS algorithm against static allocation algorithms for RB utilization.

Fig 9 shows the obtained results. It is evident that the Maximum MCS selection criteria uses the least amount of resource blocks to serve users. This is understandable as we assume the best channel conditions for all RBs. But, there may be significant re-transmissions which would increase latency. However, The performance of MaRS algorithm out performs Average MCS and Lowest MCS selection criteria. There is a significant decrease in the number of resource blocks used to serve the users using MaRS algorithm when compared to these criteria. Therefore, using MaRS algorithm we can serve more users in a time slot TT than using Lowest MCS and Average MCS static algorithms.

IX CONCLUSIONS

In this paper, we investigated the problem of RAN slicing in multi-MVNO environment with varied users having minimum data rate requirement as a specification for the users. First, we discussed the SD-RAN architecture and discussed its operation flow. Then, we formulated the MCS-aware RAN Slicing (MaRSP) problem as optimization problem with an objective function to increase the number of supported users at each time slot TT. We proved that MaRSP problem is NP-Hard. Next, we developed the novel MCS-aware RAN Slicing (MaRS) algorithm where we maximize the data rate for each user at each TTI and assign resources to it based on a greedy paradigm. We also showed that the MaRS algorithm has a polynomial time complexity. Following that, we developed a upper performance bound for the MaRS algorithm by considering no frequency and time correlation. Finally, we carry out thorough evaluation of the MaRS algorithm under various network and channel scenarios. Results conclude that the proposed slicing algorithm achieves near-optimal performance when compared with the upper bound. Through various simulation settings, we have also shown that MaRS algorithm is easily scalable. In compliance with the O-RAN architecture, we have seen through results that MaRS algorithm can be applied to non-real-time and near-real-time RIC deployments. Using RB utilization as a metric, we have compared the performance of MaRS algorithm with other static allocation algorithms. We see that MaRS algorithm outperforms many static allocation algorithms by using least amount of resource blocks to serve minimum data rate requirement for each user.

References

  • [1] Ericsson Incorporated. Ericsson mobility report, nov 2019 https://www.ericsson.com/4acd7e/assets/local/mobility-report/documents/2019/emr-november-2019.pdf,2019.
  • [2] Ltd Samsung Electronics Co. Technical report: 5g core vision, 2019 https://image-us.samsung.com/SamsungUS/samsungbusiness/pdfs/5G_Core_Vision_Technical_Whitepaper.pdf,2019.
  • [3] I. da Silva, G. Mildh, A. Kaloxylos, P. Spapis, E. Buracchini, A. Trogolo, G. Zimmermann, and N. Bayer. Impact of network slicing on 5g radio access networks. In 2016 European Conference on Networks and Communications (EuCNC), pages 153–157, 2016.
  • [4] I. Afolabi, T. Taleb, K. Samdanis, A. Ksentini, and H. Flinck. Network slicing and softwarization: A survey on principles, enabling technologies, and solutions. IEEE Communications Surveys Tutorials, 20(3):2429–2453, 2018.
  • [5] X. Li, M. Samaka, H. A. Chan, D. Bhamare, L. Gupta, C. Guo, and R. Jain. Network slicing for 5g: Challenges and opportunities. IEEE8407021 Internet Computing, 21(5):20–27, 2017.
  • [6] Salvatore D’Oro, Francesco Restuccia, and Tommaso Melodia. Toward operator-to-waveform 5g radio access network slicing. CoRR, abs/1905.08130, 2019.
  • [7] Tchiumento, a., bennis, m., desset, c. et al. adaptive csi and feedback estimation in lte and beyond: a gaussian process regression approach. j wireless com network 2015, 168 (2015). https://doi.org/10.1186/s13638-015-0388-0.
  • [8] A. Papa, M. Klugel, L. Goratti, T. Rasheed, and W. Kellerer. Optimizing dynamic ran slicing in programmable 5g networks. In ICC 2019 - 2019 IEEE International Conference on Communications (ICC), pages 1–7, 2019.
  • [9] Salvatore D’Oro, Francesco Restuccia, Alessandro Talamonti, and Tommaso Melodia. The slice is served: Enforcing radio access network slicing in virtualized 5g systems. In IEEE INFOCOM 2019-IEEE Conference on Computer Communications, pages 442–450. IEEE, 2019.
  • [10] A. Kaloxylos. A survey and an analysis of network slicing in 5g networks. IEEE Communications Standards Magazine, 2(1):60–65, 2018.
  • [11] C. Chang, N. Nikaein, and T. Spyropoulos. Radio access network resource slicing for flexible service execution. In IEEE INFOCOM 2018 - IEEE Conference on Computer Communications Workshops (INFOCOM WKSHPS), pages 668–673, 2018.
  • [12] O. Sallent, J. Perez-Romero, R. Ferrus, and R. Agusti. On radio access network slicing from a radio resource management perspective. IEEE Wireless Communications, 24(5):166–174, 2017.
  • [13] Alcardo Barakabitze, Arslan Ahmad, Andrew Hines, and Rashid Mijumbi. 5g network slicing using sdn and nfv: A survey of taxonomy, architectures and future challenges. Computer Networks, 167:106984, 11 2019.
  • [14] M. Chahbar, G. Diaz, A. Dandoush, C. Cérin, and K. Ghoumid. A comprehensive survey on the e2e 5g network slicing model. IEEE Transactions on Network and Service Management, pages 1–1, 2020.
  • [15] R. Wen and G. Feng. Robust RAN Slicing, pages 189–208. 2021.
  • [16] Xenofon Foukas, Mahesh Marina, and Kimon Kontovasilis. Orion: Ran slicing for a flexible and cost-effective multi-service mobile network architecture. pages 127–140, 10 2017.
  • [17] K. Samdanis, S. Wright, A. Banchs, A. Capone, M. Ulema, and K. Obana. 5g network slicing - part 1: Concepts, principles, and architectures. IEEE Communications Magazine, 55(5):70–71, 2017.
  • [18] R. Ferrus, O. Sallent, J. Perez-Romero, and R. Agusti. On 5g radio access network slicing: Radio interface protocol features and configuration. IEEE Communications Magazine, 56(5):184–192, 2018.
  • [19] X. Foukas, G. Patounas, A. Elmokashfi, and M. K. Marina. Network slicing in 5g: Survey and challenges. IEEE Communications Magazine, 55(5):94–100, 2017.
  • [20] Tengteng Ma, Yong Zhang, Fanggang Wang, Dong Wang, and Da Guo. Slicing resource allocation for embb and urllc in 5g ran. Wireless Communications and Mobile Computing, 2020:1–11, 01 2020.
  • [21] Aditya Gudipati, Li Li, and Sachin Katti. Radiovisor: A slicing plane for radio access networks. 08 2014.
  • [22] W. Wu, N. Chen, C. Zhou, M. Li, X. Shen, W. Zhuang, and X. Li. Dynamic ran slicing for service-oriented vehicular networks via constrained learning. IEEE Journal on Selected Areas in Communications, pages 1–1, 2020.
  • [23] Mustufa Abidi, Hisham Alkhalefah, Khaja Moiduddin, Mamoun Alazab, Muneer Khan Mohammed, Wadea Ameen, and Thippa Gadekallu. Optimal 5g network slicing using machine learning and deep learning concepts. Computer Standards & Interfaces, 76:103518, 01 2021.
  • [24] Anurag Thantharate, Rahul Paropkari, Vijay Walunj, and Cory Beard. Deepslice: A deep learning approach towards an efficient and reliable network slicing in 5g networks. 10 2019.
  • [25] H. Xiang, S. Yan, and M. Peng. A realization of fog-ran slicing via deep reinforcement learning. IEEE Transactions on Wireless Communications, 19(4):2515–2527, 2020.
  • [26] P. Korrai, E. Lagunas, S. K. Sharma, S. Chatzinotas, A. Bandi, and B. Ottersten. A ran resource slicing mechanism for multiplexing of embb and urllc services in ofdma based 5g wireless networks. IEEE Access, 8:45674–45688, 2020.
  • [27] Yasir Zaki, Liang Zhao, Carmelita Görg, and Andreas Timm-Giel. Lte mobile network virtualization. Mobile Networks & Applications, 16:424–432, 08 2011.
  • [28] Y. Zaki, Liang Zhao, C. Goerg, and A. Timm-Giel. Lte wireless virtualization and spectrum management. In WMNC2010, pages 1–6, 2010.
  • [29] M. Li, L. Zhao, X. Li, X. Li, Y. Zaki, A. Timm-Giel, and C. Gorg. Investigation of network virtualization and load balancing techniques in lte networks. In 2012 IEEE 75th Vehicular Technology Conference (VTC Spring), pages 1–5, 2012.
  • [30] Xenofon Foukas, Navid Nikaein, Mohamed M. Kassem, Mahesh K. Marina, and Kimon Kontovasilis. Flexran: A flexible and programmable platform for software-defined radio access networks. In Proceedings of the 12th International on Conference on Emerging Networking EXperiments and Technologies, CoNEXT ’16, page 427–441, New York, NY, USA, 2016. Association for Computing Machinery.
  • [31] ETSI. Ts 38 211 - v15.4.0 - 5g; nr; physical channels and modulation (3gpp ts 38.211 version 15.4.0 release 15).
  • [32] ORAN Alliance. O-ran: Towards an open and smart ran.
  • [33] ORAN Alliance. Oran-wg2.aiml.v01.00 o-ran working group 2 ai/ml workflow description and requirements.
  • [34] John R Rice. Complexity of computer computations (raymond e. miller and james w. thatcher, eds.). SIAM Review, 16(3):407–409, 1974.
  • [35] S. M. Yu and S. Kim. Downlink capacity and base station density in cellular networks. In 2013 11th International Symposium and Workshops on Modeling and Optimization in Mobile, Ad Hoc and Wireless Networks (WiOpt), pages 119–124, 2013.
  • [36] ETSI. Ts 138 214 - v15.3.0 - 5g;nr;physical layer procedures for data; (3gpp ts 38.214 version 15.3.0 release 13).