<?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; mac</title>
	<atom:link href="http://wireless.pyncus.com/tag/mac/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>How many instances of MAC for UE and Network?</title>
		<link>http://wireless.pyncus.com/2009/10/31/how-many-instances-of-mac-for-ue-and-network/</link>
		<comments>http://wireless.pyncus.com/2009/10/31/how-many-instances-of-mac-for-ue-and-network/#comments</comments>
		<pubDate>Sat, 31 Oct 2009 06:34:08 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[CRNC]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[srnc]]></category>

		<guid isPermaLink="false">http://wireless.pyncus.com/?p=695</guid>
		<description><![CDATA[There is a single MAC instance within the UE.
In the network, usually a single MAC instance for each UE exists.
However, multiple MAC instances for a single UE may happen (e.g., one in a CRNC and one in an SRNC)
]]></description>
			<content:encoded><![CDATA[<p>There is a single MAC instance within the UE.</p>
<p>In the network, usually a single MAC instance for each UE exists.<br />
However, multiple MAC instances for a single UE may happen (e.g., one in a CRNC and one in an SRNC)</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/10/31/how-many-instances-of-mac-for-ue-and-network/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Layer 2 protocols</title>
		<link>http://wireless.pyncus.com/2009/10/31/layer-2-protocols/</link>
		<comments>http://wireless.pyncus.com/2009/10/31/layer-2-protocols/#comments</comments>
		<pubDate>Sat, 31 Oct 2009 06:28:01 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[bmc]]></category>
		<category><![CDATA[layer 2]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[pdcp]]></category>
		<category><![CDATA[rlc]]></category>

		<guid isPermaLink="false">http://wireless.pyncus.com/?p=693</guid>
		<description><![CDATA[Layer 2 protocols consists fo 4 protocol entities:
1. MAC (Medium access control)
2. RLC (Radio link control)
3. PDCP (Packet data convergence protocol)
4. BMC (Broadcast and multicast control)
]]></description>
			<content:encoded><![CDATA[<p>Layer 2 protocols consists fo 4 protocol entities:</p>
<p>1. MAC (Medium access control)<br />
2. RLC (Radio link control)<br />
3. PDCP (Packet data convergence protocol)<br />
4. BMC (Broadcast and multicast control)</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/10/31/layer-2-protocols/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What does MAC protocol do?</title>
		<link>http://wireless.pyncus.com/2009/07/26/what-does-mac-protocol-do/</link>
		<comments>http://wireless.pyncus.com/2009/07/26/what-does-mac-protocol-do/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 13:31:21 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[wcdma]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=339</guid>
		<description><![CDATA[The MAC is responsible for dynamic resource allocation under the control of RRC layer.
Using relative priorities betweeservices, MAC does
1. mapping between logical and the transport channels
2. transport format selection
3. priority handling of data flow
4. UE identification management to facilitate transactions such as random access and the use of downlink common channels
5. data ciphering when RLC [...]]]></description>
			<content:encoded><![CDATA[<p>The MAC is responsible for dynamic resource allocation under the control of RRC layer.</p>
<p>Using relative priorities betweeservices, MAC does</p>
<p>1. mapping between logical and the transport channels</p>
<p>2. transport format selection</p>
<p>3. priority handling of data flow</p>
<p>4. UE identification management to facilitate transactions such as random access and the use of downlink common channels</p>
<p>5. data ciphering when RLC is operating in transparent mode</p>
<p>6. traffic volume measurement (monitor the buffer levels for the different RLC instances)</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/07/26/what-does-mac-protocol-do/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Layer 2 consists of what protocol entities?</title>
		<link>http://wireless.pyncus.com/2009/07/26/layer-2-consists-of-what-protocol-entities/</link>
		<comments>http://wireless.pyncus.com/2009/07/26/layer-2-consists-of-what-protocol-entities/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 13:22:39 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[bmc]]></category>
		<category><![CDATA[layer 2]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[pdcp]]></category>
		<category><![CDATA[rlc]]></category>
		<category><![CDATA[wcdma]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=336</guid>
		<description><![CDATA[Layer 2 comprises of 4 protocol entities.
1. MAC protocol
2. RLC protocol
3. PDCP (packet data convergence protocol)
4. BMC (broadcast and multicast control) protocol
]]></description>
			<content:encoded><![CDATA[<p>Layer 2 comprises of 4 protocol entities.</p>
<p>1. MAC protocol</p>
<p>2. RLC protocol</p>
<p>3. PDCP (packet data convergence protocol)</p>
<p>4. BMC (broadcast and multicast control) protocol</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/07/26/layer-2-consists-of-what-protocol-entities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Does MAC protocol segment MAC SDUs?</title>
		<link>http://wireless.pyncus.com/2009/06/24/does-mac-protocol-segment-mac-sdus/</link>
		<comments>http://wireless.pyncus.com/2009/06/24/does-mac-protocol-segment-mac-sdus/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 14:01:47 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[segment]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=298</guid>
		<description><![CDATA[No.
]]></description>
			<content:encoded><![CDATA[<p>No.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/24/does-mac-protocol-segment-mac-sdus/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is MAC layer delivery service guaranteed?</title>
		<link>http://wireless.pyncus.com/2009/06/24/is-mac-layer-delivery-service-guaranteed/</link>
		<comments>http://wireless.pyncus.com/2009/06/24/is-mac-layer-delivery-service-guaranteed/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 13:59:58 +0000</pubDate>
		<dc:creator>wirelessoom</dc:creator>
				<category><![CDATA[umts]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[rlc]]></category>

		<guid isPermaLink="false">http://wirelessoom.wordpress.com/?p=296</guid>
		<description><![CDATA[No!
MAC layer transfer service is done in unacknowledged mode. That is, no guaranteed delivery service.
RLC layer has mechanisms to detect errors and retransmit.
]]></description>
			<content:encoded><![CDATA[<p>No!</p>
<p>MAC layer transfer service is done in unacknowledged mode. That is, no guaranteed delivery service.</p>
<p>RLC layer has mechanisms to detect errors and retransmit.</p>
]]></content:encoded>
			<wfw:commentRss>http://wireless.pyncus.com/2009/06/24/is-mac-layer-delivery-service-guaranteed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>
	</channel>
</rss>

