Re: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
Sanjay,
While it is true the current GATEs only grant in the time dimension Broadcom has proposed that there be a 1D to 2D mapping function included in the standard so the GATE message does not need to be changed.
Best Regards,
Duane
FutureWei Technologies Inc.
duane.remein@xxxxxxxxxx
Director, Access R&D
919 418 4741
Raleigh, NC
From: Sanjay Goswami [mailto:sanjay.goswami@xxxxxxxxxxxx]
Sent: Thursday, June 27, 2013 6:24 PM
To: Duane Remein; STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
Duane,
EPON GATE grants only in Time Quanta (TQ) and not in frequency. I am not sure if in EPoC the plan is to change the GATE format.
Regards
Sanjay
Sanjay Goswami | Associate Technical Director, Broadband Communications Group
Broadcom Corporation | (O) 707-792-9026 | (M) 707-217-2931
[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: cid:image009.jpg@01CD505E.7B800DB0]
[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image005]<http://www.linkedin.com/company/broadcom>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image002]<http://twitter.com/#!/broadcom>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image003]<https://www.facebook.com/Broadcom>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image004]<https://plus.google.com/109188783526874806673/posts#109188783526874806673/posts>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image006]<https://www.youtube.com/user/BroadcomCorporation>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image008]<http://blog.broadcom.com/>[Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image007]<http://broadcom.com/>
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Sent: Thursday, June 27, 2013 2:38 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
I agree we havn't a formal definition. I would purpose something like: "a set of sub-carriers connected in time related in frequency, but not necessarily contigeous in frequency, allocated by a single GATE message".
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: Thursday, June 27, 2013 1:48 AM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
In the joint upstream pilot contribution by QCOM+BRCM we described what we called a RB. It wasn't a "formal" definition though.
From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxx]
Sent: Thursday, June 27, 2013 1:46 AM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
Thank you for confirmation, Syed,
It is hard for me then to understand proposals towards such an undefined entity .... Is anybody actually planning to define this term ?
Marek
From: Syed Rahman [mailto:Syed.R@xxxxxxxxxx]
Sent: Wednesday, 26 June 2013 11:24 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
Marek,
* To the best of my knowledge, so far we have not decided on a formal resource block definition.
* There have been multiple presentations which talked about resource blocks for different applications (pilots, burst markers, et cetra..)
* Attached is one such presentation
Thanks,
Syed
From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxx]
Sent: Wednesday, June 26, 2013 2:45 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
Dear colleagues,
Have we ever really generated a consented definition of the whole "resource block"? I have been looking through a number of contributions and it seems that it is kind of give, yet I must have missed a formal definition of what this really is. Could anybody point to where it was defined (if it was done before) or try to come up with a consistent definition of what this is (at best, relative to EPON for simpler comprehension) ?
Thank you in advance
Marek
From: Syed Rahman [mailto:Syed.R@xxxxxxxxxx]
Sent: Wednesday, 26 June 2013 9:05 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-3-EPOC] Resoruce block presentation in todays phy sub-task call
All,
Attached is the presentation I gave in today's Phys sub-task force call.
Thanks,
Syed
________________________________
<="" p="">
________________________________
<="" p="">
________________________________
________________________________
<="" p="">
________________________________
<="" p="">
________________________________
<="" 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
