from Part III - Resource Allocation and Networking in C-RANs
Published online by Cambridge University Press: 23 February 2017
Introduction
In the wireless network literature, scheduling denotes the strategy according to which users are active at each time-frequency resource block. In this classical literature, scheduling is done per base station (BS), i.e., without coordination between the BSs. With the large demand for mobile data services that is straining wireless networks nowadays, coordination among transmitters becomes a real necessity to better manage the high levels of interference.
The C-RAN architecture is a practical platform for the implementation of coordinated multi-point (COMP) systems. By connecting all BSs to a central computing center (i.e., a cloud) via wire or wireless backhaul links, C-RAN allows joint signal processing and coordinated resource allocation at the cloud. Depending on the capacity of the connecting backhaul, the level of coordination among the BSs may vary from a high coordination level (e.g., signal-level coordination as in fiber optic high-capacity backhaul links) to a low coordination level (e.g., resource allocation coordination as in wireless backhaul links). In situations where optical fiber backhaul links are unavailable at the exact location of a BS, or when the extension of optical fiber cables to the base station location is prohibitively expensive, wireless backhauls become a cheaper and easier-to-deploy solution. Intelligently devising schemes for the coordination of resource allocation in a C-RAN setup is, therefore, a real necessity for providing a practical, reliable, and scalable solution to the impending capacity crunch.
From the recent literature, coordinated resource allocation can be classified into three categories:
• coordinated beamforming;
• coordinated power control;
• coordinated scheduling.
While adjustment of the continuous variables (i.e., the beamforming vectors and the power) typically requires high-resolution algorithms and sensitive hardware physical platforms, discrete allocation (i.e., scheduling) is considered a more practical resource-allocation solution. Scheduling problems are, nevertheless, discrete optimization problems which may be often NP-hard problems. This chapter provides a framework for solving coordinated scheduling problems in C-RANs, using graph theory practical techniques that perform close-to-optimal solutions.
In conventional cellular network architecture, scheduling policies are often performed per base station given a pre-known association of users and base stations, e.g., the classical proportionally fair scheduling [1, 2]. One point illustrated in this chapter is that coordinated scheduling not only allows assigning users to resource blocks across the network but also jointly solves for the user-to-BS association problem.
To save this book to your Kindle, first ensure no-reply@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.
Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.
Find out more about the Kindle Personal Document Service.
To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.
To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.