<?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>Wireless Oom &#187; dpdch</title>
	<atom:link href="http://wireless.pyncus.com/tag/dpdch/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireless.pyncus.com</link>
	<description>Build and Share wireless technology</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:38:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why data rates of uplink and downlink DPDCH are different even with the same spreading factor?</title>
		<link>http://wireless.pyncus.com/2009/06/23/why-data-rates-of-uplink-and-downlink-dpdch-are-different-even-with-the-same-spreading-factor/</link>
		<comments>http://wireless.pyncus.com/2009/06/23/why-data-rates-of-uplink-and-downlink-dpdch-are-different-even-with-the-same-spreading-factor/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 14:16:23 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[bit rate]]></category>
		<category><![CDATA[dpcch]]></category>
		<category><![CDATA[dpdch]]></category>
		<category><![CDATA[sf]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=250</guid>
		<description><![CDATA[Let us consider the case of spreading factor 256.
Remember that each slot has 2560 chips.
2560/256 = 10 symbol can be sent in each slot.
For uplink case, remember that DPDCH and DPCCH are code multiplexed. Here 1 symbol is divided into I and Q component. Thus, 1 symbol can convey 1 bit for uplink case (with [...]]]></description>
			<content:encoded><![CDATA[<p>Let us consider the case of spreading factor 256.</p>
<p>Remember that each slot has 2560 chips.</p>
<p>2560/256 = 10 symbol can be sent in each slot.</p>
<p>For uplink case, remember that DPDCH and DPCCH are code multiplexed. Here 1 symbol is divided into I and Q component. Thus, 1 symbol can convey 1 bit for uplink case (with QPSK).</p>
<p>Thus, uplink DPDCH has 10 bit data in a slot with 256 SF.</p>
<p>For downlink case, DPDCH and DPCCH are time multiplexed.</p>
<p>Thus, 1 symbol can still convey 2 bits.</p>
<p>Thus, downlink has 20 bit data in a slot with 256 SF. However, remember that some of bits are allocated to DPCCH control information.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/23/why-data-rates-of-uplink-and-downlink-dpdch-are-different-even-with-the-same-spreading-factor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is the time relation between uplink and downlink dedicated physical channels?</title>
		<link>http://wireless.pyncus.com/2009/06/23/what-is-the-time-relation-between-uplink-and-downlink-dedicated-physical-channels/</link>
		<comments>http://wireless.pyncus.com/2009/06/23/what-is-the-time-relation-between-uplink-and-downlink-dedicated-physical-channels/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 06:54:38 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[dpcch]]></category>
		<category><![CDATA[dpdch]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=242</guid>
		<description><![CDATA[The uplink frame should start 1024 chips after the reception of the first part of the downlink frame.
]]></description>
			<content:encoded><![CDATA[<p>The uplink frame should start 1024 chips after the reception of the first part of the downlink frame.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/23/what-is-the-time-relation-between-uplink-and-downlink-dedicated-physical-channels/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to change dedicated channel bit rate in uplink and downlink?</title>
		<link>http://wireless.pyncus.com/2009/06/23/how-to-change-dedicated-channel-bit-rate-in-uplink-and-downlink/</link>
		<comments>http://wireless.pyncus.com/2009/06/23/how-to-change-dedicated-channel-bit-rate-in-uplink-and-downlink/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 06:20:47 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[bit rate]]></category>
		<category><![CDATA[dpcch]]></category>
		<category><![CDATA[dpdch]]></category>
		<category><![CDATA[dtx]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=235</guid>
		<description><![CDATA[Uplink:
uplink transmission is continuos and changes in bit rate can be achieved by modifying the spreading factor of the code sequence being used.
Downlink:
Spreading factor is chosen to support the highest bit rate of TFCS.
The variable bit rate is implemented with discontinuous transmission (DTX), swithcing off the transmission during the DPDCH fields in certain time slots.
]]></description>
			<content:encoded><![CDATA[<p>Uplink:</p>
<p>uplink transmission is <a href="http://wirelessoom.wordpress.com/2009/06/23/why-uplink-dpcch-and-dpdch-are-code-multiplexed-and-downlink-dpcch-and-pddch-are-time-multiplexed/">continuos </a>and changes in bit rate can be achieved by modifying the spreading factor of the code sequence being used.</p>
<p>Downlink:</p>
<p>Spreading factor is chosen to support the highest bit rate of TFCS.</p>
<p>The variable bit rate is implemented with discontinuous transmission (DTX), swithcing off the transmission during the DPDCH fields in certain time slots.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/23/how-to-change-dedicated-channel-bit-rate-in-uplink-and-downlink/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why uplink DPCCH/DPDCH are code multiplexed and downlink DPCCH/PDDCH are time multiplexed ?</title>
		<link>http://wireless.pyncus.com/2009/06/23/why-uplink-dpcch-and-dpdch-are-code-multiplexed-and-downlink-dpcch-and-pddch-are-time-multiplexed/</link>
		<comments>http://wireless.pyncus.com/2009/06/23/why-uplink-dpcch-and-dpdch-are-code-multiplexed-and-downlink-dpcch-and-pddch-are-time-multiplexed/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 06:05:19 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[dpcch]]></category>
		<category><![CDATA[dpdch]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=231</guid>
		<description><![CDATA[First, DPCCH and DPDCH are time-multiplexed in the downlink direction.
Note that if code multiplexing was used, each DPCH (DPCCH and DPDCH) requires two channelization codes, and is less efficient.
Second, the control channel must always be present because of the power control mechanism. But, what if there is no user data?
This will result in a pulsed [...]]]></description>
			<content:encoded><![CDATA[<p>First, DPCCH and DPDCH are time-multiplexed in the downlink direction.</p>
<p>Note that if code multiplexing was used, each DPCH (DPCCH and DPDCH) requires two channelization codes, and is less efficient.</p>
<p>Second, the control channel must always be present because of the power control mechanism. But, what if there is no user data?</p>
<p>This will result in a pulsed transmission, which is not a problem in the downlink, as common channels (CPICH etc) will be sent all the time.</p>
<p>In the uplink, however, the discontinous transmission with time multiplexing would cause severe electromagnetic problems.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/23/why-uplink-dpcch-and-dpdch-are-code-multiplexed-and-downlink-dpcch-and-pddch-are-time-multiplexed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How many DPCCH channels are in a UE?</title>
		<link>http://wireless.pyncus.com/2009/06/20/how-many-dpcch-channels-are-in-a-ue/</link>
		<comments>http://wireless.pyncus.com/2009/06/20/how-many-dpcch-channels-are-in-a-ue/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 22:56:50 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[dpcch]]></category>
		<category><![CDATA[dpdch]]></category>
		<category><![CDATA[tfci]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=176</guid>
		<description><![CDATA[User data is carried on one or more DPDCHs.
However, there is a single DPCCH with a fixed spreading factor 256.
The below depicts channelization and scrambling for multiple uplink DPDCHs.

The below shows the transmission with multiple downlink DPDCHs

Note that DPCCH contains TFCI (transport format combination indicator).
This means that TFCI will apply to all DPDCHs at the [...]]]></description>
			<content:encoded><![CDATA[<p>User data is carried on one or more DPDCHs.</p>
<p>However, there is a <strong>single</strong> DPCCH with a fixed spreading factor 256.</p>
<p>The below depicts channelization and scrambling for multiple uplink DPDCHs.</p>
<p><img class="alignnone size-full wp-image-177" title="uplinkdpch" src="http://wirelessoom.files.wordpress.com/2009/06/uplinkdpch.png" alt="uplinkdpch" width="480" height="503" /></p>
<p>The below shows the transmission with multiple downlink DPDCHs</p>
<p><img class="alignnone size-full wp-image-178" title="downlinkdpch" src="http://wirelessoom.files.wordpress.com/2009/06/downlinkdpch.png" alt="downlinkdpch" width="480" height="446" /></p>
<p>Note that DPCCH contains TFCI (transport format combination indicator).</p>
<p>This means that TFCI will apply to all DPDCHs at the same time.</p>
<p>Also, spreading facotrs for DPDCHs are the same.</p>
<p>Note that DPDCH data rate varies frame by frame.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/20/how-many-dpcch-channels-are-in-a-ue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Overview of UMTS physical channels</title>
		<link>http://wireless.pyncus.com/2009/06/20/overview-of-umts-physical-channels/</link>
		<comments>http://wireless.pyncus.com/2009/06/20/overview-of-umts-physical-channels/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 06:07:03 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[aich]]></category>
		<category><![CDATA[cpich]]></category>
		<category><![CDATA[dpcch]]></category>
		<category><![CDATA[dpdch]]></category>
		<category><![CDATA[hs-dpcch]]></category>
		<category><![CDATA[hs-pdsch]]></category>
		<category><![CDATA[hs-scch]]></category>
		<category><![CDATA[p-ccpch]]></category>
		<category><![CDATA[physical channel]]></category>
		<category><![CDATA[pich]]></category>
		<category><![CDATA[prach]]></category>
		<category><![CDATA[s-ccpch]]></category>
		<category><![CDATA[sch]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=166</guid>
		<description><![CDATA[The combination of different frequency, code and time specify a set of physical channels.
Two main categories: (1) dedicated and (2) control
1. Dedicated physical channels
a. DPDCH (Dedicated Physical Data Channel):
carries DCH transport channel.
As with DCH, this exists both in the uplink and downlink.
closed loop power control (1500 Hz/sec)
b. DPCCH (Dedicated Physical Control Channel):
relates to DPDCH and [...]]]></description>
			<content:encoded><![CDATA[<p>The combination of different frequency, code and time specify a set of physical channels.</p>
<p>Two main categories: (1) dedicated and (2) control</p>
<p>1. Dedicated physical channels</p>
<p>a. DPDCH (Dedicated Physical Data Channel):</p>
<p>carries DCH transport channel.</p>
<p>As with DCH, this exists both in the uplink and downlink.</p>
<p>closed loop power control (1500 Hz/sec)</p>
<p>b. DPCCH (Dedicated Physical Control Channel):</p>
<p>relates to DPDCH and transmits physical layer signal information (e.g., power control commands and synch. sequences)</p>
<p>In the uplink, it is code multiplexed with DPDCH.</p>
<p>In the downlink, it is time multiplexed with DPDCH.</p>
<p>Note that this has nothing with DCH or DCCH or DTCH!</p>
<p>2. Physical control channels</p>
<p>a. P-CCPCH (Primary Common Control Physical Channel):</p>
<p>only in the downlink.</p>
<p>fixed bit rate of 30kbps (spreading factor 256)</p>
<p>carry the BCH transport channel.</p>
<p>b. S-CCPCH (Secondary Common Control Physical Channel):</p>
<p>carry the PCH and FACH transport channels.</p>
<p>only in the downlink.</p>
<p>different bit rates.</p>
<p>c. SCH (Synchronization Channel):</p>
<p>used for cell search and the first channel that UE needs to know.</p>
<p>allow synchronization at frame and code sequence of P-CCPCH.</p>
<p>d. CPICH (Common Pilot Channel):</p>
<p>transmits pre-defined bit sequence in downlink with 30kbps</p>
<p>allows UEs to measure power of cells</p>
<p>e. PRACH (Physical Random Access Channel):</p>
<p>uplink direction; carries RACH transport channel</p>
<p>open loop power control</p>
<p>f. HS-PDSCH (High Speed Physical Downlink Shared Channel):</p>
<p>carries HS-DSCH transport channel; multicode transmission with spreading factor 16</p>
<p>2ms frame with 3 slots</p>
<p>QPSK or 16-QAM</p>
<p>HARQ</p>
<p>g. HS-SCCH (High Speed Shared Control Channel):</p>
<p>fixed bit rate of 60kbps carry downlink signal for HS-DSCH.</p>
<p>Data will come soon.. be ready.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>No transport related but</p>
<p>a. AICH (Acquisition Indicator Channel):</p>
<p>used for PRACH response</p>
<p>b. PICH (Paging Indicator Channel):</p>
<p>this is associated with S-CCPCH to which a PCH channel is mapped.</p>
<p>carries paging indicator that inform UEs that they need to decode the information of the PCH channel.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/20/overview-of-umts-physical-channels/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

