Tariq, Faisal; Dooley, Laurence S. and Poulton, Adrian
Due to copyright restrictions, this file is not available for public download
Click here to request a copy from the OU Author.
|Google Scholar:||Look up in Google Scholar|
Femtocells are primarily used to extend high-quality radio coverage in indoor environments. Dense femtocell access point (FAP) deployment however, can lead to severe interference on femtocell user equipment (FUE) from neighbouring FAP, when they operate on the same channel. The problem is compounded as FAP are deployed in an uncoordinated manner by the end-user, which means either avoiding or minimising interference is an essential prerequisite to achieve successful femtocell operation. This paper adopts a new strategy towards radio resource distribution and management by creating virtual clusters of femtocells which are managed by a logical entity called the Virtual Cluster Controller(VCC). Each VCC is situated between the FAPs and Radio Network Controller (RNC) and has a set of sub-channels which it can allocate amongst its members. A Virtual Cluster Formation (VCF) algorithm exploits location information to assign each FAP to a VCC so that the minimum distance between a FAP and the nearest FAP allocated to the same VCC is maximised, thereby ensuring minimal inter-FAP interference. Simulation results corroborate the significant performance improvement achieved by this virtual clustering model in terms of both interference minimisation and throughput for various FAP deployment scenarios.
|Item Type:||Conference Item|
|Copyright Holders:||2011 IEEE|
|Extra Information:||ISBN: 978-963-8111-77-7; ISBN: 978-963-8111-76-0; Article No:1569475985|
|Keywords:||femtocell; virtual cluster; hybrid resource management; two-tier system|
|Academic Unit/Department:||Mathematics, Computing and Technology > Computing & Communications|
|Interdisciplinary Research Centre:||Centre for Research in Computing (CRC)|
|Depositing User:||Faisal Tariq|
|Date Deposited:||30 Sep 2011 13:58|
|Last Modified:||10 Dec 2012 22:17|
Actions (login may be required)
|Report issue / request change|