<?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 :: UCD</title>
	<atom:link href="http://volpefirm.com/blog/docsis-101/docsis101_ucd/feed/" rel="self" type="application/rss+xml" />
	<link>http://volpefirm.com/docsis-101/docsis101_ucd/</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: Charter Cable Channels</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-141</link>
		<dc:creator>Charter Cable Channels</dc:creator>
		<pubDate>Fri, 04 Nov 2011 05:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-141</guid>
		<description>Hello! I want to say that this post is amazing, nice written and come with almost all important infos. I&#039;d like to peer more posts like this .</description>
		<content:encoded><![CDATA[<p>Hello! I want to say that this post is amazing, nice written and come with almost all important infos. I&#8217;d like to peer more posts like this .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-140</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Tue, 08 Dec 2009 15:25:30 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-140</guid>
		<description>Sathish,

The MAC address you identified, 01E02F000001 is called out in Annex A of the DOCSIS specification.  This is defined using the Ethernet/ISO8802-3 [ISO8802-3] convention.  Specifically, it states:

The following multicast address MUST be used to address the set of all CM MAC sublayers; for example, when transmitting Allocation Map PDUs:
01-E0-2F-00-00-01

So, to answer your question, yes, it will be sent with all UCDs.

Regards,
-Brady</description>
		<content:encoded><![CDATA[<p>Sathish,</p>
<p>The MAC address you identified, 01E02F000001 is called out in Annex A of the DOCSIS specification.  This is defined using the Ethernet/ISO8802-3 [ISO8802-3] convention.  Specifically, it states:</p>
<p>The following multicast address MUST be used to address the set of all CM MAC sublayers; for example, when transmitting Allocation Map PDUs:<br />
01-E0-2F-00-00-01</p>
<p>So, to answer your question, yes, it will be sent with all UCDs.</p>
<p>Regards,<br />
-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sathish Kumar</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-139</link>
		<dc:creator>Sathish Kumar</dc:creator>
		<pubDate>Thu, 12 Nov 2009 04:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-139</guid>
		<description>Hi Brady,

Yet another informative post.  Simply these posts are real stepping stones to understand the base of working of Cable modem.

Enormous amount of info is present in UCD.
This PDU DA 01E02F000001, you mentioned this a Multicast address.

Whether this address is unique for each UCD, that will be sent for CM&#039;s ?

Thanks,
Sathish.</description>
		<content:encoded><![CDATA[<p>Hi Brady,</p>
<p>Yet another informative post.  Simply these posts are real stepping stones to understand the base of working of Cable modem.</p>
<p>Enormous amount of info is present in UCD.<br />
This PDU DA 01E02F000001, you mentioned this a Multicast address.</p>
<p>Whether this address is unique for each UCD, that will be sent for CM&#8217;s ?</p>
<p>Thanks,<br />
Sathish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Priya</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-138</link>
		<dc:creator>Priya</dc:creator>
		<pubDate>Wed, 14 Oct 2009 02:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-138</guid>
		<description>Hi Brady,

I got really confused at one point. UCD contains the US frequency to be used for transmitting from CM right. But if there are 8 US for 1 DS and 8 UCDs are sent,Then what will each UCD contain and which US frquency will be chosen??

I know This is a silly question but I&#039;m helpless.

Could you please help me??


Thanks,
Priya</description>
		<content:encoded><![CDATA[<p>Hi Brady,</p>
<p>I got really confused at one point. UCD contains the US frequency to be used for transmitting from CM right. But if there are 8 US for 1 DS and 8 UCDs are sent,Then what will each UCD contain and which US frquency will be chosen??</p>
<p>I know This is a silly question but I&#8217;m helpless.</p>
<p>Could you please help me??</p>
<p>Thanks,<br />
Priya</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-137</link>
		<dc:creator>Carol</dc:creator>
		<pubDate>Tue, 03 Mar 2009 20:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-137</guid>
		<description>Hmmm, when I cut and paste the preamble into the text editor, I see 80 words before the start of the line ending in &quot;33 F7&quot;, but I&#039;m sure there&#039;s something I&#039;m misunderstanding that makes you come up with 78.

Anyway, thanks for your speedy reply and this great blog!

Oh, and you might want to wait till I note that 160Ksym/sec would be correct and 1.6Msym/sec would be wrong before you recruit me! :-)</description>
		<content:encoded><![CDATA[<p>Hmmm, when I cut and paste the preamble into the text editor, I see 80 words before the start of the line ending in &#8220;33 F7&#8243;, but I&#8217;m sure there&#8217;s something I&#8217;m misunderstanding that makes you come up with 78.</p>
<p>Anyway, thanks for your speedy reply and this great blog!</p>
<p>Oh, and you might want to wait till I note that 160Ksym/sec would be correct and 1.6Msym/sec would be wrong before you recruit me! <img src='http://volpefirm.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-136</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Tue, 03 Mar 2009 20:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-136</guid>
		<description>Carol,

I really should recruit you to help me on these blogs - you are reading them very thoroughly!  You are correct on the symbol rate, it is 160 ksym/sec, the lowest rate DOCSIS supports.  1.6 Msym/sec is not even a supported rate, so I completely dropped the ball there.  Supported DOCSIS rates are 160, 320, 640, 1280, 2560 and 5120 ksym/sec.  Yes, I also made a typo - I&#039;ll fix these in a minute and no one will know aside from these comments. :-)

Regarding the preamble offset, I have double checked this and believe that it is correct.  624/8 bits = 78 bytes.  Counting in from the beginning of the preamble 78 bytes (two hex characters) leaves you with 14 &quot;F3&quot; bytes left in the preamble before the first &quot;33&quot; byte.  This matches exactly with the Request preamble shown.  Maybe I&#039;m not seeing what you are seeing.

-Brady</description>
		<content:encoded><![CDATA[<p>Carol,</p>
<p>I really should recruit you to help me on these blogs &#8211; you are reading them very thoroughly!  You are correct on the symbol rate, it is 160 ksym/sec, the lowest rate DOCSIS supports.  1.6 Msym/sec is not even a supported rate, so I completely dropped the ball there.  Supported DOCSIS rates are 160, 320, 640, 1280, 2560 and 5120 ksym/sec.  Yes, I also made a typo &#8211; I&#8217;ll fix these in a minute and no one will know aside from these comments. <img src='http://volpefirm.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Regarding the preamble offset, I have double checked this and believe that it is correct.  624/8 bits = 78 bytes.  Counting in from the beginning of the preamble 78 bytes (two hex characters) leaves you with 14 &#8220;F3&#8243; bytes left in the preamble before the first &#8220;33&#8243; byte.  This matches exactly with the Request preamble shown.  Maybe I&#8217;m not seeing what you are seeing.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-135</link>
		<dc:creator>Carol</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:03:59 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-135</guid>
		<description>Hi Brady,

I&#039;m wondering if there is a typo or two in this post.

First, I think the symbol rate should be 1600000 symbols/sec, if it is 1.6M as you state in the text.

Second, I think the Preamble Offset for the Request IUC should be 640 instead of 624, or am I misunderstanding how that&#039;s derived? If I did understand it as an index into the Preamble Pattern sent by the CMTS, then I&#039;m assuming that only the the length and offset are really sent by the modem as that would be enough to derive the preamble itself.

Sorry if the second question is very elementary, but I&#039;m brand new to docsis.

Thanks! Carol

PS: I think the second paragraph of the explanation should read &quot;is the PDU DA&quot; instead of &quot;in the PDU DA&quot;.</description>
		<content:encoded><![CDATA[<p>Hi Brady,</p>
<p>I&#8217;m wondering if there is a typo or two in this post.</p>
<p>First, I think the symbol rate should be 1600000 symbols/sec, if it is 1.6M as you state in the text.</p>
<p>Second, I think the Preamble Offset for the Request IUC should be 640 instead of 624, or am I misunderstanding how that&#8217;s derived? If I did understand it as an index into the Preamble Pattern sent by the CMTS, then I&#8217;m assuming that only the the length and offset are really sent by the modem as that would be enough to derive the preamble itself.</p>
<p>Sorry if the second question is very elementary, but I&#8217;m brand new to docsis.</p>
<p>Thanks! Carol</p>
<p>PS: I think the second paragraph of the explanation should read &#8220;is the PDU DA&#8221; instead of &#8220;in the PDU DA&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-134</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Tue, 03 Mar 2009 13:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-134</guid>
		<description>Hi Ishwar,
If you are talking about prorogation delay, well an electromagnetic signal propagates through coax cable at about 1.17 nanoseconds per foot.  :-)  But I suspect that you were referring to a T1 timeout as defined in Annex B of the DOCSIS 2.0 specification.  A T1 Timeout occurs when a cable modem fails to receive a UCD after five (5) consecutive UCD broadcast intervals.  Since the UCD broadcast interval is two (2) seconds, a T1 timeout should occur at 2 * 5 = 10 seconds.  T1 timeouts are actually pretty rare, but if you have them you probably have some pretty substantial downstream impairments or faulty equipment.

My next blog due out this afternoon will talk a lot more about T3 And T4 timeouts, which are much more common.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Ishwar,<br />
If you are talking about prorogation delay, well an electromagnetic signal propagates through coax cable at about 1.17 nanoseconds per foot.  <img src='http://volpefirm.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />   But I suspect that you were referring to a T1 timeout as defined in Annex B of the DOCSIS 2.0 specification.  A T1 Timeout occurs when a cable modem fails to receive a UCD after five (5) consecutive UCD broadcast intervals.  Since the UCD broadcast interval is two (2) seconds, a T1 timeout should occur at 2 * 5 = 10 seconds.  T1 timeouts are actually pretty rare, but if you have them you probably have some pretty substantial downstream impairments or faulty equipment.</p>
<p>My next blog due out this afternoon will talk a lot more about T3 And T4 timeouts, which are much more common.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ishwar</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-133</link>
		<dc:creator>Ishwar</dc:creator>
		<pubDate>Tue, 03 Mar 2009 10:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-133</guid>
		<description>for the guys who are new to DOCSIS,
ICU means &quot;Interval Usage Code&quot; the name it self explains all

Thanks Brady for the blog, This is to early to ask but I cant hold myself I have to get the answer for this question
What about the delay involved in the transmition of these msgs like if CMTS sends UCD at time interval t1 the CM will receive this at time interval t2 ?</description>
		<content:encoded><![CDATA[<p>for the guys who are new to DOCSIS,<br />
ICU means &#8220;Interval Usage Code&#8221; the name it self explains all</p>
<p>Thanks Brady for the blog, This is to early to ask but I cant hold myself I have to get the answer for this question<br />
What about the delay involved in the transmition of these msgs like if CMTS sends UCD at time interval t1 the CM will receive this at time interval t2 ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-101/docsis101_ucd/#comment-132</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Sat, 28 Feb 2009 19:59:58 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=230#comment-132</guid>
		<description>Thanks for the feedback Brian, it is much appreciated. -Brady</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Brian, it is much appreciated. -Brady</p>
]]></content:encoded>
	</item>
</channel>
</rss>

