<?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; umts</title>
	<atom:link href="http://wireless.pyncus.com/tag/umts/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireless.pyncus.com</link>
	<description>Build and Share Wireless Network Technology</description>
	<lastBuildDate>Sat, 29 May 2010 14:32:27 +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>Radio interface protocol structure</title>
		<link>http://wireless.pyncus.com/2009/06/19/radio-interface-protocol-structure/</link>
		<comments>http://wireless.pyncus.com/2009/06/19/radio-interface-protocol-structure/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 04:09:55 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[layer 1]]></category>
		<category><![CDATA[layer 2]]></category>
		<category><![CDATA[layer 3]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[rb]]></category>
		<category><![CDATA[rlc]]></category>
		<category><![CDATA[rnc]]></category>
		<category><![CDATA[srb]]></category>
		<category><![CDATA[ue]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=102</guid>
		<description><![CDATA[Radio interface protocol structure:

Note that RB vs. SRB
At the UTRAN side, RLC and above protocols are located at RNC.
MAC protocols: some functionalities are at Node B, others are at RNC.
]]></description>
			<content:encoded><![CDATA[<p>Radio interface protocol structure:</p>
<p><img class="alignnone size-full wp-image-103" title="radiointerfaceprotocol" src="http://wirelessoom.files.wordpress.com/2009/06/radiointerfaceprotocol.png" alt="radiointerfaceprotocol" width="480" height="289" /></p>
<p>Note that <a href="http://wirelessoom.wordpress.com/2009/06/19/rab-vs-rb-vs-srb/">RB vs. SRB</a></p>
<p>At the UTRAN side, RLC and above protocols are located at RNC.</p>
<p>MAC protocols: some functionalities are at Node B, others are at RNC.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/19/radio-interface-protocol-structure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can you give me a simple UMTS protocol overview?</title>
		<link>http://wireless.pyncus.com/2009/06/18/can-you-give-me-a-simple-umts-protocol-overview/</link>
		<comments>http://wireless.pyncus.com/2009/06/18/can-you-give-me-a-simple-umts-protocol-overview/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 18:32:57 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[overview]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=84</guid>
		<description><![CDATA[You want to know UMTS ?
Then, first you need to be familiar with the terminologies in the below picture.

]]></description>
			<content:encoded><![CDATA[<p>You want to know UMTS ?</p>
<p>Then, first you need to be familiar with the terminologies in the below picture.</p>
<p><img class="alignnone size-full wp-image-95" title="umts" src="http://wirelessoom.files.wordpress.com/2009/06/umts1.png" alt="umts" width="480" height="265" /></p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/18/can-you-give-me-a-simple-umts-protocol-overview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is it OK to have different TTI values in multiplexed channel?</title>
		<link>http://wireless.pyncus.com/2009/06/18/is-it-ok-to-have-different-tti-values-in-multiplexed-channel/</link>
		<comments>http://wireless.pyncus.com/2009/06/18/is-it-ok-to-have-different-tti-values-in-multiplexed-channel/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 04:13:19 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[tfc]]></category>
		<category><![CDATA[tti]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=49</guid>
		<description><![CDATA[Yes!
Transport format combination (TFC)  selection frequency is equal to the length of the shortest configured TTI duration.
]]></description>
			<content:encoded><![CDATA[<p>Yes!</p>
<p>Transport format combination (<a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-transport-format-combination-in-umts/">TFC</a>)  selection frequency is equal to the length of the shortest configured TTI duration.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/18/is-it-ok-to-have-different-tti-values-in-multiplexed-channel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How does the receiver know transport format combination?</title>
		<link>http://wireless.pyncus.com/2009/06/18/how-does-the-receiver-know-transport-format-combination/</link>
		<comments>http://wireless.pyncus.com/2009/06/18/how-does-the-receiver-know-transport-format-combination/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 04:09:38 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[tfc]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=47</guid>
		<description><![CDATA[During a given TTI, the selected transport formation combination (TFC) must reamin the same.
It can be changed by the transmitter from one TTI to another.
Such a change involves alterations in physical layer parameters suchas the spreading factor etc.
Thus, the receiver should detect the transport format combination that is being used at a given moment.
This can [...]]]></description>
			<content:encoded><![CDATA[<p>During a given TTI, the selected transport formation combination (TFC) must reamin the same.</p>
<p>It can be changed by the transmitter from one TTI to another.</p>
<p>Such a change involves alterations in physical layer parameters suchas the spreading factor etc.</p>
<p>Thus, the receiver should detect the transport format combination that is being used at a given moment.</p>
<p>This can be done explicitly by means of TFCI (indicator), included in the control physical channels, or by means of blind detection procedures.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/18/how-does-the-receiver-know-transport-format-combination/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is transport format combination set in umts?</title>
		<link>http://wireless.pyncus.com/2009/06/18/what-is-transport-format-combination-set-in-umts/</link>
		<comments>http://wireless.pyncus.com/2009/06/18/what-is-transport-format-combination-set-in-umts/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 03:55:33 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[tfcs]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=43</guid>
		<description><![CDATA[Transport format combination set is the set of all transport format combination.
This is equivalent to transport format set for transport format when several transport channels are multiplexed.
]]></description>
			<content:encoded><![CDATA[<p>Transport format combination set is the set of all <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-transport-format-combination-in-umts/">transport format combination</a>.</p>
<p>This is equivalent to transport format set for transport format when several transport channels are multiplexed.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/18/what-is-transport-format-combination-set-in-umts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is transport format combination in umts?</title>
		<link>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-combination-in-umts/</link>
		<comments>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-combination-in-umts/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 23:29:23 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[tfc]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=39</guid>
		<description><![CDATA[So confusing with transport format, transport format set ?
The fact: Several transport channels can be multiplexed in a single physical channel.
So, transport format combination (TFC) defines the number of transport blocks that are transmitted from each of the multiplexed transport channels in a given TTI.
Example:
DCH1:
{10ms, turbo coding, static rate matching parameter =1}
{40 bits, 40 bits}
DCH2:
{10ms, [...]]]></description>
			<content:encoded><![CDATA[<p>So confusing with <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-transport-format-in-umts/">transport format</a>, <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-transport-format-set-in-umts/">transport format set</a> ?</p>
<p>The fact: Several transport channels can be multiplexed in a single physical channel.</p>
<p>So, transport format combination (TFC) defines the number of transport blocks that are transmitted from each of the multiplexed transport channels in a given <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-tti-in-umts/">TTI</a>.</p>
<p>Example:</p>
<p>DCH1:</p>
<p>{10ms, turbo coding, static rate matching parameter =1}</p>
<p>{40 bits, 40 bits}</p>
<p>DCH2:</p>
<p>{10ms, convolutional coding, static rate matching parameter =3}</p>
<p>{320 bits, 320 bits}</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-combination-in-umts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is transport format set in umts?</title>
		<link>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-set-in-umts/</link>
		<comments>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-set-in-umts/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 23:16:41 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[tf]]></category>
		<category><![CDATA[tfs]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=35</guid>
		<description><![CDATA[Transport format set is
a set of allowed transport formats for a given transport channel.
As a result, it limits the max number of transport blocks that can be transmitted in a TTI, or it limits the max instantaneous bit rate.
Example:
{10ms, turbo coding, static rate matching parameter =1}
{40 bits, 40 bits}; {40 bits, 80 bits}; {40 bits, [...]]]></description>
			<content:encoded><![CDATA[<p>Transport format set is</p>
<p>a set of allowed <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-transport-format-in-umts/">transport formats</a> for a given transport channel.</p>
<p>As a result, it limits the max number of transport blocks that can be transmitted in a TTI, or it limits the max instantaneous bit rate.</p>
<p>Example:</p>
<p>{10ms, turbo coding, static rate matching parameter =1}</p>
<p>{40 bits, 40 bits}; {40 bits, 80 bits}; {40 bits, 120 bits}</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-set-in-umts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is transport format in umts?</title>
		<link>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-in-umts/</link>
		<comments>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-in-umts/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 23:01:02 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[tb]]></category>
		<category><![CDATA[tbs]]></category>
		<category><![CDATA[tf]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=32</guid>
		<description><![CDATA[Transport format defines the data in a transport block set and how it should be handled by the physical layer.
It consists two parts:
1. semistatic
TTI, error protection scheme, size of CRC, static rate matching parameter,
2. dynamic
transport block size, transport block set size
Example:
{10ms, turbo coding, static rate matching parameter =1}
{320 bits, 640 bits}
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;
Interesting point:
The number of transport [...]]]></description>
			<content:encoded><![CDATA[<p>Transport format defines the data in a <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-tti-in-umts/">transport block set </a>and how it should be handled by the physical layer.</p>
<p>It consists two parts:</p>
<p>1. semistatic</p>
<p><a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-tti-in-umts/">TTI</a>, error protection scheme, size of CRC, static rate matching parameter,</p>
<p>2. dynamic</p>
<p>transport block size, transport block set size</p>
<p>Example:</p>
<p>{10ms, turbo coding, static rate matching parameter =1}</p>
<p>{320 bits, 640 bits}</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>Interesting point:</p>
<p>The number of transport block set size defines the the instantaneous bit rate or equivalently the <a href="http://wirelessoom.wordpress.com/2009/06/17/why-smaller-spreading-factor-can-achieve-higher-data-rate/">spreading factor</a> that should be used in the physical layer.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/17/what-is-transport-format-in-umts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Q: What if UE receives data in the middle of TTI?</title>
		<link>http://wireless.pyncus.com/2009/06/17/q-what-if-ue-receives-data-in-the-middle-of-tti/</link>
		<comments>http://wireless.pyncus.com/2009/06/17/q-what-if-ue-receives-data-in-the-middle-of-tti/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 22:51:30 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[question]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=27</guid>
		<description><![CDATA[Does the UE lose the entire TTI data or not ?
If you know the answer, I&#8217;ll appreciate if you let me know.
]]></description>
			<content:encoded><![CDATA[<p>Does the UE lose the entire <a href="http://wirelessoom.wordpress.com/2009/06/17/what-is-tti-in-umts/">TTI</a> data or not ?</p>
<p>If you know the answer, I&#8217;ll appreciate if you let me know.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/17/q-what-if-ue-receives-data-in-the-middle-of-tti/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What is TTI in umts?</title>
		<link>http://wireless.pyncus.com/2009/06/17/what-is-tti-in-umts/</link>
		<comments>http://wireless.pyncus.com/2009/06/17/what-is-tti-in-umts/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 22:46:21 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[Exclusive]]></category>
		<category><![CDATA[umts]]></category>
		<category><![CDATA[transport channel]]></category>
		<category><![CDATA[tti]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=23</guid>
		<description><![CDATA[The MAC layer generates a new transport block every 10-ms (or multiple of blocks.)
A set of simultaneous transport blocks is the transport block set.
The transmission time interval (TTI) is the duration of each transport block set.
This can be 10, 20, 40, 80 ms.
TTI does not tell you data size. It tells you how often the [...]]]></description>
			<content:encoded><![CDATA[<p>The MAC layer generates a new transport block every 10-ms (or multiple of blocks.)</p>
<p>A set of simultaneous transport blocks is the transport block set.</p>
<p>The transmission time interval (TTI) is the duration of each transport block set.</p>
<p>This can be 10, 20, 40, 80 ms.</p>
<p>TTI does not tell you data size. It tells you how often the transport channel data rate can be changed.</p>
<p><img class="alignnone size-full wp-image-25" title="tti" src="http://wirelessoom.files.wordpress.com/2009/06/tti.jpg" alt="tti" width="480" height="250" /></p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/17/what-is-tti-in-umts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
