Re: [STDS-802-16] [PREAMBLE] Aug 13 Preamble Ad-Hoc group CC rem inder

-----Original Message-----
From: owner-stds-802-16@LISTSERV.IEEE.ORG [mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Zhu, Peiying [CAR:DP13:EXCH]
Sent: Wednesday, August 11, 2004 11:10 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [PREAMBLE] Aug 10 Preamble Ad-Hoc group CC sum mary

Sorry, a typo for the next conference date, Aug. 13, not Aug. 3.

Peiying

-----Original Message-----
From: Zhu, Peiying [CAR:DP13:EXCH]
Sent: Wednesday, August 11, 2004 11:08 PM
To: STDS-802-16@listserv.ieee.org
Subject: Re: [STDS-802-16] [PREAMBLE] Aug 10 Preamble Ad-Hoc group CC sum mary

Dear All:

Thank you for attending the CC. Here is the summary:
Companies present:

Alvarion; Beceem; Broadband Mobile Technologies; ETRI; Hanaro Telecom; Intel; KT; LGE; Motorola; Nextel; Nortel; TI; Proxim; Qualcomm; Runcom; SOLiD Technologies; Samsung; Sprint; ZTE

We discussed the following items:

1. Continue the discussion on the issues related to the current preamble design

In the last CC, there is an action item requesting Runcom to give more detailed explanations. Yossi and Zion uploaded two contributions to address the action item. There was a quite long debates on the process of timing/frequency synchronization, frequency tracking, complexity and performance. There is also a short discussion related to Samsung's contribution on reasoning for OMI.

2. How to harmonize the contributions?

One issue discussed is whether we need a new preamble sequence design if the current preamble structure is used? It was agreed that we do need new preamble sequences for other FFT sizes since the current sequences are truncations of 2k FFT sequences, which do not preserve low PAPR property. Suggestion is to harmonize the sequence design based on the current preamble structure in parallel to the harmonization of other contributions related to the structure of the preamble.

All contributions related to structure of the preamble should be harmonized into another document. Hopefully, we can make one contribution based on these two documents. There is a debate whether the structure change of the preamble is out of the scope. No consensus was reached on this issue.

LGE requested to create an preamble supporting contribution since the contribution on "reference signaling" is not related to structure or sequence. We can include this in the harmonized contribution if most of people in the ad-hoc agree.

There are only a few days left for the submission deadline, we need to get at least a baseline version together. One suggestion on sequence design is that Jeff will share with others the simulation results to compare different sequence design before next CC. For structure design, Sriram and Wen volunteered to start a draft via offline discussion with others before next CC.

Please voice your opinions on the harmonization before CC.

3. Next CC

Friday, Aug 3 --- 7:00-9:00 am USA pacific time, 11 pm for Seoul, 5 pm for TelAviv, 10 am for Ottawa

The conference bridge is:

1+ (613)7650160
Pass code: 3958089 #

Regards,

Peiying

-----Original Message-----
From: owner-stds-802-16@LISTSERV.IEEE.ORG [mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Zhu, Peiying [CAR:DP13:EXCH]
Sent: Tuesday, August 10, 2004 9:28 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [PREAMBLE] Aug 10 Preamble Ad-Hoc group CC rem inder

Dear All:

Just to remind you that I will open the bridge 10 min before the CC. Please try to dial in on time.

Regards,

Peiying

-----Original Message-----
From: owner-stds-802-16@LISTSERV.IEEE.ORG [mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Zhu, Peiying [CAR:DP13:EXCH]
Sent: Monday, August 09, 2004 4:28 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] [PREAMBLE] Aug 10 Preamble Ad-Hoc group CC rem inder

Dear All:

This is a reminder for tomorrow's CC:

Tuesday, Aug 10 --- 20:00-22:00 USA pacific time, 12 for Seoul, 6 for TelAviv, 23 for Ottawa

The conference bridge is:

1+(613)7650160
Pass code: 3958089#

Please let me know any specific requests to be included in the agenda.

Regards,

Peiying