Re: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

[Sean Cai <scai@ZTESANDIEGO.COM>]

Title: RE: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

Hi Ran,

Sorry, I meant "If ConstantSets are defined in odd numbers" in the text.

Regards,

Sean

-----Original Message-----
From: owner-stds-802-16-mobile@listserv.ieee.org [mailto:owner-stds-802-16-mobile@listserv.ieee.org] On Behalf Of Sean Cai
Sent: Friday, October 29, 2004 4:58 PM
To: STDS-802-16-MOBILE@listserv.ieee.org
Subject: Re: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

Hi Ran,

Once Comment#342 is accepted then it will be automatically adopted in

16e. Therefore I don't think you need to submit another one in TGe.

If you take a look at Table 309, VariableSets are defined in even

subcarrier numbers. If ConstantSets are defined in even numbers, then

Vriable and Constant Sets will never be overlapping.

Regards,

Sean

-----Original Message-----

From: Ran Yaniv [mailto:ran.yaniv@alvarion.com]

Sent: Friday, October 29, 2004 3:20 PM

To: 'scai@ztesandiego.com'

Subject: RE: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

Hi Sean,

Thanks, I looked at comment #342, and it addresses the problem. A

similar

comment should be submitted to TGe for the sub-2K FFT modes. I can

submit a

comment of this nature.

btw, in comment #342 you mention that "odd numbers are preferred for

Constant Set". why is that?

Regards,

Ran

-----Original Message-----

From: Sean Cai [mailto:scai@ztesandiego.com]

Sent: Fri 29 October 2004 23:13

To: Ran Yaniv; STDS-802-16-MOBILE@listserv.ieee.org

Subject: RE: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

Hi Ran,

We have noticed this problem in the D5, and have submitted the comment

(Comment# 342) to the Corrigenda in the last meeting. Please take a look

at it to see whether it addresses the problem you mentioned.

Regards,

Sean Cai

ZTE

-----Original Message-----

From: owner-stds-802-16-mobile@listserv.ieee.org

[mailto:owner-stds-802-16-mobile@listserv.ieee.org] On Behalf Of Ran

Yaniv

Sent: Friday, October 29, 2004 1:56 AM

To: STDS-802-16-MOBILE@listserv.ieee.org

Subject: Re: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

Hi Yossi,

Sorry to disagree. Take the the 2K mode for example - there are 1702

active

subcarriers which should account for 1536 data subcarriers + pilots.

When

the overlap occurs, you have 1544 remaining subcarriers after you

allocate

pilots (see section 8.4.6.1.2.2.2). How would you allocate these extra 8

subcarriers to data subchannels?

I would either not transmit them and leave nulls (negligible power

gain), or

transmit them as.. pilots.

thanks

Ran

-----Original Message-----

From: Yossi Segal [mailto:yossis@RUNCOM.CO.IL]

Sent: Fri 29 October 2004 10:27

To: STDS-802-16-MOBILE@listserv.ieee.org

Subject: Re: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

Hi Varma,

The overlapping is not by mistake.

By using this overlapping you may use the same pilot for estimation/AFC

etc.

without

Adding more non overlapping pilots, and without increasing the number of

subcarriers used.

Same method is also used in the DVB-T (EN 300744).

Regards,

Yossi

-----Original Message-----

From: owner-stds-802-16-mobile@listserv.ieee.org

[mailto:owner-stds-802-16-mobile@listserv.ieee.org] On Behalf Of varma

indukuri

Sent: Friday, October 29, 2004 7:58 AM

To: STDS-802-16-MOBILE@listserv.ieee.org

Subject: [STDS-802-16-MOBILE] Regarding Pilots Overlapping

hi all

I am seeing the same problem in 16e also for the "1024-FFT OFDMA

downlink

carrier allocations - FUSC". Table 309a from "802.16e/D5"

standard.

The variable pilots at the locations 324,336,516,520 are overlaping with

330,342,522,526 constant pilots. Perhaps I am mistaken.Plz intimate me

if

you find some solution for this Regards, varma ivs

This mail passed through mail.alvarion.com

************************************************************************

****

********

This footnote confirms that this email message has been scanned by

PineApp Mail-SeCure for the presence of malicious code, vandals &

computer

viruses.

************************************************************************

****

********

This mail was sent via mail.alvarion.com

************************************************************************

************

This footnote confirms that this email message has been scanned by

PineApp Mail-SeCure for the presence of malicious code, vandals &

computer viruses.

************************************************************************

************

This mail passed through mail.alvarion.com

************************************************************************

****

********

This footnote confirms that this email message has been scanned by

PineApp Mail-SeCure for the presence of malicious code, vandals &

computer

viruses.

************************************************************************

****

********

This mail was sent via mail.alvarion.com

************************************************************************

************

This footnote confirms that this email message has been scanned by

PineApp Mail-SeCure for the presence of malicious code, vandals &

computer viruses.

************************************************************************

************