Re: [STDS-802-3-EPOC] 致主席先生，���懂中文的朋友���译一下，谢谢！
Dear Mr. Yao,
We wanted to send a response to your email from 20 January 2013 that was sent to the IEEE P802.3bn EPoC PHY Task Force reflector. Unfortunately, many people did not receive your initial email. Guangsheng Wu from Huawei provided translations just prior to the start of the formal meeting. The Task Force was then able to consider this on a “best effort” basis for this meeting.
The considerations were reviewed in the Evaluation Criteria and Requirements ad hoc committee meeting and then again in the closing session of the Task Force. We have collected the following feedback for you:
On item number 1 in your email on channel bandwidth, the general feeling is that it is better to specify a standard that is "future proof" than to have multiple generations of the same product. It is felt at this time that the estimated relative cost difference of the 64 MHz versus 192 MHz OFDM channel size would be small.
On item number 2 in your email, the RF Spectrum ad hoc committee still has yet to recommend frequency coverage to the Task Force. The ad hoc committee has your input and it should come up as a discussion item during the conference calls.
On your key points items, both rate control and channel bonding are current discussion topics in the Task Force and there is no consensus at this point in time.
Having individuals affiliated with Chinese MSOs and vendors participating in regular IEEE P802.3bn ad hoc committee conference calls may help to better socialize recommendations and key points as part of building consensus. Please note that several conference call attempts were made after the Hangzhou meeting in October. There was little participation from individuals in China even though the times were selected to be convenient for Chinese participation.
A proposal was suggested to hold Evaluation Criteria and Requirement ad hoc committee conference calls in Chinese with presentation materials and meeting minutes recorded in English. Guangsheng Wu from Huawei has volunteered to coordinate these conference calls, and hold them according to IEEE Standards Association guidelines.
In closing, we are very much looking forward to more participation from individuals affiliated with Chinese MSO and vendor interests for the Chinese market for EPoC.
Yours truly,
David Law, Chair IEEE 802.3 Working Group, and
Mark Laubach, Chair IEEE P802.3bn EPoC PHY Task Force
From: yaoyong@xxxxxxxxxxx [mailto:yaoyong@xxxxxxxxxxx]
Sent: Sunday, January 20, 2013 7:52 PM
To: Mark Laubach
Cc: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: 致主席先生，请懂中文的朋友翻译一下，谢谢！
尊敬的David Law主席，尊敬的Mark主席
我们想对IEEE P802.3bn已经讨论和正在讨论的几个问题发表几点看法：
1、关于TDD单信道带宽
我们建议TDD单信道带宽设置为64MHz或192MHz可选，要求支持64MHz信道的主要理由如下：
1.我们针对中国有线运营商的调查结果显示，所有运营商都认为终端带宽应该小于或等于局端带宽。多数运营商对终端最大双向速率之和的要求≤500Mbps
2.单信道带宽设置应综合考虑终端带宽需求和终端成本，在满足带宽需求的前提下追求最低成本和能耗——运营商不愿意为不需要的速率付出代价。64MHz可以满足500Mbps速率的带宽需求，没有必要把带宽搞得太大。
3.局端既可以支持192MHz信道，也可以支持64MHz信道，并可以通过信道绑定或粘结提高速率（或采用 OFDMA的大信道，划分若干子信道），同时可以更灵活地应用频谱，采用更简单的调制方案；终端尽可能单信道（64MHz或192MHz）。
4.64MHz终端有利于降低成本（AD/DA、RF发送功率）；可以降低终端芯片生产的门槛，有利于市场推广。
2、关于频谱规划
FDD需要仔细规划。我们建议下行频谱初期可以应用960-1200MHz，今后可以逐步向两端扩展；上行频谱初期可以应用5-200MHz（也可以更小一些带宽），今后向上扩展；这样可以保证前后兼容，并始终保持只分割一次。如果上行带宽不够，可以在高端再设置一段上行频谱，这要多分割一次。
TDD不需要严格划分频谱，可以占用现有上行频谱，并首先占用960MHz以上空闲频谱，今后可以逐步向两端延伸。
3、关于体系架构（以TDD为例）
我们在3月、5月、7月IEEE会议上多次提出中国运营商最需要的体系架构如下：
[#][#]
其中关键有几点：
1.FCU不仅起到光-电转换作用，还起到10G-1G的作用。这样的好处在于FCU之下的不同支路可以频率复用，这样在现有网络条件下下就可以完全解决EPoC频谱需求，不需要改造网络。
2.1GEPoC由若干（4-5个）64MHz（究竟多大带宽可以讨论）子信道组成，既可以采用FBC技术也可以采用绑定或粘结技术实现。
3.终端速率以子信道带宽为准。
后两点的好处在1、中已经说明。
我们因为参加会议有困难，恳请主席先生能充分考虑我们的意见，并转达给相关专题组。
以上内容我们做了一个简单的提案(见附件，一个中文、一个英文），请允许华为的吴广生替我们在即将召开的会议上宣讲，之前有过充分沟通，他对我们的想法十分了解，同时也是支持者之一。
由于时间仓促，没有按照规定时间提交，请做个临时安排，只需要5-10分钟。
姚 永 中国广播电视协会技术工作委员会
支持者
高晓峻 EPoC论坛秘书长 江苏省广电网络公司
陈 威 河南有线电视网络集团有限公司
石江明 北京歌华有线电视网络股份有限公司
李学明 内蒙古广电网络集团有限公司
胡晓平 楚天襄阳有线电视网络有限公司
戴书胜 北京海尔集成电路设计有限公司
吴广生 华为
曹 凌 瑞斯康达科技发展股份有限公司
胡保民 武汉长光科技
许 磊 无锡路通
________________________________________________________________________
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