<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://lteuniversity.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Chris</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/default.aspx</link><description /><dc:language>en-US</dc:language><generator>6.x Production</generator><item><title>Clearwire and LTE-Advanced</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/08/04/clearwire-and-lte-advanced.aspx</link><pubDate>Thu, 04 Aug 2011 21:19:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:11444</guid><dc:creator>Chris</dc:creator><slash:comments>4</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/08/04/clearwire-and-lte-advanced.aspx#comments</comments><description>&lt;p&gt;Well it is official. Clearwire announced this week that it
will deploy LTE and maintain the existing WiMAX network. For a good article on
their announcement, see &lt;a href="http://www.fiercewireless.com/story/clearwire-deploy-lte-if-it-can-get-additional-funding/2011-08-03"&gt;http://www.fiercewireless.com/story/clearwire-deploy-lte-if-it-can-get-additional-funding/2011-08-03&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;Not only is Clearwire deploying LTE, they are deploying
LTE-Advanced. LTE-Advanced, or just LTE-A, is the next iteration of LTE that
has been defined in Release 10 of the 3GPP specifications. There are a number
of advancements that they have incorporated into LTE-A. One of the most
interesting, in my opinion, is Carrier Aggregation. It is one of the
technologies that Clearwire is intending to use. With Carrier Aggregation, an
LTE-A base station (or eNB) and a mobile device (of UE) can talk to each other
using multiple frequency blocks spread, or as we would say in broadcast radio,
&amp;quot;up and down the dial&amp;quot;. So a single UE could send and receive data on 850 MHz,
1900 MHz, and 2.5 GHz simultaneously. This will allow an operator the ability
to increase data rates by aggregating the different spectrums that they have. &lt;/p&gt;
&lt;p&gt;Another technology that Clearwire is planning on using, as
they did with WiMAX, is a Time Division Duplex, or TDD, version of LTE. This
will allow them to have a single frequency (or set of frequencies in the case
of carrier aggregation) for both the uplink and downlink. The other type of LTE
is Frequency Division Duplex or FDD. FDD requires dedicated uplink frequencies
and dedicated downlink frequencies. What we have seen so far has been our
traditional cellular operators that have gone to LTE, Verizon Wireless and
AT&amp;amp;T, will use FDD because the spectrum they have is specifically designed
for FDD. Clearwire, on the other hand, will use a single band and TDD. &lt;/p&gt;
&lt;p&gt;If you are interested in more information on LTE-A, a
colleague of mine, Dr. Nishith Tripathi, has written an overview of LTE-A. For
more information, see his blog at &lt;a href="http://lteuniversity.com/expert_opinion1/b/nishithtripathi/archive/2010/05/04/lte-advanced-in-5-minutes.aspx"&gt;http://lteuniversity.com/expert_opinion1/b/nishithtripathi/archive/2010/05/04/lte-advanced-in-5-minutes.aspx&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;I wish the best to Clearwire, as well as the other LTE
operators, and I look forward to seeing the types of data rates, devices, and
services that they have to offer. &lt;/p&gt;
&lt;p&gt;What is your opinion? I would love to hear from you and your
thoughts on LTE-A or anything on LTE in general. &lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;
Chris
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=11444&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Clearwire/default.aspx">Clearwire</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte_2D00_advanced/default.aspx">lte-advanced</category></item><item><title>Spectrum and LTE</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/07/22/spectrum-and-lte.aspx</link><pubDate>Fri, 22 Jul 2011 22:41:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:11407</guid><dc:creator>Chris</dc:creator><slash:comments>1</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/07/22/spectrum-and-lte.aspx#comments</comments><description>&lt;p&gt;I was reading my telecom news blogs this week and stumbled
across an article about LightSquared and the spectrum they are planning on
using for LTE (&lt;a href="http://www.fiercewireless.com/story/lightsquared-ceo-ahuja-confident-fcc-will-approve-network-plan/2011-07-19?utm_medium=rss&amp;amp;utm_source=rss"&gt;http://www.fiercewireless.com/story/lightsquared-ceo-ahuja-confident-fcc-will-approve-network-plan/2011-07-19?utm_medium=rss&amp;amp;utm_source=rss&lt;/a&gt;).
LightSquared&amp;#39;s spectrum is part of the L-band satellite spectrum. What dawned
me while reading the article was that I didn&amp;#39;t really have a good feel for the
spectrum breakdown in the U.S. &amp;nbsp;I know
about the standard cellular frequencies, i.e. 800 MHz, 1900 MHz, AWS, and 700
MHz, but not some of the others parts of the spectrum. I did a bit of poking
around and found this radio spectrum map: &lt;a href="http://www.ntia.doc.gov/osmhome/allochrt.pdf"&gt;www.ntia.doc.gov/osmhome/allochrt.pdf&lt;/a&gt;.
It was produced by the U.S. Department of Commerce, and shows how we are using
the spectrum here in the U.S. It is amazing how many things we have allocated.
LightSquared wants to use a satellite band for terrestrial LTE, which is on the
lower portion of the map. &lt;/p&gt;
&lt;p&gt;Another thing that this map helped me see is how much space
is &amp;quot;wasted&amp;quot; by broadcast television. This is the reason for the big push over
the last few years to move to a digital television standard in order to free up
space for other things. That is what happened a few years ago when some
television frequencies were taken back and then sold as the 700 MHz spectrum. &lt;/p&gt;
&lt;p&gt;Spectrum will always be an issue in cellular
telecommunications. I can see from this map how full things are now. There&amp;#39;s no
doubt in my mind that in the future we will be playing the same game as now:
optimizing some service (like TV) and then reusing that for something else
(like cellular data). This map also helps to show why there is so much interest
in technologies like Multiple Input Multiple Output (MIMO) and Smart Antennas.
It&amp;#39;s not just about increasing the data rate; it&amp;#39;s about increasing the
spectral efficiency (more bits/second/Hz) so that we can continue to increase
the data available for subscribers, even if the spectrum itself cannot grow.&lt;/p&gt;
&lt;p&gt;I look forward to hearing your thoughts.&lt;/p&gt;
&lt;p&gt;Chris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=11407&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lightsquared/default.aspx">lightsquared</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Opinion/default.aspx">Opinion</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/spectrum/default.aspx">spectrum</category></item><item><title>So how many LTE Operators are there?</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/05/13/so-how-many-lte-operators-are-there.aspx</link><pubDate>Fri, 13 May 2011 20:22:08 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:11170</guid><dc:creator>Chris</dc:creator><slash:comments>1</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/05/13/so-how-many-lte-operators-are-there.aspx#comments</comments><description>&lt;p&gt;Living here in the United States, I don&amp;#39;t think about the
rest of the world as often as I would like. So when I think about there being a
lot of LTE operators, I focus on the fact that three operators in the US have
either launched or are going to launch soon (i.e. Verizon Wireless, MetroPCS,
and AT&amp;amp;T). But there was a new report from the GSA (the GSM mobile
Suppliers Association) that shows all the operators in the world that have
either deployed LTE or are committed in some way to LTE. It is a very interesting
report that gives an operator by operator break-down of where they are in the
process, i.e. deployed, in trial, starting to work on it, etc. The most
interesting statistic is that there are 208 operators that are interested in
LTE in 80 countries. Of those interested, 154 have firm commitments and plans.
Those 154 are in 60 different countries. Those are pretty big numbers.&lt;/p&gt;
&lt;p&gt;The report is a very interesting read and it is great to see
that the LTE momentum continuing to pick-up. For more information please see
the report at &lt;a href="http://www.gsacom.com/news/gsa_329.php4"&gt;http://www.gsacom.com/news/gsa_329.php4&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;What are your thoughts about LTE deployment? I would love to
hear your thoughts. Also if you live outside the US, I would love to hear from
you about the buzz on LTE. Is it being deployed? What is being discussed? I would
love to hear from you.&lt;/p&gt;
&lt;p&gt;
Chris
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=11170&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/LTE+Operators/default.aspx">LTE Operators</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Opinion/default.aspx">Opinion</category></item><item><title>Who is 4G?</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/05/04/who-is-4g.aspx</link><pubDate>Wed, 04 May 2011 14:23:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:11151</guid><dc:creator>Chris</dc:creator><slash:comments>1</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/05/04/who-is-4g.aspx#comments</comments><description>&lt;p&gt;I am sure you have seen the commercials. T-Mobile says they
have the largest 4G network. Verizon says they are 4G and they have the fastest
4G network. AT&amp;amp;T also claims 4G. But, they don&amp;#39;t all use the same
technology. So that begs the question, who is 4G? &lt;/p&gt;
&lt;p&gt;Before we discuss that, let&amp;#39;s take a look at who makes the
rules as to who is 4G. They are the International Telecommunication Union or
the ITU. They were the group back in the 90&amp;#39;s that set the requirements for who
could call themselves 3G and they are setting the requirements for 4G.
Interestingly, last year they stated that 4G was reserved for technology like
LTE-Advanced or WirelessMAN-Advanced. Technology that provided a significant
increase in data rates over 3G. But, late last year they changed that. Now they
say anything can be called 4G if it is a &amp;quot;forerunner of these technologies&amp;quot;
(like LTE and WiMAX) or &amp;quot;evolved 3G technologies providing a substantial level
of improvement in performance and capabilities with respect to the initial
third generation systems now deployed&amp;quot; (read HSPA+). So based on this statement
you can call yourself 4G if you are LTE, WiMAX, or HSPA+. &lt;/p&gt;
&lt;p&gt;T-Mobile, AT&amp;amp;T, Verizon, MetroPCS, and Clear all meet
these requirements and are free to call themselves 4G. I hope that helps clear
up any confusion on who is 4G. I know it did for me when I did some research on
this recently. &lt;/p&gt;
&lt;p&gt;What do you think? &lt;/p&gt;
&lt;p&gt;For more information on the ITU and 4G, check out &lt;a href="http://www.intomobile.com/2010/12/18/itu-reverses-its-decision-lte-wimax-and-hspa-are-now-4g/"&gt;http://www.intomobile.com/2010/12/18/itu-reverses-its-decision-lte-wimax-and-hspa-are-now-4g/&lt;/a&gt;
and &lt;a href="http://www.itu.int/net/pressoffice/press_releases/2010/48.aspx"&gt;http://www.itu.int/net/pressoffice/press_releases/2010/48.aspx&lt;/a&gt;.
&amp;nbsp;&lt;/p&gt;
&lt;p&gt;
I look forward to your thoughts.
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=11151&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/4G/default.aspx">4G</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/AT_2600_amp_3B00_T/default.aspx">AT&amp;amp;T</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Clear/default.aspx">Clear</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/HSPA_2B00_/default.aspx">HSPA+</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/metropcs/default.aspx">metropcs</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Opinion/default.aspx">Opinion</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/t_2D00_mobile/default.aspx">t-mobile</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Verizon+Wireless/default.aspx">Verizon Wireless</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/WiMAX/default.aspx">WiMAX</category></item><item><title>The Thunderbolt – A Game Changer?</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/04/15/the-thunderbolt-a-game-changer.aspx</link><pubDate>Fri, 15 Apr 2011 22:13:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:11122</guid><dc:creator>Chris</dc:creator><slash:comments>1</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2011/04/15/the-thunderbolt-a-game-changer.aspx#comments</comments><description>&lt;p&gt;Over the past month Verizon Wireless has released the HTC
Thunderbolt. Normally we do not talk about mobile devices here on LTE
University, but this one is quite interesting. It has a couple of claims to
fame. The first is that it is a LTE smartphone. It is Android 2.2 based device
and it also supports both LTE and 1xEV-DO for data. Being the first Verizon LTE
smartphone is a pretty good claim to fame, but there is more. It is also the
first smartphone on Verizon&amp;#39;s network that is capable of supporting both voice
and data. That is something that the iPhone is not capable of on Verizon&amp;#39;s
network. This allows a subscriber to talk on the phone while simultaneously
surfing the web or using apps that interact with the Internet.&lt;/p&gt;
&lt;p&gt;The question is &amp;quot;is this really a game changer&amp;quot;? For me
personally I would have to say yes. You see, there is really only one big stick
that AT&amp;amp;T has over Verizon and that is the fact that they can do
simultaneous voice and data, but Verizon cannot. It is one of the technological
issues that come from the technology choices of over 10 years ago. But now the
game has changed. Now Verizon is capable of a similar feature. Is this the
beginning of more of these types of devices? I hope so.&lt;/p&gt;
&lt;p&gt;What do you think?&lt;/p&gt;
&lt;p&gt;For more information on the HTC Thunderbolt, check out:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.gottabemobile.com/2011/03/14/htc-thunderbolt-first-verizon-phone-to-feature-simultaneous-voice-data/"&gt;http://www.gottabemobile.com/2011/03/14/htc-thunderbolt-first-verizon-phone-to-feature-simultaneous-voice-data/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I look forward to your thoughts.
&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=11122&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/HTC/default.aspx">HTC</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Opinion/default.aspx">Opinion</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/smartphone/default.aspx">smartphone</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/thunderbolt/default.aspx">thunderbolt</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Verizon+Wireless/default.aspx">Verizon Wireless</category></item><item><title>SIP vs. GTP/MIP</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/06/18/sip-vs-gtp-mip.aspx</link><pubDate>Fri, 18 Jun 2010 21:34:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10151</guid><dc:creator>Chris</dc:creator><slash:comments>3</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/06/18/sip-vs-gtp-mip.aspx#comments</comments><description>&lt;p&gt;Hello All,&lt;/p&gt;
&lt;p&gt;I had a question recently about different types of mobility that I thought might be of interest. The question was about using SIP mobility instead of GTP or MIP in LTE. This is a good question. On the surface both are solving mobility issues so why have different solutions. The problem is that SIP mobility and MIP/GTP are really trying to solve different problems. MIP (or Mobile IP) and GTP (or GPRS Tunneling Protocol) are trying to solve geographical mobility. 
&lt;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&gt;
&lt;meta content="Word.Document" /&gt;
&lt;meta content="Microsoft Word 12" /&gt;
&lt;meta content="Microsoft Word 12" /&gt;



&lt;!--[if gte mso 9]&gt;
 
  Normal
  0
  
  
  
  
  false
  false
  false
  
  EN-US
  X-NONE
  X-NONE
  
   
   
   
   
   
   
   
   
   
   
   
  
  
  
   
   
   
   
   
   
   
   
   
   
   
  
&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;
 
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 
&lt;![endif]--&gt;

&lt;!--[if gte mso 10]&gt;
&lt;![endif]--&gt;
&lt;!--[endif]--&gt; As a mobile moves through the network, we need to direct the packets
to its current S-GW and eNodeB. MIP is an option for sending packets from the
P-GW to the current S-GW of the mobile. I don&amp;#39;t see many people using MIP. Most
are looking at using the GTP. SIP Mobility is used
to map the current IP address of the UE to a logical name. Since we can use dynamic IP
addresses in LTE, we need a way to map the current IP address assigned by the
P-GW to the UE to a logical name that is static (i.e. Chris@LTEISCOOL.com). So they are just
trying to solve different problems.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I found this an interesting question and I hope you find this helpful.&lt;/p&gt;
&lt;p&gt;Take care,&lt;/p&gt;
&lt;p&gt;Chris&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10151&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/GTP/default.aspx">GTP</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/MIP/default.aspx">MIP</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Mobility/default.aspx">Mobility</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/SIP/default.aspx">SIP</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Supporting+Technologies/default.aspx">Supporting Technologies</category></item><item><title>Compare and contrast of UMTS and LTE Mobility</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/05/17/compare-and-contrast-of-umts-and-lte-mobility.aspx</link><pubDate>Mon, 17 May 2010 14:15:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10123</guid><dc:creator>Chris</dc:creator><slash:comments>0</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/05/17/compare-and-contrast-of-umts-and-lte-mobility.aspx#comments</comments><description>&lt;p&gt;As I think about mobility in LTE, I always go back to making
comparisons with UMTS. I thought t might be good to do a comparison 
chart of
the two. Below is a list of the key mobility terms/concepts and their 
equivalent
terms in UMTS and LTE. Let me know what you think of this and if you 
have any
questions/comments.
&lt;/p&gt;
&lt;div&gt;Thanks,&lt;/div&gt;
&lt;div&gt;Chris&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;table class="MsoTableGrid" style="border-collapse:collapse;border:medium none;" border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Mobility Concept&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;UMTS Concept&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;LTE Concept&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Paging Zone&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Location Area, Routing Area, UTRAN Registration Area&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Tracking Area&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Types of Handover&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Soft, Softer, and Hard&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Hard Only&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Basic dBm measurement&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Received Signal Code Power (RSCP)&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Reference Signal Received Power (RSRP)&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Basic dB measurement&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Energy per Chip over Noise (Ec/No)&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Reference Signal Received Quality (RSRQ)&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Measurement Configuration sent to UE&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;In multiple Measurement Control Messages. One message is needed
 per
  event configuration.&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Included in RRC Connection Reconfiguration. One message can 
include
  multiple measurement configurations.&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Intra-Frequency Measurement events&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e1 event types&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;A event types&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Inter-Frequency Measurement events&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e2 event types&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;A event types&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:159.6pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Inter-RAT Measurement events&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e3 event types&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;B event types&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10123&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/comparison/default.aspx">comparison</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte_2D00_advanced/default.aspx">lte-advanced</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Mobility/default.aspx">Mobility</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/UMTS/default.aspx">UMTS</category></item><item><title>Measurement Event Comparison</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/05/12/measurement-event-comparison.aspx</link><pubDate>Wed, 12 May 2010 22:43:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10120</guid><dc:creator>Chris</dc:creator><slash:comments>1</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/05/12/measurement-event-comparison.aspx#comments</comments><description>&lt;div&gt;While sitting in a colleague&amp;rsquo;s class this week we 
were
discussing the UMTS measurement event types.&lt;span&gt;&amp;nbsp;
&lt;/span&gt;I thought it might be good to do a comparison of UMTS&amp;rsquo;s 
measurement
events with the measurement events in LTE. There are a couple of key
differences between the two. The first is that UMTS supports a soft 
handover
and LTE does not. That is important in looking at this comparison as 
there is
no active set in LTE. The second difference is that LTE does not 
highlight the
differences between intra-frequency measurements and inter-frequency
measurements as strongly as UMTS does. The following table gives a 
comparison
and comments on how the LTE measurements compare with UMTS. 
&lt;/div&gt;
&lt;div&gt;I hope it is helpful.&lt;/div&gt;
&lt;div&gt;Thanks,&lt;/div&gt;
&lt;div&gt;Chris&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;table class="MsoTableGrid" style="width:638px;border-collapse:collapse;border:medium none;" border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;LTE Measurement Events and Description&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;UMTS Measurement Events and Description&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Comments&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event A1 - Serving becomes better than threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e2f &lt;span&gt;&amp;nbsp;&lt;/span&gt;- The estimated quality of
  the currently used frequency is above a certain threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;In LTE this may be used to stop looking for a cell on a different
  frequency or technology, as e2f is used in UMTS.&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event A2 - Serving becomes worse than threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e2d &lt;span&gt;&amp;nbsp;&lt;/span&gt;- The estimated quality of
  the currently used frequency is below a certain threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;In LTE this may be used to start looking for a cell on a different
  frequency or technology, as e2d is used in UMTS. &lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event A3 - Neighbor becomes offset better than serving&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e1a - A Primary CPICH enters the reporting range&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;This comparison is a bit of a stretch. The reason I have equated them
  is because in both cases a neighbor should be considered for a handover,
  either soft or hard depending on the technology. &lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event A4 - Neighbor becomes better than threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e1e - A Primary CPICH becomes better than an absolute threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;&amp;nbsp;&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event A5 - Serving becomes worse than threshold1 and neighbor becomes
  better than threshold2&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e2b - The estimated quality of the currently used frequency is below
  a certain threshold and &lt;/div&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;the estimated quality of a non-used frequency is above a certain
  threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;This comparison is good for saying that the current cell is below an
  absolute threshold and the new cell is above a threshold. This would mean
  that the current cell is not good enough and the new one is good, which is a
  good reason to do a hard handover (in either technology).&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event B1 - Inter RAT neighbor becomes better than threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e3c - The estimated quality of other system is above a certain
  threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;&amp;nbsp;&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="width:144.9pt;border-right:1pt solid black;padding:0in 5.4pt;" valign="top" width="193"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;Event B2 - Serving becomes worse than threshold1 and inter RAT
  neighbor becomes better than threshold2&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:174.3pt;padding:0in 5.4pt;" valign="top" width="232"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;e3a - The estimated quality of the currently used UTRAN frequency is
  below a certain &lt;/div&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;threshold and the estimated quality of the other system is above a
  certain threshold&lt;/div&gt;
&lt;/td&gt;
&lt;td style="width:159.6pt;padding:0in 5.4pt;" valign="top" width="213"&gt;
&lt;div style="margin-bottom:0.0001pt;line-height:normal;"&gt;This comparison is good for saying that the current cell is below an
  absolute threshold and the new cell on a different technology is above a
  threshold. This would mean that the current cell is not good enough and the
  new one is good, which is a good reason to do a hard handover to the new
  technology.&lt;/div&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10120&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/comparison/default.aspx">comparison</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Measurements/default.aspx">Measurements</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Mobility/default.aspx">Mobility</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/UMTS/default.aspx">UMTS</category></item><item><title>A Mobility Question</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/03/22/a-mobility-question.aspx</link><pubDate>Mon, 22 Mar 2010 16:39:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10028</guid><dc:creator>Chris</dc:creator><slash:comments>3</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2010/03/22/a-mobility-question.aspx#comments</comments><description>&lt;p&gt;Hello All,&lt;/p&gt;
&lt;p&gt;Sorry for my lack of blogging lately. Projects can 
be tough.
With the apologies out of the way, I had a colleague ask a couple of 
questions
recently and I thought it would be good to share the answers with LTE-U.
 &lt;/p&gt;
&lt;p&gt;His main question was about mobility. Mobility in 
LTE can be
quite tricky. The main point of his question was about the frequency 
band size.
In LTE there is a scalable OFDM channel. The bandwidth can vary from 1.4
 MHz to
20 MHz. There are also a number of frequency bands that are going to be 
used
for LTE (the new 700 MHz as well as the old PCS and Cellular bands). &lt;/p&gt;
&lt;p&gt;The question basically was can a mobile move 
between
frequency bands and the answer is absolutely yes. The second part of the
 question
regarded movement between different sizes of bands. The best way to 
approach
this question is to define two terms. The two terms are intra-frequency 
and
inter-frequency mobility. We are use to these terms in other 
technologies (i.e.
GSM and UMTS), but LTE puts a new spin on things. Intra-frequency 
mobility is
when a mobile moves between two cells and both cells have the same 
frequencies (I
know, not the most profound statement).&amp;nbsp; If there is&amp;nbsp;&lt;span style="text-decoration:line-through;"&gt;&lt;/span&gt;a change in the center 
frequency this is now called 
inter-frequency mobility. In
LTE both intra-frequency and inter-frequency mobility are supported. (5/4/10 Note - I has come to my attention that if the bandwidth changes, but the center frequency does not change it is still a intra-frequency handover.)&lt;/p&gt;
&lt;p&gt;For example, let&amp;#39;s say that an operator has in one 
city a 10
MHz block in the 850 MHz band that they are using for LTE. In a city 
that is
only a few miles away this same operator has only 5 MHz available in the
 850
MHz band. When a subscriber drives from city A to city B the size of the
frequency band is changing (as will probably the DC carrier) and the 
mobile
will have to do inter-frequency mobility measurements to provide 
information on
the new cells signal strength. &lt;/p&gt;
&lt;p&gt;The reason this is an important discussion is that 
when the
mobile does intra-frequency measurements the network does not need to 
allow any
time to do the measurements. The mobile can just do them whenever they 
want to.
For inter-frequency measurements the mobile must be given time to stop 
listening
to its current cell and listen to a new cell to take the measurements. 
That increases
the level of complexity and the amount of work the mobile will need to 
do. &lt;/p&gt;
&lt;p&gt;I hope this helps give some insight into mobility. 
Please
feel free to send questions if you have any.&lt;/p&gt;
&lt;p&gt;Take care,&lt;/p&gt;
&lt;p&gt;Chris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10028&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/intra_2D00_frequency/default.aspx">intra-frequency</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Measurements/default.aspx">Measurements</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Mobility/default.aspx">Mobility</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/OFDM/default.aspx">OFDM</category></item><item><title>The Magic 86</title><link>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2009/08/04/the-magic-86.aspx</link><pubDate>Tue, 04 Aug 2009 13:45:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:7076</guid><dc:creator>Chris</dc:creator><slash:comments>0</slash:comments><comments>http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/2009/08/04/the-magic-86.aspx#comments</comments><description>&lt;p&gt;I had a student in one of my classes ask me about the &amp;quot;Magic
86&amp;quot; number (as much as I would love to insert a Harry Potter reference, I will
restrain myself). After a little discussion, it became clear that she was
talking about the raw physical bandwidth of LTE and how it was 86 Mbps. She was
interested in understanding how this &amp;quot;magic&amp;quot; number was calculated. I thought
it would be beneficial to go through the steps in calculating the uplink and
downlink maximum theoretical data rates. &lt;/p&gt;
&lt;p&gt;Before we start, it is important to note that these data
rates are not practical data rates. Typically when I say that &amp;quot;maximum
theoretical&amp;quot; it essentially means, in the words of my Granddaddy (we called him
&amp;quot;Pa&amp;quot;), &amp;quot;You ain&amp;#39;t gonna see that.&amp;quot; (It&amp;#39;s a southern Oklahoma thing.) In this
context I mean a bit more. The standard does not allow for a mobile to reach
the magic number, as I&amp;#39;m about to illustrate. Practical maximums will be
discussed in a later post, so keep in mind that the numbers presented here are achievable
data rates for LTE. &lt;/p&gt;
&lt;p&gt;Now, with all of our introductions and caveats covered,
let&amp;#39;s look at the &amp;quot;Magic 86&amp;quot; number. There are two instances in which this
value comes into play. The first is the uplink rate and the second is the
downlink with only a single transmit antenna. &lt;/p&gt;
&lt;p&gt;Let&amp;#39;s look at the uplink first. In the uplink there are two
key assumptions: first, that we are using a 20 Mhz spectrum and, second, that
we are always able to support 64 QAM. Since we are assuming a 20 MHz spectrum,
we have 100 Resource Blocks (RB) per slot (.5 ms). A RB has 84 Resource
Elements (RE). In every RB there are 12 REs that are lost due to overhead
(specifically the Uplink Reference Signal). That leaves us with 72 REs per RB.
Since resources are assigned per ms, a UE will be assigned a minimum of two RBs
(one in the first .5 ms and one in the second .5 ms). For simplicity&amp;#39;s sake, I
am calling this a Resource Block pair. This will give us a total of 144 REs per
Resource Block pair. If all of the bandwidth is given to just one UE, then that
UE will received a total of 14400 REs (144 REs per RB and 100 RBs).&amp;nbsp; With the maximum modulation scheme of 64QAM,
we are able to transmit 6 bits per RE. That gives us 86400 bits per subframe or
86.4 Mbps.&amp;nbsp; The following table provides
a summary of these calculations. &lt;/p&gt;
&lt;table style="width:661px;" border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Uplink&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total Bandwidth (MHz)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;20&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total Resource Blocks&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;100&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Elements per Resource Block&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;84&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Element Overhead&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;12&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;
&lt;p&gt;Uplink Reference Signals&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Available Resource Elements per Resource Block (after overhead)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;72&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Elements per Resource Block pair (in one ms)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;144&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total Resource Elements available per subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;14400&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Bits per Resource Element&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;6&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;
&lt;p&gt;64 QAM&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total bits per subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;86400&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Raw Channel Bandwidth (Mbps)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;86.4&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="187" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s take a look at the downlink maximum theoretical data
rates. We are going to examine this in two stages. The first is when we are
using a single transmit antenna (also referred to as Single Input Single Output
or SISO) or when we are using a 2x2 MIMO or Multiple Input Multiple Output. The
second case is when we are using 4x4 MIMO. The difference is that there is more
overhead for 4x4 MIMO. &lt;/p&gt;
&lt;p&gt;In the first case we will look at the SISO or 2x2 MIMO
maximum theoretical data rates. The calculations start the same as they did for
the uplink case. We assume a 20 MHz spectrum and a 64 QAM modulation scheme.
For every Resource Block pair we will lose 24 REs for overhead, 12 for the
Physical Downlink Control Channel and 12 for Downlink Reference Signals. This
gives us a total of 144 REs per RB after the overhead is removed. If all of the
bandwidth is given to just one UE, then that UE will receive a total of 14400
REs (144 REs per RB and 100 RBs).&amp;nbsp; With
the maximum modulation scheme of 64QAM, we are able to transmit 6 bits per RE.
That gives us 86400 bits per subframe or 86.4 Mbps.&amp;nbsp; So for SISO in the DL and the UL, they both
support the same maximum. All we need to do is double this number for a 2x2
MIMO case. That gives us a maximum of 172.8 Mbps. The following table provides
a summary of these calculations.&lt;/p&gt;
&lt;table style="width:674px;" border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Downlink SISO or 2x2 MIMO&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Total MHz&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;20&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Total Resource Blocks&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;100&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Resource Elements per Resource Block&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;84&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Resource Elements per RB pair&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;168&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Resource Element Overhead - PDCCH&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;12&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;
&lt;p&gt;Assuming only one OFDM symbol for PDCCH&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Resource Element Overhead - Reference Signals&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;12&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Available Resource Elements per Resource Block (after overhead)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;144&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Total Resource Elements available per subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;14400&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Bits per Resource Element&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;6&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;
&lt;p&gt;64 QAM&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Total bits per subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;86400&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Raw Channel Bandwidth (Mbps) for SISO&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;86.4&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="415" nowrap="nowrap"&gt;
&lt;p&gt;Raw Channel Bandwidth (Mbps) for 2x2 MIMO&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="54" nowrap="nowrap"&gt;
&lt;p align="right"&gt;172.8&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="204" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the last case we will examine the maximum bandwidth for
4x4 MIMO. The calculations are the same as the other DL case with just one
change. There are more Reference Signals that are lost due to overhead. When
this new overhead number is used, the per antenna data rate drops from 86.4 to
81.6 Mbps. We take this number and multiply it by 4 and we have the maximum of
326.4 Mbps. Se the following table for more details. &lt;/p&gt;
&lt;table style="width:673px;" border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Downlink 4x4 MIMO&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total MHz&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;20&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total Resource Blocks&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;100&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Elements per Resource Block&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;84&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Elements per RB pair&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;168&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Element Overhead - PDCCH&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;12&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;
&lt;p&gt;Assuming only one OFDM symbol for PDCCH&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Resource Element Overhead - Reference Signals&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;20&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Available Resource Elements per Resource Block (after overhead)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;136&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total Resource Elements available per subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;13600&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Bits per Resource Element&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;6&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;
&lt;p&gt;64 QAM&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Total bits per subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;81600&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Raw Channel Bandwidth (Mbps)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;81.6&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;
&lt;p&gt;per antenna&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td valign="top" width="423" nowrap="nowrap"&gt;
&lt;p&gt;Raw Channel Bandwidth (Mbps)&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="52" nowrap="nowrap"&gt;
&lt;p align="right"&gt;326.4&lt;/p&gt;
&lt;/td&gt;
&lt;td valign="top" width="199" nowrap="nowrap"&gt;
&lt;p&gt;4x4 MIMO&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So there you have it. This is where the &amp;quot;magic&amp;quot; numbers come
from. I hope that I have not taken too much of the mystique behind LTE away from
you. In all seriousness, I hope this helps to provide some understanding of
where these capacity numbers come from. If you have any questions, please let
me know.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=7076&amp;AppID=54&amp;AppType=1&amp;ContentType=0" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Air+Interface/default.aspx">Air Interface</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Data+Rate/default.aspx">Data Rate</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/E_2D00_UTRAN/default.aspx">E-UTRAN</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/magic+86/default.aspx">magic 86</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Reference+Signals/default.aspx">Reference Signals</category><category domain="http://lteuniversity.com/get_trained/expert_opinion1/b/chrisreece/archive/tags/Resource+Blocks/default.aspx">Resource Blocks</category></item></channel></rss>