z-logo
open-access-imgOpen Access
Simple Tight Performance Bound Based on the GFBT for Binary Linear Codes
Author(s) -
Jia Liu,
Mingyu Zhang,
Rongjun Chen,
Chaoyong Wang,
Xin An,
Yufei Wang
Publication year - 2020
Publication title -
iop conference series. earth and environmental science
Language(s) - English
Resource type - Journals
eISSN - 1755-1307
pISSN - 1755-1315
DOI - 10.1088/1755-1315/428/1/012028
Subject(s) - upper and lower bounds , decoding methods , mathematics , simple (philosophy) , bounding overwatch , binary number , hamming distance , hamming code , combinatorics , additive white gaussian noise , algorithm , list decoding , binary code , discrete mathematics , computer science , white noise , concatenated error correction code , block code , statistics , arithmetic , mathematical analysis , philosophy , epistemology , artificial intelligence
A simple tight upper bound, without any integral and optimal operations in its final version, is proposed over additive white Gaussian noise (AWGN) channels. We derive the simple bound both on the frame probability and on the bit error probability. The proposed bound is within the framework of Gallager’s first bounding technique (GFBT), in which the Gallager region is chosen by the hamming distance, avoiding the limitation of the Euclidean distance. To compute the upper bound inside the Gallager region, we can tighten the union bound not only by collecting more information about the receiving vector which can cause the maximum-likelihood (ML) decoding error events, but also by employing the independence between the ML decoding error events and some positions of the received vectors. The proposed bound is tight since numerical results show that it is tighter than the proposed bound by Divsalar (without any integral and optimal operations) and the proposed bound by Poltyrev (considered as one of the tightest upper bounds for the binary linear codes with lower rate).

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here