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

Re: [802.3_EPOC] Study Group Questions



Hal,

It's good to know that once OFDM worked for HFC in both directions. Another example can be DVB-C2 protocol that defined OFDM for broadcasting, but probably was not deployed yet.
The difference between Homeworx and EPOC, from QAM/OFDM coexistence point of view, is a number of OFDM carriers and a variety of scenarios for QAM, Analog and OFDM carriers allocation over the spectrum.
Another difference can be a higher level of QAM constellation. To my knowledge, 10 years ago QAM-64 wasn't defined for US, but today there are many talks about QAM-256 for US and QAM-1024 for DS. 

I absolutely agree with you that the properly designed OFDM signal can co-exist with Analog and QAM on HFC. We just have to define this signal and build a guidelines for all possible deployment scenarios.

Thanks,
Boris 

-----Original Message-----
From: Hal Roberts [mailto:Hal.Roberts@xxxxxxxxx] 
Sent: Tuesday, January 03, 2012 10:21 PM
To: Boris Brun; STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: RE: [802.3_EPOC] Study Group Questions

Boris,

While it is not well known within the cable industry, OFDM was proven to coexist with HFC QAM and analog channels 15 years ago (at least OFDM using 6MHz wide channels) in both upstream and downstream HFC.  ADC telecommunications, where I worked developing this technology, created an HFC telephony system called "Homeworx", that used QAM-32 OFDM with 8kHz wide subcarriers in FDD mode.  The power density of the OFDM channels were set to the same level as the QAM digital channels, whether upstream or downstream. The OFDM subcarriers occupied approximately 5MHz of the bandwidth. No additional guard band was used for both upstream and downstream.

This technology was initially deployed during '97 by Optus in Australia.  Later it was deployed in the US by MediaOne, Adelphia, ATT (and inherited and operated by Comcast after that), and a number of smaller MSOs. Over 500,000 lines were eventually deployed in the US. I know for sure that ATT in Los Angelis operated 256-QAM channels directly above and below the Homeworx OFDM channel. Extensive testing was done internally by ADC and by ATT to determine that this was safe.

In short, a properly designed OFDM channel can be treated like a QAM channel. Yes the OFDM peak to average ratio is higher but that doesn't matter once you have large numbers of 256-QAM channels on a plant as the peak to average curve starts to look like Gaussian noise.

It has been a long time but I could probably dig up relevant specifications we used for this. I am not saying some new requirements should not be crafted. However I think we can proceed confidently knowing that if this technology could coexist with adjacent QAM-256 over 10 years ago that new SoC technology applied to OFDM will easily be able to achieve this.

Best regards,

Hal Roberts
System Architect
Calix Networks

-----Original Message-----
From: Boris Brun [mailto:boris.brun@xxxxxxxxxxxxxxx]
Sent: Thursday, December 15, 2011 9:32 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_EPOC] Study Group Questions

Hi Mark,

I think that coexistence issue can't be solved by manufacturer only. From my perspective, the lower level of coexistence is a coexistence between PHYs, or ability to deliver different kind of signals over the same network. It is not obvious that traditional HFC signals, analog video and QAM, will coexist with OFDM or other kind of modulation. Like it wasn't obvious that QAM can coexist with analog video signal and Cablelabs issued the DOCSIS DRFI document specifying the requirements to QAM manufacturers for coexistence with analog signals. Also, different cable network topology will cause a different signal distortion. As result, the Study Group should learn the influence of EPOC's PHY on existing signals for each network topology.

Regards,
Boris



-----Original Message-----
From: Mark Laubach [mailto:laubach@xxxxxxxxxxxx]
Sent: Thursday, December 15, 2011 9:30 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_EPOC] Study Group Questions

Hi All,

I'd like to encourage, as per the prior "cry", that contributions are definitely in order and that merits can be discussed when presented.

Personally, I think coexistence issues can be solved by manufacturers and this will probably serve in boosting both the home gateway and perhaps "campus" gateway where other legacy systems exist.  EPON/EPoC will just be the service provider "WAN port" on the such gateways.

As cable operator contribution in the CFI has already laid out 3 cable network topologies that we have to study as well as the MxU topologies, my suspicion, and Howard can speak to this, is that the Study Group will be encouraged to focus work towards a single PHY standard; i.e. one that can work over all the topologies.  However, that focus is highly susceptible to cable operator input...<g>

Mark

________________________________________________________________________

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

________________________________________________________________________

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

________________________________________________________________________

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