<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Doktertomi.com &#187; Communications Systems and Networks</title>
	<atom:link href="http://www.doktertomi.com/category/best-seller-books/communications-systems-and-networks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.doktertomi.com</link>
	<description>Free Inspirations, Informations, News, Guides, Tips and Tricks</description>
	<lastBuildDate>Tue, 27 Apr 2010 13:59:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Seventeen)</title>
		<link>http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/</link>
		<comments>http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/#comments</comments>
		<pubDate>Wed, 26 Nov 2008 08:02:02 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[108/228 Card T-1 with cable - Refurbished. - - Phone]]></category>
		<category><![CDATA[ATM]]></category>
		<category><![CDATA[Bell Telephone Laboratories Incorporated]]></category>
		<category><![CDATA[broadband]]></category>
		<category><![CDATA[Bruce R. Private Telecommunication Networks]]></category>
		<category><![CDATA[Bury]]></category>
		<category><![CDATA[California]]></category>
		<category><![CDATA[Channel Packet Service]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[D.C.  The interface message processor]]></category>
		<category><![CDATA[Datapro Communications Analyst]]></category>
		<category><![CDATA[David J]]></category>
		<category><![CDATA[Delran]]></category>
		<category><![CDATA[Emporia Telecom Isoetec IDS]]></category>
		<category><![CDATA[Federal Communications Commission]]></category>
		<category><![CDATA[Frame Relay]]></category>
		<category><![CDATA[Harper]]></category>
		<category><![CDATA[Horsham]]></category>
		<category><![CDATA[Indianapolis]]></category>
		<category><![CDATA[interface message processor]]></category>
		<category><![CDATA[Internet   Work]]></category>
		<category><![CDATA[ISDN]]></category>
		<category><![CDATA[John Wiley and Sons Inc.]]></category>
		<category><![CDATA[LAN]]></category>
		<category><![CDATA[McGraw-Hill Inc.]]></category>
		<category><![CDATA[Norwood]]></category>
		<category><![CDATA[Piscataway]]></category>
		<category><![CDATA[Prentice-Hall]]></category>
		<category><![CDATA[Regis]]></category>
		<category><![CDATA[Regis J.  Introduction]]></category>
		<category><![CDATA[SAMS Publishing]]></category>
		<category><![CDATA[San Francisco]]></category>
		<category><![CDATA[SONET]]></category>
		<category><![CDATA[Sprint]]></category>
		<category><![CDATA[Switched Data Service]]></category>
		<category><![CDATA[T-1]]></category>
		<category><![CDATA[Telecom Library Inc.]]></category>
		<category><![CDATA[Telecommuting]]></category>
		<category><![CDATA[Virtual Circuit]]></category>
		<category><![CDATA[X.25]]></category>
		<category><![CDATA[X.25 Protocol]]></category>

		<guid isPermaLink="false">http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/</guid>
		<description><![CDATA[References [8-1] Brooks, John. Telephone: The First Hundred Years. NY: Harper and Row, 1976. [8-2] Engineering and Operations in the Bell System. NJ: Bell Telephone Laboratories, Incorporated. 1977. [8-3] Bates, Regis J. Introduction to T1/T3 Networking. Norwood, MA: Artech House. 1992. [8-4] Trulove, James E. A Guide to Fractional T1. Norwood, MA: Artech House. 1992. [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F11%2F26%2Fchapter-8-conventional-public-data-networks-pdns-page-seventeen%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<h3>References</h3>
<dl>
<dd>[8-1] Brooks, John. <i>Telephone: The First Hundred Years</i>. NY: Harper and Row, 1976. </dd>
<dd>[8-2] <i>Engineering and Operations in the Bell System</i>. NJ: Bell Telephone Laboratories, Incorporated. 1977. </dd>
<dd>[8-3] Bates, Regis J. <i>Introduction to T1/T3 Networking</i>. Norwood, MA: Artech House. 1992. </dd>
<dd>[8-4] Trulove, James E. <i>A Guide to Fractional T1</i>. Norwood, MA: Artech House. 1992. </dd>
<dd>[8-5] Flanagan, William A. <i>The Guide to T-1 Networking</i>. NY: Telecom Library Inc. 1990. </dd>
<dd>[8-6] Minoli, Daniel. <i>Enterprise Networking: Fractional T1 to SONET, Frame Relay to BISDN</i>. Norwood, MA: Artech House. 1993. </dd>
<dd>[8-7] Nolle, Tom. &#8220;Don&#8217;t Bury Traditional T1 Just Yet.&#8221; <i>Business Communications Review</i>. September 1995. </dd>
<dd>[8-8] Gelber, Stan. <i>Introduction to Data Communications: A Practical Approach</i>. Horsham, PA: Professional Press Books. 1991. </dd>
<dd>[8-9] Doll, Dixon R. <i>Data Communications: Facilities, Networks, and Systems Design</i>. NY: John Wiley and Sons, Inc. 1978. </dd>
<dd>[8-10] Elbert, Bruce R. <i>Private Telecommunication Networks</i>. Norwood, MA: Artech House. 1989. </dd>
<dd>[8-11] Korzeniowski, Paul. &#8220;T1 Continues to Grow in Private Networks.&#8221; <i>Business Communications Review</i>. February 1996. </dd>
<dd>[8-12] Rhode, David. &#8220;Sprint turns on 800 Switched Data Service.&#8221; <i>Network World</i>. October 30, 1995. </dd>
<dd>[8-13] Briere, Daniel. &#8220;Digital 800 Era Arrives-So Does a Dilemma.&#8221; <i>Network World</i>. March 6, 1995. </dd>
<dd>[8-14] &#8220;Digital 800 Gains Momentum.&#8221; <i>Network World</i>. September 25, 1995. </dd>
<dd>[8-15] Kleinrock, Leonard. <i>Principles and Lessons in Packet Communications</i>. Partridge, Craig. <i>Innovations in Internetworking</i>. Norwood MA: Artech House. 1988. </dd>
<dd>[8-16] Heart, F.E.; Kahn, R.E.; Ornstein, S.M.; Crowther, W.R.; and Walden, D.C. <i>The interface message processor for the ARPA computer network</i>. Partridge, Craig. <i>Innovations in Internetworking</i>. Norwood, MA: Artech House. 1988. </dd>
<dd>[8-17] Spohn, Darren L. <i>Data Network Design</i>. NY: McGraw-Hill, Inc. 1993. </dd>
<dd>[8-18] Stallings, William. <i>ISDN and Broadband ISDN with Frame Relay and ATM</i> (Third Edition). NY: Prentice-Hall. 1995. </dd>
<dd>[8-19] Rybczynski, Antony. <i>X.25 Interface and End-to-End Virtual Circuit Service Characteristics</i>. Partridge, Craig. <i>Innovations in Internetworking</i>. Norwood, MA: Artech House. 1988. </dd>
<dd>[8-20] Held, Gilbert. <i>Understanding Data Communications</i>. Indianapolis, IN: SAMS Publishing. 1994. </dd>
<dd>[8-21] Burch, Bill. &#8220;X.25 Protocol Proves to Have Enduring Appeal.&#8221; <i>Network World</i>. October 31, 1995. </dd>
<dd>[8-22] &#8220;X.25 Emerges as a LAN Interconnect Option.&#8221; <i>Data Communications</i>. March 1995. </dd>
<dd>[8-23] Levitt, Jason. &#8220;Hold The Phone!&#8221; <i>Information Week</i>. May 15, 1995. </dd>
<dd>[8-24] Horak, Ray. &#8220;ISDN: To Be Delivered as Promised?&#8221; <i>Datapro Communications Analyst</i>. Delran, NJ: Datapro Information Services. January 1995. </dd>
<dd>[8-25] Greene, Tim. &#8220;Sprint/United, Other Small Carriers Get Into ISDN Game.&#8221; <i>Network World</i>. August 7, 1995. </dd>
<dd>[8-26] Buerger, David J. &#8220;National ISDN&#8217;s Third Birthday is Nothing to Write Home About.&#8221; <i>Network World</i>. November 13, 1995. </dd>
<dd>[8-27] Roth, Cliff. &#8220;ISDN Modems Come to Town.&#8221; <i>NewMedia</i>. March 11, 1996. </dd>
<dd>[8-28] Gareiss, Robin. &#8220;ISDN: Stop Singing Those Blues.&#8221; <i>Data Communications</i>. March 1996. </dd>
<dd>[8-29] Sullivan, Kristina B. &#8220;ISDN Moves Toward the Mainstream.&#8221; <i>PC Week</i>. December 11, 1995. </dd>
<dd>[8-30] Stargess, James. &#8220;ISDN D Channel Packet Service: Coming Soon to a Store Near You.&#8221; <i>Network World</i>. March 11, 1996. </dd>
<dd>[8-31] <i>ISDN: A User&#8217;s Guide to Services, Applications and Resources in California</i>. San Francisco, CA: Pacific Bell. 1994 </dd>
<dd>[8-32] &#8220;ISDN and Data Networking.&#8221; <i>Datapro Communications Analyst</i>. Delran, NJ: Datapro Information Services. May 1995. </dd>
<dd>[8-33] Metcalfe, Bob. &#8220;The FCC&#8217;s Doubling of ISDN Rates May Finally Kick Off a User Revolt.&#8221; <i>Infoworld</i>. April 3, 1995. </dd>
<dd>[8-34] Case, Linda and Mulligan, John. <i>ISDN As a Telecommuting Solution</i>. Piscataway, NJ: Bellcore. 1996. </dd>
<dd>[8-35] Tredinnick, Ian. &#8220;X.25: A New Lease on Life with ISDN.&#8221; Telecommunications. June 1995. </dd>
<dd>[8-36] Kalman, Steve. &#8220;So You Want to Use ISDN&#8230;.&#8221; <i>Network World</i>. December 4, 1995.</dd>
</dl>
<p></p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seventeen%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seventeen%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seventeen%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seventeen%29+-+http://b2l.me/bexu3&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seventeen%29&amp;body=Link: http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A References%20%5B8-1%5D%20Brooks%2C%20John.%20Telephone%3A%20The%20First%20Hundred%20Years.%20NY%3A%20Harper%20and%20Row%2C%201976.%20%5B8-2%5D%20Engineering%20and%20Operations%20in%20the%20Bell%20System.%20NJ%3A%20Bell%20Telephone%20Laboratories%2C%20Incorporated.%201977.%20%5B8-3%5D%20Bates%2C%20Regis%20J.%20Introduction%20to%20T1%2FT3%20Networking.%20Norwood%2C%20MA%3A%20Artech%20House.%201992.%20%5B8-4%5D%20Trulov" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1806" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1806', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1806&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/11/26/chapter-8-conventional-public-data-networks-pdns-page-seventeen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Fourteen)</title>
		<link>http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/</link>
		<comments>http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/#comments</comments>
		<pubDate>Sat, 14 Jun 2008 07:01:21 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[B-channel]]></category>
		<category><![CDATA[bandwidth-intensive applications]]></category>
		<category><![CDATA[carrier electronics]]></category>
		<category><![CDATA[carrier side]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[D-Channel]]></category>
		<category><![CDATA[functional device]]></category>
		<category><![CDATA[individual devices]]></category>
		<category><![CDATA[International Standards Organization]]></category>
		<category><![CDATA[ISDN]]></category>
		<category><![CDATA[ITU-T V.120 protocol]]></category>
		<category><![CDATA[Japan]]></category>
		<category><![CDATA[LAN router]]></category>
		<category><![CDATA[Motorola HEADSET/MOTO BT HEADSET H12 Bluetooth]]></category>
		<category><![CDATA[Motorola Motopure H12 Bluetooth Headset]]></category>
		<category><![CDATA[multirate communications]]></category>
		<category><![CDATA[network protocols]]></category>
		<category><![CDATA[NikeSound SS7 AM/FM Radio]]></category>
		<category><![CDATA[North America]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[PRI]]></category>
		<category><![CDATA[RJ-45]]></category>
		<category><![CDATA[SS7]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[video conferencing]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/</guid>
		<description><![CDATA[A single BRI line can support up to eight devices, which might be in the form of telephones, facsimile machines, or computers. Additionally, up to 64 individual telephone numbers can be supported [8-31]. While BRI supports as many as three simultaneous calls, only one can be a voice conversation. BRI uses an 8-pin connector which [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F14%2Fchapter-8-conventional-public-data-networks-pdns-page-fourteen%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<p>A single BRI line can support up to eight devices, which might be in the form of telephones, facsimile machines, or computers. Additionally, up to 64 individual telephone numbers can be supported [8-31]. While BRI supports as many as three simultaneous calls, only one can be a voice conversation.</p>
<p>BRI uses an 8-pin connector which is defined by the International Standards Organization (ISO) in ISO 8877 and which uses a RJ-45 jack. Full duplex (FDX) connectivity is accomplished over a digital twisted-pair local loop through the application of special carrier electronics. A NT1 (Network Termination 1) device provides for compatibility with network protocols.</p>
<p><b>Primary Rate Interface (PRI)</b></p>
<p><i>Primary Rate Interface</i> (<i>PRI</i>) also is known as <i>23B+D</i> in the US and Japan. The European or ITU version is known as <i>Primary Rate Access</i> (<i>PRA</i>) or <i>30B+D</i>. PRI offers 23 B (Bearer) Channels, plus 1 D (Data) channel. Both the B and D channels operate at 64 Kbps. The individual B channels can be used as discussed in the case of BRI; the D channel is reserved exclusively for signaling. As the standards provide for a D channel to support up to five PRI connections, numerous carriers have recently embraced this concept, thereby yielding additional usable bandwidth for user application. For example, the first PRI in a PBX trunking application would be provided at 23B+D; the next four PRIs would be deliver 24B+0D.</p>
<p>PRI provides a full duplex (FDX) point-to-point connection through a NT2-type intelligent CPE switching device (e.g., a PBX or router) device for protocol interface with the carrier CO exchange switch.</p>
<p>While designed for transmission over a standard T1 trunk, PRI is a significant improvement over T1, because the channels can be allocated dynamically. Each channel can act as an incoming, outgoing, combination, or DID trunk as the need arises. The nature of the channel can be determined as required or as specified, varying based on user-definable parameters. Additionally, multiple B channels can be aggregated to serve bandwidth-intensive applications, such as videoconferencing.</p>
<p><b>H-Channels</b></p>
<p><i>H-channels</i> (<i>H</i>igh-speed <i>channels</i>), are functionally equivalent to B-channels, but provided greater aggregate bandwidth in PRI applications. H0 channel signals have a aggregate bit rate of 384 Kbps, while H1 channels operate at an aggregate of 1.536 Mbps for the North American version (H11) and 1.920 Mbps for the European version (H12). This capability of channel aggregation allows multirate communications on a dynamic basis through inverse multiplexing over multiple B-channels. It does have a drawback, however, when compared to traditional Inverse MUXs as the connection must be torn down and reinitiated when channels are added or dropped. The feature is known variously as <i>Multirate ISDN</i>, <i>Nx64</i>, <i>Channel Aggregation</i> and <i>bonding</i>. H channels find application in fast faxing (Group IV), videoconferencing, high-speed data transfer and high-quality audio transmission.</p>
<h4 align="left">ISDN Equipment</h4>
<p>ISDN hardware, at the end user side of the connection, includes <i>Terminal Equipment (TE), Terminal Adapters (TAs),</i> and <i>Network Terminations (NTs)</i> as shown in Figure 8.10. The carrier requires digital COs that are equipped with ISDN and SS7 software.</p>
<p><b>Terminal Equipment (TE)</b></p>
<p>Terminal Equipment (TE) is the term for a functional device that connects a customer site to ISDN services. Examples include computers, telephones, facsimile machines, and videoconferencing units. <i>TE1</i> has a built-in ISDN interface, while <i>TE2</i> devices do not have native ISDN compatibility.</p>
<p><b>Terminal Adapters (TAs)</b></p>
<p>Terminal Adapters (TAs) are interface adapters for connecting one or more TE2 (non-ISDN) devices to an ISDN network. TAs act as ISDN DCE, serving a function equivalent to protocol or interface converters. Applied to equipment which does not have ISDN capability built within it; the TAs must be exactly tuned to the specific CPE/DTE. TAs can be in the form of either standalone units or printed circuit boards fitting into an expansion slot of a PC.</p>
<p>A key function of the TA is that of <i>rate adaption</i>, which effectively throttles down the transmission rate from 64 Kbps to the rate at which the non-ISDN device is capable [8-32]. As an example, a non-ISDN PC might be capable of only 19.2 Kbps through the serial port. Another example might involve a connection supported at only 56 Kbps (non-ISDN or Pacific Bell &#8220;ISDN&#8221;) on the receiving end; the device would throttle down to that rate, rather than 64 Kbps. Rate adaptation is accomplished in North America through the ITU-T V.120 protocol; the European standard is V.110.</p>
<p><b>Network Terminations (NTs)</b></p>
<p>Network Terminations 0(NTs) are Network Termination devices, NT1s and NT2s.</p>
<p><b>NT2s</b></p>
<p>NT2s (Network <i>T</i>ermination type <i>2</i>) are intelligent devices responsible for the user&#8217;s side of the connection to the network, performing such functions as multiplexing, switching or ISDN concentration. A NT2 device would likely be in the form of a PABX, LAN router or switching hub.</p>
<p><b>NT1s</b></p>
<p>NT1s (Network <i>T</i>ermination type <i>1</i>) physically connect the customer site to the carrier side of the connection, performing such functions as signal conversion and maintenance of the local loop&#8217;s electrical characteristics. In a PRI environment, these functions are similar to those provided by Data Service Units (DSUs) and Channel Service Units (CSUs). In a BRI environment, these devices are TE1 devices.</p>
<p><b>Inverse MUXs,</b></p>
<p>Inverse MUXs, offered by some manufacturers, allow multiple BRIs to be bonded, or linked, for greater aggregate transmission over a BRI circuit(s). For example, four BRIs can be linked to support a 512 Kbps data transmission. Such an approach competes effectively with Fractional T1 (FT1).</p>
<p><b>D-Channel Contention Devices</b></p>
<p>D-Channel Contention Devices, offered by some manufacturers, allow as many as eight devices to share a BRI circuit, contending for access to the B-channel. The individual devices identify themselves to the network through contention for the D channel.</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Fourteen%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Fourteen%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Fourteen%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Fourteen%29+-+http://b2l.me/bexu4&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Fourteen%29&amp;body=Link: http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A A%20single%20BRI%20line%20can%20support%20up%20to%20eight%20devices%2C%20which%20might%20be%20in%20the%20form%20of%20telephones%2C%20facsimile%20machines%2C%20or%20computers.%20Additionally%2C%20up%20to%2064%20individual%20telephone%20numbers%20can%20be%20supported%20%5B8-31%5D.%20While%20BRI%20supports%20as%20many%20as%20three%20simultaneous%20calls%2C%20only%20one%20can%20be%20a%20voice%20conversation.BRI" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1635" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1635', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1635&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/14/chapter-8-conventional-public-data-networks-pdns-page-fourteen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Thirteen)</title>
		<link>http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/</link>
		<comments>http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/#comments</comments>
		<pubDate>Fri, 13 Jun 2008 07:00:57 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[Ameritech]]></category>
		<category><![CDATA[author]]></category>
		<category><![CDATA[basic services]]></category>
		<category><![CDATA[broadband]]></category>
		<category><![CDATA[carrier deploying]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[Europe]]></category>
		<category><![CDATA[given carrier]]></category>
		<category><![CDATA[given manufacturer]]></category>
		<category><![CDATA[GTE]]></category>
		<category><![CDATA[high-bandwidth applications]]></category>
		<category><![CDATA[ISDN]]></category>
		<category><![CDATA[meaningful and cost-effective applications]]></category>
		<category><![CDATA[Minox GT-E 35mm Film Camera]]></category>
		<category><![CDATA[network management]]></category>
		<category><![CDATA[New York]]></category>
		<category><![CDATA[NikeSound SS7 AM/FM Radio]]></category>
		<category><![CDATA[North America]]></category>
		<category><![CDATA[NYNEX]]></category>
		<category><![CDATA[Pacific Rim]]></category>
		<category><![CDATA[Small Office/Home Office]]></category>
		<category><![CDATA[SS7]]></category>
		<category><![CDATA[Telecommuting]]></category>
		<category><![CDATA[telephone]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[USD]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/</guid>
		<description><![CDATA[Islands of ISDN were the result of these various implementations. A given carrier, using the hardware and software of a given manufacturer, could not easily achieve full connectivity with another carrier deploying another version of ISDN. Weary of delays in the standards process, some carriers (e.g., Southwestern Bell) developed and implemented proprietary versions of ISDN, [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F13%2Fchapter-8-conventional-public-data-networks-pdns-page-thirteen%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<p>Islands of ISDN were the result of these various implementations. A given carrier, using the hardware and software of a given manufacturer, could not easily achieve full connectivity with another carrier deploying another version of ISDN. Weary of delays in the standards process, some carriers (e.g., Southwestern Bell) developed and implemented proprietary versions of ISDN, further contributing to the problem. During the past several years, this problem has been mitigated through cooperation of the manufacturers and carriers, with active involvement of Bellcore [8-23] and [8-24].</p>
<p>Availability of ISDN was slow to develop, as the carriers were reluctant to invest in the technology unless they were convinced that a market existed for the services and/or that the technology offered internal cost savings. ISDN is not inexpensive to deploy, a fact which unfortunately has been reflected in high end-user circuit and equipment costs. Availability recently has increased to a significant extent, with the RBOC&#8217;s and GTE having made considerable commitments to its deployment. The independent telephone companies are increasingly making ISDN a priority, although they understandably lag far behind the RBOCs due to cost-of-service factors [8-25].</p>
<p>Regulators generally have required that the LECs pass on the cost of ISDN infrastructure to ISDN users, rather than allowing them to average those costs across the entire rate base. In other words, they have viewed ISDN as an optional service that must pay its own way, or that the carriers should absorb any associated losses. As the carriers have been unwilling to do so, ISDN rates have remained high.</p>
<p>Rates for ISDN access were not tariffed at attractive levels compared with the cost of basic services. Again, the regulators were, and still are, largely responsible. The carriers also bear responsibility as well, as they have not been willing to absorb initial losses in order to stimulate the growth of the service offering. Ameritech, for instance, charges $135 for installation and $34.64 per month for a low-speed ISDN BRI circuit; an additional $20 per month applies if the premise is more than three miles from an ISDN central office. Southwestern Bell is the prize winner, at $578 for installation and $57.70 per month [8-26]. In New York, NYNEX charges $14 per month in addition to the normal line charge, plus installation or upgrade charges which vary from about $50 to $312 [8-27]. Rates for PRI vary considerably as well. In some cases based on a per-channel charge and in other cases on a flat rate per PRI [8-28]. In some states, additional per-minute surcharges apply to ISDN; starting with call setup, rather than call connection. The charges typically are higher for a data call than for a voice call.</p>
<p>Equipment costs were high, as the manufacturers were constantly investing in R&#038;D to maintain ISDN compliance with developing standards. Additionally, the limited demand for ISDN caused the manufacturing runs to be small-lower costs are achieved through increased volume. As an example, Terminal Adapters, which provide the interface to an ISDN circuit for non-ISDN equipment, have come down in price from about $1,000 in 1993 to an average of less than $500 today. That is an improvement, but still a substantial investment for a small business or residential user [8-29].</p>
<p>Marketing by the LECs was not effective. Not only were costs maintained at unattractive levels, but advertising and promotion were limited, and availability clearly was not high. Further, meaningful and cost-effective applications were not identified and stressed. With typical lack of foresight, the LECs placed heavy emphasis on the low-speed BRI version, which is suitable only for residence, small business, and <i>SOHO</i> (<i>Small Office/Home Office</i>) application. High-speed PRI was not emphasized heavily as a replacement of T1 trunking. ISDN Centrex was touted heavily, but with limited success. Centrex ISDN marketing was heavily slanted toward CO-based Local Area Networking, which was a dismal failure.</p>
<p>While ISDN has frustrated the industry, in general, there currently are over 200,000 ISDN access lines worldwide. Some industry pundits forecast that more than 750 million will be installed by the year 2000-the author does not share that level of enthusiasm. ISDN is much more mature in Europe and certain parts of the Pacific Rim than it is in the United States. In those regions, deployment was encouraged by the regulators and even subsidized by the governments. Additionally, marketing was much more effective, focusing on PRI, rather than BRI [8-24].</p>
<h4 align="left">Standard Interfaces and Channel Types</h4>
<p>The current version of ISDN is <i>Narrowband ISDN (N-ISDN)</i>. (Broadband ISDN (B-ISDN), which is still on the drawing boards, is discussed in Chater 11.) ISDN currently is available in essentially two interface varieties BRI (2B+D) and PRI (23B+D in North America, and 30B+D in Europe and many other countries) (see Figure 8.9). In each case, the ITU specifies the electrical characteristics, signaling, coding and frame formatting. There is one variation on the theme; H-channel, designed for high-bandwidth applications, <i>bonds</i> multiple B channels.</p>
<p><b>Basic Rate Interface (BRI)</b></p>
<p><i>Basic Rate Interface</i> (<i>BRI</i>) also is known as <i>Basic Rate Access</i> (<i>BRA</i>) and <i>2B+D</i>. BRI provides 2 <i>B channels</i> (<i>Bearer</i>, or information-bearing channels), each operating at the clear-channel rate of 64 Kbps by virtue of SS7 nonintrusive signaling. Each B channel can carry digital data, digitized voice (PCM-encoded at 64 Kbps or a lower rate), or a mixture of low-speed (subrate) data as long as it all is intended for the same destination. BRI also provides a <i>D</i> (<i>Data</i>) channel at 16 Kbps, which is used for control, messaging, and network management. The D channel also generally is made available for packet data transmission and low-speed telemetry when not in use for signaling purposes. Cost-effective applications include credit card authorization, which involves very small bursts of data [8-30]. BRI is primarily used for residential, small business, Centrex, and telecommuting applications that are not particularly bandwidth-intensive. The B channels can be <i>aggregated</i> or <i>bonded</i>, to provide up to 128 Kbps to a given conversation, such as a videoconference; additionally, multiple BRIs can be bonded for even greater capacity. Whether bonded or not, ISDN BRI provides multiple channels over a single physical loop, which is a great advantage.</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Thirteen%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Thirteen%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Thirteen%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Thirteen%29+-+http://b2l.me/bdvef&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Thirteen%29&amp;body=Link: http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Islands%20of%20ISDN%20were%20the%20result%20of%20these%20various%20implementations.%20A%20given%20carrier%2C%20using%20the%20hardware%20and%20software%20of%20a%20given%20manufacturer%2C%20could%20not%20easily%20achieve%20full%20connectivity%20with%20another%20carrier%20deploying%20another%20version%20of%20ISDN.%20Weary%20of%20delays%20in%20the%20standards%20process%2C%20some%20carriers%20%28e.g." rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1633" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1633', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1633&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/13/chapter-8-conventional-public-data-networks-pdns-page-thirteen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Twelve)</title>
		<link>http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/</link>
		<comments>http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/#comments</comments>
		<pubDate>Thu, 12 Jun 2008 07:00:25 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[airline reservations systems]]></category>
		<category><![CDATA[America Online]]></category>
		<category><![CDATA[ATM]]></category>
		<category><![CDATA[bandwidth-intensive applications]]></category>
		<category><![CDATA[Bank branches]]></category>
		<category><![CDATA[Belgium]]></category>
		<category><![CDATA[Blue Book]]></category>
		<category><![CDATA[broadband]]></category>
		<category><![CDATA[carrier network]]></category>
		<category><![CDATA[Central Europe]]></category>
		<category><![CDATA[channel signaling protocols]]></category>
		<category><![CDATA[contemporary applications]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[data communications]]></category>
		<category><![CDATA[E-1]]></category>
		<category><![CDATA[fiber optic]]></category>
		<category><![CDATA[Frame Relay]]></category>
		<category><![CDATA[France]]></category>
		<category><![CDATA[interactive processing]]></category>
		<category><![CDATA[Internet access]]></category>
		<category><![CDATA[Internet backbone network]]></category>
		<category><![CDATA[Internet Service Providers]]></category>
		<category><![CDATA[ISDN]]></category>
		<category><![CDATA[LAN]]></category>
		<category><![CDATA[Latin America]]></category>
		<category><![CDATA[low-bandwidth applications]]></category>
		<category><![CDATA[network technologies]]></category>
		<category><![CDATA[network technology]]></category>
		<category><![CDATA[NikeSound SS7 AM/FM Radio]]></category>
		<category><![CDATA[North America]]></category>
		<category><![CDATA[Packet Switching]]></category>
		<category><![CDATA[Prodigy]]></category>
		<category><![CDATA[reservations systems]]></category>
		<category><![CDATA[SS7]]></category>
		<category><![CDATA[supplementary services]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[Western Europe]]></category>
		<category><![CDATA[X.25]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/</guid>
		<description><![CDATA[Packet Switching Applications and Futures The original application for X.25 packet switching was that of interactive time-sharing, which involves long connect times and low data volume. While such applications are still supported effectively by X.25, contemporary applications include online interactive processing (reservations systems), messaging (email), batch file transfer (data backup), information service access (America Online, [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F12%2Fchapter-8-conventional-public-data-networks-pdns-page-twelve%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<h4 align="left">Packet Switching Applications and Futures</h4>
<p>The original application for X.25 packet switching was that of interactive time-sharing, which involves long connect times and low data volume. While such applications are still supported effectively by X.25, contemporary applications include online interactive processing (reservations systems), messaging (email), batch file transfer (data backup), information service access (America Online, CompuServe, and Prodigy), and Internet access.</p>
<p>Packet-switching offers the advantage of being a highly mature, if limited, network technology. Therefore, it is relatively inexpensive to deploy and is highly cost-effective in support of applications that require many-to-many connectivity and which involve relatively low volumes of data transport. Additionally, it is virtually ubiquitous, having been deployed in every corner of the globe. However, it is limited in terms of speed and latency. As a result, many applications and service providers are moving toward newer network technologies. For example, the airline reservations systems are rapidly moving to Frame Relay, at least for the domestic (U.S.) networks. Internet Service Providers prefer ISDN or Frame Relay. The Internet backbone network largely has shifted to Frame Relay or ATM, operating at T1 or T3 speeds at a minimum; much of the backbone is being upgraded to fiber optic facilities operating at speeds of 155 Mbps. The future of packet switching is assured because of its low cost and high availability. Additionally, low-intensity users will continue for many years to access the Internet on a dialup basis through X.25 packet switches.</p>
<p>X.25 is growing at record rates in Latin America, Central Europe, and other developing regions. In such areas, the poor quality of the networks make X.25&#8242;s error correction capabilities a must for data communications. Demand also is growing in Western Europe and North America, where Internet access is X.25-based, at least at the edges of the networks [8-21]. The postal administration in France recently built a X.25 LAN internetwork that eventually will extend to most of its 7,000 post offices. Bank branches in Belgium and other countries of Western Europe also are expanding their X.25 networks due to the low cost and high degree of flexibility [8-22].</p>
<p><b>Integrated Services Digital Network (ISDN)</b></p>
<p>ISDN (Integrated Services Digital Network) was first explored as a concept from 1968 to 1971 by a CCITT study group. A more focused conceptual study took place during the 1981 to 1984 CCITT study period. The first set of published standards recommendations appeared in 1984 in the form of a CCITT <i>Red Book</i>, which provided the basic framework for the concept, network architecture, <i>UNI (User Network Interface)</i> protocols and common channel signaling protocols. As a result of the 1985 to 1988 study period, a <i>Blue Book</i> was published, which provided description of supplementary services, rate adaptation, ISDN Frame Relay, and the initial set of B-ISDN (Broadband ISDN) recommendations. (The color of the books has no significance, other than the fact that a different color is chosen for each study period.)</p>
<p>ISDN is a suite of services based on a set of technologies, including transmission, switching, and signaling and control. ISDN is a set of international standards recommendations which will allow the provisioning of a wide range of services which are intended to be available on a ubiquitous basis. Additionally, the ISDN network is accessible through a standard set of interfaces-one for low-bandwidth applications and another for high-bandwidth.</p>
<p>The specific characteristics of ISDN include its entirely digital nature-CPE, transmission facilities and switching systems all are fully digital. Three channel types are identified, including <i>B-channels</i> (<i>Bearer channels</i>) that carry the information, <i>D-channels</i> (<i>Data channels</i>) for signaling and control, and <i>H-channels</i> (<i>High-speed channels</i>) for channel aggregation in order to accommodate bandwidth-intensive applications. The User Network Interface (UNI) protocols include <i>Basic Rate Interface (BRI)</i> for low-speed termination, and <i>Primary Rate Interface (PRI)</i> for high-speed access. <i>Common Channel Signaling System #7 (SS7)</i> is a fundamental requirement of ISDN.</p>
<p>Announced to the world with great fanfare, ISDN quickly captured the imagination of carriers, manufacturers and user organizations worldwide. ISDN offers the compelling advantages of improved bandwidth, flexibility, error performance, reliability, availability, and interconnection to a wide range of services. Unfortunately, it has stalled. For the past 25 years, ISDN has progressed at such a slow pace that it has become legendary. Among the many reasons for its slow development are slow standards development, lack of adherence to standards, lack of availability, regulatory hurdles, circuit and equipment costs, and poor marketing.</p>
<p>Standards development at the ITU-T is infamously slow. Standards traditionally were released every four years in monsoon fashion and with total droughts in the interim. Over time, the various committees were afforded the privilege of developing and releasing certain standards recommendations on an intermediate basis-standards now come in sprinkles and showers.</p>
<p>Standards from the ITU actually are in the form of standards recommendations. Individual member nations are free to implement ISDN options as they see fit, or to deviate from the standards, as long as international interconnectivity is accomplished at some reasonable level. The most notable international difference is that of the basic ISDN hierarchy. The North American version follows the T1 hierarchy, with PRI including 24 B channels; the European (ITU) version is based on E-1, providing 30 B channels. While this difference is understandable in the context of maintaining backward compatibility with existing networks, it also perpetuates issues of basic protocol incompatibility.</p>
<p>Systems manufacturers of CO exchanges and PBXs have a strong interest in maintaining the proprietary nature of their systems architectures. Therefore, they have implemented ISDN in distinctly different ways. <i>ISDN compatibility</i> became <i>ISDN compliance</i> -a decidedly lower level.</p>
<p>Additionally, carriers have implemented nonstandard versions of ISDN. Pacific Bell, for instance, offers ISDN at a rate of 56 Kbps per channel, rather than the standard 64 Kbps. This limitation is due to the fact that SS7 is not fully deployed in Pacific Bell&#8217;s carrier network; as a result, in-band signaling and control consumes 8 Kbps of channel bandwidth. Pacific Bell has announced its intention to rectify this situation in 1997, although the recently announced Pacific Bell/Southwestern Bell merger may affect that decision.</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Twelve%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Twelve%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Twelve%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Twelve%29+-+http://b2l.me/bdx6r&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Twelve%29&amp;body=Link: http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Packet%20Switching%20Applications%20and%20FuturesThe%20original%20application%20for%20X.25%20packet%20switching%20was%20that%20of%20interactive%20time-sharing%2C%20which%20involves%20long%20connect%20times%20and%20low%20data%20volume.%20While%20such%20applications%20are%20still%20supported%20effectively%20by%20X.25%2C%20contemporary%20applications%20include%20online%20interacti" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1630" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1630', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1630&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/12/chapter-8-conventional-public-data-networks-pdns-page-twelve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Eleven)</title>
		<link>http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/</link>
		<comments>http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/#comments</comments>
		<pubDate>Wed, 11 Jun 2008 07:01:24 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[airline reservation systems]]></category>
		<category><![CDATA[America Online]]></category>
		<category><![CDATA[American Airlines]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[Data Link Control]]></category>
		<category><![CDATA[disparate networks]]></category>
		<category><![CDATA[e-mail communications]]></category>
		<category><![CDATA[Frame Relay]]></category>
		<category><![CDATA[IBM]]></category>
		<category><![CDATA[Internet Service Providers]]></category>
		<category><![CDATA[ISDN]]></category>
		<category><![CDATA[ISP]]></category>
		<category><![CDATA[online information service]]></category>
		<category><![CDATA[Packet Assembly]]></category>
		<category><![CDATA[packet level protocols]]></category>
		<category><![CDATA[packet network]]></category>
		<category><![CDATA[packet networks]]></category>
		<category><![CDATA[Packet Switching]]></category>
		<category><![CDATA[packet-switched]]></category>
		<category><![CDATA[Packet-Switching Hardware]]></category>
		<category><![CDATA[Prodigy]]></category>
		<category><![CDATA[public packet networks]]></category>
		<category><![CDATA[reservation networks]]></category>
		<category><![CDATA[T1 facility]]></category>
		<category><![CDATA[United Airlines]]></category>
		<category><![CDATA[Value-Added Networks]]></category>
		<category><![CDATA[X.25]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/</guid>
		<description><![CDATA[Protocol Conversion As an option, packet-switched networks will accomplish protocol conversion (Figure 8.8). Protocol conversion can include any protocol that is well-established, well-understood, widely-deployed and, therefore, supported by the carrier. As this process of protocol conversion adds value, packet networks (X.25) are widely recognized as the first Value-Added Networks (VANs). Protocols supported typically include asynchronous, [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F11%2Fchapter-8-conventional-public-data-networks-pdns-page-eleven%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<p><b>Protocol Conversion</b></p>
<p>As an option, packet-switched networks will accomplish <i>protocol conversion</i> (Figure 8.8). Protocol conversion can include any protocol that is well-established, well-understood, widely-deployed and, therefore, supported by the carrier. As this process of protocol conversion adds value, packet networks (X.25) are widely recognized as the first <i>Value-Added Networks (VANs)</i>. Protocols supported typically include asynchronous, IBM Bisync (BSC), and IBM SDLC.</p>
<p><b>Latency</b></p>
<p><i>Latency</i> or <i>delay</i>, is a troublesome and limiting characteristic of packet networks. As each packet may take a different route though the network, each may travel a route of a different length; therefore, propagation delay may vary from packet to packet. Additionally, each packet may travel through a different number of packet nodes, each of which must act on the packet to read its address, check for errors, request retransmissions of errored packets, and so on-this fact compounds the issue of packet delay. Further, each packet may encounter different levels of congestion in the network, which may add to packet delays. Finally, additional delay is imposed on each packet if protocol conversion is required. While this process adds value, it does add to the latency factor. The end result is that some level of latency not only is assured, but also is variable and uncertain in magnitude [8-6].</p>
<p>While this characteristic of packet switching does not affect some applications, it renders others ineffective. For instance, e-mail communications over the Internet is not seriously impacted, although the delays may be aggravating at times. On the other hand, isochronous (stream-oriented) communications such as realtime audio, voice, or video are not effectively supported over a packet network.</p>
<p><b>Access</b></p>
<p>X.25 actually is the ITU-T standard describing the physical, link and packet level protocols between the user DTE/DCE and the network [8-17] and [8-18]. Devices capable of packetizing the data are connected over a X.25 link. In a true X.25 environment, the user accomplishes the packetizing process through DCE in the form of a <i>PAD</i> (<i>Packet Assembler/Disassembler</i>), the standard for which is <i>X.3</i>. The PAD also may contain intelligence for password protection and performance reporting [8-8].</p>
<p>Occasional or casual users typically access a packet network on a dialup basis, from asynchronous PCs through modems. In such a scenario, the actual packetizing of the data is performed at the originating network node. For example, individuals accessing the Internet through an online information service often use this approach.</p>
<p>Large user organizations often access the network via a dedicated, leased-line link to the closest network node. Such access often is in the form of an unchannelized T1 facility, perhaps supporting frame relay. Large users connecting substantial hosts to a X.25 network present data to the node under the terms of a protocol known as subscriber <i>Link Access Procedure Balanced (LAPB)</i>, which ensures error-free local access and egress on a full duplex (FDX) basis. The user data is segmented into a packet by the PAD, and encapsulated in a LAPB frame before presentation to the network [8-18] and [8-20]. The frame level procedure described in X.25 can be either the ISO <i>High Level Data Link Control Procedure (HDLC)</i> or IBM Bisync (BSC) [8-20]. <i>Internet Service Providers</i> (<i>ISP</i>s), for instance, make heavy use of such dedicated facilities.</p>
<p><b>Network Interconnection</b></p>
<p>X.25 networks are widely available as a Public Data Network (PDN) service offering, generally using packets of 128B or 256B. However, certain applications are supported more effectively by transmission of larger packets. For example, the airline reservation systems (e.g., American Airlines&#8217; SABRE and United Airlines&#8217; APOLLO) have deployed custom packet networks that use packet payloads of 1,028B. As this application involves the frequent transmission of relatively large sets of data (e.g., flight schedules, fares, and seating availability), a larger packet size is more appropriate. The larger packet size improves efficiency, because the payload is very large, while the overhead information is roughly the same as in the case of a smaller packet. While a larger packet is more likely to contain an errored bit, require retransmission and, therefore, reduce throughput; the custom reservation networks employ digital facilities in order to minimize this exposure.</p>
<p>The interconnection of such disparate networks is accomplished through an ITU-T standard known as <i>X.75</i>. Through an X.75 network-to-network interface, as depicted in Figure 8.8, issues of packet size are resolved in order that information flow is not affected.</p>
<p><b>Packet-Switching Hardware</b></p>
<p>The user of a X.25 packet network may require no hardware other than a PC and modem. Occasional and casual users of the Internet through an online information service (e.g., America Online, Australia Online, CompuServe and Prodigy) fall into this category. The packetizing of the asynchronous data is performed at the local X.25 node. Larger users will install DCE in the form of a <i>Packet Assembler/Disassembler (PAD)</i>, which is specified by the ITU-T as <i>X.3</i>. The PAD performs the packet assembly (segmentation) of the data for the transmitting device, disassembling the packet for the receiving device in order to reconstitute the data in its native format.</p>
<p>Packet carriers, of course, must invest in packet nodes, rather than circuit switches. Such packet nodes are intelligent devices capable of supporting complex routing tables, buffering packets in temporary memory, resolving packet errors, and accomplishing protocol conversions.</p>
<h4 align="left">Packet Switching Standards</h4>
<p>The ITU-T sets standards recommendations for packet switching. Those standards include the following [8-6], [8-8] and [8-20]:</p>
<ul>
<li>X.3: Packet Assembly/Disassembly functions </li>
<li>X.25: Interface between DCE and DTE for public packet networks </li>
<li>X.28: Terminal-to-PAD communications formats </li>
<li>X.29: Host-to-PAD communications formats </li>
<li>X.31: Packet-mode services over ISDN </li>
<li>X.32: Defines X.25 synchronous dialup mode </li>
<li>X.75: X.25 internetwork call control procedures </li>
</ul>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eleven%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eleven%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eleven%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eleven%29+-+http://b2l.me/bexu5&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eleven%29&amp;body=Link: http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Protocol%20ConversionAs%20an%20option%2C%20packet-switched%20networks%20will%20accomplish%20protocol%20conversion%20%28Figure%208.8%29.%20Protocol%20conversion%20can%20include%20any%20protocol%20that%20is%20well-established%2C%20well-understood%2C%20widely-deployed%20and%2C%20therefore%2C%20supported%20by%20the%20carrier.%20As%20this%20process%20of%20protocol%20conversion%20adds%20va" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1628" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1628', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1628&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/11/chapter-8-conventional-public-data-networks-pdns-page-eleven/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Ten)</title>
		<link>http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/</link>
		<comments>http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/#comments</comments>
		<pubDate>Tue, 10 Jun 2008 07:00:44 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[analog]]></category>
		<category><![CDATA[circuit-switched]]></category>
		<category><![CDATA[Control data]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[digital media]]></category>
		<category><![CDATA[early packet networks]]></category>
		<category><![CDATA[fiber optic]]></category>
		<category><![CDATA[packet networks]]></category>
		<category><![CDATA[Packet Switching]]></category>
		<category><![CDATA[target device]]></category>
		<category><![CDATA[terminal equipment]]></category>
		<category><![CDATA[Virtual Circuit]]></category>
		<category><![CDATA[X.25]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/</guid>
		<description><![CDATA[The payload data is encapsulated by a beginning flag (8 bits) and an ending flag (8 bits) that serve to the distinguish each packet from other packets traveling the same path. The beginning flag also serves as synchronizing bits in order that the packet nodes (intelligent switches) and the receiving terminal equipment synchronize on the [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F10%2Fchapter-8-conventional-public-data-networks-pdns-page-ten%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<p>The payload data is encapsulated by a beginning flag (8 bits) and an ending flag (8 bits) that serve to the distinguish each packet from other packets traveling the same path. The beginning flag also serves as synchronizing bits in order that the packet <i>nodes</i> (intelligent switches) and the receiving terminal equipment synchronize on the rate of transmission. As discussed in Chapter 7, this approach reduces overhead in data transmission and improves the efficiency of transmission. A packet address field of 8 bits (4 bits for the calling DTE and 4 bits for the called DTE) is prepended to the data in order that the various packet nodes might route each packet to the target device. Control data (8-16 bits) includes the packet sequence number so that the target node and terminal equipment are able to identify errored, corrupted, or lost packets, or to resequence the packets should they arrive out of order. Further, the packet sequence number allows the identification of lost or corrupted (errored) data packets in a stream of data. Additionally, the control data includes the number of the virtual circuit (4 bits) and virtual channel (8 bits) over which the data will travel, if a path has been preordained. Finally, error control data is included in the form of a CRC check (16 bits), As discussed in Chapter 7, this level of error control offers a high degree of reliability [8-17].</p>
<p><b>Packet Switching and Transmission</b></p>
<p>In a typical scenario, the transmitting terminal, equipped with a modem, dials a telephone number to gain access to a local packet node on a circuit-switched basis through the LEC central office exchange. Alternatively, a short-haul dedicated circuit might connect the user location directly to the packet node. Once the connection to the packet node is established, the transmitting device sends a control packet across the network to establish a data session with the target host computer. The originating node receives that packet, checks for transmission errors, reads the address, and forwards the packet towards the destination, across the most direct and available link. The process is repeated at the next node and so on, until the data reaches the packet node serving the target host. That node sends the packet to the target, which acknowledges its receipt and establishes a session by responding with a control packet to the originating device.</p>
<p>At that point, the originating device begins a stream of data, segmented into packets, with each packet numbered sequentially. Each packet is routed through the network independently, from node to node, in the direction of the target device, based on the most direct and available path at that instant. Should a reasonable route not be available immediately, the packet will be held in queue in buffer storage for a reasonable length of time, until a link becomes available. Once the communication session is complete, a control packet is sent across the network to terminate the data call.</p>
<p>In this scenario in Figure 8.7, each packet may take a different route from transmitter to receiver, in what is known as a <i>datagram</i> mode of transmission. This mode, therefore, requires that the packets be resequenced before being transmitted from the final node to the receiving device, ARPANET and its X.25 successor, pioneered the concepts of <i>locally adaptive routing</i>, <i>network message segmentation,</i> and <i>datagram transmission mode</i>.</p>
<p>The internodal links originally were dedicated analog trunks, which later were replaced by digital circuits-usually 56 Kbps DDS circuits. Over time, many of those circuits were replaced with T-carrier facilities. Currently, the facilities generally are high-speed fiber optic in nature, although all variety of analog and digital media are employed in consideration of specific network economics.</p>
<p><b>Error Control</b></p>
<p>X.25 also provides for error control through the use of a <i>Cyclic Redundancy Check (CRC)</i>. Should an error occur in transmission, the node receiving that packet will recognize the error and correct for it through requesting a retransmission of the <i>corrupted</i> packet. Each node acting on the packet repeats that process. Additionally, lost packets are discovered at the destination node through examination of packet sequence numbers. Retransmissions of lost packets are then requested.</p>
<p>Error control was extremely important in early packet networks, as the facilities consisted of analog twisted-pair. Through a cascading error control process, the integrity of the individual packets and of the packet stream could be improved. However, this process is CPU-intensive, adding to the cost of the packet nodes. Additionally, the process is time-consuming, as each packet must be checked for errors prior to being forwarded to the next node.</p>
<p><b>Connection-Oriented</b></p>
<p>It should be noted that X.25 packet switching is a <i>connection-oriented</i> service. A call is set up over a shared path (virtual circuit), over which all packets may travel in support of a logical connection. On the other hand, each packet may travel over a different path, depending on the availability of the various network links at any given moment in time. Each packet of data is separately addressed and, therefore, is capable of working its way through the network independently of the other packets in a stream of packetized data. This characteristic of packet networks is a critical advantage, as the network and all of its elements are shared among large number of users-the cost of transmission across such a network is very low in the context of an appropriate application. Remember X.25 is an interface standard and does not address the internal operation of the network.</p>
<p><b>Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs)</b></p>
<p>Packet switching supports a large number of conversations over virtual circuits using the same, previously designated circuit or path. While the individual packets of the typical user may travel different paths, large users may be supported by PVCs. In this scenario, all packets will travel the same path between two computers, which path is established by routing instructions programmed in the involved nodes. Alternatively, the network may select the most available and appropriate path on a call-by-call basis using Switched Virtual Circuits (SVCs). Again, all packets in a given session travel the same path [8-19].</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Ten%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Ten%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Ten%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Ten%29+-+http://b2l.me/bexu6&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Ten%29&amp;body=Link: http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A The%20payload%20data%20is%20encapsulated%20by%20a%20beginning%20flag%20%288%20bits%29%20and%20an%20ending%20flag%20%288%20bits%29%20that%20serve%20to%20the%20distinguish%20each%20packet%20from%20other%20packets%20traveling%20the%20same%20path.%20The%20beginning%20flag%20also%20serves%20as%20synchronizing%20bits%20in%20order%20that%20the%20packet%20nodes%20%28intelligent%20switches%29%20and%20the%20receiving" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1627" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1627', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1627&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/10/chapter-8-conventional-public-data-networks-pdns-page-ten/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Nine)</title>
		<link>http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/</link>
		<comments>http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/#comments</comments>
		<pubDate>Mon, 09 Jun 2008 07:00:22 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[airline reservation networks]]></category>
		<category><![CDATA[asynchronous communications]]></category>
		<category><![CDATA[bursty communications]]></category>
		<category><![CDATA[circuit-switched]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[Defense Advanced Research Project Agency Network]]></category>
		<category><![CDATA[early networks]]></category>
		<category><![CDATA[Europe]]></category>
		<category><![CDATA[federal government]]></category>
		<category><![CDATA[interactive applications]]></category>
		<category><![CDATA[interactive computer communications]]></category>
		<category><![CDATA[interactive data communications]]></category>
		<category><![CDATA[network technology]]></category>
		<category><![CDATA[occasional communications requirements]]></category>
		<category><![CDATA[Pacific Rim]]></category>
		<category><![CDATA[packet networks]]></category>
		<category><![CDATA[Packet Switching]]></category>
		<category><![CDATA[packet-switched]]></category>
		<category><![CDATA[Paul Baran]]></category>
		<category><![CDATA[RAND Corporation]]></category>
		<category><![CDATA[U.S. General Accounting Office]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[WAN]]></category>
		<category><![CDATA[wide area network]]></category>
		<category><![CDATA[wide area network technology]]></category>
		<category><![CDATA[X.25]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/</guid>
		<description><![CDATA[X.25 Packet Switching Packet switching was invented in the early 1960s by Paul Baran and his research associates for the RAND Corporation. Interestingly enough, the concept first was published in 1964 as a means of transmitting secure voice for military application. In the late 1960s, the U.S. General Accounting Office (GAO) issued a report suggesting [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F09%2Fchapter-8-conventional-public-data-networks-pdns-page-nine%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<h3>X.25 Packet Switching</h3>
<p>Packet switching was invented in the early 1960s by Paul Baran and his research associates for the RAND Corporation. Interestingly enough, the concept first was published in 1964 as a means of transmitting secure voice for military application. In the late 1960s, the U.S. General Accounting Office (GAO) issued a report suggesting that there existed a large number of data centers supported, at least in part, by the federal government. Further, the report indicated that many of those data centers were underutilized, and others were severely stressed. The imbalance was due largely to the lack of a wide area network technology that would allow the sharing of those resources on a cost-effective basis.</p>
<p>As a result of that study, the Advanced Research Project Agency Network (ARPANET), the first sophisticated packet switched network, was created in 1971. ARPANET was developed to link computers on a time-share basis in order to share computer resources on a cost-effectively [8-15]. Specifically, ARPANET was designed to support various defense, higher education, and research and development organizations [8-16]. In 1983 the majority of ARPANET users spun off to form the Defense Data Network (DDN), also called MILNET (MILitary NETwork), which included European and Pacific Rim continents. The United States and European locations which remained ARPANET then merged with the Defense Advanced Research Project Agency Network to become DARPA Internet [8-17].</p>
<p>Packet switching soon was commercialized and made widely available by Telenet, Graphnet (a facsimile-like service) and others. Packet switching was utilized very early on and extensively in Europe, as well. In fact, packet switching quickly became available in most countries, and currently is virtually ubiquitous. The CCITT (now the ITU-T) in 1976 internationally standardized X.25 as the interface for a packet-switched network.</p>
<p>The wide availability of packet switching has made it consistently popular over the last twenty years or so. Additionally, packet networks are highly cost-effective for applications that require many-to-many connectivity, and which involve relatively low data volumes. That popularity is growing and is ensured well into the future, largely through its historical deployment as the network technology of the Internet. It should be noted that X.25 is an interface specification, and does not define the internal operations characteristics of the data network.</p>
<h4 align="left">The Concept of Packet Switching</h4>
<p>The basic concept of packet switching is one of a highly flexible, shared network in support of interactive computer communications across a wide area network (WAN). Previously, large numbers of users spread across a wide area with only occasional communications requirements had no cost-effective means of sharing computer resources (<i>time-share</i>) from their remote terminals. In specific, the issue revolved around the fact that asynchronous communications are <i>bursty</i> in nature; data transmission is in bursts of keystrokes or data file transfers, with lots of idle time on the circuit between transmissions in either direction or relatively small amounts of data. Additionally, those early networks consisted of analog, twisted-pair facilities, which offered very poor error performance and relatively low bandwidth.</p>
<p>Existing circuit-switched networks certainly offered the required flexibility, as users could dial up the various host computers on which the desired database resided. Through a low-speed modem, data is passed over the analog network, although error performance was less than desirable. However, the cost of the connection was significant, because calls were billed based on the entire duration of the connection, even though the circuit was idle most of the time. Dedicated circuits could solve the cost issue, as costs are not usage-sensitive; however, dedicated circuits are expensive. Further, users tended not to be concentrated in locations where they could make effective use of dedicated circuits on a shared basis. Finally, large numbers of dedicated circuits would be required to establish connectivity to the various hosts.</p>
<p>Packet switching solved many of those problems, in the context of the limitations of the existing networks-namely, analog, twisted-pair. Packet-switched networks support low-speed, asynchronous, conversational and bursty communications between computer systems. As packet-switched network usage is billed to the user on the basis of the number of packets transmitted, they are very cost-effective for low-volume, interactive data communications. This cost advantage comes from the fact that the bursty nature of such interactive applications allows large volumes of data transmissions from multiple users to be aggregated in order to share network facilities and bandwidth [8-17]. Further, packet-switched networks perform the process of error detection and correction at each of the packet switches, or nodes, improving the integrity of the transmitted data considerably.</p>
<p>Understanding the concept and nature of packet switching requires the examination of a number of dimensions and characteristics of such networks including packet structure, switching and transmission, error control, connection-oriented service, latency, permanent virtual circuits versus switched virtual circuits, protocol conversion, and access techniques.</p>
<p><b>Packet Structure</b></p>
<p>Information is transported and switched through the network on the basis of <i>packets</i> (Figure 8.6). Each packet is of a fixed maximum size, typically containing 128B (B=byte or octet) or 256B of <i>payload</i> (user data); packet sizes of up to 4,096B can be accommodated in some networks. The typical upper limit of a packet is 1,024B [8-18], as is the case in many airline reservation networks.</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Nine%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Nine%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Nine%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Nine%29+-+http://b2l.me/beedm&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Nine%29&amp;body=Link: http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A X.25%20Packet%20SwitchingPacket%20switching%20was%20invented%20in%20the%20early%201960s%20by%20Paul%20Baran%20and%20his%20research%20associates%20for%20the%20RAND%20Corporation.%20Interestingly%20enough%2C%20the%20concept%20first%20was%20published%20in%201964%20as%20a%20means%20of%20transmitting%20secure%20voice%20for%20military%20application.%20In%20the%20late%201960s%2C%20the%20U.S.%20Genera" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1624" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1624', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1624&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/09/chapter-8-conventional-public-data-networks-pdns-page-nine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Eight)</title>
		<link>http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/</link>
		<comments>http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/#comments</comments>
		<pubDate>Sun, 08 Jun 2008 07:01:45 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[adapter cards]]></category>
		<category><![CDATA[addressable devices]]></category>
		<category><![CDATA[alternative leased-line technologies]]></category>
		<category><![CDATA[analog]]></category>
		<category><![CDATA[AT&T]]></category>
		<category><![CDATA[ATM]]></category>
		<category><![CDATA[broadband network technologies]]></category>
		<category><![CDATA[business to business]]></category>
		<category><![CDATA[carrier interconnection]]></category>
		<category><![CDATA[carrier network]]></category>
		<category><![CDATA[cent]]></category>
		<category><![CDATA[central site]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[data-intensive applications]]></category>
		<category><![CDATA[digital carrier]]></category>
		<category><![CDATA[enterprise-wide networking]]></category>
		<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[fiber optic]]></category>
		<category><![CDATA[Frame Relay]]></category>
		<category><![CDATA[hottest-selling equipment]]></category>
		<category><![CDATA[IBM]]></category>
		<category><![CDATA[International Data Corporation]]></category>
		<category><![CDATA[ISDN]]></category>
		<category><![CDATA[LAN internetworking technologies]]></category>
		<category><![CDATA[large bank]]></category>
		<category><![CDATA[leased-line technologies]]></category>
		<category><![CDATA[MCI]]></category>
		<category><![CDATA[Missouri]]></category>
		<category><![CDATA[multimedia communications]]></category>
		<category><![CDATA[online information services]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[remote bank branches]]></category>
		<category><![CDATA[software uploads/downloads]]></category>
		<category><![CDATA[SONET]]></category>
		<category><![CDATA[Sprint Corporation]]></category>
		<category><![CDATA[St. Louis]]></category>
		<category><![CDATA[Termination equipment]]></category>
		<category><![CDATA[Token Ring]]></category>
		<category><![CDATA[Toll-Free Switched Digital Service]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[USD]]></category>
		<category><![CDATA[video conferencing]]></category>
		<category><![CDATA[virtual private networks]]></category>
		<category><![CDATA[voice and data]]></category>
		<category><![CDATA[voice-intensive user applications]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/</guid>
		<description><![CDATA[Even in comparison to newer LAN internetworking technologies such as Frame Relay, T-carrier holds it own. For instance, a large bank in Missouri recently tripled the size of its private T-carrier network to 30 nodes. They have plans to increase the network by another 20 nodes by 1997. The primary application is the transport of [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F08%2Fchapter-8-conventional-public-data-networks-pdns-page-eight%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<p>Even in comparison to newer LAN internetworking technologies such as Frame Relay, T-carrier holds it own. For instance, a large bank in Missouri recently tripled the size of its private T-carrier network to 30 nodes. They have plans to increase the network by another 20 nodes by 1997. The primary application is the transport of data from ATM machines and remote bank branches to IBM mainframes located at the central site in St. Louis. The T-spans are leased from a combination of IXCs [8-11].</p>
<h4 align="left">T-carrier Developments and Futures</h4>
<p>The most significant recent and emerging developments of digital carrier relate to equipment and applications. Many manufacturers of CSUs/DSUs have incorporated intelligence into their products, in effect turning them into commodity-level MUXs. MUX manufacturers have developed adapter cards which allow the transmission of SNA, ISDN, Frame Relay, and ATM over T-carrier. Direct connection of Ethernet and Token Ring LANs is sometimes supported, with the MUX effectively acting as a bridge or router. Some manufacturers have also released direct SONET fiber optic interfaces at speeds up to 155 Mbps. Contemporary MUXs are addressable devices that can be managed and controlled remotely. Additionally, several manufacturers of traditional MUXs have incorporated inverse multiplexing capabilities. Inverse multiplexing will spread a high-bandwidth transmission (a videoconference or file transfer) across multiple DS-0 channels or across multiple DS-1 circuits.</p>
<p>T-carrier certainly offers cost and performance advantages when compared to individual trunking. Additionally, it is attractive due to its ability to integrate voice, data, video, and other forms of information. Additionally, competition and deregulation have caused T-carrier costs to drop dramatically during the past ten years, although they recently have begun to increase. Yet, in a private, leased-line network application, T-carrier suffers from the same flexibility and vulnerability issues that affect alternative leased-line technologies. As a result, virtual private networks have replaced T-carrier networks in many large, voice-intensive user applications. Additionally, ISDN competes effectively with T-carrier in PBX-CO trunking applications. In data-intensive applications, T-carrier is losing ground to emerging broadband network technologies such as Frame Relay, SMDS, and ATM. Ultimately, ATM is likely to replace T-carrier, altogether.</p>
<p>In the meantime, however, T-carrier continues to enjoy a strong following, with T1 MUXs being the hottest-selling equipment for enterprise-wide networking. According to International Data Corporation, 1995 mux sales were $1.2 billion worldwide, an increase of 20% over the previous year. IDC forecast sales of $1.5 billion for 1996 [8-11].</p>
<h3>Digital 800 Services</h3>
<p><i>Digital 800</i> service is a very new offering, having been announced and trialed in 1994 by AT&#038;T; the first general release offerings were those of AT&#038;T and MCI in January, 1995. The service currently is offered nationwide in the United States by AT&#038;T (800 Multimedia) and MCI (MCI 800 Digital Service) at a cost of less than 30 cents per minute. In the case of AT&#038;T, different rates apply to voice calls (typically 6 to 10 cents per minute under contract) and data (22 cents a minute for peak calling and 19 cents for off-peak) calls [8-12]. It is intended only for medium-to-large customers subscribing to high-volume 800 service offerings. Sprint Corporation announced its Toll-Free Switched Digital Service in December 1995.</p>
<p>Digital 800 uses the same numbering conventions used for voice calls, based on the North American Numbering Plan (NANP), which is governed by the ITU standard dialing scheme. Therefore, carrier interconnection is provided, a problem which plagues Switched 56/64 Kbps and Frame Relay data service offerings employing proprietary numbering schemes. Additionally, the 800 numbers are portable. In fact, the same, and even existing, 800 number can be used for both analog and digital voice and data.</p>
<p>The carrier network distinguishes the nature of the call and routes it to the call destination via the appropriate facilities. Digital calls are routed exclusively over digital facilities. Although capabilities differ by carrier, routing considerations can include type of call (digital data versus analog voice versus videoconference), originating NPA, and time-of-day. Separate and distinct and management reports are available for each class of calling activity [8-13].</p>
<p><i>Bandwidth-on-demand</i>, within limits, is provided as an inherent part of Digital 800. Digital bandwidth is provided in 64 Kbps increments (Nx64), up to full T1 at 1.544 Mbps. Depending on the nature of the call (voice versus data versus videoconference) the appropriate amount of bandwidth is supported.</p>
<p>Termination of Digital 800 requires a digital local loop, which can be in the form of ISDN, T1, or Switched 56/64 Kbps service. Termination equipment varies according to the nature of the terminating loop, although an Inverse MUX is required in order to associate multiple 64 Kbps channels where required. The carriers have suggested that the Inverse MUX requirement is temporary, to be eliminated as soon as multirate ISDN is available.</p>
<p>Access to the service can be in the form of an analog dialup connection, Switched 56/64 Kbps service, or ISDN. Where multiple channels are required for a high-bandwidth transmission, an inverse MUX currently is required at the originating end of the connection.</p>
<p>Digital 800 issues abound, as the LECs are not fully equipped at this point to handle the potential demand for the service. Therefore, users should not assume that Digital 800 termination is possible in every location. The features differ significantly between AT&#038;T and MCI, especially with respect to sophisticated routing capabilities of analog voice versus digital data calls. Additionally, the carriers have not yet established (nor are they likely to establish) network-to-network interfaces; in other words, all incoming call centers must use the same Digital 800 carrier.</p>
<p>Applications for Digital 800 primarily are business-to-business. The envisioned applications include catalog ordering, software uploads/downloads, online information services, publishing, graphics editing, videoconferencing, multimedia communications, video augmentation, and image augmentation. While the carriers have a lot of work to do in order to make Digital 800 ready for mass consumption, it is expected to be a mainstream business service offering by 1998 [8-13] and [8-14].</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eight%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eight%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eight%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eight%29+-+http://b2l.me/bexu7&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Eight%29&amp;body=Link: http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Even%20in%20comparison%20to%20newer%20LAN%20internetworking%20technologies%20such%20as%20Frame%20Relay%2C%20T-carrier%20holds%20it%20own.%20For%20instance%2C%20a%20large%20bank%20in%20Missouri%20recently%20tripled%20the%20size%20of%20its%20private%20T-carrier%20network%20to%2030%20nodes.%20They%20have%20plans%20to%20increase%20the%20network%20by%20another%2020%20nodes%20by%201997.%20The%20primary%20ap" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1622" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1622', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1622&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/08/chapter-8-conventional-public-data-networks-pdns-page-eight/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Seven)</title>
		<link>http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/</link>
		<comments>http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/#comments</comments>
		<pubDate>Sat, 07 Jun 2008 07:00:32 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[a 
CDSU]]></category>
		<category><![CDATA[Asia]]></category>
		<category><![CDATA[backbone network]]></category>
		<category><![CDATA[Canada]]></category>
		<category><![CDATA[carrier use]]></category>
		<category><![CDATA[clear channel communications]]></category>
		<category><![CDATA[Committee on European Post and Telegraph]]></category>
		<category><![CDATA[contemporary systems]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[cross-connect digital carrier bit streams]]></category>
		<category><![CDATA[data communications]]></category>
		<category><![CDATA[Digital Access Cross-Connect Systems]]></category>
		<category><![CDATA[digital carrier]]></category>
		<category><![CDATA[digital data networks]]></category>
		<category><![CDATA[E-1]]></category>
		<category><![CDATA[E-carrier]]></category>
		<category><![CDATA[Europe]]></category>
		<category><![CDATA[food chain]]></category>
		<category><![CDATA[Integrated Service Unit]]></category>
		<category><![CDATA[Internet backbone]]></category>
		<category><![CDATA[Internet Service Providers]]></category>
		<category><![CDATA[larger site]]></category>
		<category><![CDATA[leased-line networks]]></category>
		<category><![CDATA[LEC CO]]></category>
		<category><![CDATA[less communications-intensive environments]]></category>
		<category><![CDATA[low-speed data communications]]></category>
		<category><![CDATA[nodal processor]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[private digital carrier networks]]></category>
		<category><![CDATA[private networks]]></category>
		<category><![CDATA[resident site]]></category>
		<category><![CDATA[Statistical Time Division Multiplexers]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[video conferencing]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/</guid>
		<description><![CDATA[Channel Service Units (CSUs) and Digital Service Units (DSUs) Discussed at length in Chapters 2 and 7, DSUs are devices which, in combination, interface the user environment to the digital network at the physical (mechanical) and electrical level, corresponding with Layer 1 of the OSI model. In contemporary systems, they generally are combined into a [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F07%2Fchapter-8-conventional-public-data-networks-pdns-page-seven%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<h4 align="left">Channel Service Units (CSUs) and Digital Service Units (DSUs)</h4>
<p>Discussed at length in Chapters 2 and 7, DSUs are devices which, in combination, interface the user environment to the digital network at the physical (mechanical) and electrical level, corresponding with Layer 1 of the OSI model. In contemporary systems, they generally are combined into a single device, known as a <i>CDSU</i> or an <i>ISU (Integrated Service Unit)</i>, which may be under the skin of another device, such as a multiplexer (MUX). They are used in a wide variety of digital data networks, including DDS and T-carrier.</p>
<p><b>Multiplexers (MUXs)</b></p>
<p>MUXs are a significant step up from channel banks in terms of intelligence, capability, and cost. Originally based on channel banks and containing CSUs and DSUs, contemporary Statistical Time Division Multiplexers (Stat MUXs) offer a tremendous range of flexibility and capability. MUXs typically offer capabilities that include support for both channelized and non-channelized service, support for multiple medium interfaces (e.g., twisted-pair, coax, and fiber), support for multiple trunk types (e.g., DID and combination), support for superrate transmission (&gt;64 Kbps channels), and support for subrate transmission (&lt;64 Kbps channels). Additionally, they offer the advantage of user-definable configuration, internal diagnostics, voice compression, and T-carrier to-E-carrier protocol conversion. Intelligent MUXs also have the ability to allocate bandwidth on a priority basis for specified users and applications, and even to reserve bandwidth, perhaps for a scheduled videoconference. Finally, intelligent MUXs can allocate bandwidth on a dynamic basis, assigning channel capacity as required to meet the demands of traffic. For instance, a videoconference may require superrate capacity for a short period of time, multiple low-speed data communications may require subrate channels for a brief moment and, at other times, the entire capacity of the circuit may be in support of 32 Kbps voice conversations.</p>
<p><b>Nodal Multiplexers</b></p>
<p>Nodal MUXs, a further step up the MUX food chain, act as T-carrier network switches. In addition to serving as a traditional MUX for the resident site, they also serve as true networking devices, much as does a combined CO/Tandem switch in the voice world. Nodal MUXs provide the additional function of dynamic alternate routing (Figure 8.5), which allows them to switch traffic over an alternate path in the event of a condition of blockage or failure in the primary circuit.</p>
<p><b>Digital Access Cross-Connect Systems (DACS or DCCS)</b></p>
<p>These are nonblocking, electronic common control switches which serve to cross-connect digital carrier bit streams on a buffered basis by redirecting individual channels or frames from one circuit to another. Effectively, they provide an electronic common control means of cross-connection which replaces the traditional manual method of physical cross-connection of wires. A DAC can redirect traffic in order to better manage the capacity and performance of the T-carrier network [8-10]. Although originally developed for carrier use, DACS also are deployed in large user organizations to support private digital carrier networks. Smaller versions, residing on a PC, are available for less communications-intensive environments. Typically of significant port capacity, DACS provide support for DS-0, DS-1, and DS-3 [8-3].</p>
<h4 align="left">Variations on the Theme: E-carrier and J-carrier</h4>
<p>While the theme for digital carrier was set in the United States, the concept was quickly adopted by the CEPT (Committee on European Post and Telegraph). The resulting E-carrier standard is quite different in its implementation. The Japanese version, J-carrier, is similar to T-carrier, but with differences sufficient to cause incompatibility.</p>
<p><i>E-carrier</i> is characterized by an entirely different digital hierarchy, (Table 8.2) beginning with E-1, at 2.048 Mbps. E-1 supports 30 clear information channels; 2 channels are set aside for signaling and control. This non-intrusive signaling and control convention, plus the fact that there are no 1s density rules which apply, results in E-carrier&#8217;s providing clear channel communications of a full 64 Kbps per channel. The E-carrier <i>multiframe</i> (16 Frames) corresponds to the T-carrier superframe (12-24 Frames).</p>
<p><i>J-carrier</i> is quite similar to T-carrier, although the hierarchy is slightly different. Line coding and framing also vary from the U.S. ANSI approach. The advantages of these differences are questionable; incompatibility is assured, which fact should not be surprising. The J-carrier digital hierarchy begins at 1.544 Mbps, proceeding to 6.313 Mbps, 32.064 Mbps (J1), 97.728 Mbps (J3), and 397.20 Mbps [8-3] and [8-6].</p>
<h4 align="left">Fractional T1</h4>
<p><i>Fractional T1</i> (<i>FT1</i>), previously offered only in Canada, first was tariffed in the United States in 1987 by Cable and Wireless. Now offered by many LECs and IXCs, FT1 provides T1 functions and features, but involving fewer DS-0s. It is offered in fractions of T1 channel capacity, generally at 1, 2, 4, 6, 8 or 12 DS-0 channels. Subrate transmission also is available at speeds of 9.6 Kbps. FT1 is particularly applicable where remote locations are connected to a more significant location such as a regional office. At that point, they connect to a full T1 MUX or nodal processor, which aggregates the traffic with that of the larger site over a full T1/T3 backbone network. FT1 also serves videoconferencing, data communications, and other applications that require more than 56/64 Kbps, but less than a full T1 [8-4].</p>
<h4 align="left">T-carrier Applications</h4>
<p>The applications for Digital Carrier are many. Large user organizations find Digital Carrier services to be highly cost-effective for local loop access, typically replacing multiple, individual PBX trunks. Large corporations find T-carrier effective for private, leased-line networks or access to virtual private networks (VPNs). The ability of T-carrier to accommodate voice, facsimile, data, video, and image information on an unbiased basis and, therefore, to eliminate or reduce the number and variety of specialized circuits, offers great advantage.</p>
<p>Internet service providers commonly use T-carrier for access to the LEC CO, as well as access to an Internet backbone provider. Given current US tariffs, a T1 clearly becomes cost-effective in replacement of 8-10 or more individual circuits; a T3 becomes cost-effective at a level of 3-4 T1s. Notably, the relationship is far different in Europe and parts of Asia, where leased line costs are considerably higher.</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seven%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seven%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seven%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seven%29+-+http://b2l.me/bexu8&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Seven%29&amp;body=Link: http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Channel%20Service%20Units%20%28CSUs%29%20and%20Digital%20Service%20Units%20%28DSUs%29Discussed%20at%20length%20in%20Chapters%202%20and%207%2C%20DSUs%20are%20devices%20which%2C%20in%20combination%2C%20interface%20the%20user%20environment%20to%20the%20digital%20network%20at%20the%20physical%20%28mechanical%29%20and%20electrical%20level%2C%20corresponding%20with%20Layer%201%20of%20the%20OSI%20model.%20In%20conte" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1621" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1621', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1621&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/07/chapter-8-conventional-public-data-networks-pdns-page-seven/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapter 8 : Conventional Public Data Networks (PDNs) (Page Six)</title>
		<link>http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/</link>
		<comments>http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/#comments</comments>
		<pubDate>Fri, 06 Jun 2008 07:00:31 +0000</pubDate>
		<dc:creator>antz</dc:creator>
				<category><![CDATA[Communications Systems and Networks]]></category>
		<category><![CDATA[Amplitude Modulation]]></category>
		<category><![CDATA[analog]]></category>
		<category><![CDATA[AT&T]]></category>
		<category><![CDATA[carrier networks]]></category>
		<category><![CDATA[carrier side]]></category>
		<category><![CDATA[coaxial cable]]></category>
		<category><![CDATA[Conventional Public Data Networks]]></category>
		<category><![CDATA[digital carrier signals]]></category>
		<category><![CDATA[DS]]></category>
		<category><![CDATA[fiber optic]]></category>
		<category><![CDATA[Japan]]></category>
		<category><![CDATA[Kbps channel]]></category>
		<category><![CDATA[microwave]]></category>
		<category><![CDATA[network management]]></category>
		<category><![CDATA[North America]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[Remington m24]]></category>
		<category><![CDATA[T-carrier]]></category>
		<category><![CDATA[unintelligent devices]]></category>
		<category><![CDATA[voice and data]]></category>

		<guid isPermaLink="false">http://doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/</guid>
		<description><![CDATA[Quantizing variations are sometimes employed, although they are neither generally accepted nor widely deployed. Those variations include the following [8-5]: Continuously Variable Slope Delta (CVSD): Compression Ratio = 4:1 (16 Kbps), or 8:1 (9.6 Kbps) Vector Quantizing Code (VQC): Compression Ratio = 4:1 (16 Kbps) High Capacity Voice (HCV): Compression Ratio = 8:1 (8 Kbps) [...]]]></description>
			<content:encoded><![CDATA[<div class="fblike_button" style="margin: 10px 0;"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.doktertomi.com%2F2008%2F06%2F06%2Fchapter-8-conventional-public-data-networks-pdns-page-six%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;font=tahoma&amp;colorscheme=light" scrolling="no" frameborder="0" allowTransparency="true" style="border:none; overflow:hidden; width:450px; height:23px"></iframe></div>
<p><i>Quantizing variations</i> are sometimes employed, although they are neither generally accepted nor widely deployed. Those variations include the following [8-5]:</p>
<ul>
<li>Continuously Variable Slope Delta (CVSD): Compression Ratio = 4:1 (16 Kbps), or 8:1 (9.6 Kbps) </li>
<li>Vector Quantizing Code (VQC): Compression Ratio = 4:1 (16 Kbps) </li>
<li>High Capacity Voice (HCV): Compression Ratio = 8:1 (8 Kbps) </li>
</ul>
<h4 align="left">Framing</h4>
<p>T-carrier employs a very specific set of conventions to transmit information, with framing being one example. Using T1 as an illustration, each channel of input is time division multiplexed into a T1 <i>frame</i>, or set of data. In other words, conversation 1 might be allocated time slot 1 (channel 1), conversation 2 might be allocated time slot 2 (channel 2), and so on through conversation 24 and channel 24. That set of sampled data is inserted into frame 1, which is appended by a framing bit in order to distinguish it from subsequent frames of data. The process is then repeated for frame 2, and so on.</p>
<p>The combined processes of voice encoding and framing yield a total T1 bandwidth of 1.544 Mbps. Of that total, 1.536 Mbps is available for information transfer, as noted in the following calculation; the remaining 8 Kbps is required for framing.</p>
<p><code>4,000 Hz x 2<br /> 8,000 Samples/Second<br /> x 8 Bits per Sample<br /> 64 Kbps = DS-0<br /> x24 Channels<br /> 1.536 Mbps<br /> + 8 Kbps Framing<br /> 1.544 Mbps = DS-1 (T1)</code>
<p>There exist several generations of framing conventions, designated as D1, D2, D3, D4, and Extended SuperFrame (ESF). Additionally, the ITU-T has developed an international set of recommendations for framing digital carrier signals.</p>
<p><b>D1 Framing</b></p>
<p>Developed in 1962, D1 framing <i>robbed</i> the <i>Least Significant Bit (LSB)</i>, the eighth bit, in order to insert a signaling bit in each channel of each frame; signaling bits were alternating <i>1</i>s and <i>0</i>s. The quality of digitized voice conversation was not affected, as 7 bits are satisfactory for reconstructing a high-quality approximation of the analog voice input. Data, however, is seriously impacted by truncating an 8-bit value. As a result, data transmission was limited to 56 Kbps. Data remains limited to 56 Kbps in many carrier networks due to similar limitations imposed in D4 framing. While D1 framing no longer is used, the least significant bit is still robbed, even in the contemporary D4 framing technique.</p>
<p><b>D2 Framing</b></p>
<p>D2 Framing was used to create a superframe, a 12-bit pattern for framing locators. Information was transmitted in a 12-frame sequence or <i>superframe</i>.</p>
<p><b>D3 Framing</b></p>
<p>D3 Framing, which is still in use, assumes that all inputs are analog, whether they are voice or data. It uses a <i>superframe</i> format and sequence bits.</p>
<p><b>D4 Framing (M24 Superframe)</b></p>
<p>D4 Framing (M24 Superframe) uses a repeating 12-bit sequence (1000 1101 1100), repeated every 12 frames, to allow robbing of the least significant bits of the sixth and twelfth frames only. Voice and data are accommodated, with data being treated as a digital input. While this improves available signal capacity and yields better voice transmission, data is still limited to 56 Kbps. Additionally, <i>one&#8217;s density</i> must be maintained through the insertion of <i>stuff bits</i>. Considered together, the twelve frames are designated a superframe.</p>
<p><b>Extended Superframe (ESF)</b></p>
<p>Extended Superframe (ESF), originally tariffed by AT&#038;T in 1985, is now widely available. ESF superframes are 24 frames in length; signaling is accomplished in frames 6, 12, 18, and 24. The bit positions liberated by ESF are used for error checking and network management. ESF offers the advantages of nondisruptive error detection (6-bit CRC) and network management, using only 8 Kbps of overhead [8-2], [8-3], and [8-4].</p>
<p><b>ITU-T Framing Conventions</b></p>
<p>ITU-T Framing Conventions are quite different from those described above, which are used in North America and Japan (modified). ITU conventions call for Level 1 (E1) to employ 32 DS-0 channels, 30 for information and two specifically designated for signaling and control. The functional equivalent of framing bits are carried in the first such DS-0 channel, while the second carries signaling bits [8-5].</p>
<p><b>Transmission</b></p>
<p>Transmission facilities can include unshielded twisted-pair (22 or 24 gauge), shielded copper, coaxial cable, microwave, satellite, infrared or fiber optic cable. Therefore, Digital Carrier is medium-independent. A T-carrier circuit is also know as a <i>T-span</i> or <i>T1 pipe</i>. Regenerative repeaters are used to reshape and boost the signal at regular intervals, every 6,000 ft. in a twisted-pair system. The repeaters are powered by the CO exchange at levels up to 100 volts. The repeaters maintain their synchronization through the transmission bit stream. Therefore bipolar transmission is critical, as is the 1&#8242;s density rule.</p>
<h4 align="left">Hardware</h4>
<p>DS-1 equipment is required both for end-user organizations and for carriers. That equipment must be of the same generation in order to effect compatibility. Ideally, within the user organization, it should be of the same origin and software generic as is the carrier side in order to deliver the same functionality and feature set.</p>
<p><b>Channel Banks</b></p>
<p>Designed for voice-only service in analog applications, channel banks are used for interfacing analog switches (PBXs and COs) to DS-1 circuits. Channel banks perform two functions in sequence. First, they multiplex up to 24 (T1) analog signals on a common <i>Pulse Amplitude Modulation</i> (<i>PAM</i>) electrical bus. Second, they encode the individual PAM channels into a digital format, using PCM, for transmission over a DS-1 circuit [8-3] and [8-4].</p>
<p>Channel banks also will accommodate digital data. As relatively unintelligent devices, channel banks place each conversation on a separate channel; for instance, a 9.6 Kbps data conversation occupies a 64 Kbps channel, just as does a 56 Kbps data transmission or a digitized voice conversation. Therefore, channel banks do not make efficient use of available bandwidth. Combined channel banks and CSUs often are in the form of printed circuit boards which fit into PBX card slots for seamless interface to a network T1 circuit.</p>
<p>
<ul>
<li><a target="_blank" href="http://www.doktertomi.com" title="Free Inspirations, News, Guides, Tips and Tricks" target="_blank">Doktertomi.com</a> : Free Inspirations, News, Guides, Tips and Tricks</li>
<li><a target="_blank" href="http://www.botolempangan.info" title="Everything You Need To Know About Makassar" target="_blank">Makassar Today</a> : Everything You Need To Know About Makassar</li>
<li><a target="_blank" href="http://www.masterbiznet.com" title="Masternya Bisnis Internet" target="_blank">Masterbiznet.com</a> : Masternya Bisnis Internet</li>
<li><a target="_blank" href="http://www.workinthewebsite.com" title="News, Guides, Tips and Tricks on Website Monitization and Advertising" target="_blank">Work in The Website</a> : News, Guides, Tips and Tricks on Website Monitization and Advertising</li>
</ul>


<div class="shr-bookmarks shr-bookmarks-expand shr-bookmarks-center shr-bookmarks-bg-shr">
<ul class="socials">
		<li class="shr-blogger">
			<a href="http://www.blogger.com/blog_this.pyra?t&amp;u=http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/&amp;n=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Six%29&amp;pli=1" rel="nofollow" class="external" title="Blog this on Blogger">Blog this on Blogger</a>
		</li>
		<li class="shr-comfeed">
			<a href="http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Six%29" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/&amp;t=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Six%29" rel="nofollow" class="external" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Six%29+-+http://b2l.me/bexu9&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-yahoomail">
			<a href="http://compose.mail.yahoo.com/?Subject=Chapter+8+%3A+Conventional+Public+Data+Networks+%28PDNs%29+%28Page+Six%29&amp;body=Link: http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/ (sent via shareaholic)%0D%0A%0D%0A----%0D%0A Quantizing%20variations%20are%20sometimes%20employed%2C%20although%20they%20are%20neither%20generally%20accepted%20nor%20widely%20deployed.%20Those%20variations%20include%20the%20following%20%5B8-5%5D%3AContinuously%20Variable%20Slope%20Delta%20%28CVSD%29%3A%20Compression%20Ratio%20%3D%204%3A1%20%2816%20Kbps%29%2C%20or%208%3A1%20%289.6%20Kbps%29%20Vector%20Quantizing%20Code%20%28VQC%29%3A%20Compression%20Ratio%20" rel="nofollow" class="external" title="Email this via Yahoo! Mail">Email this via Yahoo! Mail</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

<p><img src="http://wptextads.s3.amazonaws.com/images/press/wpta-20x20.jpg" alt="WP Text Ads" border="0" /> <a rel="nofollow" href="http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1620" onclick="window.open('http://www.doktertomi.com/wp-content/plugins/wptextads1/wpta.php?wpta_form=1&wpta_cmd=buy&wpta_id=1620', 'nehemiah_window', 'width=550,height=530,scrollbars,resizable'); return false;">Want visitors to your site? Buy an ad here.</a></p><img src="http://www.doktertomi.com/?ak_action=api_record_view&id=1620&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.doktertomi.com/2008/06/06/chapter-8-conventional-public-data-networks-pdns-page-six/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
