Skip to main navigation Skip to search Skip to main content

On receiver design for uplink low density signature OFDM (LDS-OFDM)

  • Razieh Razavi
  • , Mohammed Al-Imari
  • , Muhammad Ali Imran
  • , Reza Hoshyar
  • , Dageng Chen
  • University of Surrey
  • Texas Instruments
  • Huawei Technologies Co., Ltd.

Research output: Contribution to journalArticlepeer-review

98 Scopus citations

Abstract

Low density signature orthogonal frequency division multiplexing (LDS-OFDM) is an uplink multi-carrier multiple access scheme that uses low density signatures (LDS) for spreading the symbols in the frequency domain. In this paper, we introduce an effective receiver for the LDS-OFDM scheme. We propose a framework to analyze and design this iterative receiver using extrinsic information transfer (EXIT) charts. Furthermore, a turbo multi-user detector/decoder (MUDD) is proposed for the LDS-OFDM receiver. We show how the turbo MUDD is tuned using EXIT charts analysis. By tuning the turbo-style processing, the turbo MUDD can approach the performance of optimum MUDD with a smaller number of inner iterations. Using the suggested design guidelines in this paper, we show that the proposed structure brings about 2.3 dB performance improvement at a bit error rate (BER) equal to 10^{-5} over conventional LDS-OFDM while keeping the complexity affordable. Simulations for different scenarios also show that the LDS-OFDM outperforms similar well-known multiple access techniques such as multi-carrier code division multiple access (MC-CDMA) and group-orthogonal MC-CDMA.

Original languageEnglish
Article number6294411
Pages (from-to)3499-3508
Number of pages10
JournalIEEE Transactions on Communications
Volume60
Issue number11
DOIs
StatePublished - 2012
Externally publishedYes

Keywords

  • Code division multi access
  • Iterative methods
  • Multi access communication
  • Multi-user channels

Fingerprint

Dive into the research topics of 'On receiver design for uplink low density signature OFDM (LDS-OFDM)'. Together they form a unique fingerprint.

Cite this