<?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>Don Hanley </title><link>http://lteuniversity.com/expert_opinion1/b/donhanley/default.aspx</link><description /><dc:language>en</dc:language><generator>Telligent Community (Build: 5.5.133.9594)</generator><item><title>1xEV-DO vs. LTE: Connection Setup</title><link>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2010/07/21/1xev-do-vs-lte-connection-setup.aspx</link><pubDate>Wed, 21 Jul 2010 18:29:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10213</guid><dc:creator>Don Hanley</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://lteuniversity.com/expert_opinion1/b/donhanley/rsscomments.aspx?WeblogPostID=10213</wfw:commentRss><comments>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2010/07/21/1xev-do-vs-lte-connection-setup.aspx#comments</comments><description>&lt;p&gt;So far in this ongoing series comparing 1xEV-DO with LTE,
I&amp;#39;ve covered initial system acquisition and the random access process. Although
the specific details obviously differ, 1xEV-DO and LTE have some remarkable
similarities in these functions. &lt;/p&gt;
&lt;p&gt;The next step in setting up a call is the actual message
exchange between the mobile device and the network. This is where resources are
allocated and the radio link is configured for the particular service being
requested; this is also where 1xEV-DO and LTE start to diverge, due to some of
the fundamental differences between the technologies.&lt;/p&gt;
&lt;p&gt;
The basic connection setup sequences for 1xEV-DO
and LTE are illustrated here:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://lteuniversity.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/1xEV_2D00_DOvsLTE_5F00_ConnectionSetup.png"&gt;&lt;img src="http://lteuniversity.com/resized-image.ashx/__size/550x0/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/1xEV_2D00_DOvsLTE_5F00_ConnectionSetup.png" border="0" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Although both 1xEV-DO and LTE are solely packet-oriented
solutions, 1xEV-DO has its roots in its circuit-oriented predecessor, cdma2000 1x.
In particular, this means that the AT will be in soft handoff with up to 6
sectors, based on the measurements reported in Route Update messages. An LTE UE
only supports hard handovers, and communicates with only 1 eNB at a time.&lt;/p&gt;
&lt;p&gt;Since (1) connections in 1xEV-DO are pre-defined during the DO
session configuration exchange between the AT and the RNC, (2) there&amp;#39;s really
only one type of service supported in 1xEV-DO (high speed packet data), and (3)
all ATs are functionally the same, there&amp;#39;s no need to include any of that
information in the signaling messages. This keeps the setup exchange short and
simple; in fact, the first part of the setup messaging occurs during the random
access process itself. Other than the Route Update and Traffic Channel
Assignment, the messages used in a 1xEV-DO connection setup contain little or
no extra information. &amp;nbsp;In LTE, however,
the requested service, radio link configuration, and UE characteristics must
all be explicitly defined, which can make for some fairly lengthy messages.&lt;/p&gt;
&lt;p&gt;1xEV-DO forward link traffic channels are identified by an
assigned MAC index, one for each member of the active set; this pre-allocation
reduces the signaling overhead needed for transmitting data to the AT, but may
lead to MAC index blocking under high traffic conditions. LTE resources are
basically assigned on the fly.&lt;/p&gt;
&lt;p&gt;The operation of the 1xEV-DO forward link relies on the
successful receipt of Data Rate Control (DRC) covers and values sent from the
AT over the DRC channel, so confirmation that the DRC channel is working
properly is built into the setup process before traffic begins to flow. LTE
does not perform a similar check for its Channel Quality Indicator (CQI)
values. (I&amp;#39;ll cover the details of traffic operations in a later blog.)&lt;/p&gt;
&lt;p&gt;
What&amp;#39;s the bottom line? 1xEV-DO is optimized for
best effort, delay tolerant, packet data applications, and is designed to keep
the signaling necessary to set up and maintain a call short and to the point.
LTE, in contrast, is intended to be flexible, supporting a wide variety of
packet services and Quality of Service requirements, which requires long and
complex messages to properly assign the appropriate radio resources to the
call.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10213" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/don+hanley/default.aspx">don hanley</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/1xEV-DO/default.aspx">1xEV-DO</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/connection/default.aspx">connection</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/setup/default.aspx">setup</category></item><item><title>1xEV-DO vs. LTE: Random Access</title><link>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2010/06/23/1xev-do-vs-lte-random-access.aspx</link><pubDate>Wed, 23 Jun 2010 20:51:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10154</guid><dc:creator>Don Hanley</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://lteuniversity.com/expert_opinion1/b/donhanley/rsscomments.aspx?WeblogPostID=10154</wfw:commentRss><comments>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2010/06/23/1xev-do-vs-lte-random-access.aspx#comments</comments><description>&lt;p&gt;In my previous blog, I compared how 1xEV-DO and LTE devices
perform an initial system acquisition. Now I&amp;#39;ll continue with the next step in
setting up a data call, random access. &lt;/p&gt;
&lt;p&gt;In virtually every mobile wireless system, mobiles
attempting to get on the system have to overcome a Catch-22: they need a radio
channel in order to request a radio channel. The usual solution to this is to
define a common, or shared, random access channel, which allows devices to
transmit their initial messages without permission. Since these random accesses
are not coordinated with the network, there is a risk of colliding with other
users; in addition, there is only limited information available from the
network to help the mobile determine how much power it should use for its transmission.&lt;/p&gt;
&lt;p&gt;3G and 4G systems have taken a remarkably similar approach
to managing collisions and initial power. Based on the system parameters sent
over the broadcast channels, each mobile selects a random access time, and
estimates the amount of power its transmission should require. If it receives a
positive acknowledgement from the network (indicating that its transmission was
successfully received and accepted), then the mobile proceeds with the rest of
the signaling needed to set up the call; otherwise, it waits a small amount of
time (in order to avoid colliding with another user) and tries again with a
little more power (to improve its chances to be heard by the network). How many
times it tries and how loud it gets are determined by the system configuration
parameters.&lt;/p&gt;
&lt;p&gt;
The random access sequences for 1xEV-DO and LTE
are illustrated here:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.lteuniversity.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/1xEV_2D00_DO_5F00_vs_5F00_LTE_5F00_Random-Access_5F00_fig1.jpg"&gt;&lt;img src="http://www.lteuniversity.com/resized-image.ashx/__size/550x0/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/1xEV_2D00_DO_5F00_vs_5F00_LTE_5F00_Random-Access_5F00_fig1.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;These sequences are very similar, but there are a few
important differences:&lt;/p&gt;
&lt;p&gt;1)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;b&gt;Random
access content.&lt;/b&gt; A transmission over the 1xEV-DO Access Channel (ACH),
called a probe, consists of an initial preamble (containing only the pilot)
followed by the actual messages themselves (typically a Route Update and a
Connection Request). In LTE, the UE transmits a simple preamble signal over the
Physical Random Access Channel (PRACH); the actual RRC Connection Request
message is sent only after a positive acknowledgement is received from the
network.&lt;/p&gt;
&lt;p&gt;2)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;b&gt;Initial
power estimate.&lt;/b&gt; 1xEV-DO determines its initial power level by subtracting the
measured forward link signal strength (Mean RX Power) from its nominal power
level (Open Loop Adjust) and then adding the downlink path loss (Pilot Strength
Nominal minus the measured pilot strength) and a &amp;quot;fudge factor&amp;quot;, Probe Initial
Adjust; note that the downlink path loss estimate is constrained within
configured minimum and maximum values. LTE simply adds the configured Preamble
Received Target Power to an uplink path loss value determined by the UE, and
then ensures that the initial power does not exceed the allowed maximum power P&lt;sub&gt;CMAX&lt;/sub&gt;.&lt;/p&gt;
&lt;p&gt;3)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;b&gt;Access
retries.&lt;/b&gt; In both systems, if a positive acknowledgement is not received in
response to the access attempt, the device will try again, increasing its power
by a small amount (Power Step in 1xEv-DO, Power Ramping Step in LTE). A 1xEV-DO
AT will try a total of Probe Num Step probes, wait a randomized amount of time,
and then repeat the entire sequence Probe Sequence Max times, recalculating the
initial power at the start of each sequence. In LTE, the UE will send up to
Preamble Trans Max preambles, but will not repeat the sequence if it does not
receive an acknowledgement.&lt;/p&gt;
&lt;p&gt;
1xEV-DO and LTE use similar processes to make
their first contact with the network, but 1xEV-DO works a little harder at it,
giving the AT more opportunities to be heard. Of course, the more accurate the
initial power estimate is, the more likely it is that the transmission will be
heard and acknowledged.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10154" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/don+hanley/default.aspx">don hanley</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/system+aquisition/default.aspx">system aquisition</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/1xEV-DO/default.aspx">1xEV-DO</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/random+access/default.aspx">random access</category></item><item><title>1xEV-DO vs. LTE: System Acquisition</title><link>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2010/06/10/1xev-do-vs-lte-system-acquisition.aspx</link><pubDate>Thu, 10 Jun 2010 16:18:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:10143</guid><dc:creator>Don Hanley</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://lteuniversity.com/expert_opinion1/b/donhanley/rsscomments.aspx?WeblogPostID=10143</wfw:commentRss><comments>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2010/06/10/1xev-do-vs-lte-system-acquisition.aspx#comments</comments><description>&lt;p&gt;LTE (Long Term Evolution) has been designed from the very
beginning to provide a natural evolution path for GSM/GPRS and UMTS networks. As
a consequence, someone knowledgeable about UMTS will find many aspects of LTE
to be familiar. But how does someone used to the unique design of a 1xEV-DO
network learn about how LTE works? Earlier blogs and white papers have
discussed the different terms used in 1xEV-DO and LTE networks; let me put
those into context now, comparing key LTE network operations with their 1xEV-DO
equivalents.&lt;/p&gt;
&lt;p&gt;
I&amp;#39;ll begin at the beginning. When a mobile
device (an AT in 1xEV-DO, or a UE in LTE) first powers on, it must first go
through a process called &amp;quot;system acquisition&amp;quot;, where it locks on to a suitable
radio channel and learns some basic information about the network. The
illustration below lays out the key system acquisition steps for 1xEV-DO and
LTE, side by side.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.lteuniversity.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/1xEV_2D00_DO-vs-LTE_5F00_Fig1.png"&gt;&lt;img src="http://www.lteuniversity.com/resized-image.ashx/__size/550x0/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/1xEV_2D00_DO-vs-LTE_5F00_Fig1.png" border="0" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;At first glance, they don&amp;#39;t look very much alike; however,
both sequences perform the same basic functions:&lt;/p&gt;
&lt;p&gt;1)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;b&gt;Locate a
channel.&lt;/b&gt; 1xEV-DO devices search for the distinctive DO pilot signal in each
slot, while LTE UEs look for the Direct Current (DC) subcarrier at the center
of the LTE channel.&lt;/p&gt;
&lt;p&gt;2)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;b&gt;Synchronize
with the radio link.&lt;/b&gt; 1xEV-DO uses the timing of the pilot signal and the
Control Channel preamble to determine slot and frame timing, while LTE uses
explicit Primary and Secondary Synchronization signals.&lt;/p&gt;
&lt;p&gt;3)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&lt;b&gt;Learn the
system configuration.&lt;/b&gt; A 1xEV-DO AT will read the Synch, Quick Config,
Sector Parameters and Access Parameters messages in the Control Channel, while
an LTE UE reads the Master Information Block (MIB) and System Information
Blocks (SIBs) 1 and 2 in the Physical Broadcast Channel (PBCH). Note that an AT
learns the cell&amp;#39;s identity (the PN offset) from the Synch message, while a UE
derives the physical cell ID from the synchronization signals.&lt;/p&gt;
&lt;p&gt;
At this point, both devices (1xEV-DO and LTE)
are ready to send their first message to the network. I&amp;#39;ll cover that process
in the next entry in this series.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://lteuniversity.com/aggbug.aspx?PostID=10143" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/don+hanley/default.aspx">don hanley</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/at/default.aspx">at</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/ue/default.aspx">ue</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/system+aquisition/default.aspx">system aquisition</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/1xEV-DO/default.aspx">1xEV-DO</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/channel/default.aspx">channel</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/radio+link/default.aspx">radio link</category></item><item><title>LTE and 1x/1xEV-DO Terminology and Concepts</title><link>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2009/02/10/lte-and-1x-1xev-do-terminology-and-concepts.aspx</link><pubDate>Tue, 10 Feb 2009 18:25:00 GMT</pubDate><guid isPermaLink="false">05bacdad-08ce-46d8-8ce2-4d61cae666b7:340</guid><dc:creator>Don Hanley</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://lteuniversity.com/expert_opinion1/b/donhanley/rsscomments.aspx?WeblogPostID=340</wfw:commentRss><comments>http://lteuniversity.com/expert_opinion1/b/donhanley/archive/2009/02/10/lte-and-1x-1xev-do-terminology-and-concepts.aspx#comments</comments><description>&lt;p&gt;By Don Hanley, Senior Consultant - 2/2009&lt;/p&gt;
&lt;h3&gt;1xEV-DO and LTE networks are surprisingly similar in many respects, but the terms, labels and acronyms they use are very different. How can a 1xEV-DO operator make sense of this new jargon?&lt;/h3&gt;
&lt;h2&gt;Introduction&lt;/h2&gt;
&lt;p&gt;As 4G technologies like Mobile WiMAX and Long Term Evolution (LTE) move closer to commercial reality, operators are beginning to understand the differences and the similarities between what they have currently deployed and what is coming down the road. Service providers who are contemplating the transition from 1xEV-DO to LTE will have to contend not only with new radio technologies and new network architectures, but with a whole new set of terms and concepts as well.&lt;/p&gt;
&lt;p&gt;Both 1xEV-DO and LTE are designed to offer high-speed packet data services to mobile subscribers, so it should not be surprising that they have taken similar approaches to solving some of the challenges they both face. An engineer familiar with 1xEV-DO can get a head start with understanding LTE simply by learning the meaning of key LTE terms and associating them with their 1xEV-DO counterparts.&lt;/p&gt;
&lt;p&gt;The following sections take various LTE concepts, grouped into related categories, and provide a brief explanation of each, along with the corresponding 1xEV-DO equivalent. In some cases, there is a one-to-one match between LTE and 1xEV-DO; in others, there simply is no equivalent concept. In most cases, however, there is generally something within 1xEV-DO that does the same thing as its LTE counterpart, under a different name or in a different location. We will identify the similarities and differences of LTE-EPC and 1x/1xEV-DO networks in various categories, including Air Interface, Access and Core Networks, Identities and Operations.&lt;/p&gt;
&lt;h2&gt;General&lt;/h2&gt;
&lt;p&gt;LTE is an evolution of the UMTS system defined by the 3G Partnership Project (3GPP), which is an offshoot of the European Telecommunications Standards Institute (ETSI). 1xEV-DO, on the other hand, is designed by the 3G Partnership Project 2 (3GPP2), which is associated with the North American Telecommunications Industry Association (TIA). Both 3GPP and 3GPP2 have mandates to develop specifications for wireless networks, but they have adopted rather different design philosophies, which are reflected in the resulting standards:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a) Flexibility versus optimization: In general, 3GPP prefers to create standards which are very open and flexible, allowing them to incorporate a variety of options, and to easily extend the interfaces to accommodate new features and capabilities. In contrast, 3GPP2 tends to define very optimized interfaces, which perform specific tasks as efficiently as possible. 1xEV-DO, for example, takes far fewer (and much shorter) messages to set up a data session than UMTS requires, but new features tend to require new sets of messages.&lt;/li&gt;
&lt;li&gt;b) Authentication and security: 3GPP takes privacy very seriously, and very little information is sent over the air in its original form; encryption, temporary identifiers, message integrity checking, and user verification are basic elements of LTE signaling. 3GPP2 also includes security functions in the definition of 1xEV-DO, but they are optional extensions to the basic operation of the system.&lt;/li&gt;
&lt;li&gt;c) User information: 3GPP makes extensive use of the Subscriber Identity Module (SIM), which stores user subscription data and related information separately from the phone itself. This allows a user to make use of a different device without losing their features and contacts. In 3GPP2 systems, the subscriber&amp;#39;s identity and the phone&amp;#39;s identity are usually tightly linked.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Despite the different mindsets behind the specifications, however, both 1xEV-DO and LTE do what they were designed to do quite well: deliver high-speed packet data to mobile users.&lt;/p&gt;
&lt;h2&gt;Air Interface&lt;/h2&gt;
&lt;p&gt;Not surprisingly, the greatest differences between LTE and 1xEV-DO lie in the air interface. 1xEV-DO is a CDMA-based system, using fixed 1.25 MHz channels, while LTE is a scalable OFDMA system, capable of using anywhere between 1.4 MHz and 20 MHz, divided into 15 kHz subcarriers. 1xEV-DO devices are assigned timeslots for downlink traffic, but can transmit at any time on the uplink (the hallmark of a CDMA system); LTE terminals must be explicitly allocated uplink and downlink non-overlapping resources to send and receive traffic. The Physical Layer descriptions of these two technologies are as different as night and day.&lt;/p&gt;
&lt;p&gt;Nonetheless, they must both be capable of supporting multiple users simultaneously, of allowing new users to access the network, of tracking the terminal&amp;#39;s location and redirecting traffic as the user moves. Key LTE terms relating to the air interface, and their 1xEV-DO equivalents, are listed here.&lt;/p&gt;
&lt;table border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;LTE Term&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p align="center"&gt;Meaning and Usage&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;1xEV-DO Equivalent&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;OFDMA&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Orthogonal Frequency Division Multiple Access, physical layer of LTE Downlink&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;CDMA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;SC-FDMA&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Single Carrier Frequency Division Multiple Access, physical layer of LTE Uplink&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;CDMA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Subcarrier&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A single 15 kHz radio channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Radio channel &lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Symbol&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A single 66.67 &amp;micro;s time period&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Chip (0.81 &amp;micro;s)&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Resource Element&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;The smallest unit of radio resources, one subcarrier for one symbol&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;n/a&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Resource Block&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;The smallest block of resources that can be allocated, 12 subcarriers for 7 symbols (84 resource elements)&lt;a name="_ftnref1" href="http://www.lteuniversity.com/tiny_mce/plugins/paste/blank.htm#_ftn1"&gt;[1]&lt;/a&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;n/a&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Timeslot&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;7 consecutive symbols&lt;sup&gt;1&lt;/sup&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Slot&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Subframe&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;2 consecutive timeslots&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;n/a&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Frame&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;10 consecutive subframes, the basic transmission interval&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Frame&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Synchronization Signal&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Periodic signal for synchronizing with and identifying cells&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Sync message&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Reference Signal&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Periodic signal for transmission quality measurements&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Pilot Channel&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PBCH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Broadcast Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Control Channel&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PDSCH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Downlink Shared Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Forward Traffic Channel&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PDCCH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Downlink Control Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Preambles + MAC channels&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PCFICH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Control Format Indicator Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;DO Session&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PHICH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Hybrid ARQ Indication Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;ARQ Channel&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PRACH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Random Access Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Access Channel&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PUSCH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Uplink Shared Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Reverse Traffic Channel&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PUCCH&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Physical Uplink Control Channel&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;MAC Channels&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;&amp;nbsp;&lt;/h2&gt;
&lt;h2&gt;Access Network&lt;/h2&gt;
&lt;p&gt;&lt;a href="http://www.lteuniversity.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/access.png"&gt;&lt;img border="0" src="http://www.lteuniversity.com/resized-image.ashx/__size/550x0/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/access.png" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Figure 1 illustrates an LTE eUTRAN, the radio access network. The eUTRAN has a flat architecture, with no centralized controller; instead each eNode B manages its own radio resources, and collaborates with other eNode B&amp;#39;s over the X2 interface. The eNode B&amp;#39;s connect to the core network over the S1 interface, to allow users to register with the network and send and receive traffic.&lt;/p&gt;
&lt;p&gt;Key LTE terms relating to the access network, and their 1xEV-DO equivalents, are listed here:&lt;/p&gt;
&lt;table border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;LTE Term&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p align="center"&gt;Meaning and Usage&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;1xEV-DO Equivalent&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;eUTRAN&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Evolved Universal Terrestrial Radio Access Network&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;AN&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;eNode B&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Evolved Node B&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Base station + RNC&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Physical Layer Cell ID&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Unique cell identifier&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Pilot PN offset&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;UE&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;User Equipment&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;AT&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;X2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;eNode B &amp;lt;-&amp;gt; eNode B interface&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;A13/A16/A17/A18&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;S1&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;eNode B &amp;lt;-&amp;gt; core network interface&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;A10/A11/A12&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Uu&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;LTE air interface&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Specified per 3GPP2 C.S0024 (IS-856)&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Attach&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A configured signaling path between the UE and the eNode B&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;DO Session&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Radio Bearer&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A configured and assigned radio resource&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;DO Connection&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Core Network&lt;/h2&gt;
&lt;p&gt;The LTE and 1xEV-DO core networks are more similar than they are different; Figure 2 shows a view of the LTE Evolved Packet Core (EPC). Both are based on IP protocols, and support seamless access to packet-based services; both make use of Mobile IP to redirect traffic as the user moves through the network.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.lteuniversity.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/core.png"&gt;&lt;img border="0" src="http://www.lteuniversity.com/resized-image.ashx/__size/550x0/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/core.png" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Key LTE terms associated with the core network, and their 1xEV-DO equivalents, are listed here:&lt;/p&gt;
&lt;table border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;LTE Term&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p align="center"&gt;Meaning and Usage&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;1xEV-DO Equivalent&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;EPC&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Evolved Packet Core&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Packet Data Network&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;MME&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Mobility Management Entity&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;RNC + PDSN + AN-AAA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;S-GW&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Serving Gateway&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;PDSN + PCF&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PDN-GW&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Packet Data Network Gateway&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;HA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;HSS&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Home Subscriber System&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;AAA&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;PCRF&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Policy Charging Rule Function&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;PCRF&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;MIP&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Mobile IP&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;MIP&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;S1 Bearer&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A configured traffic path between the eNode B and the S-GW&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;A10 + R-P Session&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;S5/S8 Bearer&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A configured traffic path between the S-GW and the PDN-GW&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;MIP&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;EPS Bearer Service&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;A configured end-to-end traffic path between the UE and the PDN-GW (Radio Bearer + S1 Bearer + S5/S8 Bearer)&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;PPP + MIP&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;Operational Terms and Identifiers&lt;/h2&gt;
&lt;p&gt;When a mobile device arrives in the network, it must be recognized, configured and assigned resources, and its services must be maintained as it moves from cell to cell. Various terms associated with LTE operational functions, and their 1xEV-DO equivalents, are listed here:&lt;/p&gt;
&lt;table border="1" cellpadding="0" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;LTE Term&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p align="center"&gt;Meaning and Usage&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p align="center"&gt;1xEV-DO Equivalent&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;UE&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;User Equipment (the mobile device)&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Access Terminal (AT)&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;IMSI&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;International Mobile Subscriber Identity&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;IMSI [Mobile Country Code (MCC), Mobile Network Code (MNC) and &amp;nbsp;Mobile Identification Number (MIN) or&lt;/p&gt;
&lt;p&gt;Mobile Directory Number (MDN)]&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;IMEI&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;International Mobile Equipment Identity&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Mobile Serial Number (MSN) or Mobile Equipment Identity (MEID)&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Downlink (DL)&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Transmissions from the network to the mobile&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Forward Link (FL)&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Uplink (UL)&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Transmissions from the mobile to the network&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Reverse Link (RL)&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Ciphering&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Over-the-air privacy&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Encryption&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Attach&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Initial registration process&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;UATI Assignment + DO Session Establishment + MIP Registration&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;MIB, SIB&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Master Information Block and System Information Block&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Quick Config + Sector Parameters + Access Parameters + DO Session&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;DCI, UCI&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Downlink Control Information and Uplink Control Information&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Traffic Channel Assignment&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;C-RNTI&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Cell Radio Network Temporary Identifier&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;MAC Index&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;CQI&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Channel Quality Indicator&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;DRC value&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;HARQ&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Hybrid ARQ&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;HARQ&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Handover&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Redirection of traffic from one base station to another&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Handoff&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td width="151"&gt;
&lt;p&gt;Measurement Control events A1, A2, A3, A4, A5, B1, B2&lt;/p&gt;
&lt;/td&gt;
&lt;td width="336"&gt;
&lt;p&gt;Thresholds for cell selection and handover&lt;/p&gt;
&lt;/td&gt;
&lt;td width="151"&gt;
&lt;p&gt;Pilot Add, Pilot Drop, Dynamic (Soft Slope) Thresholds&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;A simple description in a table does not convey the full complexity of a concept; a detailed understanding of LTE&amp;#39;s technologies, architectures and interfaces is needed to fully appreciate both the similarities and the differences it has with 1xEV-DO. Nevertheless, the fact that LTE and 1xEV-DO concepts can be laid out side-by-side in this way should help to reassure 1xEV-DO operators that the step from 3G to 4G is not as big a leap as they may have thought.&lt;/p&gt;
&lt;p&gt;Award Solutions, Inc. provides exceptional training and consulting in advanced wireless and Internet technologies. Our proven experience enables us to offer a complete suite of services: cutting edge technology training, customized training solutions, and advanced technology consulting.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Our products and services provide our clients with innovative, flexible, and cost-effective solutions that help rapidly boost their workforce productivity and competence to more quickly meet their market demands. Award Solutions will be happy to customize our course content to meet any specific needs.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The level of technical depth in our training courses gives students a unique benefit that they can apply immediately. We offer a range of courses appropriate for audiences needing a high-level overview, as well as engineers looking for in-depth details.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Award Solutions continues to provide successful training and network performance solutions as well as professional consulting services for many telecommunications and Internet equipment manufacturers, service providers and enterprises, just as we have since 1997.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please visit our website at &lt;a href="http://www.awardsolutions.com/"&gt;www.awardsolutions.com&lt;/a&gt; for our full line of services and latest curriculums.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you have any questions, concerns or comments regarding this document, please write to us at: &lt;a href="mailto:friends@awardsolutions.com"&gt;friends@awardsolutions.com&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.lteuniversity.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/logos.png"&gt;&lt;img border="0" src="http://www.lteuniversity.com/resized-image.ashx/__size/550x0/__key/CommunityServer.Blogs.Components.WeblogFiles/donhanley/logos.png" alt="" /&gt;&lt;/a&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/p&gt;
&lt;p&gt;&amp;nbsp;The 3GPP and LTE logos are the property of Third Generation Partnership Project (3GPP). The 3GPP2 logo is property of Third Generation Partnership Project (&lt;em&gt;3GPP2&lt;/em&gt;) and its organization partners. The TIA logo is property of Telecommunications Industry Association (TIA). The content of this document is based on 3GPP/LTE, 3GPP2 and TIA specifications which are available at &lt;a href="http://www.3gpp.org/"&gt;www.3gpp.org&lt;/a&gt;, &lt;a href="http://www.3gpp2.org/"&gt;www.3gpp2.org&lt;/a&gt;, and &lt;a href="http://www.tiaonline.org/"&gt;www.tiaonline.org&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;br clear="all" /&gt;&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=340" width="1" height="1"&gt;</description><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/don+hanley/default.aspx">don hanley</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/wimax/default.aspx">wimax</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/lte/default.aspx">lte</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/umts/default.aspx">umts</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/mobile+wimax/default.aspx">mobile wimax</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/whitepaper/default.aspx">whitepaper</category><category domain="http://lteuniversity.com/expert_opinion1/b/donhanley/archive/tags/3gpp-+1xEV-DO/default.aspx">3gpp. 1xEV-DO</category></item></channel></rss>