Re: Error rate probability





"Keith A. Lewis" wrote:
>
> "jan hauben" <jan.hauben@xxxxxxxxxx> writes in article <dviwe.132562$ej.7213120@xxxxxxxxxxxxxxxxxxxxx> dated Tue, 28 Jun 2005 20:34:17 GMT:
> >in general :
> >one extra bit can detect one fault (like parity-bit)
>
> True for any size frame.
>
> >two extra bits can correct one fault bit
>
> Certainly for a single bit. But for 2 data bits + 2 check bits, you can
> have 4 different single-bit errors, or no error at all (a 5th case). So you
> would need more than 2 bits to correct them all.
>
> Let
> N = data bits
> C = check bits
> E = maximum expected errors in (n+c) frame
>
> You need
> sum(choose(N+C,i),i=1..E) <= 2^C
>
> See "Hamming Codes" for more info.
>
> >if a little mistake is acceptable, one can use gray-code
>
> Gray code is useful in circuits where you want only 1 bit to change at a
> time, for whatever reason. I don't understand what use that would be in
> error detection.

Gray coding prevents excessive biterrors in a bitstream. As an example, with QAM (Quadrature
Amplitude Modulation) the data is send in packages of N bits which are called symbols. All 2^N
possible symbols can be represented as a 2-D grid (the symbol constellation), such that each symbol
has neighbour symbols. Due to an error vector in the communcations channel, it is possible that the
receiver decides that one of the neighbouring symbols was sent instead of the truly sent symbol
itself. If the symbol constellation is Gray-coded such that neigbouring symbols only differ by one
bit, it is likely that if an error occurs only a single bit error occurs. If the symbol
constellation is not Gray-coded, then you'll get multiple bit-errors in the described case.

Jeroen


>
> --Keith Lewis klewis {at} mitre.org
> The above may not (yet) represent the opinions of my employer.
.



Relevant Pages

  • Re: 100% repeatable crashes on 6.2-RELEASE-p3 (bt full)
    ... klon# kgdb kernel.debug /var/crash/vmcore.0 ... Fatal trap 12: page fault while in kernel mode ... frame pointer = 0x28:0xcc76fa78 ...
    (freebsd-stable)
  • Re: Amd64 Unstable Areca
    ... Copyright 2004 Free Software Foundation, ... GDB is free software, covered by the GNU General Public License, and you are ... page fault while in kernel mode ... #16 0xffffffff8063af81 in syscall (frame= ...
    (freebsd-stable)
  • Re: Strange panics
    ... The box runned two jails without any flaws for several weeks, after adding third one it begins to panics at least once a day. ... CPU: IntelXeonCPU 2.80GHz ... page fault while in kernel mode ... #12 0xc084a613 in syscall (frame= ...
    (freebsd-stable)
  • Bug in FAST IPSEC pfkey interaction ...
    ... I have encountered a bug while doing some testing using the ike daemon that is bundled with the client software that I posted recently on this list. ... The daemon is multi threaded and tends to stress the pfkey interface a bit more than racoon by submitting batches of pfkey messages in rapid sequence when adding or removing client security policy. ... This triggers a page fault in netipsec/key.c key_spddelete2. ... #17 0xffffffff804c2531 in syscall (frame= ...
    (freebsd-net)
  • Strange panics
    ... The box runned two jails without any flaws for several weeks, after adding third one it begins to panics at least once a day. ... CPU: IntelXeonCPU 2.80GHz ... page fault while in kernel mode ... #12 0xc084a613 in syscall (frame= ...
    (freebsd-stable)