RE: stds-802-16: RS encode example
Actually, Ron, I worked through the example for the RS encoder, which Leo
refered to, and I found that what was given in the P802.16a/D7-2002 document
on p. 159 to be correct. I did get the same parity byte information.
What was incorrect was the interleaving example, for which a correction has
already been included in the P802.16d/d2 draft.
Jon
-----Original Message-----
From: owner-stds-802-16@majordomo.ieee.org
[mailto:owner-stds-802-16@majordomo.ieee.org]On Behalf Of Ron Murias
Sent: Monday, July 14, 2003 10:33 PM
To: stds-802-16@ieee.org; Roger B. Marks
Subject: Re: stds-802-16: RS encode example
Several of us have completed and are currently reviewing corrections for the
mistakes you mention and will submit those corrections within the next two
days.
----- Original Message -----
From: "Roger B. Marks" <r.b.marks@ieee.org>
To: <stds-802-16@ieee.org>
Sent: Monday, July 14, 2003 11:43 AM
Subject: stds-802-16: RS encode example
> {Forwarded for a nonsubscriber.}
>
> >Did anyone out there actually work through the coding example listed in
> >p.159 of P802.16a/D7-2002 document? I found the original document
"Example
> >Uplink Encoding" (IEEE802.16abc-01/54) produced by Mike Puff where the
> >coding example is first provided. I noticed the 2 examples do not match
and
> >I could not obtain the same check symbols as either of the Reed-solomon
> >encoded data. I followed the guideline on how to obtain shorten and
> >punctured code listed in 8.4.3.2.1
> >
> >Please advice.
> >
> >Thx.
> >
> >Zhiqun (Leo) Liu
> >KatanaMe, Inc.
> >345 Shoreway Road
> >San Carlos, CA 94070
> >Tel: 650-593-2294
> >Fax: 650-593-2296
> >zliu@kataname.com
>