136280714-LTE100-Motorola-LTE-Training.pdf

LTE100: Introduction to Long Term Evolution
FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
© 2010 Motorola, Inc.

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories
or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs,
including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer
programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express
written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation
of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or
disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized
copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies
or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to
time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the
application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
M-Cell™, Taskfinder™ and Intelligence Everywhere™ are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
CE Compliance
The CE mark confirms Motorola Ltd’s statement of compliance with
EU directives applicable to this product. Copies of the Declaration
of Compliance and installation information in accordance with the
requirements of EN50385 can be obtained from the local Motorola
representative or the CNRC help desk, contact details below:
Email: csc.emea@motorola.com
Tel: +44 (0) 1793 565 444
© 2010 Motorola, Inc. LTE100: Introduction to Long Term Evolution

Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
■
■
■
■
Chapter 1: Lesson 1: What is Long Term Evolution (LTE)?
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Conventions Used in this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
Purpose of the Participant Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 3
References and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 4
Expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 5
Practicalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 5
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
Course Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 6
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 8
Drivers for Long Term Evolution (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 9
3rd Generation Partnership Project (3GPP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
GSM Network Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Global System for Mobile Communication (GSM) Evolution . . . . . . . . . . . . . . . . . . . 1-11
How Does LTE Fit into 3GPP Roadmap? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
3GPP Release 8 Network Architecture (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
E-EUTRAN Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Performance Goals for LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Spectrum Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Spectrum Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Increased Peak Data Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Increased User Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Control Plane Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
User Plane Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Cell Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Lesson 1 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Chapter 2: Lesson 2: LTE Network Architecture
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 3
3GPP Release 8 Network Architecture (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 4
evolved Node B (eNodeB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 4
User Entity (UE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 5
Mobility Management Entity (MME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 6
Serving Gateway (S-GW). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 8
Packet Data Network Gateway (P-GW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 9
Other EPC Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Interworking with Other Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
eNodeB Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Motorola LTE Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
eNodeB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Wireless Broadband Controller (WBC) 700 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Wireless Broadband Controller (WBC) 700 as S-GW . . . . . . . . . . . . . . . . . . . . . . 2-17
Wireless Broadband Core (WBC) 700 as P-GW . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Wireless Broadband Manager (WBM) 700 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
WBM 700 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
GSM to LTE Migration/Overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
CDMA LTE Overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
CDMA Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Self-Organizing Network (SON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
i

Contents LTE100: Introduction to Long Term Evolution
SON Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Motorola SON Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Proposed Motorola SON Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Lesson 2 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Chapter 3: Lesson 3: LTE Air Interface
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 3
Radio Frequency Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 4
LTE Spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 4
Channel Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 4
Channel Sampling Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 6
Orthogonal Frequency Division Multiplexing (OFDM) . . . . . . . . . . . . . . . . . . . . . . . . 3- 7
Non-Orthogonal Subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 7
Orthogonal Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 8
Subcarrier Transmitter Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 9
Subcarrier Receiver Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Fast Fourier Transform (FFT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Scalable OFDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Subcarrier Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Symbol Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Multipath Delay and Inter-Symbol Interference . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Cyclic Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Subcarrier Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Occupied Subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
LTE Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
LTE Frame Length and Subcarriers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Channel Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Frequency Division Duplexing (FDD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Time Division Duplexing (TDD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Frame Type 1 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Resource Blocks and Resource Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Physical and Virtual Resource Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Reference Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Frame Type 1 Subframes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
FDD Operation – DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
FDD UL Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Frame Type 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Special Subframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Frame Type 2 UL/DL Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
OFDM Bandwidth Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
OFDMA Bandwidth Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
OFDMA Transmitter Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
OFDMA Receiver Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Single Carrier-Frequency Division Multiple Access (SC-FDMA) . . . . . . . . . . . . . . . . . . . 3-36
OFDMA Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
UE Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
SC-FDMA Transmitter Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
SC-FDMA Receiver Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
OFDMA Subcarrier Encoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
SC-FDMA Subcarrier Encoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Modulation and Coding Schemes (MCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Selected Transmitter Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Modulation Techniques Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Modulation Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Modulation and Signal Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Estimating FDD Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Multiple Antenna Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Single Input Multiple Output (SIMO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Multiple Input Single Output (MISO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Multiple Input Multiple Output (MIMO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
MIMO Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Single User MIMO (SU–MIMO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Multi-User MIMO (MU–MIMO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
ii LTE100: Introduction to Long Term Evolution

LTE100: Introduction to Long Term Evolution Contents
Lesson 3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Chapter 4: Lesson 4: LTE and EPC Protocol Overview
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 3
Selected EPS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 4
EPS and the TCP/IP Protocol Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 4
Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 5
User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 6
Uu Interface Data Link Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 8
Radio Resource Control (RRC) Sublayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 9
Packet Data Convergence Protocol (PDCP) Sublayer . . . . . . . . . . . . . . . . . . . . . 4- 9
Radio Link Control (RLC) Sublayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 9
Medium Access Control (MAC) Sublayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Uu Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
SAE and LTE Channel Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Logical Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Transport Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Physical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Transport to Physical Channel Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Mapping DL Physical Channels to Subframes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Broadcast Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Synchronization Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Mapping UL Physical Channels to Subframes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Mapping PUCCH to Subframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Random Access Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Random Access Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
S1-MME Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
S1-MME Interface Control Protocol Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
S1 Application Protocol (S1AP) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
UE to MME Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
S1-U and S5-U Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
S1-U User Plane Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
S5 Interface User Plane Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
S5 Control Plane Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Uu to P-GW User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
X2 Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
X2 Control Plane Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
X2 Application Protocol (X2AP) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
X2 User Plane Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Lesson 4 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Chapter 5: Lesson 5: Network Acquisition and Call Process
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 3
Basic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 4
Radio Resource Control (RRC) States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 5
Radio Resource Control (RRC) – Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 5
Radio Resource Control (RRC) – Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 5
Radio Resource Control (RRC) Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 5
EPS Mobility Management (EMM) States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 7
EPS Mobility Management (EMM) – Deregistered . . . . . . . . . . . . . . . . . . . . . . . 5- 7
EPS Mobility Management (EMM) – Registered . . . . . . . . . . . . . . . . . . . . . . . . 5- 7
EPS Connection Management (ECM) States . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
EPS Connection Management (ECM) – Idle . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
EPS Connection Management (ECM) – Connect . . . . . . . . . . . . . . . . . . . . . . . . 5- 8
EPS Session Management (ESM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 9
ESM_INACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 9
ESM_ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5- 9
Non Access Stratum (NAS) States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
EMM_DEREGISTERED, ECM_IDLE and ESM_INACTIVE . . . . . . . . . . . . . . . . . . . 5-10
EMM_REGISTERED, ECM_IDLE and ESM_ACTIVE. . . . . . . . . . . . . . . . . . . . . . 5-10
EMM_REGISTERED, ECM_CONNECT and ESM_ACTIVE. . . . . . . . . . . . . . . . . . . 5-10
Selected EPS IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
iii

Contents LTE100: Introduction to Long Term Evolution
MME IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
UE IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
International Mobile Subscriber Identifier (IMSI) Structure . . . . . . . . . . . . . . . . . . . 5-13
Attaching to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
eNodeB Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
System Information (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Initial Cell Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Network Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Quality of Service (QoS) / EPS Bearer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Bearer Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
QoS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Service Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
UE Triggered Service Request — Simplified . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Mobility Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Tracking Area (TA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
MME and S-GW Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Tracking Area Update (TAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
X2 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
UE Triggered Detach (UE Switched Off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Security in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
LTE Security Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Function of LTE Security Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Authentication and Key Agreement Process (AKA) . . . . . . . . . . . . . . . . . . . . . . . 5-31
Lesson 5 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Memory Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
iv LTE100: Introduction to Long Term Evolution

About This Manual Version 3 Rev 1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
■
■
■
■
1

Version 3 Rev 1
This page intentionally left blank.
2 LTE100: Introduction to Long Term Evolution

Lesson 1: What is Long Term Evolution (LTE)? Version 3 Rev 1
Chapter 1
Lesson 1: What is Long Term Evolution (LTE)?
In this lesson, we will introduce the LTE standards body, define LTE and its performance goals, look at the network
architecture changes introduced by LTE, and compare/contrast LTE to current wireless technologies.
1-1

Version 3 Rev 1 Lesson 1: What is Long Term Evolution (LTE)?
1-2 LTE100: Introduction to Long Term Evolution

Course Introduction Version 3 Rev 1
Course Introduction
Preface
The course is designed to provide an introductory technical overview to the Evolved Packet System
(EPS), including the Long Term Evolution (LTE) and Evolved Packet Core (EPC) infrastructure,
operations, and signaling. In this course, we will focus on the LTE Uu (air) interface and LTE/SAE
signaling and operation.
Prerequisite
Students should have a general knowledge of telecommunications systems or have attended LTE102 a
two hour online LTE Technical Overview course.
Target Audience
The primary audience of this course is Motorola and customer RF Engineers, Network Planning
Engineers, and Senior Technical Staff. A secondary audience includes anyone who requires an
overview of LTE/SAE concepts, operation, and signaling.
Conventions Used in this Guide
Throughout this guide, you will find icons representing various types of information. These icons serve
as reminders of their associated text.
Table 1-1
Indicates a Note or additional
information that might be
helpful to you.
Indicates If/then situations.
These are found in many of
the labs.
LTE
300
Telecoms
Indicates a list of References
that provide additional
information about a topic.
Indicates a Warning or
Caution. These generally
flag a service affecting
operation.
Indicates a Lab that provides
the opportunity for you to
exercise what you’ve learned.
Indicates a Memory Point.
These provide a chance for
the candidate to reflect on the
training and if necessary ask
a relevant question.
Purpose of the Participant Guide
The Participant Guide contains the content that the instructor will cover during the course. Given the
interactive nature of instructor-led courses, this guide may not contain everything the instructor discusses.
Since the book is yours to take with you, feel free to make notes in it. You can also use it to document
key points, questions you’d like to pose and the answer(s), and if you are inclined, you can doodle in it.
While the Participant Guide can act as reference when you return to work, keep in mind that the
information does change. If you require technical references to the information presented in this
Participant Guide, always use the most current versions of the pertinent technical documentation.
1-3

Version 3 Rev 1 Course Introduction
Course Introduction
References and Resources
The Participant Guide is not a technical book in the traditional, analytical sense. The material and
information contained here is subject to change. The following references were used in the development
of this course and should be used for most current information:
Table 1-2
Trade Press Books
• Dahlman, Parkvall, Skolk, Beming; 3G Evolution: HSPA and LTE for Mobile
Broadband, Academic Press, 2nd edition 2008
• Lescuyer, Lucidarme; Evolved Packet System (EPS): The LTE and SAE
Evolution of 3G UMTS, John Wiley and Sons, 2008
LTE
300
Telecoms
3GPP Technical Specifications (www.3gpp.org)
• 23.122 NAS Procedures for Idle MS
• 23.401 GPRS Enhancements for E-UTRAN Access
• 23.402 Architecture Enhancements for non-3GPP Access
• 24.301 NAS Protocol for EPS
• 36.201 LTE Physical Layer, General Description
• 36.211 Physical Channels and Modulation
• 36.212 Multiplexing and Channel Coding
• 36.213 Physical Layer Procedures
• 36.214 Physical Layer Measurements
• 36.300 E-UTRA/E-UTRAN Overall description; Stage 2
• 36.321 Medium Access Control (MAC) Protocol Specification
• 36.322 Radio Link Control (RLC) Protocol Specification
• 36.323 Packet Data Convergence Protocol (PDCP) Specification
• 36.331 Radio Resource Control (RRC) Protocol Specification
• 36.410 S1 General Aspects and Principles
• 36.411 S1 Layer 1
• 36.412 S1 Signaling Transport
• 36.413 S1 Application Program (S1AP)
• 36.414 S1 Data Transport
• 36.420 X2 General Aspects and Principles
• 36.421 X2 Layer 1
• 36.422 X2 Signaling Transport
• 36.423 X2 Application Program (S1AP)
• 36.424 X2 Data Transport
MyNetworkSupport Web Page
The on-line support allows customers to open cases trouble tickets, open RMA’s to send boards back
for repair, and download technical documentation.

Course Introduction Version 3 Rev 1
Course Introduction
Figure 1-1
The URL of the customer support web
page is:
hps://mynetworksupport.motorola.com
This is a secure web site. A password
request form can be downloaded from
this page.
page is:
this p
pag
ge.
page is:
this page.
As LTE products continue to evolve, we will make a continued effort to keep this material up-to-date. All
suggestions and recommendations are welcomed. Please submit your recommended changes to the
instructor. Thanks for all your constructive feedback.
Expectations
The activities in this course will require individual and team participation and we ask you to:
• Ask questions
• Share openly
• Return promptly from lunch and breaks
• Avoid distracting others by turning off cell phones or setting them to voicemail or vibrate
• Respect others
• Have fun!!!
Practicalities
Many participants who attend this course may not be familiar with this location’s facilities or the
surrounding area. To ensure your comfort during this course, please make notes on the following
helpful information.
Locations
Restrooms close to classroom: _______________________________________________________
Restroom locations in building: _______________________________________________________
Lunch facilities in building: __________________________________________________________
Lunch facilities nearby: _____________________________________________________________
After hours activities
Where to eat?.........What to see?.........What to do?........
During class breaks, ask the instructor and other participants about local sites that may be of interest.
Jot down the information below.
1-5

Course Introduction
Course Objectives
• Describe the goals of the 3rd Generation Partnership Project (3GPP)
• Explain the performance goals of LTE
• Explain where LTE fits in the evolution of GSM/UMTS networks
• Explain how LTE differs from existing 3G networks
• Describe the changes in network architecture introduced by LTE
• State the functional blocks that comprise an LTE network
• Explain the function of the network elements that comprise the Evolved Universal Terrestrial
Radio Access Network (E-UTRAN)
• Explain the function of the network elements that comprise the Evolved Packet Core (EPC)
• Describe Motorola’s LTE network architecture
• State the operating frequencies used by the LTE air interface
• Describe OFDM subcarrier and symbol characteristics
• Describe LTE duplexing and framing methods
• List the modulation techniques used by the LTE air interface
• Compare OFDMA and SC-FDMA usage in LTE
• Describe LTE antenna systems
• Describe the LTE Uu User and Control Plane protocol stacks
• List the LTE transport, logical and physical channels
• Explain the functions of the LTE physical channels
• List the Uu, S1-MME, S1-U, S5-U, and X2 interface functions
• Describe the S1-MME, S1-U, S5-U, S5–C and X2 User and Control Plane protocol stacks
• List the UE states
• Describe the UE network acquisition process
• Describe the UE registration process
• Describe “typical” UE call processes
• Describe UE active and mobility processes
• Describe the UE authentication process
Course Schedule
Table 1-3
Day 1
Course Introduction
Lesson 1 – What is Long Term Evolution (LTE)?
Lesson 2 – LTE Network Architecture
Lesson 3 — LTE Air Interface
Day 2
Lesson 3 – LTE and EPC Protocol Overview
Lesson 4 – Network Acquisition and Call Process

1-7

Version 3 Rev 1 Objectives
Objectives
At the completion of this lesson, you’ll be able to:
• Describe the goals of the 3rd Generation Partnership Project (3GPP)
• Explain the performance goals of LTE
• Explain where LTE fits in the evolution of GSM/UMTS networks
• Explain how LTE differs from existing 3G networks
• Describe the changes in network architecture introduced by LTE

Drivers for Long Term Evolution (LTE) Version 3 Rev 1
Drivers for Long Term Evolution (LTE)
Figure 1-2 Introduction – Drivers for Long Term Evolution
Over the last several decades, technological advancements have had a huge impact on the consumer
as well as the telecommunications carriers. Today, consumers expect voice, video and data information
to be available anytime, anywhere.
These advancements have also brought changes to the way the Telecom industry does business as
the traditional boundaries are blurring. Traditional fixed-line operators are expanding their boundaries
outside the home while the traditional mobile operators are moving into the fixed line business. The
goal of both is to capture maximum revenue while trying to meet the customer’s needs with what is now
referred to as the Quadruple Play; TV, Internet, Telephone, and Mobile.
The key is to be able to provide these services with a low cost per bit, higher capacity, increased flexibility,
and have global appeal so that network operators will want to deploy the technology.
To that end, the 3rd Generation Partnership Project (3GPP) has drafted a set of standards for the next
generation mobile broadband network: Long Term Evolution (LTE).
1-9

Version 3 Rev 1 3rd Generation Partnership Project (3GPP)
3rd Generation Partnership Project (3GPP)
Figure 1-3 Figure 1-2: 3GPP Standards Organization
GSM
GPRS/EDGE
UMTS
HSDPA
HSUPA
HSPA+
IMS
MBMS
LTE

Formalized in December 1998, the 3rd Generation Partnership Project (3GPP) is a group of
telecommunications associations whose main goal is to make globally applicable specifications for
Third Generation (3G) mobile phone systems.
3GPP is responsible for establishing the global standards for Global System for Mobile
Communication (GSM) and all of its subsequent releases; General Packet Radio Service (GPRS),
Enhanced Data rates for GSM Evolution (EDGE), High-Speed Downlink Packet Access (HSDPA),
High-Speed Uplink Packet Access (HSUPA), and now Long Term Evolution (LTE).

GSM Network Evolution Version 3 Rev 1
GSM Network Evolution
Figure 1-4 GSM Network Evolution
New “mobile” services such as streaming HD video, Online Gaming, Live Video, Social Networking, and
Peer2Peer file exchanges are in demand and on the horizon. Current wireless networks will struggle
to deliver enough capacity to “future proof” the desire for greater access, greater speed, and more
applications. To better understand why current networks struggle, let’s look at the evolution of GSM.
The following section is intended to be a brief review of GSM network evolution. Because
of the time constraints of the course, a detailed discussion is not possible. Talk with your
instructor during breaks, before, or after class if you need further explanation.
1-11

Version 3 Rev 1 GSM Network Evolution
Global System for Mobile Communication (GSM) Evolution
Figure 1-5 GSM Evolution – GSM, GPRS, EDGE, UMTS R99
Global System for Mobile Communication (GSM)
GSM is the most popular standard for mobile communication in the world. It is estimated that over 80%
of the global market uses the standard. GSM is considered a 2G network as both the signaling and voice
channels are digital. GSM also introduced Short Message Service (SMS). GSM data rates are 2.4, 4.8,
and 9.6 kbps.
General Packet Radio Service (GPRS)
GPRS is a packet data network that shares the radio access network with GSM but has a separate core
network. GPRS provides services such as Wireless Application Protocol (WAP), Short Message
Service (SMS), Multimedia Messaging Service (MMS), and email and Internet Access. GPRS has
theoretical data rates between 56 and 114 kbps. GPRS is considered a 2.5G network.
Enhanced Data Rates for GSM Evolution (EDGE)
EDGE provides coding and modulation improvements to GPRS that provides data speeds from 236 kbps
to 473 kbps depending on coding and modulation techniques used. Because of the latter (i.e., 473 kbps)
data rates, EDGE is considered 3G technology.
Univeral Mobile Telecommunications System R99 (UMTS R99)
UMTS R99 is the first release of UMTS. UMTS changes the air interface from Time Division Multiple
Access (TDMA) to Wideband Code Division Multiple Access (WCDMA). It is also characterized by
two separate core networks; Circuit Switch Core Network (CS-CN, voice traffic) and a Packet Switch
Core Network (PS-CN, data traffic).

Figure 1-6 GSM Evolution – UMTS R4, R5, R6, R7
UMTS R4
UMTS R4 does not affect data rates. However, with the introduction of softswitch technology and Bearer
Independent Call Control (BICC), UMTS R4 provides a more efficient core network.
UMTS R5
UMTS R5 and R6 bring about sizeable increases in data rates. UMTS R5 starts the shift to all IP
networking by introducing the IP Multimedia Subsystem (IMS). UMTS R5 also introduces High Speed
Downlink Packet Access (HSDPA) that increases peak downlink throughput to 14.4 Mbps.
UMTS R6
UMTS R6 increases peak uplink speed to 5.76 Mbps with the introduction of High Speed Uplink Packet
Access (HSUPA). UMTS R6 also introduces Multimedia Broadcast Multicast Services (MBMS) that
supports services such as mobile TV.
UMTS R7
UMTS R7 is also known as High Speed Packet Access “plus” (HSPA+). UMTS R7 introduces Multiple
Input Multiple Output (MIMO) antenna systems as well as higher-order modulation schemes. Peak
Data rates in UMTS R7 are 28 Mbps downlink and 11 Mbps uplink. The downlink rate increases in R8
to 42 Mbps.
1-13

How Does LTE Fit into 3GPP Roadmap?
Figure 1-7 How Does LTE Fit into 3GPP Roadmap?
LTE can evolve directly from a GPRS/EDGE network without having to go through the UMTS releases.
If the UMTS path was followed, LTE can evolve directly from UMTS R5/R6 or UMTS R7.
GSM – The Starting Point
Figure 1-8 GSM – The Starting Point
The GSM network is characterized by a 200 kHz air interface, and a Circuit Switched (CS) domain for
digital voice/signaling as well as SMS.

GPRS/EDGE
Figure 1-9 GPRS/EDGE
GPRS introduces a new domain, the Packet Switched (PS) domain. While the PS domain shares the
Radio Access Network (RAN) with the CS domain, all data traffic now goes through the PS domain
while all voice traffic (and SMS) goes through the CS domain.
EDGE DOES NOT introduce any changes to the network other than coding and modulation
enhancements to the air interface to increase data speed.
UMTS R99
Figure 1-10 UMTS R99
UMTS R99 is the first release of UMTS. There are a couple of major changes in UMTS R99.
The Air Interface changes from Time Division Multiple Access (TDMA) using 200 kHz bandwidth to
Wideband Code Division Multiple Access (WCDMA) using 5 MHz bandwidth.
Also, the BTS and BSC are now replaced by the NodeB and Radio Network Controller (RNC).
1-15

UMTSR4
Figure 1-11 UMTS R4
UMTS R4 provides a more efficient network with the addition of the Softswitch (MSC Server/Media
Gateways) in the CS Domain and Bearer Independent Call Control (BICC).
UMTS R5
Figure 1-12 UMTS R5
UMTS R5 introduces big changes to the UMTS network.
1. Starts the shift to an all IP network with the introduction of the IP Multimedia Subsystem (IMS).
2. The Circuit Switch Domain is “collapsed” moving the Softswitch and telephony functions into the
IMS cloud.
3.

Changes the UE functionality enabling it to setup multimedia calls using the IETF’s Session Initiation
Protocol (SIP).
The IP Multimedia Subsystem replaces the call control and interworking functions of the circuit
switched domain with a more flexible, packet-based, multimedia core service architecture. Although
originally defined by the 3GPP for UMTS networks, IMS has been adopted as the core multimedia
service architecture for CDMA, packet cable, DSL, and WiFi access networks.
IMS allows new services to be rapidly and cheaply deployed.
UMTS R6
Figure 1-13 UMTS R6
Along with increasing peak uplink data speed to 5.76 Mbps, UMTS R6 introduces Multimedia Broadcast
Multicast Service (MBMS). MBMS offers broadcast and/or multicast, unidirectional, point-to-multipoint,
multimedia flows.
Broadcast and multicast are two completely different services. A broadcast service is transmitted to all
user devices which have the service activated in their equipment. A service provider does not attempt
to charge for or limit the broadcast transmission.
In contrast, a multicast service is subscription-based. A UE must have subscribed to the service and
explicitly joined the multicast group to receive the multicast transmission. A service provider may track,
control, and charge for the multicast transmission.
1-17

UMTS R7
Figure 1-14 UMTS R7
Along with enhancing IMS, UMTS R7 introduces higher-order modulation techniques (DL 64QAM, UL
16QAM) and Multiple Input Multiple Output (MIMO) antenna technology. These enhancements can
increase uplink speeds to 11.5 Mbps uplink and 42 Mbps downlink.
UMTS R8
Figure 1-15
UMTS Release 8 introduced the Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
and the Evolved Packet Core (EPC).
To reduce latency, the E-UTRAN collapsed the UMTS NodeB and RNC functionality into the evolved
NodeB (eNodeB). In addition to 5 MHz, the E-UTRAN radio access network supports 1.4, 3, 10, 15, and
20 MHz channels.
R8 with 2x2 MIMO and 64QAM modulation increases UL speeds to 23 Mbps, and DL speeds to 42 Mbps.
In the Evolved Packet Core (EPC), the SGSN and GGSN are replaced by the Serving Gateway (S-GW)
and Packet Data Network Gateway (P-GW). The Mobility Management Entity (MME) manages UE
mobility and paging functions.

3GPP Release 8 Network Architecture (LTE) Version 3 Rev 1
3GPP Release 8 Network Architecture (LTE)
Figure 1-16 3GPP Release 8 Network Architecture (LTE)
LTE introduces new terminology to describe the architecture. The Evolved Universal Terrestrial Radio
Access Network (E-UTRAN) consists of the User Equipment (UE), Evolved Node B (eNodeB), and
their associated interfaces. The E-UTRAN is also known as Long Term Evolution (LTE).
The Evolved Packet Core (EPC) is an all-IP, packet-switched core network consisting of:
• Mobility Management Entity (MME) – key control node for the LTE access network
• Serving Gateway (S-GW) – routes and forwards data packets
• Packet Data Network Gateway (P-GW) – provides connectivity to external packet data networks
The EPC is also known as System Architecture Evolution (SAE). The goal of the SAE is to create an
evolutionary framework which supports higher data rates, lower latency, packet optimized systems using
multiple Radio Access Technologies (RATs).
NOTE
EPC network elements will be discussed in greater detail in Lesson 2.
1-19

Version 3 Rev 1 E-EUTRAN Air Interface
E-EUTRAN Air Interface
Figure 1-17 E-EUTRAN Air Interface
The key air interface changes for E-UTRAN are Orthogonal Frequency Division Multiplexing (OFDM)
and the use of Multiple Input Multiple Output (MIMO) antennas.
The LTE air interface utilizes Orthogonal Frequency Division Multiple Access (OFDMA) in the
downlink and Single Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink. It also
supports both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) schemes.
Multiple Input Multiple Output (MIMO) antenna systems are also now fully employed. MIMO uses
multiple antennas at both the transmitter and receiver, improving the network efficiency.
NOTE
OFDMA, SC-FDMA, TDD, FDD, and MIMO will be discussed in greater detail in Lesson 3.

Performance Goals for LTE Version 3 Rev 1
Performance Goals for LTE
Figure 1-18 Performance Goals for LTE – Spectrum
The 3GPP working group established several goals for LTE:
• Provide the user with the services they desire
• Provide the network operators with low cost per bit, higher capacity, and flexible architecture they
will want to deploy
Spectrum Flexibility
The LTE air interface operates in 1.4, 3, 5, 10, 15, and 20 MHz spectrum allocations in both uplink and
downlink, paired and unpaired.
1-21

Version 3 Rev 1 Performance Goals for LTE
Spectrum Efficiency
Spectrum efficiency is the amount of bits of data that are able to be transmitted per 1 hertz
(bits/sec/Hz/site). The more bits, in less bandwidth, equals less cost. In a loaded network, the downlink
target is 3-4 times R6 HSDPA while the uplink target is 2-3 times R6 Enhanced Uplink.
Figure 1-19 Performance Goals for LTE – Throughput/Data Rates
Increased Peak Data Rates
Within a 20 MHz spectrum, LTE supports theoretical instantaneous peak data rates of 100 Mbps downlink
(5bps/Hz) and 50 Mbps uplink (2.5bps/Hz).

Performance Goals for LTE Version 3 Rev 1
Increased User Throughput
The target for downlink average user throughput per MHz is 3-4 times R6 HSDPA while the uplink target
is 2-3 times R6 Enhanced Uplink. This equates to greater than 10 Mbs downlink and greater than 5
Mbps uplink.
Figure 1-20 Performance Goals for LTE – Latency
Control Plane Latency
Control plane latency is the transition time from different connection modes, e.g. from idle or dormant
states to the active state. From an idle state to an active state, transition time is less than 100ms. From
a dormant state to an active state, transition time is less than 50ms.
1-23

Version 3 Rev 1 Performance Goals for LTE
User Plane Latency
User Plane Latency is the one-way transit time of a packet between the user equipment and the radio
access network (and vice versa). In an LTE network, user plane latency is less than 5ms in an unloaded
condition for small IP packet (single user with single data stream, 0 byte payload + IP headers).
Figure 1-21 Performance Goals for LTE – Capacity, Mobility, Cell Coverage
Capacity
At least 200 users per cell will be supported (5 MHz). For larger spectrum allocations, up to 400 users
may be supported.
Mobility
Full 3GPP mobility will be supported and optimized for 0-15 km/h (~9 mph). Speeds from 15-120 km/h
(~9-75 mph) will also be supported with high performance. Mobility will be maintained for speeds of
120-350 km/h (~217 mph).
Cell Coverage
Throughput, spectral efficiencies, and mobility will be met for cell ranges up to 5 km (~3 miles). For cell
ranges up to 30 km (~18 miles), mobility will be maintained but degradation in throughput and spectral
efficiency is permitted. Cell ranges up to 100 km (~62 miles) are supported…degradation is accepted.

Lesson 1 Summary Version 3 Rev 1
Lesson 1 Summary
In this lesson you learned about:
• The key drivers for Long Term Evolution (LTE)
• The Standards Body – 3GPP – that established the goals for LTE
• The GSM network evolutions and the upgrade path to LTE
• The Performance Goals for LTE
• The changes to the current 3G architecture brought about by LTE
• The 3GPP Release 8 (LTE) Network Architecture
1-25

Version 3 Rev 1 Memory Points
Memory Points
Take a few minutes to recall key points that you may use in the
near future or that may address a current need. This is also a
good opportunity to jot down a question. If the debriefing of key
points does not address your question, ask it during this exercise
or during a break period. Be prepared to share a key point or
question with others in the class
Key Point – Something New:
Key Point – Something Forgotten, but Relearned:
Question on what was just covered:

Lesson 2: LTE Network Architecture Version 3 Rev 1
Chapter 2
Lesson 2: LTE Network Architecture
In this lesson, we will discuss the network elements that comprise the LTE network; the Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) and the Evolved Packet Core (EPC). We will then look at
Motorola’s LTE solution.
2-1

Version 3 Rev 1 Lesson 2: LTE Network Architecture

Objectives Version 3 Rev 1
Objectives
At the completion of this lesson, you’ll be able to:
• State the functional blocks that comprise an LTE network
• Explain the function of the network elements that comprise the Evolved Universal Terrestrial
Radio Access Network (E-UTRAN)
• Explain the function of the network elements that comprise the Evolved Packet Core (EPC)
• Describe Motorola’s LTE network architecture
2-3

Version 3 Rev 1 3GPP Release 8 Network Architecture (LTE)
Figure 2-1 3GPP Release 8 Network Architecture (LTE)
As we discussed in Lesson 1, the Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
and Evolved Packet Core (EPC) make-up the overall LTE architecture. In Lesson 2, we will discuss the
network elements that comprise the E-UTRAN and EPC.
The graphic above illustrates the E-UTRAN and EPC architecture we will discuss, in its
simplest form.
After we have discussed the function of each of the network elements in the graphic, we
will expand and explain the “rest” of the system.

evolved Node B (eNodeB)
Figure 2-2 eNodeB
The eNodeB is responsible for the following functions:
• Radio Resource Management (RRM) – assignment, reassignment, and release of radio resources
• Header compression and encryption of user data streams
• Routing user plane data to S-GW
• Scheduling and transmission of paging messages received from the MME
• Scheduling and transmission of broadcast information received from the MME or configured from
the Element Manager
• Measurement gathering for use in scheduling and mobility decisions
• Radio Protocol Support
• Transfer of Non-Access Stratum (NAS) signaling
• Access Stratum (AS) Signalling
• SAE (EPC) Bearer activation/deactivation
• Lawful Intercept
• MME selection for handovers with MME change
2-5

User Entity (UE)
Figure 2-3 User Entity
The User Equipment (UE) must perform the following functions:
• Signal network entry and other state changes
• Report its Tracking Area location while in idle mode
• Request UL grants to transmit data while in active mode
• Act as PDCP, RLC, MAC, and PHY “client”. The eNodeB controls the air interface and all DL and
UL scheduling. The UE reacts to instructions from the eNodeB.
LTE
300
Telecoms
3GPP TS 36.101 User Equipment (UE) Radio Transmission and Reception

Mobility Management Entity (MME)
Figure 2-4 Mobility Management Entity (MME)
The MME helps authenticate UEs onto the system, tracks active and idle UEs, and pages UEs when
triggered by the arrival of new data.
When a UE attaches to an eNodeB, the eNodeB selects an MME. The MME in turn selects the Serving
Gateway (S-GW) and the Packet Data Network Gateway (P-GW) that will handle the user’s bearer
packets.
Other MME functions include:
• Non-Access Stratum (NAS) signaling
• Authentication (in conjunction with the Home Subscriber Server - HSS)
• Idle State Mobility Handling
• SAE (EPC) Bearer Control
• Lawful Intercept
2-7

Serving Gateway (S-GW)
Figure 2-5 Serving Gateway (S-GW)
The S-GW routes and forwards user data packets, terminates downlink data for idle UEs, and is also the
local mobility anchor for inter-eNodeB handovers. The mobility anchor function applies to both a UE in
the E-UTRAN and other 2G/3G technologies. The S-GW also maintains a buffer for each idle UE and
holds the packets until the UE is paged and an RF channel is re-established. For each UE associated
with the EPC, at a given point of time, there is a single S-GW.
Other S-GW functions include:
• Policy enforcement point
• IP backhaul admission control
• IP backhaul congestion control
• IP backhaul QoS
• Core IP QoS
• Billing records
• Lawful intercept
• Call trace

Packet Data Network Gateway (P-GW)
Figure 2-6 Packet Data Network Gateway (P-GW
The P-GW is responsible for the UE IP address assignment and provides UE connectivity to the external
packet data networks (operator’s network and Internet). The P-GW provides charging (billing) support,
packet filtering/screening, policy enforcement, and lawful intercept. If a UE is accessing multiple packet
data networks, it may have connectivity to more than one P-GW.
Other P-GW functions include:
• Mobile IP / Proxy Mobile IP (MIP/PMIP) anchor point across E-UTRAN and non 3GPP
technologies (i.e. WiMAX, 3GPP2, WiFi, etc.)
• DHCP server and client
• Transport level packet marking in uplink and downlink
• Transfer of QoS policy and charging rules from Policy and Charging Rules Function (PCRF) to
the Policy and Charging Enforcement Function (PCEF) within the P-GW
• UL and DL bearer binding
• UL bearer binding verification
2-9

Other EPC Network Elements
Figure 2-7 Other EPC Network Elements
Home Subscriber Server (HSS)
The HSS is the master database that contains the UE profiles and authentication data used by the MME
for authenticating and authorizing UEs. It also stores the location information of the UE which is used for
user mobility and inter-technology handovers (similar to the GSM HLR/VLR). The HSS communicates
with the MME using Diameter protocol.
Policy and Charging Rules Function (PCRF)
The PCRF creates rules for setting policy and charging rules for the UE. It provides network control for
service data flow detection, gating, QoS authorization and flow based charging.
• Applies the security procedures, as required by the operator, before accepting service information
• Decides how a certain service data flow will be treated in the P-GW and ensures that the P-GW
user plane traffic mapping and treatment matches the user’s subscription profile
• Provides the S-GW with QoS policy and traffic flow mapping information
Packet Lawful Intercept Gateway (P-LIG)
The P-LIG provides the interface between the LTE access network and Law Enforcement Agencies
(LEAs), enabling the LEAs to intercept UE communications carried by a carrier.

Interworking with Other Technologies
Figure 2-8 Interworking with Trusted 3GPP and non-3GPP Networks
Serving GPRS Support Node (SGSN)
In 2G and 3G systems, the Serving GPRS Support Node (SGSN) is responsible for the delivery of
data packets to and from UEs within its geographical service area. The SGSN provides the interfaces
between the MME and S-GW in the EPC.
Trusted Non-3GPP Access
“Non-3GPP IP Access” describes access to the EPC by technologies not defined by 3GPP. Non-3GPP
access technologies include WiFi, WiMAX, fixed access such as cable or DSL, and so on. System
Architecture Evolution (SAE) describes trusted and untrusted non-3GPP IP access.
The individual carrier must decide if a non-3GPP network is trusted or untrusted. This is a business
decision and does not depend on the access network technology.
2-11

Figure 2-9 Interworking with Untrusted non-3GPP Networks
evolved Packet Data Gateway (ePDG)
The evolved Packet Data Gateway (ePDG) connects the LTE network to an untrusted, non-3GPP
network. To access the LTE network, the non-3GPP subscriber must establish an IP Security (IPSec)
tunnel via the ePDG.
The ePDG is the encapsulation/decapsulation point for Mobile IP/Proxy Mobile IP (MIP/PMIP). The
ePDG also authenticates, authorizes, and enforces QoS policies in conjunction with the 3GPP AAA
server.
3GPP AAA Server
The 3GPP AAA server provides Authentication, Authorization, and Accounting (AAA)services for
untrusted, non-3GPP IP access.

eNodeB Reference Points
Figure 2-10 eNodeB Reference Points
• S1-MME – Carries control plane traffic between E-UTRAN and MME.
• S1-U - Carries bearer plane traffic between the eNodeB and S-GW.
• S5 – Carries control and bearer traffic between an S-GW and P-GW located in the same network.
• S6a - Carries context and other information between the HSS and MME.
• S8 – Carries control and bearer traffic between an S-GW and P-GW located in different networks.
• S10 - Carries context and other information between MMEs.
• S11 – Carries control traffic between MME and the S-GW for session management functions.
• SGi – Carries bearer information between the P-GW and the external data network.
• Uu - Air interface from eNodeB to UE.
• X2 - Connects eNodeBs. The X2 is used for mobility control, bearer forwarding, and load
management.
2-13

Version 3 Rev 1 Motorola LTE Architecture
Motorola LTE Architecture
Figure 2-11 Motorola LTE Architecture
In this section, we will discuss the platforms used for the Motorola suggested minimum offering; the
eNodeB; the Wireless Broadband Controller (WBC) 700 MME, the Wireless Broadband Controller
(WBC) 700 S-GW and P-GW, and the Wireless Broadband Manager (WBM) 700.
This section will give you a general idea of Motorola’s solution for each of the
LTE Network Elements.

Motorola LTE Architecture Version 3 Rev 1
eNodeB
Figure 2-12 eNodeB Types
Motorola’s eNodeB consists of a site control / baseband chassis and a radio unit. The control / baseband
chassis leverages the BCUII platform from the WiMAX Access Point (AP).
The eNodeB comes in two different configurations:
• Traditional Frame where all equipment is co-located in a 19”, indoor frame configuration
• Remote Radio Head where the transceiver and Power Amplifier (PA) are mounted on the roof, wall,
or pole, and the baseband controller is mounted at the bottom of the tower (enclosed) or mounted
indoors in a 19” rack.
2-15

Wireless Broadband Controller (WBC) 700
Figure 2-13 Wireless Broadband Controller (WBC) 700
Motorola’s Wireless Broadband Controller (WBC) 700 performs the functions of the MME. It leverages
the WiMAX Carrier Access Point Controller (CAPC) hardware.
Subscriber Capacity
• Coverage Only Model: 8 Million UEs
• Dense Urban or Rural Model: 4 Million UEs
• Regional or High Mobility Model: 2 Million UEs
Each MME Supports
• Up to 8192 eNodeBs
• Up to 32 MMEs per MME pool
• Up to 8000 Tracking Areas (per MME Pool)
• Simultaneous communication to 128 MMEs, however the number of MMEs which can be connected
dynamically is unlimited
• Up to 128 S-GW Service Areas
• Up to 51 eNodeBs per Tracking Area
• Up to 64 HSSs
• 2 AAAs

Wireless Broadband Controller (WBC) 700 as S-GW
Figure 2-14 WBC 700 as S-GW
Motorola’s Wireless Broadband Core (WBC) 700 performs the functions of the Serving Gateway
(S-GW) and Packet Data Network Gateway (P-GW). The WBC 700 is a carrier-grade, fully redundant
Linux platform that can be employed in several configurations:
• Standalone S-GW or,
• Standalone P-GW or,
• Combined S-GW and P-GW
2-17

Wireless Broadband Core (WBC) 700 as P-GW
Figure 2-15 WBC 700 as P-GW
Wireless Broadband Manager (WBM) 700
Figure 2-16 WBM 700
The Element Management System (EMS) for the eNodeB, WBC 700 MME, WBC 700 S-GW, and WBC
700 P-GW is the WBM 700. The WBM 700 leverages the implementation of the low cost reference
management architecture defined by the Motorola Public Safety team. The platform is comprised of a
collection of Sun T5440 servers to provide the required processing and RAID disk drive array systems
to provide multiple Terabytes of storage capability.
LTE 1.0 employs one Sun Microsystems T5440 server with no RAID
solution.

WBM 700 Features
Figure 2-17 WBM 700 Features
2-19

GSM to LTE Migration/Overlay
Figure 2-18 GSM to LTE Migration
For operators with installed GSM infrastructure, Motorola plans to provide a migration path based on the
Motorola GSM Horizon II BTS to support both GSM and LTE access functionality in a single base station.
The Horizon II operating in the 900/1800 band supports a smooth migration to LTE. For operators with
additional spectrum, Motorola can also provide a complete LTE overlay network to work in conjunction
with the installed GSM base.
A migration to LTE in the 900/1800 band would entail:
• Hardware upgrade of the radio modem by adding the rack mounted LTE BCU
• Firmware upgrade to the radio PA
• Provision of an IP connection from the radio modem to link into the Evolved Packet Core (EPC)
• No changes to feeders, antennas or other site ancillary equipment
• No other changes to BTS cabinet (apart from LTE BCU)
Figure 2-19 GSM to LTE Overlay

CDMA LTE Overlay
Motorola will offer the ability to add LTE via a modular expansion of installed 1X or DO Universal Base
Station (UBS), regardless of band. Initially both the user interface and backhaul will remain common.
Motorola’s solution will enable combining onto existing antennas for use on an existing band or adding
a separate band within the same frame.
The above illustration shows the upgrade path – adding LTE in a separate band to an existing UBS frame.
Figure 2-20 CDMA LTE Overlay
The Motorola LTE eNodeB will also support site co-location with non-Motorola equipment in an “overlay”
solution.
The migration of 3GPP2 service providers to E-UTRAN/EPC involves the overlay of the EPC network
elements and the potential to use the EV-DO BTS frame to deploy both the baseband and radio head
E-UTRAN components (as discussed on the previous page).
2-21

CDMA Evolution
CDMA2000 technical specifications are established by the 3rd Generation Partnership Project 2
(3GPP2). 3GPP2 was set up in late 1998 to create globally applicable specifications for CDMA 3G
mobile phone systems. 3GPP2 working groups and standards are found at www.3gpp2.org.
CDMAOne
Introduced in 1993, CDMAOne was based on the IS-95 standard. Like its counterpart GSM, CDMAOne
is a voice and low speed circuit switched data network that provides circuit switched data rates of 14.4
kbps.
CDMA2000 1x
Similar to GPRS, CDMA2000 added packet switching to CDMAOne. The packet switching network
initially supported peak data rates of 153 kbps in both downlink and uplink. 1x refers to the number of
CDMA 1.25 MHz channels
CDMA 1x EV-DO Rev 0 (Evolution-Data Optimized Revision 0)
CDMA 1x EV-DO Rev 0 improved packet data throughput to 2.4 Mbps downlink and 153 kbps uplink for
FDD operation. In commercial networks, Rev 0 supports an average 300-700 kbps downlink and 70-90
kbps uplink. The UL rate does not provide adequate bandwidth for real-time services. The packet data
network provides an “always-on” IP service.
CDMA 1x EV-DO Rev A (Evolution-Data Optimized Revision A)
CDMA 1x EV-DO Rev A increased the downlink data rate to 3.1 Mbps and the uplink data rate to 1.8
Mbps. In commercial networks, Rev A supports an average 450-800 kbps downlink and 300-400 kbps
uplink. The improved UL bandwidth and low average latency (50 ms) allow Rev A to support real-time
services. Rev A is an all-IP service, supporting Voice over IP (VoIP).

CDMA 1x EV-DO Rev B (Evolution-Data Optimized Revision B)
Rev B aggregates multiple Rev A 1x channels into a high performance broadband service. For example,
15x (20 MHz) service supports 46.5 Mbps downlink and 27 Mbps uplink. Rev B also incorporates
Orthogonal Frequency Division Multiplexing (OFDM) and Multiple In Multiple Out (MIMO) in the
air interface.
UMB (Ultra Mobile Broadband)
Ultra Mobile Broadband was intended as the next evolutionary step beyond Rev B, incorporating
improved MIMO performance and so on. After Qualcomm dropped support for UMB, this step is
essentially dead.
2-23

Version 3 Rev 1 Self-Organizing Network (SON)
Self-Organizing Network (SON)
SON Definition
A self-organizing network is a network that can automatically extend, change, configure, and optimize
its topology, coverage, capacity, cell size, and channel allocation based on changes in location, traffic
pattern, interference, and the situation/environment.
• Purpose
– Reduce operational costs
• Focus Areas
– Self-installation and self-configuration
– Self-operating
– Self-optimization
– Operator controls the behavior of the SON instead of controlling detail and fixed parameters
◊ The operator provides boundaries for neighbor auto-discovery by controlling which
neighbor must be included or not included, and allowing the system to discover the rest
Self-configuring, self-optimizing wireless networks concepts are not new. As operators and standards
bodies move towards next generation networks, the ability to automate network management has
become an important requirement.
The objective is to minimize the cost of running a network by eliminating manual configuration – using
expensive dedicated resources – of equipment at the time of deployment as well as dynamically
optimizing radio network performance during operation.
Motorola SON Architecture
Figure 2-21 Motorola SON Architecture
The Motorola SON architecture places little responsibility of the SON functionality at the EMS layer. This
design when combined with the intelligence and autonomous nature of the Motorola NE’s, creates an
EMS layer upon which there is little dependence for vital, daily operations. The Motorola LTEManager
provides support for operators related to the networks SON functions such as, SON enable/disable

Self-Organizing Network (SON) Version 3 Rev 1
Self-Organizing Network (SON)
controls, verification of SON optimization recommendations (establishing trust), and full tracking
of all manual and automated configuration changes. The LTEManager also provides NE software
management including automated software upgrade and activation. The Motorola SON architecture
also provides for a centralized SON function to support optimization and configuration capabilities
required which span across the network or multiple NE types.
Proposed Motorola SON Features
Basic Auto Operations
{ Autonomous Inventory, auto detection, test and configuration of hardware on insert
¾ Near Real-Time PM reporting
{ Automatic EMS Software Upgrade
{ Automatic NE Software Upgrade
{ Dynamic Configuration of signaling links
¾ Automatic generation of radio, HO configuration parameters
{ Auto Backup and restore
Advanced Auto Operations
¾ Resource outage detection and action, e.g. Sleeping Cell
¾ Outage Compensation
¾ Smart re-configuration
Basic Deployment
{ Auto-detect PnP hardware, auto-authenticate
{ Auto inventory
{ On connection to EMS, auto-software upgrade
{ Auto RF/Transport config update
{ Self discovery of new NE resources
Advanced Deployment
¾ Auto-test NE
¾ Auto-compute antenna loss at eNB
Interference Coordination and Control
¾ Exchange of metrics over X2 interface to enable coordination of determining edge of cell
Physical Radio Resource Blocks
¾ Motorola enhanced Algorithm
Automatic Neighbor Relationships
{ eNB discovers new neighbors (eNB directed UE measurements), deletes stale neighbors
{ Operator control of on-demand, periodic, white/black list
{ Dynamic configuration of X2 signaling link
Subscriber Trace Support
{ NE support for trace on per-subscriber identity (IMSI) and per-equipment identity (IMEI) basis
2-25

Version 3 Rev 1 Lesson 2 Summary
Lesson 2 Summary
In this lesson you learned about:
• The function of the eNodeB
• The functions of the Network Elements in the Evolved Packet Core (EPC); MME, S-GW, P-GW
• Traffic Areas and Pooling (MME and S-GW) concepts
• How LTE interworks with other technologies
• Motorola’s LTE architecture
• Motorola’s migration paths from GSM/CDMA to LTE

Memory Points Version 3 Rev 1
Memory Points
Take a few minutes to recall key points that you may use in the
near future or that may address a current need. This is also a
good opportunity to jot down a question. If the debriefing of key
points does not address your question, ask it during this exercise
or during a break period. Be prepared to share a key point or
question with others in the class
Key Point – Something New:
Key Point – Something Forgotten, but Relearned:
Question on what was just covered:
2-27

Version 3 Rev 1 Memory Points

Lesson 3: LTE Air Interface Version 3 Rev 1
Chapter 3
Lesson 3: LTE Air Interface
In this lesson, we will discuss LTE Radio Frequency parameters, OFDM concepts, LTE Frame structure, OFDMA
and SC-FDMA operation, modulation and coding schemes, and LTE antenna systems.
3-1

Version 3 Rev 1 Lesson 3: LTE Air Interface

Objectives Version 3 Rev 1
Objectives
At the completion of this lesson, you will be able to:
• State the operating frequencies used by the LTE air interface
• Describe OFDM subcarrier and symbol characteristics
• Describe LTE duplexing and framing methods
• List the modulation techniques used by the LTE air interface
• Compare OFDMA and SC-FDMA usage in LTE
• Describe LTE antenna systems
LTE
300
Telecoms
3GPP TS 36.201; LTE Physical Layer, General Description
3GPP TS 36.211; Physical Channels and Modulation
3GPP TS 36.212; Multiplexing and Channel Coding
3GPP TS 36.213; Physical Layer Procedures
3GPP TS 36.214; Physical Layer Measurements
3-3

Version 3 Rev 1 Radio Frequency Parameters
Radio Frequency Parameters
LTE Spectrum
Figure 3-1 LTE Spectrum
In addition to new RF bands, LTE reuses the cellular IMT-2000 spectrum. Because the initial focus is on
Frequency Division Duplexing (FDD) operation, LTE needs paired spectrum. An important objective
for LTE is RF band coordination to facilitate roaming across each of the global regions.
Channel Bandwidth
Figure 3-2 Channel Bandwidth

Radio Frequency Parameters Version 3 Rev 1
Extremely small channel sizes (1.4 and 3 MHz) are useful in the lower RF bands (such as 700 MHz).
Larger channel sizes are more appropriate for the higher and larger RF bands.
3GPP LTE Spectrum
E-EUTRA Frequency Bands and Channel Bandwidth
E-EUTRA
BAND
Uplink (UL) Downlink (DL) Duplex
Mode
Channel BW Supported
1 1920–1980 MHz 2110–2170
MHz
FDD 5, 10, 15, 20 MHz
2 1850–1910 MHz 1930–1990
MHz
FDD 1.4, 3, 5, 10, 15Note1, 20Note1 MHz
3 1710–1785 MHz 1805–1880
MHz
FDD 1.4, 3, 5, 10, 15Note1, 20Note1 MHz
4 1710–1755 MHz 2110–2155
MHz
FDD 1.4, 3, 5, 10, 15, 20 MHz
5 824–849 MHz 869–894 MHz FDD 1.4, 3, 5, 10Note1 MHz
6 830–840 MHz 875–885 MHz FDD 5, 10Note1 MHz
7 2500–2570 MHz 2620–2690
MHz
FDD 5, 10, 15, 20Note1 MHz
8 880–915 MHz 925–960 MHz FDD 1.4, 3, 5, 10Note1 MHz
9 1749.9–1784.9
MHz
1844.9–1879.9
MHz
FDD 5, 10, 15Note1, 20Note1 MHz
10 1710–1770 MHz 2110–2170
MHz
FDD 5, 10, 15, 20 MHz
11 1427.9–1452.9
MHz
1475.9–1500.9
MHz
FDD 5, 10Note1, 15Note1, 20Note1 MHz
12 698–716 MHz 728–746 MHz FDD 1.4, 3, 5Note1, 10Note1 MHz
...
...
33 1900–1920 MHz TDD 5, 10, 15, 20 MHz
34 2010–2025 MHz TDD 5, 10, 15 MHz
35 1850–1910 MHz TDD 1.4, 3, 5, 10, 15, 20 MHz
36 1930–1990 MHz TDD 1.4, 3, 5, 10, 15, 20 MHz
37 1910–1930 MHz TDD 5, 10, 15, 20 MHz
38 2570–2620 MHz TDD 5, 10 MHz
39 1880–1920 MHz TDD 5, 10, 15, 20 MHz
40 2300–2400 MHz TDD 10, 15, 20 MHz
Note1: The UE receiver sensitivity may be relaxed when operating at this channel bandwidth.
3-5

Version 3 Rev 1 Radio Frequency Parameters
E-UTRA is designed to operate in the RF bands listed above.
LTE
300
Telecoms
3GPP TS 36.101 E-UTRA UE Radio Transmission and Reception
Channel Sampling Frequency
Figure 3-3
What is the “actual” channel bandwidth? We must “over-sample” the nominal channel bandwidth to
account for guard bands and orthogonal spacing of subcarriers. The resulting channel bandwidth is
called the Sampling Frequency (SF).
The table shows the Sampling Frequency for each supported channel size. We will use FS to calculate
subcarrier spacing.
Sampling Frequencies
Nominal Channel Bandwidth
Parameters 1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
Sampling Freq
(Fs)
1.92 MHz 3.84 MHz 7.68 MHz 15.36 MHz 23.04 MHz 30.72 MHz

Orthogonal Frequency Division Multiplexing (OFDM) Version 3 Rev 1
Orthogonal Frequency Division Multiplexing (OFDM)
Figure 3-4 Orthogonal Frequency Division Multiplexing (OFDM)
Orthogonal Frequency Division Multiplexing (OFDM) divides the channel bandwidth into lower
bandwidth subcarriers. Each subcarrier uses a different, equally-spaced center frequency to carry
modulated data or reference signals.
All data subcarriers may be modulated for simultaneous transmission during a time interval called the
symbol time.
Orthogonal Frequency Division Multiple Access (OFDMA) and Single Carrier Frequency Division
Multiple Access (SC-FDMA) add multiple access techniques to OFDM. We will discuss OFDMA and
SC-FDMA later in this lesson.
3-7

Version 3 Rev 1 Orthogonal Frequency Division Multiplexing (OFDM)
Non-Orthogonal Subcarriers
Figure 3-5 Non-Orthogonal Subcarriers
OFDM divides the channel into lower-bandwidth, non-interfering subcarriers.
Without OFDM, the sidebands and harmonics of a frequency would interfere with adjacent frequencies.
The traditional solution is to insert guard bands between the frequencies. The graphic shows
non-orthogonal frequencies; that is, the sidebands of the frequencies interfere with each other.

Orthogonal Frequencies
Figure 3-6 Orthogonal Frequencies
In OFDM the channel is divided into many equally-spaced, lower-bandwidth subcarriers. Orthogonal
frequencies are designed (spaced) so they don’t interfere with each other, and don’t require guard bands
between subcarriers.
Do you see that the sidebands for frequencies f1 and f3 are null at frequency f2? If a receiver samples
an orthogonal subcarrier at precisely the correct (center) frequency, there is no inter-carrier interference
from the adjacent subcarriers.
OFDM Signal Requirements
• An integer number of cycles during an OFDM symbol
• An integer number of Hz separating the subcarriers
• No phase or amplitude changes may occur during the OFDM symbol
3-9

Subcarrier Transmitter Operation
Figure 3-7 Subcarrier Transmitter Operation
Imagine that every subcarrier is associated with a separate modem, and each “modem” operates at
a different center frequency. Each subcarrier modulates some number of bits (called a symbol), and
transmits the modulated signal simultaneously during a time interval called the symbol time.
This example shows blocks of 4 bits modulated by each subcarrier, or 16QAM
modulation. As we will see, groups of subcarriers may use different modulation and
coding schemes during the same symbol time.

Subcarrier Receiver Operation
Figure 3-8 Subcarrier Receiver Operation
At the receiver, each subcarrier receives the modulated signal at its specific frequency, demodulates the
signal into bits, and restores the original bit pattern.
Fast Fourier Transform (FFT)
Figure 3-9 IFFT Operation
We don’t actually have hundreds or thousands of modems in each eNodeB or UE. Instead, a single
modem performs the functions we saw on the previous pages using special algorithms called Fast
Fourier Transforms (FFT).
3-11

A Fourier Transform converts signals between the time and frequency domains. The transmitter modem
performs Inverse Fast Fourier Transforms (IFFT) to convert the modulated signals to a single summed
output.
From a transmitted power and radio frequency perspective, a single modem performing
IFFT looks exactly like individual “mini-modems” (1 per subcarrier). For example,
IFFT for 512 subcarriers generates the same output as 512 individual modems (1
per subcarrier).
FFT Operation
Figure 3-10 FFT Operation
The receiving modem uses FFT processing to convert the received signal back to its constituent
modulated signals. Demodulation converts the modulated signals back to bits.
FFT Algorithm Requirements
• An integer number of cycles during an OFDM symbol
• An integer number of Hz separating the subcarriers
• No phase or amplitude changes may occur during the OFDM symbol
The term FFT is used interchangeably with the total number of subcarriers.

Scalable OFDM
Figure 3-11 Scalable OFDM
Scalable OFDM uses different numbers of subcarriers based on the channel size. For example, a 1.4
MHz channel is divided into 128 subcarriers (128 FFT), while a 10 MHz channel uses 1024 subcarriers
(1024 FFT). The OFDM subcarrier spacing and symbol characteristics are identical; only the FFT size
and channel bandwidth vary.
The table below shows the number of FFT (subcarriers) for each channel size.
FFT and Channel Bandwidth
Sampling
Freq (Fs)
NFFT 128 256 512 1024 1536 2048
3-13

Subcarrier Spacing
Figure 3-12 Subcarrier Spacing
How “big” is a subcarrier? Because the subcarrier center frequencies are equally spaced across the
channel bandwidth, we can calculate the subcarrier spacing (Δf) by dividing the Sampling Frequency
(FS) by the number of subcarriers
Δf = FS/NFFT
Calculating Subcarrier Spacing
Sampling
Freq (Fs)
NFFT 128 256 512 1024 1536 2048
Subcarrier
Spacing (Δf)
For multimedia broadcast/multicast (MBMS) traffic, LTE uses 7.5 kHz subcarrier
spacing.

Symbol Time
Figure 3-13 Symbol Time vs. Subcarriers
The symbol time is the time interval used across all the subcarriers for simultaneous operation and
modulation. A symbol represents one encoded/modulated block of bits, based on the modulation and
coding scheme selected for each group of subcarriers. During a symbol time, data subcarriers may carry
modulated bits, while reference subcarriers carry signals used to estimate channel quality.
The symbol time is the inverse of the subcarrier spacing (1/ Δf). For LTE 15 kHz subcarriers, each symbol
time is 66.67 microseconds long. MBMS 7.5 kHz subcarriers use 133 microsecond symbols.
OFDM combines many symbol times into fixed-length, time-dependent Physical Layer
frames. For LTE, a frame is exactly 10 milliseconds long. We will talk about the frame
structure later in this lesson.
3-15

Multipath Delay and Inter-Symbol Interference
Figure 3-14 Multipath Delay and Inter-Symbol Interference
How do we account for multipath delay? The graphic illustrates what happens to traffic between the
eNodeB and the UE. Symbol 1 is radiated out of the eNodeB, and arrives at the UE over the shortest
path, path A. However, the same symbol also arrives over paths B, C and D. If we transmit symbol 2
immediately after symbol 1, the delayed symbols 1B, 1C and 1D will interfere with symbol 2.
We need a guard interval between the symbols to protect against inter-symbol interference. The guard
interval must be large enough to account for “normal” delay in the cell, e.g., the RMS (Root, Mean,
Square) delay spread.
Another way of looking at multipath is linear path distance. Free space propagation delay is about 1
nanosecond per foot or 3.3 microseconds per kilometer. The guard interval must handle (account for)
multipath delay based on the cell radius.

Cyclic Prefix
Figure 3-15 Cyclic Prefix
The Cyclic Prefix or TCP accounts for the multipath delay (distance) as described on the preceding page.
The guard interval itself contains a copy of the signals from the end of the symbol time. The Cyclic Prefix
process captures the signals from the end of the symbol time and copies them to the guard interval in
front of the symbol.
The Cyclic Prefix guarantees a whole number of Hz per symbol time and no phase or amplitude changes
during the extended symbol time (requirements of FFT).
LTE defines two TCP sizes, normal (4.67 microseconds) and extended (16.67
microseconds).
3-17

Subcarrier Types
Figure 3-16 Subcarrier Types
The DC and Guard Subcarriers are not used to carry data or reference information;
they are set to null (unpowered).
DC Subcarrier
• DC Subcarrier = Subcarrier associated with the channel center frequency
• DC Subcarrier is not used
• If used, this subcarrier would be contaminated in the receiver by any DC leakage current
Guard Subcarriers
• Used to eliminate inter-channel interference
• Guard Subcarriers are null (unpowered)
How can we avoid Inter-Channel Interference (ICI) between the cells (sectors) or networks? OFDM
requires guard subcarriers at each end of the channel frequency range to avoid interference with other
channels. Guard subcarriers are null (unpowered).
Data Subcarriers
• Carry user data
• Carry messages which control the Physical Layer
• Modulated based on signal quality (SNR)
Data subcarriers contain modulated data bits. In the next lesson, we will see that LTE is
connection-oriented. For now, groups of data subcarriers are temporarily scheduled to carry user or
control connection packets.
Reference Signals
• Used to estimate signal quality
• Distributed across the subcarriers

Occupied Subcarriers
Figure 3-17 Occupied Subcarriers
Occupied Subcarriers
Sampling
Freq (Fs)
NFFT 128 256 512 1024 1536 2048
Subcarrier
Spacing (Δf)
Occupied
Subcarriers
72 180 300 600 900 1200
3-19

Version 3 Rev 1 LTE Frame Structure
LTE Frame Structure
Figure 3-18 LTE Frame
Think of a frame as a matrix of subcarriers and symbol times. The frequency domain (vertical axis)
consists of subcarriers, while the time domain (horizontal axis) consists of symbol times.
An LTE frame is always exactly 10 milliseconds long. This applies to both FDD and TDD configurations
for Frame Type 1 or 2.
Calculating the Frame Rate
1. Assuming 10 ms per frame, how many LTE frames are transmitted per second?

LTE Frame Structure Version 3 Rev 1
LTE Frame Structure
LTE Frame Length and Subcarriers
Figure 3-19 LTE Frame Length and Subcarriers
This graphic shows the impact of channel bandwidth over a frame time. The vertical dimension shows
the number of subcarriers (FFT), while the horizontal dimension shows the 10 millisecond LTE frame.
While the frame duration is always the same, the channel bandwidth (FFT) varies dramatically.
3-21

Version 3 Rev 1 Channel Direction
Channel Direction
Figure 3-20 Channel Direction
The Down Link (DL) carries traffic flowing from or through the eNodeB to the subscribers, while the Up
Link (UL) carries traffic from the subscriber stations to the eNodeB. DL and UL bandwidth is shared by
the active subscribers in a sector.
DLand UL traffic may be carried on different (pairs of) frequencies, or the same frequency. Paired
frequency operation is called Frequency Division Duplexing (FDD), while single frequency operation
is known as Time Division Duplexing (TDD).
Frequency Division Duplexing (FDD)
Figure 3-21 Frequency Division Duplexing (FDD)

Channel Direction Version 3 Rev 1
Channel Direction
FDD uses pairs of frequencies, one to transmit traffic from the eNodeB to the subscribers (DL) and one
to receive traffic from the subscribers to the eNodeB (UL).
FDD operation uses LTE Frame Type 1.
Time Division Duplexing (TDD)
Figure 3-22 Time Division Duplexing (TDD)
TDD uses a single frequency for both directions of traffic. Both DL and UL traffic are included in the same
10 ms frame.
TDD operation may use LTE Frame Type 1 or 2. Frame Type 2 includes time gaps
to switch the transmit direction from DL to UL.
3-23

136280714-LTE100-Motorola-LTE-Training.pdf

136280714-LTE100-Motorola-LTE-Training.pdf

Recommended

Recommended

More Related Content

Similar to 136280714-LTE100-Motorola-LTE-Training.pdf

Similar to 136280714-LTE100-Motorola-LTE-Training.pdf (20)

More from MohamedShabana37

More from MohamedShabana37 (20)

Recently uploaded

Recently uploaded (20)

136280714-LTE100-Motorola-LTE-Training.pdf