<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DOCSIS and Cable Modems &#8211; How it works :: Upstream RF</title>
	<atom:link href="http://volpefirm.com/blog/docsis-101/docsis101_upstream-rf/feed/" rel="self" type="application/rss+xml" />
	<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/</link>
	<description>A Technical Communications Company</description>
	<lastBuildDate>Wed, 16 May 2012 06:51:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-89</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Fri, 30 Dec 2011 16:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-89</guid>
		<description>Hi Daswang,

This is a very good question!  Symbol rate and bandwidth are directly related to one another.  Also, the higher the symbol rate the higher the data rate (think faster data speeds), so we ideally we want big symbol rates, but that means big bandwidths.  There are a couple of problems with big bandwidths.  The upstream has a limited usable bandwidth and the larger the channel bandwidth the greater the chance it will be impacted by noise or other upstream impairments such as group delay.

So what is the relationship between symbol rate and bandwidth?  As the symbols are passed through the root-raised cosine filter in the cable modem to filter away high frequency components, it is up-sampled with a resulting factor of 1.25 (rrc shaping alpha = 0.25).  So the bandwidth is 1.25x the symbol rate.  A symbol rate of 2560 ksym/sec is then 2560 ksym/sec * 1.25 = 3.2 MHz.

A number of studies have been down which show that two 3.2 MHz channels running at 64 QAM are much more resilient to RF impairments than one 6.4 MHz (5120 ksym/sec) channel at 64 QAM.  Why?  The biggest impairment is group delay which has a substantial impact over a large bandwidth channel like 6.4 MHz.

So to answer your question succinctly, the most important thing which will affect the symbol rate on HFC is RF impairments as the symbol rate increases.  The smaller the symbol rate, the less impact by RF impairments; similarly the larger the symbol the more impact by RF impairments.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Daswang,</p>
<p>This is a very good question!  Symbol rate and bandwidth are directly related to one another.  Also, the higher the symbol rate the higher the data rate (think faster data speeds), so we ideally we want big symbol rates, but that means big bandwidths.  There are a couple of problems with big bandwidths.  The upstream has a limited usable bandwidth and the larger the channel bandwidth the greater the chance it will be impacted by noise or other upstream impairments such as group delay.</p>
<p>So what is the relationship between symbol rate and bandwidth?  As the symbols are passed through the root-raised cosine filter in the cable modem to filter away high frequency components, it is up-sampled with a resulting factor of 1.25 (rrc shaping alpha = 0.25).  So the bandwidth is 1.25x the symbol rate.  A symbol rate of 2560 ksym/sec is then 2560 ksym/sec * 1.25 = 3.2 MHz.</p>
<p>A number of studies have been down which show that two 3.2 MHz channels running at 64 QAM are much more resilient to RF impairments than one 6.4 MHz (5120 ksym/sec) channel at 64 QAM.  Why?  The biggest impairment is group delay which has a substantial impact over a large bandwidth channel like 6.4 MHz.</p>
<p>So to answer your question succinctly, the most important thing which will affect the symbol rate on HFC is RF impairments as the symbol rate increases.  The smaller the symbol rate, the less impact by RF impairments; similarly the larger the symbol the more impact by RF impairments.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daswang</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-88</link>
		<dc:creator>Daswang</dc:creator>
		<pubDate>Thu, 29 Dec 2011 09:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-88</guid>
		<description>Hi Brady,

   I&#039;m a new guy for DOCSIS, and I have a question about the symbol rate. The symbol rate is increased a lot from DOCSIS1.x to DOCSIS2.0, and I want to know what is the most important thing which will affect the symbol rate on HFC? Both for downstream and upstream.

Thanks,
Daswang.</description>
		<content:encoded><![CDATA[<p>Hi Brady,</p>
<p>   I&#8217;m a new guy for DOCSIS, and I have a question about the symbol rate. The symbol rate is increased a lot from DOCSIS1.x to DOCSIS2.0, and I want to know what is the most important thing which will affect the symbol rate on HFC? Both for downstream and upstream.</p>
<p>Thanks,<br />
Daswang.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-87</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Sun, 20 Feb 2011 22:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-87</guid>
		<description>Fantastic Blog.  I&#039;m a network sales engineer just getting up to speed on DOCSIS and this is such a great read!  I&#039;ve been reading the specs but the explanation you give creates a visual perspective that helps comprehend the material.

Thank you!  I plan to keep reading.</description>
		<content:encoded><![CDATA[<p>Fantastic Blog.  I&#8217;m a network sales engineer just getting up to speed on DOCSIS and this is such a great read!  I&#8217;ve been reading the specs but the explanation you give creates a visual perspective that helps comprehend the material.</p>
<p>Thank you!  I plan to keep reading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-86</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Thu, 17 Feb 2011 17:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-86</guid>
		<description>Hi Arthur,

If your modem is running 64-QAM in the upstream, then your operator supports at least DOCSIS 2.0 (maybe even DOCSIS 3.0).  It is not uncommon for an operator to run a 64-QAM modulation with a low symbol rate.  Why?  Because using the higher modulation with a lower symbol rate gives higher data rates in the same bandwidth with reasonably good impairment immunity when using the DOCSIS 2.0 pre-equalization and adaptive signal cancellation available in the DOCSIS 2.0 and higher chip sets.  

So your your cable operator is doing the right thing, making the most out of their upstream.  I would imagine that they likely have some upstream issue to still resolve before they can go full 64-QAM, 6.4 MHz, but until then they are using a smaller bandwidth (3.2 MHz).  It is also likely, as you suggest that they are using A-TDMA where the legacy modem transmit data in 16-QAM on the same channel, which is perfectly normal.  The DOCSIS 1.1 modem just uses a different burst descriptor (IUC) in order to do this.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Arthur,</p>
<p>If your modem is running 64-QAM in the upstream, then your operator supports at least DOCSIS 2.0 (maybe even DOCSIS 3.0).  It is not uncommon for an operator to run a 64-QAM modulation with a low symbol rate.  Why?  Because using the higher modulation with a lower symbol rate gives higher data rates in the same bandwidth with reasonably good impairment immunity when using the DOCSIS 2.0 pre-equalization and adaptive signal cancellation available in the DOCSIS 2.0 and higher chip sets.  </p>
<p>So your your cable operator is doing the right thing, making the most out of their upstream.  I would imagine that they likely have some upstream issue to still resolve before they can go full 64-QAM, 6.4 MHz, but until then they are using a smaller bandwidth (3.2 MHz).  It is also likely, as you suggest that they are using A-TDMA where the legacy modem transmit data in 16-QAM on the same channel, which is perfectly normal.  The DOCSIS 1.1 modem just uses a different burst descriptor (IUC) in order to do this.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-85</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Thu, 17 Feb 2011 14:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-85</guid>
		<description>Hi NOCTech82,

There were actual pre-DOCSIS deployments in the mid-90&#039;s, but these were done without using an inter-operable specification.  The first DOCSIS 1.0 spec was developed in the late 90&#039;s (released in 1999 I believe), but actual deployments to subscribers did not occur until about 1990.  It took awhile before the last non-DOCSIS LanCity modems where taken out of service.  So the cable upstream was used for data since in a non-telephony method since at least 1994, but I bet there is a geek out there who can date it back even before then. :-)

-Brady</description>
		<content:encoded><![CDATA[<p>Hi NOCTech82,</p>
<p>There were actual pre-DOCSIS deployments in the mid-90&#8242;s, but these were done without using an inter-operable specification.  The first DOCSIS 1.0 spec was developed in the late 90&#8242;s (released in 1999 I believe), but actual deployments to subscribers did not occur until about 1990.  It took awhile before the last non-DOCSIS LanCity modems where taken out of service.  So the cable upstream was used for data since in a non-telephony method since at least 1994, but I bet there is a geek out there who can date it back even before then. <img src='http://volpefirm.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NOC Tech82</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-84</link>
		<dc:creator>NOC Tech82</dc:creator>
		<pubDate>Fri, 11 Feb 2011 20:11:39 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-84</guid>
		<description>Brady,

Thanks for the all the great HFC information on your sight.  I mainly work on metro ethernet &amp; SONET but still get allot of CMTS work at my job and this site has really helped.

My question:

When did cable providers first get the chance to offer cable modem returns on the cable network without relying on the telco return architecture?  Based off my research it appears this was achieved with the launch of 1.1.

Thanks</description>
		<content:encoded><![CDATA[<p>Brady,</p>
<p>Thanks for the all the great HFC information on your sight.  I mainly work on metro ethernet &amp; SONET but still get allot of CMTS work at my job and this site has really helped.</p>
<p>My question:</p>
<p>When did cable providers first get the chance to offer cable modem returns on the cable network without relying on the telco return architecture?  Based off my research it appears this was achieved with the launch of 1.1.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arthur</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-83</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Tue, 08 Feb 2011 09:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-83</guid>
		<description>Hi Brady,

I&#039;m trying to figure out what docsis version my provider supports.
Weird thing is, the symbol rate as I can see at my modem diag page, is 2.560Msym. So that should team up with 16QAM for docsis 1.1.
But my upstream modulation is 64QAM. 
So maybe I have docsis 2.0? 
The only reason my provider is not doing 5.12 Msym could be that they have still a lot of docsis 1.1 modems in the field. 
Is this technically possible? I mean, combine 64QAM with 2.560Msym?

Cheers,
Arthur.</description>
		<content:encoded><![CDATA[<p>Hi Brady,</p>
<p>I&#8217;m trying to figure out what docsis version my provider supports.<br />
Weird thing is, the symbol rate as I can see at my modem diag page, is 2.560Msym. So that should team up with 16QAM for docsis 1.1.<br />
But my upstream modulation is 64QAM.<br />
So maybe I have docsis 2.0?<br />
The only reason my provider is not doing 5.12 Msym could be that they have still a lot of docsis 1.1 modems in the field.<br />
Is this technically possible? I mean, combine 64QAM with 2.560Msym?</p>
<p>Cheers,<br />
Arthur.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: End</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-82</link>
		<dc:creator>End</dc:creator>
		<pubDate>Mon, 31 Jan 2011 20:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-82</guid>
		<description>Hi Brady,
excellent post!
One question about the 64QAM for Motorolla CMTS. We reach only  max upstream throughput of 4Mbps with 3,2MHz, but changing de bw for 6,4 MHz the throughput turn regular.
This problem there isn´t for CISCO CMTS.

Thanks</description>
		<content:encoded><![CDATA[<p>Hi Brady,<br />
excellent post!<br />
One question about the 64QAM for Motorolla CMTS. We reach only  max upstream throughput of 4Mbps with 3,2MHz, but changing de bw for 6,4 MHz the throughput turn regular.<br />
This problem there isn´t for CISCO CMTS.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-81</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Tue, 31 Aug 2010 00:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-81</guid>
		<description>Hi Peter,

For the upstream, the DOCSIS 3.0 RFI specifies the upstream signal accuracy as being within 50 ppm (parts per million) over an operating temperature range of 0C to 40C for 5 years from the day the cable modem was manufactured.  So how do we translate 50 ppm to frequency?  Simple, just use this equation:

delta f = (center freq * x ppm) / 1e6

So if your cable modem is transmitting at a center frequency of 35 MHz
Your x ppm = 50

Then your allowed cable modem error (or delta f) is:

delta f = (35 MHz * 50 ppm) / 1e6 = 1,750 Hz = 1.75 KHz (error)

Then your minimum frequency could be 34.998250 MHz and your maximum frequency could be 35.001750 MHz and you would still be within the DOCSIS specification.

For the downstream accuracy, the DOCSIS specification just defines this with an straight forward spec. of +/- 30 kHz.  So no math involved.

Hope that helps.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>For the upstream, the DOCSIS 3.0 RFI specifies the upstream signal accuracy as being within 50 ppm (parts per million) over an operating temperature range of 0C to 40C for 5 years from the day the cable modem was manufactured.  So how do we translate 50 ppm to frequency?  Simple, just use this equation:</p>
<p>delta f = (center freq * x ppm) / 1e6</p>
<p>So if your cable modem is transmitting at a center frequency of 35 MHz<br />
Your x ppm = 50</p>
<p>Then your allowed cable modem error (or delta f) is:</p>
<p>delta f = (35 MHz * 50 ppm) / 1e6 = 1,750 Hz = 1.75 KHz (error)</p>
<p>Then your minimum frequency could be 34.998250 MHz and your maximum frequency could be 35.001750 MHz and you would still be within the DOCSIS specification.</p>
<p>For the downstream accuracy, the DOCSIS specification just defines this with an straight forward spec. of +/- 30 kHz.  So no math involved.</p>
<p>Hope that helps.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://volpefirm.com/docsis-101/docsis101_upstream-rf/#comment-80</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 26 Aug 2010 18:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.wordpress.com/?p=128#comment-80</guid>
		<description>Any info on whether DOCSIS specifies the frequency resolution for setting the center frequency of a channel.  Of course the UCD shows a resolution of 1Hz.  My question is if you have some special application where you want to use an arbitrary center frequency, what is the resolution for setting it?

If the isn&#039;t anything in Docsis about it, is there any controlling document that specifies what the frequency resolotion can be?

Same question applies for the downstream as well.</description>
		<content:encoded><![CDATA[<p>Any info on whether DOCSIS specifies the frequency resolution for setting the center frequency of a channel.  Of course the UCD shows a resolution of 1Hz.  My question is if you have some special application where you want to use an arbitrary center frequency, what is the resolution for setting it?</p>
<p>If the isn&#8217;t anything in Docsis about it, is there any controlling document that specifies what the frequency resolotion can be?</p>
<p>Same question applies for the downstream as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

