Re: [STDS-802-3-EPOC] Repeating Pilot pattern definition
Duane
DOCSIS has more flexibility in the pilot settings. If we decide on a single pattern over the entire bandwidth, your proposal for the start SC and repeat are OK. Otherwise we would need more bits for the start SC. I am OK with deciding on a single pattern, with a risk of some performance loss on extreme reflections.
I didn't see in your text a reference to type-2 before and after exclusions. Is this stated somewhere else?
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Sent: Monday, August 18, 2014 8:57 PM
To: Avi Kliger; STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Cc: Duane Remein
Subject: RE: Repeating Pilot pattern definition
Avi,
Here are my responses to your questions.
Comment [AK1]: Are different repeat values allowed over the whole channel?
In this proposal there is one pattern for Type 1 pilots and another for Type 2 pilots. SC that qualify for both Type 1 and Type 2 are treated as Typep 2. Do we need more than one pattern for each type? Setting up multiple pattern zones would be significantly more complex. How many would be needed; 2, 5, 10, more? Can zones overlap?
In my example all SC number is absolute with 0 = the first SC in the channel and 4095 being the last.
Comment [AK2]: 1003? SC 1003 would have a Type 2 pilot because it is an edge boundary but not because it is part of the pattern.
Comment [AK3]: 1011?
Comment [AK4]: 1018? Isnt it 1003+15? Yes 1018 is correct (my typo) but not for the reason you state. SC would qualify for both Type 1 (8+101*10) and Type 2 (15+59*17), in this case the SC is assigned a Type 2 pilot.
Comment [AK5]: Do we allow multiple rukes? If so, any subcarrier can start a rule, so it should be any number between 1 and 4095. Or we exclusion are not included between 1 and 3840
Comment [AK6]: Same comment as above [AK5]
We can make the rule set as complex as needed, please make an explicit proposal.
An updated proposal with corrections and some additional clarifications is attached
Best Regards,
Duane
FutureWei Technologies Inc.
duane.remein@xxxxxxxxxx<mailto:duane.remein@xxxxxxxxxx>
Director, Access R&D
919 418 4741
Raleigh, NC
From: Avi Kliger [mailto:akliger@xxxxxxxxxxxx]
Sent: Saturday, August 16, 2014 1:25 PM
To: Duane Remein; STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: RE: Repeating Pilot pattern definition
Duane
Thanks for initiating it.
Please find some comments attached.
Best Regards,
Avi
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Sent: Thursday, August 14, 2014 12:25 AM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-3-EPOC] Repeating Pilot pattern definition
In today's call it was suggested that a proposal for definition of parameters defining the Type 1 and Type 2 repeating Pilot pattern would be appreciated. Please find attached such a proposal. As always comments on the reflector are encouraged.
Mark,
Please add this to next week's Call agenda.
Best Regards,
Duane
FutureWei Technologies Inc.
duane.remein@xxxxxxxxxx<mailto:duane.remein@xxxxxxxxxx>
Director, Access R&D
919 418 4741
Raleigh, NC
________________________________
<="" p="">
________________________________________________________________________
To unsubscribe from the STDS-802-3-EPOC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-EPOC&A=1