Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] [PREAMBLE] Preamble Ad-Hoc group



Title: Message
Hi All,
 
I have uploaded our contribution on PRBS based preambles.
 
Regards
 
Tal
 
 
 
 
-----Original Message-----
From: Peiying Zhu [mailto:pyzhu@nortelnetworks.com]
Sent: Tuesday, July 27, 2004 5:47 PM
To: Tal Kaitz; STDS-802-16@listserv.ieee.org
Subject: RE: [STDS-802-16] [PREAMBLE] Preamble Ad-Hoc group

Hi, Tal:
 
My apology. Let us keep this meeting schedule since it will be too late to change for people in Korean and I will change the next one.
 
Thanks.
 
Peiying
-----Original Message-----
From: Tal Kaitz [mailto:tal.kaitz@alvarion.com]
Sent: Tuesday, July 27, 2004 6:40 AM
To: Zhu, Peiying [CAR:DP13:EXCH]; STDS-802-16@listserv.ieee.org
Subject: RE: [STDS-802-16] [PREAMBLE] Preamble Ad-Hoc group

Peiying and all,
 
Please note that it is 2 AM in Tel Aviv, not 2 PM !
 
It might be too late to change this meeting but I would request another time for the  Aug 10 meeting, perhaps
 
15:00-16:30 pm, 7 am for soel,  1 am for TelAviv,  18 pm for Ottawa
Regards,
 
Tal
 
 
-----Original Message-----
From: Peiying Zhu [mailto:pyzhu@NORTELNETWORKS.COM]
Sent: Tuesday, July 27, 2004 12:00 AM
To: STDS-802-16@listserv.ieee.org
Subject: Re: [STDS-802-16] [PREAMBLE] Preamble Ad-Hoc group

Hi, All:

Just to clarify that the last date for the conference call is Aug. 13, Friday, not Aug. 15.  The first time slot is US pacific time.

Regards,

Peiying

     -----Original Message-----
    From:   Zhu, Peiying [CAR:DP13:EXCH] 
    Sent:   Monday, July 26, 2004 12:55 PM
    To:     'STDS-802-16@LISTSERV.IEEE.ORG'
    Subject:        RE: [STDS-802-16][PREAMBLE] Preamble Ad-Hoc group

    Hi, All:

    Thank you for all the discussions related to a suitable conference call time. Taking consideration of all suggestions, let us use a rotation scheme to be fair for everyone. The following is the schedule (US Pacific time)

      Tuesday, July 27   --- 16:00-17:30 pm, 8 am for soel,  2 pm for TelAviv,  19 pm for Ottawa
      Tuesday, Aug  3    ---  7:00-8:30 am, 11 pm for soel, 17 pm for TelAviv, 10 am for Ottawa
      Tuesday, Aug 10   ---  16:00-17:30 pm, 8 am for soel,  2 pm for TelAviv,  19 pm for Ottawa
      Friday, Aug 15 (if needed) -- 7:00-8:30am, 11 pm for soel, 17 pm for TelAviv, 10 am for Ottawa

    The conference bridge is:

    (613)7650160
    Passcode: 3958089

    Please upload any documents in the following directory: <http://temp.wirelessman.org>

    Please let me know if you have specific items to be discussed in the call. I will send the agenda tomorrow morning after I get input from everyone.

    Regards,

    Peiying


       -----Original Message-----
      From:   Zhu, Peiying [CAR:DP13:EXCH] 
      Sent:   Saturday, July 17, 2004 12:14 AM
      To:     STDS-802-16@LISTSERV.IEEE.ORG
      Subject:        [STDS-802-16][PREAMBLE] Preamble Ad-Hoc group

      Dear all:

      A preamble ad-hoc group was formed within 802.16e as agreed in Portland meeting. This group is tasked to consolidate all the preamble issues raised and related contributions into a single set of preamble proposals to be submitted during the ballot recirculation. The ad-hoc group will follow the recirculation process, hence must finish harmonized contribution before the Aug. 15th deadline.


      Given that we have an extremely aggressive timeline, we need to follow some process going forward. The following is my suggestion, your feedback is welcomed.

      •  Email discussions will use the 802-16-MOBILE reflector with prefix [PREAMBLE].

      • Regular conference calls proposed on the following dates (90 min each):

              Tuesday, July 27
              Tuesday, Aug  3
              Tuesday, Aug 10
              Friday, Aug 15 (if needed)
       
      Proposed time: 8 AM - 9:30 AM US Pacific time (the same time slot used by Jose, seems ok by most people). If I do not hear any objections to these dates/times, I will go ahead and setup call logistics and publish the information by July 26.

      • Milestones - I propose the following milestones to keep us on track:


      July 19- July 27: Discussions on the requirements and issues to be addressed. Discussion on possible harmonization based on the following list of contributions rejected in Portland. Any new contributions must be submitted before this date for the consideration.

      July 27-Aug 3: Consolidate contributions to form one harmonized version

      Aug 3 - Aug 10: Update the harmonized version before Aug. 15 deadline

      Aug 15 - Aug 23: respond to reply comments if needed
       
      To start the conversion, here is the list of issues raised and contributions rejected in Portland meeting.

      Issues raised:

      • Backward compatibility
      • Low PAPR
      • Enable channel estimation
      • Enable fast cell search

      Contributions:

C80216e-04_115r2  Fast cell search for OFDMA   
C80216e-04_125  Preambles design for OFDMA PHY layer, FFT sizes of 1024,512 and 128    
C80216e-04_164
r1  Preamble sequence for supporting scalable FFT
C80216e-04_188
r1  Preamble of scalable OFDMA supporting MIMO system    
C80216e-04_192  Preamble design to enhance MIMO support

 
Hope to see a fruitful discussion on this reflector.

Regards
Peiying Zhu
Preamble ad-hoc group Chair



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.
************************************************************************************