Re: [STDS-802-16-MOBILE] Changes to pilot location in OFDMA FUSC and PUSC zones
I have explained already to Naftaly, Please ask him to educate you at home.
Since it out of scope why to interfere with all our friends here.
Zion
-----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, July 16, 2004 2:39 AM
To: STDS-802-16-MOBILE@listserv.ieee.org
Subject: Re: [STDS-802-16-MOBILE] Changes to pilot location in OFDMA
FUSC and PUSC zones
Hi Zion,
Our intension is not to mock your solution. We are looking at the
performance of the STC case because we do believe there is an accute
performance issue. Please tell me exactly why you think the contribution is
misleading and has wrong assumptions.
I'd appreciate it if we could indeed stick to a technical discussion for the
time being.
Thanks,
Ran
-----Original Message-----
From: Zion Hadad [mailto:zionh@RUNCOM.CO.IL]
Sent: Thursday, July 15, 2004 6:17 PM
To: STDS-802-16-MOBILE@listserv.ieee.org
Subject: Re: [STDS-802-16-MOBILE] Changes to pilot location in OFDMA FUSC
and PUSC zones
Hi Ran
Technical speaking, this contribution is misleading and the assumptions are
totally wrong.
We have excellent solution. I will not repeat what Yigal said...
Practically, this is out of scope of the PAR.
Zion
-----Original Message-----
From: owner-stds-802-16-mobile@listserv.ieee.org
[mailto:owner-stds-802-16-mobile@listserv.ieee.org]On Behalf Of Zion
Hadad
Sent: Friday, July 16, 2004 2:52 AM
To: STDS-802-16-MOBILE@listserv.ieee.org
Subject: Re: [STDS-802-16-MOBILE] Changes to pilot location in OFDMA
FUSC and PUSC zones
This is out of scope and break the Extension scaled down definition in the
PAR.
Zion
-----Original Message-----
From: owner-stds-802-16-mobile@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-16-mobile@LISTSERV.IEEE.ORG]On Behalf Of Yigal
Sent: Thursday, July 15, 2004 2:38 PM
To: STDS-802-16-MOBILE@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16-MOBILE] Changes to pilot location in OFDMA
FUSC and PUSC zones
Hi Ran,
Since Alvarion was one of the main supporters of OFDM mode, I would be very
interested to see an analysis of OFDM performance in similar conditions, so
we can apply whatever critical corrections we arrive at to OFDM mode as
well.
BR,
Yigal
-----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: Wednesday, July 14, 2004 8:21 PM
To: STDS-802-16-MOBILE@listserv.ieee.org
Subject: [STDS-802-16-MOBILE] Changes to pilot location in OFDMA FUSC
and PUSC zones
Hi all,
I'd like to initiate a technical discussion on this above topic, based on
contribution #238. As the contribution shows, the STC scheme in these modes
completely fails for relatively high multi-path cases.
In my view, the solution should allow good channel tracking ability for STC,
as appropriate for subcarrier-spacing values that result from the
scalable-OFDMA recommendations.
Any thoughts?
I see this issue as vital for basic performance of .16d as well as .16e STC
systems, so IMHO the ideal outcome would be a joint contribution submitted
to both the .16e and the corrigenda group for recirc in the next meeting.
BR,
Ran
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.
****************************************************************************
********